• Computer that has detection for Oracle DB product installations, but missing Oracle Verified Solution data.
• SIOS not marked as OK when processing completeness status for Database

Explanation

SIOS Troubleshooting

1. First, confirm whether or not any data is being collected by SIOS. If you look at the Oracle tab for the computer under scrutiny, are any databases listed?
   • If no databases are listed or if some data is present but the error persists on the OVS screen, you should confirm that the latest version of the scanner is deployed and running correctly. 
   • If the latest version of the scanner has been deployed, but there is no data in Snow License Manager for any database, continue troubleshooting. 
2. Confirm that SIOS is configured to run. The SIOS is Snow's only scanner developed in Java that doesn't require a separate launcher on Windows, or a cron job for Unix/Linux. To confirm:
   • Open snowagent.config and confirm that the key <Oracle enabled="true"> is configured as true. 
   • If the key is configured correctly, proceed with the next step.
3. Is SIOS actually running as expected?
   • When SIOS runs, it creates the log file C:\Program Files\Snow Software\Inventory\Agent\data\sios.rotationn.log in Windows and /opt/snow/data/sios.rotationn.log in Unix/Linux. If no log has been created, SIOS is failing to start, likely because a compatible version of Java was not found. Confirm that a supported version has been installed, and if not, perform the installation and try again.  Supported versions of Java Runtime Environments are Oracle Java SE and Oracle OpenJDK (versions 8, 11 and 17).
     • SIOS reads the setting env.java_home in the snow agent config file to determine which Java instanced to use. The information in the key is handled on a per-OS basis:
       • For Windows, the configuration points to the Java Home, for example: <Setting key="env.java_home" value="C:\Program Files\sqldeveloper\jdk\jre" /> or <Setting key="env.java_home" value=" C:\Program Files (x86)\Java\jdk1.8.0_202" />.
       • For Unix/Linux, the configuration requires the absolute path to the Java executable, for example: <Setting key="env.java_home" value="/usr/bin/java"/> or <Setting key="env.java_home" value=" /opt/oracle/product/19c/dbhome_1/OPatch/jre/bin/java"/>
       • Using Java from another installed application is acceptable, providing it is a supported version as listed above. 
   • If SIOS appears to be running, but is not actually running successfully, proceed with the next step.
4. Analyze the SIOS log for the following conditions:
   • Confirm a running database was located by searching for the string No instances to get data from. Errors located with this string indicate that no database was found. This information may need to be gathered from your database administrator (DBA).
     • Was the database present and running properly at the time of the scan?
     • Is the datbase currently running and accepting logins?
   • Confirm that the logs indicate no issues with the target database by searching for the string ORA-. If any such errors are present, there is likely an operational issue with the database itself that should be reviewed with your DBA. See the section below for specific guidance around these errors. 
   • For Unix/Linux system running as non-root users, check the logs for any issues relating to the strings sudo or chown which may indicate problems executing commands due to permissions misconfiguration.
   • Confirm there are no group ownership issues by searching for the string SP21-0310. After the SIOS scanner unpacks the scripts, it recursively changes the group ownership of those files to the OS group dba or the group specified in the CommonOSGroup tag in the sios.config. These errors may indicate:
     • The chown command was not successful due to a sudo failure.
     • The dba group doesn’t exist on this machine (chown command fails.)
     • 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.1
5. If you have not remedied the issue, please open a new case with Snow Support, providing the information and observations you've collected during this troubleshooting:
   • All relevant software versions (snowagent, sios, java, oracle db version and edition if known)
   • A snowpack with agent logging level set to verbose .
6. Proceed with Oracle Management Option Service Troubleshooting.

ORA Errors Reference

Oracle Management Option Service Troubleshooting

1. Confirm that the following services are running, without error, in this order (default runtimes provided in the brackets): 
   • Snow License Manager Virtualization Service (06:00)
   • Snow License Manager Oracle Management Option Service (07:00)
   • Snow License Manager Oracle Verified Solution Service (available as of SLM 9.26) (08:00)
2. Confirm there are no errors in the respective logs for these services. Search for the strings ERR and FTL and compare to the list of known issues below . 
   • %:\Program Files\Snow Software\Logs\VirtualizationService
   • %:\Program Files\Snow Software\Logs\OracleManagementOption
   • %:\Program Files\Snow Software\Logs\OracleVerifiedSolution

Known Issues

• Violation of PRIMARY KEY constraint 'PK_ManagementServer'. Cannot insert duplicate key in object 'vir.ManagementServer'
• Violation of PRIMARY KEY constraint 'PK_Datacenter'. Cannot insert duplicate key in object 'vir.Datacenter'
• Violation of PRIMARY KEY constraint 'PK_ComputerCluster'. Cannot insert duplicate key in object 'vir.ComputerCluster'
• Sequence contains no elements
• Sequence contains more than one element

• Response status code does not indicate success: 400 (Bad Request)
• Violation of PRIMARY KEY constraint 'PK_Database'. Cannot insert duplicate key in object 'omo.Database'
• [FTL] () Unhandled exception - System.ArgumentException: An item with the same key has already been added. Key: 1
• …was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction