- 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
The message indicates that the OVS database was not received in the snowpack. This data is provided by the Snow Inventory Oracle Scanner (SIOS) and populates the files highlighted in this example snowpack:
SIOS Troubleshooting
- 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.
- 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.
- 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.
- 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:
- If SIOS appears to be running, but is not actually running successfully, proceed with the next step.
- 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).
- 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
- 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).
- 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 .
- Proceed with Oracle Management Option Service Troubleshooting.
ORA Errors 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 the credentials used with your DBA.
ORA-28000: The account is locked
The Oracle database account specified in the Oracle section of the snowagent.config is locked out. Provide your DBA with the credentials used and ask that the account be unlocked.
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 the credentials used with your DBA.
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 your DBA with the database name (SID) that’s reporting the error.
The message indicates that the username / password combination entered in the Oracle section of the snowagent.config file is not correct. Verify the credentials used with your DBA.
ORA-28000: The account is locked
The Oracle database account specified in the Oracle section of the snowagent.config is locked out. Provide your DBA with the credentials used and ask that the account be unlocked.
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 the credentials used with your DBA.
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 your DBA with the database name (SID) that’s reporting the error.
Oracle Management Option Service Troubleshooting
If you have already verified that the latest scanner is running successfully, and all the siosOVS files are being received in the snowpack as expected, the next possible cause to investigate is the status of the Oracle Management Option Services.- 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)
- 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
Snow License Manager Virtualization Service log- 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
Snow License Manager Oracle Management Option Service log & Snow License Manager Oracle Verified Solution Service log (9.26 onwards)
- 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
Was this helpful?
Related Articles
Oracle Verified - No data was processed by Snow Inventory Oracle Middleware Scanner 72Number of Views Oracle Verified - No data was processed by Snow Inventory Oracle Hardware Scanner 34Number of Views Oracle Verified - At least one java installation was not successfully inventoried 59Number of Views Oracle Verified - The processing of the inventoried data for java installations is not successfully executed according to … 21Number of Views Oracle Verified - The processing of the inventoried data (options file) is not successfully executed 18Number of Views
Revenera Assistant
Online
Hi, I am Reva - Ask me anything.
Updates
No new updates
Chat
Home
Updates
/**/
Thanks for the feedback!
Your feedback has been saved.Rate this response:
1
2
3
4
5
Add Additional feedback ( Optional )
0/240
English
English
Language changed successfully
Something went wrong
Email sent successfully
Something went wrong
Case create successfully
Are you sure you want to cancel
the case creation?
Please select a product to submit the case.
Please select a product version to submit the case.
0/255
Upload Attachment
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to cancel the case creation?
Case closed successfully
File Upload
Maximum file size allowed is 3 MB.
File type not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
© 2026 Flexera Software. All Rights Reserved.
Case id: 00001065
Activity: Status change: 2 hours ago