Oracle Error ORA-12650 when starting Master
search cancel

Oracle Error ORA-12650 when starting Master


Article ID: 85049


Updated On:


CA Automic Applications Manager (AM)


Error Message :
ErrorMsg: AwE-5001 Database Query Error 
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 
Details: null
java.sql.SQLException: Oracle Error ORA-12650
at oracle.jdbc.driver.T4CConnection.logon(
at oracle.jdbc.driver.PhysicalConnection.<init>(
at oracle.jdbc.driver.T4CConnection.<init>(
at oracle.jdbc.driver.T4CDriverExtension.getConnection(
at oracle.jdbc.driver.OracleDriver.connect(
at java.sql.DriverManager.getConnection(



All Versions


This is an Oracle error which occurs when the client and server have no algorithm in common for the encryption, data integrity or both.


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.


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 supported release of Java (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.3+ allows for stronger encryption with Java 8 +, along with implementing the encryption changes to the awenv.ini as noted above. You may also want to upgrade the ojdbc.jar file in the $AW_HOME/web/classes directory to the latest ojdbc.jar version applicable to the database release  if you still have connection issues after updating the awenv.ini and restarting.

Additional Information

Workaround :