Create option is failing :-( The first log shows all ok, except to the final (it is in the emca_repos_create log): Recompile invalid objects... ERROR: ORA-24344: correcto con error de compilacion ORA-06512: en linea 38 If I go to the other log with more details, it shows to the final: INFO: Creando el repositorio de EM. Puede tardar unos minutos... 31-ago-2011 9:55:57 oracle.sysman.emcp.EMReposConfig createRepository CONFIG: ORA-24344: correcto con error de compilacion ORA-06512: en linea 38 oracle.sysman.assistants.util.sqlEngine.SQLFatalErrorException: ORA-24344: correcto con error de compilacion ORA-06512: en linea 38 at oracle.sysman.assistants.util.sqlEngine.SQLEngine.executeImpl(SQLEngine.java:1467) at oracle.sysman.assistants.util.sqlEngine.SQLEngine.executeScript(SQLEngine.java:841) at oracle.sysman.assistants.util.sqlEngine.SQLPlusEngine.executeScript(SQLPlusEngine.java:265) at oracle.sysman.assistants.util.sqlEngine.SQLPlusEngine.executeScript(SQLPlusEngine.java:306) at oracle.sysman.emcp.EMReposConfig.createRepository(EMReposConfig.java:360) at oracle.sysman.emcp.EMReposConfig.invoke(EMReposConfig.java:182) at oracle.sysman.emcp.EMReposConfig.invoke(EMReposConfig.java:124) at oracle.sysman.emcp.EMConfig.perform(EMConfig.java:142) at oracle.sysman.emcp.EMConfigAssistant.invokeEMCA(EMConfigAssistant.java:479) at oracle.sysman.emcp.EMConfigAssistant.performConfiguration(EMConfigAssistant.java:1123) at oracle.sysman.emcp.EMConfigAssistant.statusMain(EMConfigAssistant.java:463) at oracle.sysman.emcp.EMConfigAssistant.main(EMConfigAssistant.java:412) 31-ago-2011 9:55:57 oracle.sysman.emcp.EMReposConfig invoke GRAVE: Error al crear el repositorio 31-ago-2011 9:55:57 oracle.sysman.emcp.EMReposConfig invoke 31-ago-2011 9:55:57 oracle.sysman.emcp.EMConfig perform CONFIG: Stack Trace: oracle.sysman.emcp.exception.EMConfigException: Error al crear el repositorio at oracle.sysman.emcp.EMReposConfig.invoke(EMReposConfig.java:194) at oracle.sysman.emcp.EMReposConfig.invoke(EMReposConfig.java:124) at oracle.sysman.emcp.EMConfig.perform(EMConfig.java:142) at oracle.sysman.emcp.EMConfigAssistant.invokeEMCA(EMConfigAssistant.java:479) at oracle.sysman.emcp.EMConfigAssistant.performConfiguration(EMConfigAssistant.java:1123) at oracle.sysman.emcp.EMConfigAssistant.statusMain(EMConfigAssistant.java:463) at oracle.sysman.emcp.EMConfigAssistant.main(EMConfigAssistant.java:412) Someone knows this error? I need help please. Thanks beforehand. 2011/8/31 Oliver <ofabelo@xxxxxxxxx> > I have simple instance, it isn't RAC environment. Is it valid too for me > configuration? thanks beforehand. > El 31/08/2011 06:18, "Sreejith S Nair" <Sreejith.Sreekantan@xxxxxxxxxx> > escribió: > > > Here are the manual steps for dropping emca. > > Please test it yourself before executing this. > > > > 1. stop dbconsole , if running and the following process from ORACLE_HOME > > > (from each node) > > > > $ps -ef | grep console > > $ps -ef| grep emwd > > $ps -ef | grep emagent > > $ps -ef |grep java > > > > 2. set env variables > > > > > > SET ORACLE_HOSTNAME=< Hostname of your machine " > > SET ORACLE_HOME=< Location where your database is installed > > > SET ORACLE_SID=< name of your database " > > SET PATH=%ORACLE_HOME%\bin;%PATH% > > > > 3. Logon SQLPLUS as user SYS or SYSTEM, and drop the sysman account and > > management objects: > > > > a. drop user sysman cascade; > > b. drop role MGMT_USER; > > c. drop user MGMT_VIEW cascade; > > d. drop public synonym MGMT_TARGET_BLACKOUTS; > > e. drop public synonym SETEMVIEWUSERCONTEXT; > > > > f. drop public synonym MGMT_target_blackouts; > > g. drop public synonym mgmt_severity_array; > > h. drop public synonym mgmt_guid_obj; > > > > > > + Verify any left over object owned by SYSMAN > > SQL> SELECT owner,TABLE_NAME, synonym_name name FROM dba_synonyms WHERE > > table_owner = 'SYSMAN'; > > > > if yo notice any public synonym or any rows returned by the above query . > > > > SQL> DECLARE > > CURSOR c1 IS > > SELECT owner, synonym_name name > > FROM dba_synonyms > > WHERE table_owner = 'SYSMAN'; > > BEGIN > > FOR r1 IN c1 LOOP > > IF r1.owner = 'PUBLIC' THEN > > EXECUTE IMMEDIATE 'DROP PUBLIC SYNONYM '||r1.name; > > ELSE > > EXECUTE IMMEDIATE 'DROP SYNONYM '||r1.owner||'.'||r1.name; > > END IF; > > END LOOP; > > END; > > / > > > > + move or rename config folders on each node : > > > > $rm -rf $ORACLE_HOME/<HOSTNAME_SID> > > $rm -rf $ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_<hostname>_<sid> > > > > > > You would replace the values in the <> with the correct values. > > > > > > With Regards, > > Sreejith > > > > > > > > > > > > > > From: Oliver <ofabelo@xxxxxxxxx> > > To: "Sweetser, Joe" <JSweetser@xxxxxxxx> > > Cc: Oracle L <oracle-l@xxxxxxxxxxxxx>, Sreejith Nair > > <sreejithsna@xxxxxxxxx> > > Date: 08/30/2011 10:40 PM > > Subject: RE: Backups failing > > Sent by: oracle-l-bounce@xxxxxxxxxxxxx > > > > > > > > Thanks to all. It hangs,so it didn't enter in quiesce mode. > > Can someone paste me the manual steps for dropping EM manually? thanks > > beforehand. > > El 30/08/2011 17:55, "Sweetser, Joe" <JSweetser@xxxxxxxx> escribió: > >> I agree with Sreejith but would suggest the quiesce state is a little > > more restrictive than just not accepting new connections. From here: > > > http://download.oracle.com/docs/cd/B28359_01/server.111/b28310/start004.htm > > > >> > >> Is this: > >> Occasionally you might want to put a database in a state that allows > > only DBA transactions, queries, fetches, or PL/SQL statements. Such a > > state is referred to as a quiesced state, in the sense that no ongoing > > non-DBA transactions, queries, fetches, or PL/SQL statements are running > > in the system. > >> > >> But if your emca process is hanging with both drop and recreate, then > > that may not be the issue. > >> > >> -joe > >> > >> -----Original Message----- > >> From: Sreejith Nair [mailto:sreejithsna@xxxxxxxxx] > >> Sent: Tuesday, August 30, 2011 10:42 AM > >> To: ofabelo@xxxxxxxxx > >> Cc: Sweetser, Joe; Oracle L > >> Subject: Re: Backups failing > >> > >> Quiesce mode means no new connections will be accepted. This is when you > > > use emca for dropping. With 11.2 database will not come in quiesce mode > > when dropping em repository and objects. > >> > >> However, I am not sure whether dropping em 'manually' will put database > > in quiesce mode for 10g. > >> I have done this ( manual drop ) in 11.2 and database does not go in > > quiesce mode. In my case also. Dropping using emca and Repmanager did > > hang, which is why I went for manual drop. > >> > >> Sreejith > >> ~Sent from my samsung phone > >> > >> ------- Original message ------- > >>> From: Oliver <ofabelo@xxxxxxxxx> > >>> To: sreejithsna@xxxxxxxxx > >>> Cc: JSweetser@xxxxxxxx, oracle-l@xxxxxxxxxxxxx > >>> Sent: 30/8/'11, 21:36 > >>> > >>> What is quiesce mode? > >>> Can someone paste me the content of that note? thanks. > >>> I've executed recreate but it hangs too,so I've executed drop first > > (although it hangs too). > >>> Thanks beforehand. > >>> El 30/08/2011 16:18, "Sreejith Nair" <sreejithsna@xxxxxxxxx> escribió: > >> > >> > >> Confidentiality Note: This message contains information that may be > > confidential and/or privileged. If you are not the intended recipient, > you > > should not use, copy, disclose, distribute or take any action based on > > this message. If you have received this message in error, please advise > > the sender immediately by reply email and delete this message. Although > > ICAT Managers, LLC, Underwriters at Lloyd's, Syndicate 4242, scans e-mail > > > and attachments for viruses, it does not guarantee that either are > > virus-free and accepts no liability for any damage sustained as a result > > of viruses. Thank you. > > > > > > > > > > > > > > DISCLAIMER: > > > > "The information in this e-mail and any attachment is intended only for > > the person to whom it is addressed and may contain confidential and/or > > privileged material. If you have received this e-mail in error, kindly > > contact the sender and destroy all copies of the original communication. > > IBS makes no warranty, express or implied, nor guarantees the accuracy, > > adequacy or completeness of the information contained in this email or > any > > attachment and is not liable for any errors, defects, omissions, viruses > > or for resultant loss or damage, if any, direct or indirect." > > > > > > > > >