ERROR: 1045 (28000): Access denied for user 'abc'@'localhost' (using password: YES)

This issue comes when you are not entering your MYSQL connection string properly. Below screenshot shows how to connect to MYSQL and avoid this issue.

Read More

Jdeveloper windows not showing

 Problems:

Jdeveloper windows are not showing properly 

Solution:

Rename or delete this file from Jdeveloper direcotry 

windowinglayout.xml

just search it and delete it

second option 

Reset windows to factory settings 

Read More

[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