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:
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.
Technical Account Manager
Date: Mon, 21 Feb 2011 23:32:58 -0800
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
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?
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.
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