search cancel

Upgrade of APM EM fails if Oracle DB password contains $ or ' characters


Article ID: 190486


Updated On:


CA Application Performance Management Agent (APM / Wily / Introscope) CA Application Performance Management (APM / Wily / Introscope) INTROSCOPE DX Application Performance Management


When upgrading the APM Enterprise Manager from 10.5 to 10.7, if the Oracle database user's password contains the $ or ' characters it the upgrade will fail as it will not be able to connect to the APM database.

The Introscope_10.7.0.45_InstallLog.log shows: 
Upgrade Database Schema Failed
                          Status: ERROR
                          Additional Notes: ERROR - . Check /apps/CA/Introscope10.5.2_SP2/install/schematools.log for more details

The schematools.log show the following error:

7/31/19 11:26:33.105 AM EDT [INFO] [main] [root] [UpgradeSchema] - DBDetails: hostName: port: 1521 databaseName: cem user: apmuser
7/31/19 11:26:33.114 AM EDT [INFO] [main] [root] [UpgradeSchema] - DBType: oracle
7/31/19 11:26:33.114 AM EDT [INFO] [main] [root] [UpgradeSchema] - Desired Version:
7/31/19 11:26:33.115 AM EDT [INFO] [main] [root] [UpgradeSchema] - Scripts location: /apps/CA/Introscope10.5.2_SP2/install/oracle/database-scripts
7/31/19 11:26:41.285 AM EDT [ERROR] [main] [root] [UpgradeSchema] - ORA-01017: invalid username/password; logon denied

java.sql.SQLException: ORA-01017: invalid username/password; logon denied


APM 10.x to 10.7 Upgrade
Oracle DB


The root cause of the exception was found to be a "$" character in the database password.
"$" is a special character used by the InstallAnywhere software to refer to variables.
A single quote character "'" is also known to be another special character for InstallAnywhere that can cause a similar error.


The workaround is to change the APM Oracle DB user password to a text only (no special characters) password prior to the upgrade. Then run the upgrade and when complete, change the password back to the desired password. Once the password has bee changed back,  update the EM_HOME/config/tess-db-cfg.xml file to reflect the new current password.

Additional Information

CA APM tess-db-cfg.xml file does not get updated with correct Oracle parameters for the APM database after a new APM EM install: