Error on propagation

I am trying to setup propagation from a queue on one database, to a queue on a different database. Both instances are 9.2.0.6 on HP-UX.
Job_queue_processes is set to 7 and aq_tm_processes is set to 1.
When I add a propagation schedule I get an error in the alter logs (no messages are propagated):-
*** SESSION ID:(32.933) 2005-09-21 11:14:56.539
kwqjaq: Exception Occured
kwqjschupd: schedule not found, unschedule assumed
*** 2005-09-21 11:14:56.546
ORA-12012: error on auto execute of job 392
ORA-06512: at "SYS.DBMS_AQADM_SYS", line 5636
ORA-06512: at "SYS.DBMS_AQADM_SYS", line 6061
ORA-06512: at "SYS.DBMS_AQADM", line 895
ORA-06512: at line 1
Has anyone got any idea what is causing this?
Thanks.

Check to ensure that your propagation subscriber is correctly set up.
select * from AQ$_<queue_table_name>_S;
You should be able to detect the differences between your local and propagation subscribers.

Similar Messages

Error during propagation process in streaming

I am getting following error during propagation
ORA-12170: TNS:Connect timeout occurred ORA-12170: TNS:Connect timeout occurred
In order to resolve this i add following lines in sqlnet.ora on both nodes, but problem is still there....
SQLNET.SEND_TIMEOUT=300
SQLNET.RECV_TIMEOUT=300
SQLNET.INBOUND_CONNECT_TIMEOUT=300
SQLNET.DEFAULT_SDU_SIZE=32767
SQLNET.RECV_BUFF_SIZE=655336
SQLNET.SEND_BUF_SIZE=65536Need your help in resolving this issue........

Hi,
What is Resp. Resolver Name and Decision Type in your Process Level Definition? Did you create custom agent BADI implementation?
Regards,
Masa

ERROR: The Propagation operation ended in error. java.lang.reflect.Undeclar

Dear all,
i am using bea weblogic 10.0 ant i am downloading the running Inventory.
but the below problem occurc when i run ant task for downloading that is
ant -buildfile propagation_ant.xml downloadSrc the below problem occurs. i am new to bea so how can i debug the problem
VERBOSE: InventoryTreeWalker: visiting node: Application:ContentServices:BEA Repository:ContentNodes:Webmasters:Sports:I won`t step down from presidency Khan.txt
ERROR: The Propagation operation ended in error.
java.lang.reflect.UndeclaredThrowableException
at weblogic.security.providers.xacml.authorization.XACMLAuthorizerMBeanImpl.policyExists(XACMLAuthorizerMBeanImpl.java:245)
at sun.reflect.GeneratedMethodAccessor477.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.bea.p13n.security.internal.SecurityProviderProxy.invoke(SecurityProviderProxy.java:48)
at $Proxy54.policyExists(Unknown Source)
at com.bea.p13n.entitlements.management.internal.SecurityPolicyDelegate$3.run(SecurityPolicyDelegate.java:241)
at com.bea.p13n.entitlements.management.internal.SecurityPolicyDelegate$3.run(SecurityPolicyDelegate.java:239)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at com.bea.p13n.entitlements.management.internal.SecurityPolicyDelegate.kernelRunAs(SecurityPolicyDelegate.java:433)
at com.bea.p13n.entitlements.management.internal.SecurityPolicyDelegate.policyExists(SecurityPolicyDelegate.java:246)
at com.bea.p13n.entitlements.management.internal.RDBMSSecurityPolicyManager.getSecurityPolicy(RDBMSSecurityPolicyManager.java:204)
at com.bea.p13n.entitlements.management.SecurityPolicyManager.getSecurityPolicy(SecurityPolicyManager.java:119)
at com.bea.propagation.content.online.util.SecurityHelper.getSecurityPolicy(SecurityHelper.java:146)
at com.bea.propagation.content.online.util.SecurityHelper.getSecurityPolicies(SecurityHelper.java:122)
at com.bea.propagation.content.online.hierarchy.ContentNodeHierarchy.discoverChildren(ContentNodeHierarchy.java:113)
at com.bea.propagation.framework.hierarchy.ListNodeHierarchy.getChildrenNodes(ListNodeHierarchy.java:113)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst_Recur(InventoryTreeWalker.java:215)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst_Recur(InventoryTreeWalker.java:224)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst_Recur(InventoryTreeWalker.java:224)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst_Recur(InventoryTreeWalker.java:224)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst_Recur(InventoryTreeWalker.java:224)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst_Recur(InventoryTreeWalker.java:224)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst_Recur(InventoryTreeWalker.java:224)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst(InventoryTreeWalker.java:158)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst(InventoryTreeWalker.java:102)
at com.bea.propagation.framework.tool.io.InventoryTreeExport.walkDepthFirst(InventoryTreeExport.java:88)
at com.bea.propagation.framework.tool.io.InventoryFolderExport.walkDepthFirst(InventoryFolderExport.java:110)
at com.bea.propagation.framework.tool.io.InventoryArchiveExport.walkDepthFirst(InventoryArchiveExport.java:103)
at com.bea.propagation.framework.tool.servlet.InventoryManagementServlet.writeInventoryToLocalFile(InventoryManagementServlet.java:1017)
at com.bea.propagation.framework.tool.servlet.InventoryManagementServlet.writeInventoryToLocalFile(InventoryManagementServlet.java:991)
at com.bea.propagation.framework.tool.servlet.InventoryManagementServlet.downloadOperation_Remote(InventoryManagementServlet.java:510)
at com.bea.propagation.framework.tool.servlet.InventoryManagementServlet.downloadOperation(InventoryManagementServlet.java:453)
at com.bea.propagation.framework.tool.servlet.InventoryManagementServlet.doService(InventoryManagementServlet.java:318)
at com.bea.propagation.framework.tool.servlet.InventoryManagementServlet.doPost(InventoryManagementServlet.java:199)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:315)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3393)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
ERROR: The Propagation operation ended in error.
java.lang.reflect.UndeclaredThrowableException
at weblogic.security.providers.xacml.authorization.XACMLAuthorizerMBeanImpl.policyExists(XACMLAuthorizerMBeanImpl.java:245)
at sun.reflect.GeneratedMethodAccessor477.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.bea.p13n.security.internal.SecurityProviderProxy.invoke(SecurityProviderProxy.java:48)
at $Proxy54.policyExists(Unknown Source)
at com.bea.p13n.entitlements.management.internal.SecurityPolicyDelegate$3.run(SecurityPolicyDelegate.java:241)
at com.bea.p13n.entitlements.management.internal.SecurityPolicyDelegate$3.run(SecurityPolicyDelegate.java:239)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at com.bea.p13n.entitlements.management.internal.SecurityPolicyDelegate.kernelRunAs(SecurityPolicyDelegate.java:433)
at com.bea.p13n.entitlements.management.internal.SecurityPolicyDelegate.policyExists(SecurityPolicyDelegate.java:246)
at com.bea.p13n.entitlements.management.internal.RDBMSSecurityPolicyManager.getSecurityPolicy(RDBMSSecurityPolicyManager.java:204)
at com.bea.p13n.entitlements.management.SecurityPolicyManager.getSecurityPolicy(SecurityPolicyManager.java:119)
at com.bea.propagation.content.online.util.SecurityHelper.getSecurityPolicy(SecurityHelper.java:146)
at com.bea.propagation.content.online.util.SecurityHelper.getSecurityPolicies(SecurityHelper.java:122)
at com.bea.propagation.content.online.hierarchy.ContentNodeHierarchy.discoverChildren(ContentNodeHierarchy.java:113)
at com.bea.propagation.framework.hierarchy.ListNodeHierarchy.getChildrenNodes(ListNodeHierarchy.java:113)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst_Recur(InventoryTreeWalker.java:215)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst_Recur(InventoryTreeWalker.java:224)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst_Recur(InventoryTreeWalker.java:224)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst_Recur(InventoryTreeWalker.java:224)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst_Recur(InventoryTreeWalker.java:224)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst_Recur(InventoryTreeWalker.java:224)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst_Recur(InventoryTreeWalker.java:224)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst(InventoryTreeWalker.java:158)
at com.bea.propagation.framework.InventoryTreeWalker.walkDepthFirst(InventoryTreeWalker.java:102)
at com.bea.propagation.framework.tool.io.InventoryTreeExport.walkDepthFirst(InventoryTreeExport.java:88)
at com.bea.propagation.framework.tool.io.InventoryFolderExport.walkDepthFirst(InventoryFolderExport.java:110)
at com.bea.propagation.framework.tool.io.InventoryArchiveExport.walkDepthFirst(InventoryArchiveExport.java:103)
at com.bea.propagation.framework.tool.servlet.InventoryManagementServlet.writeInventoryToLocalFile(InventoryManagementServlet.java:1017)
at com.bea.propagation.framework.tool.servlet.InventoryManagementServlet.writeInventoryToLocalFile(InventoryManagementServlet.java:991)
at com.bea.propagation.framework.tool.servlet.InventoryManagementServlet.downloadOperation_Remote(InventoryManagementServlet.java:510)
at com.bea.propagation.framework.tool.servlet.InventoryManagementServlet.downloadOperation(InventoryManagementServlet.java:453)
at com.bea.propagation.framework.tool.servlet.InventoryManagementServlet.doService(InventoryManagementServlet.java:318)
at com.bea.propagation.framework.tool.servlet.InventoryManagementServlet.doPost(InventoryManagementServlet.java:199)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:315)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3393)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)

your error seems to indicate that your embeddedLdap isnt in sync with the Database ? Did you either delete files from your file systems or cleanup the portal db or finally used a copy of some existing database for your domain?

ESB errors not propagating to BPEL process

I am working in SOA Suite 10.1.3.3. I have an asynchronous BPEL process that is orchestrating a number of ESB services, most of which perform database operations. Occasionally an attempt is made to insert a record into a table which results in an error (e.g., null value inserted into a non-null field, record already exists, non-existent record in parent table upon which current table depends, etc.). This correctly results in an error in the ESB service that shows up in the ESB Control console.
The problem is that the error is NOT propagated upward to the invoking BPEL process (which contains all manner of fault catching branches to process the error, log it, send email notifications, and perform other database operations dependent upon the success or failure of the ESB operations). The BPEL process is therefore left "hanging" and never appears in the BPEL Control console as an instance. It shows up in the Manual Recovery queue as an essentially unrecoverable process.
I am assuming that this change in behavior (such errors formerly propagated to the calling BPEL) is a direct result of the new Fault Handling Framework. My question is: what do I have to do in order to restore the original behavior of the system (ESB service encounters an error and propagates the fault to the async BPEL process, which catches it and does whatever it needs to do to fulfill the requirements of the overall system)? Is this something that can be handled by changes to the BPEL/ESB system configuration, the BPEL process definition, the ESB service definitions, or some combination thereof?
Thanks for your time.
Paul Camann

Hello. We applied 10.1.3.3.1 MLR14 in late October 2008.
We are seeing large numbers of errors like this in the ESB log ($ORACLE_HOME/j2ee/oc4j_soa/log/oc4j_soa_default_group_1/oc4j/log.xml):
<MESSAGE>
<HEADER>
<TSTZ_ORIGINATING>2009-01-26T13:11:15.497-05:00</TSTZ_ORIGINATING>
<COMPONENT_ID>tip</COMPONENT_ID>
<MSG_TYPE TYPE="ERROR"></MSG_TYPE>
<MSG_LEVEL>1</MSG_LEVEL>
<HOST_ID>biwsvlbat027.gdbiw.com</HOST_ID>
<HOST_NWADDR>1.2.3.4</HOST_NWADDR>
<MODULE_ID>esb.server.service.impl.soap</MODULE_ID>
<THREAD_ID>98</THREAD_ID>
<USER_ID>oracle</USER_ID>
<SUPPL_ATTRS>
<ATTR NAME="J2EE_MODULE.name">provider-war</ATTR>
<ATTR NAME="J2EE_APP.name">esb-rt</ATTR>
<ATTR
NAME="WEBSERVICE_PORT.name">__soap_Router_ODS_STAGE_Insert_ODS_STAGE_I_PortType</ATTR>
<ATTR NAME="WEBSERVICE.name">ESB_Router_ODS_STAGE_Insert_Service</ATTR>
</SUPPL_ATTRS>
</HEADER>
<CORRELATION_DATA>
<EXEC_CONTEXT_ID><UNIQUE_ID>1232993475:1.2.3.4:7097:0:307</UNIQUE_ID><SEQ>5</SEQ></EXEC_CONT
EXT_ID>
</CORRELATION_DATA>
<PAYLOAD>
<MSG_TEXT>Exception while print response</MSG_TEXT>
<SUPPL_DETAIL><![CDATA[java.lang.NullPointerException
at oracle.tip.esb.server.service.impl.soap.EventOracleSoapProvider.processMessage
(EventOracleSoapProvider.java:215)
at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing
(ProviderProcessor.java:956)
at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation
(WebServiceProcessor.java:349)
at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing
(ProviderProcessor.java:466)
at oracle.j2ee.ws.server.WebServiceProcessor.processRequest
(WebServiceProcessor.java:114)
at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:96)
at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:177)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ServletRequestDispatcher.invoke
(ServletRequestDispatcher.java:713)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal
(ServletRequestDispatcher.java:370)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest
(HttpRequestHandler.java:871)
at com.evermind.server.http.HttpRequestHandler.processRequest
(HttpRequestHandler.java:453)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:302)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run
(ServerSocketReadHandler.java:260)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run
(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)
]]></SUPPL_DETAIL>
</PAYLOAD>
</MESSAGE>
which is possibly the message that would come back from ESB to BPEL failing?
Thank you.

How to remove error from propagation and verify replication is ok?

Have a one-way schema level streams setup and the target DB is 3-node RAC (named PDAMLPR1). I run a large insert at source DB (35million rows). After committing on source, I made a failure test on the target DB by shutting down the entire database. The streams seems stopped as the heartbeat table sequence (it inserts a row each min) on target is still reflecting last night. We get the error in the dba_propagation:
ORA-02068: following severe error from PDAMLPR1
ORA-01033: ORACLE initialization or shutdown in progress
ORA-06512: at "SYS.DBMS_AQADM_SYS", line 1087
ORA-06512: at "SYS.DBMS_AQADM_SYS", line 7639
ORA-06512: at "SYS.DBMS_AQADM", line 631
ORA-06512: at line 1
08-FEB-10
while capture, propagation, and apply are all in enabled status. I restarted capture and propagation at source DB. But still see the error message above. My questions are:
1. How to delete the error from dba_propagation?
2. How to verify the streams is still running fine?
In normal test, during such large insert, the heartbeat table added a row in an hour. Very slow.
thanks for advice.

Well, if I can give you my point of view: I think that 35 millions LCR is totally unreasonnable. Did you really post a huge insert of 35 millions then committed that single utterly huge transaction? Don't be surprised it's going to work very very hard for a while!
With a default setup, Oracle recommends to commit every 1000 LCR (row change).
There are ways to tune Streams for large transaction but I have not done so personnaly. Look on Metalink, you will find information about that (mostly documents id 335516.1, 365648.1 and 730036.1).
One more thing: you mentionned about a failure test. Your target database is RAC. Did you read about queue ownership? queue_to_queue propagation? You might have an issue related to that.
How did you setup your environment? Did you give enough streams_pool_size? You can watch V$STREAMS_POOL_ADVICE to check what Oracle think is good for your workload.
If you want to skip the transaction, you can remove the table rule or use the IGNORETRANSACTION apply parameter.
Hope it helps
Regards,

Error Cluster Propagation Issue

Consider the following diagram:
This VI is intended to be used in a chain of VIs.
This VI copies a file to a folder, and in case of error, tries with another path of the file (located in a "backup" location)
Due to the intrinsic dataflow programming model, how can I manage the error in the arrow place????
The behaviour I want is this:
if (error in == true) --> skips all and propagates error_in to error_out
else { try to copy, and in case of error try with backup copy. If errors again then report the error (custom error code) }
Is it possible???
thanks
Solved!
Go to Solution.

thanks all,
the note about the "lost warning" was really interesting, I never noticed it because I never used warning.
I discovered another source of bug.
Consider the following:
If error_in is true, the error_out would be false.
The reason is that the filename array is EMPTY and the for case is never executed, so error_out takes a default value.
As a consequence the error is not correctly propagated.
I think this is not trivial to see at a first glance.

Error Icon Propagation

When I have an error in my Actionscript, I get a nice red X
next to the the line where the error occurred. Unfortunately,
unlike in an Eclipse Java project, the file tab does not show an
error icon, nor does the navigator. Can someone suggest how to
enable this functionality?
thanks
PS. perhaps I am expecting more from flex in Eclipse, but as
an Eclipse user for Java Programming, are many of the nice features
not going to be present?

Check to ensure that your propagation subscriber is correctly set up.
select * from AQ$_<queue_table_name>_S;
You should be able to detect the differences between your local and propagation subscribers.

Error details propagation among proxies

Hi all,
I've a question about how to propagate back error details from one proxy to another.
I've setup a simple alsb project:
- proxyA that calls proxyB
- proxyB a local proxy with only one stage where there is a 'raise error' action with a custom error code & message
In proxyB I've also added a service error handler only for tracing what error has been raised.
In proxyA I've also added a service error handler where I would like to catch error raised by proxyB and get details about the error raised by proxyB.
From log file I see:
####<Sep 11, 2007 1:04:31 PM CEST> <Error> < [null, null, null, ERROR] ERROR catched in proxyB: <fault xmlns="http://www.bea.com/wli/sb/context">
<errorCode>999</errorCode>
<reason>error in proxyB</reason>
<location>
<node>ProxyB-Pipeline</node>
<pipeline>ProxyB-Pipeline_request</pipeline>
<stage>stage1</stage>
<path>request-pipeline</path>
</location>
</fault>>
####<Sep 11, 2007 1:04:31 PM CEST> <Error> < [null, null, null, ERROR] ERROR catched in proxyA: <event-bus:fault xmlns:event-bus="http://www.bsource.ch/EventBus" xmlns="http://www.bea.com/wli/sb/context" xmlns:con="http://www.bea.com/wli/sb/stages/transform/config">
<event-bus:fault>
<errorCode>BEA-382502</errorCode>
<reason>ALSB Service Callout action received an error response</reason>
<details>
<con:ErrorResponseDetail/> // I'm wondering how to get here details about the error raised by proxyB
</details>
<location>
<node>ProxyA-Pipeline</node>
<pipeline>ProxyA-Pipeline_request</pipeline>
<stage>callout to ProxyB</stage>
<path>request-pipeline</path>
</location>
</event-bus:fault>
<event-bus:body>
<test xmlns="">ciao</test>
</event-bus:body>
</event-bus:fault>>
Do you have any idea?
Thanks in advance
ferp

We filed a CR to address the soap fault propagation from one proxy to another and we got confirmation from engineering that it is work as designed. As a workaround, if you want to get the actual cause, you need to get that from fault (by replacing the body with fault in the error handler of proxy A).
For eg. In your process A error handler, you can do the following.
Replace [ node contents ] of [ . ] in [ body ] with [ $fault ]
and you will get the following output.
<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
     <con:errorCode>BEA-382502</con:errorCode>
     <con:reason>
     ALSB Service Callout action received an error response
     </con:reason>
     <con:details>
     <con1:ErrorResponseDetail
xmlns:con1="http://www.bea.com/wli/sb/stages/transform/config">
     <con1:detail>
     <con:fault xmlns:con="http://www.bea.com/wli/sb/context">
     <con:errorCode>BEA-382515</con:errorCode>
     <con:reason>[ALSB Transform:382515]Callout to java method "public
static void com.bea.test.TestJavaCallout.throwException() throws
java.lang.Exception" resulted in exception: Exception raised
here........:</con:reason>
     <con:location>
     <con:node>PipelinePairNode1</con:node>
     <con:pipeline>PipelinePairNode1_request</con:pipeline>
     <con:stage>Java Callout</con:stage>
     <con:path>request-pipeline</con:path>
     </con:location>
     </con:fault>
     </con1:detail>
     </con1:ErrorResponseDetail>
     </con:details>
     <con:location>
     <con:node>PipelinePairNode1</con:node>
     <con:pipeline>PipelinePairNode1_request</con:pipeline>
     <con:stage>stage1</con:stage>
     <con:path>request-pipeline</con:path>
     </con:location>
     </con:fault>
The actual fault will be wrapped into the con1:detail. Hope this helps.
Thanks,
Muthu.

Error in propagation -- ORA-02019

Hi All,
i have setup streams replications at db level and it is wroked fine for 1 day after that it has stopped working and when i checked in dba_propatation i am getting error like this
SQL> select propagation_name, destination_dblink, status, error_date, error_message from dba_propagation;
PROPAGATION_NAME DESTINATION_DBLINK STATUS ERROR_MESSAGE
STRMADMIN_PROP SABLINE1 ENABLED ORA-02019: connection description for remote database not found
AND MY DB LINKS ARE
SQL>select db_link,owner from dba_db_links;
DB_LINK OWNER
SABLINE1 PUBLIC
SABLINE1 STRMADMIN
and TNS ENTRIES IS
[oracle@dataguard2 admin]$ more tnsnames.ora
sabline=
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 172.16.1.75)(PORT = 1521))
(CONNECT_DATA =
(SID = sabline)
SABLINE1 =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = VM-VJ-TEST-002.infotechdev.dev)(PORT =
1521))
(CONNECT_DATA =
(SERVICE_NAME = sabline1)
can you please guide me what is the reason for getting the above error

Streams requires the usage of GLOBAL_NAME=TRUE. You must create a tns entry with the db_name + domain name and your dblink name must have the same global name for the target DB.
Source db_name = SRC.domain.com
target db_name = TRG.domain.com
DB link name created by strmadmin and used by strmadmin on SRC:
create database link TRG.domain.com connect to STRMADMIN identified by STRMADMIN using 'TRG.domain.com'
And in your tnsnames.ora you must have:
TRG, TRG.domain.com = ....
In your setup, obviously the global_name is not used.

Streams propagation error

I have 2 Oracle 11.2 standard edition databases and I am attempting to perform synchronous capture replication from one to the other.
I have a propagation rule created with:
begin
DBMS_STREAMS_ADM.ADD_TABLE_PROPAGATION_RULES(
table_name => 'duptest.test1',
streams_name => 'send_test1',
source_queue_name => 'strmadmin.streams_capt_q',
destination_queue_name => '[email protected]',
include_dml => true,
include_ddl => false,
inclusion_rule => true);
end;
As stradmin on the source database I can query the streams_apply_q_table at orac11g.world (the destination database).
However the propagation fails and produces a job trace file stating:
kwqpdest: exception 24033
kwqpdest: Error 24033 propagating to "STRMADMIN"."STREAMS_APPLY_Q"
94272890B6B600FFE040007F01006D4C
Can anyone suggest what is wrong and how to fix this?

Paul,
The capture process is:
BEGIN
DBMS_STREAMS_ADM.ADD_TABLE_RULES(
table_name => 'duptest.test1',
streams_type => 'sync_capture',
streams_name => 'sync_capture',
queue_name => 'streams_capt_q');
END;
The apply process on the destination database is:
begin
dbms_apply_adm.create_apply(
queue_name => 'streams_apply_q',
apply_name => 'sync_apply',
apply_captured => false,
source_database => 'ORALIN1');
end;
begin
dbms_streams_adm.add_table_rules(
table_name => 'duptest.test1',
streams_type => 'apply',
streams_name => 'sync_apply',
queue_name => 'streams_apply_q',
include_dml => true,
include_ddl => false,
include_tagged_lcr => false,
source_database => 'ORALIN1',
inclusion_rule => true);
end;
There is an entry in the AQ$_STREAMS_CAPT_Q_TABLE_E table, and no entries in dba_apply_error or streams_apply_q_table so I am assuming that the message does not make it to the destination queue.
I have been assuming that the propagation and apply steps are independent. I.e. The apply queue separates the propagation activity from the apply activity. Is this wrong?
Thanks

Propagation Problem

Hi
i am trying to propagate message from a queue in 8i database to a queue in 9i database.The problem is that i can see the message being enqueued in 8i database but the 9i queue is always empty.Is there any problem with propagation.How can i check if there are some errors during propagation?

I've done it with 8.1.7.4 and 9.2.0.6 in both directions
with event scheduling (in ora8i i realized it by myself because it is a 9i feature)
and it is working now for half a year in production at customers site!
so, what have you tried in detail?

Propagation not working. Basic Question.

Hi,
I was trying to setup Replication between 2 Oracle 10g Enterprise Editions installed on 2 different machines using Oracle Streams. While Installing the 2 databases I created the first database with the name source and the other with name target.
global_names is set to true:
alter system set global_names=true;
Created the user strmadmin in both the databases and created the tables EMP_SOURCE in the source database and EMP_TARGET in target database.
Setup the links as below:
CREATE DATABASE LINK target CONNECT TO strmadmin IDENTIFIED BY strmadmin USING *'target'*;
CREATE DATABASE LINK source CONNECT TO strmadmin IDENTIFIED BY strmadmin USING *'source'*;
Tested that the DB Links works in both the databases giving results back.
select * from strmadmin.EMP_SOURCE@source;
select * from strmadmin.EMP_TARGET@target;
select * from [email protected]
select * from [email protected]
I then go to setup the capture, propogation and apply process. The capture and apply process seem ok however the propogation process is throwing the error as below:
Propagation Process:
BEGIN
DBMS_STREAMS_ADM.ADD_TABLE_PROPAGATION_RULES(
table_name => 'strmadmin.EMP_SOURCE',
streams_name => 'strm01_propagation',
source_queue_name => 'strmadmin.source_queue',
destination_queue_name => *'strmadmin.target_queue@target'*,
include_dml => true,
include_ddl => true,
source_database => *'source'*,
inclusion_rule => true,
queue_to_queue => true);
END;
Error thrown:
Propagation Schedule for (STRMADMIN.SOURCE_QUEUE, "STRMADMIN"."TARGET_QUEUE"@TARGET.REGRESS.RDBMS.DEV.US.ORACLE.COM) encountered following error:~ORA-04052: error occurred when looking up remote object [email protected]~ORA-00604: error occurred at recursive SQL level 4~ORA-12154: TNS:could not resolve the connect identifier specified~ORA-06512: at "SYS.DBMS_AQADM_SYS", line 1087~ORA-06512: at "SYS.DBMS_AQADM_SYS", line 7616~ORA-06512: at "SYS.DBMS_AQADM", line 631~ORA-06512: at line 1~Propagation Schedule for (STRMADMIN.SOURCE_QUEUE, "STRMADMIN"."TARGET_QUEUE"@TARGET.REGRESS.RDBMS.DEV.US.ORACLE.COM) disabled due to 16 consecutive errors.
Any pointers will be greatly appreciated.
PS: I am new to Oracle Streams and DBA and need to accomplish this quickly so please forgive my ignorance.
Do let me know if you need any other information.
Warm Regards,
Edited by: user8784956 on Oct 8, 2009 8:52 AM
Edited by: user8784956 on Oct 8, 2009 10:47 AM

global name means that dblink_name=db_global_name so:
CREATE DATABASE LINK target.REGRESS.RDBMS.DEV.US.ORACLE.COM CONNECT TO strmadmin IDENTIFIED BY strmadmin USING 'target.REGRESS.RDBMS.DEV.US.ORACLE.COM';
CREATE DATABASE LINK source.REGRESS.RDBMS.DEV.US.ORACLE.COM CONNECT TO strmadmin IDENTIFIED BY strmadmin USING 'source.REGRESS.RDBMS.DEV.US.ORACLE.COM'';
and...
destination_queue_name => 'strmadmin.target_queue@target',
source_database => 'source',
replace
destination_queue_name => '[email protected]',
source_database => null,
or
destination_queue_name => '[email protected]',
source_database => 'source.REGRESS.RDBMS.DEV.US.ORACLE.COM',

System error in program SAPLRRK0 and....Value '_' of characteristic 0EMP...

Folks,
We are using ESS/MSS business packages for integration with BW backend, on trying to access status report using,
Manager Self - Service --> Reports --> Development Discussion Status Reports
We are getting the following warning & error messages on the portal screen:
Value '_' of characteristic 0EMPLOYEE is not a number with 000008 spaces
System error in program SAPLRRK0 and form SET_SIDFIX_01-01-
On the face, it looks like a BW error (a BEx query error) being propagated and getting caught by the portal screen.
Any pointers in resolve this will be appreciated with maximum points..
Please let me know.
Cheers
Paras

Thanks Nikhil,
Request your guidance on this, I am new to ESS/MSS business packages and using BW as a backend.
Can I expect to have any errors in configuration (from the portal end) for this kind of error/messages to come up ? If yes, pls gimme pointers to resolve this discrepancy or is this some BEx query error due inconsistencies in employee master data ?
Please let me know.
Paras

Teststand error handling Option

Hi all,
I am looking for a way that when a step get error, Sequence will not be terminated but continue to run other steps.
I found no error handle option to fit my need as the below. Value 1 seems to be good but it terminated the sequence. Value 2 sumary test result validate as good which is not useful. is there any way I can change the error handle structure?
RTEOption_Abort–(Value: 3) Instructs the execution to abort the execution.
RTEOption_Continue–(Value: 1) Instructs the execution to process the error by propagating the error to the calling sequence, if one exists. If the current step group is Setup or Main, the execution jumps directly to the Cleanup step group.
RTEOption_Ignore–(Value: 2) Instructs the execution to ignore the error and continue normal execution.
RTEOption_Retry–(Value: 4) Instructs the execution to ignore the error and re-execute the step that caused the error condition. For the StationOptions.RTEOption property, the Execution.RTEOptionForThisExecution property, and the Thread.SetBatchRTEOption method, TestStand interprets the RTEOption_Retry value as RTEOption_Continue.
RTEOption_ShowDialog–(Value: 0) Instructs the execution to launch the Run-Time Error dialog box when an error occurs.
Purpose
Solved!
Go to Solution.

You could use the SequenceFilePostStepRuntimeError callback and handle errors if you need to do something custom.
An example ships with Teststand which will give you some pointers.
http://zone.ni.com/reference/en-XX/help/370052K-01/tssuppref/infotopics/callbacks_sequencefilepostst...
Beginner? Try LabVIEW Basics
Sharing bits of code? Try Snippets or LAVA Code Capture Tool
Have you tried Quick Drop?, Visit QD Community.

Exception errors

void jButtonRun_actionPerformed(ActionEvent e) {
readMyLog();
void readMyLog() {
try {
connectionDB(); //error
}// end try
catch (IOException e) {
}// end catch
}// end readMyLog
void connectionDB() throws ClassNotFoundException
try
Class.forName ("sun.jdbc.odbc.JdbcOdbcDriver");
I am using JBuilder7. I get an error message while calling the method connectionDB().
I was told to add a 'throws ClassNotFoundException' in method redaMyLog() and a try/catch
statement while calling connectionDB().
But now I get a 'ClassNotFoundException:must be caught or declared to be thrown' at readMyLog().
If I put a ClassNotFoundException or FileNotFoundException in void jButtonRun_actionPerformed(ActionEvent e),
an error occur at void readMyLog();Class or interface expected.
If i continue errors are propagated everywhere in the application.
Can someone sort out this problem for me plz.

Apologies if this reply is too dumbed-down. I'm not sure how much you understand exceptions:
If a method might throw an exception, you are required to write 'throws <MyExceptionClass>' statement before the start of the curly braces. This is in order that any part of your program which calls that method knows that it might get an exception back from it, and then can handle it.
In using try/catch blocks, you are stating that the bit of code inside the 'try' block might generate an exception from a method call. In the 'catch' section, you place a catch statement for each type of exception which you may receive, so that you can handle each type differently.
However, all exceptions descend from the Exception class, so you can handle all exceptions by just using this base class.
Your code:
try {
connectionDB();
} catch (IOException e) {
}is saying that inside the try block, an IOException might occur, and you also have a routine to handle one in the catch section. However, the connectionDB throws a ClassNotFoundException, which is NOT an IOException. Therefore, you should have another catch statement for this exception:
try {
connectionDB();
} catch (IOException e) {
} catch (ClassNotFoundException e) {
System.err.println("Ooops! A ClassNotFoundException occurred!");
}Alternatively, if you wish to handle any exception the same, you can do this:
try {
connectionDB();
} catch (Exception e) {
System.err.println("Ooops! An Exception occurred!");
}The 'Class or interface expected' problem is saying that your code is incorrectly structured. You will find the problem is too many or too few opening or closing braces, or braces in the wrong places. Read through your code and check this.

Error on propagation

Similar Messages

Maybe you are looking for