Error preparing metadata repository

Hi Experts,
I'm getting this error when trying to install the XL Reporter. We have SBO2005 SP01 PL51. I've tried the suggestion posted here in the forum regarding XL Reporter installation error but to no avail.
Here's a screenshot of the error.
http://www.imagecross.com/11/image-hosting-view-39.php?id=4021SP32-20100629-130718.jpg
Please help. Thank you.
Best Regards.

Hi,
You may check these threads:
ADD-ON XL Reporter: Error installing XL Reporter in various PCs
XL Reporter Install - Can't delete [ServerName]/IXMetaSBOOEM
Thanks,
Gordon

Similar Messages

Red error of a web template in Metadata Repository in TEST system

This red error only occurs on our test system (maybe related to transport). RSA1->Goto Metadata Repository page->Double Local objects under Activated objects in the middle frame -> Double click Web Template Name in the right frame, then can see two same lines of red errors (see below in between two dashed lines):
Object 'our_web_template_name' (our_web_template_name) of type 'Web Template Name' is not available in version 'A'
Message no. RSO252
Diagnosis
You wanted to generate an object with the name 'our_web_template_name' (in transport request our_web_template_name) of type 'Web Template Name' (TLOGO). This is, however, not available in the BW Repository database. It does not exist in the requested version A. If the version is 'D' then it is possible that an error arose during the delivery or installation. If the version is 'A' then the Object was either not created or not activated.
System response
The object was not taken into account in the next stage of processing.
What could cause the above red error in Metadata Repository how to correct it?
Thanks

For these requests can you check if they contained objects like:
BW: LOIO Class Web Templates
BW: PHIO Class Web Templates
See, even if the transport for a web template does not contain these, it is imported fine, but the web template will not function in the target system. This happens quite often and you need to make sure that the above objects are also included in the request.
Hope this helps...

Error in Installing SSO Metadata Repository Creation Assistant (10.1.4.3.1)

I am trying to Install Portal Forms Reports 11, so I had to Install all prerequisites
My Machine Specifications:-
1- Oracle Enterprise Linux 5.5 x86-64
2- DB 11g R2
3- WebLogic 10.3.3 (X64)
4- Oracle Identity Management 11.1.1.2.0
I was executed the inspre11.pl with -op1
than I was trying to Install SSO Metadata Repository Creation Assistant (10.1.4.3.1)
in the last step (Step 7 - Loading Repository)
http://lh3.ggpht.com/_bMH90GEkTL4/SwW1jlNHzFI/AAAAAAAABjE/ZZm55usPKu0/s1600-h/clip_image054%5B3%5D.jpg
I encountered this error :-
ERROR - Unable to connect to the database. See the log file for details. Check that you have provided the proper service name for the database, that the database is running, the database connection information is valid, and that the database is set up for password file authentication. For more information, click the Help button.:ORA-06550: line 1, column 7:
PLS-00201: identifier 'DBMS_IAS_VERSION.SET_COMPONENT_LOADING' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
what can I do ? my Database is start up and the connection is OK !!!!!!!!!!!
I followed the oracle documentation:-
Installation Guide for Oracle Identity Management 11g Release 1 (11.1.1) E12002-02 October 2009
now we are going to 2011 !!!!!!!!!!!!!!!!!!!
Is there another newer Installation guide from oracle?
thank you

Good question, rozester.
I encountered this problem also, while trying to install the SSO MRCA 10.1.4.3.1 on 64-bit RHEL5 (though it's at version 5.7 but I'm positive that won't make any difference to the result).
This may or may not match your situation, but when I looked in the log file $ORACLE_HOME/assistants/repca/log/repca_<datestamp>.log, I saw what was probably the reason behind the error:
<$ORACLE_HOME>/bin/sqlplus: error while loading shared libraries: libclntsh.so.9.0: cannot open shared object file: No such file or directory
I think I remember seeing that the link operation during installation had failed, but I hoped it would be OK. And it possibly would have been, if I'd remembered to specify the destination database Oracle home rather than the SSO MRCA Oracle home when prompted (on the page where it asks for database home and log file path). Perhaps then it would have used the sqlplus binary from the database oracle home, and since that one definitely works, it might have worked. But before I thought of that, I did a workaround; I installed the SSO MRCA on a 32-bit RHEL5 box (using the same directory paths) and copied the shared library files to the 64-bit box's shared library directory via scp as follows:
cd $ORACLE_HOME/lib; scp -pr * oracle@rhel64box:$PWD/
When I re-ran $ORACLE_HOME/runRepca, it then worked without error. Another thing I could have tried is just running runRepca on the 32-bit RHEL5 box, and that probably would have worked too, but it probably would have been a lot slower compared to running it locally on the destination server; it's takes quite a while as it is.
Hope this helps. I'm sure it'll help me if next time I do this I forget what I did before and go searching again ;-)

BI Metadata Repository Configuration Error

Hello gurus.
Maybe somebody can tell how to solve this problem.
When try to create BI Metadata Repository (see note 1049784) an error received:
Configuration Error: Missing attribute: cacheid_lock, configuration node = component-config, location = config://local/cm/repository_managers/bw_metadata
The same error received on BI Document Repository activation.
So, where could find this cacheid_lock attribute?
EP7 SP15
Thanks.

SPS 16 solved this problem.
Edited by: Gunars Blumbahs on Jul 26, 2008 2:22 PM

Errors running MRUA for Metadata Repository Upgrade to version 10.1.2.0.2

Hi,
I am encountering the following errors trying to run the MRUA for our Metadata Repository Upgrade on an AIX 5.3 box:
<mrua_runs> ../mrua/mrua.sh -oracle_home /u01/oracle/product/9.2.0.8 -oid_host ourhost.domain.com -oid_ssl_port 3130
Executing mrua.pl
Running on UNIX
OracleAS Metadata Repository Upgrade Assistant 10.1.4.0.1
Enter the password for SYS: <syspw>
Enter the password for cn=orcladmin: <pwd>
Exception in thread "main" java.lang.NoClassDefFoundError: oracle/sysman/oii/oiio/oiiol/OiiolTextLogger
at oracle.ias.repqueries.RepositoryQueries.formatGlobalDBName(RepositoryQueries.java:603)
at oracle.ias.mrua.RepQueries.getDBInfo(RepQueries.java:180)
at oracle.ias.mrua.Util.getTheDBInfo(Util.java:50)
at oracle.ias.mrua.MRUA.getInfoFromOID(MRUA.java:690)
at oracle.ias.mrua.MRUA.driver(MRUA.java:297)
at oracle.ias.mrua.MRUA.main(MRUA.java:193)
MRUA detected an error at /mnt/MRUA/mrua/mrua.pl line 237.
<mrua_runs>
Before running the MRUA for the Metadata Repository:
1. I have just recently completed a Middle Tier and Identity Mangement upgrade to 10.1.2.0.2 from version 9.0.4.1.
2. I was able to successfully run the MRUA upgrade script for upgrading our Portal Repository (customer database).
Our Metadata Repository database is at version 9.2.0.8. Has anyone seen these errors or had this problem?
The MRUA CD that I have is labelled "Oracle Metadata Repository Upgrade Assistant and Utilities 10g (10.1.2.0.2) for AIX based systems".
But in the errors I see "OracleAS Metadata Repository Upgrade Assistant 10.1.4.0.1". Is something wrong there? Should it say 10.1.2.0.2?
Any help would be greatly appreciated.
Thanks.
CV
Hi,
I have downloaded the 10.1.2.0.2 version of the MRUA and tried the upgrade again. This time I see the following errors:
Executing mrua.pl
Running on UNIX
OracleAS Metadata Repository Upgrade Assistant 10.1.2.0.2
Enter the password for SYS: <syspwd>
Enter the password for cn=orcladmin: <pwd>
Exception in thread "main" java.lang.NoClassDefFoundError: oracle/sysman/oii/oiio/oiiol/OiiolTextLogger
at oracle.ias.repqueries.RepositoryQueries.formatGlobalDBName(RepositoryQueries.java:603)
at oracle.ias.mrua.RepQueries.getDBInfo(RepQueries.java:180)
at oracle.ias.mrua.Util.getTheDBInfo(Util.java:50)
at oracle.ias.mrua.MRUA.getInfoFromOID(MRUA.java:784)
at oracle.ias.mrua.MRUA.driver(MRUA.java:290)
at oracle.ias.mrua.MRUA.main(MRUA.java:186)
MRUA detected an error at /mnt/MRUA_downloaded/ohome/mrua/mrua.pl line 239.
Thanks.
CV
Edited by: CV on Jul 28, 2009 1:37 PM

Hi,
Found out from Oracle that the "oracle/sysman/oii/oiio/oiiol/OiiolTextLogger" class is in the $ORACLE_HOME/oui/jlib/OraInstaller.jar file and as per their suggestion added the jar file to the $classpath list of jar files in the mrua.pl script. I tried running the MRUA again, and ran into the following errors:
Exception in thread "main" java.lang.NullPointerException
at oracle.ias.mrua.MRUA.formatHostPortSid(MRUA.java:1449)
at oracle.ias.mrua.MRUA.getInfoFromOID(MRUA.java:794)
at oracle.ias.mrua.MRUA.driver(MRUA.java:290)
at oracle.ias.mrua.MRUA.main(MRUA.java:186)
MRUA detected an error at /u01/oracle/mrua_runs/MRUA_downloaded/ohome/mrua/mrua.pl line 243.
I am still troubleshooting. So if you have any ideas please let me know.
Thanks.
CV

Error: Cannot retrieve repository metadata (repomd.xml) for repository: ol6_UEK_latest. Please verify its path and try again

i am trying to executing command
"yum update"
and i am facing error during this
[Errno 14] PYCURL ERROR 7 - "couldn't connect to host"
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: ol6_UEK_latest. Please verify its path and try again

here i found the "ol6_UEK_latest" in public-yumo.l6.repo.
and here is URL corresponding to this:
name=Latest Unbreakable Enterprise Kernel for Oracle Linux $releasever ($basearch)
baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL6/UEK/latest/$basearch/
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-oracle
gpgcheck=1
enabled=1
plz help me is something wrong with URL or what i do ?

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

Metadata Repository Creation Assistant fails with ORA-01119


Hi All,
My DB version is 10.1.0.2 and I've upgraded the same to
10.1.0.4.2
In order to install B2B, I started off by installing the
Metadata Repository Creation Assistant.
After the initial steps, I got the following message:
<h5>
OracleAS RepCA was not able to find the Oracle Text Supplied
Knowledge Base in the database specified. </h5>
<h5>If you are planning to use this repository for installing
OracleAS Portal, you have to install Oracle Text Supplied Knowledge Base.
Oracle Text Supplied Knowledge Base can be installed in the database using
Oracle Database 10g Companion CD.</h5>
<h5>
If you are not planning to use this repository for
installing OracleAS Portal, you may continue further. Continue? Yes/No?</h5>
I continued with "Yes" and I chose the storage option as
"Regular or Cluster File system". In the next step -<strong>Specify Tablespace
information</strong>, I chose to install it in the C:\ , where there was approx 18GB
of free space. Yet, I encountered the following error:
<h5>
Unable to create tablespace. Please see the OracleAS RepCA
log file for more details.</h5>
<h5>ORA-01119 error in creating database file 'string'</h5>
<h5>Cause: Insufficient space on device or invalid database file
path.</h5>
<h5>Action:</h5>
<h5>a) Verify the database file path specified.</h5>
<h5>b) Decrease the size of the requested file or allocate a
file on another device with more available space. If a file size was not
specified in the statement, then specify a file size smaller than the available
space on the device.</h5>I have verified the database file path. I also tried
decreasing the size. I further tried using another directory where there was
11GB of free space. It still didn't work.
Please HELP!
-Suhas.

Hi Suhas,
Can you please do the following?
1. Please try pointing to C:\b2b.dbf file during installation and see if the installation goes fine or not.
Regards
Vipin R.S

Grapbical Display of Metadata repository in SAP BW 7.31

Hi,
I am working on SAP BW 7.31 and couldnt find Graphical display of BI Content in Meta data repsository,
We have updraded to the Support pack level 04 and now I could see object details tab but when I click on it its shows
Service cannot be reached
What has happened?
URL call was terminated because the corresponding service is not available.
Note
The termination occurred in system with error code 403 and for the reason Forbidden.
What can I do?Please select a valid URL.
HTTP 403 - Forbidden
Your SAP Internet Communication Framework Team
In general, object details shows network display of data flows? or is there anything I am missing apart from ICF.
Please let me know how this can be resloved...
Thanks in advance

