News creation error in Km Repository
hi,
There is a Km repository in portal Km content.
When I tried to create a news in its sub folders using the sap demo news template it gives an error 'creation error'.But I am able to create news with the same template in other folders in root.Please help me to solve this issue.
Thanks in advance,
jesmi.
Hi Jesmi,
Create your contents under /root/documents. Contents created using XML forms builder can be saved only under /root/documents and not /root itself.
To access the repository, use Explorer menu under Content Management role. I believe that you are accessing it using KM Content menu under Content Admin role.
Hope it helps,
Shankar
Similar Messages
-
An error occurred during creation of the central repository. (BODI-300020)
I am trying to create a central repository for Data Service, the following error appear
Creating repository... (BODI-300026)
Reading SQL file <C:\BO\DataServices_12\admin\repo\MSSQL\ms.sql>. (BODI-20001)
Executing SQL file <C:\BO\DataServices_12\admin\repo\MSSQL\ms.sql>. (BODI-20002)
Reading SQL file <C:\BO\DataServices_12\admin\repo\MSSQL\ms_content.sql>. (BODI-20001)
Executing SQL file <C:\BO\DataServices_12\admin\repo\MSSQL\ms_content.sql>. (BODI-20002)
Reading SQL file <C:\BO\DataServices_12\Admin\repo\options.sql>. (BODI-20001)
Executing SQL file <C:\BO\DataServices_12\Admin\repo\options.sql>. (BODI-20002)
Verifying repository... (BODI-300077)
Importing objects... (BODI-300036)
Adding Data Quality new substitution configuration... (BODI-300133)
An error occurred during creation of the central repository. (BODI-300020)
It's a sql DBMS, and the default user language is spanish, during the installation was the same issue.
The first installation user language was english and everything was ok, then the default user anguage was set to spanish and the jobs crashed because an english format was sent to the al_history table. I tried to recreate the repository and an error ocurrer during the creation.
has someone faced the same problem?what is the version of Data Services ? if its 12.2, then there was a bug that is fixed in 12.2 SP1 (12.2.1.0), apply the SP1 or it would be better if you apply the latest fix pack for 12.2 i.e 12.2.1.2
the problem was with date format used in insert was different than the user's default date format. -
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 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 -
Child creation Error on vms HELP
Hi,
Iam trying to execute a file from withing a java program on VMS This is my code
public class BAMBOE {
public static void main(String[] args) {
BamboeRunner boe = new BamboeRunner();
boe.start();
import java.io.*;
public class BamboeRunner extends Thread implements Runnable {
public void run() {
try {
Process process = Runtime.getRuntime().exec("@SIMPEL");
process.waitFor();
return ;
catch (Exception e) {
e.printStackTrace();
return ;
}But I keep getting the following error:
java.io.IOException: Child creation error: error 100052
VMS error code: error 100052
at java.lang.UNIXProcess.<init>(Compiled Code)
at java.lang.Runtime.exec(Compiled Code)
at java.lang.Runtime.exec(Compiled Code)
at BamboeRunner.run(Compiled Code)Anybody that can help me fix this problem please??I've managed to get somewhere with this...
I've got it to work by having the system command I want to run in a com file and specifying the full path to that file in the exec method without the '@'...
e.g.
Process proc = Runtime.getRuntime.exec("ppoi_dev:[user.dba_ppoi.matt.proc]proc.com");
where the file
ppoi_dev:[user.dba_ppoi.matt.proc]proc.com
contains
$ dir
When I run this I can get the output from the dir command by reading from the InputStream of the Process object.
Have fun. -
Hi all, i have tried to define a new VIP on my ORACLE 11gR2 RAC cluster, in order to manage third-party component by using ORACLE Clusterware.
I have used the info written on the ORACLE manual "Oracle Clusterware Administration and Deployment Guide E10717-04" at page 5-15.
I have executed the command "/u01/app/grid/bin/appvipcfg create -network=1 -ip=xx.xxx.xxx.140 -vipname=appsVIP -user=root", as the manual says, from root user.
My environment is AIX 6.1.
Unfortunately, i get an error (reported following) but i am not able to solve it.
Please, may you help me?
Thanks
Marco
CUSTOM VIP CREATION ERROR
[nodo01][]>/u01/app/grid/bin/appvipcfg create -network=1 -ip=xx.xxx.xxx.140 -vipname=appsVIP -user=root
Production Copyright 2007, 2008, Oracle.All rights reserved
2010-05-31 18:39:54: Creating Resource Type
2010-05-31 18:39:54: Executing cmd: /u01/app/grid/bin/crsctl add type app.appvip.type -basetype cluster_resource -file
/u01/app/grid/crs/template/appvip.type
2010-05-31 18:39:55: Create the Resource
2010-05-31 18:39:55: Executing cmd: /u01/app/grid/bin/crsctl add resource appsVIP -type app.appvip.type -attr
USR_ORA_VIP=xx.xxx.xxx.,START_DEPENDENCIES=hard(ora.net1.network)
pullup(ora.net1.network),STOP_DEPENDENCIES=hard(ora.net1.network),ACL='owner:root:rwx,pgrp:root:r-x,other::r--,user:root:r-x'
CRS-0247: User name or group name is invalid
CRS-4000: Command Add failed, or completed with errors.
Command return code of 1 (256) from command: /u01/app/grid/bin/crsctl add resource appsVIP -type app.appvip.type -attr
USR_ORA_VIP=xx.xxx.xxx.,START_DEPENDENCIES=hard(ora.net1.network)
pullup(ora.net1.network),STOP_DEPENDENCIES=hard(ora.net1.network),ACL='owner:root:rwx,pgrp:root:r-x,other::r--,user:root:r-x'
2010-05-31 18:39:56: ###### Begin Error Stack Trace ######
2010-05-31 18:39:56: Package File Line Calling
2010-05-31 18:39:56: --------------- -------------------- ---- ----------
2010-05-31 18:39:56: 1: crsconfig_lib crsconfig_lib.pm 7474 crsconfig_lib::error
2010-05-31 18:39:56: 2: main appvipcfg.pl 241 crsconfig_lib::system_cmd
2010-05-31 18:39:56: 3: main appvipcfg.pl 93 main::config
2010-05-31 18:39:56: 4: main appvipcfg.pl 74 main::process_arguments
2010-05-31 18:39:56: ####### End Error Stack Trace #####
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------Hi,
On Solaris 10 and Oracle Grid Infrastructure 11.2.0.2 did the following. Posting this as it might be useful to someone else. Installed Grid Infrastructure as oracle.
As root:
# ${GRID_HOME}/bin/appvipcfg create -network=1 -ip=<vip_address> -vipname=<vip_name> -user=root
In the above command, if you are wondering what -network=1 is, got useful info from "Oracle GoldenGate high availability using Oracle Clusterware" white paper at http://www.oracle.com/technetwork/middleware/goldengate/overview/ha-goldengate-whitepaper-128197.pdf
As per the white paper, if you do
crsctl status resource -p | egrep -i 'network|subnet' | egrep -i 'name|subnet'
output will look something like this:
NAME=ora.net1.network
USR_ORA_SUBNET=10.2.0.0
net1 in NAME indicates this is network 1, and second line indicates the subnet on which the vip will be created.
# ${GRID_HOME}/bin/crsctl setperm resource <vip_name> -u user:oracle:r-x
I did the following as oracle:
Oracle_Prompt> ${GRID_HOME}/bin/crsctl start resource <vip_name>
If you want to relocate this vip to other node in the cluster:
Oracle_Prompt> ${GRID_HOME}/bin/crsctl relocate resource <vip_name> -s <source_node> -n <target_node>
Hope this helps.
Thanks,
Moorthy.
帖子经 Moorthy Rekapalli编辑过 -
Error Installing OWB Repository
I exported a 9.2.0.1 Database and imported the user into a new Database Instance.
However, not all the runtime and repository components were reimported into the new schema.
I dropped and reinstalled the runtime successfully.
I also dropped the repository but have been unable to reinstall the repository.
OWB Client NT Client Version: 9.0.3.36.2
DB OS: Sun Solaris
DB Version 9.2.0.1.0
The following is the error in the repository error log:
Sat Jun 21 17:50:12 VET 2003
oracle.wh.util.DebugUtility: java.sql.SQLException: ORA-00904: "OWM_VIEW_UTILITIES"."CLASSIFIED_OBJ_TYPE": invalid identifier
Sat Jun 21 17:50:12 VET 2003
oracle.wh.util.DebugUtility: ORA-06512: at line 2
Sat Jun 21 17:50:12 VET 2003
oracle.wh.util.DebugUtility: [ at runSqlScript(RuntimeInstaller.java ) ].
Sat Jun 21 17:50:12 VET 2003
oracle.wh.util.DebugUtility: this is SQL error
Sat Jun 21 17:50:12 VET 2003
oracle.wh.util.DebugUtility: java.sql.SQLException: ORA-00904: "OWM_VIEW_UTILITIES"."CLASSIFIED_OBJ_TYPE": invalid identifier
Sat Jun 21 17:50:12 VET 2003
oracle.wh.util.DebugUtility: ORA-06512: at line 2
Sat Jun 21 17:50:12 VET 2003
oracle.wh.util.DebugUtility: java.sql.SQLException: ORA-00904: "OWM_VIEW_UTILITIES"."CLASSIFIED_OBJ_TYPE": invalid identifier
Sat Jun 21 17:50:12 VET 2003
oracle.wh.util.DebugUtility: ORA-06512: at line 2
Sat Jun 21 17:50:12 VET 2003
oracle.wh.util.DebugUtility:Kirt,
Are you rerunning the repository assistant, or are you trying to restore from a dump? Officially we do not support restoring from a dump (not yet, at least) ... but there are some notes on metalink on how to do it anyway:
Repository, note 228918.1:
http://metalink.oracle.com/metalink/plsql/ml2_documents.showFrameDocument?p_database_id=NOT&p_id=228918.1
Runtime, note 235658.1:
http://metalink.oracle.com/metalink/plsql/ml2_documents.showFrameDocument?p_database_id=NOT&p_id=235658.1
Mark. -
Hi!
I ran into the following problem when referencing the public parts of
an external j2ee library project stored in the NWDI. Specifically I would
like to reference an API part for having a correct build path during development.
Unfortunately I can create this reference but afterwards the NWDS tells
me that it requires to rebuild the ejb-jar.xml and the ejb-j2ee-engine.xml.
This automated refactoring leaves me with two 'empty' files, having all
my ejb definitions removed.
I tried to define new stateless ejbs by creating them via the context menu
and ran into the error 'Not able to create Session Bean'. In order to find out
what happened, I checked the .log file of the NWDS in my workspace folder
and found the following lines:
com.tssap.j2ee.ui.ejb.external.EjbCreationException: Creation error of EJB
at com.tssap.j2ee.ui.ejb.external.EjbFactory.createSessionBean(EjbFactory.java:304)
at com.tssap.j2ee.ui.ejb.external.EjbFactory.createSessionBean(EjbFactory.java:91)
at com.tssap.j2ee.ui.perspective.core.action.CreateEjbInPackageActionProvider$CreateStatelessSessionBeanInPackageAction.run(CreateEjbInPackageActionProvider.java:468)
at com.tssap.selena.model.extension.action.SelenaActionCollector$GenericElementActionWrapper.run(SelenaActionCollector.java:224)
at com.tssap.util.ui.menu.MenuFactory$MuSiAction.saveRunAction(MenuFactory.java:1425)
at com.tssap.util.ui.menu.MenuFactory$MuSiAction.run(MenuFactory.java:1407)
at com.tssap.util.ui.menu.MenuFactory$DelegateAction.processInternal(MenuFactory.java:616)
at com.tssap.util.ui.menu.MenuFactory$DelegateAction.access$100(MenuFactory.java:586)
at com.tssap.util.ui.menu.MenuFactory$DelegateAction$BusyProcessWorker.run(MenuFactory.java:716)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
at com.tssap.util.ui.menu.MenuFactory$DelegateAction.process(MenuFactory.java:610)
at com.tssap.util.ui.menu.internal.MenuListenerFactory$ProcessAdapter.widgetSelected(MenuListenerFactory.java:172)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
at com.sap.ide.eclipse.startup.Main.main(Main.java:607)
Nested exception -
com.tssap.j2ee.model.J2eeCreateException: Creation error of EJB
at com.tssap.j2ee.model.ejb.impl.EjbProject.createSessionBean(EjbProject.java:155)
at com.tssap.j2ee.model.ejb.impl.EjbModule.createSessionBean(EjbModule.java:385)
at com.tssap.j2ee.ui.ejb.wizard.internal.CreationFactorySemanticAPI.createEJB(CreationFactorySemanticAPI.java:115)
at com.tssap.j2ee.ui.ejb.wizard.internal.CreationFactorySemanticAPI.createSessionBean(CreationFactorySemanticAPI.java:55)
at com.tssap.j2ee.ui.ejb.external.EjbFactory.createSessionBean(EjbFactory.java:301)
at com.tssap.j2ee.ui.ejb.external.EjbFactory.createSessionBean(EjbFactory.java:91)
at com.tssap.j2ee.ui.perspective.core.action.CreateEjbInPackageActionProvider$CreateStatelessSessionBeanInPackageAction.run(CreateEjbInPackageActionProvider.java:468)
at com.tssap.selena.model.extension.action.SelenaActionCollector$GenericElementActionWrapper.run(SelenaActionCollector.java:224)
at com.tssap.util.ui.menu.MenuFactory$MuSiAction.saveRunAction(MenuFactory.java:1425)
at com.tssap.util.ui.menu.MenuFactory$MuSiAction.run(MenuFactory.java:1407)
at com.tssap.util.ui.menu.MenuFactory$DelegateAction.processInternal(MenuFactory.java:616)
at com.tssap.util.ui.menu.MenuFactory$DelegateAction.access$100(MenuFactory.java:586)
at com.tssap.util.ui.menu.MenuFactory$DelegateAction$BusyProcessWorker.run(MenuFactory.java:716)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
at com.tssap.util.ui.menu.MenuFactory$DelegateAction.process(MenuFactory.java:610)
at com.tssap.util.ui.menu.internal.MenuListenerFactory$ProcessAdapter.widgetSelected(MenuListenerFactory.java:172)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
at com.sap.ide.eclipse.startup.Main.main(Main.java:607)
Does anyone has been confronted with such an error before and could give
me a hint about how to solve this problem.
Kind regards,
Christian KreutzfeldtI resolved the problem myself by creating a new library project where I added
the libraries stepwise until building the referencing project failed. The library
project contains the hibernate framework which includes a file named jboss-j2ee.jar.
In some way or another this conflicts with the NWDS which leads to failures
when updating the ejb-jar.xml and ejb-j2ee-engine.xml files. -
Server version 180 cannot read the newer version 183 of the Repository.
Hi All,
We have our BI Server on Linux at version 10.1.3.3.0.070809.0909 and the Adminstration tool at version 10.1.3.3.1.071012.2100 and we are getting the following error.
"Server version 180 cannot read the newer version 183 of the Repository."
This is so surprising that a minor version is causing the Repository to be unreadable. Now we have to ensure all our developers are using the precise version of the Administration tool. Just wanted to let you guys know, so that you do not face the same problem.
Is there some patch available to directly upgrade to 10.1.3.3.2.
Thanks,
Neil.FYI: We are attempting to downgrade our Repository for now. Let's hope this works.
http://oraclebizint.wordpress.com/2008/03/03/oracle-bi-ee-101332-downgrading-repositories/ -
Download Helper Screen Capture worked to capture video if the default "no audio" option is active. But, no audio. The "speakers" or "microphone" audio options are confusing....the audio to be captured is from the video, so what do you choose? With either "speakers" or "microphone" selected, the captured file has poor audio and no video. Re-capture efforts (speakers) get "Invalid capture file error" and "File Creation error- Unable to rename/copy audio file"
The paid upgrade of "Converter" doesn't work.
Instructive documentation - not very good.
Suggestions - Need time delay between initiation of "Record" and starting the video to be recorded.
Could use timer tracking of the record process.
Are there operating system limitations? (Have Windows XP Pro)That is an issue for the developer of that Download Helper.
-
Hi all, Can anyone help me with this problem?
I have created a master detail table but have had problems with adding new detail lines.
The detail region contains an advanced table with an addTableRow bean set in the footer. I wish to navigate to a new page when the ‘add new row’ button is selected so I have set the ‘insert rows automatically’ property to false. I have been able to capture the event in my controller and call the new page and then access the application module, however I do not seem to be able to set a property in the new child line from an attribute in the parent line.
//in my AM I have called…
public void CreateLine()
//get child vo that is to have line added
DoiLinesVOImpl vo = (DoiLinesVOImpl) getDoiLinesVO1();
if (!vo.isExecuted()) vo.executeQuery();
//find parent vo to determine which questionId the line relates to
OAViewObject hvo = (OAViewObject)findViewObject("DoiDecQuestionsVO1");
OARow hRow = (OARow)hvo.getCurrentRow();
Number sid = (Number) hRow.getAttribute("QuestionId ");
System.out.println ( " qid= " + qid );
if ( vo != null)
vo.setMaxFetchSize(0);
Row vRow = vo.createRow();
vo.insertRow(vRow);
vRow.setAttribute("QuestionId",qid);
vRow.setNewRowState(Row.STATUS_INITIALIZED);
Initially the page was running, however it was only ever showing the id for the first line, regardless of which child table I was select add new line on. Now the new page errors and when I click on exception details the page does not show any error details
Can anyone see anything wrong with the code in the AM or have any suggestions as to what else may be wrong. Is it actually possible to do what I am trying to do? My aim is to have a table of questions and then a table region under the detail region of each question. Either no lines, one line or multiple lines can be added under each questions details. The questions may have slightly different required fields so I would like to navigate to a new page and then back to the main page when save is selected.
Any insights into what I am doing wrong or how I might achive my requirement would be very much appreciated.
Mike.Ok, I have now got the page to stop erroring.
I have created a new VO instance of the child EO in the application module and used the new vo in the seperate create page attributes, however when I query the current row against the parent vo I am still getting the value from the first line, not the selected parent line.
mike. -
Error While Creating Repository Content at the time of Installation
Hi Guys,
When i'm trying to create repository content at the time of informatica installation i'm getting error "Cannot create repository content or restore".
I'hve attached the log file below
ONE')
INSERT INTO REP_CARD_TYPE VALUES (4, 'MANY TO MANY')
CREATE TABLE REP_TARG_TYPE
TARGET_TYPE integer,
TYPE_NAME varchar(20)
INSERT INTO REP_TARG_TYPE VALUES (0, 'NONE')
INSERT INTO REP_TARG_TYPE VALUES (1, 'DIMENSION')
INSERT INTO REP_TARG_TYPE VALUES (2, 'FACT')
CREATE VIEW REP_DATABASE_DEFS AS SELECT
DISTINCT
DBDNAM DATABASE_NAME,
SRCNAM DEF_SOURCE,
SUBJ_NAME SUBJECT_AREA,
NULL VERSION_ID,
OPB_DBD.VERSION_NUMBER DATABASE_VERSION_NUMBER
FROM OPB_DBD, OPB_SUBJECT, OPB_SRC
WHERE OPB_DBD.SUBJ_ID = OPB_SUBJECT.SUBJ_ID AND
OPB_SRC.DBDID = OPB_DBD.DBDID AND
OPB_SRC.VERSION_NUMBER = OPB_DBD.VERSION_NUMBER AND
OPB_SRC.IS_VISIBLE = 1
ORA-01031: insufficient privileges
Database driver error...
Function Name : executeDirect
SQL Stmt : CREATE VIEW REP_DATABASE_DEFS AS SELECT
DISTINCT
DBDNAM DATABASE_NAME,
SRCNAM DEF_SOURCE,
SUBJ_NAME SUBJECT_AREA,
NULL VERSION_ID,
OPB_DBD.VERSION_NUMBER DATABASE_VERSION_NUMBER
FROM OPB_DBD, OPB_SUBJECT, OPB_SRC
WHERE OPB_DBD.SUBJ_ID = OPB_SUBJECT.SUBJ_ID AND
OPB_SRC.DBDID = OPB_DBD.DBDID AND
OPB_SRC.VERSION_NUMBER = OPB_DBD.VERSION_NUMBER AND
OPB_SRC.IS_VISIBLE = 1
Oracle Fatal Error
Database driver error...
Function Name : ExecuteDirect
Oracle Fatal Error
Error occurred while creating the repository
An error has occurred while creating contents. Dropping repository tables...
Create Contents operation on repository [Oracle_BI_DW_Base] ended at 08/10/2009 11:50:49. Elapsed time is 0:00:10.
[[REP_57106] Repository operation error. See repository service log for detailed information.]
Failed to execute create.
Completed at Mon Aug 10 11:50:49 2009
Error:
ExitCode: 1
Installation Complete
======================Hi Rama,
You don't need to give your etl_ram user a dba role.
Please refer to the Oracle® Business Intelligence Applications - Installation Guide for Informatica PowerCenter Users, especially to chapter +4.4.1 Create Databases for Oracle BI Applications and Informatica PowerCenter Components+
Quoting:
Make sure that the Oracle Business Analytics Warehouse instance is granted the SSE_ROLE. For more information, see Section 4.4.1.1, "How to Create the SSE Role."
This role would typically get more privileges than just CONNECT and RESOURCE.
Hope it helps,
Michal -
New-AzureDeployment - Error while copying content to a stream
Hi All,
I am trying to deploy a packages using the Azure Powershell Cmdlets.
Each time I try to deploy a particular package, I get the following error message..
New-AzureDeployment : Error while copying content to a stream.
At line:1 char:1
+ New-AzureDeployment -DoNotStart -ServiceName $strStagingCCPDeploymentServiceName ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [New-AzureDeployment], HttpRequestException
+ FullyQualifiedErrorId : System.Net.Http.HttpRequestException,Microsoft.WindowsAzure.Commands.ServiceManagement.HostedServices.NewAzureDeploymentCommand
Looking at the inner exception I am getting
Unable to read data from the transport connection: The connection was closed.
The package itself is only 80mb and uploads to my blob storage successfully however when it tries to deploy using my config file the error occurs. The same config file works fine if I use the Azure Website to deploy the package, rather than the cmdlets
and I can deploy other packages successfully using PowerShell and using Visual Studio.
Thank you for any help you can provide.Hi,
This seems to be a network issue, but it's quite strange as you can deploy the package from Visual Studio. Could you please try it on another machine (in another network environment if possible)? Also, can you try
to write a program and call the management API (http://msdn.microsoft.com/en-us/library/windowsazure/ee460813.aspx) to deploy it?
Best Regards,
Ming Xu
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey. -
Error while Configuring Repository INS0017: Installation of the seeded data
I am getting error while configuring repository at 36%
Error:
Seeding Failed:
The warehouse builder workspace owner installation failed on user OWBSYS.
INS0017:Installation of the seeded data failed java.io.FileNotFoundException:
xmlClasses.xml (Access is denied)
Operating system: Windows 2008 server 64 bit
Database: Oracle 11g Release 11.2.0.1.0 64 bit
Log file is not created in given location(Unified repos)Hi David,
But we have successfully Created the Repository(Using Repository Assistance) using OWB 10.2.0.4 on Oracle 11.1.0.7 Db on Solaris OS.
and i also checked the Metalink it say the OWB 10.2.0.4 can be used with Oracle 11.1.0.7 Db.
Nawneet -
Service Contracts Billing Schedule Creation Error
Hi,
I have a requirement of creating service contracts from back-end for which I am using the oks_contracts_pub.create_contract_header, create_service_line, and create_bill_schedule. I am creating my contracts with active status and renewal type of EVN (Header level), FUL(Line Level). My contract is of type subscription. The contract header and line are creating fine but the Bill schedule API is throwing an UNEXPECTED ERROR. The billing schedules need to be created based on accounting rule which can be quarterly or monthly. I have included the bill schedule code (hard coded values) for review. Any help is greatly appreciated.
Also the version I am working on is R12
________________________________________________CODE___________________________________________________________________
CREATE OR REPLACE PROCEDURE BILLING_SCHEDULE AS
l_strm_level_tbl OKS_BILL_SCH.STREAMLVL_TBL;
v_bill_qtrs NUMBER := 0;
v_bill_mths NUMBER := 0;
v_bill_days NUMBER := 0;
v_net_amount NUMBER := 468;
v_acct_rule_name VARCHAR2(50) := 'QUARTERLY';
v_amt_per_day NUMBER;
x_error_locator VARCHAR2(2000);
v_start_date DATE := '04-MAY-2010';
v_end_date DATE := '25-MAY-2010';
x_return_status VARCHAr2(3);
x_msg_count NUMBER;
x_msg_data VARCHAR2(2000);
v_billing_sequence NUMBER;
x_chr_id NUMBER := 17000;
x_line_id NUMBER := 223248604345353294444923586786456728480;
g_day_uom VARCHAR2(10) := 'DAY';
g_month_uom VARCHAR2(10) := 'MTH';
g_quarter_uom VARCHAR2(10) := 'QTR';
v_amt NUMBER;
v_invoicing_rule_id NUMBER := -2;
BEGIN
--Create Billing Schedule based on accounting rule
okc_context.set_okc_org_context;
MO_GLOBAL.INIT('OKS');
MO_GLOBAL.SET_POLICY_CONTEXT('S', 83);
v_bill_qtrs := 0;
v_bill_days := 0;
v_bill_mths := 0;
SELECT NVL(v_net_amount, 0)/(v_end_date - v_start_date)
INTO v_amt_per_day
FROM dual;
dbms_output.put_line('Calculated amt per day ' || v_amt_per_day);
IF v_acct_rule_name LIKE '%QUARTERLY%' THEN
--Quarterly billing schedule
SELECT FLOOR(MONTHS_BETWEEN( v_end_date,
v_start_date)/3),
v_end_date - ADD_MONTHS(v_start_date, (FLOOR(MONTHS_BETWEEN(v_end_date, v_start_date)/3)*3))
INTO v_bill_qtrs,
v_bill_days
FROM dual;
dbms_output.put_line('Calculated the qtrs and days');
IF v_bill_qtrs > 0 THEN
SELECT (ADD_MONTHS(v_start_date, (FLOOR(MONTHS_BETWEEN(v_end_date, v_start_date)/3)*3)) - v_start_date)*v_amt_per_day
INTO v_amt
FROM dual;
dbms_output.put_line('Calculated qtr amt');
SELECT NVL(MAX(sequence_no), 0) + 1
INTO v_billing_sequence
FROM oks_stream_levels_b
WHERE dnz_chr_id = x_chr_id
AND cle_id = x_line_id;
--Populating the stream line variables
l_strm_level_tbl(v_billing_sequence).sequence_no := v_billing_sequence;
l_strm_level_tbl(v_billing_sequence).dnz_chr_id := x_chr_id;
-- l_strm_level_tbl(v_billing_sequence).id := x_line_id;
l_strm_level_tbl(v_billing_sequence).cle_id := x_line_id;
l_strm_level_tbl(v_billing_sequence).uom_code := g_quarter_uom;
l_strm_level_tbl(v_billing_sequence).uom_per_period := 1;
l_strm_level_tbl(v_billing_sequence).level_periods := v_bill_qtrs;
l_strm_level_tbl(v_billing_sequence).start_date := v_start_date;
l_strm_level_tbl(v_billing_sequence).end_date := v_end_date;
l_strm_level_tbl(v_billing_sequence).invoice_offset_days := NULL;
l_strm_level_tbl(v_billing_sequence).amount := v_amt/v_bill_qtrs;
l_strm_level_tbl(v_billing_sequence).level_amount := v_amt/v_bill_qtrs;
l_strm_level_tbl(v_billing_sequence).lines_detailed_yn := 'Y';
l_strm_level_tbl(v_billing_sequence).due_arr_yn := 'Y';
dbms_output.put_line('Before calling the Bill Sch API for QTR');
OKS_CONTRACTS_PUB.CREATE_BILL_SCHEDULE ( p_billing_sch=>'E',
p_strm_level_tbl=>l_strm_level_tbl,
p_invoice_rule_id=>v_invoicing_rule_id,
x_return_status=>x_return_status);
dbms_output.put_line('After calling the Bill Sch API for QTR');
IF x_return_status <> 'S' THEN
x_msg_count := 1;
dbms_output.put_line('Quarterly schedule creation error ' || x_msg_data);
---DBMS_TRANSACTION.ROLLBACK_SAVEPOINT('OKS_A');
-- RETURN;
END IF;
END IF;
IF v_bill_days > 0 THEN
SELECT NVL(MAX(sequence_no), 0) + 1
INTO v_billing_sequence
FROM oks_stream_levels_b
WHERE dnz_chr_id = x_chr_id
AND cle_id = x_line_id;
dbms_output.put_line('sequence '||v_billing_sequence);
--Populating the stream line variables
l_strm_level_tbl(v_billing_sequence).sequence_no := v_billing_sequence;
l_strm_level_tbl(v_billing_sequence).dnz_chr_id := x_chr_id;
--l_strm_level_tbl(v_billing_sequence).id := x_line_id;
l_strm_level_tbl(v_billing_sequence).cle_id := x_line_id;
l_strm_level_tbl(v_billing_sequence).uom_code := g_day_uom;
l_strm_level_tbl(v_billing_sequence).uom_per_period := v_bill_days;
l_strm_level_tbl(v_billing_sequence).level_periods := 1;
l_strm_level_tbl(v_billing_sequence).start_date := v_start_date;
l_strm_level_tbl(v_billing_sequence).end_date := v_end_date;
l_strm_level_tbl(v_billing_sequence).invoice_offset_days := NULL;
l_strm_level_tbl(v_billing_sequence).amount := v_net_amount;--v_amt_per_day*v_bill_days;
l_strm_level_tbl(v_billing_sequence).level_amount := v_net_amount;--v_amt_per_day*v_bill_days;
l_strm_level_tbl(v_billing_sequence).lines_detailed_yn := 'Y';
l_strm_level_tbl(v_billing_sequence).due_arr_yn := 'Y';
dbms_output.put_line('Before calling the Bill Sch API for QTR days');
OKS_CONTRACTS_PUB.CREATE_BILL_SCHEDULE ( p_billing_sch=>'E',
p_strm_level_tbl=>l_strm_level_tbl,
p_invoice_rule_id=>v_invoicing_rule_id,
x_return_status=>x_return_status);
dbms_output.put_line('After calling the Bill Sch API for QTR days ' || v_bill_days || ' ' || x_return_status);
IF x_return_status <> 'S' THEN
x_msg_count := 1;
dbms_output.put_line('Day schedule, for quarterly accounting rule, creation error ' || x_msg_data);
--DBMS_TRANSACTION.ROLLBACK_SAVEPOINT('OKS_A');
--RETURN;
END IF;
END IF;
ELSE
--Monthly billing schedule
SELECT FLOOR(MONTHS_BETWEEN( v_end_date,
v_start_date)),
v_end_date - ADD_MONTHS(v_start_date, FLOOR(MONTHS_BETWEEN(v_end_date, v_start_date)))
INTO v_bill_mths,
v_bill_days
FROM dual;
dbms_output.put_line('Calculated the mths and days');
IF v_bill_mths > 0 THEN
SELECT (ADD_MONTHS(v_start_date,FLOOR(MONTHS_BETWEEN(v_end_date, v_start_date))) - v_start_date)*v_amt_per_day
INTO v_amt
FROM dual;
dbms_output.put_line('Calculated the mths amt');
SELECT NVL(MAX(sequence_no), 0) + 1
INTO v_billing_sequence
FROM oks_stream_levels_b
WHERE dnz_chr_id = x_chr_id
AND cle_id = x_line_id;
--Populating the stream line variables
l_strm_level_tbl(v_billing_sequence).sequence_no := v_billing_sequence;
l_strm_level_tbl(v_billing_sequence).dnz_chr_id := x_chr_id;
--l_strm_level_tbl(v_billing_sequence).id := x_line_id;
l_strm_level_tbl(v_billing_sequence).cle_id := x_line_id;
l_strm_level_tbl(v_billing_sequence).uom_code := g_month_uom;
l_strm_level_tbl(v_billing_sequence).uom_per_period := 1;
l_strm_level_tbl(v_billing_sequence).level_periods := v_bill_mths;
l_strm_level_tbl(v_billing_sequence).start_date := v_start_date;
l_strm_level_tbl(v_billing_sequence).end_date := v_end_date;
l_strm_level_tbl(v_billing_sequence).invoice_offset_days := NULL;
l_strm_level_tbl(v_billing_sequence).amount := v_amt/v_bill_mths;
l_strm_level_tbl(v_billing_sequence).level_amount := v_amt/v_bill_mths;
l_strm_level_tbl(v_billing_sequence).lines_detailed_yn := 'Y';
l_strm_level_tbl(v_billing_sequence).due_arr_yn := 'Y';
dbms_output.put_line('Before calling the Bill Sch API for MTHS');
OKS_CONTRACTS_PUB.CREATE_BILL_SCHEDULE ( p_billing_sch=>'E',
p_strm_level_tbl=>l_strm_level_tbl,
p_invoice_rule_id=>v_invoicing_rule_id,
x_return_status=>x_return_status);
dbms_output.put_line('After calling the Bill Sch API for MTHS');
IF x_return_status <> 'S' THEN
x_msg_count := 1;
dbms_output.put_line('Monthly schedule creation error ' || x_msg_data);
--DBMS_TRANSACTION.ROLLBACK_SAVEPOINT('OKS_A');
--RETURN;
END IF;
END IF;
IF v_bill_days > 0 THEN
SELECT NVL(MAX(sequence_no), 0) + 1
INTO v_billing_sequence
FROM oks_stream_levels_b
WHERE dnz_chr_id = x_chr_id
AND cle_id = x_line_id;
--Populating the stream line variables
l_strm_level_tbl(v_billing_sequence).sequence_no := v_billing_sequence;
l_strm_level_tbl(v_billing_sequence).dnz_chr_id := x_chr_id;
--l_strm_level_tbl(v_billing_sequence).id := x_line_id;
l_strm_level_tbl(v_billing_sequence).cle_id := x_line_id;
l_strm_level_tbl(v_billing_sequence).uom_code := g_day_uom;
l_strm_level_tbl(v_billing_sequence).uom_per_period := v_bill_days;
l_strm_level_tbl(v_billing_sequence).level_periods := 1;
l_strm_level_tbl(v_billing_sequence).start_date := v_start_date;
l_strm_level_tbl(v_billing_sequence).end_date := v_end_date;
l_strm_level_tbl(v_billing_sequence).invoice_offset_days := NULL;
l_strm_level_tbl(v_billing_sequence).amount := v_amt_per_day*v_bill_days;
l_strm_level_tbl(v_billing_sequence).level_amount := v_amt_per_day*v_bill_days;
l_strm_level_tbl(v_billing_sequence).lines_detailed_yn := 'Y';
l_strm_level_tbl(v_billing_sequence).due_arr_yn := 'Y';
dbms_output.put_line('Before calling the Bill Sch API for MTH days');
OKS_CONTRACTS_PUB.CREATE_BILL_SCHEDULE ( p_billing_sch=>'E',
p_strm_level_tbl=>l_strm_level_tbl,
p_invoice_rule_id=>v_invoicing_rule_id,
x_return_status=>x_return_status);
dbms_output.put_line('After calling the Bill Sch API for MTH days');
IF x_return_status <> 'S' THEN
x_msg_count := 1;
dbms_output.put_line('Day schedule, for monthly accounting rule, creation error ' || x_msg_data);
--DBMS_TRANSACTION.ROLLBACK_SAVEPOINT('OKS_A');
--RETURN;
END IF;
END IF;
END IF;
COMMIT;
EXCEPTION
when others then
dbms_output.put_line('Error ' || sqlerrm);
END;
Thanks,
Yash.Hi There,
I have a similar requirement to create rental service contracts and create billing schedules.
Can you please pass on your functional docs so that i can refer to them.
Thanks,
Raidu -
Request creation error for mitigation control workflow
Dear Expert,
I had activiate the workflow from RAR to CUP on Mitigated User assignment, I had completed following customizing:
1)RAR->configaration->Workflow
2)CUP->configaration->initiator, stage, path.
but when I created mitigated user assignments in RAR, after click "Submit", error popup: "Request creation error"
can some one help?
thanks!Dear,
the log is below:
ERROR service 'SAPGW00' unknown
TIME Thu May 20 13:33:16 2010
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -3
MODULE niuxi.c
LINE 1732
DETAIL NiPGetServByName2: service 'SAPGW00' not found
SYSTEM CALL getservbyname_r
COUNTER 375
May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server YYY:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
Could not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
ERROR service 'SAPGW00' unknown
TIME Thu May 20 13:33:16 2010
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -3
MODULE niuxi.c
LINE 1732
DETAIL NiPGetServByName2: service 'SAPGW00' not found
SYSTEM CALL getservbyname_r
COUNTER 375
May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server YYY:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
Could not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
ERROR service 'SAPGW00' unknown
TIME Thu May 20 13:33:16 2010
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -3
MODULE niuxi.c
LINE 1732
DETAIL NiPGetServByName2: service 'SAPGW00' not found
SYSTEM CALL getservbyname_r
COUNTER 375
May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server YYY:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
Could not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
ERROR service 'SAPGW00' unknown
TIME Thu May 20 13:33:16 2010
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -3
MODULE niuxi.c
LINE 1732
DETAIL NiPGetServByName2: service 'SAPGW00' not found
SYSTEM CALL getservbyname_r
COUNTER 375
May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server YYY:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
Could not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
ERROR service 'SAPGW00' unknown
TIME Thu May 20 13:33:16 2010
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -3
MODULE niuxi.c
LINE 1732
DETAIL NiPGetServByName2: service 'SAPGW00' not found
SYSTEM CALL getservbyname_r
COUNTER 375
May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server YYY:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
Could not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
ERROR service 'SAPGW00' unknown
TIME Thu May 20 13:33:16 2010
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -3
MODULE niuxi.c
LINE 1732
DETAIL NiPGetServByName2: service 'SAPGW00' not found
SYSTEM CALL getservbyname_r
COUNTER 375
May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server YYY:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
Could not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
ERROR service 'SAPGW00' unknown
TIME Thu May 20 13:33:16 2010
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -3
MODULE niuxi.c
LINE 1732
DETAIL NiPGetServByName2: service 'SAPGW00' not found
SYSTEM CALL getservbyname_r
COUNTER 375
May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server YYY:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
Could not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
ERROR service 'SAPGW00' unknown
TIME Thu May 20 13:33:16 2010
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -3
MODULE niuxi.c
LINE 1732
DETAIL NiPGetServByName2: service 'SAPGW00' not found
SYSTEM CALL getservbyname_r
COUNTER 375
May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server YYY:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
Could not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
ERROR service 'SAPGW00' unknown
TIME Thu May 20 13:33:16 2010
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -3
MODULE niuxi.c
LINE 1732
DETAIL NiPGetServByName2: service 'SAPGW00' not found
SYSTEM CALL getservbyname_r
COUNTER 375
May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server YYY:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
Could not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
ERROR service 'SAPGW00' unknown
TIME Thu May 20 13:33:16 2010
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -3
MODULE niuxi.c
LINE 1732
DETAIL NiPGetServByName2: service 'SAPGW00' not found
SYSTEM CALL getservbyname_r
COUNTER 375
May 20, 2010 2:10:50 PM com.virsa.cc.workflow.bo.WorkflowBO submit
INFO: END POOINT URL: http://9.186.143.129:50100/AEWFRequestSubmissionService_5_2/Config1?style=document
May 20, 2010 2:10:50 PM com.virsa.cc.workflow.bo.WorkflowBO submit
INFO: before submit:
May 20, 2010 2:10:50 PM com.virsa.cc.workflow.bo.WorkflowBO submit
INFO: wftype: MITIOBJ reqid: GRC01
May 20, 2010 2:10:50 PM com.virsa.cc.rulearchitect.dao.dto.MitObjDTO getObjContext
FINEST: validfrom: 2010-05-20 validto: 2011-05-20
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Data Type: String
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Descripton: MITREFNO
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Name: MOMITREFNO
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Value: CT01
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Data Type: String
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Descripton: RISKID
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Name: MORISKID
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Value: ZC02
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Data Type: String
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Descripton: LANG
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Name: LANG
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Value: EN
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Data Type: String
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Descripton: MONITORID
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Name: MONITORID
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Value: GRC01
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Data Type: Integer
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Descripton: STATUS
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Name: MOSTATUS
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Value: 0
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Data Type: DATE
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Descripton: VALIDFROM
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Name: VALIDFROM
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Value: 05/20/2010
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Data Type: DATE
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Descripton: VALIDTO
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Name: VALIDTO
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Value: 05/20/2011
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Data Type: String
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Descripton: BU ID
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Name: BUID
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Value: null
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Data Type: String
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Descripton: Approver ID
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Name: MOAPPROVERID
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Value: null
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Data Type: String
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Descripton: OBJTYPE
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Name: OBJTYPE
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Value: U
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Data Type: String
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Descripton: OBJID
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Name: OBJID
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Value: 207471
May 20, 2010 2:10:50 PM com.virsa.cc.workflow.bo.WorkflowBO submit
INFO: Return code: 2010 Message: com.virsa.ae.core.ObjectNotFoundException: Invalid Priority Value : MO_HIGH workflow id: null Status: null
May 20, 2010 2:10:50 PM com.virsa.cc.workflow.bo.WorkflowBO submit
WARNING: 2010: null
Maybe you are looking for
-
What are the order of interactive objects
If you have two interactive objects on top of each other what are the rules regarding which shows up on top. for instance if you have a MSO slideshow and you try to put a button on top it will disappear behind the MSO on the iPad, I can work round th
-
Can't Install Boot Camp from Snow Leopard DVD in Windows 7
I have an iMac "Core 2 Duo" 3.06 24-inc (08) running 10.6.2 and Windows 7. I was able to successfully use the Boot Camp Assistant to partition and install Windows 7 on my iMac. After the installation, I was able to download updates from Windows Updat
-
IDoc to csv file with required fields
All, I have a source IDoc going to XI. For example it contains source fields SF1 (required), SF2 (required), SF3(optional) and SF4(optional). I want to produce a target file using file content conversion. I want to produce target fields TF1(require
-
Apply validations on internal table fields before updating table
I have to upload data from a CSV file to R3 ztable, but before that I have to apply diffrent validations to check if fileds does not contaion invalid characters .... eg for a currency field I want to check if user has entered value in decimail format
-
Confused about Acrobat 9 and CS5
Hi... I recently upgraded from CS4 (Design Premium) to CS5. No problem. However, I am not sure what to do about the separate Acrobat 9 installation disk. In the CS5 instructions, it says that old versions of Acrobat have to be removed before installi