Posts

Showing posts from April, 2010

To delete/undeploy multiple BPEL processes from BPELConsole (10.1.3.4)

Image
There was some performance issue in Development server due to thousands of unused/junk BPEL processes deployed within the container , but I couldn’t able to delete all at once as there was no option and if deleting one by one could take many hours to perform this , then I found a solution over the net which changes little code of some JSPs of the product ( Although not change in the product code not supported by Oracle). Here is the process to do the same which saved huge amount of hours and work :- Note :- Replace all "*" with "<" and "#" with ">" 1) Take a backup of the files; bulkUpdateProcess.jsp and doBulkUpdateProcess.jsp. The path is :- $ORACLE_HOME/j2ee/oc4j_soa/applications/orabpel/console 2) Add the below code in the the file bulkUpdateProcess.jsp. (Add the code after the label: *label for="processStateOff"# *%= I18nUtil.getString("off", locale)%# */label#) Code to be added :- ---- *p# *

ORABPEL-05002 Message handle error.

ORABPEL-05002 Message handle error. An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.instance.CallbackDeliveryMessage"; the exception is: JTA transaction is not present or the transaction is not in active state. The current JTA transaction is not present or it is not in active state when processing activity or instance "26090849-BpInv2-BpSeq0.3-3". The reason is The execution of this instance "26090849-BpInv2-BpSeq0.3-3" for process "Test" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information.. Please consult your administrator regarding this error. Symptoms :- The error is occurring intermittently in BPEL logs for test domain in the format above. Cause:- It’s a generic error but in our case it is request time out which is due to inappropriate value of “tran

java.sql.SQLException: Connection Cache with this Cache Name is Disabled

Error :- JDBC Connection; nested exception is java.sql.SQLException: Connection Cache with this Cache Name is Disabled Caused by: org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is java.sql.SQLException: Connection Cache with this Cache Name is Disabled Caused by: java.sql.SQLException: Connection Cache with this Cache Name is Disabled at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:138) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:175) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:240) at oracle.jdbc.pool.OracleImplicitConnectionCache.getConnection(OracleImplicitConnectionCache.java:310) at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:286) at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:179) at oracle.jdbc.pool.OracleDataSource.get

An error occurred while making the JMX RMI connection and it should have only one AS-control running in Application server 10.1.3.4.

An error occurred while making the JMX RMI connection and it should have only one AS-control running in Application server 10.1.3.4. Resolution Steps :- 1) Go to $OH/j2ee/test_oc4j/config path ( In each OC4J) 2) Update the new password for "oc4jadmin" in system-jazn-data.xml file with "!newpasword". "!" is used for encrytption. 3) Go to $OH/j2ee/home/persistence/ascontrol/ascontrol/securestore directory. 4) Delete the contents of the "securestore" directory . 5) Restart the application server or oc4j container.

How to re-point nodes to current Oracle Grid Agent to new Grid OMS (10.2.0.5)

It is a two step process as far as my documentation goes given below :- (i) STEP1 :- a) Remove the agent from the old OMS otherwise the same agent will not be able to point to the new OMS as it is registered in the old OMS with below tasks :- a.1)From OMS, drop all the Targets on the host to be removed, except the Host and Agent.All targets except the Host and Agent should now be gone from the OMS. a.2) Confirm the targets (except Host and Agent) are removed successfully and completely from the OMS: Click on "Setup" in upper right. Click on the "EM 10g Grid Control Management System" tab You will see this information on the page: --> Management Services and Repository --> Overview page --> General section --> Deleted Targets: < click on the digit listed here > a.3) Click on "Deleted Targets" (Note this only appears once a delete is attempted.) a.4) Confirm that the "Time Delete Completed" column is filled in;