Hello,
As of 7.30 the BW Metadata Repository has been designed as a WebDynpro Application. It can also run as an imbedded process in the Analytic Workbench (RSA1). Due to the nature of this technology
a separate login to the WebAS is needed to establish a Web-Session on the local WebAS. However if Single Sign On for the target system is activated the WebAS may be customized to use it as well. In this case you would see no login screen when calling the BW Metadata Repository. Please also note that also all relevant ICF-Services for BW must be active (i.e. all Web Document services) to be able to use the repository normally. Please find here some useful links to relevant ICF and ICM
documentation which might help you to properly set up your system:
http://help.sap.com/saphelp_nw73/helpdata/en/48/7f28a10fa44cdbe10000000a42189d/frameset.htm
http://help.sap.com/saphelp_nw73/helpdata/en/48/3ae05299c172d0e10000000a42189c/frameset.htm
Regards,
Michael

Metadata Repository search doesn't work NW 2004

Hi all,
After system patching Metadata Repository search stoped working, when I start search short dump occurs
"Function parameter "PTEXT" is unknown.
Error in ABAP application program.
The current ABAP program "CL_RSO_REPOSITORY=============CP" had to be
terminated because one of the statements could not be executed.
This is probably due to an error in the ABAP program.
Function module "SUSR_INTERFACE_PROF" was called
with the parameter "PTEXT".
This parameter is not defined."
I tried to find SAP-notes, but was able to find about NW 2004s
NW 2004, Basis 6-40, BW 3.5, SP BW21, SP Basis21
Any help will be appreciated
Thanks in advance,
Elena

Hi Susanne,
unfortunately NO repository is indexed by default so therefore you can not find Room Content before you create an index with the relevant information.
You must create yourself a new index of the repository where Room Content is stored. In EP6 SP2 Patch 5 and higher as well as NW'04 this should be /room_extensions. So add this repository as the Data Source of the index.
After indexing you should be able to perform search of the room content.
Hope this helps,
Robert

In the metadata repository, display the object detail links don't work

We've upgraded to 7.3 and when we lick on display the object details links we get the following message. I've looked in SICF and everything looks active and is set up
Service cannot be reached
What has happened?
call was terminated because the corresponding service is not available.

HI LMM
I have also same Problem . I thing SICF is working fine but SAP BW 7.3 Metadata Repository is not available (Not maintained) the corresponding service is not available that why System shows An error.
Regard's
R.S.Reddy

Applying 10.1.2.3 Metadata Repository update in 10.1.4.3 distributed IDM

Hi there, I seem to have a unique issue.
I have the following config of 10.1.4.3 IDM :
SSO in a separate Oracle home
OID in a separate Oracle home
DB (10.2.0.50) in a separte OH and metadata repository installed in this DB
and this is set up in ASR replication mode with other similer setup.
Task : Apply 10.1.2.3 OracleAS patchset.
The story:
To be fully compliant according to Orcale we ned to apply 10.1.2.3 patch. This patch has two components - a software update and a Metadata Repository (MR) update.
I have applied software update to all the Oracle homes above (with the exception of DB ofcourse).
But to apply MR update I have to do it from a mid-tier OH that also has MR installed, I have none.
I tried installing MR update from SSO and OID oracle home but it would not allow me , I got this message :
The Metadata Repository Update cannot be run from the selected ORACLE_HOME.
The Update must be run from either an Identity Management with Metadata
Repository installation ...
But we have no middle-tier using this MR, and from this metalik note, it seems applying MR update is not mandatory, only a desirable housekeeping execrcise . :
Understanding How AS 10g Patch Sets Update the AS Metadata Repository [ID 795143.1]
Exract from that note :
a. apply the binary update to each AS Oracle Home in the AS Farm.
b. finally, if possible apply the MR update exactly once from any home that allows it to be run.
also from the same note :
Scenario 6: Applying the 10.1.2.3 AS patch set to a 10.1.4.3 Identity Management home.
The 10.1.2.3 AS patch set is a required patch set, as documented in :
Note: 465847.1 Oracle Identity Management 10g (10.1.4.0.1) Release Notes Addendum.
In this case, the MR Product schemas will not be directly accessed. It is however good practice/ housekeeping to apply the MR update in order to keep the MR in line with the binary patch sets.
My question :
I am correct in my understanding that apply 10.1.2.3 software update only is neccessary, applying the MR update is only desirable house keeping and not mandatory ?
Would you say this is the correct assessment. if not how would you go about applying the MR update ?
Thanks in advance for your answers.
Narsimha

TooManyOracleToysToLearn wrote:
Upgraded OPatch to 1.0.0.0.64
Attempted to apply 10.1.2.3 patchset 5983622
Encountered 2 issues, 1 has prevented us from continuing
Issue 1: Received following on stdout ...
failed to get the ias-instance ...
Error: no ias instance to append to
Val: 3Did you source the correct env file before applying the patch? --> $INST_TOP/ora/10.1.3/<CONTEXT_NAME>.env
Issue 2: When running the Configuration Assistants, it fails right away on step "Run One-Off Patches".
It's looking for the ocm.rsp. Received the following:
Oracle Configuration Manager (OCM) is included with this release of OPatch.
This is a OCM patch.
EBS environment: no OCM installation and configuration.
To run in silent mode, OPatch requires a response file for Oracle Configuration Manager (OCM).
Run /u04/app/ebupg/ebupgora/10.1.2/OPatch/ocm/bin/emocmrsp to generate an OCM response file. The generated response file can be reused on different platforms and
in multiple OPatch silent installs.
To regenerate an OCM response file, rerun /u04/app/ebupg/ebupgora/10.1.2/OPatch/ocm/bin/emocmrsp.
ERROR: OPatch failed because of cmd. args. problem.Error Applying Patch Using OPatch "This version of OPatch is obsolete", "OPatch failed because of cmd. args. problem" [ID 762403.1]
10.1.4.3 Patch Set Pre Installation Step: dcmctl updateconfig FAILS: Fatal Relocation Error [ID 849474.1]
Getting Error 'OPatch requires a response file for Oracle Configuration Manager (OCM)' while Running OPatch [ID 727991.1]
Thanks,
Hussein

CD2 of Metadata Repository Creation Assistant (10.1.2.0.3) bad

Top Url of Page reads: http://www.oracle.com/technology/software/products/ias/htdocs/101202.html
CD2 of the Metadata Repository Creation Assistant (10.1.2.0.3) downloads fine and my cksumm of the file matches what I see on the download site of:
688884944 104409600 as_hp_risc_mrca_101203_disk2.cpio
However when I try to cpio in the file, I get the following error:
Disk2/stage/Patches/oracle.rdbms.hybrid/9.2.0.6.0/1/DataFiles/group.jar
End of volume
errno: 25, Can't read input
So if I could have you send me the correct cpio file at [email protected] it would be most helpful.
Thanks,
Ron

I ended up ordering the full HP 10gAS R2 disk set to get this. Would be nice if someone from Oracle would respond about the bad file though.
-Ron

How to refresh XI RFC Metadata Repository?

Hi everyone,
I would like to know how to refresh the XI RFCadapter Metadata Repository.
I had a scenario RFC(R/3) -> XI -> Legacy System. I made some changes in RFC on R/3 environment, adding some fields, but unfortunately these fields are not appearing in XI.
I imported and activated the RFC in "Design:Integration Builder" but XI still not receiving these new fields.
Thanks for your attention.
Best Regards,
Gabriel Santana
Message was edited by: Gabriel Sant'Anna

