We can check following to see if there is corruption in Oracle VM Manager Database.
Below are detailed steps for validating above points to determine if there is OVM DB corruption.
1) Look for ONF (Object Not Found) errors in OVM DB
For this login to the Host where OVM Manager is running and follow below steps to check if there are ONF errors in OVM DB.
a. Login to EMOC Control vserver which runs OVMM as root user.
b. Login to OVM shell prompt by running below command.
In above command replace <password> with the OVMM admin user password. You will be logged into ">>>" OVMM shell prompt.
c. Run below commands in same order in OVMM shell prompt.
If there is no ONF errors we should see blank output []. If we see any output when running above steps, it means that there is corruption and inconsistencies in OVM DB.
2) Validate if Daily AutoFullBackup DB backups stopped working.
Run below command to validate if there are AutoFullBackup DB backups are happening regularly.
Please note above is the default OVM DB autobackups directory. If you have changed the default directory make changes to above command as needed.
3) Check if there are any "cluster is null" or "ObjectNotFound" errors in OVM Manager Admin Server logs
For this login to the Host where you have OVM Manager running and run below command.
If you see ObjectNotFound or "cluster is null" errors as follows, that means that there is corruption in OVM Manager DB.
Above is the default OVM Manager Admin Server log directory in OVM 3.3 & higher versions. In some versions of OVM Manager (old versions) the Admin Server log directory may be different.
Oracle VM Manager versions 3.3 & Above
https://docs.oracle.com/cd/E50245_01/
- Look for ONF (Object Not Found) errors in OVM DB
- Validate if Daily AutoFullBackup DB backups stopped working.
- Look for Object Not Found (ONF) and Cluster is null errors in OVM Manager Admin Server logs.
Below are detailed steps for validating above points to determine if there is OVM DB corruption.
1) Look for ONF (Object Not Found) errors in OVM DB
For this login to the Host where OVM Manager is running and follow below steps to check if there are ONF errors in OVM DB.
a. Login to EMOC Control vserver which runs OVMM as root user.
b. Login to OVM shell prompt by running below command.
/usr/bin/ovm_shell.sh -u admin -p <password>
In above command replace <password> with the OVMM admin user password. You will be logged into ">>>" OVMM shell prompt.
c. Run below commands in same order in OVMM shell prompt.
om = OvmClient.getOvmManager()
f = om.getFoundryContext()
f.fixupScan()
If there is no ONF errors we should see blank output []. If we see any output when running above steps, it means that there is corruption and inconsistencies in OVM DB.
2) Validate if Daily AutoFullBackup DB backups stopped working.
Run below command to validate if there are AutoFullBackup DB backups are happening regularly.
ls -ldt /u01/app/oracle/mysql/dbbackup/Auto*
Please note above is the default OVM DB autobackups directory. If you have changed the default directory make changes to above command as needed.
3) Check if there are any "cluster is null" or "ObjectNotFound" errors in OVM Manager Admin Server logs
For this login to the Host where you have OVM Manager running and run below command.
egrep -iR "cluster is null|ObjectNotFound" /u01/app/oracle/ovm-manager-3/domains/ovm_domain/servers/AdminServer/logs/AdminServer*
If you see ObjectNotFound or "cluster is null" errors as follows, that means that there is corruption in OVM Manager DB.
<Exception in archiver moving jobs to jpa store: No such object (level 1), cluster is null: <XXXX>
<Day> <Mon DD Time> com.oracle.odof.exception.ObjectNotFoundException: No such object (level 1), cluster is null: <XXXX>
<Day> <Mon DD Time> com.oracle.odof.exception.ObjectNotFoundException: No such object (level 1), cluster is null: <XXXX>
Above is the default OVM Manager Admin Server log directory in OVM 3.3 & higher versions. In some versions of OVM Manager (old versions) the Admin Server log directory may be different.
Products to which Article Applies
Oracle VM Manager versions 3.3 & Above
Additional References
tarun boyella
No comments:
Post a Comment