Oracle Verified data is listed as incomplete for the following reason(s):

• At least one database installation (instance) was not successfully inventoried, due to connection or other issues.

Explanation

In OracleOvsService method ProcessSiosOvsDataAsync ovs_status.json file has status different than OK and NOT all databases are OK

Troubleshooting

1. Confirm that the prequisites have been met and all installation instructions followed. 
2. Ensure logging is set to verbose in snowagent.config and run a manual agent scan. Check the data\sios.rototaion.n.log(s).
3. Review the SIOS log for Oracle errors by searching for the string ORA-. Refer to the Example Issues below.
   • If you identify issues with the database like those provided below, please bring details to your Oracle database administrator to resolve. 
4. If you have not remedied the issue, please open a new case with Snow Support, providing the following information and observations you've collected during this troubleshooting:
   • All relevant software versions (snowagent, sios, siohws, java, oracle db version and edition if known.)
   • A snowpack with agent logging set to verbose.
   • The details of any ORA- error.

Example Issues 

ORA-01017: invalid username/password; logon denied
The message indicates that the username / password combination entered in the Oracle section of the snowagent.config file is not correct. Verify credentials with the Oracle dba and provide correct access. 

ORA-28000: The account is locked
The Oracle database account specified in the Oracle section of the snowagent.config is locked out. Verify credentials with the Oracle dba and provide correct access. 

ORA-28001: the password has expired
The password for the Oracle database account specified in the Oracle section of the snowagent.config has expired. Verify credentials with the Oracle dba and provide correct access. 

ORA-01033: ORACLE initialization or shutdown in progress
The message indicates the database is not fully started, or otherwise not ready for user logins. Provide the Oracle dba with the database name (SID)  for the database reporting the error.

SP2-0310: unable to open the file "run_TEST.sql"
After the SIOS scanner unpacks the scripts to run, it recursively changes the group ownership of those files to the operating system group “dba” or the group specified in the CommonOSGroup tag in the sios.config. If you see SP21-0310 in the sios log then one of the following may have occurred:

• The dba group doesn’t exist on this machine (the chown command will fail)

• The “chown” command failed due to a sudo failure

• The oracle owner (typically “oracle” but not always) is not a member of this group

See the Prerequisites / Permissions and Environment sections in the SIOS documentation for more details.


The list above is far from exhaustive but as you can see, they are often fairly clear. It is likely the issue can be solved by your Oracle dba.