Oracle Error ORA-12650 when starting Master
Article ID: 85049
Updated On:
Products
CA Automic Applications Manager (AM)
Issue/Introduction
Error Message :
ErrorMsg: AwE-5001 Database Query Error (12/4/15 9:32 AM)
Details: null
java.sql.SQLException: Oracle Error ORA-12650
When starting the Applications Manager (AM) processes the following error is seen in the RmiServer.log and the RmiServer process fails to start.
ErrorMsg: AwE-5001 Database Query Error (12/4/15 9:32 AM)
Details: null
java.sql.SQLException: Oracle Error ORA-12650
When starting the Applications Manager (AM) processes the following error is seen in the RmiServer.log and the RmiServer process fails to start.
ErrorMsg: AwE-5001 Database Query Error (12/4/15 9:32 AM)
Details: null
java.sql.SQLException: Oracle Error ORA-12650
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:489)
at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:553)
at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:254)
at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:528)
at java.sql.DriverManager.getConnection(DriverManager.java:571)
java.sql.SQLException: Oracle Error ORA-12650
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:489)
at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:553)
at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:254)
at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:528)
at java.sql.DriverManager.getConnection(DriverManager.java:571)
Cause
Cause type:
Configuration
Root Cause: This is an Oracle error which occurs when the client and server have no algorithm in common for the encryption, data integrity or both.
Configuration
Root Cause: This is an Oracle error which occurs when the client and server have no algorithm in common for the encryption, data integrity or both.
Environment
OS Version: N/A
Resolution
The default net.encryption_types_client variable for Applications Manager can be changed by defining it in the $AW_HOME/site/awenv.ini.
This needs to be added the following under the [default] section of the file.
net.encryption_types_client=AES256
net.crypto_checksum_types_client=SHA256
Note: This is an example of setting AES256 and SHA256. Other encryption/checksum types can be added to the variable as well. You can confirm what should be required by looking at the database server side sqlnet.ora file for your Oracle install.
Ensure the master is on a version of Java which supports the higher encryption (1.8).
Once in place the Application Manager back end processes will need to be stopped and restarted.
The setting can be confirmed by looking in the RmiServer log with debug enabled. The line will look as follows:
08:50:42.914 main: .AwEnvOptions: net.encryption_types_client = AES256
08:50:42.915 main: .AwEnvOptions: .AwEnvOptions: net.crypto_checksum_types_client = SHA256
08:50:42.915 main: .AwEnvOptions: net.crypto_checksum_types_client = MD5
08:50:43.177 main: .AxConnection: inUse (sync) null AM9 false
08:50:43.178 main: .AxConnection: inUse (sync) done null AM9
Applications Manager version 9.1 allows for stronger encryption if using Java 8 or above. It is advised to update to java 1.8 along with implementing the encryption changes to the awenv.ini as noted above. You may also want to upgrade the ojdbc6.jar file in the $AW_HOME/web/classes directory of the product to ojdbc7.jar if using Oracle 12c and Java 1.8 if you still have connection issues after updating the awenv.ini and restarting.
Fix Status: No Fix
Fix Version(s):
N/A
This needs to be added the following under the [default] section of the file.
net.encryption_types_client=AES256
net.crypto_checksum_types_client=SHA256
Note: This is an example of setting AES256 and SHA256. Other encryption/checksum types can be added to the variable as well. You can confirm what should be required by looking at the database server side sqlnet.ora file for your Oracle install.
Ensure the master is on a version of Java which supports the higher encryption (1.8).
Once in place the Application Manager back end processes will need to be stopped and restarted.
The setting can be confirmed by looking in the RmiServer log with debug enabled. The line will look as follows:
08:50:42.914 main: .AwEnvOptions: net.encryption_types_client = AES256
08:50:42.915 main: .AwEnvOptions: .AwEnvOptions: net.crypto_checksum_types_client = SHA256
08:50:42.915 main: .AwEnvOptions: net.crypto_checksum_types_client = MD5
08:50:43.177 main: .AxConnection: inUse (sync) null AM9 false
08:50:43.178 main: .AxConnection: inUse (sync) done null AM9
Applications Manager version 9.1 allows for stronger encryption if using Java 8 or above. It is advised to update to java 1.8 along with implementing the encryption changes to the awenv.ini as noted above. You may also want to upgrade the ojdbc6.jar file in the $AW_HOME/web/classes directory of the product to ojdbc7.jar if using Oracle 12c and Java 1.8 if you still have connection issues after updating the awenv.ini and restarting.
Fix Status: No Fix
Fix Version(s):
N/A
Additional Information
Workaround :
N/A
N/A
Feedback
Powered by
