Patch 6501312 - BPEL Repository spring cleaning

A new patch with id 6501312 creates a purge_instances procedure in the oraclebpel schema that you can use to delete your old BPEL Process instances.

Currently (Thu Dec 13 15:36:56 CET 2007) there seemes to be a problem with the paths for this patch in unix so I installed it using the following procedure:

1 Copy the files in 6501312/files/bpel\system\database\scripts to $ORACLE_HOME/bpel/system/database/scripts

2. Run the sqlplus scrip to create index and create the procedure "purge_instances".

Example:

bash$ sqlplus /nolog
SQL*Plus: Release 10.1.0.5.0 - Production on Thu Dec 13 10:19:06 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> connect orabpel@instance
Enter password:
Connected.
SQL> @upgrade_6501312_oracle.sql
SQL> commit;
SQL> @purge_instances_oracle.sql

After this you may start your spring cleaning:

BEGIN
purge_instances(to_timestamp('2007-12-13 10:30:25','YYYY-MM-DD HH24:MI:SS'));
COMMIT;
END;

Happy cleaning!

Sphere: Related Content

[Error ORABPEL-10902]: compilation failed, XML parsing failed because ""

ORABPEL-10902 shows up from time to time to annoy any BPEL developer.

It could be (I think) somthing like:

1. General namespace errors
2. Incorrect variable errors
3. Variables that you try to access "out-of-scope"

The error message "" is not that helpful in any case, but if we change the 'verbose' setting to true in the ant build.properties file we get better information.

deployment tasksverbose = true

Thanks to Marc Kelderman, I can't wait until I get the next ORABPEL-10902!

Today we saw an ORA-600 when we added a diskgroup into our ASM instance... but that is a different story.

Sphere: Related Content

Trick Question - "good but expensive" vs "quick and dirty"

Your project manager has asked you to estimate the difference in cost between the "good but expensive", "quick and dirty" path or solution!

What should you do?

Steve McConnells answer in this blogentry is that you should ask three more questions:

1.How much it will cost to backfill the good path after you've already gone down the quick path?
2.If you choose the quick path now, how much does that slow down other work until you're able to retrofit the good path?
3.Is there a path that is quicker than the good path and that won't affect the rest of the system?

Steves Bottom line: When facing the prospect of taking on technical debt, be sure to generate more than two design options.

Sphere: Related Content

10.1.3.3.1 deployment

After deploying 10.1.3.3.1 I got the following startup errors (even if I followed the README to the point)

--------
07/12/11 22:10:41 Start process--------
07/12/11 22:11:39 log4j:WARN No appenders could be found for logger (wsif).
07/12/11 22:11:39 log4j:WARN Please initialize the log4j system properly.¨
07/12/11 22:11:44 WARNING: Application.setConfig Application: orabpel is in failed state as initialization failed. java.lang.InstantiationException: Error initializing ejb-modules: error in opening zip file; nested exception is: java.util.zip.ZipException: error in opening zip file
07/12/11 22:11:44 WARNING: Application.setConfig Application: hw_services is in failed state as initialization failed. java.lang.InstantiationException: Error initializing ejb-modules: [hw_services:hw_services_ejb:RemoteWorklistService] - Unable to load ejb-class oracle.tip.pc.services.hw.worklist.RemoteWorklistServiceBean, see section 23.2 of the EJB 2.1 specificationoracle.classloader.util.AnnotatedClassNotFoundException:
Missing class: oracle.tip.pc.services.hw.worklist.RemoteWorklistServiceBean
Dependent class: com.evermind.server.ejb.deployment.BeanDescriptor Loader: oc4j:10.1.3 Code-Source: /oracle/product/soa_10.1.3/j2ee/home/lib/oc4j-internal.jar Configuration: in META-INF/boot.xml in /oracle/product/soa_10.1.3/j2ee/home/oc4j.jar
This load was initiated at hw_services.root:0.0.0 using the Class.forName() method.
The missing class is available from the following locations:
1. Code-Source: /oracle/product/soa_10.1.3/bpel/system/services/lib/bpm-services.jar (from in /oracle/product/soa_10.1.3/j2ee/oc4j_soa/config/server.xml) This code-source is available in loader oracle.bpel.common:10.1.3. This shared-library can be imported by the "hw_services" application.

07/12/11 22:11:50 Initializing B2BDiscoveryServlet07/12/11 22:11:54 Finished initializing B2BDiscoveryServlet07/12/11 22:11:56 Oracle Containers for J2EE 10g (10.1.3.3.0) initialized

I then tried to redeploy BPEL services by using the $ORACLE_HOME/config/deploy_bpel.sh script.

This script gave me the following error:

config>> ./deploy_bpel.sh
BUILD FAILED/oracle/product/soa_10.1.3/bpel/system/services/install/ant-tasks/redeploy.xml:33: The following error occurred while executing this line:/oracle/product/soa_10.1.3/bpel/system/services/install/ant-tasks/redeploy.xml:66: Error while expanding /oracle/product/soa_10.1.3/bpel/system/services/lib/workflow_javadoc.jar

I then commeted out the workflow_javadoc.jar from bpel/system/services/install/ant-tasks/redeploy.xml, and then the redeploy works again!

Sphere: Related Content

10.1.3.3.1 Patchset Release now available!

Patchset 10.1.3.3.1 for 10.1.3.3.0 is avaliable as Patchid 6492514.

For more information see the BPEL home page.

Sphere: Related Content