VMware Cloud Community
ami857
Contributor
Contributor

Oracle 8.0.5 on ESXi

I’m trying to install Oracle 8.0.5 on an virtual Windows 2000 server based on an ESXi infrastructure. The physical machine is an IBM  SystemX 3200 M3 model  7328-K8G.  After installing Oracle 8.0.5 the following error is generated:

Fatal NI connect error 12203, connecting to (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=BEQ)(PROGRAM=oracle80)(ARGV0=oracle80ORCL)(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))')))(CONNECT_DATA=(SID=ORCL)(CID=(PROGRAM=G:\orant\BIN\SVRMGR30.EXE)(HOST=SERVERMIJLOCII)(USER=Administrator))))

  VERSION INFORMATION:

                TNS for 32-bit Windows: Version 8.0.5.0.0 - Production

                Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 8.0.5.0.0 - Production

  Time: 21-FEB-11 14:53:42

  Tracing not turned on.

  Tns error struct:

    nr err code: 12203

    TNS-12203: TNS:unable to connect to destination

    ns main err code: 12560

    TNS-12560: TNS:protocol adapter error

    ns secondary err code: 0

    nt main err code: 530

    TNS-00530: Protocol adapter error

    nt secondary err code: 0

    nt OS err code: 0

And the database doesn’t start

Can anyone help me?

Thanks

Reply
0 Kudos
4 Replies
admin
Immortal
Immortal

I'd verify listener (listener.ora and tnsnames.ora) configuration in both sides… And of course, check if lsnrctl is up and running, and with which services.

From the command line enter:

C:\> LSNRCTL80

LSNRCTL> STATUS LISTENER_NAME where LISTENER_NAME is the name of the network listener defined in the LISTENER.ORA file with the alias LISTENER. It is not necessary to identify the network listener if you are using the default network listener, named LISTENER.

Looks like a misconfiguration issue with Net8.

Here http://download.oracle.com/docs/pdf/A64419_01.pdf you can find Net8 config manual for Oracle 8.0.5.

Cheers.

--

Paulo García

Technical Account Manager

From: Communities emailer <communities-emailer@vmware.com<mailto:communities-emailer@vmware.com>>

Reply-To: Communities emailer <communities-emailer@vmware.com<mailto:communities-emailer@vmware.com>>

Date: Mon, 21 Feb 2011 23:32:58 -0800

To: Paulo Garcia <pgarcia@vmware.com<mailto:pgarcia@vmware.com>>

Subject: New message: "Oracle 8.0.5 on ESXi"[80d5he-ivde-10icw]

VMware Communities<http://communities.vmware.com/index.jspa>

Oracle 8.0.5 on ESXi

created by ami857<http://communities.vmware.com/people/ami857> in Virtualizing Oracle - View the full discussion<http://communities.vmware.com/message/1703408#1703408

Reply
0 Kudos
ami857
Contributor
Contributor

I’m afraid that this not the solution in my case. After I have done some research it looks that Oracle 8.0.5 want to write direct to the disk in some strange way and the virtualization layer is not what this Oracle wants.

As a matter of fact it didn’t even create the database. This is my opinion after doing some research, but I have no knowledge about Oracle in general.

Do you consider using raw device mapping for this virtual machine?

Reply
0 Kudos
admin
Immortal
Immortal

Hi,

Frankly, Oracle 8.0.x was a very "special" version. I don't know the reason why you're deploying 8.0. Maybe, you can consider the option of deploying Oracle 8.1.7. It was a very good an stable version, and probably you can run it in VM... I did it in the past.

If exists some reason to use 8.0, maybe using RDM can remove one posible source of problems. In this way you can access directly to the disk.

Resuming, If you can, try 8.1.7, if not, use RDM.

Cheers,

Paulo.

Reply
0 Kudos
ami857
Contributor
Contributor

It' licensing problem for Oracle 8.0.5. As I said I'm not a database administrator and not very familiar with this. I'll try RDM

Thank You very much

Mircea Albutiu

Reply
0 Kudos