[PCA 2.x / OVM] Troubleshooting Password issues for Connecting to Oracle VM Weblogic Data Source
(Doc ID 2232064.1)
Last updated on MARCH 08, 2024
Applies to:
Private Cloud Appliance - Version 1.0.1 to 2.2.2 [Release 1.0 to 2.0]Oracle VM - Version 3.0.1 and later
Oracle Cloud Infrastructure - Version N/A and later
Linux x86-64
Purpose
In the scope of connecting from the Weblogic Server which hosts the VM Manager to the MySQL database which holds the VM Manager Data, there can be several reasons why the connection fails to get established. This troubleshooting guide outlines part of them and should serve as a basis when troubleshooting such issues.
Troubleshooting Steps
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Purpose |
| Troubleshooting Steps |
| 1. Check that the ovmm_mysql service is running |
| 2. Test connection from the root user on the Oracle VM Manager / Management Node |
| 3. Check that the appropriate user(s) have been created. |
| 4. If the password is different for the ovs user, run : |
| 5. Check that you are able to log in to mysql using this password, e.g. : |
| 6. Restart the VM Manager Service : |
| 7. Check if the Oracle VM Manager is now able to open a connection to the database. |
| 8. If it is not working at this point, please raise a new Service Request with Oracle VM / Private Cloud Appliance support mentioning this document's identifier. |
| a. cp /u01/app/oracle/ovm-manager-3/machine1/base_adf_domain/config/jdbc/OVMDS-6373-jdbc.xml /u01/app/oracle/ovm-manager-3/machine1/base_adf_domain/config/jdbc/OVMDS-6373-jdbc.xml.pre.passwords |
| b. su to oracle user |
| c. Change directory to (important) : |
| d. From that directory , run : |
| e. This will bring the WLST prompt : |
| f. Run the following commands sequence, replacing NEW_PASSWORD with the new password used at step 4 : |
| g. copy the hash generated |
| h. insert the hash generated including {AES} to the following file : |
| i. restart the ovmm service : |