Could not create XML document carrying AQ Headers

Hi gurus,
I’m trying to run the "Simple_XMLType_Payload" sample, and I have successfully deploy it on Oracle BPEL v10.1.3.1.0 , and after en-queue into the XMLType_Payload_In queue the recorded has been de-queued successfully, however there no instance for the BPEL has been created on the BPEL Console moreover there is no recorded inserted in XMLType_Payload_Out queue.
After investigating the OC4j_SOA log file, I found the following error
11/03/29 16:32:45 Confluent Monitor component started
11/03/29 16:32:45 Oracle Containers for J2EE 10g (10.1.3.1.0) initialized
11/03/29 16:52:28 java.lang.ClassCastException: oracle.xdb.XMLType
11/03/29 16:52:28 at oracle.tip.adapter.aq.database.MessageReader.readMessage(MessageReader.java:448)
11/03/29 16:52:28 at oracle.tip.adapter.aq.inbound.AQActivationSpecDequeuer.run(AQActivationSpecDequeuer.java:189)
11/03/29 16:52:28 at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
11/03/29 16:52:28 at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:272)
11/03/29 16:52:28 at java.lang.Thread.run(Thread.java:595)
<2011-03-29 16:52:28,082> <ERROR> <defualt.collaxa.cube.activation> <AQ Adapter::Inbound> MessageReader_ReadMessage: Could not create XML document carrying AQ Headers: [Ljava.lang.StackTraceElement;@748771
<2011-03-29 16:52:28,089> <ERROR> <defualt.collaxa.cube.activation> <AQ Adapter::Inbound>
java.lang.ClassCastException: oracle.xdb.XMLType
 at oracle.tip.adapter.aq.database.MessageReader.readMessage(MessageReader.java:448)
 at oracle.tip.adapter.aq.inbound.AQActivationSpecDequeuer.run(AQActivationSpecDequeuer.java:189)
 at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
 at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:272)
 at java.lang.Thread.run(Thread.java:595)

But I have tried it on another server that also has 10.1.3.1 version but the OS version is HP-UX B.11.23 U ia64 , and it woks fine, however I’m still has the same issue on the original server that has OS version HP-UX B.11.31 U ia64 ?
Edited by: user11096490 on Apr 4, 2011 11:06 AM

Similar Messages

AQ Adapter error: Could not create XML document carrying AQ Headers

I'm having problem with the AQ adapter (ADT) sample that comes with the SOA 10g install.
I am running 10.1.3.4 on XP, using Oracle XE.
I can use the sample sql script to enque and deque. However, when I deploy the sample ADT (BPEL project), I see errors in the opmn log. The BPEL instance is not even created.
I see another post with similar question, Re: Debugging BPEL when using Oracle AQ but no answer.
Any help is greatly appreciated. Thx!
----------------- err log --------------
<2009-07-15 00:04:31,656> <INFO> <collaxa> <ServerManager::loadProcesses> Done loading processes for all domains
<2009-07-15 00:04:32,031> <INFO> <default.collaxa.cube.activation> <AQ Adapter::Inbound> MessageReader_ctor: Initialized MessageReader for queue CUSTOMER_IN_QUEUE, consumer = null)
<2009-07-15 00:12:15,984> <ERROR> <default.collaxa.cube.activation> <AQ Adapter::Inbound> MessageReader_ReadMessage: Could not create XML document carrying AQ Headers: [Ljava.lang.StackTraceElement;@e7af3a
<2009-07-15 00:12:15,984> <ERROR> <default.collaxa.cube.activation> <AQ Adapter::Inbound>
java.lang.Exception: java.lang.NullPointerException
 at oracle.tip.adapter.aq.database.MessageReader.readMessage(MessageReader.java:750)
 at oracle.tip.adapter.aq.inbound.AQActivationSpecDequeuer.run(AQActivationSpecDequeuer.java:261)
 at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
 at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:280)
 at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NullPointerException
 at oracle.oc4j.sql.proxy.StatementBCELProxy.oc4j_releaseToCache(StatementBCELProxy.java:67)
 at oracle.oc4j.sql.proxy.StatementBCELProxy.oc4j_releaseTarget(StatementBCELProxy.java:79)
 at oracle.oc4j.sql.proxy.SQLBCELProxy.oc4j_close(SQLBCELProxy.java:95)
 at oracle.oc4j.sql.proxy.StatementBCELProxy.close(StatementBCELProxy.java:92)
 at oracle.AQ.AQOracleQueue.destroyStmt(AQOracleQueue.java:3099)
 at oracle.AQ.AQOracleQueue.dequeue(AQOracleQueue.java:1793)
 at oracle.AQ.AQOracleQueue.dequeue(AQOracleQueue.java:1307)
 at oracle.tip.adapter.aq.database.MessageReader.readMessage(MessageReader.java:485)
 ... 4 more
<2009-07-15 00:12:16,203> <FATAL> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Uncaught exception oracle.as.j2ee.transaction.tpc.ProtocolErrorWithNotification in JCA-work-instance:AQ Adapter-0 - cause: Branch [oracle.oc4j.sql.xa.EmulatedXAResource@14d9865, Xid( Global Id 34.5f.1e.a8.ff.ff.ff.ff.cd.b9.38.7d.22.01.00.00.7a.02.00.00.00.00.00.00, Format Id 1330790740, Branch Id 7c.e5.55.76.00.00.00.00.00.00.00.00.00.00.00.01), oracle.oc4j.sql.xa.EmulatedXAResource@14d9865, state={PREPARED}, exception error code=] in transaction Global Transaction Xid( Global Id 34.5f.1e.a8.ff.ff.ff.ff.cd.b9.38.7d.22.01.00.00.7a.02.00.00.00.00.00.00, Format Id 1330790740), type=orabpel, state=COMMITTING, time in completion or recovering=0)
....

thanks for the reply. I did look into that post, and couldn't found where to set that option either.
However, my PC was rebooted a few times today (I didn't change anything with BPEL), and I just re-ran the test now, that problem disappeared! It is working fine now.

Error in tutorial: Could not create XML document carrying AQ Headers

Hi,
We try to run the AQOutboundCorrelation tutorial. After running the enqueue_reply.sql script the message was placed from the request to the reply queue and read by the AQ inbound adapter.
Nothing happened in the flow. The following error occured in the domain log:
Could not create XML document carrying AQ Headers
Please help!!
See log messages below
<2007-01-18 13:58:59,187> <DEBUG> <default.collaxa.cube.activation> <AQ Adapter::Inbound> MessageReader_addPrimitive: field = PAYLOAD, value = Hallo
<2007-01-18 13:58:59,187> <DEBUG> <default.collaxa.cube.activation> <AQ Adapter::Inbound> MessageReader_addPrimitive: field = RESULT, value = request received
<2007-01-18 13:58:59,187> <DEBUG> <default.collaxa.cube.activation> <AQ Adapter::Inbound> MessageReader_getAsXML message:<<<<<<<
<?xml version = '1.0' standalone = 'yes'?>
<CORRELATIONREPLY_TYPE xmlns="http://xmlns.oracle.com/xdb/ANDRE">
<PAYLOAD xmlns="">Hallo</PAYLOAD>
<RESULT xmlns="">request received</RESULT>
</CORRELATIONREPLY_TYPE>
>>>>>>>>
<2007-01-18 13:58:59,187> <DEBUG> <default.collaxa.cube.activation> <AQ Adapter::Inbound> MessageReader_readMessage: aqHeader = oracle.xml.parser.v2.XMLDocument@eabad
<2007-01-18 13:58:59,187> <DEBUG> <default.collaxa.cube.activation> <AQ Adapter::Inbound> MessageReader_readMessage:Header<<<<<<<
<?xml version = '1.0' standalone = 'yes'?>
<Header xmlns="http://xmlns.oracle.com/pcbpel/adapter/aq/inbound/">
<MessageId>CA714367FA1B4BB3B2AC0211C9ECF2DB</MessageId>
<Priority>1</Priority>
<Correlation>209EE57CB6AC4B2FA2034C6FA58AD24B</Correlation>
<Attempts>0</Attempts>
<EnqueueTime>2007-01-18T13:58:59.000+01:00</EnqueueTime>
<OrigMessageId></OrigMessageId>
</Header>
>>>>>>>>
<2007-01-18 13:58:59,187> <ERROR> <default.collaxa.cube.activation> <AQ Adapter::Inbound> MessageReader_ReadMessage: Could not create XML document carrying AQ Headers: [Ljava.lang.StackTraceElement;@12916fe
<2007-01-18 13:58:59,187> <ERROR> <default.collaxa.cube.activation> <AQ Adapter::Inbound>
java.lang.NullPointerException
 at java.lang.String.<init>(String.java:479)
 at oracle.tip.adapter.aq.database.MessageReader.readMessage(MessageReader.java:573)
 at oracle.tip.adapter.aq.inbound.AQActivationSpecDequeuer.run(AQActivationSpecDequeuer.java:183)
 at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
 at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:272)
 at java.lang.Thread.run(Thread.java:595)
Message was edited by:
rverbeea1

Sorry for not mentioning the product versions:
The bpel process was build and deployed with Jdeveloper Studio edition version 10.1.3.1.0.3984 on a Bpel server/Application Server with version 10.1.3.1 (NT).

Could not create discount document

Hello!
We are having the following error either on automatic (F110) or manual payments (F-53) when generating a discount documents:
Manual Payments error:
Could not create discount document
Message no. 8A605
Automatic Payments error:
FF848: Entry of tax for C1 000 is not possible because of tax base 0
I think that the error is generated because the tax base amount is not being completed automatically.
I have already checked discount documents customizing and I´ve founded everything ok.
Also Tax Category field for the discount GL account is completed.
Any help would be appreciated.
Regards.

Hi Nirav, thank for your answer.
I have already check that field that you mentioned.
It is exactly the way you told me.
Do you have in mind anything else?
Regards.

Error in Trace Level: could not create BPE proxy for message, no XML objec

Hi
We are doing a scenario of File to RFC using BPM and I am getting this errror in Tcode SXMB_MONI.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="BPE_ADAPTER">UNKNOWN_MESSAGE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No object type found for this message; check the activation of the corresponding process</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
And getting this error in Trace level
could not create BPE proxy for message, no XML object definition found for message EB32BB50610A11DC9648001321CB837D
Why this error occurs?
What could be in error?
Thanks in advance
Regards
Sami Qureshi

Hi Sami,
Check if thse threads can help u,
Error in BPE Adapter
BPM - BPE_ADAPTER errors
BPE Adapter Error
Exeception during execution error
***********Reward points if helpfull************

EHSM - Create Vendor - error: 'Could not find a document for the given key'

Dear all,
In the Chemical Approval Process I have attached a SDS document to the Approval Request. You can assign a Vendor to the SDS. As there are no (EHSM) Vendors currently available in the system I would like to create a new (EHSM) Vendor by clicking on 'Create Vendor'.
This will lead me to the following Webdynpro Application: Edit Vendor (EHFND_UI_VENDOR_OVP).
Only one field is shown in the Webdynpro named: 'Name of the Vendor'. After typing a name e.g. 'test', the following error message appears; 'Could not find a document for the given key'. See also attached document. This issue looks like a missing number range, however I could not find a EHSM number range for Vendors.
How to solve this issue?
More information:
Software Component: SAP EHS Management (EHSM) Support Package: 3
Process: Chemical Approval
Webdynpro application: EHFND_UI_VENDOR_OVP
Thank you.
Kind regards,
Roy

Hi
babooraj
This might be a problem with Windows Power Shell.
The solution is to copy the folder: "PSWorkflow" from "C:\Windows\System32\WindowsPowerShell\v1.0\Modules\"
to "C:\Windows\SysWOW64\WindowsPowerShell\v1.0\Modules"
Than everything works fine.
Ps.: @Microsoft, please fix this problem in future versions.
Thomas van Veen

ERROR Could not create DOM from control.xml

Hi All,
I am installaing 4.7EE on Sun Solaris 5.9 SPARC with Oracle and JDK version is 1.4.2_08. When i am running sapinst, sapinst GUI opens and after when i am selecting the Central installtion and i click on Next it giving error message that
WARNING Could not read file control.xml. Please make sure that you called SAPinst with the correct control file (the control file is given to SAPinst as its first command line parameter or as value of the command line property SAPINST_CONTROL_URL)
ERROR Could not create DOM from control.xml
How to solve this error. I have searched in SDN but i am unable to get the solution.
Mahesh C

Hi Kiran,
I have given all permissions to the control file. But these control files are in different places /SAPINST/UNIX/SUNOS_64/PATCOL640/WEBAS630 and ORA, DB2, DB6, IND, INF, ADA in these folders i can c the Control.xml files. But i have given all read write and execute permissions but still its getting the same error. I have downloaded the same IM for 3 times and tried.. But the result is the same.
Is there any other way of work around for this...
Thanks
Mahesh C

Com.bea.xml.XmlException error for "could not create child element"

In Workshop 9.2, after I created a project with XMLBeans Builder Builder against the xsd's and created a web service control against a wsdl, I inserted the control in a client project for consumption. However, when calling into a method of the control, I got a com.bea.xml.XmlException, saying "could not create child element" for an object parameter passed in the call to the method. The relevant info in the server console looks like this:
Caused by: com.bea.xml.XmlException: could not create child element 'wirelessPhoneNumber' for Wrapped XMLBean operation on '<?xml version="1.0" encoding="UTF-8
"?><m:sendSMSMessage xmlns:m="http://service.xyz.com/provider/mobile/abc/sendSMSMessage/200701/"><ns:behaviorVersion xmlns:ns="http://service.xyz.com/entity/message/2003/">0</ns:behaviorVersion><ns:custNbr xmlns:ns="http
://service.xyz.com/entity/party/2003/">Hello</ns:custNbr></m:sendSMSMessage>'
Does any have an idea what this is trying to tell me?
Thanks in advance for any help,
Jason

Looking into it further, I think it's the parameter wirelessPhoneNumber, which is a complex type from xsd and a java object passed to the call sendSMSMessage, that is having a namespace problem, or other problem.
This parameter object was from XMLBeans java binding. I created and set it up like this before passing it to the call:
PhoneNumberType phoneNumberType = phoneNumberType.Factory.newInstance();
phoneNumberType.setFormat(PhoneNumberFormatEnum.FREEFORM);
phoneNumberType.setFullNumber(phoneNumber);
Obviously, com.bea.xbeanmarshal.buildtime.internal.util.XmlBeanUtil.createWrappedXBeanTopElement of XmlBeanUtil.java had a problem creating a wrapper element for it.
Any clue from anyone?
Jason

Error: "Could not create document" on fileshare

Ladies and Gentleman,
I integrated a fileshare to our PoC Mobile Documents instance like described in the article
SAP Mobile Documents - Connecting a File Share as Corporate Repository
created by Jens Koster.
The Configuration worked well, and I can see the repository under the "Corporate" tab. I can see the directory structure and the files, and I am able to browse the directory and open the files. As soon as I want to create a directory, or to upload a new file into the repository, I am getting an Error.
The logs on the Netweaver show me "Could not create document"
All the settings I did during the configuration look like described in the document of Jens.
The permissions I set on the file share itself should allow everybody to create documents and directories - I did a successful test on the Windows File explorer.
Is there anything missing in my configuration?
Thank you for your help.
br
Ernst

Hi Ernst,
try to use a CM Repository manager instead of the File System manager. Configure the persistence mode of the cm repository to fsdb and specify a versioning folder. Set the Security Manager to ACLSecurityManager and the ACL Manager cache to ca_rsrc_acl.
There are some issues when you grant write access to a file system via SAP km. You can read about the impacts here: CM Repository Manager - Knowledge Management - SAP Library in the section FSDB Mode.
Hope this helps.
Best Regards,
Simon

I can't open protools error could not create a new document because assertion in/volume/ development/w.s.Protools_10.1.2/Altura parts/DFW/macBuild/../view/umenu.MacOS.mm.line 1351

I can't open protools error could not create a new document because assertion in/volume/ development/w.s.Protools_10.1.2/Altura parts/DFW/MacBuild/../view/umenu.MacOS.mm.line 1351

I'd search or post here:
http://www.macosxaudio.com/forums/viewforum.php?f=26

"Could not create SSOToken" error while setting agent for SSO

Hello,
I configured my agent as follows:
Version: 3.0
Build Date: 20071212
Application Server Config Directory : C:\Sun\SDK\domains\domain1\config
Application Server Instance name : server
Access Manager URL : http://juno:6140/opensso
Domain Administration Server Host is remote : false
Agent URL : http://juno:8080
Deployment URI for the Agent Application : /agentapp
Encryption Key : J+KQLOM+s6gAQb1Y1H8uJoej3bzKBAEN
Agent Profile name : asagent
Agent Profile Password file name : c:\temp\password.TXT
Agent installed on the DAS host for a remote instance : false
The AM and the sample applications are both running on separate domains.
Following steps I performed:
1. I started my SSO domain (domain2) first and then the application domain where my agent is installed (domain1).
2. I deployed the agentsample.ear file after compilation through build.xml file
When I try to access the URL (http://localhost:8080/agentsample/index.html), it throw the following exception (recorded in amSSO log file located in the Agent_001
12/14/2007 11:16:16:242 AM EST: Thread[httpSSLWorkerThread-8080-0,10,Grizzly]
12/14/2007 11:16:16:242 AM EST: Thread[httpSSLWorkerThread-8080-0,10,Grizzly]
could not create SSOTOken for token ID AQIC5wM2LY4SfcykqWPzOYlM/mkFg8E9ozYLBizVono/kDE=@AAJTSQACMDE=#
com.iplanet.dpro.session.SessionException: Service URL not found:session
 at com.iplanet.dpro.session.Session.refresh(Session.java:1133)
 at com.iplanet.dpro.session.Session.getSession(Session.java:808)
 at com.iplanet.sso.providers.dpro.SSOProviderImpl.createSSOToken(SSOProviderImpl.java:154)
 at com.iplanet.sso.SSOTokenManager.createSSOToken(SSOTokenManager.java:300)
 at com.sun.identity.authentication.AuthContext.getSSOToken(AuthContext.java:1105)
 at com.sun.identity.security.SystemAppTokenProvider.getAppSSOToken(SystemAppTokenProvider.java:87)
 at com.sun.identity.security.AdminTokenAction.run(AdminTokenAction.java:222)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sun.identity.common.PropertiesFinder.getProperty(PropertiesFinder.java:49)
 at com.iplanet.am.util.SystemProperties.get(SystemProperties.java:255)
 at com.iplanet.am.util.SystemProperties.get(SystemProperties.java:298)
 at com.iplanet.dpro.session.SessionID.<clinit>(SessionID.java:90)
 at com.iplanet.sso.providers.dpro.SSOProviderImpl.createSSOToken(SSOProviderImpl.java:153)
 at com.iplanet.sso.SSOTokenManager.createSSOToken(SSOTokenManager.java:300)
 at com.sun.identity.authentication.AuthContext.getSSOToken(AuthContext.java:1105)
 at com.sun.identity.security.SystemAppTokenProvider.getAppSSOToken(SystemAppTokenProvider.java:87)
 at com.sun.identity.security.AdminTokenAction.run(AdminTokenAction.java:222)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sun.identity.common.configuration.ConfigurationBase.isLegacy(ConfigurationBase.java:180)
 at com.sun.identity.common.configuration.ConfigurationObserver.createAttributeMapping(ConfigurationObserver.java:62)
 at com.sun.identity.common.configuration.ConfigurationObserver.<init>(ConfigurationObserver.java:58)
 at com.sun.identity.common.configuration.ConfigurationObserver.<clinit>(ConfigurationObserver.java:50)
 at com.sun.identity.common.DebugPropertiesObserver.<clinit>(DebugPropertiesObserver.java:44)
 at com.sun.identity.agents.arch.AgentConfiguration.bootStrapClientConfiguration(AgentConfiguration.java:587)
 at com.sun.identity.agents.arch.AgentConfiguration.initializeConfiguration(AgentConfiguration.java:1008)
 at com.sun.identity.agents.arch.AgentConfiguration.<clinit>(AgentConfiguration.java:1321)
 at com.sun.identity.agents.arch.Manager.<clinit>(Manager.java:622)
 at com.sun.identity.agents.filter.AmAgentBaseFilter.initializeFilter(AmAgentBaseFilter.java:217)
 at com.sun.identity.agents.filter.AmAgentBaseFilter.getAmFilterInstance(AmAgentBaseFilter.java:279)
 at com.sun.identity.agents.filter.AmAgentBaseFilter.doFilter(AmAgentBaseFilter.java:64)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:230)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:198)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:288)
 at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:271)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:202)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
 at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
 at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:270)
 at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
 at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568)
 at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
 at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:339)
 at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:261)
 at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:212)
 at com.sun.enterprise.web.portunif.PortUnificationPipeline$PUTask.doTask(PortUnificationPipeline.java:361)
 at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
 at com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)
12/14/2007 11:32:28:916 AM EST: Thread[httpSSLWorkerThread-8080-0,10,Grizzly]
12/14/2007 11:32:28:916 AM EST: Thread[httpSSLWorkerThread-8080-0,10,Grizzly]
could not create SSOTOken for token ID AQIC5wM2LY4SfcyqQ1KVtRFCVm5y4qGBf7JcHCnC6du58xk=@AAJTSQACMDE=#
com.iplanet.dpro.session.SessionException: Service URL not found:session
 at com.iplanet.dpro.session.Session.refresh(Session.java:1133)
 at com.iplanet.dpro.session.Session.getSession(Session.java:808)
 at com.iplanet.sso.providers.dpro.SSOProviderImpl.createSSOToken(SSOProviderImpl.java:154)
 at com.iplanet.sso.SSOTokenManager.createSSOToken(SSOTokenManager.java:300)
 at com.sun.identity.authentication.AuthContext.getSSOToken(AuthContext.java:1105)
 at com.sun.identity.security.SystemAppTokenProvider.getAppSSOToken(SystemAppTokenProvider.java:87)
 at com.sun.identity.security.AdminTokenAction.run(AdminTokenAction.java:222)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sun.identity.common.PropertiesFinder.getProperty(PropertiesFinder.java:49)
 at com.iplanet.am.util.SystemProperties.get(SystemProperties.java:255)
 at com.iplanet.am.util.SystemProperties.get(SystemProperties.java:298)
 at com.iplanet.dpro.session.SessionID.<clinit>(SessionID.java:90)
 at com.iplanet.sso.providers.dpro.SSOProviderImpl.createSSOToken(SSOProviderImpl.java:153)
 at com.iplanet.sso.SSOTokenManager.createSSOToken(SSOTokenManager.java:300)
 at com.sun.identity.authentication.AuthContext.getSSOToken(AuthContext.java:1105)
 at com.sun.identity.security.SystemAppTokenProvider.getAppSSOToken(SystemAppTokenProvider.java:87)
 at com.sun.identity.security.AdminTokenAction.run(AdminTokenAction.java:222)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sun.identity.common.configuration.ConfigurationBase.isLegacy(ConfigurationBase.java:180)
 at com.sun.identity.common.configuration.ConfigurationObserver.createAttributeMapping(ConfigurationObserver.java:62)
 at com.sun.identity.common.configuration.ConfigurationObserver.<init>(ConfigurationObserver.java:58)
 at com.sun.identity.common.configuration.ConfigurationObserver.<clinit>(ConfigurationObserver.java:50)
 at com.sun.identity.common.DebugPropertiesObserver.<clinit>(DebugPropertiesObserver.java:44)
 at com.sun.identity.agents.arch.AgentConfiguration.bootStrapClientConfiguration(AgentConfiguration.java:587)
 at com.sun.identity.agents.arch.AgentConfiguration.initializeConfiguration(AgentConfiguration.java:1008)
 at com.sun.identity.agents.arch.AgentConfiguration.<clinit>(AgentConfiguration.java:1321)
 at com.sun.identity.agents.arch.Manager.<clinit>(Manager.java:622)
 at com.sun.identity.agents.filter.AmAgentBaseFilter.initializeFilter(AmAgentBaseFilter.java:217)
 at com.sun.identity.agents.filter.AmAgentBaseFilter.getAmFilterInstance(AmAgentBaseFilter.java:279)
 at com.sun.identity.agents.filter.AmAgentBaseFilter.doFilter(AmAgentBaseFilter.java:64)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:230)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:198)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:288)
 at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:271)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:202)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
 at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
 at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:270)
 at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
 at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568)
 at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
 at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:339)
 at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:261)
 at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:212)
 at com.sun.enterprise.web.portunif.PortUnificationPipeline$PUTask.doTask(PortUnificationPipeline.java:361)
 at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
 at com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)
I spent lot of time refering the supporting document but could not find any solution.
Your assistance will be greatly appreciated.
Thanks,
Vinit

Seems that the « Reuse connection » command is essential to assure that an application use ONLY ONE Jco. I get rid of the disconnectIfAlive.
Recommendation 1: Put all the BAPIs that you call in the same system into the same model!
Recommendation 2: If you canu2018t follow recommendation 1, make sure that the two models synchronize their (JCo) connections!
// two separate model instances are created ...
MyFirstModelTypemodelMyFirst= (MyFirstModelType) WDModelFactory.getModelInstance(
MyFirstModelType.class,
WDModelScopeType.APPLICATION_SCOPE);
MyOtherModelTypemodelMyOther= (MyOtherModelType) WDModelFactory.getModelInstance(
MyOtherModelType.class,
WDModelScopeType.APPLICATION_SCOPE);
// ... but the first model manages and provides the
// connection for the other model
modelMyOther.setConnectionProvider(modelMyFirst);
Edited by: Emanuel Champagne on Jun 27, 2008 2:38 PM

UCCX 8 - Dramatic change in the Create File Document step that is used by the Create XML Document step in order to read an XML file

/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
For the last 5 years (and in IPCC3.x/4.x,UCCX/5.x/7.x) I've used the same basic subflow to read a XML document that contains holiday dates where the queue should be closed. I've re-used this script on 20+ client installs and it's always worked. The structure of the script allows you to pass the path and filename of the XML document as parameters to the subflow. (The document is in the repository)
I loaded this script in UCCX 8.0.2 recently and it crashed with a Java.IO error. It looked like it was trying to read the file system directly and not the repository. (In the Linux appliance model this kind of makes sense but why is the step trying to read the file system directly?)
So I open a TAC case (SR# 615243125) and TAC tells me that the method of using the Create File Document step is not supported anymore and that I should specify the filename directly in the Create XML Document step
The problem that I see (aside from having to edit all my scripts that use XML files) is that the Create XML Document step is looking for the input to be a type DOCUMENT and not a type STRING. This seems to imply that I have to hardcode the document in each script that I deploy for a customer. When it was a string it was easy to construct the full file path from parameters and pass to the subflow.
Questions to the group
#1 Am I missing something here?
#2 Do you assume that you'll be able to load a script that worked fine in UCCX 7 into UCCX 8 and that it should completely function when you're doing everything according to the step reference documentation.
#3 Cisco didn’t document this in any way that I can find.
#4 How can you use the Create XML Document step in a fashion that would let you construct the path of the file and the filename previously in the script so you could pass it to a subflow ? It would seem this functionality has been killed in UCCX 8
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
(Background)
Create File Document Step
The input filename is a STRING, could be an explicit path and filename in the repository or a variable that represents that path and string
The output of this step is a DOCUMENT to be used in the Create XML Document step
The string FILE_FullPathHolidayFiles references en_us\folderName\documentName.xml
The document was properly uploaded into the repository only, NOT trying to directly read c:\foo\blah…
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
The create XML document input can only be a type DOCUMENT

#1 Am I missing something here?
You are mixing two different issues together here.
The Create File Document step is indeed not needed or supported for creating an XML document. That is why there is a unique step; to trigger XML parsing within the MIVR subsystem.
Accessing the file system is restricted to a single folder within the VOS model (i.e. 8.0+). This folder is not backed up, replicated, or cleaned up automatically. It was intended to give developers some FS access as a temporary swap location only.
#2 Do you assume that you'll be able to load a script that
worked fine in UCCX 7 into UCCX 8 and that it should completely
function when you're doing everything according to the step reference
documentation.
Assume nothing; read the documentation and attend one of the dozens of partner training sessions that CCBU put on advising of the upcoming changes.
#3 Cisco didn’t document this in any way that I can find.
You're right, I guess, on the Create File vs. XML Document step. AFAIK Cisco never wrote a notice into the Step Reference Guide explicitly stating that you cannot use the Create File Document although the documentation seemed pretty clear to me without it. File system restrictions are documented in the 8.0 release notes.
Scripting and Development Series: Volume 2, Editor Step ReferenceUse the Create XML Document step to create a logical document that maps a document to another document variable (where the document has already been pre-parsed as an XML document and is ready to be accessed by the Get XML Document Data step).Use this step before the Get XML Document Data step to obtain data from a document formatted using the Extensible Markup Language (XML).
#4 How can you use the Create XML Document step in a fashion that would
let you construct the path of the file and the filename previously in
the script so you could pass it to a subflow ? It would seem this functionality has been killed in UCCX 8
No it hasn't; just concatinate a string to build the Source Document parameter the step needs. Example: "DOC[" + myFilePath + "]"

Could not create Purchase Order Stock Transfer Order

Hi Expert!
Need your help.
User could not make Could not create Purchase Order Stock Transfer Order for new plant 1075 & 1076 at P05 with error message Not posible to determine shipping data for material. Our new vendor are 510022060 for new plant 1075 and 510022061 for new plant 1076.
The problem was caused by the missing STO setup for these two plant 1075 and 1076, as no customer code being referred.
Now i got the customer number for these two plants but how to set it up in configuration? Please guide me step by step.

Hi Crystal,
The following customising need to be carried out for Inter Company Stock Transfer.
Path : sproMaterials ManagementPurchasing-Purchase OrderSet up Stock Transport Order
Define Shipping Data for Plants :
For the Supplying plant (1) the Sales Org data to be maintained.
For the Receiving plant (2) the Customer No to be maintained.
Create Checking Rule - U can use existing one Eg : B
Define Checking Rule : Use Standard one Eg :01 linked to B.
Assign Delivery Type and Checking Rule -- For the Supplying Plant (1) and document type NB use the delviery type NLCC and Checking Rule B.
Assign Document Type, One-Step Procedure, Underdelivery Tolerance :
For the supplying Plant (1) and Receving Plant (1) ; assign the document type : NB.
Points to be noted :
The Material should exists in both the plants ( 1 & 2 ) with the sales view maintained . Note that the Loading grp / Transporting Grp is mantaory in Sales Views.
The Vendor is to be assigned to the supplying Plant (1 ) in Purchasing View of Vendor Master.
For that click on Extras - Add Purchasing data in Purchasing view of Vendor Master (XK02 )
Do maintain the customer in Control data of Vendor Master.
Do maintain the Vendor in Control data of Customer Master.
Also note that shipping conditions are maintained in the Customer Master . The same can be found in Sales Area - Shipping Tab.
Shipping Point determination :
SPROLogistics ExecutionShippingBasic Shipping FunctionsShipping Point and Goods Receiving Point Determination--Assign Shipping Points ( For a particular Shipping condition/ Loading Grp /Plant - the shipping point is assigned ).
Regards
Ramesh Ch

"Could not create renderer with alias..." after deploying ResourceRenderer

Hello everybody
I've developed a custom ResourceRenderer class that looks like this:
package no.expert.portal.km.relateddocs;
import com.sapportals.htmlb.Component;
import com.sapportals.htmlb.Link;
import com.sapportals.wcm.WcmException;
import com.sapportals.wcm.rendering.resource.cm.ResourceRenderer;
import com.sapportals.wcm.repository.IResource;
public class RelatedDocsNamePropertyRenderer extends ResourceRenderer
 protected Component renderContentLink(com.sapportals.htmlb.Component comp) throws WcmException
 Link result = (Link) super.renderContentLink(comp);
 result.setTarget("");
 return result;
 protected Component renderContentLink(IResource resource, com.sapportals.htmlb.Component comp) throws WcmException
 Link result = (Link)super.renderContentLink(resource, comp);
 result.setTarget("");
 return result;
All it does, really, is preventing links to documents in KM to open in a new window. At least that's what I'm hoping it will do, as it's based on ideas in <a href="https://www.sdn.sap.com/irj/sdn/thread?threadID=20316">this post</a>.
I've added all the necessary .jar files, and implemented a wrapper portal service as described here: <a href="http://media.sdn.sap.com/html/submitted_docs/nw_kmc/ide/projects/Setting%20Up%20a%20KMC%20Project.html">http://media.sdn.sap.com/html/submitted_docs/nw_kmc/ide/projects/Setting%20Up%20a%20KMC%20Project.html</a>.
I've created an alias for the class in Content Management -> User Interface -> Mapping, and assigned this to the resource renderer settings that I use.
OK, here is where the trouble starts. When viewing the layout set with debugging on, I check Rendering Information. It informs me that "The given configuration was not used, because the alias is not defined or points to an invalid java class". Looking in the log, this is the error message:
Could not create renderer with alias ZRelatedDocsNameResourceRender and classname no.expert.portal.km.relateddocs.RelatedDocsNamePropertyRenderer:java.lang.NoClassDefFoundError: com/sapportals/wcm/rendering/resource/cm/ResourceRenderer
------------------------- Loader Info -------------------------
ClassLoader name: [com.sapportals.portal.prt.util.ApplicationClassLoader@6b247b]
Parent loader name: [com.sapportals.portal.prt.util.ApplicationClassLoader@4e82c4]
References:
 not registered!
Resources:
 C:usrsapEPUJC00j2eeclusterserver0appssap.comirjservlet_jspirjrootWEB-INFportalportalappsno.expert.portal.km.relateddocs.RelatedDocsNamePropertyRendererprivatelibno.expert.portal.km.relateddocs.RelatedDocsNamePropertyRenderercore.jar
The error occurred while trying to load "no.expert.portal.km.relateddocs.RelatedDocsNamePropertyRenderer".
 at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:389)
I have a suspicion this might have something to do with the SharingRefernce in portalapp.xml, but after experimenting with different values, I'm no nearer a solution. Any ideas, anyone? Any help greatly appreciated.
-martin
Yes, and here is my portalapp.xml:
<?xml version="1.0" encoding="utf-8"?>
<application>
<application-config>
 <property name="SharingReference" value="com.sap.netweaver.bc.crt,knowledgemanagement"/>
 <property name="PrivateSharingReference" value="com.sap.km.cm.ui.flex"/>
</application-config>
<components>
 <component name="RelatedDocsNamePropertyRenderer">
 <component-config>
 <property name="ClassName" value="no.expert.portal.km.relateddocs.RelatedDocsNamePropertyRenderer"/>
 </component-config>
 <component-profile/>
 </component>
</components>
<services>
 <service name="BootStrapNamePropertyRender">
 <service-config>
 <property name="className" value="no.expert.portal.km.relateddocs.BootStrapNamePropertyRender"/>
 <property name="startup" value="true"/>
 </service-config>
 </service>
</services>
</application>

Hi Gourab,
Double check the the page.xml has referring to the correct CO. Open the page.xml and see which controller is attached to it.
Also attach the extended controller through personalization to the page/Region.
Thanks
--Anil

DBMS_XMLSCHEMA.CopyEvolve produces ORA-30945: Could not create mapping tabl

Hi,
I am trying to update a XML Schema concerning the documents relaties.xsd (the old one) and relaties_v2.xsd (the new one containing only a minor change).
The document relaties.xsd looks like this:
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xdb="http://xmlns.oracle.com/xdb"
elementFormDefault="unqualified"
attributeFormDefault="unqualified"
version="1.0">
 <xsd:element name="Relatie" xdb:defaultTable="">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name="Voornaam" type="xsd:string"/>
 <xsd:element name="Achternaam" type="xsd:string"/>
 <xsd:element name="Tussenvoegsel" type="xsd:string"/>
 <xsd:element name="Geboortedatum" type="xsd:date"/>
 <xsd:element name="Geslacht">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="M"/>
<xsd:enumeration value="V"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
 <xsd:element name="Sofinummer">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="\d{9}"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
 <xsd:element name="Straatnaam" type="xsd:string"/>
 <xsd:element name="Huisnummer" type="xsd:string"/>
 <xsd:element name="Woonplaats" type="xsd:string"/>
 
 <xsd:element name="Postcode">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="\d{4} [A-Z]{2}"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
 <xsd:element name="Zrn">
<xsd:simpleType>
<xsd:restriction base="xsd:integer">
<xsd:minInclusive value="1000000"/>
<xsd:maxInclusive value="99999999999999"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
</xsd:schema>
Here are the steps I took.
DECLARE
res BOOLEAN;
BEGIN
res := DBMS_XDB.createResource('/xsd/relaties.xsd',
bfilename('XSDDIR', 'relaties.xsd')
END;
DECLARE
res BOOLEAN;
BEGIN
res := DBMS_XDB.createResource('/xsd/relaties_v2.xsd',
bfilename('XSDDIR', 'relaties_v2.xsd')
END;
BEGIN
DBMS_XMLSCHEMA.registerSchema(
'http://localhost:8080/xsd/relaties.xsd',
XDBURIType('/xsd/relaties.xsd').getClob(),
TRUE,
FALSE,
FALSE,
TRUE);
END;
CREATE
TABLE relatie_documenten OF XMLTYPE
XMLSCHEMA "http://localhost:8080/xsd/relaties.xsd"
ELEMENT "Relatie"
CREATE OR REPLACE
TRIGGER upo_rdt_ai
AFTER INSERT ON relatie_documenten
FOR EACH ROW
DECLARE
doc XMLType;
BEGIN
doc := :new.SYS_NC_ROWINFO$;
XMLType.schemaValidate(doc);
END;
Then I inserted some xml documents into the table relatie_documenten. The XSD worked fine.
Then I executed the following statement:
BEGIN
DBMS_XMLSCHEMA.copyEvolve
( schemaURLs => xdb$string_list_t('http://localhost:8080/xsd/relaties.xsd')
, newSchemas => XMLSequenceType(XDBURIType('/xsd/relaties_v2.xsd').getXML())
, preserveOldDocs => TRUE
, mapTabName => 'RELATIE_DOCUMENTEN_TEMP'
, generateTables => FALSE
END;
This resulted in:
ERROR at line 1:
ORA-30945: Could not create mapping table 'RELATIE_DOCUMENTEN_TEMP'
ORA-00600: internal error code, arguments: [kqludp2], [0x66AB407C], [0], [],
ORA-06512: at "XDB.DBMS_XMLSCHEMA_INT", line 113
ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 210
ORA-06512: at line 2
I checked system priviliges as documented in XML DB Developers Guide, Chapter 8 XML Schema Evolution. No other users were connected. The mapping table RELATIE_DOCUMENTEN_TEMP nor any other object named RELATIE_DOCUMENTEN_TEMP did not exist.
Anyone an idea why I cannot create my mapping table ?
Gregor

Which release / platform are you working with
With 10.2.0.2.1 on Widows I get
SQL> var schemaURL varchar2(256)
SQL> var schemaPath varchar2(256)
SQL> --
SQL> begin
2 :schemaURL := 'http://localhost:8080/xsd/relaties.xsd';
3 :schemaPath := '/public/relaties.xsd';
4 end;
5 /
PL/SQL procedure successfully completed.
SQL> call dbms_xmlSchema.deleteSchema(:schemaURL,4)
2 /
Call completed.
SQL> declare
2 res boolean;
3 xmlSchema xmlType := xmlType(
4 '<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
5 xmlns:xdb="http://xmlns.oracle.com/xdb"
6 elementFormDefault="unqualified"
7 attributeFormDefault="unqualified"
8 version="1.0">
9 <xsd:element name="Relatie" xdb:defaultTable="">
10 <xsd:complexType>
11 <xsd:sequence>
12 <xsd:element name="Voornaam" type="xsd:string"/>
13 <xsd:element name="Achternaam" type="xsd:string"/>
14 <xsd:element name="Tussenvoegsel" type="xsd:string"/>
15 <xsd:element name="Geboortedatum" type="xsd:date"/>
16 <xsd:element name="Geslacht">
17 <xsd:simpleType>
18 <xsd:restriction base="xsd:string">
19 <xsd:enumeration value="M"/>
20 <xsd:enumeration value="V"/>
21 </xsd:restriction>
22 </xsd:simpleType>
23 </xsd:element>
24 <xsd:element name="Sofinummer">
25 <xsd:simpleType>
26 <xsd:restriction base="xsd:string">
27 <xsd:pattern value="\d{9}"/>
28 </xsd:restriction>
29 </xsd:simpleType>
30 </xsd:element>
31 <xsd:element name="Straatnaam" type="xsd:string"/>
32 <xsd:element name="Huisnummer" type="xsd:string"/>
33 <xsd:element name="Woonplaats" type="xsd:string"/>
34 
35 <xsd:element name="Postcode">
36 <xsd:simpleType>
37 <xsd:restriction base="xsd:string">
38 <xsd:pattern value="\d{4} [A-Z]{2}"/>
39 </xsd:restriction>
40 </xsd:simpleType>
41 </xsd:element>
42 <xsd:element name="Zrn">
43 <xsd:simpleType>
44 <xsd:restriction base="xsd:integer">
45 <xsd:minInclusive value="1000000"/>
46 <xsd:maxInclusive value="99999999999999"/>
47 </xsd:restriction>
48 </xsd:simpleType>
49 </xsd:element>
50 </xsd:sequence>
51 </xsd:complexType>
52 </xsd:element>
53 </xsd:schema>');
54 begin
55 if (dbms_xdb.existsResource(:schemaPath)) then
56 dbms_xdb.deleteResource(:schemaPath);
57 end if;
58 res := dbms_xdb.createResource(:schemaPath,xmlSchema);
59 end;
60 /
PL/SQL procedure successfully completed.
SQL> BEGIN
2 DBMS_XMLSCHEMA.registerSchema(
3 :schemaURL,
4 XDBURIType(:schemaPath).getClob(),
5 TRUE,
6 FALSE,
7 FALSE,
8 TRUE);
9 END;
10 /
PL/SQL procedure successfully completed.
SQL> DROP TABLE relatie_documenten FORCE
2 /
Table dropped.
SQL> CREATE TABLE relatie_documenten OF XMLTYPE
2 XMLSCHEMA "http://localhost:8080/xsd/relaties.xsd"
3 ELEMENT "Relatie"
4 /
Table created.
SQL> CREATE OR REPLACE TRIGGER upo_rdt_ai
2 AFTER INSERT ON relatie_documenten
3 FOR EACH ROW
4 DECLARE
5 doc XMLType;
6 BEGIN
7 doc := :new.SYS_NC_ROWINFO$;
8 XMLType.schemaValidate(doc);
9 END;
10 /
Trigger created.
SQL> INSERT
2 INTO relatie_documenten
3 VALUES (XMLType
4 ('<Relatie>
5 <Voornaam>Johan</Voornaam>
6 <Achternaam>Hermans</Achternaam>
7 <Tussenvoegsel/>
8 <Geboortedatum>1978-01-02</Geboortedatum>
9 <Geslacht>M</Geslacht>
10 <Sofinummer>233300417</Sofinummer>
11 <Straatnaam>Stationstraat</Straatnaam>
12 <Huisnummer>10</Huisnummer>
13 <Woonplaats>Weesp</Woonplaats>
14 <Postcode>1383 AK</Postcode>
15 <Zrn>1234567</Zrn>
16 </Relatie>'
17 ).CreateSchemaBasedXML(:schemaURL))
18 /
1 row created.
SQL> commit
2 /
Commit complete.
SQL> INSERT
2 INTO relatie_documenten
3 VALUES (XMLType
4 ('<Relatie>
5 <Voornaam>Johanna</Voornaam>
6 <Achternaam>Gurts</Achternaam>
7 <Tussenvoegsel/>
8 <Geboortedatum>1975-11-12</Geboortedatum>
9 <Geslacht>V</Geslacht>
10 <Sofinummer>234109807</Sofinummer>
11 <Straatnaam>Stationstraat</Straatnaam>
12 <Huisnummer>10</Huisnummer>
13 <Woonplaats>Weesp</Woonplaats>
14 <Postcode>1383 AK</Postcode>
15 <Zrn>7654321</Zrn>
16 </Relatie>').CreateSchemaBasedXML(:schemaURL))
17 /
1 row created.
SQL> commit
2 /
Commit complete.
SQL> INSERT
2 INTO relatie_documenten
3 VALUES (XMLType
4 ('<Relatie>
5 <Voornaam>Johanna</Voornaam>
6 <Achternaam>Gurts</Achternaam>
7 <Tussenvoegsel/>
8 <Geboortedatum>1975-11-12</Geboortedatum>
9 <Geslacht>O</Geslacht>
10 <Sofinummer>234109807</Sofinummer>
11 <Straatnaam>Stationstraat</Straatnaam>
12 <Huisnummer>10</Huisnummer>
13 <Woonplaats>Weesp</Woonplaats>
14 <Postcode>1383 AK</Postcode>
15 <Zrn>7654321</Zrn>
16 </Relatie>').CreateSchemaBasedXML(:schemaURL))
17 /
VALUES (XMLType
ERROR at line 3:
ORA-31038: Invalid enumeration value: "O"
ORA-06512: at "SYS.XMLTYPE", line 345
ORA-06512: at "SCOTT.UPO_RDT_AI", line 5
ORA-04088: error during execution of trigger 'SCOTT.UPO_RDT_AI'
SQL> commit
2 /
Commit complete.
SQL> declare
2 xmlschema xmltype;
3 res boolean;
4 begin
5 select xdburitype(:schemaPath).getXML()
6 into xmlSchema
7 from dual;
8 dbms_xdb.deleteResource(:schemaPath);
9 select insertChildXML
10 (
11 xmlschema,
12 '/xsd:schema//xsd:element[@name="Geslacht"]/xsd:simpleType/xsd:restriction',
13 'xsd:enumeration',
14 xmltype('<xsd:enumeration xmlns:xsd="http://www.w3.org/2001/XMLSchema" value="O"/>'),
15 'xmlns:xsd="http://www.w3.org/2001/XMLSchema"'
16 )
17 into xmlSchema
18 from dual;
19 res := dbms_xdb.createResource(:schemaPath,xmlSchema);
20 end;
21 /
PL/SQL procedure successfully completed.
SQL> commit
2 /
Commit complete.
SQL> set long 100000 pages 200 lines 140
SQL> --
SQL> select xdburitype(:schemaPath).getXML()
2 from dual
3 /
XDBURITYPE(:SCHEMAPATH).GETXML()
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" elementFormDefault="unqualified" attributeF
ormDefault="unqualified" version="1.0">
<xsd:element name="Relatie" xdb:defaultTable="">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name="Voornaam" type="xsd:string"/>
 <xsd:element name="Achternaam" type="xsd:string"/>
 <xsd:element name="Tussenvoegsel" type="xsd:string"/>
 <xsd:element name="Geboortedatum" type="xsd:date"/>
 <xsd:element name="Geslacht">
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:enumeration value="M"/>
 <xsd:enumeration value="V"/>
 <xsd:enumeration xmlns:xsd="http://www.w3.org/2001/XMLSchema" value="O"/>
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="Sofinummer">
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:pattern value="\d{9}"/>
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="Straatnaam" type="xsd:string"/>
 <xsd:element name="Huisnummer" type="xsd:string"/>
 <xsd:element name="Woonplaats" type="xsd:string"/>
 
 <xsd:element name="Postcode">
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:pattern value="\d{4} [A-Z]{2}"/>
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="Zrn">
 <xsd:simpleType>
 <xsd:restriction base="xsd:integer">
 <xsd:minInclusive value="1000000"/>
 <xsd:maxInclusive value="99999999999999"/>
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 </xsd:sequence>
 </xsd:complexType>
</xsd:element>
</xsd:schema>
SQL> DROP TABLE RELATIE_DOCUMENTEN_TEMP
2 /
Table dropped.
SQL> BEGIN
2 DBMS_XMLSCHEMA.copyEvolve
3 ( schemaURLs => xdb$string_list_t(:schemaURL)
4 , newSchemas => XMLSequenceType(XDBURIType(:schemaPath).getXML())
5 , preserveOldDocs => TRUE
6 , mapTabName => 'RELATIE_DOCUMENTEN_TEMP'
7 , generateTables => FALSE
8 );
9 END;
10 /
PL/SQL procedure successfully completed.
SQL> CREATE TABLE relatie_documenten OF XMLTYPE
2 XMLSCHEMA "http://localhost:8080/xsd/relaties.xsd"
3 ELEMENT "Relatie"
4 /
Table created.
SQL> CREATE OR REPLACE TRIGGER upo_rdt_ai
2 AFTER INSERT ON relatie_documenten
3 FOR EACH ROW
4 DECLARE
5 doc XMLType;
6 BEGIN
7 doc := :new.SYS_NC_ROWINFO$;
8 XMLType.schemaValidate(doc);
9 END;
10 /
Trigger created.
SQL> declare
2 tablename varchar2(2000);
3 begin
4 select temp_tabname
5 into tablename
6 from RELATIE_DOCUMENTEN_TEMP
7 where table_name = USER || '.' || upper('relatie_documenten');
8 execute immediate 'insert into relatie_documenten select xmltype(data) from ' || tablename;
9 commit;
10 end;
11 /
PL/SQL procedure successfully completed.
SQL> select *
2 from relatie_documenten
3 /
SYS_NC_ROWINFO$
<Relatie>
<Voornaam>Johan</Voornaam>
<Achternaam>Hermans</Achternaam>
<Tussenvoegsel/>
<Geboortedatum>1978-01-02</Geboortedatum>
<Geslacht>M</Geslacht>
<Sofinummer>233300417</Sofinummer>
<Straatnaam>Stationstraat</Straatnaam>
<Huisnummer>10</Huisnummer>
<Woonplaats>Weesp</Woonplaats>
<Postcode>1383 AK</Postcode>
<Zrn>1234567</Zrn>
</Relatie>
<Relatie>
<Voornaam>Johanna</Voornaam>
<Achternaam>Gurts</Achternaam>
<Tussenvoegsel/>
<Geboortedatum>1975-11-12</Geboortedatum>
<Geslacht>V</Geslacht>
<Sofinummer>234109807</Sofinummer>
<Straatnaam>Stationstraat</Straatnaam>
<Huisnummer>10</Huisnummer>
<Woonplaats>Weesp</Woonplaats>
<Postcode>1383 AK</Postcode>
<Zrn>7654321</Zrn>
</Relatie>
SQL> INSERT
2 INTO relatie_documenten
3 VALUES (XMLType
4 ('<Relatie>
5 <Voornaam>Johanna</Voornaam>
6 <Achternaam>Gurts</Achternaam>
7 <Tussenvoegsel/>
8 <Geboortedatum>1975-11-12</Geboortedatum>
9 <Geslacht>O</Geslacht>
10 <Sofinummer>234109807</Sofinummer>
11 <Straatnaam>Stationstraat</Straatnaam>
12 <Huisnummer>10</Huisnummer>
13 <Woonplaats>Weesp</Woonplaats>
14 <Postcode>1383 AK</Postcode>
15 <Zrn>7654321</Zrn>
16 </Relatie>').CreateSchemaBasedXML(:schemaURL))
17 /
1 row created.
SQL> commit
2 /
Commit complete.
SQL> select *
2 from relatie_documenten
3 /
SYS_NC_ROWINFO$
<Relatie>
<Voornaam>Johan</Voornaam>
<Achternaam>Hermans</Achternaam>
<Tussenvoegsel/>
<Geboortedatum>1978-01-02</Geboortedatum>
<Geslacht>M</Geslacht>
<Sofinummer>233300417</Sofinummer>
<Straatnaam>Stationstraat</Straatnaam>
<Huisnummer>10</Huisnummer>
<Woonplaats>Weesp</Woonplaats>
<Postcode>1383 AK</Postcode>
<Zrn>1234567</Zrn>
</Relatie>
<Relatie>
<Voornaam>Johanna</Voornaam>
<Achternaam>Gurts</Achternaam>
<Tussenvoegsel/>
<Geboortedatum>1975-11-12</Geboortedatum>
<Geslacht>V</Geslacht>
<Sofinummer>234109807</Sofinummer>
<Straatnaam>Stationstraat</Straatnaam>
<Huisnummer>10</Huisnummer>
<Woonplaats>Weesp</Woonplaats>
<Postcode>1383 AK</Postcode>
<Zrn>7654321</Zrn>
</Relatie>
<Relatie>
<Voornaam>Johanna</Voornaam>
<Achternaam>Gurts</Achternaam>
<Tussenvoegsel/>
<Geboortedatum>1975-11-12</Geboortedatum>
<Geslacht>O</Geslacht>
<Sofinummer>234109807</Sofinummer>
<Straatnaam>Stationstraat</Straatnaam>
<Huisnummer>10</Huisnummer>
<Woonplaats>Weesp</Woonplaats>
<Postcode>1383 AK</Postcode>
<Zrn>7654321</Zrn>
</Relatie>
SQL>Here's the SQL, can you cut'n'paste and run the whole thing as XML_OWNER
var schemaURL varchar2(256)
var schemaPath varchar2(256)
begin
:schemaURL := 'http://localhost:8080/xsd/relaties.xsd';
:schemaPath := '/public/relaties.xsd';
end;
call dbms_xmlSchema.deleteSchema(:schemaURL,4)
declare
res boolean;
xmlSchema xmlType := xmlType(
'<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
 xmlns:xdb="http://xmlns.oracle.com/xdb"
 elementFormDefault="unqualified"
 attributeFormDefault="unqualified"
 version="1.0">
 <xsd:element name="Relatie" xdb:defaultTable="">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name="Voornaam" type="xsd:string"/>
 <xsd:element name="Achternaam" type="xsd:string"/>
 <xsd:element name="Tussenvoegsel" type="xsd:string"/>
 <xsd:element name="Geboortedatum" type="xsd:date"/>
 <xsd:element name="Geslacht">
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:enumeration value="M"/>
 <xsd:enumeration value="V"/>
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="Sofinummer">
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:pattern value="\d{9}"/>
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="Straatnaam" type="xsd:string"/>
 <xsd:element name="Huisnummer" type="xsd:string"/>
 <xsd:element name="Woonplaats" type="xsd:string"/>
 
 <xsd:element name="Postcode">
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:pattern value="\d{4} [A-Z]{2}"/>
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="Zrn">
 <xsd:simpleType>
 <xsd:restriction base="xsd:integer">
 <xsd:minInclusive value="1000000"/>
 <xsd:maxInclusive value="99999999999999"/>
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
</xsd:schema>');
begin
if (dbms_xdb.existsResource(:schemaPath)) then
 dbms_xdb.deleteResource(:schemaPath);
end if;
res := dbms_xdb.createResource(:schemaPath,xmlSchema);
end;
BEGIN
DBMS_XMLSCHEMA.registerSchema(
 :schemaURL,
 XDBURIType(:schemaPath).getClob(),
 TRUE,
 FALSE,
 FALSE,
 TRUE);
END;
DROP TABLE relatie_documenten FORCE
CREATE TABLE relatie_documenten OF XMLTYPE
 XMLSCHEMA "http://localhost:8080/xsd/relaties.xsd"
 ELEMENT "Relatie"
CREATE OR REPLACE TRIGGER upo_rdt_ai
AFTER INSERT ON relatie_documenten
FOR EACH ROW
DECLARE
 doc XMLType;
BEGIN
 doc := :new.SYS_NC_ROWINFO$;
 XMLType.schemaValidate(doc);
END;
INSERT
INTO relatie_documenten
VALUES (XMLType
 ('<Relatie>
 <Voornaam>Johan</Voornaam>
 <Achternaam>Hermans</Achternaam>
 <Tussenvoegsel/>
 <Geboortedatum>1978-01-02</Geboortedatum>
 <Geslacht>M</Geslacht>
 <Sofinummer>233300417</Sofinummer>
 <Straatnaam>Stationstraat</Straatnaam>
 <Huisnummer>10</Huisnummer>
 <Woonplaats>Weesp</Woonplaats>
 <Postcode>1383 AK</Postcode>
 <Zrn>1234567</Zrn>
 </Relatie>'
 ).CreateSchemaBasedXML(:schemaURL))
commit
INSERT
INTO relatie_documenten
VALUES (XMLType
 ('<Relatie>
 <Voornaam>Johanna</Voornaam>
 <Achternaam>Gurts</Achternaam>
 <Tussenvoegsel/>
 <Geboortedatum>1975-11-12</Geboortedatum>
 <Geslacht>V</Geslacht>
 <Sofinummer>234109807</Sofinummer>
 <Straatnaam>Stationstraat</Straatnaam>
 <Huisnummer>10</Huisnummer>
 <Woonplaats>Weesp</Woonplaats>
 <Postcode>1383 AK</Postcode>
 <Zrn>7654321</Zrn>
 </Relatie>').CreateSchemaBasedXML(:schemaURL))
commit
INSERT
INTO relatie_documenten
VALUES (XMLType
 ('<Relatie>
 <Voornaam>Johanna</Voornaam>
 <Achternaam>Gurts</Achternaam>
 <Tussenvoegsel/>
 <Geboortedatum>1975-11-12</Geboortedatum>
 <Geslacht>O</Geslacht>
 <Sofinummer>234109807</Sofinummer>
 <Straatnaam>Stationstraat</Straatnaam>
 <Huisnummer>10</Huisnummer>
 <Woonplaats>Weesp</Woonplaats>
 <Postcode>1383 AK</Postcode>
 <Zrn>7654321</Zrn>
 </Relatie>').CreateSchemaBasedXML(:schemaURL))
commit
declare
xmlschema xmltype;
res boolean;
begin
select xdburitype(:schemaPath).getXML()
 into xmlSchema
 from dual;
dbms_xdb.deleteResource(:schemaPath);
select insertChildXML
 xmlschema,
 '/xsd:schema//xsd:element[@name="Geslacht"]/xsd:simpleType/xsd:restriction',
 'xsd:enumeration',
 xmltype('<xsd:enumeration xmlns:xsd="http://www.w3.org/2001/XMLSchema" value="O"/>'),
 'xmlns:xsd="http://www.w3.org/2001/XMLSchema"'
into xmlSchema
from dual;
res := dbms_xdb.createResource(:schemaPath,xmlSchema);
end;
commit
set long 100000 pages 200 lines 140
select xdburitype(:schemaPath).getXML()
from dual
DROP TABLE RELATIE_DOCUMENTEN_TEMP
BEGIN
DBMS_XMLSCHEMA.copyEvolve
 ( schemaURLs => xdb$string_list_t(:schemaURL)
 , newSchemas => XMLSequenceType(XDBURIType(:schemaPath).getXML())
 , preserveOldDocs => TRUE
 , mapTabName => 'RELATIE_DOCUMENTEN_TEMP'
 , generateTables => FALSE
END;
CREATE TABLE relatie_documenten OF XMLTYPE
 XMLSCHEMA "http://localhost:8080/xsd/relaties.xsd"
 ELEMENT "Relatie"
CREATE OR REPLACE TRIGGER upo_rdt_ai
AFTER INSERT ON relatie_documenten
FOR EACH ROW
DECLARE
 doc XMLType;
BEGIN
 doc := :new.SYS_NC_ROWINFO$;
 XMLType.schemaValidate(doc);
END;
declare
tablename varchar2(2000);
begin
select temp_tabname
 into tablename
 from RELATIE_DOCUMENTEN_TEMP
 where table_name = USER || '.' || upper('relatie_documenten');
execute immediate 'insert into relatie_documenten select xmltype(data) from ' || tablename;
commit;
end;
select *
from relatie_documenten
INSERT
INTO relatie_documenten
VALUES (XMLType
 ('<Relatie>
 <Voornaam>Johanna</Voornaam>
 <Achternaam>Gurts</Achternaam>
 <Tussenvoegsel/>
 <Geboortedatum>1975-11-12</Geboortedatum>
 <Geslacht>O</Geslacht>
 <Sofinummer>234109807</Sofinummer>
 <Straatnaam>Stationstraat</Straatnaam>
 <Huisnummer>10</Huisnummer>
 <Woonplaats>Weesp</Woonplaats>
 <Postcode>1383 AK</Postcode>
 <Zrn>7654321</Zrn>
 </Relatie>').CreateSchemaBasedXML(:schemaURL))
commit
select *
from relatie_documenten
/

Could not create XML document carrying AQ Headers

Similar Messages

Maybe you are looking for