Home » RDBMS Server » Server Administration » ORA-15180 (merged) (Oracle 11G:11.1.0.6.0:Windows Server 2003)
icon2.gif  ORA-15180 (merged) [message #418971] Wed, 19 August 2009 07:45 Go to next message
amul
Messages: 252
Registered: April 2001
Location: Chennai
Senior Member
Hi,

I am facing the error ORA-15180 while trying to start the database.

DB Version:11.1.0.6.0

I have the administrator privileges in my system.

I have given permission to my ID to the LIB folder, with Full control.

OS used: Windows Server 2003.

Regards,
Abdul

[Updated on: Wed, 19 August 2009 08:35] by Moderator

Report message to a moderator

Re: ORA-15180 [message #418983 is a reply to message #418971] Wed, 19 August 2009 08:35 Go to previous messageGo to next message
Michel Cadot
Messages: 68718
Registered: March 2007
Location: Saint-Maur, France, https...
Senior Member
Account Moderator
ORA-15180: Could not open dynamic library %s, error [%s]
 *Cause:  The library was not accessible
 *Action: Correct the permissions of the library and try again
Re: ORA-15180 [message #419117 is a reply to message #418983] Wed, 19 August 2009 22:23 Go to previous messageGo to next message
amul
Messages: 252
Registered: April 2001
Location: Chennai
Senior Member
I have given full control to my id in all the folders including the LIB folder, but still i am facing this issue
Re: ORA-15180 (merged) [message #419118 is a reply to message #418971] Wed, 19 August 2009 22:28 Go to previous messageGo to next message
BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal
Senior Member
> but still i am facing this issue
Trust the error message. Oracle is too dumb to lie.
Please post whole & complete error message.
Re: ORA-15180 (merged) [message #419119 is a reply to message #419118] Wed, 19 August 2009 23:02 Go to previous messageGo to next message
amul
Messages: 252
Registered: April 2001
Location: Chennai
Senior Member
Hi,

Please find the complete error message when i try to startup.

ORA-15180 Could not open Dynamic Library ODM library error[The specified module could not b]
Re: ORA-15180 (merged) [message #419120 is a reply to message #419119] Wed, 19 August 2009 23:31 Go to previous messageGo to next message
ThomasG
Messages: 3212
Registered: April 2005
Location: Heilbronn, Germany
Senior Member
Has this ever worked, or is this a fresh install that never worked?

If the full message is "The specified module could not be loaded", then it could be a i386/x64 conflict, if the full message is "The specified module could not be found", then it still looks like a permission / path problem.

Can't you post the really complete error message?
Re: ORA-15180 (merged) [message #419123 is a reply to message #418971] Wed, 19 August 2009 23:36 Go to previous messageGo to next message
BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal
Senior Member
From what I have learned, ODM seems to be Oracle Disk Manager; what ever that may be.
I am not going spend more time chasing this ghost.
Re: ORA-15180 (merged) [message #419149 is a reply to message #419120] Thu, 20 August 2009 01:32 Go to previous messageGo to next message
amul
Messages: 252
Registered: April 2001
Location: Chennai
Senior Member
This DB was working fine till this issue came up.

This is the complete error i got. If you dont believe i can upload screenshot.
Re: ORA-15180 (merged) [message #419221 is a reply to message #418971] Thu, 20 August 2009 09:29 Go to previous messageGo to next message
BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal
Senior Member
>This DB was working fine till this issue came up.
You are reporting Oracle was working, until it stopped working.
OK.
What changed between when it was working & when it stopped working?
Re: ORA-15180 (merged) [message #419397 is a reply to message #419149] Fri, 21 August 2009 16:26 Go to previous message
ThomasG
Messages: 3212
Registered: April 2005
Location: Heilbronn, Germany
Senior Member
amul wrote on Thu, 20 August 2009 08:32
This is the complete error i got. If you dont believe i can upload screenshot.


Then look in the alert.log for the complete error. Or try to start the database from the command line to get the complete error.
Previous Topic: ORA-01652: unable to extend temp segment by 64 in tablespace TEMP
Next Topic: block cleanout
Goto Forum:
  


Current Time: Sun Dec 01 17:26:30 CST 2024