Hi,
Thank you for your replies.
Chris, I followed the guide you sent me, very helpful, but unfortunately when I tried to realize "Single Repository Object Cache Refresh" to object type "AdapterMetaData", the following error appeared:
Method fault! Message : Plain exception:null com.sap.guid.GUIDFormatException at com.sap.guid.GUID.parseHexGUID(GUID.java:814) at com.sap.guid.GUIDGenerator.parseHexGUID(GUIDGenerator.java:111) at com.sap.aii.utilxi.misc.api.GUIDFactory.parseHexGUID(GUIDFactory.java:120) at com.sap.aii.ibrep.server.abapcache.HmiMethod_CacheRefresh.process(HmiMethod_CacheRefresh.java:62) at com.sap.aii.ib.server.hmi.HmiServiceImpl.invokeMethod(HmiServiceImpl.java:132) at com.sap.aii.ib.server.hmi.HmiServer.process(HmiServer.java:248) at com.sap.aii.ib.sbeans.hmi.HmiBean.process(HmiBean.java:62) at com.sap.aii.ib.sbeans.hmi.HmiLocalLocalObjectImpl10.process(HmiLocalLocalObjectImpl10.java:144) at com.sap.aii.ib.web.hmi.HmiServlet.processRequestByHmiServer(HmiServlet.java:281) at com.sap.aii.ib.web.hmi.workers.ExternalClient.doWork(ExternalClient.java:78) at com.sap.aii.ib.web.hmi.HmiServlet.doWork(HmiServlet.java:560) at com.sap.aii.ib.web.hmi.HmiServlet.doGet(HmiServlet.java:704) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37) at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162) Stack trace: com.sap.aii.utilxi.hmi.api.HmiMethodFault: Plain exception:null com.sap.guid.GUIDFormatException at com.sap.guid.GUID.parseHexGUID(GUID.java:814) at com.sap.guid.GUIDGenerator.parseHexGUID(GUIDGenerator.java:111) at com.sap.aii.utilxi.misc.api.GUIDFactory.parseHexGUID(GUIDFactory.java:120) at com.sap.aii.ibrep.server.abapcache.HmiMethod_CacheRefresh.process(HmiMethod_CacheRefresh.java:62) at com.sap.aii.ib.server.hmi.HmiServiceImpl.invokeMethod(HmiServiceImpl.java:132) at com.sap.aii.ib.server.hmi.HmiServer.process(HmiServer.java:248) at com.sap.aii.ib.sbeans.hmi.HmiBean.process(HmiBean.java:62) at com.sap.aii.ib.sbeans.hmi.HmiLocalLocalObjectImpl10.process(HmiLocalLocalObjectImpl10.java:144) at com.sap.aii.ib.web.hmi.HmiServlet.processRequestByHmiServer(HmiServlet.java:281) at com.sap.aii.ib.web.hmi.workers.ExternalClient.doWork(ExternalClient.java:78) at com.sap.aii.ib.web.hmi.HmiServlet.doWork(HmiServlet.java:560) at com.sap.aii.ib.web.hmi.HmiServlet.doGet(HmiServlet.java:704) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37) at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162) at com.sap.aii.ibrep.server.abapcache.HmiMethod_CacheRefresh.process(HmiMethod_CacheRefresh.java:68) at com.sap.aii.ib.server.hmi.HmiServiceImpl.invokeMethod(HmiServiceImpl.java:132) at com.sap.aii.ib.server.hmi.HmiServer.process(HmiServer.java:248) at com.sap.aii.ib.sbeans.hmi.HmiBean.process(HmiBean.java:62) at com.sap.aii.ib.sbeans.hmi.HmiLocalLocalObjectImpl10.process(HmiLocalLocalObjectImpl10.java:144) at com.sap.aii.ib.web.hmi.HmiServlet.processRequestByHmiServer(HmiServlet.java:281) at com.sap.aii.ib.web.hmi.workers.ExternalClient.doWork(ExternalClient.java:78) at com.sap.aii.ib.web.hmi.HmiServlet.doWork(HmiServlet.java:560) at com.sap.aii.ib.web.hmi.HmiServlet.doGet(HmiServlet.java:704) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37) at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162) Root cause : null
Details: No details available
My path for this service is:
http://mslsr08:50000/rep/hmi_cache_refresh_service/ext?method=CacheRefresh&mode=RM&type=AdapterMetaData&guid0=&guid1=
How could I solve this issue and finally refresh the cache?
Best Regards,
Gabriel Santana

Crashing Metadata Repository?

