unable to connect after installing OEM 2.0

Here's the configuration: Multiple NT4.0 servers, each hosting multiple Oracle databases. One server (let's call it ORASRV_1) has multiple Oracle homes. D:\orant80 for Oracle 8.0.5, and D:\orant8i for Oracle 8.1.5. There are currently no 8.1.5 databases on the server. In the registry key HKLM\software\oracle, we have set the value TNS_ADMIN = E:\oradmin\net80\admin. In that directory (E:\oradmin\net80 \admin) we have a TNSNAMES file that has entries for all databases, regardless of the host server. (Yes, I know about Oracle Names, but that's a different issue.)

All of the above has been working fine for well over a year. Now the problem. Today I installed Oracle Enterprise Manager 2.0 on the above described server, ORASRV_1. Instructions said it needed to be in an 8.1.6 home, so I specified an \ORANT816 directory during installation. I specified *local* name resolution during install. Now, I can only connect to databases that are on the local box, ORSRV1. This holds true for SQL*Plus as well as the OEM2.0 products. It is behaving as if the TNSNAMES file only has entries for the databases on this server, yet there are no TNSNAMES files like that. I can connect to every db on the server, but none of the db's on any other server. Yet every TNSNAMES file on the server (and several have gotten scattered around over the years) has entries for db's on multiple boxes.

Another strange thing I observed was the TNSNAMES.ORA file created during installation/configuration of OEM 2.0. We have never used a multi-domain model for our oracle networking files -- everthing is simply dbname.WORLD. Yet the TNSNAMES file that the OEM install set up an entry for dbname.node1.node2 (where node1.node2) are real nodes on our corporate network). *I* never specified these nodes anywhere during installation, but somehow the installer detected them and assumed to use them.

--
Ed Stevens
(Opinions are not necessarily those of my employer)


Sent via Deja.com http://www.deja.com/
Before you buy.