Installation of the repository creation utility

Hello

I downloaded BIPublisher_11.1.1.3_Desktop and you want to install it on my machine (windows 32-bit).

in the tutorial, it's sad that I have before installing BI Publisher to run the scripts of the utility of creating repository (RCU) in the Oracle 11 g database.

I have an Oracle 11 g XE installed on my machine in C:\oraclexe, and it is started.

I downloaded the ofm_rcu_win32_11.1.1.3.3_disk1_1of1 package and started it.

I have a problem on a step 2 - connection to the base. I get an error - invalid service name.

Where can I get the name of the Service, please!

Try XE service name

Generally, it is a database name. It was supposed to be specified during the installation of the database.
If it has not been changed, it should be set in your case.

Tags: Business Intelligence

Similar Questions

  • Download the repository creation utility

    Hi all


    As part of the installation of Oracle Fusion Middleware, I am unable to find the download of Oracle repository creation Utiliity.


    Could you guide me to the right link?


    Kind regards
    Barros has

    Scroll to the required additional software section
    http://www.Oracle.com/technetwork/middleware/BI-Enterprise-Edition/downloads/bus-intelligence-11g-165436.html

  • How to run the repository creation utility (11.1.1.3.3)

    Hi experts, I downloaded utility creation (11.1.1.3.3) at oracle.com repository as I was told to run it before installing Oracle Business Intelligence, v. 11.1.1.3.0, I already unzipped the UCR, my problem is I do not know where and what run.i I ask the name of the file to be executed, the location of this file because there are so many issues after having unpacked the downloaded file. Finally, how to run the file (for example by double-clicking). Thank you

    Visit this link,

    http://obiee101.blogspot.com/2010/08/obiee11g-installation-on-32-bits-XP-Pro.html

    He noted the location of the controls on the remote file, double click will start the process.

    Thank you
    Vino

  • Is "Repository creation utility" a mandatory for SOA Suite

    Hi all

    I am new to Oracle 11g Weblogic application server. I worked on the Oracle 10 g application server. I am very interested to BPEL and planning to learn BPEL and SOA concepts in.

    I have 11.1.1.0.1 Jdeveloper, Oracle Weblogic server 10.3.2, database Oracle 10.2.0.3 for windows vista installed on my laptop.

    Now, I downloaded SOA Suite 11.1.1.2.0 and JDeveloper SOA Composite editor. But in the list of additional software required for SOA Suite, we need to * "repository creation utility."

    Can someone give me the link for documentation of what is it and why is it necessary?

    I worked in BPEL in Oracle 10 g and there was no such additional deposit creation utility. I'm quite novice in this technology and planning only to learn that basic concepts of the BPEL (Basic is very widespread word here. I mean using adapters, working with the web services BPEL etc.).

    For this kind of basics and running SOA Suite is the repository creation utility, a mandatory requirement?
    If so, can I install utility of creating repository with my version of the database of * 10.2.0.3 * (because I read that the repository creation utility works with 10.2.0.4 or higher)?
    If not, how can I get the Group of hotfixes to upgrade my 10.2.0.4 Database 10.2.0.3.

    Thank you and best regards,
    Pavan.

    1--> Yes, it is mandatory to run 'Remote control' to install/upgrade using FMW/SOA Suite 11 g.
    2--> you don't need to install the regional coordination unit, it can be downloaded in zip file, and once you unpack this last, it can be run directly.
    3--> "What it is"--> to a higher level, that it's a bunch of scripts required to create storage space related to the SOA/BPEL processes. As you know that BPEL process are with States of the process and their States, etc. must be stored in a database.
    4--> even in Oracle 10g, there used repository, but it got installed by default and the tables created in the database of default olite.

    http://www.Oracle.com/technology/software/products/middleware/htdocs/111110_fmw.html

    Cheers!

  • Getting error when installing repository creation utility (RCU).

    Hello

    During the installation of the remote control, I was getting the Error Invalid Username/password on the database connection details screen when I give a Userid sys. on the database connection details screen, I tried to login with the user sys but failed so I used the user of the system, and it connects.
    Then on screen components, I was getting the error below.

    UCR-6083: impossible - check requirement prerequisites for the selected item: ORAESS
    Refer to the journal of the RCUS to /u01/app/oracle/logdir.2009-12-22_16-46/rcu.log for more details.
    Try to connect as a user not SYSDBA. User must have SYSDBA privileges to properly load the schema of the ESS.

    RCU - 6092:Component validation selection failed. Please refer to connect to /u01/app/oracle/logdir.2009-12-22_16-46/rcu.log for more details.

    I don't know why I am unable to connect with the sys user, I give the password. Now, I changed the password but still can't connect sys.
    Please see the link below.

    http://download.Oracle.com/docs/CD/E12839_01/ doc.1111 /e14259/rcu_screens.htm

    Please suggest something.

    -The log file error-

    2009-12-22 16:46:06.904 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: hostname: cicl - 11 g
    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: U.S.
    2009-12-22 16:46:06.912 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: the user's 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 : chemin de la bibliothèque Java : /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: launch RCU.
    2009-12-22 16:46:06.916 NOTIFICATION rcu: oracle.sysman.assistants.rcu.Rcu::execute: InteractiveRCUModel of creation
    2009-12-22 16:46:07.876 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager: < init >: basic 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 >: xml storage 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: the connection to the database: user: System, role: Normal, connectString: (description = (address = (host = cicl - 11 g)(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: execution of task: initialization of metadata repository configuration
    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 component analysis: MDS
    2009-12-22 16:46:40.713 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: MDS
    2009-12-22 16:46:40.714 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: MDS
    2009-12-22 16:46:40.716 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: 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 component analysis: IDM
    2009-12-22 16:46:40.721 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: OID
    2009-12-22 16:46:40.723 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: 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 component analysis: 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 component analysis: 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 component analysis: WEBCENTER
    2009-12-22 16:46:40.771 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: WEBCENTER
    2009-12-22 16:46:40.772 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: WEBCENTER
    2009-12-22 16:46:40.774 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: PORTLET
    2009-12-22 16:46:40.776 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: PORTLET
    2009-12-22 16:46:40.777 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: 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 component analysis: DISCUSSIONS
    2009-12-22 16:46:40.784 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: DISCUSSIONS
    2009-12-22 16:46:40.785 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: 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 component analysis: WIKI
    2009-12-22 16:46:40.795 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: WIKI
    2009-12-22 16:46:40.795 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: 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 component analysis: PORTAL
    2009-12-22 16:46:40.800 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: 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 analysis repository Config data 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 analysis repository Config data 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 analysis repository Config data 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 analysis repository Config data 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 analysis repository Config data 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 analysis repository Config data 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 analysis repository Config data 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 analysis repository Config data 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 analysis repository Config data 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 analysis repository Config data 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 analysis repository Config data 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 analysis repository Config data 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 analysis repository Config data 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 analysis repository Config data 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 analysis repository Config data 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 analysis repository Config data 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 analysis repository Config data 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 analysis repository Config data 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 analysis repository Config data 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: turnaround time for initialization of configuration metadata repository: 937 milliseconds
    2009-12-22 16:46:41.464 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: execution of task: get the 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: lead time to get the properties of the specified database: 34 milliseconds
    2009-12-22 16:46:41.514 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: execution of task: obligation of verification for the 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: lead time for the requirement of verification for the specified database: 43 milliseconds
    2009-12-22 16:46:41.572 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: task execution: run before 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: ValidationRule result was false. Jump action: oracle.ias.version.SchemaVersionUtil:utilCreateRegistryAndCopyData
    2009-12-22 16:46:41.582 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.AbstractCompTask::execute: ValidationRule result was false. Jump action: oracle.ias.version.SchemaVersionUtil:utilCreateRegistryTable
    2009-12-22 16:46:41.582 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: lead time to run before the operations of creation: 9 milliseconds
    2009-12-22 16:46:55.687 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: execution of 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: from prereq check component
    2009-12-22 16:46:55.722 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: turnaround time for metadata Services: 35 milliseconds
    2009-12-22 16:46:55.727 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: execution of task: Services of Audit
    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: from prereq check component
    2009-12-22 16:46:55.761 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: lead time for the Services of Audit: 34 milliseconds
    2009-12-22 16:46:55.766 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: tasks: business 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: from prereq check component
    2009-12-22 16:46:55.773 rcu ERROR: oracle.sysman.assistants.rcu.backend.task.PrereqTask::execute: Prereq evaluation failed
    oracle.sysman.assistants.rcu.backend.validation.PrereqException: UCR-6083: impossible - check requirement prerequisites for the selected item: ORAESS
    Refer to the journal of the RCUS to /u01/app/oracle/logdir.2009-12-22_16-46/rcu.log for more 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 rcu ERROR: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: UCR failed
    oracle.sysman.assistants.common.task.TaskExecutionException: UCR-6083: impossible - check requirement prerequisites for the selected item: ORAESS
    Refer to the journal of the RCUS to /u01/app/oracle/logdir.2009-12-22_16-46/rcu.log for more details.
    Try to connect as a user not SYSDBA. User must have SYSDBA privileges to properly load the schema of the ESS.

    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)

    Published by: yousufpaya on December 22, 2009 19:31

    Hi yousuf;

    Please follow below and see its useful for your question:
    http://soadev.blogspot.com/2009_07_01_archive.html ( part: error in the running database repository creation Utility (RCU) using Oracle XE )

    Check also:
    http://forums.tangosol.com/forums/thread.jspa?threadID=930952&TSTART=60 (post Joaanas)

    Respect of
    HELIOS

  • ORA-1450 during the installation of the repository

    I tried to use the MISP utility on a 10.2.0.4.4 database on Red Hat Enterprise Linux Server release 5.7 (Tikanga) 2.6.18 274.7.1.el5 (64-bit). I got the below error when you try to create the repository. Anyone else has come across this or have no work around for it? The plan is to update this database to 11.2.0.3 on new hardware. It will go to AL32UTF8 WE8ISO8859P1 in the process.
    Thank you
    Brian


    29.13:56:32:529; P035; S; 10042 encountered an error during the installation of the repository: error occurred during batch processing: ORA-01450: maximum (3118) key length exceeded

    29.13:56:32:531; P035; S; 10008 cannot install the repository.
    29.13:56:33:211; P035; I; 10016 uninstalled repository.

    The MISP repository requires a tablespace with block size of 8 k or higher. Please, try the following for MISP 1.1:

    (1) create a tablespace with block size 8 k
    (2) change the default tablespace for the user of the SYSTEM to use this new space of tables
    (3) install the MISP repository on a new basis
    4) reset the user of the SYSTEM to use the original table space

  • Need 11g for AIX repository creation utility.

    Hello

    Are there "Repository creation utility" download available for AIX?

    As I can't find it on OTN download. Its only available for Linux and Windows. I install OID 11 g on AIX that requires a deposit, but there is no available for AIX repository creation utility. Need advice on this.

    Thank you and best regards,
    Noman

    Hi Noman,
    RCU is available for Linux & Windows. Download the RCU utility to run all of the windows/linux box, from there, specify the db details it & create the respective schemas.

    Regional coordinating unit will be not available for AIX and other platforms. You must use UCR in both Linux/Windows platforms only.

  • Document of the repository creation OBIEE 11 G

    Hi all

    Could provide OBIEE document creating the repository of practice with 11 G screenshots (HS or Samplesales repository).
    Exmple obiee 10g SH creation document from the repository.

    Thank you
    Raja

    Hello

    Refer,

    http://www.Oracle.com/technetwork/middleware/BI-Enterprise-Edition/tutorials/obiee11g-453435.html

    Thank you
    Deva

  • Online recovery process is frozen to the installation of the Flash Card Utility

    Following an attack of serious virus a month ago, my computer ended up with at least a corrupted user file. Efforts to correct without great expense may have hurt rather than helped - it is difficult to know what does what.

    Until two days ago, I was faced with three distinct start-up, two partial process and a normal (usually first start in the morning). One of the partial featured no connection. The other managed to connect, but not with the document data.

    After a normal boot, if for some reason, the computer fell asleep or has been disabled, it has not started normally for the rest of the day, except on rare occasions, seemingly random.

    Two days ago Windows began to send messages that Windows 7 has to be reinstalled. Once it does automatically search and correction process. Subsequently, the message became, you may be victim of illegitimate (or Word like this) Windows software.

    On a forum this morning, I came across the steps in a process of recovery Toshiba DIY (no cd or usb) and has begun. Everything went along well for about half an hour, going from one thing to another, sometimes restart. But the process now seems to be frozen. For about 40 minutes, the installation was on Toshiba Flash Card Utility - 10/80.

    I followed the direction does not stop somehow. I really don't think it's still going to complete recovery successfully.

    It is I think that all I could do just end the installation and I'll be back where I was before, but without anything left on my laptop.

    I called Toshiba Support (I'm out of warranty) and the person to whom I spoke and his supervisor, do not seem to have any idea of what could be done, but knew I had to talk to a person "out of warranty". I have to pay their fees, but the only one I think that options are available to me are 1) do nothing and see if the recovery work always or 2 (repeat the recovery.

    Can anyone offer an alternative to $200 at Best Buy?
    .

    There is a mistake in the background which you can cancel and continue the recovery.

    Press ALT + TAB to display the error dialog box, close it.

  • Error during installation of the repository of BPA on LINUX

    based on DOC-ID 554528.1

    I did following steps:
    -installed Database 10g on Linux Enterprise.
    -created a new database with UTF-8 character set
    -created two tablespaces ARISDATA, ARISINDEX (2GB)
    -runs the aris70.sh script
    -created the new schema

    Installation of BPA on LINUX repository
    -If I run install_bpr10.1.3.4271679.sh following error occurs:

    tail: cannont open "+ 182' for reading: no such file or directory".
    3158 records + 0 in
    records of 3158 + 0 out
    3158 (3.2 KB) copied, 0,115841 seconds, 27.3 kB/s

    gzip: stdin: not in gzip format
    . / install_bpr10.1.3.4271679.sh: line 173: /tmp/_install.3889/configure.sh: no such directory

    Published by: user10191651 on May 18, 2009 04:31

    RedHat 5.X / OEL 5.X is not certified.

    Please check the link below certification.
    http://www.Oracle.com/technology/products/BPA/index.html
    http://www.Oracle.com/technology/products/BPA/bpa_certification%20Matrix.xls

    Note: RHEL 4.0 (64) is the Certified version.

    See you soon,.
    Vish

  • How to upgrade the repository Oracle Designer 9.0.4 to 10.1.2.5 mi

    I need to find a way to upgrade my Oracle Designer Repositroy 9.0.4 to 10.1.2.5?, is there a procedure to upgrade my Version of Oracle Designer? I hope you can help me.

    The version of the repository is very closely related to the version of the client. First, back up your repository - you want to be able to restore if something goes wrong. Upgrade your client to Designer by installing 10.1.2.5 according to the instructions in the installation guide. Do not forget that the designer belongs to Developer Suite, and you must install the entire Suite. All the workstations that will use this repository will need to be upgraded. Then start the repository Administration Utility (RAU), recording as the repository owner. Run the utility to check the requirements, to ensure that the owner has all the necessary privileges. If you have a valid 9.0.4, you probably don't need any privilege that you have not already, but it never hurts to check. Since the repository String corresponds to that client, the button 'Upgrade' in RAU will not be gray. Press "Upgrade" to upgrade the repository. There are choices to make here, especially what storage spaces to use for various components of the repository. Usually, you want to make the same selections you made when you first installed the repository, but if you have any questions about this, ask your DBA. Or you can ask a more specific question here. The upgrade will take a little time, and you want to have no user use it until the upgrade is complete. Once the repository has been upgraded, you will not be able to use the former client against her.

  • HP OfficeJet Pro 8610: Impossible to activate the scan of the computer, complete the installation of the utility

    I'm not able to activate the analysis of my desktop computer or my laptop. I pedaled power the router, printer and computers, ran disk utility and repair permissions, I uninstalled the printer and reinstalled. I received a message that the installation of the HP Officejet Pro 8610 has been completed successfully, but when he goes then HP utility-Setup-HP Officejet Pro 8610, happens to alerts from HP and I get the error message: "a critical error has occurred. Please restart the application, and then try again ' and I am unable to continue. Download and open HP Easy Start are successful but he opens the HP utility at the end and I get the same message once it arrives to alerts from HP.

    Opening to the high HP utility-HP Officejet Pro 8610 and clicking on scan settings, Scan of the computer initially appears without the box checked to activate this function and the error message: "the computer Scan is disabled. You can always start the scanning of your computer software analysis - for example, HP scanning "." Click on the button to activate the Scan of the computer generates this error message: "error of Communication. Unable to communicate with the device. Check the cables and the connection parameters. If the problem persists, try restarting your computer and the HP device "."

    In the window of the printer, press Scan and the Scan of the computer selection produces the error message: "not found computer. Scanning software HP is required for this feature. If installed, open the HP utility and under settings of scanning, select scan to computer and enable "."

    I tried everything suggested, and what I found online to try.  I'm missing something or not doing something correctly?

    Thanks for any help!

    Hi @3star8,.

    Welcome to the Forums of HP Support! I read your post and see that you are unable to activate the computer option via the software scan. I would like to help you today. If this helps you to find a solution, please click on the button "Accept as Solution" down below in this message. If you want to say thanks for my effort to help, click on the 'Thumbs Up' to give me a Kudos.

    I think that the procedure described in this post, will help solve this problem. Here is the link: Re: impossible to activate the Scan.

    This is the URL of your drivers, e-all-in-one-HP Officejet Pro printer 8610 series full feature software and drivers.

    Please let me know the result and if there is anything else I can help you. Thank you.

  • Use the host update utility or install ESXi4 Installable Update 2?

    I have 3 ESXi 4.0 host and you want to upgrade to 4.0 Update 2 and never really used the host update utility, but I doubt if Host Update Utility allows some dirt or something.

    I've read in a book but said nothing, while it records the settings of network, security and storage.

    What could be better? Use the host update utility or install ESXi4 Installable Update 2?

    Kind regards!

    If you have found this information useful, please consider awarding points to 'Correct' or 'Useful'*.

    Host update utility is the safest way to do it - and you will save the local VMFS more your configuration.

    If you go directly to the host with the installation CD, your configuration will not be saved, just the VMFS (that with ESXi). In addition, is a way of failure to take in charge of the upgrade.

    Dirty? With ESXi, I really doubt...

    Marcelo Soares

    VMWare Certified Professional 310/410

    Master virtualization technology

    Globant Argentina

    Review the allocation of points for "useful" or "right" answers.

  • Error 25003. Installation failed to create the repository of the vCenter server.

    Hello

    I try to install vCenter Server 4.0. When the Installer tries to Creator repository an error pops up:

    Error 25003. Installation failed to create the repository of the vCenter server.

    I click OK and the installation of double-dipping.

    The last records in the Setup log are:

    Found "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\vpxd.exe".

    Run as user logon administrator

    Found "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\vpxd.exe".

    3221225477 returned by process

    ERROR: Failed to create the repository of VirtualCenter

    Displaying the Error 25003

    Description of our environment:

    • VCenter service runs under the SYSTEM account.

    • Autonomous mode eval version.

    • All ports are standard.

    • Using SQL2005 Express on the installation media.

    • I downloaded the trial version.

    • The server is VM on ESX with SP2 of Win 2003 x 86 CZE Standard Edition

    • The server is not in AD

    • Space 7.5 GB free disk

    I also tried to create the manully database but no luck.

    Thanks for the tips.

    After Installing Win XP SP3 ENG everything works OK... If the problem was really in the language version of the operating system...

  • SEVERE: Error creating the repository

    Ugh, help, stayed in it for hours! I messed up my oracle dbconsole, and now service dbconsole itself disappeared! (I checked services.msc on my windows xp pro) I'm on oracle 11 g 2

    So I gave up and recreate repo em but got the error msg ff:

    C:\Documents and Settings\abigail > emca-rest create

    EMCA STARTED on 11 October 2013 05:17:51

    Configuration MS Assistant, Production of the Version 11.2.0.0.2

    Copyright (c) 2003, 2005, Oracle.  All rights reserved.

    Enter the following information:

    SID of the database: orcl

    Listener port number: 1521

    User SYS password:

    SYSMAN user password:

    Do you want to continue? [yes (Y) (N) /no]: y

    11 October 2013 05:18:08 oracle.sysman.emcp.util.EMCALogManager addLogFileInterna

    l

    WARNING: Adding file E:\app\abigail\cfgtoollogs\emca\SP2-0640 journal: not connected

    \emca_2013_10_11_05_17_51.log failed. Messages will not be saved in this file.

    11 October 2013 05:18:08 oracle.sysman.emcp.EMConfig perform

    INFO: This operation is currently logged in E:\app\abigail\cfgtoollogs\emca\SP2-0640

    : Not connected\emca_2013_10_11_05_17_51.log.

    11 October 2013 05:18:08 oracle.sysman.emcp.EMReposConfig createRepository

    INFO: Creation of the EM repository (this may take a while)...

    05:18:08 oracle.sysman.emcp.EMReposConfig rely on 11 October 2013

    SEVERE: Error creating the repository

    05:18:08 oracle.sysman.emcp.EMReposConfig rely on 11 October 2013

    NEWS: Check the log to E:\app\abigail\cfgtoollogs\emca\SP2-0640 file: no con

    nected\emca_repos_create_ < date > .log for more details.

    11 October 2013 05:18:08 oracle.sysman.emcp.EMConfig perform

    SEVERE: Error creating the repository

    Check the log to E:\app\abigail\cfgtoollogs\emca\SP2-0640 file: not connected

    \emca_2013_10_11_05_17_51.log for more details.

    Unable to complete the configuration. Check the log to E:\app\abigail\cf file

    gtoollogs\emca\SP2-0640: not connected\emca_2013_10_11_05_17_51.log for more det

    ails.

    My Log file

    CONFIG: queue E:\app\abigail\cfgtoollogs\emca\orcl\emca_repos_create_2013_10_11_05_13_56.log

    11 October 2013 05:13:56 oracle.sysman.emcp.EMReposConfig createRepository

    INFO: Creation of the EM repository (this may take a while)...

    11 October 2013 05:13:56 oracle.sysman.emcp.EMReposConfig createRepository

    CONFIG: ORA-20001: SYSMAN already exists...

    ORA-06512: at line 17 level

    oracle.sysman.assistants.util.sqlEngine.SQLFatalErrorException: ORA-20001: SYSMAN already exists...

    ORA-06512: at line 17 level

    at oracle.sysman.assistants.util.sqlEngine.SQLEngine.executeImpl(SQLEngine.java:1655)

    at oracle.sysman.assistants.util.sqlEngine.SQLEngine.executeScript(SQLEngine.java:1005)

    at oracle.sysman.assistants.util.sqlEngine.SQLPlusEngine.executeScript(SQLPlusEngine.java:339)

    at oracle.sysman.assistants.util.sqlEngine.SQLPlusEngine.executeScript(SQLPlusEngine.java:380)

    at oracle.sysman.emcp.EMReposConfig.createRepository(EMReposConfig.java:511)

    at oracle.sysman.emcp.EMReposConfig.invoke(EMReposConfig.java:229)

    at oracle.sysman.emcp.EMReposConfig.invoke(EMReposConfig.java:158)

    at oracle.sysman.emcp.EMConfig.perform(EMConfig.java:253)

    at oracle.sysman.emcp.EMConfigAssistant.invokeEMCA(EMConfigAssistant.java:590)

    at oracle.sysman.emcp.EMConfigAssistant.performConfiguration(EMConfigAssistant.java:1453)

    at oracle.sysman.emcp.EMConfigAssistant.statusMain(EMConfigAssistant.java:574)

    at oracle.sysman.emcp.EMConfigAssistant.main(EMConfigAssistant.java:522)

    05:13:56 oracle.sysman.emcp.EMReposConfig rely on 11 October 2013

    SEVERE: Error creating the repository

    05:13:56 oracle.sysman.emcp.EMReposConfig rely on 11 October 2013

    NEWS: Check the log to E:\app\abigail\cfgtoollogs\emca\orcl\emca_repos_create_ file < date > .log for more details.

    11 October 2013 05:13:56 oracle.sysman.emcp.EMConfig perform

    SEVERE: Error creating the repository

    See the log file at E:\app\abigail\cfgtoollogs\emca\orcl\emca_2013_10_11_05_13_31.log for more details.

    11 October 2013 05:13:56 oracle.sysman.emcp.EMConfig perform

    CONFIG: Stack Trace:

    oracle.sysman.emcp.exception.EMConfigException: error creating the repository

    at oracle.sysman.emcp.EMReposConfig.invoke(EMReposConfig.java:241)

    at oracle.sysman.emcp.EMReposConfig.invoke(EMReposConfig.java:158)

    at oracle.sysman.emcp.EMConfig.perform(EMConfig.java:253)

    at oracle.sysman.emcp.EMConfigAssistant.invokeEMCA(EMConfigAssistant.java:590)

    at oracle.sysman.emcp.EMConfigAssistant.performConfiguration(EMConfigAssistant.java:1453)

    at oracle.sysman.emcp.EMConfigAssistant.statusMain(EMConfigAssistant.java:574)

    at oracle.sysman.emcp.EMConfigAssistant.main(EMConfigAssistant.java:522)

    11 October 2013 05:13:56 oracle.sysman.emcp.EMConfig restoreOuiLoc

    CONFIG: Restoration of oracle.installer.oui_loc to E:\app\abigail\product\11.2.0\dbhome_1\oui

    ALTER YOUR_TEMPORARY_TABLESAPCE add tempfile XXXXX reuse;

Maybe you are looking for