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

• Message displayed in the log: “Missing SIJS raw data”

Explanation

The error message indicates that no data was received from the Snow Java scanner.

Troubleshooting

1. Confirm the Java Scanner has been deployed by checking for the jar file in these locations listed below. If not present, request a new agent from the support team.  
   • Windows - C:\Program Files\Snow Software\Inventory\Agent\snowjavascanner.jar
   • Linux / Unix - /opt/snow/snowjavascanner.jar 
2. Confirm that the agent is scheduled to scan the computer, by checking:
   • Windows - the snowagent launches the Java Scanner via the PowerShell script C:\Program Files\Snow Software\Inventory\Agent\scan-SIJSLauncher.snow-ps1
   • Linux / Unix - The scanner needs to be scheduled in such a way to leave enough time for the cron job to complete before the main snowagent scheduled job runs. Issue the command crontab -I and review the output. Use this example and its explanation below to interpret the results:

3. If there's no log file in the log location (see below) it means the scanner has not even started, which suggests Java cannot be found. Confirm an appropriate Java version is installed following the directions below for each OS. Supported versions of Java Runtime Environments are Oracle Java SE and Oracle OpenJDK (versions 8, 11 and 17).
   • Windows - The scan-SIJSLauncher.snow-ps1 script looks for java installations in the windows registry and also in the %PATH% environment variable. Add the Java executable to the System Path to correct. 
   • Linux / Unix - If the java you want to use is in the scanning user's $PATH, you can technically just enter the command line java -jar /opt/snow/sijs.jar in the crontab, but it's recommend that Java location be defined with the absolute path, for example:
     • ​​​​​​​/usr/bin/java -jar /opt/snow/sijs.jar
     • /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.352.b08-2.el8_7.x86_64/jre/bin/java -jar /opt/snow/sijs.jar
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 java scan log if it exists, see below for log locations.

Log Locations: