Database Connection [message #322206] |
Thu, 22 May 2008 15:09 ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
wkray
Messages: 1 Registered: May 2008
|
Junior Member |
|
|
We have two computers that are using Oracle to back-up databases. We had the
system up and running for a couple weeks after we moved to a new location (where the computers were given new IP addresses) but then things just stopped working.
Symantec found a couple copies of 'hacktool' on the computers (and removed them)
which I'm not sure is relevant or not. When we try to start software that uses
Oracle, we get an error saying 'database connection failed' or 'oracle
initialization or shut down in progress.'
In the nmiconf.log are the following errors:
Warning : Skipping OracleOraHome92TNSListener : Could not find corresponding
listener definition in {D:\oracle\ora92\network\admin\listener.ora}
Warning : No Listener found for SID PSDB. PSDB will be skipped
Warning : Error while sourcing third party discovery file emddiscover.tcl :
unable to get value "em_loc" from key "HKEY_LOCAL_MACHINE\Software\Oracle" :
The system cannot find the file specified.
I ran the WSname change script but was told by the computer that no change to the listener file was necessary.
Any help you can provide would be greatly appreciated.
Keith
|
|
|
Re: Database Connection [message #322215 is a reply to message #322206] |
Thu, 22 May 2008 15:38 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) |
joy_division
Messages: 4963 Registered: February 2005 Location: East Coast USA
|
Senior Member |
|
|
I don't know anything about how Oracle runs in Windows, so I don't about anything about HKEY_LOCAL_MACHINE, but did you check the first error you got? Quote: |
Warning : Skipping OracleOraHome92TNSListener : Could not find corresponding
listener definition in {D:\oracle\ora92\network\admin\listener.ora}
|
Is that file there?
Sounds like maybe Symantec removed some files that Oracle needs. If initialization or shutdown is in progress, connect internal and abort, since it seems you never got the database up and running in the new location. you may have not shut it down properly from the old location.
|
|
|