Oracle BPEL & ESB - Error & Resolution - 2

Error 8: An unhandled exception has been thrown in the ESB system. The exception reported is: "java.util.zip.ZipException: error in opening zip file"
Resolution: Same as that of Error 6 & 7.


Error 9: xref:lookupxref not found when compiling bpel process. This happens when we use xref:lookupxref in assign activity instead of transformation activity.
Resolution: Search for http://www.oracle.com/XSL/Transform/java/oracle.apps.aia.core.xpath.AIAFunctions in .bpel file and replace the namespace with xref. Eg if its
xmlns:ns14= http://www.oracle.com/XSL/Transform/java/oracle.apps.aia.core.xpath.AIAFunctions
then replace ns14 with xref ie
xmlns:xref= http://www.oracle.com/XSL/Transform/java/oracle.apps.aia.core.xpath.AIAFunctions


Error 10: "No WebService Provider is registered at this URL" when trying to open any service url on ESB Console.
Resolution: Workaround is to modify $Oracle_HOme/j2ee/oc4j_soa/config/default-web-site.xml file.
Remove 'ohs-routing=true' if its already present for esb-dt and esb-rt. If its absent then add it for esb-dt and esb-rt.
Restart the server.
Another workaround is to click on 'DISABLE' and then 'ENABLE' if the error is coming for few services only.
As a fix you have to apply MLR#18 on 10.1.3.3.


Error 11: XPath expression failed to execute.
Error while processing xpath expression, the expression is ""ora:getFaultAsString()"", the reason is Variant not found.
The variant ""__fault"" has not been declared in the current scope. All variants must be declared in the scope before being accessed.
Please check that the variant ""__fault"" is properly declared; otherwise there may be a misspelling in the name of the variant.
.
Please verify the xpath query.
Resolution: The cause of this error is assigning value to outofscope variable. When a fault is created such as remote fault, a variable is generated for it say SystemFaultMsg. Now if you try assign ora:getFaultAsString() to this variable then it will throw the above fault. So create a new global fault variable and then assign ora:getFaultAsString() to it.


Error 12: failed due to: null; nested exception is:
javax.resource.ResourceException when invoking an OPCODE of BRM.
Resolution:1. add false
in the partnerlink binding in bpel.xml of the partnerlink invoking which this error is coming.
2. You can try clearing the wsdl cache also from your bpel console.


Error 13:Oracle BPEL Domain Initialization Failed
Reported Error:
Incorrect db schema version.
The database schema version '2.0.51' from the database does not match the
version '10.1.3.3.17' expected by the server.
The database schema currently in place has probably been configured for a
previous release please re-install the database schema and try to start the server again.
Resolution: This error may be caused because of MLR rollback.
1. Source DB env
2. Login to your DB as orabpel
sqlplus
Enter user-name: orabpel
Enter password: Please check it with your admin about this pwd
3. SQL> select guid from version;
(Note down this value. It must be equal to 2.0.51 as shown in the error message)
4. SQL> UPDATE VERSION SET guid = '10.1.3.3.17';
5. SQL>exit
6. Restart your server

Oracle BPEL & ESB - Error & Resolution

I think its better to start my blogging with the errors that I have faced during development and their resolutions which worked for me. I am very excited to bring forth the first blog of my life. Your positive response will encourage me to share more and more of my knowledge with you. Sometimes for an error there are more than one resolution, I'll be highly thankful to you if you can share the other resolutions which are not present in this blog.

Error 1: XML-22036: (Error) Cannot convert result tree fragment to NodeSet
Detail: This error comes in the transformation file. This is due to the version mismatch of stylesheet.
Resolution: Change the version of stylesheet from '1.0' to '2.0' . Now redeploy your process.

Error 2: Invalid xml document.
According to the xml schemas, the xml document is invalid.
Please make sure that the xml document is valid against your schemas.
Resolution: One cause of this error could be when you set “validateXML” property “true”.
Please make it false and then retry.
Goto BPELConsole-> ManageBPELDomain ->Set validateXML =false.

Error 3: oracle.xml.parser.v2.XMLParseException: PI with the name 'xml' can occur only in the beginning of the document.
Resolution: Check the transformation file and ensure that "<?xml version="1.0" encoding="UTF-8" ?>" is the first line in all the XSL file.

Error 4: failed due to: null; nested exception is: javax.resource.ResourceException
Resolution: Add <property name="cacheWSIFPort">false</property>
in the partnerlink binding in bpel.xml of the partnerlink invoking which this error is coming.
Another resolution is to try clearing the wsdl cache at BPELConsole->BPEL Process-> Clear the wsdl cache.

Error 5:The Method 'commit' Cant Be Called When a Global Transaction is Active Displayed in log.xml
Resolution: Amend ESBDataSource to local in the $ORACLE_HOME/j2ee//config/data-sources.xml
i.e. <managed-data-source name="ESBDataSource" connection-pool-name="ESBPool"
jndi-name="jdbc/esb" tx-level="local" /><managed-data-source name="ESBDataSource" level="local">

Error 6:ESB Services disappeared
Check for "connection pool is full" in $OracleHome/opmn/logs/*soa*
Error 7:Unable to delete or register ESB on ESB console
Resolution: Login to EM console
Goto Cluster Topology -> Application Server ->oc4j_soa -> Application:default -> ResourceAdapter:OracleASjms ->Edit Connection Factory: OracleASjms/MyXATCF -> ConnectionPool:private
Increase Maximum Connections to 100.