Error in Partner Link creation

Hi,
I tried to call an OSB project from a bpel process and i created a partner link for that . when i try to deploy that BPEL process i am getting the following error,
Error during deployment: oracle.fabric.common.FabricException: Malformed WS Binding port. Missing # between namespace URI and service/port names
Please help me to solve this issue.
Thanks

Hi Anuj,
thanks for yr guidance. now i am able to deploy that bpel process, but when i give inputs in test console i am getting the following error.
An exception occured while invoking the webservice operation. Please see logs for more details.
oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: oracle.fabric.common.FabricInvocationException: Unable to access the following endpoint(s): http://crmsbldeva64.st.sk/eai_enu/start.swe?SWEExtSource=SecureWebService&SWEExtCmd=Execute&WSSOAP=1
Please help me to solve this issue.
thanks in advance

Similar Messages

Receiving error during partner link invoke

Hi Guys,
I am trying to call a partner link using Bpel 10.1.3.3 in a weblogic app server and I am receiving the following error on bpel console:
<remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>exception on JaxRpc invoke: unexpected null</summary>
Any clue what can be happening ?
Tks in advance
Edited by: user11222809 on 17/08/2009 11:21

Tks for ur reply.
Is a syncronous process and there is no patch applied in this case.
We are trying to perform a simple business scenario, is a invoke to a java webservices, no adapter service.
Follows below the whole message (sorry some of the elements were wrote in portuguese):
<messages><input><AutenticarUsuarioExternoFSGue_autenticarUsuarioExterno_InputVariable><part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="request"><AutenticarUsuarioExternoRequest xmlns="http://www.claro.com.br/EBS/Claro/v1">
<usuario>
<usuario-id xmlns:ns2="http://www.claro.com.br/EBO/Claro/v1" xmlns="http://www.claro.com.br/EBO/Claro/v1">1191680138</usuario-id>
<nome xmlns="http://www.claro.com.br/EBO/Claro/v1"/>
<apelido xmlns="http://www.claro.com.br/EBO/Claro/v1"/>
<tipo xmlns="http://www.claro.com.br/EBO/Claro/v1"/>
<sub-tipo xmlns="http://www.claro.com.br/EBO/Claro/v1"/>
<data-efetivacao xmlns="http://www.claro.com.br/EBO/Claro/v1"/>
<data-expiracao xmlns="http://www.claro.com.br/EBO/Claro/v1"/>
<data-inicio-bloqueio xmlns="http://www.claro.com.br/EBO/Claro/v1"/>
<data-termino-bloqueio xmlns="http://www.claro.com.br/EBO/Claro/v1"/>
<situacao xmlns="http://www.claro.com.br/EBO/Claro/v1"/>
<situacao-senha xmlns="http://www.claro.com.br/EBO/Claro/v1"/>
<senha xmlns:ns3="http://www.claro.com.br/EBO/Claro/v1" xmlns="http://www.claro.com.br/EBO/Claro/v1">121382</senha>
<data-expiracao-senha xmlns="http://www.claro.com.br/EBO/Claro/v1"/>
<data-ultima-alteracao-senha xmlns="http://www.claro.com.br/EBO/Claro/v1"/>
<dados-cadastrais-pf xmlns="http://www.claro.com.br/EBO/Claro/v1"/>
<dados-cadastrais-pj xmlns="http://www.claro.com.br/EBO/Claro/v1"/>
<perfis xmlns="http://www.claro.com.br/EBO/Claro/v1"/>
<localidades xmlns="http://www.claro.com.br/EBO/Claro/v1"/>
<setor-atividade xmlns="http://www.claro.com.br/EBO/Claro/v1"/>
<grupo-vendedor xmlns="http://www.claro.com.br/EBO/Claro/v1"/>
<cargo xmlns="http://www.claro.com.br/EBO/Claro/v1"/>
<estado xmlns="http://www.claro.com.br/EBO/Claro/v1"/>
<resumo-acesso xmlns="http://www.claro.com.br/EBO/Claro/v1"/>
<historico-autenticacao xmlns="http://www.claro.com.br/EBO/Claro/v1"/>
</usuario>
<meta-informacao>
<transacao-id xmlns="http://www.claro.com.br/EBO/Claro/v1"/>
<codigo-aplicacao-origem xmlns:ns5="http://www.claro.com.br/EBO/Claro/v1" xmlns="http://www.claro.com.br/EBO/Claro/v1">?</codigo-aplicacao-origem>
<codigo-operacao-origem xmlns:ns6="http://www.claro.com.br/EBO/Claro/v1" xmlns="http://www.claro.com.br/EBO/Claro/v1">?</codigo-operacao-origem>
<correlacao-id-origem xmlns:ns7="http://www.claro.com.br/EBO/Claro/v1" xmlns="http://www.claro.com.br/EBO/Claro/v1">?</correlacao-id-origem>
<endereco-aplicacao-origem xmlns:ns8="http://www.claro.com.br/EBO/Claro/v1" xmlns="http://www.claro.com.br/EBO/Claro/v1">?</endereco-aplicacao-origem>
<usuario-id-origem xmlns:ns9="http://www.claro.com.br/EBO/Claro/v1" xmlns="http://www.claro.com.br/EBO/Claro/v1">?</usuario-id-origem>
<data-hora-origem xmlns="http://www.claro.com.br/EBO/Claro/v1"/>
<canal-id-origem xmlns:ns11="http://www.claro.com.br/EBO/Claro/v1" xmlns="http://www.claro.com.br/EBO/Claro/v1">?</canal-id-origem>
</meta-informacao>
</AutenticarUsuarioExternoRequest>
</part></AutenticarUsuarioExternoFSGue_autenticarUsuarioExterno_InputVariable></input><fault><remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>exception on JaxRpc invoke: unexpected null</summary>
</part></remoteFault></fault></messages>
Thanks a million !