Hi,
Realize this may be more suited for the General Database forum, but since it involves the OID metadata repository and the DBMS_LDAP APIs, thought I would try this board first.
I am trying to load 1400+ users into Oracle Internet Directory from an existing database.
I have written a small PL/SQL procedure that queries the database for the users info and then loads it into OID using the DBMS_LDAP APIs. I am using SQL*Developer to write and debug the procedure.
The procedure loads 1131 users, but then halts, returning a "No more data to read from socket" error. All users before this point are loaded correctly into OID.
Running this procedure from SQL*Plus results in a "ORA-03113: end-of-file on communication channel"
Researching the OTN and MetaLink forums leads me to believe that either the source database or the OID metadata repostitory is crashing, causing the connection to be lost. Perhaps this is a memory issue. . .?
I checked the logs for both the source database and the OID metadata repository - I can't find anything related to this problem (i.e. messages occuring at the same time I run the procedure.)
Can anyone give me any hints on how to troubleshoot this problem?
TIA
Jim
Here's the procedure. . .
CREATE OR REPLACE
PROCEDURE upload_users_oid AS
GN$Errcode NUMBER ;
GC$ErrLib VARCHAR2(2000) ;
GC$ldap_host VARCHAR2(256) := 'something.com'; -- your LDAP Host url
GC$ldap_port VARCHAR2(256) := '389'; -- your LDAP Port
GC$ldap_user VARCHAR2(256) := 'cn=orcladmin';
GC$ldap_passwd VARCHAR2(256) := 'somepassword';
GC$ldap_base VARCHAR2(256) := 'cn=users,dc=something,dc=com';
my_session DBMS_LDAP.SESSION;
emp_dn VARCHAR2(256);
emp_array DBMS_LDAP.MOD_ARRAY;
emp_vals DBMS_LDAP.STRING_COLLECTION;
cursor user_cur is
select username, lname, fname from usertable
where username IS NOT NULL AND status = 'A';
retval PLS_INTEGER;
user_username varchar2(30);
user_lname varchar2(32);
user_fname varchar2(32);
user_passwd varchar2(12);
BEGIN
retval := -1;
user_passwd := 'Passwd01';
open user_cur;
DBMS_OUTPUT.ENABLE(1000000);
DBMS_LDAP.USE_EXCEPTION := TRUE;
my_session := DBMS_LDAP.init(GC$ldap_host,GC$ldap_port);
retval := DBMS_LDAP.simple_bind_s(my_session, GC$ldap_user,GC$ldap_passwd);
LOOP
emp_array := DBMS_LDAP.create_mod_array(6);
FETCH user_cur into user_username, user_lname, user_fname;
EXIT WHEN user_cur%NOTFOUND;
emp_vals(1) := user_username;
DBMS_LDAP.populate_mod_array(emp_array,DBMS_LDAP.MOD_ADD, 'uid',emp_vals);
DBMS_LDAP.populate_mod_array(emp_array,DBMS_LDAP.MOD_ADD, 'cn',emp_vals);
emp_vals(1) := user_lname;
DBMS_LDAP.populate_mod_array(emp_array,DBMS_LDAP.MOD_ADD, 'sn',emp_vals);
emp_vals(1) := user_fname;
DBMS_LDAP.populate_mod_array(emp_array,DBMS_LDAP.MOD_ADD, 'givenname',emp_vals);
emp_vals.delete;
emp_vals(1) := user_passwd;
DBMS_LDAP.populate_mod_array(emp_array,DBMS_LDAP.MOD_ADD, 'userpassword',emp_vals);
emp_vals(1) := 'top';
emp_vals(2) := 'person';
emp_vals(3) := 'organizationalPerson';
emp_vals(4) := 'inetOrgPerson';
emp_vals(5) := 'orcluser';
emp_vals(6) := 'orcluserv2';
DBMS_LDAP.populate_mod_array(emp_array,DBMS_LDAP.MOD_ADD, 'objectclass',emp_vals);
emp_dn := 'cn=' || user_username || ', ' || GC$ldap_base;
DBMS_OUTPUT.PUT_LINE(RPAD('Adding Entry for DN ',25,' ') ||': [' || emp_dn || ']');
retval := DBMS_LDAP.add_s(my_session,emp_dn,emp_array);
DBMS_LDAP.free_mod_array(emp_array);
emp_vals.delete;
END LOOP;
Close user_cur;
retval := DBMS_LDAP.unbind_s(my_session);
EXCEPTION
WHEN OTHERS THEN
raise_application_error(-20001,'An error was encountered - '||SQLCODE||' -ERROR- '||SQLERRM);
END;

Because your stored procedure executes on the source database, I would look there thoroughly first.
Have you checked with your DBA for any resource limits on the userid that owns the session. Limits can be expressed in a number of ways, typically are defined in a user profile and can definitely manifest themselves as unexpected aborts out of nowhere for long running processes.
Of course a DBA can manually whack it, as well.
regards,
tt

Error preparing metadata repository

Similar Messages

Maybe you are looking for