Data access problems for Oracle data sources
Use troubleshooting tips for help accessing Oracle data sources.
What error do you see when you try to access your Oracle-based data source?
- Invalid Oracle URL is specified
- DSRA0080E: Exception was received by the data store adapter. See original exception message: ORA-00600
- DSRA8100E: Unable to get a {0} from the data source. Explanation: See the linkedException for more information.
- Error while trying to retrieve text for error
- Class loader errors occur when using an Oracle OCI driver as your JDBC provider
- java.lang.UnsatisfiedLinkError when connecting to an Oracle data source
- Errors occur when referencing Oracle classes or when connecting to an Oracle data source
- WSVR0016W: Class path entry for the Oracle JDBC Thin Driver has an invalid variable
- Transaction recovery failure (for XA data sources)
- Application server receives an error in the SystemOut.log file when it registers the Oracle JDBC Diagnosability MBean
Invalid Oracle URL is specified
This error might be caused by an incorrectly specified URL on the URL property of the target data source.
Examine the URL property for the data source object in the administrative console to ensure that it is correct.
- For the thin driver: jdbc:oracle:thin:@//hostname:1521/myDatabase
- For the thick (OCI) driver: jdbc:oracle:oci:@tnsname1
DSRA0080E: Exception was received by the data store adapter. See original exception message: ORA-00600
A possible reason for this exception is that the version of the Oracle JDBC driver being used is older than the Oracle database. It is possible that more than one version of the Oracle JDBC driver is configured on the WebSphere® Application Server.
Examine the version of the JDBC driver. Sometimes you can determine the version by looking at the class path to determine what directory the driver is in.
import java.sql.*;
import oracle.jdbc.driver.*;
class JDBCVersion
{
public static void main (String args[])
throws SQLException
{
// Load the Oracle JDBC driver
DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
// Get a connection to a database
Connection conn = DriverManager.getConnection
("jdbc:oracle:thin:@appaloosa:1521:app1","sys","change_on_install");
// Create Oracle DatabaseMetaData object
DatabaseMetaData meta = conn.getMetaData();
// gets driver info:
System.out.println("JDBC driver version is" + meta.getDriverVersion());
}
}
If the driver and the database are at different versions, replace the JDBC driver with the correct version. If multiple drivers are configured, remove any that occur at the incorrect level.
DSRA8100E: Unable to get a {0} from the data source. Explanation: See the linkedException for more information.
When using an oracle thin driver, Oracle creates a java.sql.SQLException: invalid arguments in call error if no user name or password is specified when getting a connection. If you see this error while running WebSphere Application Server, the alias is not set.
To remove the exception, define the alias on the data source.
Error while trying to retrieve text for error
The likely cause of this error is that the Oracle OCI driver is being used with an ORACLE_HOME property that is either not set or is set incorrectly.
To correct the error, examine the user profile that WebSphere Application Server is running under to verify that the $ORACLE_HOME environment variable is set correctly.
Class loader errors occur when using an Oracle OCI driver as your JDBC provider
When you configure an Oracle OCI driver as your JDBC provider, you must specify the path to where the native libraries are stored. If you did not specify a native library path, the first time you try to connect using this provider, class loader errors occur.
To correct this problem, in the administrative console, click Native library path field.
, select the Oracle OCI driver, and then specify the path to the native libraries in thejava.lang.UnsatisfiedLinkError when connecting to an Oracle data source
The environment variable LIBPATH might not be set or is set incorrectly, if your data source creates an UnsatisfiedLinkError error, and the full exception indicates that the problem is related to an Oracle module.
- Examine the user profile under which the WebSphere Application Server is running to verify that the LIBPATH environment variable includes Oracle libraries.
Errors occur when referencing Oracle classes or when connecting to an Oracle data source
Receive java.lang.NullPointerException errors when referencing Oracle classes, or internal error: oracle.jdbc.oci. OCIEnv errors when connecting to an Oracle data source
The problem might be that the OCI driver is being used on an AIX® machine, the LIBPATH is set correctly, but the ORACLE_HOME environment variable is not set or is set incorrectly. You can encounter an exception similar to either of the following when your application attempts to connect to an Oracle data source:
To correct the problem, examine the user profile that WebSphere Application Server is running under to verify that it has the $ORACLE_HOME environment variable set correctly, and that the $LIBPATH includes $ORACLE_HOME/lib.
WSVR0016W: Class path entry for the Oracle JDBC Thin Driver has an invalid variable
This error occurs when there is no environment variable defined for the property, ORACLE_JDBC_DRIVER_PATH.
Verify this problem in the administrative console. Go to ORACLE_JDBC_DRIVER_PATH is defined.
to verify that the variableTo correct the problem, click New and define the variable. For example,
name: ORACLE_JDBC_DRIVER_PATH, value :
c:\oracle\jdbc\lib. Use a value that names the directory in your operating
system that contains the ojdbc6.jar
file (or the ojdbc6_g.jar
file
to enable Oracle trace.)
Transaction recovery failure (for XA data sources)
Problem
WTRN0037W: The transaction service encountered an error on an xa_recover operation.
The resource was com.ibm.ws.rsadapter.spi.WSRdbXaResourceImpl@1114a62.
The error code was XAER_RMERR. The exception stack trace follows:
javax.transaction.xa.XAException
at oracle.jdbc.xa.OracleXAResource.recover(OracleXAResource.java:726)
at com.ibm.ws.rsadapter.spi.WSRdbXaResourceImpl.recover(WSRdbXaResourceImpl.java:954)
at com.ibm.ws.Transaction.JTA.XARminst.recover(XARminst.java:137)
at com.ibm.ws.Transaction.JTA.XARecoveryData.recover(XARecoveryData.java:609)
at com.ibm.ws.Transaction.JTA.PartnerLogTable.recover(PartnerLogTable.java:511)
at com.ibm.ws.Transaction.JTA.RecoveryManager.resync(RecoveryManager.java:1784)
at com.ibm.ws.Transaction.JTA.RecoveryManager.run(RecoveryManager.java:2241)
Cause
Oracle requires services such as the WebSphere Application Server transaction service to have special permissions for performing transaction recoveries.
Solution
grant select on pending_trans$ to public;
grant select on dba_2pc_pending to public;
grant select on dba_pending_transactions to public;
grant execute on dbms_system to <user>;
User
is a user ID in the application server that is authorized to perform transaction recovery for the XA
data source. If you have not authorized any user IDs to perform transaction recovery, the
application server uses the login alias for the data source as the user ID.This problem is mentioned under Oracle bug: 3979190. Running the preceding commands solves the problem.
Application server receives an error in the SystemOut.log file when it registers the Oracle JDBC Diagnosability MBean
E Error while registering Oracle JDBC Diagnosability MBean.
javax.management.MalformedObjectNameException: Invalid character '' in value part of property
This error occurs during the initial connection to an Oracle database because the diagnosis for the MBean is not properly initialized.