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.
...
Thursday, May 11, 2017
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 ...
[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...
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-11800Unimplemented 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...
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-11616DBWriteInteractionSpec 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...
Subscribe to:
Posts (Atom)