Getting an error in the "Partner Link" when specifying an https-base wsdl

Hi friends,
this is Hari. I'm getting an error in the "Create Partner Link" dialogue when specifying an https-based wsdl url. The non-ssl wsdl url works fine, but I need it to work for ssl (https). The specific errror reads:
Error:Failed to read wsdl file at "https://serverstuff/webservice.cfc?wsdl", caused by: javax.net.ssl.SSLHandshakeException. :sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
i need to invoke secure service(https).what should i do for taht?
Regards,
hari

http://orasoa.blogspot.com/2007/09/compile-error-bpel-against-ssl.html
marc

Create Partner Link Error

Hi I was trying to add partner link to bpel process. but getting error.
1) Drag the partner link from services to Bpel process services area
2) WSDL Setting. click the service explorer icon. Then Select Local Bpel Services=>ServerConnection1=>processes=>default=>HelloWorld then select OK
3) Getting ERROR Loading wsdl file. click here to verify the details
ERROR Failed to load WSDL file.
http://localmachine.com:9700/orabpel/default/HelloWorld/HelloWorld?wsdl
caused by java.net.connectexception connection timed out.
however when try to load the http://localmachine.com:9700/orabpel/default/HelloWorld/HelloWorld?wsdl this parth in the internet explorer it is working file.
Appreciate your help on this.
Thanks
Vel

Hi',
Is your "Use HTTP Proxy Server" unchecked inside Tools>Preferences>Web Browser and Proxy.
-Yatan

BPEL - SOAP must understand error - Partner Link Reply Contains WSSE in Soa

Hello,
I'm trying to call a WS-Secured partner link from a BPEL process. The SOAP request looks perfect, however the partner link's reply contains a WSSE security element in the SOAP header. Is there a way to configure the BPEL process to expect this and not throw a 'SOAP must understand error'. Both Request and reply SOAP envelopes are below.
Any help would be much appreciated - thanks.
Request:
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><env:Header><wsse:Security xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"><wsse:UsernameToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"><wsse:Username>username</wsse:Username><wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">password</wsse:Password></wsse:UsernameToken></wsse:Security></env:Header><env:Body>soapBody</env:Body></env:Envelope>
Response:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns0="http://xmlns.domain.com/service/soa/ServiceEntitlementWS" xmlns:ns1="http://xmlns.domain.com/services" xmlns:ns2="http://xmlns.domain.com/service/contract" xmlns:ns3="http://xmlns.ni.com/support/customer/serviceLevel" xmlns:ns4="http://xmlns.ni.com/support/customer/linkageSet"><env:Header> *<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" env:mustUnderstand="1"/>* </env:Header><env:Body>soapBody</env:Body></env:Envelope>
Edited by: user639053 on Oct 6, 2009 2:33 PM

Without attaching policy can't I execute?No. You have to attach policy. If none of the pre-seeded policies fulfill your requirement then you may always create your won custom policy. Please refer -
http://technology.amis.nl/blog/11138/owsm-custom-policies-still-some-sharp-edges-so-beware-dont-cut-yourself
http://ws-security.blogspot.com/2010/01/howto-owsm-11g-creating-custom-policy.html
Regards,
Anuj

Error invoking db partner link

Hello guys;
I write a wsdl to write in a database with bpel DBAdapter.
When I write wsdl location in partner link wizard I have this error:
Required white space was missing. Context: CatapultDBLog.wsdl
Thank you
Andrea

