10 Replies Latest reply: Nov 7, 2012 8:48 AM by OOmetie RSS

    MDS Schema Configuration failed

    530465
      Hi all,

      After reading this thread (OMS 11g failing in "OMS Configuration phase" I uninstalled WebLogic 10.3.3 and OEM, installed WebLogic 10.3.2 and OEM 11gR1 again. When it got to the MDS Schema Configuration of OEM, it failed.

      I proceeded to look in the /export/home/oracle/Middleware/oms11g/cfgtoollogs/cfgfw/ directory and found the following:

      emmdscreate.err:
      ERROR:MDSoracle.sysman.assistants.rcu.backend.RCUExecutionException: RCU-6091:Component name/schema prefix validation failed.
      oracle.sysman.assistants.rcu.backend.RCUExecutionException: RCU-6091:Component name/schema prefix validation failed.
      at oracle.sysman.assistants.rcu.backend.SilentRCUModel.performOperation(SilentRCUModel.java:139)
      at oracle.sysman.assistants.rcu.backend.RCUModel.startOperation(RCUModel.java:268)
      at oracle.sysman.assistants.rcu.Rcu.execute(Rcu.java:324)
      at oracle.sysman.emdrep.mds.EMMDSSchemaManager.perform(EMMDSSchemaManager.java:230)
      at oracle.sysman.emcp.oms.MDSSchemaConfiguration.perform(MDSSchemaConfiguration.java:66)
      at oracle.sysman.emcp.oms.BaseConfiguration.invoke(BaseConfiguration.java:151)
      at oracle.sysman.emCfg.core.PerformMicroStep.runJavaClass(PerformMicroStep.java:540)
      at oracle.sysman.emCfg.core.PerformMicroStep.executeMicroStep(PerformMicroStep.java:120)
      at oracle.sysman.emCfg.core.ActionPerformer.performMicroStep(ActionPerformer.java:917)
      at oracle.sysman.emCfg.core.ActionPerformer$Performer.run(ActionPerformer.java:1038)
      Parameters are: -silent -createRepository -compInfoXMLLocation /export/home/oracle/Middleware/oms11g/sysman/emdrep/config/mds/ComponentInfo.xml -storageXMLLocation /export/home/oracle/Middleware/oms11g/sysman/emdrep/config/mds/Storage.xml -connectString (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=mercy)(PORT=1521)))(CONNECT_DATA=(SID=emrep))) -dbUser SYS -dbRole sysdba -schemaPrefix SYSMAN -component MDS



      CfmLogger_2010-05-05_04-46-49-PM.log:
      INFO: encap_oms:IAction.perform() was called on {Action state:configuration in CfmAggregateInstance: encap_oms:1.0.0.0.0:common:family=CFM:oh=/export/home/oracle/Middleware/oms11g:label=0}
      INFO: Framework waiting for Action to complete at 15:41:55.383
      INFO: CfwProgressMonitor:actionProgress:About to perform Action=configuration Status=is running with ActionStep=0 stepIndex=0 microStep=0
      INFO: oracle.sysman.top.oms:About to execute plug-in MDS Schema Configuration
      INFO: oracle.sysman.top.oms:The plug-in MDS Schema Configuration is running
      INFO: oracle.sysman.top.oms:Internal PlugIn Class: oracle.sysman.emcp.oms.MDSSchemaConfiguration
      INFO: oracle.sysman.top.oms:Classpath = /export/home/oracle/Middleware/oms11g/sysman/jlib/omsPlug.jar:/export/home/oracle/Middleware/oms11g/jdbc/lib/ojdbc6.jar:/export/home/oracle/Middleware/oms11g/sysman/jlib/emcore_client.jar:/export/home/oracle/Middleware/oms11g/../modules/com.bea.core.apache.log4j_1.2.13.jar:/export/home/oracle/Middleware/oms11g/jlib/rcucommon.jar:/export/home/oracle/Middleware/oms11g/jdbc/lib/ojdbc6.jar:/export/home/oracle/Middleware/oms11g/sysman/jlib/emagentSDK.jar:/export/home/oracle/Middleware/oms11g/../oracle_common/modules/oracle.xdk_11.1.0/xmlparserv2.jar:/export/home/oracle/Middleware/oms11g/../oracle_common/modules/oracle.odl_11.1.1/ojdl.jar:/export/home/oracle/Middleware/oms11g/../oracle_common/modules/oracle.xdk_11.1.0/xml.jar:/export/home/oracle/Middleware/oms11g/../oracle_common/modules/oracle.jdbc_11.1.1/ojdbc6dms.jar:/export/home/oracle/Middleware/oms11g/../oracle_common/modules/oracle.dms_11.1.1/dms.jar:/export/home/oracle/Middleware/oms11g/../oracle_common/modules/oracle.odl_11.1.1/ojdl.jar:/export/home/oracle/Middleware/oms11g/jlib/rcu.jar:/export/home/oracle/Middleware/oms11g/jlib/SchemaVersion.jar
      INFO: oracle.sysman.top.oms:BaseConfiguration:invoke:Starting BaseConfiguration invoke method on an aggregate=oracle.sysman.top.oms for Action=configuration in step=3:microstep=0
      INFO: oracle.sysman.top.oms:__________________________DUMPING PARAMETERS______________________________________________
      INFO: oracle.sysman.top.oms:OracleHome: /export/home/oracle/Middleware/oms11g
      INFO: oracle.sysman.top.oms:Connect String: (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=mercy)(PORT=1521)))(CONNECT_DATA=(SID=emrep)))
      INFO: oracle.sysman.top.oms:SYS User: SYS
      INFO: oracle.sysman.top.oms:________________________________________________________________________
      INFO: oracle.sysman.top.oms:MDS Schema Creation status: FAILURE
      SEVERE: oracle.sysman.top.oms:MDS Schema Creation is failed
      INFO: oracle.sysman.top.oms:The plug-in MDS Schema Configuration has failed its perform method
      INFO: Cfm.save() was called
      INFO: Cfm.save(): 8 aggregate instances saved
      INFO: done waiting for Action from 15:41:55.383



      What could be the cause? Btw, I'm on CentOS 5.4 32-bit. Thanks in advance!
        • 1. Re: MDS Schema Configuration failed
          530465
          I found the following as well...

          /export/home/oracle/Middleware/oms11g/sysman/log/schemamanager/m_050510_0451_PM/m_050510_0451_PM.CREATE/rcu.log:

          2010-05-06 15:41:57.771 TRACE rcu: oracle.sysman.assistants.rcu.backend.action.AbstractAction::evaluateValidIf: EvaluationResult =false
          2010-05-06 15:41:57.771 TRACE rcu: oracle.sysman.assistants.rcu.backend.action.AbstractAction::getCommand: command=oracle.ias.version.SchemaVersionUtil:utilCreateRegistryTable
          2010-05-06 15:41:57.771 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.AbstractCompTask::execute: ValidIf result was false. Skipping Action: oracle.ias.version.SchemaVersionUtil:utilCreateRegistryTable
          2010-05-06 15:41:57.771 TRACE rcu: oracle.sysman.assistants.rcu.util.RCUCheckpoint::resetActionAndStatements: Entering.
          2010-05-06 15:41:57.771 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Execution time for Execute pre create operations : 65 milliseconds
          2010-05-06 15:41:57.771 TRACE rcu: oracle.sysman.assistants.rcu.backend.validation.StepValidator::isConnectionStepValidated: Clear the QueryResultsCache
          2010-05-06 15:41:57.771 TRACE rcu: oracle.sysman.assistants.rcu.backend.validation.StepValidator::setPrefixInfo: Entering.
          2010-05-06 15:41:57.794 TRACE rcu: oracle.sysman.assistants.rcu.backend.validation.StepValidator::setPrefixInfo: Existing prefix:
          2010-05-06 15:41:57.794 TRACE rcu: oracle.sysman.assistants.rcu.backend.validation.StepValidator::setPrefixInfo: Detect query before variable substitution:
          2010-05-06 15:41:57.795 TRACE rcu: oracle.sysman.assistants.rcu.backend.validation.StepValidator::setPrefixInfo: Detect query after variable substitution:
          2010-05-06 15:41:57.796 TRACE rcu: oracle.sysman.assistants.rcu.backend.validation.StepValidator::isConnectionStepValidated: Leaving.
          *2010-05-06 15:41:57.797 ERROR rcu: oracle.sysman.assistants.rcu.backend.RCUCommandLineParser::setComponentSelections: RCU-6016:The specified prefix already exists.*
          *2010-05-06 15:41:57.797 NOTIFICATION rcu: oracle.sysman.assistants.common.util.SilentMessageHandler::writeToLog: RCU-6016:The specified prefix already exists.*
          2010-05-06 15:41:57.797 ERROR rcu: oracle.sysman.assistants.rcu.backend.SilentRCUModel::performOperation: RCU-6091:Component name/schema prefix validation failed.
          2010-05-06 15:41:57.797 NOTIFICATION rcu: oracle.sysman.assistants.common.util.SilentMessageHandler::writeToLog: RCU-6091:Component name/schema prefix validation failed.


          The bolded lines could be caused by me manually dropping the schemas. What I did was I executed /export/home/oracle/app/oracle/product/11.2.0/dbhome_1/sysman/admin/emdrep/bin/RepManager. After executing it, it says:

          Enter SYS user's password :
          Enter repository user name : SYSTEM
          Getting temporary tablespace from database...
          Found temporary tablespace: TEMP
          Checking SYS Credentials ... rem error switch
          OK.
          rem error switch
          Dropping the repository..
          Checking for Repos User ... Exists.
          Repos User exists..
          Clearing EM Contexts ... OK.
          Dropping EM users ...
          Done.
          Dropping Repos User ...
          Done.
          Dropping Roles/Synonymns/Tablespaces ... Done.
          Dropped Repository Successfully.



          After doing that, the installer still complained the schema still exists. So I logged in through sqlplus and ran the following query:

          drop user SYSMAN_MDS cascade;

          And also the following to recompile because it was complaining:
          @/export/home/oracle/app/oracle/product/11.2.0/dbhome_1/sysman/admin/emdrep/sql/core/latest/admin/admin_recompile_invalid.sql SYSMAN
          • 2. Re: MDS Schema Configuration failed
            530465
            More update. It looks like it really has something to do with the SYSMAN_MDS I dropped. I was reading through the "Advanced Installation and Configuration Guide" and it says to run the following:

            $<ORACLE_HOME>/sysman/admin/emdrep/bin/mdsschemamanager.pl -action=-dropRepository -connectString=<database_connect_string> -dbUser= <database_user> -dbPassword=<database_password> -oracleHome=<OMS_oracle_home> -mwHome=<middleware_home>

            I got the following output:

            Error file cannot be created for /emmdsdrop.err
            log file cannot be created for /emmdsdrop_2010_05_06_AD_17_36_41_EDT.log
            2010_05_06_AD_17_36_41_EDT EMMDSSchemaManager: Info : Oracle Home is /export/home/oracle/Middleware/oms11g/
            2010_05_06_AD_17_36_41_EDT EMMDSSchemaManager: Info : Trying to set RCU_HOME to /export/home/oracle/Middleware/oms11g/
            2010_05_06_AD_17_36_41_EDT EMMDSSchemaManager: Info : RCU_HOME is /export/home/oracle/Middleware/oms11g/
            2010_05_06_AD_17_36_41_EDT EMMDSSchemaManager: Info : Trying to set SCRIPT_HOME to /export/home/oracle/Middleware/oms11g//rcu/integration
            2010_05_06_AD_17_36_41_EDT EMMDSSchemaManager: Info : SCRIPT_HOME is /export/home/oracle/Middleware/oms11g//rcu/integration
            2010_05_06_AD_17_36_41_EDT EMMDSSchemaManager: Info : Trying to set RCU_LOG_LOCATION to
            2010_05_06_AD_17_36_41_EDT EMMDSSchemaManager: Info : RCU_LOG_LOCATION is
            2010_05_06_AD_17_36_41_EDT EMMDSSchemaManager: Info : Trying to set RCU_LOG_NAME to emmds.log
            2010_05_06_AD_17_36_41_EDT EMMDSSchemaManager: Info : RCU_LOG_NAME is emmds.log
            Enter DBA Password
            Error file cannot be created for /emmdsdrop.err
            log file cannot be created for /emmdsdrop_2010_05_06_AD_17_36_41_EDT.log
            2010_05_06_AD_17_36_41_EDT EMMDSSchemaManager: Info : Oracle Home is /export/home/oracle/Middleware/oms11g/
            2010_05_06_AD_17_36_41_EDT EMMDSSchemaManager: Info : Trying to set RCU_HOME to /export/home/oracle/Middleware/oms11g/
            2010_05_06_AD_17_36_41_EDT EMMDSSchemaManager: Info : RCU_HOME is /export/home/oracle/Middleware/oms11g/
            2010_05_06_AD_17_36_41_EDT EMMDSSchemaManager: Info : Trying to set SCRIPT_HOME to /export/home/oracle/Middleware/oms11g//rcu/integration
            2010_05_06_AD_17_36_41_EDT EMMDSSchemaManager: Info : SCRIPT_HOME is /export/home/oracle/Middleware/oms11g//rcu/integration
            2010_05_06_AD_17_36_41_EDT EMMDSSchemaManager: Info : Trying to set RCU_LOG_LOCATION to
            2010_05_06_AD_17_36_41_EDT EMMDSSchemaManager: Info : RCU_LOG_LOCATION is
            2010_05_06_AD_17_36_41_EDT EMMDSSchemaManager: Info : Trying to set RCU_LOG_NAME to emmds.log
            2010_05_06_AD_17_36_41_EDT EMMDSSchemaManager: Info : RCU_LOG_NAME is emmds.log
            2010_05_06_AD_17_36_41_EDT EMMDSSchemaManager: Info : Prepare to initialize RCU
            2010_05_06_AD_17_36_41_EDT EMMDSSchemaManager: Info : RCU initialized with parameters : -silent -dropRepository -compInfoXMLLocation /export/home/oracle/Middleware/oms11g//sysman/emdrep/config/mds/ComponentInfo.xml -storageXMLLocation /export/home/oracle/Middleware/oms11g//sysman/emdrep/config/mds/Storage.xml -connectString mercy:1521:emrep -dbUser SYS -dbRole sysdba -schemaPrefix SYSMAN -component MDS
            2010_05_06_AD_17_36_41_EDT EMMDSSchemaManager: Info : Start rewriting mds.xml
            2010_05_06_AD_17_36_41_EDT removePrereqFromMDS : mdsComp.xml[export/home/oracle/Middleware/oms11g//rcu/integration/mds/mdsComp.xml]
            2010_05_06_AD_17_36_41_EDT removePrereqFromMDS : mds.xml[export/home/oracle/Middleware/oms11g//rcu/integration/mds/mds.xml]
            2010_05_06_AD_17_36_41_EDT EMMDSSchemaManager: Info : Finish rewriting mds.xml
            2010_05_06_AD_17_36_41_EDT EMMDSSchemaManager: Info : Invoking RCU
            Failed to initialize logger with location :/emmds.log
            Initializing logger using the following location :/tmp/logdir.2010-05-06_17-36/rcu.log
            Processing command line ....
            Repository Creation Utility - Checking Prerequisites
            Checking Global Prerequisites
            Repository Creation Utility - Checking Prerequisites
            Checking Component Prerequisites
            Repository Creation Utility - Drop
            Repository Drop in progress.
            ERROR:MDS ORA-01918: user 'SYSMAN_MDS' does not exist

            *2010_05_06_AD_17_36_42_EDT ERROR:MDS ORA-01918: user 'SYSMAN_MDS' does not exist*

            Percent Complete: 54
            RCU-6130:Action failed - RCU-6134:Error while trying to execute JDBC action.
            Repository Creation Utility: Drop - Completion Summary
            Database details:
            Host Name : mercy
            Port : 1521
            Service Name : EMREP
            Connected As : SYS
            Prefix for (prefixable) Schema Owners : SYSMAN
            RCU Logfile : /tmp/logdir.2010-05-06_17-36/rcu.log
            RCU Checkpoint Object : /tmp/logdir.2010-05-06_17-36/RCUCheckpointObj
            Component schemas dropped:
            Component Status Logfile
            Metadata Services Failed /tmp/logdir.2010-05-06_17-36/mds.log

            Repository Creation Utility - Drop : Operation Completed
            Creation of MDS schema fails
            2010_05_06_AD_17_36_42_EDT Creation of MDS schema fails




            How do I fix this?
            • 3. Re: MDS Schema Configuration failed
              user4678476
              Hi ppp,

              during the first install the MDS Schema Configuration inserts 1 line into table sys.SCHEMA_VERSION_REGISTRY.


              try "delete from SCHEMA_VERSION_REGISTRY where COMP_NAME='Metadata Services';

              Then the "MDS Schema Configuration" was succesfull.

              Ci Andreas
              • 4. Re: MDS Schema Configuration failed
                530465
                Hi Ci,

                Thanks for the reply! Unfortunately, since I wasn't sure what to do, I have begun to uninstall all the components (Oracle + WebLogic + OEM). Hoping this time if I start fresh with the right version, I will have a smooth install. As a result, I won't be able to try your suggestion.

                Thanks for the suggestion!

                PPPP
                • 5. Re: MDS Schema Configuration failed
                  628404
                  Hi,

                  I have encountered the same issue when reinstalling OEM 11g coz my first attempt was on Web Logic 10.3.3 (must be 10.3.2) and once deleted that one entry:

                  delete from SCHEMA_VERSION_REGISTRY where COMP_NAME='Metadata Services';

                  installer was able to continue!

                  Many Thanks Andreas!

                  Cheers!!
                  • 6. Re: MDS Schema Configuration failed
                    user102422
                    Yeah it worked !!

                    I faced the same problem too, I was installing Oracle EM Grid 11.1.0.1.0 on top of Oracle Weblogic Server 10.3.2 after failing to install it on top of 10.3.3 but it got stuck at "MDS Schema configuration".

                    I deleted the only present row in that table and hit the retry and installation passed that stage successfully.

                    Regards,
                    Sayeed Salahuddin.
                    • 7. Re: MDS Schema Configuration failed
                      628404
                      Guys,

                      Please note that this trick also applies to SOA SUIT 11g.

                      Always keep watching on that SCHEMA_VERSION_REGISTRY table when installing, reinstalling the Oracle software.

                      Cheers!!
                      • 8. Re: MDS Schema Configuration failed
                        830195
                        Thanks Ci you got it!

                        It worked for me as well with the following installation :

                        OEM Grid Control 11gR1
                        Weblogic Server 10.3.2.0
                        Oracle Database 10.2.0.4

                        I had the same described issue and performed the manual delete and comitted it. The solution is described here ID 1100284.1 at oracle support.

                        It is related to an incorrect drop of sysman_mds schema and the resulting repository record for the sysman_mds schema is not clean. This can be corrected while the new Grid Control installer session is stopped in the failed state.


                        Regards
                        --
                        Moufid Zeribi

                        Edited by: moufid on 24 mars 2011 02:16
                        • 9. Re: MDS Schema Configuration failed
                          ramkumars77
                          Thanks Andreas...

                          Yours was the exact solution I needed ...

                          Ram
                          • 10. Re: MDS Schema Configuration failed
                            OOmetie
                            Thanks a lot. It worked for me too. The installer had been stuck for over an hour on the MDS.