Propagation error
how to clean up propagation error?
1- Oracle version 9.2.0.1.0
2-I have three instance bd1, bd2, bd3 in different machines
3-The 3 instance can communicate between them via network.
4-I have setup succefully streams environnement bidirectionally between the 3 databases
5-I have tested it. and it works.
7-I have a network disconnexion. When the connection is established my propagation display an error that the remote databases cannot be find. i have sopped then started the 3 instances but the propabgation still doesnt' work.
I have never patched my Oracle.
Could you help me plz?
Thank you a lot dear members.
after connexion establishment i have the following situation:
bd1---> bd2 ok
bd1---> bd3 ok
bd2--->bd1 ok
bd2--->bd3 ok
bd3--->bd1 no
bd3--->bd1 no
i have used DBMS_AQADM.UNSCHEDULE_
PROPAGATION in bd3--->bd1 and bd3----> bd2
then restarted my 3 databases. so the bd3--->bd1 propagation errors dispeared. but bd3-----> bd2 errors still exist. and the propagations form bd3 to bd1 and bd2 don't work. i'm sure that i have no problem with TNS because i have tested my environment before discnnxion and it worked.
Similar Messages
-
How to clean up propagation error?
I have Asynchronous Distributed Hotlog CDC setup between a 9.2.0.8 (source) and 10.2.0.3 (staging) databases. There was a temporary lost of network connection between the two db and the source database is now reporting a ORA-12535 during propagation error.
SQL> select instance, last_error_msg from dba_queue_schedules;
1 ORA-12535: TNS:operation timed out
The network is now ok but the error does not go away. How do I clean up the error to continue propagation w/o dropping and creating the entire change set?
Thanks.If stop/start_propagation don't do it, then I would try using DBMS_AQADM.UNSCHEDULE_
PROPAGATION and DBMS_AQADM.SCHEDULE_PROPAGATION
See http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14258/d_aqadm.htm#CACDAABD
PS: I have used it in 9i with succes. I recommend you try it in a test environment first.
Regards, -
DispatchKeyEvent propagation error
Hi, I have a JDialog and there is at a certain moment a child modal JDialog. These 2 dialogs have this code
public boolean dispatchKeyEvent(KeyEvent e)
switch( e.getKeyCode() )
case KeyEvent.VK_ESCAPE:
cancelButton.doClick();
return true;
default:
return false;
so when the user press escape, it simulates a cancel operation. But the problem is that when the user press ESCAPE in the child dialog, the parent dialog also close. How can I stop the propagation of the key event so only the child dialog will close ?
Thanksafter connexion establishment i have the following situation:
bd1---> bd2 ok
bd1---> bd3 ok
bd2--->bd1 ok
bd2--->bd3 ok
bd3--->bd1 no
bd3--->bd1 no
i have used DBMS_AQADM.UNSCHEDULE_
PROPAGATION in bd3--->bd1 and bd3----> bd2
then restarted my 3 databases. so the bd3--->bd1 propagation errors dispeared. but bd3-----> bd2 errors still exist. and the propagations form bd3 to bd1 and bd2 don't work. i'm sure that i have no problem with TNS because i have tested my environment before discnnxion and it worked. -
Propagation error when trying to download inventory from server
Hi there,
Has anyone seen the following error when trying to download an inventory from the server.:
Buildfile: C:\bea10.3\user_projects\workspaces\RST\RSTPropagation\21102009\propbuild.xml
import:
BUILD FAILED
C:\bea10.3\user_projects\workspaces\RST\RSTPropagation\21102009\propbuild.xml:39: The propagation servlet returned a failure response: The [Download] operation is halting due to the following failure: null
Additional Information:
The propagation servlet returned the following log information found in [C:\DOCUME~1\myuser\LOCALS~1\Temp\onlineDownload__D21_H11_M8_S11.log]:
INFO (Oct 21, 2009 11:08:11 AM SAST): Verbose logging has been disabled on the server.
INFO (Oct 21, 2009 11:08:11 AM SAST): The propagation servlet is starting the [Download] operation.
INFO (Oct 21, 2009 11:08:11 AM SAST): The modifier [allowMaintenanceModeDisabled] with a value of [true] will be used for this operation.
INFO (Oct 21, 2009 11:08:11 AM SAST): Validating that current user is in the Admin role...SUCCESS
ERROR (Oct 21, 2009 11:08:11 AM SAST): Validating that Maintenance Mode is enabled...FAILURE
ERROR (Oct 21, 2009 11:08:11 AM SAST): Maintenance Mode has not been enabled on the server. With Maintenance Mode disabled it is possible for users to modify the application. This may cause problems for propagation.
WARNING (Oct 21, 2009 11:08:11 AM SAST): Because the modifier [allowMaintenanceModeDisabled] was enabled this validation failure will be ignored and the operation will proceed. However, users will still be able to make modifications to the application, which could lead to missing data and unexpected propagation errors.
WARNING (Oct 21, 2009 11:08:11 AM SAST): The temporary directory on the server used by propagation is [portal/bea10.3/user_projects/domains/RSTDomain/servers/wl_nstf/tmp/_WL_user/RSTEar/7v9j6d/public] with a length of [99] bytes. It is recommended that you shorten this path to avoid path length related failures. See the propagation documentation on how to specify the inventoryWorkingFolder context-param for the propagation servlet.
INFO (Oct 21, 2009 11:08:19 AM SAST): Validating that LDAP and RDBMS security resources are in sync...SUCCESS
INFO (Oct 21, 2009 11:08:19 AM SAST): Writing the inventory file to the servers file system at [{0}].
ERROR (Oct 21, 2009 11:08:23 AM SAST): The [Download] operation is halting due to the following failure: null
Total time: 14 seconds
Please let me know if you have any ideas because "The [Download] operation is halting due to the following failure: null" means nothing to me.
Please note changing the maintenace mode makes no difference.Please enable Verbose Logging on the propagation servlet
http://download.oracle.com/docs/cd/E13155_01/wlp/docs103/prodOps/propToolAdvanced.html#wp1071690
and check the logs on the server, they might give a clue -
How to display propagation errors
I have script to display apply errors and i would like to know if there is any scrip to display propagation errors because oracle tools like enreprise manager displays only the last error. Is there any script to display all propagation errors?( i use oracle 9.2.0.1)
Thanks a lot.You could write a procedure to collect all propagation errors reported in catalog to your own history table. And run this procedure every couple of seconds using dbms_job to check for any errors in catalog.
-
Helps for WLP9.2 in a cluster: deploy errors, propagation errors
I wrote a document for our portal project's production support that details how to fix several recuring problems with WLP9.2 (GA) in cluster. I'm sharing this with the community as a help.
Email me if you'd like updates or have additional scenarios / fixes or you'd like the word doc version.
Curt Smith, Atlanta WLP consultant, [email protected], put HELP WLP as a part of the subject please.
1 WLP 9.2 Environment
The cluster environment where these symptoms are frequently seen is described by the following:
1. Solaris 9 on 4 cpu sparc boxes. 16Gb Ram. The VM is given ?Xmx1034m.
2. Bea private patch: RSGT, fixed cluster deployments.
3. Bea private patch: BG74, fixed session affinity, changed the session tracking cookie name back to the standard name: JSESSIONID.
4. IBM UDB (DB2) using the Bea DB2 driver. FYI: the problems described below I don?t feel have any relationship to the DB used for a portal.
2 Common problems and their fixes
2.1 Failed deploy (Install) of a new portal application via the cluster console.
Problem symptoms:
After clicking Finish (or) Commit the console displays that there where errors. All errors require this procedure.
Fix steps:
1. Shut down the whole cluster. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
a. Find the PID to kill: lsof ?C | grep <listen port number>
b. kill <pid>
c. Run kill again and if the pid is still running then do: kill -9 <pid>
2. Admin server:
a. Remove file: <domain>/config/config.lok
b. Edit file: <domain>/config/config.xml
c. Remove all elements of: <app-deployment> ? </app-deployment>
d. Start the Admin server
e. Make sure it comes up in the running state. Use the console: servers ? admin ? control - resume if needed.
3. Both Managed servers:
a. cd <domain>/config
b. rm ?rf *
This forces the re-down load of the cleaned up config.xml.
c. cd <domain>/servers/<managed_name>
d. rm ?rf tmp cache stage data
This cleans up stale or jammed sideways deploys. Be sure to delete all three directorys: tmp, cache, stage and data.
e. Start each managed server.
f. Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
You can now use the console to Install your applications.
2.2 The portal throws framework / container exceptions on one managed instance.
Problem symptoms:
If you see exceptions from the classloader re a framework class not found, serialization failure or error etc. In general the symptom is that the container is not stable, running correctly, not making sense or your application works on one managed instance but not on the other.
Fix steps:
1. Shut down the problem managed instance. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
a. Find the PID to kill: lsof ?C | grep <listen port number>
b. kill <pid>
c. Run kill again and if the pid is still running then do: kill -9 <pid>
2. Perform these clean up steps on one or both managed instances:
a. cd <domain>/config
b. rm ?rf *
This forces the re-down load of the cleaned up config.xml.
c. cd <domain>/servers/<managed_name>
d. rm ?rf tmp cache stage data
This cleans up stale or jammed sideways deploys. Be sure to delete all three directorys: tmp, cache, stage and data.
e. Start each managed server.
f. Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
3. The libraries and applications should auto deploy as the managed instance comes up. Once the managed instance goes into the running state, or you Resume into the running state. Your application should be accessible. Sometimes it takes a few seconds after going into the running state for all applications to be instantiated.
2.3 Content propagation fails on the commit step.
Problem symptoms:
In the log of the managed instance you specified in the propagation ant script you?ll see exceptions regarding not being able to create or instantiate a dynamic delegated role.
There is an underlying bug / robustness issue with WLP9.2 (GA) where periodically you can?t create delegated roles either with the PortalAdmin or via the propagation utility.
Important issue:
This procedure was supplied by Bea which will remove from the internal LDAP and the portal DB your custom / created roles. This will leave your cluster in the new installation state with just the default users and roles: weblogic and portaladmin. The implications are that you?ll have to boot your cluster with console user: weblogic / weblogic. You can then add back your secure console user/password but you?ll have to do this over and over as propagations fail. The observed failure rate is once every 2-3 weeks if you do propagations daily.
Note:
The following assumes that you left the default console user weblogic password to be the default password of: weblogic. The following procedure deletes the local LDAP but leaves the rows in the DB.users table including the SHA-1 hashed passwords. The following procedure should still work if you changed the password for weblogic, but it probably won?t work if you try to substitute your secure console user/pw because there will be no delegated authorization roles mapping to your custom console user. You might experiment with this scenario.
Fix steps:
1. Shut down the whole cluster. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
a. Find the PID to kill: lsof ?C | grep <listen port number>
b. kill <pid>
c. Run kill again and if the pid is still running then do: kill -9 <pid>
2. Admin server:
a. Remove directory: <domain>/servers/AdminServer/data/ldap
b. Run this SQL script after you edit it for your schema:
delete from yourschema.P13N_DELEGATED_HIERARCHY;
delete from yourschema.P13N_ENTITLEMENT_POLICY;
delete from yourschema.P13N_ENTITLEMENT_RESOURCE;
delete from yourschema.P13N_ENTITLEMENT_ROLE;
delete from yourschema.P13N_ENTITLEMENT_APPLICATION;
commit;
c. Start the Admin server
d. Make sure it comes up in the running state. Use the console: servers ? admin ? control - resume if needed.
3. Both Managed servers:
a. cd <domain>/servers/<managed_name>
b. rm ?rf data
This forces the re-down load of the LDAP directory.
c. Start each managed server.
d. Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
2.4 The enterprise portal DB fails and needs to be restored OR switch DB instances
Restoring a portal DB or switching existing DBs are similar scenarios. The issues that you?ll face with WLP9.2 since it now uses a JDBCauthenticator to authenticate and authorize the console / boot user you need to first be able to connect to the DB before the admin and managed instances can boot. If you haven?t properly encrypted the DB user?s password in the <domain>/config/jdbc/*.xml files, then you?ll not be able to boot the admin server since you won?t be able to create a JDBC connection to the DB. The boot messages are not clear as to what the failure is.
You?ll need to know an Admin role user and password that?s in the DB you?re wanting to connect to, to put into boot.properties and on the managed instances in their boot.properties or startManaged scripts. Don?t forget that the managed instances have local credentials which is new for 9.2. They are in the startManaged script in clear text or a local boot.properties.
Note:
The passwords in the DB are SHA-1 hashed and there is no SHA-1 hash generator tool so you can?t change a password via SQL, but you can move the password from one DB to another. This is possible because the domain encryption salt is not used to generate the SHA-1 string. As it turns out, the SHA-1 string is compatible with all 9.2 cluster domains. IE the domain DES3 salt has nothing to do with password verification. The same password SHA-1 string taken from different domains or even same domain but different users will be different, this is just a randomization put into the algorithm yet every domain will be able to validate the given password against the DB?s SHA-1 string. Because of this, I?ve not had any problem moving DB instances between clusters, especially if I?ve given up on security and use weblogic/weblogic as the console user and this user / pw is in every DB.
Steps:
The assumption for restoring a DB is that the DB has been restored but it?s an older version and doesn?t have the console user/pw that is in boot.properties. At this point swaping a DB is the same as restoring an old version of the portal DB.
1. Edit the console user and password as clear text into: <domain>/servers/AdminServers/security/boot.properties
This is where you may give in and use weblogic/weblogic.
2. Set the correct DB access password encryption in the jdbc/*.xml files.
a. cd <domain>/bin
b. . ./setDomainEnv.sh or if you?re on windows just run: setDomainEnv.cmd
c. java weblogic.security.Encrypt <the_db_password>
d. Edit the returned string into every <domain>/config/jdbc/*.xml
e. Make sure the *.xml files point to the correct DB host, port, schema, DB name, DB user.
3. Start the Admin server. I should come up. If it doesn?t it has to be not being able to create a connection to the DB, which depends on the *.xml having the correct user and DES-3 encrypted password.
4. Edit the new console user/password on the managed instance bin/startManaged script or the local boot.properties.
5. Start the managed instances.
2.5 Install patches on a host that does not have internet access
The short description is to run smart update on a host that does have internet access. Fetch out of the <domain>/utils/bsu/cache_dir directory the downloaded patch jar and xml. Manually apply the patch to your non-internet accessible hosts.I wrote a document for our portal project's production support that details how to fix several recuring problems with WLP9.2 (GA) in cluster. I'm sharing this with the community as a help.
Email me if you'd like updates or have additional scenarios / fixes or you'd like the word doc version.
Curt Smith, Atlanta WLP consultant, [email protected], put HELP WLP as a part of the subject please.
1 WLP 9.2 Environment
The cluster environment where these symptoms are frequently seen is described by the following:
1. Solaris 9 on 4 cpu sparc boxes. 16Gb Ram. The VM is given ?Xmx1034m.
2. Bea private patch: RSGT, fixed cluster deployments.
3. Bea private patch: BG74, fixed session affinity, changed the session tracking cookie name back to the standard name: JSESSIONID.
4. IBM UDB (DB2) using the Bea DB2 driver. FYI: the problems described below I don?t feel have any relationship to the DB used for a portal.
2 Common problems and their fixes
2.1 Failed deploy (Install) of a new portal application via the cluster console.
Problem symptoms:
After clicking Finish (or) Commit the console displays that there where errors. All errors require this procedure.
Fix steps:
1. Shut down the whole cluster. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
a. Find the PID to kill: lsof ?C | grep <listen port number>
b. kill <pid>
c. Run kill again and if the pid is still running then do: kill -9 <pid>
2. Admin server:
a. Remove file: <domain>/config/config.lok
b. Edit file: <domain>/config/config.xml
c. Remove all elements of: <app-deployment> ? </app-deployment>
d. Start the Admin server
e. Make sure it comes up in the running state. Use the console: servers ? admin ? control - resume if needed.
3. Both Managed servers:
a. cd <domain>/config
b. rm ?rf *
This forces the re-down load of the cleaned up config.xml.
c. cd <domain>/servers/<managed_name>
d. rm ?rf tmp cache stage data
This cleans up stale or jammed sideways deploys. Be sure to delete all three directorys: tmp, cache, stage and data.
e. Start each managed server.
f. Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
You can now use the console to Install your applications.
2.2 The portal throws framework / container exceptions on one managed instance.
Problem symptoms:
If you see exceptions from the classloader re a framework class not found, serialization failure or error etc. In general the symptom is that the container is not stable, running correctly, not making sense or your application works on one managed instance but not on the other.
Fix steps:
1. Shut down the problem managed instance. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
a. Find the PID to kill: lsof ?C | grep <listen port number>
b. kill <pid>
c. Run kill again and if the pid is still running then do: kill -9 <pid>
2. Perform these clean up steps on one or both managed instances:
a. cd <domain>/config
b. rm ?rf *
This forces the re-down load of the cleaned up config.xml.
c. cd <domain>/servers/<managed_name>
d. rm ?rf tmp cache stage data
This cleans up stale or jammed sideways deploys. Be sure to delete all three directorys: tmp, cache, stage and data.
e. Start each managed server.
f. Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
3. The libraries and applications should auto deploy as the managed instance comes up. Once the managed instance goes into the running state, or you Resume into the running state. Your application should be accessible. Sometimes it takes a few seconds after going into the running state for all applications to be instantiated.
2.3 Content propagation fails on the commit step.
Problem symptoms:
In the log of the managed instance you specified in the propagation ant script you?ll see exceptions regarding not being able to create or instantiate a dynamic delegated role.
There is an underlying bug / robustness issue with WLP9.2 (GA) where periodically you can?t create delegated roles either with the PortalAdmin or via the propagation utility.
Important issue:
This procedure was supplied by Bea which will remove from the internal LDAP and the portal DB your custom / created roles. This will leave your cluster in the new installation state with just the default users and roles: weblogic and portaladmin. The implications are that you?ll have to boot your cluster with console user: weblogic / weblogic. You can then add back your secure console user/password but you?ll have to do this over and over as propagations fail. The observed failure rate is once every 2-3 weeks if you do propagations daily.
Note:
The following assumes that you left the default console user weblogic password to be the default password of: weblogic. The following procedure deletes the local LDAP but leaves the rows in the DB.users table including the SHA-1 hashed passwords. The following procedure should still work if you changed the password for weblogic, but it probably won?t work if you try to substitute your secure console user/pw because there will be no delegated authorization roles mapping to your custom console user. You might experiment with this scenario.
Fix steps:
1. Shut down the whole cluster. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
a. Find the PID to kill: lsof ?C | grep <listen port number>
b. kill <pid>
c. Run kill again and if the pid is still running then do: kill -9 <pid>
2. Admin server:
a. Remove directory: <domain>/servers/AdminServer/data/ldap
b. Run this SQL script after you edit it for your schema:
delete from yourschema.P13N_DELEGATED_HIERARCHY;
delete from yourschema.P13N_ENTITLEMENT_POLICY;
delete from yourschema.P13N_ENTITLEMENT_RESOURCE;
delete from yourschema.P13N_ENTITLEMENT_ROLE;
delete from yourschema.P13N_ENTITLEMENT_APPLICATION;
commit;
c. Start the Admin server
d. Make sure it comes up in the running state. Use the console: servers ? admin ? control - resume if needed.
3. Both Managed servers:
a. cd <domain>/servers/<managed_name>
b. rm ?rf data
This forces the re-down load of the LDAP directory.
c. Start each managed server.
d. Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
2.4 The enterprise portal DB fails and needs to be restored OR switch DB instances
Restoring a portal DB or switching existing DBs are similar scenarios. The issues that you?ll face with WLP9.2 since it now uses a JDBCauthenticator to authenticate and authorize the console / boot user you need to first be able to connect to the DB before the admin and managed instances can boot. If you haven?t properly encrypted the DB user?s password in the <domain>/config/jdbc/*.xml files, then you?ll not be able to boot the admin server since you won?t be able to create a JDBC connection to the DB. The boot messages are not clear as to what the failure is.
You?ll need to know an Admin role user and password that?s in the DB you?re wanting to connect to, to put into boot.properties and on the managed instances in their boot.properties or startManaged scripts. Don?t forget that the managed instances have local credentials which is new for 9.2. They are in the startManaged script in clear text or a local boot.properties.
Note:
The passwords in the DB are SHA-1 hashed and there is no SHA-1 hash generator tool so you can?t change a password via SQL, but you can move the password from one DB to another. This is possible because the domain encryption salt is not used to generate the SHA-1 string. As it turns out, the SHA-1 string is compatible with all 9.2 cluster domains. IE the domain DES3 salt has nothing to do with password verification. The same password SHA-1 string taken from different domains or even same domain but different users will be different, this is just a randomization put into the algorithm yet every domain will be able to validate the given password against the DB?s SHA-1 string. Because of this, I?ve not had any problem moving DB instances between clusters, especially if I?ve given up on security and use weblogic/weblogic as the console user and this user / pw is in every DB.
Steps:
The assumption for restoring a DB is that the DB has been restored but it?s an older version and doesn?t have the console user/pw that is in boot.properties. At this point swaping a DB is the same as restoring an old version of the portal DB.
1. Edit the console user and password as clear text into: <domain>/servers/AdminServers/security/boot.properties
This is where you may give in and use weblogic/weblogic.
2. Set the correct DB access password encryption in the jdbc/*.xml files.
a. cd <domain>/bin
b. . ./setDomainEnv.sh or if you?re on windows just run: setDomainEnv.cmd
c. java weblogic.security.Encrypt <the_db_password>
d. Edit the returned string into every <domain>/config/jdbc/*.xml
e. Make sure the *.xml files point to the correct DB host, port, schema, DB name, DB user.
3. Start the Admin server. I should come up. If it doesn?t it has to be not being able to create a connection to the DB, which depends on the *.xml having the correct user and DES-3 encrypted password.
4. Edit the new console user/password on the managed instance bin/startManaged script or the local boot.properties.
5. Start the managed instances.
2.5 Install patches on a host that does not have internet access
The short description is to run smart update on a host that does have internet access. Fetch out of the <domain>/utils/bsu/cache_dir directory the downloaded patch jar and xml. Manually apply the patch to your non-internet accessible hosts. -
Standard-Entreprise Propagation error remote DB
Hello,
I use a Oracle9i Release 9.2.0.1.0 - Production
I create remotely queue tables and queues, propagation via DBLink. That's ok
But the propagation fails with this error :
ORA-02068: following severe error from REMTE
ORA-00600: internal error code, arguments: [kolaHashFind:hash table], [], [], [], [], [], [], []
Have any idear ?
Thanks for info
Regards
Rafael Rimbert.we have found it.
We transfert message wich payload is type sys.xmltype
The problem was : one instance was with character set we8iso... and the other ms1252. -
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 -
Queue propagation error---ORA-23603
Hi Experts,
I got lots of error as ORA-23603: STREAMS enqueue aborted due to low SGA for Destination
"STRMADMIN"."STREAMS_APPLY"@sale2.net.
However, destination SGA taeget and Max as 2552M. and source target/Max SGA is 1888M.
In source database EM, I saw these propagation and disable source capture and propagation.
we use oracle 10gR4 in window 2003
I check destination database, everything is ok without any error in there.
What do I need to do? I can not start propagation and capture in sourec database.
Thanks,
JimThanks for you help. Actually, we set AQ_TM_PROCESSES as 1.
I try to enable progation. but it does not work.
I try to strat propagation and get error as
SQL> begin
2 DBMS_PROPAGATION_ADM.START_PROPAGATION(
3 propagation_name=>'STREAM_PROPAGAT');
4 end;
5 /
begin
ERROR at line 1:
ORA-01403: no data found
ORA-06512: at "SYS.DBMS_PROPAGATION_INTERNAL", line 752
ORA-06512: at "SYS.DBMS_PROPAGATION_ADM", line 145
ORA-06512: at line 2
SQL>
SQL> show parameter AQ_TM_PROCESSES
NAME_COL_PLUS_SHOW_PARAM TYPE
VALUE_COL_PLUS_SHOW_PARAM
aq_tm_processes integer
1
I saw EM Failures since startup 16. error as 20603. futhter check message tab. i got ORA-23603: STREAMS enqueue aborted due to low SGA in destination apply.
However, I do not see any error for apply in destination DB.
This is a bi_direction stream. From destion DB i also saw same message for source DB Apply issue. I can not find apply error in there too.
What do I need to restart propagation? It is probation that DBA_propagation tanle that have error message ?
Thanks for help!
JIm -
Hi Friends,
My propagation was broken with 02068. After restart it. this error is still in EM. But PROPAGATION status is enabled.
What means is for this point?
We use oracle 10g 2 and window server 2003.
how to delete this error message?
Thanks
Jim,Hello Jim,
Can you check the output of the following and let us know:
connect / as sysdba
alter session set nls_date_format='dd-mm-yy hh24:mi:ss';
select propagation_name,status,error_message,error_date,sysdate from dba_propagation;
Are you able to see the same error messages in dba_propagation view?
Thanks,
Rijesh -
Propagation error during upload entitlement process
While applying entitlement we are getting this error
queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1250031360989> <BEA-000000> <The [Upload] operation is halting due to the following failure: Posted content length of 10682519 exceeds limit of 10485760>**
We are running on WLP 10.3. Any idea why we are getting this error since this used to work previously.
Here is the complete log.
####<Aug 11, 2009 3:55:21 PM PDT> <Info> <InventoryServices> <sfrhvmportalint.prn.com> <AdminServer> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1250031321516> <BEA-000000> <The environment name has been configured in web.xml as [Production].>
####<Aug 11, 2009 3:55:21 PM PDT> <Info> <InventoryServices> <sfrhvmportalint.prn.com> <AdminServer> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1250031321517> <BEA-000000> <Verbose logging has been enabled in web.xml.>
####<Aug 11, 2009 3:55:21 PM PDT> <Info> <InventoryServices> <sfrhvmportalint.prn.com> <AdminServer> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1250031321594> <BEA-000000> <Verbose logging has been disabled on the server.>
####<Aug 11, 2009 3:55:21 PM PDT> <Info> <InventoryServices> <sfrhvmportalint.prn.com> <AdminServer> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1250031321595> <BEA-000000> <The propagation servlet is starting the [Mutex] operation.>
####<Aug 11, 2009 3:55:21 PM PDT> <Info> <InventoryServices> <sfrhvmportalint.prn.com> <AdminServer> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1250031321595> <BEA-000000> <The mutex is currently available from the propagation servlet. >
####<Aug 11, 2009 3:55:21 PM PDT> <Info> <InventoryServices> <sfrhvmportalint.prn.com> <AdminServer> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1250031321595> <BEA-000000> <The propagation servlet has finished the [Mutex] operation.>
####<Aug 11, 2009 3:55:21 PM PDT> <Info> <InventoryServices> <sfrhvmportalint.prn.com> <AdminServer> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1250031321851> <BEA-000000> <Verbose logging has been disabled on the server.>
####<Aug 11, 2009 3:55:21 PM PDT> <Info> <InventoryServices> <sfrhvmportalint.prn.com> <AdminServer> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1250031321852> <BEA-000000> <The propagation servlet is starting the [Maintenance Mode] operation.>
####<Aug 11, 2009 3:55:21 PM PDT> <Info> <InventoryServices> <sfrhvmportalint.prn.com> <AdminServer> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1250031321949> <BEA-000000> <Maintenance mode has been enabled.>
####<Aug 11, 2009 3:55:21 PM PDT> <Info> <InventoryServices> <sfrhvmportalint.prn.com> <AdminServer> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1250031321950> <BEA-000000> <The propagation servlet has finished the [Maintenance Mode] operation.>
####<Aug 11, 2009 3:55:22 PM PDT> <Info> <InventoryServices> <sfrhvmportalint.prn.com> <AdminServer> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1250031322171> <BEA-000000> <Verbose logging has been disabled on the server.>
####<Aug 11, 2009 3:55:22 PM PDT> <Info> <InventoryServices> <sfrhvmportalint.prn.com> <AdminServer> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1250031322172> <BEA-000000> <The propagation servlet is starting the [Download] operation.>
####<Aug 11, 2009 3:55:22 PM PDT> <Info> <InventoryServices> <sfrhvmportalint.prn.com> <AdminServer> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1250031322173> <BEA-000000> <The modifier [allowMaintenanceModeDisabled] with a value of [true] will be used for this operation.>
####<Aug 11, 2009 3:55:22 PM PDT> <Info> <InventoryServices> <sfrhvmportalint.prn.com> <AdminServer> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1250031322173> <BEA-000000> <The modifier [allowSecurityOutOfSync] with a value of [true] will be used for this operation.>
####<Aug 11, 2009 3:55:22 PM PDT> <Info> <InventoryServices> <sfrhvmportalint.prn.com> <AdminServer> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1250031322187> <BEA-000000> <Validating that current user is in the Admin role...SUCCESS>
####<Aug 11, 2009 3:55:22 PM PDT> <Info> <InventoryServices> <sfrhvmportalint.prn.com> <AdminServer> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1250031322188> <BEA-000000> <Validating that Maintenance Mode is enabled...SUCCESS>
####<Aug 11, 2009 3:55:30 PM PDT> <Info> <InventoryServices> <sfrhvmportalint.prn.com> <AdminServer> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1250031330866> <BEA-000000> <Validating that LDAP and RDBMS security resources are in sync...SUCCESS>
####<Aug 11, 2009 3:55:30 PM PDT> <Info> <InventoryServices> <sfrhvmportalint.prn.com> <AdminServer> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1250031330892> <BEA-000000> <The current export will overwrite any existing data in the directory [local/domains/portal_domain/servers/AdminServer/tmp/_WL_user/PortalEar/omcqtg/public/invSvcTempFolder1562360295].>
####<Aug 11, 2009 3:55:43 PM PDT> <Info> <InventoryServices> <sfrhvmportalint.prn.com> <AdminServer> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1250031343259> <BEA-000000> <The user [weblogic] has initiated an export with the Propagation Tool.>
####<Aug 11, 2009 3:55:44 PM PDT> <Info> <InventoryServices> <sfrhvmportalint.prn.com> <AdminServer> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1250031344417> <BEA-000000> <Validating the inventory file [local/domains/portal_domain/servers/AdminServer/tmp/_WL_user/PortalEar/omcqtg/public/invSvcTempFile868909347.zip] does not exceed the max inventory size of [4,294,967,296] bytes...SUCCESS>
####<Aug 11, 2009 3:55:44 PM PDT> <Info> <InventoryServices> <sfrhvmportalint.prn.com> <AdminServer> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1250031344418> <BEA-000000> <The propagation servlet has finished the [Download] operation.>
####<Aug 11, 2009 3:56:00 PM PDT> <Info> <InventoryServices> <sfrhvmportalint.prn.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1250031360989> <BEA-000000> <Verbose logging has been disabled on the server.>
####<Aug 11, 2009 3:56:00 PM PDT> <Info> <InventoryServices> <sfrhvmportalint.prn.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1250031360989> <BEA-000000> <The propagation servlet is starting the [Upload] operation.>
*####<Aug 11, 2009 3:56:00 PM PDT> <Error> <InventoryServices> <sfrhvmportalint.prn.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1250031360989> <BEA-000000> <The [Upload] operation is halting due to the following failure: Posted content length of 10682519 exceeds limit of 10485760>*
####<Aug 11, 2009 4:00:00 PM PDT> <Info> <Lease> <sfrhvmportalint.prn.com> <AdminServer> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1250031600957> <BEA-403301> <Auto lease timer is still running for lease PortalFrameworkDotFilesLoadedLease&PortalEar&PortalWar.war.>I tried the last two options for Increasing the Default Upload File Size as said in the below site but it does not work out. Any other solutions for avoiding this error
The [Upload] operation is halting due to the following failure: Posted content length of 69302451 exceeds limit of 10485760
http://download.oracle.com/docs/cd/E13155_01/wlp/docs103/prodOps/propToolAdvanced.html#wp1070764 -
Propagating Error from Split join to Calling Proxy Service
Hi All,
In our project we are calling a split join service, from a Proxy Service, which in turn calls another Proxy Service.
i.e:
Proxy Service1 (PS1) <-> SplitJoin Service (SjS) <-> Proxy Service2 (PS2)
Requirement:
All the service calls are two way service calls and local protocol is being used. When an error occurs in PS2 we need to propagate the error with detailed error details to the PS1 via the SjS in order to achieve the following
1. Achieving rollback of the Transaction
2. Logging the detailed error report of PS2 in PS1
Issue:
But we are not getting the detailed error in the PS1. On further analysis we found dat the fault variable in the split join is empty in its error handling flow.
We have used reply with error activity in PS2 to propagate the fault to the split join and reply with soap fault option in split join to propagate the fault to the PS1.
We need to propagate the detailed report as error only, in order to achieve the rollback. So kindly suggest me the ways to get the detailed error report in PS1? i.e: getting the detailed error report of PS2 in split join fault variable and propagating the same to PS1.
Regards,
Balaji RBalaji,
Try to enable Execution and Message(Terse Level) Tracing for the OSB services to see where fault message is going
and
In PS2 try with Reply with Success.
as Reply with failure returns the fault variable back and Reply with success will send the content of (PS2)$body back as a response and then u can capture the fault from faulted body and send it to PS1.
Regards,
Abhinav Gupta
Edited by: Abhinav on Aug 28, 2012 3:06 PM -
Error propagating servlet user to peer?
Hello,
We currently have a Windows 2003 Server 32bit running ColdFusion 8.01 with 3 instances named: cfusion, Instance1 and Instance2. Instance 1 and Instance 2 are clustered together and serving all our sites in IIS. We're hosting just over 200 sites with approx. 6-7 hits a second.
ColdFusion is running with all the latest hot fixes and patches. The JVM is version 1.6_24.
For a while now one of the instances in the cluster randomly locks up a few times a month, fails to return pages and has high cpu usage. We'd normally just restart the instance and things would return to normal. It's bad to ignore things but it's only recently I've had a chance to look into the cause of these lock ups.
Last night both the instances appeared to fail. We have an external monitor that hits our sites every 5 minutes to ensure they are still running.
Scanning through the JRun logs at about the time we received our first monitor warning there are a bunch of what appear to be propagation errors on both instances.
Logs from Instance1:
22/03 07:10:14 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketTimeoutException: Read timed out
22/03 07:10:16 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketTimeoutException: Read timed out
22/03 07:10:17 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketTimeoutException: Read timed out
22/03 07:10:18 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketTimeoutException: Read timed out
22/03 07:10:20 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketTimeoutException: Read timed out
22/03 07:10:21 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketTimeoutException: Read timed out
22/03 07:10:23 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketTimeoutException: Read timed out
22/03 07:10:23 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketTimeoutException: Read timed out
22/03 07:10:24 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketTimeoutException: Read timed out
22/03 07:10:24 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketTimeoutException: Read timed out
22/03 07:10:25 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketTimeoutException: Read timed out
22/03 07:10:26 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketTimeoutException: Read timed out
22/03 07:10:26 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketTimeoutException: Read timed out
22/03 07:10:26 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketTimeoutException: Read timed out
22/03 07:10:26 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketTimeoutException: Read timed out
22/03 07:10:27 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketTimeoutException: Read timed out
22/03 07:10:28 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketTimeoutException: Read timed out
22/03 07:10:28 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketTimeoutException: Read timed out
22/03 07:10:29 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketTimeoutException: Read timed out
22/03 07:17:43 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketException: Connection reset by peer: socket write error
Logs from Instance2:
22/03 07:10:40 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketException: Connection reset by peer: socket write error
22/03 07:10:40 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketException: Connection reset
22/03 07:10:40 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketException: Connection reset
22/03 07:10:40 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketException: Connection reset by peer: socket write error
22/03 07:10:40 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketException: Connection reset by peer: socket write error
22/03 07:10:40 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketException: Connection reset by peer: socket write error
22/03 07:10:40 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketException: Connection reset by peer: socket write error
22/03 07:10:40 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketException: Connection reset by peer: socket write error
22/03 07:10:40 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketException: Connection reset by peer: socket write error
22/03 07:10:40 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketException: Connection reset by peer: socket write error
22/03 07:10:40 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketException: Connection reset by peer: socket write error
22/03 07:10:41 info Clusterable service JRunRMIBroker discovered ClusterManager on xxx.xxx.xxx.xxx:3862, cluster domain: cluster1 (Lookup Service's JINI-ID: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx)
22/03 07:10:42 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketException: Connection reset
22/03 07:10:42 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.io.EOFException
22/03 07:10:42 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketException: Connection reset
22/03 07:10:42 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.net.SocketException: Connection reset
22/03 07:10:42 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
java.io.EOFException
22/03 07:10:43 error ROOT CAUSE:
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:640)
I suspect it's a JVM memory issue, however I have no way of extracting or creating memory logs without bringing all our sites down again.
I only know the basics of how the JVM heap space works but my guess is that one of the instances can't create any more threads because the PermGen space has run out and it's killing the cluster.
Here's our current JVM settings: java.args=-server -Xmx768m -Xms768m -Dsun.io.useCanonCaches=false -XX:MaxPermSize=192m -XX:+UseParallelGC -Dcoldfusion.fckupload=true -Dcoldfusion.rootDir={application.home}/
Has anyone come across this issue before or has any ideas on how to better debug the issue with minimal impact on uptime?Well the classes should be in WEB-INF/classes, but I don't think that's your problem.
Getting an applet to connect to a db is notoriously difficult (so I've heard - I've never tried it), so having the applet talk to the servlet with the servlet in turn talking to the db is a good idea.
"i cant see the error message because it wont print in the VM,"
That doesn't sound right. What does your error handling code look like?
" MySQL it also has access permissions for some weird reason."
MySQL is set up so that user credentials are only valid from a specific host unless you explicitly tell it that a user can connect from anywhere. This is native to MySQL and has nothing to do with java or JDBC.
Most of the code you posted throws Exceptions. Are you catching them, and if so what did they say? -
In my Application Module I have a try/catch block for any database errors in a client interface function. This works great since it allows me to Rollback if there is a database error, but then the exception does not propagate back to the client, and I am losing the ability to see the error message on the client.
How can I both trap an exception in a client interface while still propagating error messages to the client?Would you please load the folder list item, then get DisplayName property, check whether it works?
I tested it with load folder item, then item.DisplayName, it be can be retrieved well.
Qiao Wei
TechNet Community Support -
Getting response in fault tag ?
Hi All,
My BPEL process contains an operation which has Input,Output and Fault parameters.
When I initiate the process, Its completing successfully..
but my response is wrapped up in <env:Fault >
Following is the response I am getting
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Header/><env:Body><env:Fault xmlns:ns1="http://xmlns.oracle.com/EnterpriseServices/Core/Item/V1"><faultcode>ns1:FaultMessage</faultcode><faultstring>business exception</faultstring><faultactor>cx-fault-actor</faultactor><detail>
----My response is here ---
</env:Fault>
</env:Body>
</env:Envelope>
My project WSDL file
<definitions
name="SyncItemEBIZProvBPELABCSImpl"
targetNamespace="http://xmlns.oracle.com/ABCSImpl/EBIZ/Core/SyncItemEBIZProvBPELABCSImpl/V1"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:itemabcs="http://xmlns.oracle.com/ABCSImpl/EBIZ/Core/SyncItemEBIZProvBPELABCSImpl/V1"
xmlns:corecom="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V1"
xmlns:itemebo="http://xmlns.oracle.com/EnterpriseObjects/Core/EBO/Item/V1"
xmlns:svcdoc="http://xmlns.oracle.com/Services/Documentation/V1"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:itemsvc="http://xmlns.oracle.com/EnterpriseServices/Core/Item/V1"
xmlns:pns1="http://xmlns.oracle.com/SyncItemEBIZProvBPELABCSImpl/correlationset"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:client="http://xmlns.oracle.com/ABCSImpl/EBIZ/Core/SyncItemEBIZProvBPELABCSImpl/V1"
xmlns:itemabo="http://www.example.org/SyncItemPublicationInput"
>
<import namespace="http://xmlns.oracle.com/EnterpriseServices/Core/Item/V1" location="http://ap6032fems.us.oracle.com:7831/AIAComponents/EnterpriseBusinessServiceLibrary/Core/Item/ItemEBS.wsdl"/>
<import namespace="http://xmlns.oracle.com/SyncItemEBIZProvBPELABCSImpl/correlationset"
location="SyncItemEBIZProvBPELABCSImpl_Properties.wsdl"/>
<types>
<xsd:schema targetNamespace="http://xmlns.oracle.com/ABCSImpl/EBIZ/Core/SyncItemEBIZProvBPELABCSImpl/V1"
elementFormDefault="qualified" xmlns:itemabcs="http://xmlns.oracle.com/ABCSImpl/EBIZ/Core/Item/V1"
xmlns:itemebo="http://xmlns.oracle.com/EnterpriseObjects/Core/EBO/Item/V1"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:svcdoc="http://xmlns.oracle.com/Services/Documentation/V1"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:client="http://xmlns.oracle.com/SyncItemEBIZProvBPELABCSImpl"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:itemabo="http://www.example.org/SyncItemPublicationInput">
<xsd:import namespace="http://xmlns.oracle.com/EnterpriseObjects/Core/EBO/Item/V1" schemaLocation="http://ap6032fems.us.oracle.com:7831/AIAComponents/EnterpriseObjectLibrary/Release1/Core/EBO/Item/ItemEBM.xsd"/>
<xsd:import namespace="http://www.example.org/SyncItemPublicationInput" schemaLocation="http://ap6032fems.us.oracle.com:7831/AIAComponents/ApplicationObjectLibrary/EBiz/ApplicationInterfaces/Item/Schemas/ItemABM.xsd"/>
</xsd:schema>
</types>
<message name="SyncItemRequestMessage">
<part name="SyncItemPublication" element="itemebo:SyncItemPublicationEBM"/>
</message>
<message name="SyncItemResponseMessage">
<part name="SyncItemPublicationConfirmation" element="itemebo:SyncItemPublicationConfirmationEBM"/>
</message>
<message name="FaultMessage">
<documentation>
<svcdoc:Message>
<svcdoc:Description>This message is used for propagating Error Context and Error Message</svcdoc:Description>
</svcdoc:Message>
</documentation>
<part name="FaultMessage" element="corecom:Fault"/>
</message>
<message name="SyncItemABMRequestMessage">
<part name="Item" element="itemabo:item"/>
</message>
<message name="SyncItemABMResponseMessage">
<part name="ItemStatus" element="itemabo:itemStatus"/>
</message>
<portType name="SyncItemEBIZProvBPELABCSImpl">
<operation name="SyncItemPublication">
<input message="itemabcs:SyncItemRequestMessage"/>
<output message="itemabcs:SyncItemResponseMessage"/>
<fault name="fault" message="itemabcs:FaultMessage"/>
</operation>
</portType>
<plnk:partnerLinkType name="SyncItemEBIZProvBPELABCSImpl">
<plnk:role name="SyncItemEBIZProvBPELABCSImplProvider">
<plnk:portType name="client:SyncItemEBIZProvBPELABCSImpl"/>
</plnk:role>
<plnk:role name="SyncItemEBIZProvBPELABCSImplRequester">
<plnk:portType name="client:SyncItemEBIZProvBPELABCSImplCallback"/>
</plnk:role>
</plnk:partnerLinkType>
<bpws:propertyAlias propertyName="pns1:Item_Name" xmlns:ns1="http://xmlns.oracle.com/pcbpel/adapter/file/Write_ItemABM_To_File/"
messageType="ns1:item_msg" part="item" query="/itemabo:item/item_name"/>
<bpws:propertyAlias propertyName="pns1:Item_Name" xmlns:ns1="http://xmlns.oracle.com/pcbpel/adapter/file/Read_ItemStatus_FromFile/"
messageType="ns1:itemStatus_msg" part="itemStatus" query="/itemabo:itemStatus/item_name"/>
<bpws:propertyAlias propertyName="pns1:Item_Name" messageType="itemabcs:SyncItemRequestMessage" part="SyncItemPublication"
query="/itemebo:SyncItemPublicationEBM/itemebo:DataArea/itemebo:SyncItemPublication/itemebo:ItemPublicationLine/itemebo:Item/itemebo:Base/itemebo:Name"
xmlns:ns1="http://schemas.xmlsoap.org/ws/2003/03/addressing" xmlns:ns2="http://schemas.xmlsoap.org/ws/2002/04/secext"/>
</definitions>
Any clues for the wrong ?
Thanks
PraveenLogs from EM
Caused by: com.oracle.bpel.client.BPELFault: faultName: {{http://xmlns.oracle.com/EnterpriseServices/Core/Item/V1}FaultMessage}
messageType: {{http://xmlns.oracle.com/ABCSImpl/EBIZ/Core/SyncItemEBIZProvBPELABCSImpl/V1}SyncItemResponseMessage}
parts: {{SyncItemPublicationConfirmation=<SyncItemPublicationConfirmationEBM xmlns:itemebo="http://xmlns.oracle.com/EnterpriseObjects/Core/EBO/Item/V1" xmlns="http://xmlns.oracle.com/EnterpriseObjects/Core/EBO/Item/V1">
<corecom:EBMHeader xmlns:corecom="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V1">
<corecom:EBMName>SyncItemPublicationConfirmationEBM</corecom:EBMName>
<corecom:EBOName>ItemEBO</corecom:EBOName>
<corecom:CreationDateTime>2007-10-15T23:40:27-08:00</corecom:CreationDateTime>
<corecom:VerbCode>SyncItem</corecom:VerbCode>
<corecom:EBMTracking>
<corecom:SequenceNumber>2</corecom:SequenceNumber>
<corecom:ExecutionUnitName>SynItemProvABCSImpl</corecom:ExecutionUnitName>
</corecom:EBMTracking>
</corecom:EBMHeader>
[b]-----Remainig Response Payload--------
at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.createBPELFault(BPELActivityWMP.java:476)
at com.collaxa.cube.engine.ext.wmp.BPELReplyWMP.__executeStatements(BPELReplyWMP.java:123)
at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:195)
at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3672)
at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1650)
at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:184)
at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:276)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5658)
at com.collaxa.cube.engine.CubeEngine.callbackPerformer(CubeEngine.java:1874)
at com.collaxa.cube.engine.delivery.DeliveryHelper.callbackPerformer(DeliveryHelper.java:803)
at com.collaxa.cube.engine.delivery.DeliveryService.handleCallback(DeliveryService.java:783)
at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleCallback(CubeDeliveryBean.java:378)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at com.evermind.server.ThreadState.runAs(ThreadState.java:648)
at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
at CubeDeliveryBean_LocalProxy_4bin6i8.handleCallback(Unknown Source)
at com.collaxa.cube.engine.dispatch.message.instance.CallbackDeliveryMessageHandler.handle(CallbackDeliveryMessageHandler.java:49)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:138)
at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.SetContextActionInterceptor.invoke(SetContextActionInterceptor.java:44)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
at oracle.j2ee.connector.messageinflow.MessageEndpointImpl.OC4J_invokeMethod(MessageEndpointImpl.java:297)
at WorkerBean_EndPointProxy_4bin6i8.onMessage(Unknown Source)
at oracle.j2ee.ra.jms.generic.WorkConsumer.run(WorkConsumer.java:266)
at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
Thanks
Praveen
Maybe you are looking for
-
Sharing photos between different accounts on a single comp
I wish to not only share my photos with my wife's account on my computer, but let her import photos, etc. With iTunes, I was able to move the music folder to the /users/shared directory and then change the folder location preference in iTunes. iPhoto
-
Open 0Query_Template in WAD get red error
Some documentation says we can't open 0Query_Template (with Notepad or some web development too), but we don't know how to locate this 0Query_Template file in Notepad or other web development tool. Then the only choice left would be to open this 0Qu
-
Installer une version CD d'Adobe Photoshop Élément 12 sur Mac Book Air (qui n'a pas de lecteur CD)
Bonjour, je désire installer une version 12 d'Adobe Photoshop Élément que j'ai acheté sur CD, sur MacBook Air. Malheureusement, j'ai essayé en copiant le CD sur une clé USB et en installant à partir de l'USB, mais cela me dit que la version est pirat
-
Granting select on all objects of apps in R12
Hi All, How can I achieve like user xxx having read only access to apps user objects in EBS R12. Best Regards,
-
hi all, can anybody tell me if you can change the font size on the e65 and if so how? thanxMessage Edited by jp47 on 19-Mar-2007 08:56 PM