All value was inserted as null.
My input variable in bpel console audit has the right values, but they aren't passed to the db adapter.
I write my .xml and .wsdl of db adapter whithout toplink software and I think to have commit some error, but I don't found where...
Internal Exception: java.sql.SQLException: ORA-01400: cannot insert NULL into ("EBILLING"."TAB_BPEL_TEST"."ID_THOR")
This is the complete error from bpel pm server:
Error Code: 1400
<2004-11-22 09:18:49,599> <INFO> <default.collaxa.cube.ws> <Database Adapter::Outbound> <oracle.tip.adapter.db.TopLinkLogger log> rollback transaction
<2004-11-22 09:18:49,601> <INFO> <default.collaxa.cube.ws> <Database Adapter::Outbound> <oracle.tip.adapter.db.TopLinkLogger log> client released
<2004-11-22 09:18:49,602> <ERROR> <default.collaxa.cube.ws> <AdapterFramework::Outbound> http://orcldemo.localdomain:9700/orabpel/default/ProvaLogDB/CatapultDBLog.wsdl[CatapultDBLogManager::insert(null)] Could not invoke 'insert' due to: Exception [PCBPEL-DB-11616] DBWriteInteractionSpec execute failed. Descriptor name: [masterdetail.CatapultDBLog].
<2004-11-22 09:18:49,607> <ERROR> <default.collaxa.cube.ws> <AdapterFramework::Outbound> oracle.tip.adapter.db.exceptions.DBResourceException: Exception [PCBPEL-DB-11616] DBWriteInteractionSpec execute failed. Descriptor name: [masterdetail.CatapultDBLog].
at oracle.tip.adapter.db.exceptions.DBResourceException.outboundWriteException(DBResourceException.java:412)
at oracle.tip.adapter.db.DBInteraction.executeOutboundWrite(DBInteraction.java:399)
at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:133)
at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:395)
at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:356)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:288)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:134)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:541)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:284)
at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:178)
at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3438)
at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1818)
at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:85)
at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:138)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5522)
at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1221)
at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:480)
at com.collaxa.cube.engine.bean.DeliveryBean.handleInvoke(DeliveryBean.java:307)
at IDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(IDeliveryLocalBean_StatelessSessionBeanWrapper16.java:1791)
at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:36)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:62)
at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:72)
at com.collaxa.cube.engine.bean.WorkerBean.onMessage(WorkerBean.java:86)
at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:745)
at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:917)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
at java.lang.Thread.run(Thread.java:534)
Caused by: Exception [TOPLINK-4002] (OracleAS TopLink - 10g (9.0.4.4) (Build 040705)): oracle.toplink.exceptions.DatabaseException
Exception Description: java.sql.SQLException: ORA-01400: cannot insert NULL into ("EBILLING"."TAB_BPEL_TEST"."ID_THOR")
Internal Exception: java.sql.SQLException: ORA-01400: cannot insert NULL into ("EBILLING"."TAB_BPEL_TEST"."ID_THOR")
Error Code: 1400
at oracle.toplink.exceptions.DatabaseException.sqlException(DatabaseException.java:227)
at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:732)
at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeNoSelect(DatabaseAccessor.java:780)
at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:641)
at oracle.toplink.publicinterface.Session.executeCall(Session.java:793)
at oracle.toplink.internal.queryframework.CallQueryMechanism.executeCall(CallQueryMechanism.java:134)
at oracle.toplink.internal.queryframework.CallQueryMechanism.executeCall(CallQueryMechanism.java:115)
at oracle.toplink.internal.queryframework.CallQueryMechanism.insertObject(CallQueryMechanism.java:266)
at oracle.toplink.internal.queryframework.StatementQueryMechanism.insertObject(StatementQueryMechanism.java:171)
at oracle.toplink.internal.queryframework.StatementQueryMechanism.insertObject(StatementQueryMechanism.java:188)
at oracle.toplink.internal.queryframework.DatabaseQueryMechanism.insertObjectForWrite(DatabaseQueryMechanism.java:433)
at oracle.toplink.queryframework.InsertObjectQuery.executeCommit(InsertObjectQuery.java:45)
at oracle.toplink.internal.queryframework.DatabaseQueryMechanism.performUserDefinedWrite(DatabaseQueryMechanism.java:596)
at oracle.toplink.internal.queryframework.DatabaseQueryMechanism.performUserDefinedInsert(DatabaseQueryMechanism.java:563)
at oracle.toplink.internal.queryframework.DatabaseQueryMechanism.insertObjectForWrite(DatabaseQueryMechanism.java:376)
at oracle.toplink.queryframework.InsertObjectQuery.executeCommit(InsertObjectQuery.java:45)
at oracle.toplink.internal.queryframework.DatabaseQueryMechanism.executeWrite(DatabaseQueryMechanism.java:209)
at oracle.toplink.queryframework.WriteObjectQuery.execute(WriteObjectQuery.java:53)
at oracle.toplink.queryframework.DatabaseQuery.execute(DatabaseQuery.java:493)
at oracle.toplink.publicinterface.Session.internalExecuteQuery(Session.java:1958)
at oracle.toplink.threetier.ClientSession.internalExecuteQuery(ClientSession.java:390)
at oracle.toplink.publicinterface.Session.executeQuery(Session.java:1086)
at oracle.toplink.publicinterface.Session.executeQuery(Session.java:1038)
at oracle.tip.adapter.db.DBInteraction.executeOutboundWrite(DBInteraction.java:317)
... 27 more
Caused by: java.sql.SQLException: ORA-01400: cannot insert NULL into ("EBILLING"."TAB_BPEL_TEST"."ID_THOR")
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:137)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:304)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:271)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:625)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:181)
at oracle.jdbc.driver.T4CPreparedStatement.execute_for_rows(T4CPreparedStatement.java:784)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1095)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:2901)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:2973)
at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:726)
... 49 more
Local Exception Stack:
Exception [TOPLINK-4002] (OracleAS TopLink - 10g (9.0.4.4) (Build 040705)): oracle.toplink.exceptions.DatabaseException
Exception Description: java.sql.SQLException: ORA-01400: cannot insert NULL into ("EBILLING"."TAB_BPEL_TEST"."ID_THOR")
Internal Exception: java.sql.SQLException: ORA-01400: cannot insert NULL into ("EBILLING"."TAB_BPEL_TEST"."ID_THOR")
Error Code: 1400
at oracle.toplink.exceptions.DatabaseException.sqlException(DatabaseException.java:227)
at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:732)
at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeNoSelect(DatabaseAccessor.java:780)
at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:641)
at oracle.toplink.publicinterface.Session.executeCall(Session.java:793)
at oracle.toplink.internal.queryframework.CallQueryMechanism.executeCall(CallQueryMechanism.java:134)
at oracle.toplink.internal.queryframework.CallQueryMechanism.executeCall(CallQueryMechanism.java:115)
at oracle.toplink.internal.queryframework.CallQueryMechanism.insertObject(CallQueryMechanism.java:266)
at oracle.toplink.internal.queryframework.StatementQueryMechanism.insertObject(StatementQueryMechanism.java:171)
at oracle.toplink.internal.queryframework.StatementQueryMechanism.insertObject(StatementQueryMechanism.java:188)
at oracle.toplink.internal.queryframework.DatabaseQueryMechanism.insertObjectForWrite(DatabaseQueryMechanism.java:433)
at oracle.toplink.queryframework.InsertObjectQuery.executeCommit(InsertObjectQuery.java:45)
at oracle.toplink.internal.queryframework.DatabaseQueryMechanism.performUserDefinedWrite(DatabaseQueryMechanism.java:596)
at oracle.toplink.internal.queryframework.DatabaseQueryMechanism.performUserDefinedInsert(DatabaseQueryMechanism.java:563)
at oracle.toplink.internal.queryframework.DatabaseQueryMechanism.insertObjectForWrite(DatabaseQueryMechanism.java:376)
at oracle.toplink.queryframework.InsertObjectQuery.executeCommit(InsertObjectQuery.java:45)
at oracle.toplink.internal.queryframework.DatabaseQueryMechanism.executeWrite(DatabaseQueryMechanism.java:209)
at oracle.toplink.queryframework.WriteObjectQuery.execute(WriteObjectQuery.java:53)
at oracle.toplink.queryframework.DatabaseQuery.execute(DatabaseQuery.java:493)
at oracle.toplink.publicinterface.Session.internalExecuteQuery(Session.java:1958)
at oracle.toplink.threetier.ClientSession.internalExecuteQuery(ClientSession.java:390)
at oracle.toplink.publicinterface.Session.executeQuery(Session.java:1086)
at oracle.toplink.publicinterface.Session.executeQuery(Session.java:1038)
at oracle.tip.adapter.db.DBInteraction.executeOutboundWrite(DBInteraction.java:317)
at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:133)
at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:395)
at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:356)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:288)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:134)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:541)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:284)
at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:178)
at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3438)
at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1818)
at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:85)
at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:138)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5522)
at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1221)
at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:480)
at com.collaxa.cube.engine.bean.DeliveryBean.handleInvoke(DeliveryBean.java:307)
at IDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(IDeliveryLocalBean_StatelessSessionBeanWrapper16.java:1791)
at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:36)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:62)
at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:72)
at com.collaxa.cube.engine.bean.WorkerBean.onMessage(WorkerBean.java:86)
at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:745)
at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:917)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.sql.SQLException: ORA-01400: cannot insert NULL into ("EBILLING"."TAB_BPEL_TEST"."ID_THOR")
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:137)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:304)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:271)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:625)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:181)
at oracle.jdbc.driver.T4CPreparedStatement.execute_for_rows(T4CPreparedStatement.java:784)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1095)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:2901)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:2973)
at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:726)
... 49 more
java.sql.SQLException: ORA-01400: cannot insert NULL into ("EBILLING"."TAB_BPEL_TEST"."ID_THOR")
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:137)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:304)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:271)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:625)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:181)
at oracle.jdbc.driver.T4CPreparedStatement.execute_for_rows(T4CPreparedStatement.java:784)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1095)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:2901)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:2973)
at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:726)
at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeNoSelect(DatabaseAccessor.java:780)
at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:641)
at oracle.toplink.publicinterface.Session.executeCall(Session.java:793)
at oracle.toplink.internal.queryframework.CallQueryMechanism.executeCall(CallQueryMechanism.java:134)
at oracle.toplink.internal.queryframework.CallQueryMechanism.executeCall(CallQueryMechanism.java:115)
at oracle.toplink.internal.queryframework.CallQueryMechanism.insertObject(CallQueryMechanism.java:266)
at oracle.toplink.internal.queryframework.StatementQueryMechanism.insertObject(StatementQueryMechanism.java:171)
at oracle.toplink.internal.queryframework.StatementQueryMechanism.insertObject(StatementQueryMechanism.java:188)
at oracle.toplink.internal.queryframework.DatabaseQueryMechanism.insertObjectForWrite(DatabaseQueryMechanism.java:433)
at oracle.toplink.queryframework.InsertObjectQuery.executeCommit(InsertObjectQuery.java:45)
at oracle.toplink.internal.queryframework.DatabaseQueryMechanism.performUserDefinedWrite(DatabaseQueryMechanism.java:596)
at oracle.toplink.internal.queryframework.DatabaseQueryMechanism.performUserDefinedInsert(DatabaseQueryMechanism.java:563)
at oracle.toplink.internal.queryframework.DatabaseQueryMechanism.insertObjectForWrite(DatabaseQueryMechanism.java:376)
at oracle.toplink.queryframework.InsertObjectQuery.executeCommit(InsertObjectQuery.java:45)
at oracle.toplink.internal.queryframework.DatabaseQueryMechanism.executeWrite(DatabaseQueryMechanism.java:209)
at oracle.toplink.queryframework.WriteObjectQuery.execute(WriteObjectQuery.java:53)
at oracle.toplink.queryframework.DatabaseQuery.execute(DatabaseQuery.java:493)
at oracle.toplink.publicinterface.Session.internalExecuteQuery(Session.java:1958)
at oracle.toplink.threetier.ClientSession.internalExecuteQuery(ClientSession.java:390)
at oracle.toplink.publicinterface.Session.executeQuery(Session.java:1086)
at oracle.toplink.publicinterface.Session.executeQuery(Session.java:1038)
at oracle.tip.adapter.db.DBInteraction.executeOutboundWrite(DBInteraction.java:317)
at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:133)
at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:395)
at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:356)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:288)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:134)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:541)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:284)
at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:178)
at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3438)
at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1818)
at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:85)
at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:138)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5522)
at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1221)
at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:480)
at com.collaxa.cube.engine.bean.DeliveryBean.handleInvoke(DeliveryBean.java:307)
at IDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(IDeliveryLocalBean_StatelessSessionBeanWrapper16.java:1791)
at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:36)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:62)
at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:72)
at com.collaxa.cube.engine.bean.WorkerBean.onMessage(WorkerBean.java:86)
at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:745)
at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:917)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
at java.lang.Thread.run(Thread.java:534)
Thank you.

