installing manually oem fails instance not available [message #427644] |
Fri, 23 October 2009 13:32 |
evoradba
Messages: 144 Registered: April 2005 Location: Canada
|
Senior Member |
|
|
Hi
I just installed fresh oracle 11G on a solaris 10 machine and trying to create the oem keeps failing with error - also i had installed on a differnt server the same oracle version same O/S and no problems same steps
emca -config dbcontrol db -repos create
CONFIG: SQLEngine connecting with SID: TESTDB11, oracleHome: /home/oracle/produc
t/11G, and user: SYS
Oct 23, 2009 2:25:46 PM oracle.sysman.emcp.util.GeneralUtil initSQLEngine
CONFIG: SQLEngine created successfully and connected
Oct 23, 2009 2:25:52 PM oracle.sysman.emcp.util.GeneralUtil initSQLEngine
CONFIG: SQLEngine connecting with SID: TESTDB11, oracleHome: /home/oracle/product/11G, and user: DBSNMP
Oct 23, 2009 2:25:52 PM oracle.sysman.emcp.util.GeneralUtil initSQLEngine
CONFIG: ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
oracle.sysman.assistants.util.sqlEngine.SQLFatalErrorException: ORA-01034: ORACL
E not available
ORA-27101: shared memory realm does not exist
at oracle.sysman.assistants.util.sqlEngine.SQLEngine.executeImpl(SQLEngior
|
|
|
|
Re: installing manually oem fails instance not available [message #436151 is a reply to message #427644] |
Mon, 21 December 2009 20:59 |
winter_lady
Messages: 3 Registered: December 2009
|
Junior Member |
|
|
Ok found out that there was a bug with OEM 2.2, that was the reason i kept getting this error "ORA-12640: Authentication adapter initialization failed", one bug of many aparently.
The work around for this is to set the SQLNET.AUTHENTICATION_SERVICES= (NONE) in the sqlnet.ora file
Managed to get access to metalink and found at least 38 separate pacthes for 8.1.7. The one I downloaded was 115mb.
Also found out the reason why I kept getting the VNI-2015 error with OEM 2.0.4 was not because the credentials were wrong but because it has a bug that does not allow exporting or importing.
Managed to get past the VNI-2015 in OEM 2.2 by Instead of creating an OS user logon for the domain I created one for just the server and then granted "log on as a batch job".
Hope this is some help to any poor sole that gets stuck on the same problem.
|
|
|
|