Error while putaway TO creation
Hi,
While creating putaway TO using tcode LT03 against the inbound delivery i'm getting a Express document "Update was terminated" received from author, though the TO gets created but same is not updating the table. Following is the error description when checked in SBWP " ABAP/4 processor: SAPSQL_ARRAY_INSERT_DUPREC" .
Kindly suggest
JK
HI,
Self resolved the issue.
Similar Messages
-
There's an error while delivery note creation for STO order
There's an error while delivery note creation for STO order even stock available in unrestricted stock
Edited by: sharma aman on Nov 8, 2011 9:00 AMDear Sharma Aman,
Check whether the following link helps you.
Mesaage : while creation of delivery : An item with no delivery quantity .)
Please search in google with the error message and definitely you will get some older posts in SDN which is solved.
In that case , you need not wait for the solution as it is already available.
If the solution provided do not suit you, then post it in SDN so that it will be a learning for others.
Try to search in the forum or in google before posting further queries
Thanks & Regards,
Hegal K Charles -
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 PMHi yousuf;
Please follow below and see its helpful for your issue:
http://soadev.blogspot.com/2009_07_01_archive.html ( part:Error in Running Repository Creation Utility (RCU) While Using Oracle XE database )
Also check:
http://forums.tangosol.com/forums/thread.jspa?threadID=930952&tstart=60 (Joaanas post)
Regard
Helios -
Error while Debugging MSA 'Creation of Login Object Failed'
Dear Friends,
I am working on CRM Mobile Sales 5.0 SP 5.
I have setup my Mobile Client and Mobile Application Studion On the same machine.
I have perform the initial generation of the application from Mobile Repository server to my machine.
it gave me 6 errors and 12 warnings and took about 4 hrs for generation.
Now when i tried to debug the generated application,
i get my login screen and once I enter username and password.
Error popups up stating "Creation of login object failed".
and then another error
"Starting MPPFailed" (MPP is my project name).
Please suggest me how should i go about to debug the application solving the above errors.
Awaiting Reply,
Best Regards,
Pratik PatelAm not sure if you were able to resolve the issue but below are some points:
a. I think the dlls sfabol and msa are not any more registerable, since they are more of VB.NET components and here assembly is registered and not the dll.
b. For logging into the application just ensure that you have user id in table SMOUSER and the employee for that user in SMOMITABT table.
c. If this is fine, then ensure that you have the latest BDOC metadata information on your laptop. I think in 5.0 also you need to use Clientconsole to download this information.
d. If this is all okay, then try running SQL profiler and check if the query to the ides db is being executed by the framework. If the query is fired then it means application seems to behave properly but the query is not retrieving relevant details.
For further details feel free to contact me..
thanks,
Piyush -
Error while source system creation/Source system transport
Hi,
In our BW implementation, the system landscape is only 2 servers. One is BW Dev, another is BW Prd. All configurations are done in BW Dev and I extracted the data from QAS for this BW Dev system.
Since we cant create the source systems in the BW Production system, I tried to create the source system for the SAP R3 Production system in BW Dev and trying to transport this to BW Production Instance.
I have two queries.
1. Is this way is correct for creating the Source System for BW Production system?
2. When I tried to activate the source system I am getting the following error messages. (I tested the RFC Destinations. There is no problem, I also done the configurations for logical system creation and client assignment in both the systems).
Error in source system GWPCLNT900
Message no. RSAR502
Diagnosis
With Remote Function Call to system GWPCLNT900 error connection closed
(no data) ccurred.
Procedure
Remove the cause of the error.
When tried again I got the following error message
Basic type ZSBB030 doesnt exist. EA 447
Result of the destination check: Timeout RSAR 375.
Could anyone throw some light on these errors?
Thanks in advance.
KrishnaHi,
you need to maintain the logical systems on both R/3 and BW. You also need to set up the RFC connection with users that can log in to the other system. The R/3 system must be open for customizing in scc4.
In transaction se03 the system change options for 'Business Information Warehouse: SAP Namespace' and 'Business Information Warehouse: Customer Namespace' may need to be modifiable. I am not completely sure about this.
The last thing I will mention is that I have seen source system creation fail when the RFC-users are system users, and the source system creation worked if the RFC-users was display user while creating the source system. The RFC-users must be changed back to system user later...
Please look at best practice documents on a more step-by-step guide...
Best regards,
Christian Frier -
Error while Device Installation creation in Emigall
Hi Utility Gurus,
When creating full installation through EG31, i am able to create Installation successfully. But while creating Full Device installation through Emigall (object INST_MGMT) I am getting error 'Enter Rate Type'.
I am entering the correct Rate Type and Rate category in structure DI_ZW apart from that other required fields. And in structure DI_GER I am adding the Legacy Device no. Have also added the required fields in DI_INIT structure.
When I enter Rate type in DI_GER structure I get the error "Enter permissible Rate Type'.
Can anybody please let me know how this error can be removed and what are the things to note/configure before Device installation from Emigall.
RegardsHello All,
I know this is a very old thread but just to help anyone else who comes across the same error hope this helps.
In order to complete Full install you need the following structures to be activate/generated
1) Interface (DI_INIT)
2) OKCODE -- this is a hidden auto structure
3) ZWSTAND -- this is a hidden auto structure
4) AUTO_ZW (DI_ZW)
5) AUTO_GER (DI_GER)
6) CONTAINER -- this is a hidden auto structure
In order to view the hidden structure follow the below steps:
- Once you click on the INST_MGMT go to Automatic Structure--> Display List --> All
you will now be able to view all the hidden structures. IN order to activate/generate them you will have to click them go to automatic struture --> Change --> generate
Commonly required fileds in different sturctures are below (please note, these are the commonly used fields and varies based on the project requirments)
--> Interface
- ACTION
- ANLAGE
- DEVLOC
- EADAT
--> AUTO_ZW
- ABFAKTE
- ANZDAYSOFPERIOD
- ANZERG
- EQUNRE
- KONDIGRE
- PERVERBR
- PERVERBRE
- TARIFART
- ZWNABR
- ZWNUMMERE
- ZWSTANDCE
--> AUTO_GER
- ABRFAKT
- ACTION
- DEVLOC
- EQUNRNEU
- GERWECHS
- GVERRECHG
- KONDIGRG
- MATNR
- PREISKLAG
- TARIFARTG
Hope this helps.
Thanks,
Edited by: Anshul Varshney on Feb 2, 2012 5:09 PM -
Error while running index creation
Hi All ,
I am running index creation step like below .
alter session enable parallel DDL;
alter session set workarea_size_policy=manual;
alter session set sort_area_size=250000000;
alter session set db_file_multiblock_read_count=128;
CREATE INDEX "CUST_ROUTE_IDX" ON "CUST_2_K2K" ("PP2S", "KK2S")
PCTFREE 10 INITRANS 2 MAXTRANS 255 NOLOGGING
STORAGE( INITIAL 5M
NEXT 16777216
MINEXTENTS 1
MAXEXTENTS 2147483645
PCTINCREASE 0
FREELISTS 1
FREELIST GROUPS 1
BUFFER_POOL DEFAULT)
TABLESPACE "INDX" PARALLEL 2;
when i am running like above i am getting following error..
CREATE INDEX "CUST_ROUTE_IDX" ON "CUST_ROUTE_IDX" ("PP2S", "KK2S")
**ERROR at line 1:**
**ORA-00604: error occurred at recursive SQL level 1**
**ORA-04031: unable to allocate 38410272 bytes of shared memory ("large**
**pool","SEQ$","QERHJ hash-joi","kllcqc:kllcqslt")**
DB is ORA 10gR2 installed on 8 cpu machine with 32 GB of RAM . From Unix Top command i can understand that 18GB of RAM is free.
When i remove "alter session set sort_area_size=250000000;" and run above script no error is coming .
But enough memory is availabe to the machine as per UNIX . Can any one help me out why this err is coming .
Also when I do " show parameter sort_area_size " in any new sqlplus session it displays 65536
This value is in bytes/KB/MB ...pls advice
Thanks in AdvancePlease read any error message carefully, prior to posting.
**ORA-04031: unable to allocate 38410272 bytes of shared memory (*"large**
**pool"*,"SEQ$","QERHJ hash-joi","kllcqc:kllcqslt")**
Oracle is trying to allocate memory in the large pool, and the large pool is too small.
The sort_area_size has nothing to do with it.
Also there is no gain in setting the work_policy to manual, as Oracle will allocate memory beyond pga_aggregate_target automagically.
There is also no gain in setting db_file_multiblock_read_count, as Oracle will adjust that automagically.
Sort_area_size is in bytes, as documented, and it is your value in the spfile/init.ora which is the default or which you have set.
You can read about this in the documentation which is online at http://tahiti.oracle.com
Sybrand Bakker
Senior Oracle DBA -
Error while running Project Creation BP in Unifier 10
Hi Friends,
Getting the error[/shell/action.xml:1748: Could not invoke method cloneProjectBP] while running Project Request BP.
Regards
Kedarhi,
do you have atg search installed in your environment? if so configure it properly
Edited by: Raghuram A on Mar 14, 2013 11:33 PM -
Error while creating Infoset Creation
Hi All,
I've created an infoset using a program and data structure. But while generating the infoset this below mesg was getting as error:
Generation Error-->
Data Retrival Program-->
Commentary <Query_head> or <Query_body> is missing.
Please guide me with this error.
Thnks & Rgds,
Ravino answer.
-
Dear All,
At the time of Tax code creation through FTXP . i am getting the error message as Define the tax code on level 300.we are in SAP 4.7 with procedure TAXINJ. how to resolve this issue...?..
Regards
Anand.Hi,
Please go to SM30 and enter the Table Name J_1IINDCUS. Now click on Maintain. Enter your company Code 1005 and Maintain the all settings which are required.
I hope it should work
Regards,
Jigar -
Error while uploading Customer creation ( XD01) using Call Transaction
Hi Experts,
While recording XD01, i checked on Use Central Address Management checkBox,
i got two pop-ups,
1. Postal code 500018 in country IN does not exist.
2. City Hyderabad in country IN does not exist.
i accepts those pop-ups by Clicking on Yes Button.
while executing in All Screen Mode it executes without errors,
But in No Screen mode i am getting error in address screen and in the messtab i got MSGV1= 500018 (postal code) and
FLDNAME = SZA1_D0100-TITLE_MEDI.
Is there any other way to get the Title in title list box without using Use Central Address Management Check Box,
without checking Use Central Address Management Check Box, i am not getting the title in the title list box while displaying in XD02.
Please help me out to solve the problem.
Thanks & Regards,
Karthick.Hi,
I solved this problem.
By changing the configuration Data through the path spro->SAP NetWeaver-> General Settings->set Contries->Set Contry-Specific Checks and click on the Contry code, a screen will display the default checks. Previously it is configured to a particular location with respect to Pincode , i updated as per my requirement. So the pop-ups are not coming and it workes fine in all Modes(A/N/E) of BDC.
The Title problem is also solved by revised recording of XD01.
Then my problem is solved.
Thanks & Regards,
Karthick. -
Error while excise invoice creation thru J1IJ
Dear All,
Scenario: Stock transfer from Excise depo to other plant.
Problem :
Excise Invoice is not getting Generate in Transation J1IJ. i am getting following error
"Excise invoice selection not complete for the item 000010"
Also Please tell me the process , (STPO > Delivery > Invoice > Excise Invoice) is it correct ?
Thanks in advance
VishalHi ,
The process as below
1.Create STO ---Me21n
2.Delivery with reference to STO ---Vl10B/VL10D
3.Invoice proforma with reference to delivery--Vf01
4.Excise invoicewith reference to Proforma---J1iJ
Kindly check the excise duty is coming in the proforma invoice
Regards
Damu -
Error while creating Shipment Creation
Hi all,
when am creating Collective shipment vth Tcode:VT04,
am getting the below error-
" Unit of measure between L&KG are not maintained" -
we have previous del documents for which shipment doc was created through VT04.
but this time, amnot able to create.
please suggest me,
its quite urgent.RMD,
Check IMG- Global Settings - Check Units of Measurement config
Also in shipment configurartion see if UOM is matching with ur MMR...
REWARD IF U FINDS THIS AS USEFUL...
Regds
MM -
Error while Installment Plan creation
Dear friends ,
When i am saving the installment plan i am getting this error can anyone please let me know how to rectify this error
Internal error: Incorrect use of a function module
Function module FKK_TAX_EXEMPT_KEY_DETERMINE was called with incomplete parameter specifications. One of the following entries is missing in transfer structure I_FKKTAXEXC:
Tax code
Company codeHi,
You check the a/c determination for Inst Plan in EK01 & EK02.
I beleive that the G/L a/c is incorrectly assigned.
Regards,
T -
Error while lock object creation
Hi
When I tried to create a lock object, I get the following error.
Error: "Total length of lock argument for table XXXXXXXXX longer than 150"
I have 3 tables in which Table1 is the check table for the value tables (Table2 & Table3). During the process of deletion of a record from Table1 (CT) I need the lock tobe established on value tables and then I delete all the corresponding entries in value tables are also deleted.
Would like to know If there is any other std ways of doing this ? and
Solution to overcome the error.
Regards
KarthickHi,
I think the error is becoz you have given too many LOCK parameters in the lock object. the total length of the PARAMTERS of lock object should not exceed 150.
By default all the KEY fields will be taken as Lock paramters, so your table key's length is more than 150.
Also why dont you create 3 lock objects for each table and then use only KEY's of each table as LOCK PARAMETERS.
Then Lock T1 record first then lock T2 and T3 records, then delete records from T2 and T3.
Then you delete T1 record.
The execute DEQUEUE_ALL.
Regards,
Sesh
Maybe you are looking for
-
Credit Block released Sales order report
Hi Experts, My client is given few sales orders (around 4)no and requesting us, to prepare the credit block released sales orders report (include released person user ID). *.No change logs is existing for all sales order and deliveries. For above req
-
Error: "Name" did not respond
I'm having trouble connecting to my friend. I am on a powerbook g4 running OSX 1.3.9, she's using a new macbook with Tiger. I have the older version of iChat while she has iChat AV. When we try to either audio chat or video chat, it says that she did
-
ANN: Anyone been helped by Tomaxxi (Marijan Tompa)?
Go here and help him get to the 2011 Print and ePub conference in Washington! Honestly, he comes up with so many scripts and cool stuff, like this, imagine what he'll come up with after some inspiration and encouragement! This probably should be po
-
SAPGUI and Portal Authentication using AD Credentials with usr/passw prompt
Hi Experts, We have the following requirements: 1. Portal/EP has UME set to ABAP (in other words using ECC6 system's user/password). 2. ECC6 user-id's differ from Active Directory user. 3. User logs in to Active Directory. 4. User wants to log on to
-
How to stream Live News on Apple TV Gen 3 all day long
I have searched and searched and cannot find any help with this matter. My searching must need some help. I am trying to set up this apple tv at my office. Model A1427 so it should be a Gen 3 correct? http://support.apple.com/kb/HT200008?viewloca