Error deploying composite projects with partner links in abstract wsdl

Error while deployment of PartnerLinkCompositeError. The two composites have the same wsdl files, but PartnerLinkCompositeError composite projects has a perter link inside the wsdl.
<partnerLinkType name="execute_ptt"
xmlns="http://schemas.xmlsoap.org/ws/2003/05/partner-link/">
<role name="execute_pttProvider">
<portType name="tns:execute_ptt"/>
</role>
</partnerLinkType>
The error during deployment
[04:13:04 PM] Error deploying archive sca_PartnerLinkCompositeError_rev1.0.jar to partition "default" on server soa_server1 [http://158.166.229.41:8001]
[04:13:04 PM] HTTP error code returned [500]
[04:13:04 PM] Error message from server:
There was an error deploying the composite on soa_server1: Deployment Failed: Unable to find a WSDL that has a definition for service {http://xmlns.oracle.com/EBS/PartnerLinkCompositeError/Mediator1}Mediator1_ep and port execute_pt. Please make sure that the port attribute for the binding defined in the composite file is correct by checking the namespace, service name, and port name. In addition, check that the WSDL associated with the binding namespace is imported and currently reachable (check the import nodes at the top of the composite file). Finally, validate the HTTP proxy settings for the server..
[04:13:04 PM] Check server log for more details.
[04:13:04 PM] Error deploying archive sca_PartnerLinkCompositeError_rev1.0.jar to partition "default" on server soa_server1 [http://158.166.229.41:8001]
[04:13:04 PM] #### Deployment incomplete. ####
[04:13:04 PM] Error deploying archive file:/D:/workspace/NIF2/PartnerLinkCompositeError/deploy/sca_PartnerLinkCompositeError_rev1.0.jar
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
What can be the cause for this error?
Projects for download
http://www.4shared.com/zip/w5R5zp1G/PartnerLinkCompositeError.html
http://www.4shared.com/zip/EM7butNF/PartnerLinkComposite.html

During WSDL design for composite projects like BPM or SOA using JDeveloper WSDL designer or by hand, BE sure that the partner link namespace is in the root of the wsdl definition.
<?xml version= '1.0' encoding= 'UTF-8' ?>
<wsdl:definitions name="Service"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/">
<wsdl:portType name="execute_ptt">
</wsdl:portType>
<wsdl:portType name="callback_ptt">
</wsdl:portType>
<plnk:partnerLinkType name="execute_ptt">
<plnk:role name="execute_pttProvider">
<plnk:portType name="tns:execute_ptt"/>
</plnk:role>
</plnk:partnerLinkType>
</wsdl:definitions>
Example:
WSDL that will deploy
<?xml version= '1.0' encoding= 'UTF-8' ?>
<wsdl:definitions name="Mediator1"
targetNamespace="http://xmlns.oracle.com/EBS/PartnerLinkCompositeError/Mediator1"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:inp1="http://xmlns.oracle.com/singleString"
xmlns:tns="http://xmlns.oracle.com/EBS/PartnerLinkCompositeError/Mediator1"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/">
<wsdl:types>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://xmlns.oracle.com/singleString"
schemaLocation="xsd/singleString.xsd"/>
</xsd:schema>
</wsdl:types>
<wsdl:message name="requestMessage">
<wsdl:part name="request" element="inp1:singleString"/>
</wsdl:message>
<wsdl:message name="callbackMessage">
<wsdl:part name="callback" element="inp1:singleString"/>
</wsdl:message>
<wsdl:portType name="execute_ptt">
<wsdl:operation name="execute">
<wsdl:input message="tns:requestMessage"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:portType name="callback_ptt">
<wsdl:operation name="callback">
<wsdl:input message="tns:callbackMessage"/>
</wsdl:operation>
</wsdl:portType>
<plnk:partnerLinkType name="execute_ptt">
<plnk:role name="execute_pttProvider">
<plnk:portType name="tns:execute_ptt"/>
</plnk:role>
</plnk:partnerLinkType>
</wsdl:definitions>
Seems that Oracle JDeveloper WSDL designer has contribution to this issue since when trying to add a partner link from
http://www.4shared.com/photo/7D4D4Elx/wsdl_designer.html?
it creates the wsdl with the following configuration.
http://www.4shared.com/photo/zb907pXN/wsdl_designer_2.html?
Maybe will be fixed in next versions of JDeveloper. Until then, use this work suggested around.

Getting compilation error while invoking an existing partner link.

Hi,
I am very new to BPEL.This may be a very basic issue..
Found few links on the forum related to this..but didn't understand how people solved their problems..
Created a sample project to add two numbers and return the result.[Ex : 2+ 3 = 5]
Trying to invoke that service by adding it as a partner link in other project.
Getting compile time error immediately after adding it..
Error:
[Error ORABPEL-10902]: compilation failed
[Description]: in "bpel.xml", XML parsing failed because "undefined part element.
In WSDL at "http://PC-XYZ-IN:8888/orabpel/default/BPELProcess/BPELProcess?wsdl", message part element "{http://xmlns.oracle.com/BPELProcess}BPELProcessProcessResponse" is not defined in any of the schemas.
Please make sure the spelling of the element QName is correct and the WSDL import is complete.
[Potential fix]: n/a.
(ii) how can i pass two variables to calling service using invoke option.
Since in invoke option i could see only one input variable is allowed.
Thanks in advance for the help.

the wsdl is refered correctly,I used the wizard for this..
http://PC-MSIDDHAR-IN:8888/orabpel/default/BPELProcess/BPELProcess?wsdl
For second part of the question.
Caller ----> Invoke Code ---> Partner Link for Service
Partner Link for Service expects 2 variables...
Caller i have added 2 variables as u suggested already ...
The question is how can i assign caller variables to partner link variables..[If they are more than 1)
Thx
Message was edited by:
msiddhar
Message was edited by:
msiddhar

Getting error: (301)Moved Permanently when invoking partner link

Hello,
I've set up and tested a web service that will execute a command on a host. I then built a BPEL process that invokes this web service as a Partner Link. However, I always received the following error when running the BPEL process:
Invoke_Host (faulted)
[2005/11/04 14:17:57] "{http://schemas.oracle.com/bpel/extension}remoteFault" has been thrown. less
<remoteFault xmlns="http://schemas.oracle.com/bpel/extension">
<part name="code">
<code>HTTP</code>
</part>
<part name="summary">
<summary>when invoking endpointAddress 'http://web398.xxx.com:7780/itas/ws/host', (301)Moved Permanently</summary>
</part>
<part name="detail">
<detail>AxisFault faultCode: {http://xml.apache.org/axis/}HTTP faultSubcode: faultString: (301)Moved Permanently faultActor: faultNode: faultDetail: {}:return code: 301 {http://xml.apache.org/axis/}HttpErrorCode:301</detail>
</part>
</remoteFault>
Has anybody seen this error message? Any suggestions for finding out what's going on here?
Thanks

This is a standard HTTP error code, I am not sure what it means exactly, but maybe a network specialist can make sense of it.
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
10.3.2 301 Moved Permanently
The requested resource has been assigned a new permanent URI and any future references to this resource SHOULD use one of the returned URIs. Clients with link editing capabilities ought to automatically re-link references to the Request-URI to one or more of the new references returned by the server, where possible. This response is cacheable unless indicated otherwise.
The new permanent URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).
If the 301 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.
Note: When automatically redirecting a POST request after
receiving a 301 status code, some existing HTTP/1.0 user agents
will erroneously change it into a GET request.

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

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

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

No Fault When Dynamic Partner Link Is Down?

Hello,
I have an async process that establishes a dynamic partner link based on runtime data. I understand how to fire off to a dynamic partner link, however, I ran into a problem while testing a scenario where the partner link's endpoint is down.
In situations where the dynamic endpoint is up, my process calls it without any problems. However, when testing what happens if the dynamic endpoint is not available, I expected the process to throw a fault that I can catch. What I find is that an exception is raised in the logs (see below), but the calling process does not throw a fault. The process also continues on as if the call were successful?
Is there something that I can do to ensure that faults are raised in cases where dynamic partner links are down?
<2008-06-07 21:42:13,413> <DEBUG> <default.collaxa.cube.ws> <WSIFInvocationHandler::invoke> invoke failed
org.collaxa.thirdparty.apache.wsif.WSIFException: when invoking locally the endpoint 'http://alcalba2-lap:8889/orabpel/default/CDS_DNS_process/1.0', ; nested exception is:
ORABPEL-00000
Exception not handled by the Collaxa Cube system.
An unhandled exception has been thrown in the Collaxa Cube system. The exception reported is: "ORABPEL-02178
Process not found.
The BPEL process "CDS_DNS_process", revision "1.0" has not been loaded. Either the process was not initialized properly or the process has been disabled.
Please consult your administrator regarding this error. The application server logs may provide more information regarding this error.
v10.1.3.3.0
Thanks!

There is a catch all block. I have no fault policies or fault binding set outside of what is defaulted.
Shouldn't my catch all block be enough to pick this up? It's as if nothing is bubbling up to the process and I clearly see an exception in the logs.

Error - Business partner 30000011 does not exist in role TR0151

Hello,
I am receiving an error "Business partner 30000011 does not exist in role TR0151" while creating a Fixed Deposit Transaction through FTR_CREATE.
Whilst testing Fixed Deposit accounting in SAP Treasury, i was testing a scenario of a MINOR and his/her GUARDIAN. Both have been created as Business Partners. However, i have NOT created the Minor further as a Customer.
I now have a MINOR defined as a Business Partner, a GUARDIAN defined as a BUSINESS PARTNER and CUSTOMER both and a relationship established between the two through the RELATIONSHIPS tab.
After doing the above, i am trying to create a Fixed Deposit through FTR_CREATE where i am receiving the above mentioned error.
In Customizing, i have checked that the TR0151 is assigned to COUNTERPARTY role and TR0154 to the BENEFICIARY role
The GUARDIAN was created with BP role - Business Partner General and then changed to COUNTER PARTY. The MINOR has been created with BP Role - Business Partner General and then changed to BENEFICIARY.
My expectation was that since MINOR is not defined as Customer, the system would not allow me to create a FD for the Minor and display such a message which would ask me to create the FD using the GUARDIAN as the Business Partner.
Request your help on this.
Regards,
Murtuza.
+91 9923205169

Hi,
It is not necessary that a business partner has to be linked to a customer account. In certain cases, your house bank itself acts as a counterparty, in that case you can directly settle to your bank account instead of managing through a customer.
For your case, you need to maintain the role of counterparty for MINOR as well. Only if the business partner exists in that role can you create a transaction.
Regards,
Ravi

Partner link name issue in B2B-BPEL

Hi,
I configured B2B-BPEL interoperability. I am able to see the B2B adapter services wsdl from jdeveloper. I configured custom xml using ebMS protocol in B2B. while creating the partner link for that. it is showing wsdl path:
http://127.0.0.1:8888/orainfra/wsil/adapters/B2B/Custom/ebMS+Document+Protocol+Revision1-1.0/ebMS+doc+type1/ebMS+doc+def1?wsdl.
In BPEL, symbols "+, ?" were not supported so i am getting the error like "Name is not a valid NCNAME".
please some help me to resolve this.

Hi Ramesh,
I have applied the latest Patch (Patch Number- 5983622) and Configured the custom over ebMS(I could see from jdeveloper- partnerlink using the B2B WSIL browser). when i click the patnerlink- it shows the /adapters/B2B/Custom/ebMS+Document+protocol+revision1.0/ebMS+doc+type/ebMS+doc+def.
For wsdl file it shows the location: http://127.0.0.1:8888/orainfra/wsil/adapters/B2B/Custom/ebMS+Document+Protocol+Revision-1.0/ebMS+doc+type/ebMS+doc+def?wsdl.
I opened this using IE. I found wdsl that:
<?xml version="1.0" encoding="UTF-8" ?>
- <definitions name="ebMS+doc+type1_ebMS+Document+Protocol+Revision1-1.0" targetNamespace="http://xmlns.oracle.com/pcbpel/adapter/aq/ebMS+doc+type_ebMS+Document+Protocol+Revision-1.0/" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://xmlns.oracle.com/pcbpel/adapter/aq/ebMS+doc+type_ebMS+Document+Protocol+Revision-1.0/" xmlns:plt="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:jca="http://xmlns.oracle.com/pcbpel/wsdl/jca/" xmlns:pc="http://xmlns.oracle.com/pcbpel/" xmlns:imp1="http://www.w3.org/2001/XMLSchema" xmlns:obj1="http://xmlns.oracle.com/xdb/B2B/">
- <types>
- 
- <schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://xmlns.oracle.com/pcbpel/adapter/aq/ebMS+doc+type1_ebMS+Document+Protocol+Revision1-1.0/" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:hdr="http://xmlns.oracle.com/pcbpel/adapter/aq/inbound/">
<import namespace="http://xmlns.oracle.com/xdb/B2B/" schemaLocation="ebMS+doc+def/B2B_IP_MESSAGE_TYPE.xsd" />
<import namespace="http://xmlns.oracle.com/pcbpel/adapter/aq/inbound/" schemaLocation="ebMS+doc+def/aqAdapterHeader.xsd" />
- <complexType name="HeaderType">
- <sequence>
- 
<element name="QueueHeader" type="hdr:HeaderType" />
- 
<element name="PayloadHeader" type="obj1:IP_MESSAGE_TYPE" />
</sequence>
</complexType>
<element name="Header" type="tns:HeaderType" />
</schema>
- <schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://www.w3.org/2001/XMLSchema" schemaLocation="ebMS+doc+def/ebMS+doc+def.xsd" />
</schema>
</types>
- <message name="ebMS+doc+type_msg">
<part name="ebMS+doc+type1" element="imp1:ebMS+doc+type" />
</message>
- <message name="Header_msg">
<part name="Header" element="tns:Header" />
</message>
- <portType name="Enqueue_ptt">
- <operation name="Enqueue_ebMS+doc+type1_ebMS+Document+Protocol+Revision1-1.0">
<input message="tns:ebMS+doc+type1_msg" />
</operation>
</portType>
- <portType name="Dequeue_ptt">
- <operation name="Dequeue_ebMS+doc+type1_ebMS+Document+Protocol+Revision1-1.0">
<input message="tns:ebMS+doc+type1_msg" />
</operation>
</portType>
- <binding name="Enqueue_binding" type="tns:Enqueue_ptt">
<jca:binding />
- <operation name="Enqueue_ebMS+doc+type1_ebMS+Document+Protocol+Revision1-1.0">
<jca:operation InteractionSpec="oracle.tip.adapter.aq.outbound.AQEnqueueInteractionSpec" QueueName="IP_OUT_QUEUE" DatabaseSchema="B2B" ObjectFieldName="PAYLOAD" RecipientList="b2buser" OpaqueSchema="false" PayloadHeaderRequired="true" />
- <input>
<jca:header message="tns:Header_msg" part="Header" />
</input>
</operation>
</binding>
- <binding name="Dequeue_binding" type="tns:Dequeue_ptt">
<pc:inbound_binding />
- <operation name="Dequeue_ebMS+doc+type1_ebMS+Document+Protocol+Revision1-1.0">
<jca:operation ActivationSpec="oracle.tip.adapter.aq.inbound.AQDequeueActivationSpec" QueueName="IP_IN_QUEUE" DatabaseSchema="B2B" ObjectFieldName="PAYLOAD" Consumer="b2buser" OpaqueSchema="false" PayloadHeaderRequired="true" />
- <input>
<jca:header message="tns:Header_msg" part="Header" />
</input>
</operation>
</binding>
- <service name="ebMS+doc+type1_ebMS+Document+Protocol+Revision1-1.0">
- <port name="Enqueue_pt" binding="tns:Enqueue_binding">
<jca:address adapterInstanceJndi="eis/b2b" UIConnectionName="b2b" />
</port>
- <port name="Dequeue_pt" binding="tns:Dequeue_binding">
<jca:address adapterInstanceJndi="eis/b2b" UIConnectionName="b2b" />
</port>
</service>
- <plt:partnerLinkType name="PLT_ebMS+doc+type1_ebMS+Document+Protocol+Revision1-1.0_send">
- <plt:role name="B2BSend_ebMS+doc+type_ebMS+Document+Protocol+Revision-1.0">
<plt:portType name="tns:Enqueue_ptt" />
</plt:role>
</plt:partnerLinkType>
- <plt:partnerLinkType name="PLT_ebMS+doc+type1_ebMS+Document+Protocol+Revision1-1.0receive">
- <plt:role name="B2BReceive_ebMS+doc+type_ebMS+Document+Protocol+Revision-1.0">
<plt:portType name="tns:Dequeue_ptt" />
</plt:role>
</plt:partnerLinkType>
</definitions>
So i am facing the symbols "+, ?" were not supported so i am getting the error like "Name is not a valid NCNAME".

Invoice EDI error : EDI: Partner profile inbound not available

Hi EDI experts ,
We are connecting our SAP ECC 6 ( Ehp 4) system to 3rd party system Mincom via SAP PI, to send PO Creation message (Outbound) and receive Vendor Invoice message( inbound). We already done all the settings..Output determination procedure, Partner Profile ( WE20) , Port creation , Condition Records, EDI settings in SPRO for invoice..etc as below:
Logical system ( BD54)
ECC system - EDACLNT112,
PI systems u2013 IDACLNT210
Third party u2013 LSMINCOM
Port ( WE21)
IDACLNT510 : For PI with RFC destination IDACLNT510
Partner ( WE20)
LSMINCOM : (Partn.Type LS)
Outbound parmtrs.- Partner Role- LS, Message : ORDERS , Port - IDACLNT510
Inbound parmtrs.- Partner Role- LS, Message : INVOIC , Message Variant- MM, Process code u2013 INVL, Trigger immediately (Process code INVL have Identification - IDOC_INPUT_INVOIC_MRM, Option ALE u2013 Processing with ALE services , Processing type- processing by functional module)
Here PO Creation is working fine . IDoC of PO outbound message have below details :
Recipient information:
Port :     IDACLNT510 (Logical system & Port created in WE21 )
Partner Number : LSMINCOM   ( Logical system and Partner created in WE20)
Partn.Type : LS
Function : LS
Sender information:
Port : SAPEDA ( donu2019t know how it created..but in WE21..it is not there)
Partner number:   EDACLNT112 ( Logical system and Partner created in WE20)
Partn.Type : LS
Partner Role :Blank
Just started testing, our PI team is sending the IDoC, with wrong information on partner & other data, so inbound IDoC failing with error u201CEDI: Partner profile not availableu201D. Oaky. I reprocessed these failed IDoCs by changing Partner data just opposite (i.e. Sender info as Recipient info & vice versa) to successful PO Creation O/B message in WE19 in EDIDC and when I click on u201CStandard Inboundu201D, then another window open giving error message u201CPartner profile not maintainedu201D and creates new IDoC with status 56
EDI: Partner profile inbound not availableMessage no. E0337
Diagnosis
An inbound partner profile could not be found with the following key:
/LSMINCOM/LS//INVOIC///X/
This involves the key fields of table EDP21:
-SNDPRN partner number of sender
-SNDPRT partner type of sender
-SNDPFC partner function of sender
-MESTYP logical message type
-MESCOD logical message code
-MESFCT logical message function
-TEST    test flag
Procedure
Please check the inbound partner profiles.
Execute function
I am not getting exactly what inbound partner profile could not be found or what is the problem here . Can anyone suggest me what should be the problem and solution on it ?
Thanks
NAP

Narendra,
Please advice what was the solution.

Problem in DB Link creation of Oracle Wraehouse Builder 3i - Updated question

I am facing a problem in DB Link creation.
Backend: Oracle 8i Server on my machine
DW Software: Oracle warehouse builder 3i ( client , repository
asistant.....)
Operating system: Windows NT 4 SERVICE PACK 6
I wants to use the scott database( default database given by oracle )
as my input source.
How can I create the DB LINK ( for scott database) ?
How can I create the DB LINK ( for any other database) ?
Should I need to add anything in Setting of"ODBC DATASOURCE
ADMINISTRATION"
==================
Settings done:
==================
DB Link Name :prashant
Host name
Host name: my machine's ip address
port number: 1521
oracle sid: prashant ( my oracle sid)
user name:scott
password:tiger
==================
Gives error:
==================
Testing...
Failed.
Cwm Error Message: Failed in the WBAPIFactory.createDBLink()
Cwm Error: SQL Exception
Class Name: oracle.wh.ui.integrator.common.RepositoryUtils
Method Name: createDBLink(String, String, String, String)
Method Name: -1
Repository Error Message: java.sql.SQLException: ORA-02082: a loopback database link must have a connection qualifier
==================
==================
How should I proceed further.
I am expecting URGENT FEEDBACK.
Reply me on : [email protected] or this OTN Network
From
Prashant

I solved the problem.
Procedure I followed :
UNINSTALL ORACLE WRAEHOUSE BUILDER SOFTAWARE.
'GLOBAL_NAMES = FALSE' in init.ora file.
RESTARTED MY MACHINE.
INSTALL THE ORACLE WRAEHOUSE BUILDER SOFTAWARE.

Error in Partner Link creation

Similar Messages

Maybe you are looking for