Sean,
We recently successfully implemented the Oracle Options. The Oracle Options requires additional configurations to implement that includes: 1) creating a new credential in the Oracle Database with correct roles and table access and 2) adding the new credential to the ServiceNow Discovery credential table. The Oracle Options runs the script options_packs_usage_statistics.sql which logs into the Oracle Database. The data returned is populated in the Oracle Options [samp_oracle_options] table. The data in the Oracle Options table is utilized by the ServiceNow Software Asset Management Application.
Required configurations:
- In the Oracle database application, create a credential that has connect and owner_role roles. Add the read permission to the following tables and views: V_$INSTANCE, V_$DATABASE, V_$VERSION, GV_$PARAMETER, V_$CONTAINERS, CDB_FEATURE_USAGE_STATISTICS, and DBA_FEATURE_USAGE_STATISTICS.
- In the ServiceNow Discovery credentials table, add the credential from step 1 as an Applicative Credential (CI type: Oracle Instance [cmdb_ci_db_ora_instance]).
The sequence of steps for Oracle Options:
- ServiceNow Discovery discovers a Windows Server.
- If an Oracle instance is detected running on the Windows Server, the Oracle DB On Windows Pattern is launched.
- If the Oracle credential is implemented per the required configuration section above, the Oracle option extension for windows section will execute successfully. The data returned will be populated in the Oracle Options [samp_oracle_options] table.
Note: In the Oracle DB On Windows pattern log, the Oracle option extension for windows will show green for a successful execution. If the credential is not present in the credential table, the following error will show up in this section: Applicative credentials for CI type cmdb_ci_db_ora_instance are not defined. Please go to the Credentials page to add the appropriate Applicative Credentials.
