Setting up Oracle Options for Discovery

s_sterner
Mega Guru

Hello,

Currently our organization is attempting to configure and setup the Oracle Options part of discovery based on the provided documentation found below. Looking to see if anyone has successfully set this up so far and what their hurdles were. The documentation lists ID #'s for documentation on oracles website but they seem to be missing. Documentation on SN's side seems to be missing details as well. Discovery on hosts with the correct permissions setup is not populating the samp_oracle_options table. Any help or guidance would be much appreciated.

Thank you!

Sean

https://docs.servicenow.com/bundle/paris-it-operations-management/page/product/discovery/concept/c_OracleDatabaseDiscovery.html#c_OracleDatabaseDiscovery__section_lvy_czw_xz

1 ACCEPTED SOLUTION

chuckm
Giga Guru

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:

  1. 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.
  2. 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:

  1. ServiceNow Discovery discovers a Windows Server.
  2. If an Oracle instance is detected running on the Windows Server, the Oracle DB On Windows Pattern is launched.
  3. 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.

find_real_file.png

View solution in original post

6 REPLIES 6

chuckm
Giga Guru

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:

  1. 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.
  2. 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:

  1. ServiceNow Discovery discovers a Windows Server.
  2. If an Oracle instance is detected running on the Windows Server, the Oracle DB On Windows Pattern is launched.
  3. 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.

find_real_file.png

Hi Chuck,

Very helpful post. Thank you. Would you happen to know why my Oracle DB on Unix/Windows patterns both are missing that "Oracle option extension for x" pattern step? Is there a plugin or something im missing?

Thank you!

Sean

Sean,

Yes, the Software Asset Management Professional for Oracle (com.snc.samp.oracle) plugin is required for the Oracle option extension for windows to be installed.

find_real_file.png
Additional details:

  • You can request the plugin be installed through the Now Support Service Portal.
  • When the plugin is installed, it won't be visible in the plugin list - even after activation. To validate if the plugin is installed, you can enter xmlstats.do at the end of the instance URL and com.snc.samp.oracle will show up as follows:

find_real_file.png

  • More details on the Software Asset Management plugins at:  Request Software Asset Management.
  • The plugin also adds additional attributes in the Oracle Options [samp_oracle_options] table that are populated by the extension section: Licensable, Currently used, First usage date, Last usage date, Last sample date, Detected usage, and Sample interval.

Hi,

 

Can you please elaborate what is mean by owner_role exactly here?

 

Thanks,

Ganesh