[SQLServer]Could not find stored procedure 'master..xp_jdbc_open2'.

Problem:

<Console encountered the following error java.sql.SQLException: [FMWGEN][SQLServer JDBC Driver][SQLServer]Could not find stored procedure 'master..xp_jdbc_open2'.

Workaround:

Go to your Data Source configuration on Weblogic Console and change the Driver Class Name to following:

weblogic.jdbc.sqlserver.SQLServerDriver

These are the drivers for NonXA data source. 

However if you want to create an XA connection with MS SQL server then some configuration are required at MS SQL side. 

Go to /fmwinfra/oracle_common/modules/datadirect of your weblogic installation directory. Copy these two files instjdbc.sql and x64sqljdbc.dll if you are using 64 bit SQL server otherwise select as per version from the same directory to MS  SQL Installation bin directory. 

Execute instjdbc.sql  in MS SQL server. Now create XA data source in your weblogic server. It should work. If there are multiple SQL servers then you will have to do the same configuration on all SQL servers. Hope this will help. 

Read More

Conversion of type '' whose JDBC type is OTHER to a Java object is not supported.

While calling a Store procedure from MS SQL server, following issue can come

Problem:

Conversion of type 365366 whose JDBC type is OTHER to a Java object is not supported.

An attempt was made to convert type 365366 to a Java object using an unsupported JDBC type: OTHER.
; nested exception is: 
BINDING.JCA-11800
Unimplemented object conversion.
Conversion of type 365366 whose JDBC type is OTHER to a Java object is not supported.
An attempt was made to convert type 365366 to a Java object using an unsupported JDBC type: OTHER.

Use a data type with a supported JDBC type.

Solution:

Go to your Database adapter connection factory and change PlateformClassName from

org.eclipse.persistence.platform.database.Oracle10Platform

To

oracle.toplink.platform.database.SQLServerPlatform

Read More

Caused by java.sql.SQLException: Cannot call Connection.commit in distributed transaction

Problem:
unknown failed. Descriptor name: [unknown].
Caused by java.sql.SQLException: Cannot call Connection.commit in distributed transaction.  Transaction Manager will commit the resource manager when the distributed transaction is committed..
; nested exception is: 
BINDING.JCA-11616
DBWriteInteractionSpec Execute Failed Exception.
unknown failed. Descriptor name: [unknown].
Caused by java.sql.SQLException: Cannot call Connection.commit in distributed transaction.  Transaction Manager will commit the resource manager when the distributed transaction is committed..
Please see the logs for the full DBAdapter logging output prior to this exception.  This exception is considered retriable, likely due to a communication failure.  To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml).  To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff.  All properties are integers.


Workaround:

Uncheck Support global transaction option in data source Transaction section as shown below:

Best Camping Cot

Read More

Resolved:Connection refused: connect. CFGFWK-60850: Test Failed!

While extending SOA domain for OSB, we can come across the following issue


Component Schema=OSB JMS Reporting Provider Driver=org.apache.derby.jdbc.ClientDriver
URL=jdbc:derby://localhost:1527/osbexamples;ServerName=localhost;databaseName=osbexamples
User=DEV_SOAINFRA Password=******** SQL Test=SELECT 1 FROM SYS.SYSTABLES  java.net.ConnectException :
 Error connecting to server localhost on port 1527 with message Connection refused: connect. CFGFWK-60850:  Test Failed!

OR

SQL Test=SELECT 1 FROM SYS.SYSTABLES  Insufficient data while reading from the network - expected a minimum of 6 bytes and received only 0 bytes.  The connection has been terminated. CFGFWK-60850:  Test Failed!

Solution:

This issue occurs due to wrong password, vendor or service name. To resolve this issue just make sure database connection string is fine as shown below:

Read More

java.lang.NoClassDefFoundError: sun/io/CharacterEncoding JDK Error Oracle SOA

While using JDK 8, following error might come in Oracle SOA.

java.lang.NoClassDefFoundError: sun/io/CharacterEncoding
        at oracle.j2ee.ws.common.util.TestPageUtils.encode(TestPageUtils.java:216)
        at oracle.j2ee.ws.server.management.mbeans.WebServiceOperation.createTestPagePath(WebServiceOperation.java:276)

Look like its not supported version of JDK for SOA. Try to install JDK 7 and then test. This error must resolve.   

Read More

There is not an activity (receive/pick) to start the process

Sometimes when we create SOA BPEL with define service interface later, we get the below error even if we add the receive activity.

• Error(52): There is not an activity (receive/pick) to start the process
• Error(52): Initial activity is invalid. An initial activity must be of a receive or pick activity.
• Error: there is no receive activity that starts the process 

Following is the error snapshot:

To resolve this issue open BPEL process in code view and changed the 'no' in receive activity to 'yes' as shown below

Before:

   <receive name="ReceiveInput" createInstance="no"

             variable="Receive1_Request-Response_InputVariable"

             partnerLink="HttpGet" portType="ns1:Request_Response_ptt"

             operation="Request-Response"/>

After

   <receive name="ReceiveInput" createInstance="yes"

             variable="Receive1_Request-Response_InputVariable"

             partnerLink="HttpGet" portType="ns1:Request_Response_ptt"

             operation="Request-Response"/>

Read More

Error occurred during initialization of VM

After fresh installation of Oracle SOA, I started getting the below error while starting servers.

Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.

After trying different solution from the Web I changed the JDK version and it started working fine. I was using C:\Oracle\Middleware\jdk160_24 JDK previously which did not work and then I updated it with C:\Program Files\Java\jdk1.8.0_51 in setDomainEnv file and it started working fine. 

Read More