OWB 10 repository creation issues in a 9.2.0.8 Db (using Rep Assitant)

I’m using Oracle Database Enterprise Edition 9.2.0.8 and I installed the Oracle Warehouse Builder 10.2.0.1 in the same machine (in a different oracle home, once in the installation process doesn’t allow to install in the same oracle home from the database).
While configuring the repository with the Repository Assistant, I’m experiencing a big delay in the step 5 of 8: Repository Owner Information (around 2 hours) of the advanced wizard, which ends with the error box showing the message “Database Connection Failed: ORA-00600: internal error code, arguments: [17059], [0x697F83FC] , [], [], [], [], [], []”.
Anyone had this issue? Is anyone able to help?
Thank you very much,
Miguel

have you check the Database alert log file...
is there any memory issue..........
Cheers
Nawneet

Similar Messages

  • OWB Repository creation failed at the end with ORA-01403 & ORA-06512

    I got the below error during the OWB Repository Creation on RAC Database which is newly created(11.2.0.3)
    =========================================
    java.lang.Exception: The workspace user installation failed on user(s):
    owb_cdr:
    java.lang.Exception: ORA-01403: no data found
    ORA-06512: at "OWBSYS.GETROLESTARTED", line 31
    ORA-06512: at line 1
    =========================================
    I was checking this MOM: OWB Design Client Fails to Connect to Repository With ORA-06512: at "OWBSYS.GETROLESTARTED" (Doc ID 1355764.1)
    But why this is happening for first time as this is a Fresh database.
    Can anyone help on this??? Any workaround for this issue?

    I got the below error during the OWB Repository Creation on RAC Database which is newly created(11.2.0.3)
    =========================================
    java.lang.Exception: The workspace user installation failed on user(s):
    owb_cdr:
    java.lang.Exception: ORA-01403: no data found
    ORA-06512: at "OWBSYS.GETROLESTARTED", line 31
    ORA-06512: at line 1
    =========================================
    I was checking this MOM: OWB Design Client Fails to Connect to Repository With ORA-06512: at "OWBSYS.GETROLESTARTED" (Doc ID 1355764.1)
    But why this is happening for first time as this is a Fresh database.
    Can anyone help on this??? Any workaround for this issue?

  • OWB Repository Creation with Repository Assistant

    Dear All,
    Im getting an error when configuring owb repository, this error raising at OWBSYS Information step. following is the error im getting
    OWB software with the compatible version must be installed locally on the database server machine. If it is already installed, please acquire the DBA user credentials, and run the SQL script owb/uUnifiedRepos/remote_owb_install.sql. on the database server machine. This creates a database directory named 'OWB_REMOVE_ADMIN' that the remote installation will access to read the database servers OWBHOME/owb/bin/admin directory. Relaunch the repository Assistant or execute OWB scripting command OMBSEED top seed the repository.
    Im trying to create repository on a database in another remote server. below are the my system details...
    Machine 1
    OS:Windows Server 2008 R2 (64 bit)
    Database: Oracle Database 11g Release 11.2.0.1.0 - 64bit Production
    Machine 2
    OS: Windows 7 Ultimate (32 bit)
    Database: Oracle Database 11g Release 11.2.0.1.0 - 32bit Production
    since i couldn't open design center in 64 bit environment im using the design center installed in 32 bit. where am i going wrong? what will be the ideal solution for this?
    thanks in advance.

    Hi,
    The error is self explanatory.
    If you are doing repository installation on remote server you have to run the script <OH>/owb/uUnifiedRepos/remote_owb_install.sql(where OH is Oracle Home) in order to set the remote OWB home.
    So as suggested in the error message itself you need to connect to the database as any DBA user and run the script remote_owb_install.sql and do the repository installation.
    Regards,
    Pnreddy.

  • Content Repository creation issue in OAC0 tcode

    Dear All ,
    I installed Content Server 640 verison with Max DB 7.6 successfully on Windows Server 2008 R2 server.I did the the installation on the same server where my ECC development system is running.
    When I'm creating the content repository in OAC0 getting the below error.
    <<<<CreateTab ContentStorage, connect error SQLConnect failed, [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified, Error Code: 0>>>>
    I followed SAP Note 301352 - ODBC driver is not registered ,and used the below command to register ODBC driver but it gives me error saying Can't create registry value.
    C:\>odbcreg LiveCache -i -p f:\sapdb\programs\pgm
    Error : Can't create registry value.
    I did the installation using domain ID which is assigned to administrators group on local host.not able to figure it out ,whats the issue.
    Can you please help me to fix this issue please.
    thanks

    Hi Khaiser,
    You need to do the following,
    In CSADMIN got to setting.
    Add the parameter : Driver = MaxDB
    Restart the system and check it should work.
    Regards,
    Deepak Kori

  • Master repository creation issue

    Hi ,
    I am trying to create ODI master repository. During the process I have received following error and not sure how I can resolve the issue.
    oracle.odi.setup.RepositorySetupException: com.sunopsis.tools.core.exception.SnpsSimpleMessageException: ODI-10036: Importing object SNP_LINEACTION : null failed.
         at oracle.odi.setup.support.MasterRepositorySetupImpl.internalCreateMaster(MasterRepositorySetupImpl.java:148)
         at oracle.odi.setup.support.MasterRepositorySetupImpl.createMasterRepository(MasterRepositorySetupImpl.java:222)
         at oracle.odi.ui.gallery.support.MasterCreateRepositoryPage.invoke(MasterCreateRepositoryPage.java:221)
         at oracle.odi.ui.gallery.support.AbstractMasterRepositoryWizard$2.run(AbstractMasterRepositoryWizard.java:144)
         at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:656)
         at java.lang.Thread.run(Thread.java:662)
    Caused by: com.sunopsis.tools.core.exception.SnpsSimpleMessageException: ODI-10036: Importing object SNP_LINEACTION : null failed.
         at com.sunopsis.dwg.DwgDuplicationTools.importOtherObjects(DwgDuplicationTools.java:2660)
         at com.sunopsis.dwg.DwgDuplicationTools.synonymImport(DwgDuplicationTools.java:2130)
         at com.sunopsis.dwg.DwgObject.importFromObjectLst(DwgObject.java:6493)
         at com.sunopsis.dwg.DwgObject.doImport(DwgObject.java:6011)
         at com.sunopsis.dwg.DwgObject.importFromXml(DwgObject.java:5650)
         at com.sunopsis.dwg.DwgObject.importFromXmlWithCommit(DwgObject.java:5695)
         at com.sunopsis.dwg.DwgObject.importFromXmlWithCommit(DwgObject.java:5663)
         at com.sunopsis.repository.manager.RepositoryManager.importObjectsUsingImportFromXML(RepositoryManager.java:5126)
         at com.sunopsis.repository.manager.RepositoryManager.treatObjectList(RepositoryManager.java:3274)
         at com.sunopsis.repository.manager.RepositoryManager.treatTechnoList(RepositoryManager.java:3533)
         at com.sunopsis.repository.manager.RepositoryManager.masterRepositoryImport(RepositoryManager.java:2702)
         at com.sunopsis.repository.manager.RepositoryManager.masterRepositoryCreation(RepositoryManager.java:1141)
         at oracle.odi.setup.support.MasterRepositorySetupImpl.internalCreateMaster(MasterRepositorySetupImpl.java:141)
         at oracle.odi.setup.support.MasterRepositorySetupImpl.createMasterRepository(MasterRepositorySetupImpl.java:222)
         at oracle.odi.ui.gallery.support.MasterCreateRepositoryPage.invoke(MasterCreateRepositoryPage.java:221)
         at oracle.odi.ui.gallery.support.AbstractMasterRepositoryWizard$2.run(AbstractMasterRepositoryWizard.java:144)
         at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:655)
         ... 1 more
    Caused by: java.sql.SQLException: ORA-01658: unable to create INITIAL extent for segment in tablespace ODI_DEMO
         at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:457)
         at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:405)
         at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:889)
         at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:476)
         at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:204)
         at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:540)
         at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:217)
         at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:1079)
         at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1466)
         at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3752)
         at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3887)
         at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1508)
         at com.sunopsis.sql.SnpsQuery.executeUpdate(SnpsQuery.java:650)
         at com.sunopsis.dwg.dbobj.generated.GeneratedSnpLineAction.insertAction(GeneratedSnpLineAction.java:601)
         at com.sunopsis.dwg.DwgObject.insertActionForDuplication(DwgObject.java:3202)
         at com.sunopsis.dwg.DwgObject.insertForDuplication(DwgObject.java:3443)
         at com.sunopsis.dwg.DwgDuplicationTools.importOtherObjects(DwgDuplicationTools.java:2616)
         ... 17 more
    Please help me to get the issue resolved.

    Hi
    Error : ORA-01658: unable to create INITIAL extent for segment in tablespace string
    Cause: Failed to find sufficient contiguous space to allocate INITIAL extent for segment being created.
    Action: Use ALTER TABLESPACE ADD DATAFILE to add additional space to the tablespace or retry with a smaller value for INITIAL
    Check with DBA hope he will helps you toresolve your issue by inceasing tablespace memory
    Regards,
    Phanikanth

  • ODI - Master Repository Creation Issue

    Hi Experts, I trying to create a master repository in ODI Standalone version 11.1.1 (Internal Version 11.1.1.7.0_GENERIC_130302.2156) but the following error was ocurred:
    oracle.odi.setup.RepositorySetupException: Error while updating Schema Version Registry Entry for ODI. Check if user system has DBA permissions.
    at oracle.odi.setup.support.SchemaVersionUtil.setComponentInvalid(SchemaVersionUtil.java:234)
    at oracle.odi.setup.support.MasterRepositorySetupImpl.createMasterRepository(MasterRepositorySetupImpl.java:262)
    at oracle.odi.ui.gallery.support.MasterCreateRepositoryPage.invoke(MasterCreateRepositoryPage.java:231)
    at oracle.odi.ui.gallery.support.AbstractMasterRepositoryWizard$2.run(AbstractMasterRepositoryWizard.java:168)
    at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:655)
    at java.lang.Thread.run(Thread.java:662)
    Caused by: java.sql.SQLException: setComponentInvalid: component 'ODI' not found in schema_version_registry
    at oracle.ias.version.SchemaVersion.setComponentInvalid(SchemaVersion.java:1949)
    at oracle.odi.setup.support.SchemaVersionUtil.setComponentInvalid(SchemaVersionUtil.java:232)
    ... 5 more
    Do you have any idea what might be going wrong?
    Thanks in Advance!!!
    Héctor Ortega

    Looking at the error, it seems its permissions related issues. Check if all required permissions are set for ODI Master repository user/schema & system user.
    Its trying to update ODI repository version in SCHEMA_VERSION_REGISTRY table under system tables, but not able to do it due to lack of sufficient privileges.
    Regards,
    Santy

  • Cleasing repository creation issue

    Hi,
    I am trying to create a cleasing repository for which i performed following steps:
    1.Created a database dq_repo in Microsoft SQL Server 2008 R2
    2.Created a Local repository using the dq_repo database.
    3.Then i tried to install cleasing package on this repository(dq_repo) by selecting Cleansing Package in BODS
    Repository Manager.
    4.When i hit on the Create button, it gives me an error that  'Cleansing repository does not exist'.
    5.So, i go to the BODS Designer and give the dq_repo details in Dictionary->Manage Connections.
    6.I tried to create the cleansing package now, so it gives me and error that *'Cleansing package does not contain any   
    dictionaries'.But , when i checked at the path "C:\Program Files\Business Objects\BusinessObjects Data
    Services\DataQuality\datacleanse",i see that dictionaries are present.
    Now my questions are:
    1.Whether i am taking the right approach to create the cleasing repository?
    2.If yes, where am i going wrong in my above mentioned steps?
    FYI:
    1. Enviornment:
    a.Windows XP
    b.Database- Microsoft SQL Server 2008 R2
    c.SAP BODS 3.12 with cleasing patch installed.
    2.BODS services are on.
    Please help me on this problem.

    Priyanka,
    With DS 3.X, the Cleansing Package installer must be run first which lays down the pieces that are used within the Repository Manager when you select Cleansing Package as the repository type.  If this has not be run, you won't be able to use Repo Manager to set this up. 
    Also, in Designer, you are not able to connect to a Cleansing Package using Manage Connection, until the Repo Manager part has been completed.
    To tell if this installer has been run, look to LINK_DIR\DataQuality\datacleanse to see if there are any PERSON_FIRM_*.zip files there.  If not, you know it has not been run.  If there are, the next step is to create a database to hold the cleansing package and then use Repository Manager to seed it.
    Thanks,
    Paula
    FYI...if you are really using 3.1X, that is not supported any longer and you should upgrade.  The latest version of DS is 4.0 and has changed significantly since 3.X for the CP installer as well as having the requirement of installing BIP/IPS.  Please see upgrade guide for information on this.

  • OWB repository creation error

    I will close this Post
    Edited by: ORV on Apr 24, 2013 3:49 PM

    Please post in the correct forum Warehouse Builder
    Sybrand Bakker
    Senior Oracle DBA

  • OAS 10g metadata repository creation assistant & database version issue

    Hi,
    I have to install Oracle Application Server 10.1.2.0.2 on a server which already has an Oracle database 11g running on it and I dont want to install another database due to the load factor. I am not sure if I could use that database
    (version 11g) for the metadata repository. I know that we can use an existing database for the creation of metadata repository using the metadata creation assistant but I am a bit worried about the version of the database which is 11g whereas the application server and the metadata creation assistant both are 10.1.2.x.
    Your help is highly appreciated.
    Cheers,
    Omer

    MRCA 10.1.2.0.2 cannot be used to install a repository in an 11g database. If you want to use MRCA 10.1.2.0.2 with an 11g database, you will need to install a 10g database first, create the metadata repository and then upgrade the database to 11g. Not applicable in your environment as you already have a 11g database.
    Regards,
    EJ

  • OWB 10g R2 Design repository creation problem

    Hi All,
    When i try to create OWB repository with Repository assistant i get the following error :
    ORA-22905 cannot access rows from a non nested table iteam
    ORA-06512 at line 17.
    My environment details are as given below.
    O/S : Windows 2000
    Oracle: Release 9.2.0.1.0
    OWB: Release 10.2.0.1.0
    Any help or suggestion plz.
    Thanks & Regards
    Amit Gupta

    Hi Jorg,
    OWB installation and configuration document says
    Warehouse Builder 10g Release 2 (10.2) is supported and certified for use with the
    following releases of the Oracle database:
    &#9632; Oracle9i Release 2 (9.2.x) Enterprise Edition
    &#9632; Oracle Database 10g Enterprise Edition R1 (10.1.x)
    &#9632; Oracle Database 10g Standard Edition R2 (10.2.x)
    &#9632; Oracle Database 10g Enterprise Edition R2 (10.2.x)
    Regds.
    Amit

  • Getting Error while installing Repository Creation Utility (RCU)!!!!!

    Hi,
    While installing RCU, I was getting the Invalid Username/Password error on Database Connection Details Screen when i give sys userid. on Database Connection Details Screen I was trying to connect with sys user but failed then I used system user and it got connect.
    Then on Component screen, I was getting the below error.
    RCU-6083:Failed - Check prerequisites requirement for selected component:ORAESS
    Please refer to RCU log at /u01/app/oracle/logdir.2009-12-22_16-46/rcu.log for details.
    Trying to connect as a non SYSDBA user. User should have SYSDBA privileges to successfully load the ESS schema.
    RCU-6092:Component Selection validation failed. Please refer to log at /u01/app/oracle/logdir.2009-12-22_16-46/rcu.log for details.
    I do not know why i am unable to connect with sys user as i am giving the correct password. Now i have changed the sys password but still unable to connect.
    Please check the below link.
    http://download.oracle.com/docs/cd/E12839_01/doc.1111/e14259/rcu_screens.htm
    Please suggest something.
    --- Log File Error ------------------------
    2009-12-22 16:46:06.904 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: HOSTNAME: cicl-11g
    2009-12-22 16:46:06.912 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: OSINFO: i386 2.6.18-164.6.1.el5 Linux
    2009-12-22 16:46:06.912 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: JREINFO: 1.6.0_14 /u01/app/oracle/rcuHome/jdk/jre
    2009-12-22 16:46:06.912 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: USERNAME: oracle
    2009-12-22 16:46:06.912 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: USERDIR: /u01/app/oracle/rcuHome/bin
    2009-12-22 16:46:06.912 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: User country: US
    2009-12-22 16:46:06.912 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: User language: en
    2009-12-22 16:46:06.913 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: Java class path: /u01/app/oracle/rcuHome/jlib/rcu.jar:/u01/app/oracle/rcuHome/jlib/share.jar:/u01/app/oracle/rcuHome/jlib/help-share.jar:/u01/app/oracle/rcuHome/jlib/ohj.jar:/u01/app/oracle/rcuHome/jlib/orai18n-mapping.jar:/u01/app/oracle/rcuHome/lib/xmlparserv2.jar:/u01/app/oracle/rcuHome/jdbc/lib/ojdbc5.jar:/u01/app/oracle/rcuHome/jdbc/lib/ojdbc14.jar:/u01/app/oracle/rcuHome/jlib/jewt4.jar:/u01/app/oracle/rcuHome/jlib/ojdl.jar:/u01/app/oracle/rcuHome/modules/oracle.odl_11.1.1/ojdl.jar:/u01/app/oracle/rcuHome/jlib/SchemaVersion.jar:/u01/app/oracle/rcuHome/jlib/wlsqlserver.jar:/u01/app/oracle/rcuHome/jlib/wlbase.jar:/u01/app/oracle/rcuHome/jlib/wlutil.jar:/u01/app/oracle/rcuHome/jlib/com.bea.core.weblogic.workmanager_1.6.0.0.jar:/u01/app/oracle/rcuHome/jlib/com.bea.core.weblogic.workmanager_1.7.0.0.jar:/u01/app/oracle/rcuHome/jlib/wldb2.jar:/u01/app/oracle/rcuHome/jlib/help-share.jar:/u01/app/oracle/rcuHome/jlib/ohj.jar:/u01/app/oracle/rcuHome/jlib/oracle_ice.jar:/u01/app/oracle/rcuHome/jlib/rcuhelp.jar:/u01/app/oracle/rcuHome/jlib/rcuhelppages.jar:/u01/app/oracle/rcuHome/assistants/opca/jlib/opca.jar:/u01/app/oracle/rcuHome/portal/jlib/ptlshare.jar:/u01/app/oracle/rcuHome/jlib/ldapjclnt11.jar:/u01/app/oracle/rcuHome/jlib/commons-collections-3.1.jar:/u01/app/oracle/rcuHome/jlib/commons-dbcp-1.2.1.jar:/u01/app/oracle/rcuHome/jlib/commons-logging.jar:/u01/app/oracle/rcuHome/jlib/commons-pool-1.2.jar:/u01/app/oracle/rcuHome/jlib/quartz-1.6.0.jar:/u01/app/oracle/rcuHome/jlib/jta.jar:/u01/app/oracle/rcuHome/jlib/xml.jar:/u01/app/oracle/rcuHome/jlib/iam-platform-utils.jar:/u01/app/oracle/rcuHome/jlib/iam-platform-authz-service.jar:/u01/app/oracle/rcuHome/jlib/iam-features-identity.zip:/u01/app/oracle/rcuHome/jlib/iam-features-configservice.zip:/u01/app/oracle/rcuHome/jlib/jps-api.jar:/u01/app/oracle/rcuHome/jlib/jps-common.jar:/u01/app/oracle/rcuHome/jlib/jps-ee.jar:/u01/app/oracle/rcuHome/jlib/jps-internal.jar:/u01/app/oracle/rcuHome/jlib/jps-manifest.jar:/u01/app/oracle/rcuHome/jlib/MicroSM.jar:/u01/app/oracle/rcuHome/jlib/javax.persistence_1.0.0.0_1-0-2.jar:/u01/app/oracle/rcuHome/jlib/org.eclipse.persistence_1.0.0.0_1-1-0.jar:/u01/app/oracle/rcuHome/jlib/identitystore.jar:/u01/app/oracle/rcuHome/jlib/jps-unsupported-api.jar:/u01/app/oracle/rcuHome/jlib/pd-internal.jar
    2009-12-22 16:46:06.913 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: Java library path: /u01/app/oracle/rcuHome/jdk/jre/lib/i386/client:/u01/app/oracle/rcuHome/jdk/jre/lib/i386:/u01/app/oracle/rcuHome/jdk/jre/../lib/i386:/u01/app/oracle/rcuHome/lib32:/u01/app/oracle/rcuHome/network/lib32:/u01/app/oracle/rcuHome/lib:/u01/app/oracle/rcuHome/network/lib:/u01/app/oracle/product/11.2.0/network/lib:/u01/app/oracle/product/11.2.0/jdbc/lib:/u01/app/oracle/product/11.2.0/lib:/usr/lib:/usr/local/lib:/usr/java/packages/lib/i386:/lib:/usr/lib
    2009-12-22 16:46:06.913 NOTIFICATION rcu: oracle.sysman.assistants.rcu.Rcu::execute: Launching RCU.
    2009-12-22 16:46:06.916 NOTIFICATION rcu: oracle.sysman.assistants.rcu.Rcu::execute: Creating InteractiveRCUModel
    2009-12-22 16:46:07.876 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::<init>: Base URL : file:///u01/app/oracle/rcuHome/rcu/config/
    2009-12-22 16:46:07.876 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::<init>: ComponentInfo xml location : /u01/app/oracle/rcuHome/rcu/config/ComponentInfo.xml
    2009-12-22 16:46:07.876 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::<init>: Storage xml location : /u01/app/oracle/rcuHome/rcu/config/Storage.xml
    2009-12-22 16:46:07.876 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::<init>: DTD Validation : true
    2009-12-22 16:46:07.891 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.RCUCommandLineParser::process: Processing command line ....
    2009-12-22 16:46:39.363 NOTIFICATION rcu: oracle.sysman.assistants.common.dbutil.jdbc.JDBCEngine::connect: Connecting to database: user:system, role:Normal, connectString:(description=(address=(host=cicl-11g)(protocol=tcp)(port=1521))(connect_data=(service_name=DEV11G)(server=dedicated)))
    2009-12-22 16:46:40.515 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Executing Task: Initializing repository configuration metadata
    2009-12-22 16:46:40.515 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: Prereq taskId = INIT_META_DATA
    2009-12-22 16:46:40.704 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : AS_COMMON
    2009-12-22 16:46:40.707 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : MDS
    2009-12-22 16:46:40.713 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : MDS
    2009-12-22 16:46:40.714 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : MDS
    2009-12-22 16:46:40.716 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : IAU
    2009-12-22 16:46:40.720 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : ORAESS
    2009-12-22 16:46:40.721 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : IDM
    2009-12-22 16:46:40.721 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : OID
    2009-12-22 16:46:40.723 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : OIF
    2009-12-22 16:46:40.732 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : OWLCS
    2009-12-22 16:46:40.733 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : ORASDPXDMS
    2009-12-22 16:46:40.735 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : ORASDPSDS
    2009-12-22 16:46:40.759 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : ORASDPLS
    2009-12-22 16:46:40.760 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : SOA
    2009-12-22 16:46:40.761 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : SOAINFRA
    2009-12-22 16:46:40.762 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : SOAINFRA
    2009-12-22 16:46:40.762 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : SOAINFRA
    2009-12-22 16:46:40.763 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : BAM
    2009-12-22 16:46:40.766 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : ORASDPM
    2009-12-22 16:46:40.768 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : ORASDPM
    2009-12-22 16:46:40.769 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : ORASDPM
    2009-12-22 16:46:40.770 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : WEBCENTER_SUITE
    2009-12-22 16:46:40.771 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : WEBCENTER
    2009-12-22 16:46:40.771 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : WEBCENTER
    2009-12-22 16:46:40.772 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : WEBCENTER
    2009-12-22 16:46:40.774 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : PORTLET
    2009-12-22 16:46:40.776 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : PORTLET
    2009-12-22 16:46:40.777 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : PORTLET
    2009-12-22 16:46:40.778 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : CONTENTSERVER
    2009-12-22 16:46:40.778 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : CONTENTSERVER
    2009-12-22 16:46:40.779 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : CONTENTSERVER
    2009-12-22 16:46:40.783 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : DISCUSSIONS
    2009-12-22 16:46:40.784 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : DISCUSSIONS
    2009-12-22 16:46:40.785 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : DISCUSSIONS
    2009-12-22 16:46:40.786 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : DISCUSSIONS_CRAWLER
    2009-12-22 16:46:40.791 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : DISCUSSIONS_CRAWLER
    2009-12-22 16:46:40.794 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : WIKI
    2009-12-22 16:46:40.795 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : WIKI
    2009-12-22 16:46:40.795 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : WIKI
    2009-12-22 16:46:40.796 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : PORTAL_BI
    2009-12-22 16:46:40.797 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : PORTAL
    2009-12-22 16:46:40.800 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : DISCOVERER
    2009-12-22 16:46:40.821 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseXmlData: XML Document: /u01/app/oracle/rcuHome/rcu/config/ComponentInfo.xml is valid
    2009-12-22 16:46:40.835 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : MDS
    2009-12-22 16:46:40.843 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//mds/mds.xml is valid
    2009-12-22 16:46:40.852 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : IAU
    2009-12-22 16:46:40.857 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration/iau/iau.xml is valid
    2009-12-22 16:46:40.864 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : ORAESS
    2009-12-22 16:46:40.876 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//ess/ess.xml is valid
    2009-12-22 16:46:40.883 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : OID
    2009-12-22 16:46:40.886 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//oid/oid.xml is valid
    2009-12-22 16:46:40.891 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : OIF
    2009-12-22 16:46:40.898 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//oif/oif.xml is valid
    2009-12-22 16:46:40.904 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : ORASDPXDMS
    2009-12-22 16:46:40.907 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//commspresence/commspresence.xml is valid
    2009-12-22 16:46:40.915 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : ORASDPSDS
    2009-12-22 16:46:40.932 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//commssds/commssds.xml is valid
    2009-12-22 16:46:40.938 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : ORASDPLS
    2009-12-22 16:46:40.939 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//commsls/commsls.xml is valid
    2009-12-22 16:46:40.945 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : SOAINFRA
    2009-12-22 16:46:40.950 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//soainfra/soainfra.xml is valid
    2009-12-22 16:46:40.955 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : BAM
    2009-12-22 16:46:40.958 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//bam/bam.xml is valid
    2009-12-22 16:46:40.963 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : ORASDPM
    2009-12-22 16:46:40.975 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//sdpm/sdpm.xml is valid
    2009-12-22 16:46:40.981 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : WEBCENTER
    2009-12-22 16:46:40.991 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//webcenter/webcenter.xml is valid
    2009-12-22 16:46:40.998 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : PORTLET
    2009-12-22 16:46:41.006 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//portlet/portlet.xml is valid
    2009-12-22 16:46:41.011 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : CONTENTSERVER
    2009-12-22 16:46:41.021 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration/contentserver/contentserver.xml is valid
    2009-12-22 16:46:41.024 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : DISCUSSIONS
    2009-12-22 16:46:41.030 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//jive/jive.xml is valid
    2009-12-22 16:46:41.040 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : DISCUSSIONS_CRAWLER
    2009-12-22 16:46:41.048 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//jive-crawler/jive-crawler.xml is valid
    2009-12-22 16:46:41.052 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : WIKI
    2009-12-22 16:46:41.056 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//wiki/wiki.xml is valid
    2009-12-22 16:46:41.063 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : PORTAL
    2009-12-22 16:46:41.065 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration/portal/portal.xml is valid
    2009-12-22 16:46:41.070 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : DISCOVERER
    2009-12-22 16:46:41.073 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration/dc/discoverer.xml is valid
    2009-12-22 16:46:41.108 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseStorageData: XML Document: /u01/app/oracle/rcuHome/rcu/config/Storage.xml is valid
    2009-12-22 16:46:41.452 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Execution time for Initializing repository configuration metadata : 937 milliseconds
    2009-12-22 16:46:41.464 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Executing Task: Obtain properties of the specified database
    2009-12-22 16:46:41.464 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: Prereq taskId = PREREQ_QUERY_DATABASE
    2009-12-22 16:46:41.498 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Execution time for Obtain properties of the specified database : 34 milliseconds
    2009-12-22 16:46:41.514 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Executing Task: Check requirement for specified database
    2009-12-22 16:46:41.514 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: Prereq taskId = PREREQ_GLOBAL_CHECK
    2009-12-22 16:46:41.557 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Execution time for Check requirement for specified database : 43 milliseconds
    2009-12-22 16:46:41.572 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Executing Task: Execute pre create operations
    2009-12-22 16:46:41.573 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.CustomCompManager::getActionList: CustomCompManager.getActionList: CUSTOM_COMP_PRELOAD_SETUP
    2009-12-22 16:46:41.579 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.AbstractCompTask::execute: ValidIf result was false. Skipping Action: oracle.ias.version.SchemaVersionUtil:utilCreateRegistryAndCopyData
    2009-12-22 16:46:41.582 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.AbstractCompTask::execute: ValidIf result was false. Skipping Action: oracle.ias.version.SchemaVersionUtil:utilCreateRegistryTable
    2009-12-22 16:46:41.582 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Execution time for Execute pre create operations : 9 milliseconds
    2009-12-22 16:46:55.687 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Executing Task: Metadata Services
    2009-12-22 16:46:55.687 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: Prereq taskId = MDS
    2009-12-22 16:46:55.687 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: Starting component prereq check
    2009-12-22 16:46:55.722 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Execution time for Metadata Services : 35 milliseconds
    2009-12-22 16:46:55.727 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Executing Task: Audit Services
    2009-12-22 16:46:55.727 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: Prereq taskId = IAU
    2009-12-22 16:46:55.727 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: Starting component prereq check
    2009-12-22 16:46:55.761 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Execution time for Audit Services : 34 milliseconds
    2009-12-22 16:46:55.766 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Executing Task: Enterprise Scheduler Service
    2009-12-22 16:46:55.766 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: Prereq taskId = ORAESS
    2009-12-22 16:46:55.766 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: Starting component prereq check
    2009-12-22 16:46:55.773 ERROR rcu: oracle.sysman.assistants.rcu.backend.task.PrereqTask::execute: Prereq Evaluation Failed
    oracle.sysman.assistants.rcu.backend.validation.PrereqException: RCU-6083:Failed - Check prerequisites requirement for selected component:ORAESS
    Please refer to RCU log at /u01/app/oracle/logdir.2009-12-22_16-46/rcu.log for details.
         at oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator.executePrereqTask(PrereqEvaluator.java:642)
         at oracle.sysman.assistants.rcu.backend.task.PrereqTask.execute(PrereqTask.java:68)
         at oracle.sysman.assistants.rcu.backend.task.ActualTask.run(TaskRunner.java:303)
         at java.lang.Thread.run(Thread.java:619)
    2009-12-22 16:46:55.773 ERROR rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: RCU Operation Failed
    oracle.sysman.assistants.common.task.TaskExecutionException: RCU-6083:Failed - Check prerequisites requirement for selected component:ORAESS
    Please refer to RCU log at /u01/app/oracle/logdir.2009-12-22_16-46/rcu.log for details.
    Trying to connect as a non SYSDBA user. User should have SYSDBA privileges to successfully load the ESS schema.
         at oracle.sysman.assistants.rcu.backend.task.PrereqTask.execute(PrereqTask.java:76)
         at oracle.sysman.assistants.rcu.backend.task.ActualTask.run(TaskRunner.java:303)
         at java.lang.Thread.run(Thread.java:619)
    Edited by: yousufpaya on Dec 22, 2009 7:31 PM

    Hi yousuf;
    Please follow below and see its helpful for your issue:
    http://soadev.blogspot.com/2009_07_01_archive.html ( part:Error in Running Repository Creation Utility (RCU) While Using Oracle XE database )
    Also check:
    http://forums.tangosol.com/forums/thread.jspa?threadID=930952&tstart=60 (Joaanas post)
    Regard
    Helios

  • Error While Importing Process Flow in OWB Repository.

    Hi All,
    OWB Config Details is as follows:
    Oracle 9i Warehouse Builder Client: 9.2.0.2.8
    Oracle 9i Warehouse Builder Repository: 9.2.0.2.0
    Following Error Message is displayed when i tried to import process flow from one OWB Repositoty to another OWB Repository.
    Warning at line 23: MDL1312: Referenced logical location with name <PF_STG_INC_LOC> and UOID <F3940F1D5EB84985E0340003BA0AF737> not found for PROCESSMODULE <SALES_INC>. Logical location not set for this module.
    Warning at line 28: MDL1320: PROCESS PF_C_C_CALLS_INC in STG_INC.SALES_INC.SAL_INC cannot be imported because referenced STANDALONEPROCEDURE
    FLSTG.PROC_GET_ETL_DATA_DATE does not exist.
    Warning at line 28: MDL1320: PROCESS PF_STG_CALL_CENTER_CALLS_INC in FLSTG_INC.SALES_INC.SAL_INC cannot be imported because referenced STANDALONEPROCEDURE
    FL_TRG_FLSTG.PROC_UPDATE_RECO_CTL does not exist.
    Informational: MDL1134: COMMIT issued at end of import data file.

    Hello, all the errors you've been given are related to missing objects.
    You should re-create/import the location for you process flows before importing the process flows themselves.
    Also verify that you have imported the procedures FLSTG.PROC_GET_ETL_DATA_DATE and FL_TRG_FLSTG.PROC_UPDATE_RECO_CTL because you use them in your process flows so you need them: OWB refuses to import a process flows if some objects are missing because it would break some links.
    In general process flows should be imported where you have all the other objects in the repository because they are the final step and they reference many other objects.
    Hope this helps - Antonio

  • Error while cofigring OWB repository

    Hello,
    I have installed Oracle Database 11g R2(11.2.0.1) in my laptop(windows 7,64 bit). Installation was successful and SYSTEM, OWBSYS etc schemas are already unlocked.
    Now when I start to configure OWB through repository assistant, at the time of creation of OWB workspace, it's getting stuck.Hence, I killed the process and started all again.
    But this time, it's showing error:
    java.lang exception:Package body error:
    OWBSYS.WB_WORKSPACE.MANAGEMENT has errors
    Can anyone please  help me resolve this.
    Many Thanks..

    Hi,
    Cleanup the old repository installation and start afresh as per the steps mentioned below(connection should be with any DBA user):
    1.Drop the old workspace owner( if any).
    2.Clean the owbsys user using the clean_owbsys.sql  located in <OWB_HOME>\owb\UnifiedRepos
               where <OWB_HOME> is the oracle home for your OWB.
    3.Recreate the owbsys using the script cat_owb.sql
    4.Unlock the user owbsys and owbsys_audit
    5.Start the installation afresh.
    Note: The repository creation can be successful but the OWB 11.2.0.1 design client will not work on windows 64-bit platform (11.2.0.3 is the first version that is supported on windows64-bit platform
    Regards,
    Pnreddy

  • Error While Improting Process Flow in OWB Repository.

    Hi All,
    OWB Config Details is as follows:
    Oracle 9i Warehouse Builder Client: 9.2.0.2.8
    Oracle 9i Warehouse Builder Repository: 9.2.0.2.0
    Following Error Message is displayed when i tried to import process flow from one OWB Repositoty to another OWB Repository.
    Warning at line 23: MDL1312: Referenced logical location with name &lt;PF_STG_INC_LOC&gt; and UOID &lt;F3940F1D5EB84985E0340003BA0AF737&gt; not found for PROCESSMODULE &lt;SALES_INC&gt;. Logical location not set for this module.
    Warning at line 28: MDL1320: PROCESS PF_C_C_CALLS_INC in STG_INC.SALES_INC.SAL_INC cannot be imported because referenced STANDALONEPROCEDURE
    FLSTG.PROC_GET_ETL_DATA_DATE does not exist.
    Warning at line 28: MDL1320: PROCESS PF_STG_CALL_CENTER_CALLS_INC in FLSTG_INC.SALES_INC.SAL_INC cannot be imported because referenced STANDALONEPROCEDURE
    FL_TRG_FLSTG.PROC_UPDATE_RECO_CTL does not exist.
    Informational: MDL1134: COMMIT issued at end of import data file.

    Hello, all the errors you've been given are related to missing objects.
    You should re-create/import the location for you process flows before importing the process flows themselves.
    Also verify that you have imported the procedures FLSTG.PROC_GET_ETL_DATA_DATE and FL_TRG_FLSTG.PROC_UPDATE_RECO_CTL because you use them in your process flows so you need them: OWB refuses to import a process flows if some objects are missing because it would break some links.
    In general process flows should be imported where you have all the other objects in the repository because they are the final step and they reference many other objects.
    Hope this helps - Antonio

  • Cannot Create OWB Repository Owner

    Hello All,
    On windows XP pro, 32 bit, the following tasks were completed (clean system, 1.5 gig ram and dual core)
    - Installed 9.2.0.1 Server
    - Installed 9.2.0.6 Patch
    - Installed Oracle Worflow + and created workflow user
    - Installed OWB_10.2.0.1.win.zip
    All seemed to be fine until attempting to create the OWB repository owner using the Repository Assistant
    Problem 1)
    The Repository Assistant froze after being given the user details for the repository owner.
    I found a fix (read Hack) for this that I am including FYI. The issue relates to the view dba_kgllock which was force created against objects that do not exist. To solve this I used TOAD to find the script used to create the view, deleted the view and created an empty table with the same columns.
    This is a complete hackbut allowed OWB Repository Assistant. All then continued and was looking good until about 60% complete.
    Problem 2)
    At approx 60% installation fails with a socket read fail within java.
    Thats it, I've stopped dead now, going to continue installation attempts in the morning. If anybody out there can help I would be very greatful.

    This appears to be a locking issue and looking at our Support database it is resolved in 10gR1 and 10gR2 versions of the database but remains on 9i although a warning dialog should be shown. Even so the installation should continue and should be successful.
    Do you have AQ running? This sometimes causes this error to occur. I think in the 10gR1 documentation this locking issue was documented and it was supposed to be added to the 10gR2 doc (I need to check to this).
    To figure the lock from Repo Asst code, use the following:
    select distinct
    s.sid,
    s.serial#,
    s.username,
    x.kglnaobj as objectname
    from
    dba_kgllock l,
    v$session s,
    x$kgllk x
    where
    l.kgllktype = 'Pin' and
    s.saddr = l.kgllkuse and
    s.saddr = x.kgllkuse and
    x.kglnaobj like '%DBMS_LOCK%';
    If this returns rows, display the warning with a suggestion to connect to SQLPlus and issue the following statement (where SID, Serial are what came back from the query)
    ALTER SYSTEM KILL SESSION 'SID, Serial';
    e.g.
    ALTER SYSTEM KILL SESSION '13, 8'
    That might solve the problem.
    Hope this helps.
    Keith Laker
    Data Warehouse Solution Architect
    Oracle EMEA Consulting
    BI Blog: http://oraclebi.blogspot.com/
    DM Blog: http://oracledmt.blogspot.com/
    BI on Oracle: http://www.oracle.com/bi/
    BI on OTN: http://www.oracle.com/technology/products/bi/
    BI Beans http://www.oracle.com/technology/products/bib/index.html
    Discoverer: http://www.oracle.com/technology/products/discoverer/
    BI Samples: http://www.oracle.com/technology/products/bi/samples/

Maybe you are looking for