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

• The Snow Inventory Oracle Scanner was not successfully executed on this computer/environment.

Explanation

In OracleOvsService method ProcessSiosOvsDataAsync ovs_status.json file has status different than OK and all databases are OK. As we can see in the following example, the SIOS scanner has detected a total of seven oracle database instances running on this server, of which only four have been successfully inventoried:

We get the error because, although we have some databases successfully scanned (OK), the overall status was Not OK (NOK). All present databases must be inventoried for 100% success (OK).
 

Troubleshooting

As at least some databases have been successfully scanned (OK), you can be fairly confident the issue is not with the SIOS scanner or its config (or inventory or SLM for that matter.)

To troubleshoot this issue perform the following:

1. First verify that the latest version of the Snow Agent and scanner have been deployed on this computer. If not, run the upgrades and if the issue persists, continue troubleshooting. 
2. Next, ensure logging is set to verbose in snowagent.config and run a manual agent scan.
3. Search the data\sios.rototaion.n.log(s) for the string ORA- which prepends errors for identified issues with databases. Refer the Error Reference below. Provide the information to the Oracle DBA to resolve most issues. 
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
   • A snowpack that also includes the data from SIOMS, SIJS, and SIOHWS scanners .

Error Reference

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 with the customer’s Oracle dba, let them know the account name.

ORA-28000: The account is locked
The oracle database account specified in the Oracle section of the snowagent.config is locked out.
Raise this with the customer’s Oracle dba, let them know the account name.

ORA-28001: the password has expired
The password for the oracle database account specified in the Oracle section of the snowagent.config has expired.
Raise this with the customer’s Oracle dba, let them know the account name.

ORA-01033: ORACLE initialization or shutdown in progress
The message indicates the database is not fully started, or otherwise not ready for user logins.
Raise this with the customer’s Oracle dba, let them know the database name (SID) that’s 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