Snow Inventory Oracle Scanner

2021-09-09

Description

This document describes the latest version of Snow Inventory Oracle Scanner. Some functionality described in this document may work differently or not at all in previous versions.

Note

All inventory results provide a snapshot of the environment from the time when the inventory scan was performed.

Prerequisites

  • Dependency on other Snow products:

    The Snow Inventory Oracle Scanner is started from a Snow Inventory Agent. Running the scanner requires a Snow Inventory Server 5 or 6 environment.

  • Java Runtime Environment:

    To run the Snow Inventory Oracle Scanner, the target computer is required to have Java Runtime Environment 6 (1.6), 7 (1.7) or 8 (1.8) installed.

    Note

    Due to an internal defect in the Java Runtime Environment 1.7.0_7, this version must not be used. See Known issues for more information.

  • Permissions and environment variables:

    If the operating system user running the Inventory Agent is root, all users who run database instances must be members of the operating system DBA group. This is required to get folder permissions for the temp folder.

    If the operating system user running the Inventory Agent is not root, the user

    For Linux/Unix environments, the operating system user running the Snow Inventory Oracle Scanner must have write permissions on the following directories:

    • on Linux: /var/run/SnowSoftware/Inventory/Agent/script-output

    • on Unix: /var/tmp/SnowSoftware/Inventory/Agent/script-output

    For information on supported operating systems, see Snow System Requirements.

Privileges in a Windows environment

In a Windows environment, the Snow Inventory Oracle Scanner is run by the Snow inventory Agent for Windows, which by default uses the LocalSystem account.

If this default is changed, ensure that the account used has admin user rights, otherwise the scanner will not be able to execute successfully.

Privileges in a Linux or Unix environment

For Linux and Unix environments, the scanner can be run with two privilege options: full and according to the principle of least privileges.

  • Full privileges:

    The Snow Inventory Agent must be run as root.

  • Principle of least privileges:

    A user is required with sudo rights to the operating system commands outlined in the table below. The NOPASSWD option needs to be set on the sudoers file.

    An Oracle database user is required for each database to be inventoried, and needs to be defined in the configuration file. Either the user is the same for all databases and configured using the <DefaultInstanceCredentials> element, or the user can be unique and configured using the <InstancesWithConfiguration> element.

    To run Snow Inventory Oracle Scanner with operating-system authentication instead of authenticating by means of a dedicated Oracle-database user for each database instance, the local user that runs Snow Inventory Oracle Scanner must be member of the dba group.

    Example from sudoers file for Solaris:

    User snow has the rights to execute the commands with sudo and no password:

    ##
    ## User privilege specification
    ##
    root ALL=(ALL) ALL
    snow ALL=NOPASSWD: /usr/bin/pwdx
    

    Example from sudoers file for Linux:

    User snow has the rights to execute the commands with sudo and no password:

    ##
    ## User privilege specification
    ##
    root ALL=(ALL) ALL
    snow ALL=NOPASSWD: /usr/bin/ls
    snow ALL=NOPASSWD: /usr/bin/ls -l /proc/[0-9]*/cwd
    snow ALL=NOPASSWD: /usr/bin/ps ewww [0-9]*

    The following commands are used for determining OracleHome and the location of running processes.

    Operating system

    Command

    Solaris

    pwdx

    AIX and Linux

    ls

    ls -l /proc/[0-9]*/cwd

    ps ewww [0-9]*

    HP-UX

    pfiles

Files

Executable

Description

sios.jar

This is the only required file for the Snow Inventory Oracle Scanner. It is an executable Java archive that performs inventory of Oracle databases on the current server that it is executed on.

Sios.jar is started from a Snow Inventory Agent.

snowagent.config

Configuration file used for configuration of the Snow Inventory Oracle Scanner.

sios.rotation*.log

Log file

sios.properties

Properties file containing information about installation date, last run date, Java version, output filename, and version.

Oracle inventory

The Snow Inventory Oracle Scanner is designed to perform automatic Oracle inventory without the need to create a specific user account within the Oracle databases. The scanner automatically discovers all running Oracle instances on the current server, detects what user is running each database instance, and switches to that specific user when inventorying the databases. No specific permissions and no specific user is needed to inventory the databases.

The scanner is designed to be lightweight and scalable regarding size and number of objects in database. Resource consumption is mainly CPU bound as metadata is often available in memory.

Performing only read operations on databases, the scanner has been designed in a non-invasive manner. It performs SELECT queries based on PL/SQL blocks to extract the inventory data needed to determine license needs.

Only Oracle internal objects listed in Required Oracle permissions are accessed. To avoid concerns related to data security, the scanner never reads user or application data.

Snow Software recommends the use of automatic Oracle Inventory rather than setting up specific user accounts and permissions for each Oracle database.

Oracle inventory with specific user authentication – simplified config

If you do not wish to use automatic Oracle Inventory, it is possible to use the scanner with a specific user.

To avoid the time consuming process of creating this user with specific SELECT permissions, the user account can be created with SELECT permissions on ALL TABLES and DICTIONARY in all databases. The account also needs to be able to CREATE SESSION, by granting the user SELECT ANY privileges on TABLE and DICTIONARY, see the example below.

The user needs to be created and permissions need to be granted on each database that is to be inventoried.

Example 57.

Create the user <Oracle Scanner User> and grant SELECT ANY privileges in earlier versions than Oracle 12c:

SIOS_1.png


For Oracle version 12c or later, the user needs to be created as a common user, by typing “c##” before the username. Also, CONTAINER=ALL must be added to each line, see example below.

Example 58.

Create the user <Oracle Scanner User> and grant SELECT ANY privileges in Oracle 12c or later:

SIOS_2.png


Required Oracle permissions

The list below details the objects accessed during the Oracle inventory, and so the user needs to be able to run SELECT queries on these tables/views. If Oracle built-in roles and privileges cannot be used due to security reasons, grants need to be made to the objects listed here.

  • all_sdo_geom_metadata

  • all_views

  • cdb_pdb_history

  • dba_advisor_tasks

  • dba_aws

  • dba_cpu_usage_statistics

  • dba_cubes

  • dba_encrypted_columns

  • dba_feature_usage_statistics

  • dba_flashback_archive

  • dba_flashback_archive_tables

  • dba_flashback_archive_ts

  • dba_lob_partitions

  • dba_lobs

  • dba_lob_subpartitions

  • dba_objects

  • dba_object_tables

  • dba_recyclebin

  • dba_registry

  • dba_segments

  • dba_sql_profiles

  • dba_sqlset

  • dba_sqlset_references

  • dba_tables

  • dba_tablespaces

  • dba_tab_columns

  • dba_tab_partitions

  • dba_tab_subpartitions

  • dba_users

  • dba_workload_captures

  • dba_workload_filters

  • dba_workload_replays

  • dmsys.dm$model

  • dmsys.dm$object

  • dmsys.dm$p_model

  • dual

  • dvsys.dba_dv_realm

  • dvsys.dba_dv_realm_auth

  • global_name

  • gv$instance

  • gv$parameter

  • lbacsys.lbac$polt

  • lbacsys.ols$polt

  • mdsys.sdo_feature_usage

  • mdsys.sdo_geom_metadata_table

  • mgmt_targets

  • odm_document

  • odm.odm_mining_model

  • odm_record

  • olapsys.dba$olap_cubes

  • redaction_policies

  • sys.dba_mining_models

  • sys.dba_users

  • sysman.mgmt_fu_registrations

  • sysman.mgmt_license_definitions

  • sysman.mgmt_licenses

  • sysman.mgmt_targets

  • system.product_privs

  • sys.model$

  • timesten.tt_gridid

  • timesten.tt_gridinfo

  • user_role_privs

  • v$archive_dest_status

  • v$block_change_tracking

  • v$containers

  • v$database

  • v$instance

  • v$license

  • v$option

  • v$parameter

  • v$pdbs

  • v$session

  • v$session_connect_info

  • v$version

In this scenario, the Oracle built-in roles and privileges cannot be used due to security reasons.

The following example script creates the user OSCAN, and then adds the required Oracle permissions, which are used for non-container databases:

CREATE USER OSCAN IDENTIFIED BY <passwd>;
GRANT CREATE SESSION TO OSCAN;
GRANT EXECUTE ON SYS.DBMSOUTPUT_LINESARRAY TO OSCAN;
GRANT EXECUTE ON SYS.DBMS_APPLICATION_INFO TO OSCAN;
GRANT EXECUTE ON SYS.DBMS_OUTPUT TO OSCAN;
GRANT SELECT ON DMSYS.DM$MODEL TO OSCAN;
GRANT SELECT ON DMSYS.DM$OBJECT TO OSCAN;
GRANT SELECT ON DMSYS.DM$P_MODEL TO OSCAN;
GRANT SELECT ON LBACSYS.LBAC$POLT TO OSCAN;
GRANT SELECT ON LBACSYS.OLS$POLT TO OSCAN;
GRANT SELECT ON MDSYS.ALL_SDO_GEOM_METADATA TO OSCAN;
GRANT SELECT ON MDSYS.SDO_FEATURE_USAGE TO OSCAN;
GRANT SELECT ON MDSYS.SDO_GEOM_METADATA_TABLE TO OSCAN;
GRANT SELECT ON ODM.ODM_MINING_MODEL TO OSCAN;
GRANT SELECT ON ODM_DOCUMENT TO OSCAN;
GRANT SELECT ON ODM_RECORD TO OSCAN;
GRANT SELECT ON SYS.ALL_VIEWS TO OSCAN;
GRANT SELECT ON SYS.CDB_PDB_HISTORY TO OSCAN;
GRANT SELECT ON SYS.DBA_ADVISOR_TASKS TO OSCAN;
GRANT SELECT ON SYS.DBA_AWS TO OSCAN;
GRANT SELECT ON SYS.DBA_CPU_USAGE_STATISTICS TO OSCAN;
GRANT SELECT ON SYS.DBA_CUBES TO OSCAN;
GRANT SELECT ON SYS.DBA_ENCRYPTED_COLUMNS TO OSCAN;
GRANT SELECT ON SYS.DBA_FEATURE_USAGE_STATISTICS TO OSCAN;
GRANT SELECT ON SYS.DBA_FLASHBACK_ARCHIVE TO OSCAN;
GRANT SELECT ON SYS.DBA_FLASHBACK_ARCHIVE_TABLES TO OSCAN;
GRANT SELECT ON SYS.DBA_FLASHBACK_ARCHIVE_TS TO OSCAN;
GRANT SELECT ON SYS.DBA_LOBS TO OSCAN;
GRANT SELECT ON SYS.DBA_LOB_PARTITIONS TO OSCAN;
GRANT SELECT ON SYS.DBA_LOB_SUBPARTITIONS TO OSCAN;
GRANT SELECT ON SYS.DBA_MINING_MODELS TO OSCAN;
GRANT SELECT ON SYS.DBA_OBJECTS TO OSCAN;
GRANT SELECT ON SYS.DBA_OBJECT_TABLES TO OSCAN;
GRANT SELECT ON SYS.DBA_RECYCLEBIN TO OSCAN;
GRANT SELECT ON SYS.DBA_REGISTRY TO OSCAN;
GRANT SELECT ON SYS.DBA_SEGMENTS TO OSCAN;
GRANT SELECT ON SYS.DBA_SQLSET TO OSCAN;
GRANT SELECT ON SYS.DBA_SQLSET_REFERENCES TO OSCAN;
GRANT SELECT ON SYS.DBA_SQL_PROFILES TO OSCAN;
GRANT SELECT ON SYS.DBA_TABLES TO OSCAN;
GRANT SELECT ON SYS.DBA_TABLESPACES TO OSCAN;
GRANT SELECT ON SYS.DBA_TAB_COLUMNS TO OSCAN;
GRANT SELECT ON SYS.DBA_TAB_PARTITIONS TO OSCAN;
GRANT SELECT ON SYS.DBA_TAB_SUBPARTITIONS TO OSCAN;
GRANT SELECT ON SYS.DBA_USERS TO OSCAN;
GRANT SELECT ON SYS.DBA_WORKLOAD_CAPTURES TO OSCAN;
GRANT SELECT ON SYS.DBA_WORKLOAD_FILTERS TO OSCAN;
GRANT SELECT ON SYS.DBA_WORKLOAD_REPLAYS TO OSCAN;
GRANT SELECT ON SYS.DUAL TO OSCAN;
GRANT SELECT ON SYS.GLOBAL_NAME TO OSCAN;
GRANT SELECT ON SYS.GV_$INSTANCE TO OSCAN;
GRANT SELECT ON SYS.GV_$PARAMETER TO OSCAN;
GRANT SELECT ON SYS.MODEL$ TO OSCAN;
GRANT SELECT ON SYS.REDACTION_POLICIES TO OSCAN;
GRANT SELECT ON SYS.USER_ROLE_PRIVS TO OSCAN;
GRANT SELECT ON SYS.V_$ARCHIVE_DEST_STATUS TO OSCAN;
GRANT SELECT ON SYS.V_$BLOCK_CHANGE_TRACKING TO OSCAN;
GRANT SELECT ON SYS.V_$CONTAINERS TO OSCAN;
GRANT SELECT ON SYS.V_$DATABASE TO OSCAN;
GRANT SELECT ON SYS.V_$INSTANCE TO OSCAN;
GRANT SELECT ON SYS.V_$LICENSE TO OSCAN;
GRANT SELECT ON SYS.V_$OPTION TO OSCAN;
GRANT SELECT ON SYS.V_$PARAMETER TO OSCAN;
GRANT SELECT ON SYS.V_$PDBS TO OSCAN;
GRANT SELECT ON SYS.V_$SESSION TO OSCAN;
GRANT SELECT ON SYS.V_$SESSION_CONNECT_INFO TO OSCAN;
GRANT SELECT ON SYS.V_$VERSION TO OSCAN;
GRANT SELECT ON SYSMAN.MGMT_FU_REGISTRATIONS TO OSCAN;
GRANT SELECT ON SYSMAN.MGMT_LICENSE_DEFINITIONS TO OSCAN;
GRANT SELECT ON SYSMAN.MGMT_LICENSES TO OSCAN;
GRANT SELECT ON SYSMAN.MGMT_TARGETS TO OSCAN;
GRANT SELECT ON OLAPSYS.DBA$OLAP_CUBES TO OSCAN WITH GRANT OPTION;
GRANT SELECT ON SYSTEM.PRODUCT_PRIVS TO OSCAN WITH GRANT OPTION;
GRANT SELECT ON TIMESTEN.TT_GRIDID TO OSCAN;
GRANT SELECT ON TIMESTEN.TT_GRIDINFO TO OSCAN;

The following example script creates the user C##OSCAN that needs to be created as a common user, and then adds the required Oracle permissions, which is used for container databases:

CREATE USER C##OSCAN IDENTIFIED BY <passwd> CONTAINER=ALL;
ALTER USER C##OSCAN SET CONTAINER_DATA=ALL CONTAINER=CURRENT;
GRANT CONNECT TO C##OSCAN CONTAINER=ALL;
GRANT CREATE SESSION TO C##OSCAN CONTAINER=ALL;
GRANT EXECUTE ON SYS.DBMSOUTPUT_LINESARRAY TO C##OSCAN CONTAINER=ALL;
GRANT EXECUTE ON SYS.DBMS_APPLICATION_INFO TO C##OSCAN CONTAINER=ALL;
GRANT EXECUTE ON SYS.DBMS_OUTPUT TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON DMSYS.DM$MODEL TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON DMSYS.DM$OBJECT TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON DMSYS.DM$P_MODEL TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON LBACSYS.LBAC$POLT TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON LBACSYS.OLS$POLT TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON MDSYS.ALL_SDO_GEOM_METADATA TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON MDSYS.SDO_FEATURE_USAGE TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON MDSYS.SDO_GEOM_METADATA_TABLE TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON ODM.ODM_MINING_MODEL TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON ODM_DOCUMENT TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON ODM_RECORD TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.ALL_VIEWS TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.CDB_PDB_HISTORY TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.DBA_ADVISOR_TASKS TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.DBA_AWS TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.DBA_CPU_USAGE_STATISTICS TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.DBA_CUBES TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.DBA_ENCRYPTED_COLUMNS TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.DBA_FEATURE_USAGE_STATISTICS TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.DBA_FLASHBACK_ARCHIVE TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.DBA_FLASHBACK_ARCHIVE_TABLES TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.DBA_FLASHBACK_ARCHIVE_TS TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.DBA_LOBS TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.DBA_LOB_PARTITIONS TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.DBA_LOB_SUBPARTITIONS TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.DBA_MINING_MODELS TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.DBA_OBJECTS TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.DBA_OBJECT_TABLES TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.DBA_RECYCLEBIN TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.DBA_REGISTRY TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.DBA_SEGMENTS TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.DBA_SQLSET TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.DBA_SQLSET_REFERENCES TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.DBA_SQL_PROFILES TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.DBA_TABLES TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.DBA_TABLESPACES TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.DBA_TAB_COLUMNS TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.DBA_TAB_PARTITIONS TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.DBA_TAB_SUBPARTITIONS TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.DBA_USERS TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.DBA_WORKLOAD_CAPTURES TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.DBA_WORKLOAD_FILTERS TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.DBA_WORKLOAD_REPLAYS TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.DUAL TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.GLOBAL_NAME TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.GV_$INSTANCE TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.GV_$PARAMETER TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.MODEL$ TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.REDACTION_POLICIES TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.USER_ROLE_PRIVS TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.V_$ARCHIVE_DEST_STATUS TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.V_$BLOCK_CHANGE_TRACKING TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.V_$CONTAINERS TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.V_$DATABASE TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.V_$INSTANCE TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.V_$LICENSE TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.V_$OPTION TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.V_$PARAMETER TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.V_$PDBS TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.V_$SESSION TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.V_$SESSION_CONNECT_INFO TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYS.V_$VERSION TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYSMAN.MGMT_FU_REGISTRATIONS TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYSMAN.MGMT_LICENSE_DEFINITIONS TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYSMAN.MGMT_LICENSES TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON SYSMAN.MGMT_TARGETS TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON OLAPSYS.DBA$OLAP_CUBES TO C##OSCAN WITH GRANT OPTION
CONTAINER=ALL;
GRANT SELECT ON SYSTEM.PRODUCT_PRIVS TO C##OSCAN WITH GRANT OPTION CONTAINER=ALL;
GRANT SELECT ON TIMESTEN.TT_GRIDID TO C##OSCAN CONTAINER=ALL;
GRANT SELECT ON TIMESTEN.TT_GRIDINFO TO C##OSCAN CONTAINER=ALL; 

Note

These privileges allow the Snow Inventory Oracle Scanner to read metadata about database objects, but not the data inside them. They are needed in order to determine the license needs, if there for example exist partitioned or compressed tables.

Database vault

When Database Vault is enabled, then SYS or the specific Oracle user must:

  • have PARTICIPANT or OWNER authorization on 'Oracle Data Dictionary" realm

  • have PARTICIPANT or OWNER authorization on 'Oracle Database Vault' realm 

  • be granted the DV_SECANALYST role for querying Oracle Database Vault-supplied views

  • be granted SELECT on LBAC$POLT from LBACSYS

Example using OSCAN.

Log into the database instance as a user who has been granted the DV_OWNER or DV_ADMIN role.

sqlplus /nolog
conn DV_OWNER/<password>
grant DV_SECANALYST to OSCAN;
exec DVSYS.DBMS_MACADM.ADD_AUTH_TO_REALM('Oracle Data Dictionary','OSCAN');
exec DVSYS.DBMS_MACADM.ADD_AUTH_TO_REALM('Oracle Database Vault','OSCAN');
conn LBACSYS/<password>
grant select on LBACSYS.LBAC$POLT to OSCAN;

Output

The inventory result from the Snow Inventory Oracle Scanner will be integrated with the information collected by the Snow Inventory Agent.

Install and configure Snow Inventory Oracle Scanner

Installation

The Snow Inventory Oracle Scanner is integrated with Snow Inventory Agents for Linux, Unix, and Windows. When requesting Snow for a Snow Inventory Agent deployment package, specify that the Oracle Management Option needs to be included.

Configuration

Configuration of the Snow Inventory Oracle Scanner is performed in the Snow Inventory Admin Console in Snow Management and Configuration Center.

Scheduling

Scheduling is described in the document of the specific Snow Inventory Agent that is used.

Upgrading

Upgrade of the Snow Inventory Oracle Scanner is performed in the Snow Inventory Admin Console in Snow Management and Configuration Center. For detailed information on how to upgrade, see User guide, Snow Inventory Admin Console.

Known issues

The Java Runtime Environment (JRE) 1.7.0_07 contains a defect with the consequence that the Oracle inventory does not work. Any server running JRE 1.7.0_07 must upgrade to a later version for the Snow Inventory Oracle scanner to work properly.