HP Man UniversalDiscovery OracleLMS 1.30 User Guide 2nded PDF
HP Man UniversalDiscovery OracleLMS 1.30 User Guide 2nded PDF
User Guide
Copyright Notice
© 2002 - 2016 Hewlett Packard Enterprise Development LP
Trademark Notices
Adobe™ is a trademark of Adobe Systems Incorporated.
Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
UNIX® is a registered trademark of The Open Group.
Documentation Updates
To check for recent updates or to verify that you are using the most recent edition of a document, go to: https://softwaresupport.hpe.com/.
This site requires that you register for an HPE Passport and to sign in. To register for an HPE Passport ID, click Register on the HPE Software Support site or click Create an
Account on the HPE Passport login page.
You will also receive updated or new editions if you subscribe to the appropriate product support service. Contact your HPE sales representative for details.
Document Changes
Version Changes
1.30 (2nd Edition, September 2017) l Added a known issue about Oracle STANDBY instance discovery and the solution in "Troubleshooting and Limitations"
on page 41.
Support
Visit the HPE Software Support site at: https://softwaresupport.hpe.com/.
This website provides contact information and details about the products, services, and support that HPE Software offers.
HPE Software online support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your
business. As a valued support customer, you can benefit by using the support website to:
l Search for knowledge documents of interest
l Submit and track support cases and enhancement requests
l Download software patches
l Manage support contracts
l Look up HPE support contacts
l Review information about available services
l Enter into discussions with other software customers
l Research and register for software training
Most of the support areas require that you register as an HPE Passport user and to sign in. Many also require a support contract. To register for an HPE Passport ID, click
Register on the HPE Support site or click Create an Account on the HPE Passport login page.
To find more information about access levels, go to: https://softwaresupport.hpe.com/web/softwaresupport/access-levels.
HPE Software Integration Catalog accesses the new HPE Software Integrations and Solutions Catalog website. This site enables you to explore HPE Product Solutions to
meet your business needs, includes a full list of Integrations between HPE Products, as well as a listing of ITIL Processes. The URL for this website is
https://softwaresupport.hpe.com/km/KM01702731.
o Universal Discovery (UD) for Oracle LMS is shipped with the latest scripts required for an
Oracle audit.
o HPE Software will work with Oracle to ensure the UD for Oracle LMS product is kept current
with the inclusion of the latest Oracle audit scripts and as such aligns with the release
schedule and support driven by Oracle.
o The licensing model for Oracle LMS from HPE Software does not restrict its usage to any
particular version, so upgrades for licensed installations are available at no additional cost.
HPE strongly recommends that you remain current and up to date with the UD for Oracle LMS
release versions to get the best outcome and ensure compliance during the Oracle audit.
The standard support cycle provided for software creating by HPE Software does not apply to
the UD for Oracle LMS package.
This is due to an Oracle requirement that the latest scripts be used for any audit of Oracle
software, which will be available in the latest released version of the Oracle LMS package.
Oracle reserves the right to require that you run the latest scripts during the Oracle audit.
Overview
Universal Discovery for Oracle License Management Implementation Software enables you to collect
the required data for review, analysis and checking, and to send it to Oracle for use by their License
Management Services division.
Universal Discovery for Oracle License Management Implementation Software uses SQL queries to
the underlying Oracle databases, and enriches that data with data discovered by Universal Discovery's
host discoveries.
Universal Discovery for Oracle License Management Implementation Software can report the hardware
data, including the CPU data on different platforms and VMware inventory data.
Supported Versions
UCMDB version Content Pack version Oracle version
UCMDB 10.22 CUP4 or a later Content Pack 20 or later, with or Oracle version 8
CUP without updates and later
UCMDB 10.30 or later, with or Content Pack 20 or later, with or Oracle version 8
without CUPs without updates and later
o CREATE SESSION
o SELECT ANY TABLE
o SELECT ANY DICTIONARY (for Oracle 9i or higher)
o When DATABASE VAULT is in use, PARTICIPANT or OWNER authorization on "Oracle
Database Vault Realm" is needed
l Shell access to the operating system command line (UNIX Shell or Windows Command Prompt)
through the corresponding Shell protocol of Universal Discovery (SSH, NTCMD, PowerCmd, or
Upgrade Path
You can upgrade from Oracle LMS 1.0, 1.10, or 1.20. If you are running Oracle LMS 1.0, 1.10, or 1.20,
simply install Oracle LMS 1.30.
This software requires the UCMDB version to be 10.30 or later. If UCMDB 10.30 or later is already
installed, ignore this step and move to step 2. Otherwise, perform the following:
To install UCMDB 10.30, follow the instructions in the interactive HPE Universal CMDB
Deployment Guide.
This software requires Universal Discovery Content Pack (CP) 20 or later. If CP20 or later is
already installed, ignore this step and move to step 3. Otherwise, follow the instructions for
installing CP20 or later in the Release Notes for Universal CMDB/Universal Discovery Content
Pack for the Content Pack that you are installing.
a. Locate the file OracleLMS.zip on the HPE Live Network website (https://hpln.hpe.com/), and
save it to a directory on the local hard drive.
b. Deploy the OracleLMS.zip package from the local hard drive, following the instructions in the
section describing how to deploy a package in the HPE Universal CMDB Administration
Guide.
What's New
l The existing Oracle LMS Report button Export LMS Data is renamed to Export LMS DB Options
Data.
l Added two new buttons in the Oracle LMS Report, allowing you to export more specific Oracle LMS
data:
l Added a new job Oracle LMS CPU Data Collection by Shell to run CPU query scripts (provided
by Oracle) to collect the CPU data on different platforms.
Windows lms_cpuq.cmd
Linux/UNIX lms_cpuq.sh
Platform Description
IBM LPARs Log in to each LPAR running Oracle Software and run the lms_
cpuq.sh script.
Solaris Containers Log in and run the lms_cpuq.sh script in the Global Zone.
Oracle VM Server for Log in and run the lms_cpuq.sh script in the Control Domain.
SPARC
Oracel VM Server for x86 Log in and run the lms_cpuq.sh script in dom0.
HP nPar Log in and run the lms_cpuq.sh script in each nPar running Oracle
Platform Description
Software.
Microsoft Hyper-V Log in and run the lms_cpuq.cmd script in the Root Partition.
Fixed Defects
The following table lists the defects that were fixed in Oracle LMS 1.30.
QCCR1H104072 The default size of the column Fixed the issue by changing the size
PROCESS_IDENTIFIER in the Data of the column PROCESS_
Flow Probe DB Table LMS_ IDENTIFIER to 255.
OVERVIEW is 40, causing Oracle LMS
data collection to fail when the insertion
of longer strings is attempted.
QCCR1H104190 Oracle LMS discovery fails with the Fixed the issue by increasing the
following error message: "Failed save size of the affected column col030 in
to LMS_OPTIONS.java.sql. the table lms_options to 1000.
BatchUpdateException: Batch
entry 80 INSERT INTO LMS_
OPTIONS".
QCCR1H104760 The Oracle LMS Data Collection by Fixed the issue by changing the
SQL job uses the wrong table name and Oracle LMS related table name from
should not use SYS.MODEL. SYS.MODEL to SYS.MODEL$.
QCCR1H104940 Oracle LMS discovery does not show Fixed the issue by specifying the
specific table names that are used in the required database privileged in the
QCCR1H105118
SQL query. details of adapter definition for Oracle
LMS discovery.
QCCR1H106211 When running Oracle LMS Audit, the Oracle 8 has no DATABASE_ROLE
following error message occurs: "ORA- column in the table V$DATABASE.
00904: invalid column name". Just query the column CREATED if
there is no DATABASE_ROLE.
QCCR1H109573 The OutOfMemory error occurs when If the OutOfMemory error occurs
exporting the Oracle LMS report. when exporting the Oracle LMS
report through UCMDB UI, run the
JMX method
exportOracleLMSDataWithChunks
to export the Oracle LMS report.
Fixed Defects
The following table lists the defects that were fixed in Oracle LMS 1.20.
QCCR1H99330 The errors messages returned on the Oracle Fixed the issue by adding
Database by SQL Job do not contain the none check for SID and return
Oracle error code anymore. the Oracle error messages.
QCCR1H97800 Oracle displays a warning message that the Fixed the issue by using
CPU format built into the report is not CPU.name instead of
matching what is expected. For example, CPU.cpu_pecifier as
currently "XEON" is returned instead of processor identifier in LMS_
something like "Intel Xeon CPU X5675 DETAIL.csv and LMS_
@3.07Ghz". The information needed already OVERVIEW.csv.
exists on the CI level under the name attribute
of the CPU CI type.
QCCR1H99367 When checking the option name / pack name Fixed the issue by applying
in the shortcuts mapping table, it is a case- case sensitive mode.
sensitive search. For example, there is an
option Partitioning (user) in users' Oracle
database, but the option in the mapping table
is Partitioning (User). So this option will not
show up in the LMSOverview.csv report.
QCCR1H96425 After upgrading Oracle LMS 1.0 to version 1.1 Fixed the issue by using the
using management zone, "Can not create alter table instead of the drop
Oracle LMS tables" error occurs after a rerun table to upgrade the database.
of the Oracle LMS job.
QCCR1H92683 When performing LMS Oracle discovery to Fixed the issue by applying a
prepare for an audit, it is successful in code change.
discovering a majority of Oracle DB with their
LMS files being created, but unable to
discover others.
QCCR1H100462 The Oracle LMS job failed on some host, Fixed the issue by adding
because none check failed for pdb_ none check for pdb_
credential when there is no Oracle Service credentials.
Name CI linked to Oracle.
The discovery logic has been enhanced to use Oracle LMS scripts version 14.1. These scripts include
the following new functionality:
l Enhanced usage detection for OEM Packs. Most notably, the process has been enhanced to
collect and reveal real usage of OEM Packs in OEM 12c Cloud Control. This OEM version records
weekly statistics about the usage of Licensed Links available in OEM pages (GUI), through a
mechanism that is similar to Database feature usage statistics collection.
Note: Oracle 12c is supported when used with UCMDB 10.10 or later.
l Tuning Pack real usage measurement is also enhanced through the detection of SQL Tuning
Advisor, SQL Access Advisor and SQL Tuning Sets features.
l More features of the Advanced Compression, Advanced Security, and Active Data Guard Options
are now detected, including Flashback Data Archive (Total Recall), now an Advanced Compression
feature.
Topology
This section includes:
l "Topology for the Oracle LMS Data Collection by SQL job" below
l "Topology for the Oracle LMS CPU Data Collection by Shell job" on page 13
Note: For a list of discovered CITs, see "Discovered CITs" on page 37.
This CI is used to store the data provided by users and has the following parameters:
o Aggregation Level
o Application Name
o Application Status
o Group
o Measurement Comments
o Oracle CSI
o User Count
This CI is used to store the data captured by the discovery jobs. The CSV files are generated
according to that data.
Topology for the Oracle LMS CPU Data Collection by Shell job
The following image shows the topology for the Oracle LMS CPU Data Collection by Shell job.
Note: For a list of discovered CITs, see "Discovered CITs" on page 40.
The following image shows the topology on Oracle VM Server for SPARC.
The following image shows the topology on Oracle VM Server for x86.
l An activity in Data Flow Management > Universal Discovery > Zone Based Discovery >
New Discovery Activity > Auditing. For more information see the section describing how to
run a zone-based discovery in the HPE Universal CMDB Data Flow Management Guide.
l The Oracle LMS Data Collection by SQL and Oracle LMS CPU Data Collection by Shell
jobs in Data Flow Management > Universal Discovery > Discovery Modules/Jobs >
Discovery Modules > Auditing.
l The Oracle LMS Report in Modeling > Reports > Custom Reports > Custom > Auditing.
Outline
Following is the discovery process for collecting Oracle LMS data:
l Configuring and activating discovery, to discover (a) the servers hosting Oracle databases, and (b)
virtualization information
l Running the Oracle LMS Data Collection by SQL job on the discovered Oracle database servers
to collect the LMS DB Options data
l Running the Oracle LMS CPU Data Collection by Shell job on the discovered Oracle database
servers to collect the LMS CPU data
Note: The Oracle LMS CPU data report requires UCMDB 10.30 or later.
Task
Note: This part of the document describes all the task steps. You may already have completed
some of these steps. If so, you do not have to repeat such steps, though you should ensure the
configurations are accurate. For example, you do not need to create a new Management Zone if
You must have full read access rights to the target Oracle database server.
o NTCMD, SSH, PowerCmd, or Universal Discovery; to discover the hosts where Oracle is
installed.
o Generic DB Protocol (SQL); to discover Oracle instances.
o VMware VIM; to discover virtualization topology.
For details, see the section describing Data Flow Probe Setup in the HPE Universal CMDB Data
Flow Management Guide.
Note:
o On Linux, root access is verified at the beginning of the Oracle's CPU script; if the root
access is missing, a warning message is returned by the Oracle LMS CPU Data
Collection by Shell job.
o Query scripts must be run from a temp folder with write permissions for the current user.
o If you prefer not to configure SID in the Oracle credential, you can discover the Oracle SID
in either of the following ways:
l Run the Basic Software Configuration Discovery Activity to collect the SID
information.
Discovery > Management Zones > select a Management Zone > click >
select New Discovery Activity > Software Configuration > Basic.
Make sure you select the Run Oracle Discovery check box on the Discovery
Preferences page.
C. Right-click the new activity you just configured and select Activate to discover
the Oracle CI with SID information.
l Run the Data Flow Management > Universal Discovery > Discovery
Modules/Jobs > Discovery Modules > Hosts and Resources > Basic
Applications > Host Applications by Shell job to discover the Oracle SID.
For details, see the section describing how to run a zone-based discovery in the HPE Universal
CMDB Data Flow Management Guide.
For details, see "Infrastructure Discovery Activity" in the HPE UCMDB Discovery and
Integrations Content Guide - Discovery Activities document.
For details, see "Inventory Discovery Activity" in the HPE UCMDB Discovery and
Integrations Content Guide - Discovery Activities document.
Important:
o If Oracle is also hosted on Microsoft Hyper-V, Solaris Zones, or VMware ESX, you have
the following options:
i. Go to Data Flow Management > Universal Discovery > Zone Based Discovery
> Management Zones.
iv. Select New Discovery Activity > Software Configuration > Virtualization.
v. Create the activity and activate it by following the online prompts through the activity
wizard. You must enable discovery of the virtualization technologies that are in your
environment.
The New Database Software Configuration Discovery Activity dialog box appears.
e. Create the activity and activate it by following the online prompts through the activity wizard.
You must enable Run Oracle Discovery on the Discovery Preferences page of the activity
wizard.
Management Zones.
e. Create the activity and activate it by following the online prompts through the activity wizard.
You must enable Run Oracle LMS CPU Discovery on the Preferences page of the activity
wizard.
For details, see "Oracle LMS Audit Activity User Interface" on page 27.
Note: You may also double-click the report to make it display in the pane.
A Save dialog box is displayed. The data is saved to a ZIP file named, by default, OracleLMS_
<timestamp>.zip, containing the following CSV files:
l LMS_DBA_USERS.csv
l LMS_DETAIL.csv
l LMS_OPTIONS.csv
l LMS_OVERVIEW.csv
l LMS_V$LICENSE.csv
l LMS_V$SESSION.csv
o Click Export LMS VMware Data.
A Save dialog box is displayed. The data is saved to a ZIP file named, by default, OracleLMS_
VMwareInv_Data_<timestamp>.zip, containing the following two CSV files:
A Save dialog box is displayed. The data is saved to a ZIP file named, by default, OracleLMS_
CPU_Data_<timestamp>.zip, containing several TXT files. The TXT files are named as
follows:
If different hosts have the same host name, the count number is added to the TXT file names.
For example,
l cmswin12-1-lms_cpuq.txt
l cmswin12-2-lms_cpuq.txt
l cmswin12-3-lms_cpuq.txt
See also "How to Edit the LMS Data Customer Fields" below.
Note: In the file name of the exported ZIP packages, <timestamp> follows this format:
YYYY-MM-DD_HH_MM_SS, where 24 hour system is used.
Tip: You may also access the Oracle LMS Data by exporting it using the JMX Console.
1. Log in to the UCMDB JMX console on the machine where UCMDB is installed. (Launch the
Web browser and enter the following address: https://localhost:8443/jmx-console. You
may have to log in with a user name and password.)
4. Click Invoke.
Note: The LMS data from UCMDB is created in a format required by Oracle. Besides the ZIP files,
Oracle may require other information as part of the LMS data collection. If required, you will have to
work on that with Oracle.
2. In the Search CIs mode, search for the CI Type AuditDocument in the topology map or the
CI Selector, and select it.
3. In the Advanced Pane, select the Properties tab and click Edit.
A file containing the customer fields is displayed. You may edit and save the file as required.
To access Go to Data Flow Management > Universal Discovery > Zone-Based Discovery
> Management Zones > select a Management Zone > click > select New
Discovery Activity > Auditing > Oracle LMS
Important For more information, hold the pointer over a question mark icon.
Information
Important General information about the activity is available in "Oracle LMS Audit Activity
Information User Interface" on the previous page.
Note: This screen is not displayed when editing an Oracle LMS Audit
activity.
Wizard Map The "Oracle LMS Audit Activity User Interface" contains:
Activity Name Page > "Preferences Page" > "Schedule Discovery Page" >
"Summary Page"
UI
Element
(A–Z) Description
Activity Enter a unique name for the Oracle LMS Audit activity.
Name
Note: Names should consist only of alphanumeric characters (a-z, A-Z, 0-9),
hyphens (-), and periods (.). Names appear in some reports. Additionally, names may
also appear in the Updated by attribute in the CI Properties page if a CI was
updated by a job. Names can be changed at any time, however, the Job ID attribute
that is associated with the job name does not change.
Preferences Page
Enables you to select preferences for the Oracle LMS Audit activity.
Preferences Page
Important General information about the activity is available in "Oracle LMS Audit Activity
Information User Interface" on page 27.
Wizard Map The "Oracle LMS Audit Activity User Interface" contains:
"Activity Name Page" > Preferences Page > "Schedule Discovery Page" >
"Summary Page"
UI Element (A–
Z) Description
Fill Customer Customer Fields are user definable fields in the Oracle LMS data.
Fields
You may select this option and complete these fields here, if you want them to
apply to all databases queried by this activity.
Otherwise, you may set unique values for these fields in the DocumentContent
UI Element (A–
Z) Description
Compressed A limit on the size of the collected LMS data per database CI, in bytes.
Size
Default: 2 MB (2,097,152 bytes).
Run Oracle LMS Select this option to run the Oracle LMS CPU Data discovery via Shell-based
CPU Discovery protocols.
Important General information about the activity is available in "Oracle LMS Audit Activity
Information User Interface" on page 27.
Wizard Map The "Oracle LMS Audit Activity User Interface" contains:
"Activity Name Page" > "Preferences Page" > Schedule Discovery Page >
"Summary Page"
User interface elements are described below (unlabeled elements are shown in angle brackets):
UI Element
(A–Z) Description
(Appears when you select Cron.) Click to validate the Cron expression you
entered.
Click the Time Templates icon to open the Time Templates dialog box. Enables
you to define a custom schedule to run the discovery activity. For more
information, see "Time Templates Dialog Box" in the HPE Universal CMDB Data
Flow Management Guide.
Allow Select the time template that you want to use to schedule the discovery activity.
Discovery to
run at
<Days of (Appears when you select Monthly.) Click the button to choose the days of the
month> month on which the discovery activity must run. The Select Days dialog box
opens. Choose the required days by selecting the check boxes. You can select
multiple days.
<Days of the (Appears when you select Weekly.) Select the day or days on which the discovery
week> activity should run.
(Sunday -
Saturday)
Cron (Appears when you select Cron.) Enter a Cron expression in the proper format.
Expression For descriptions and examples of Cron expressions, see "Cron Expressions" in
the HPE Universal CMDB Modeling Guide
<Months of (Appears when you select Monthly.) Select the month or months in which the
the year> discovery activity must run.
(January -
UI Element
(A–Z) Description
December)
End by (Does not appear when you select Once). Select the date and time when the
discovery activity must finish running by selecting the End by check box, opening
the calendar, selecting the date and time, and clicking OK.
Note: This step is optional. If you do not need to specify an ending date,
leave the End by check box cleared.
Invocation (Appears when you select Daily, Weekly, or Monthly.) Select the time to activate
hour the discovery activity. Click the button to open the Select Hours dialog box.
Choose the required time by selecting the check boxes. You can select multiple
times.
Note: You can also enter the time manually in the Invocation hour box.
Separate times by a comma and enter AM or PM after the hour. The manually
entered action times are not restricted to the hour and half hour only: you can
assign any hour and minute combination. Use the following format: HH:MM
AM, for example, 8:15 AM, 11:59 PM.
Invocation (Displayed when you select Once.) Choose the date and time the action should
Time begin running by opening the calendar and choosing a date and time, or accept the
default.
Repeat every (Displayed when you select Interval.) Select how often the discovery activity
runs.
Type a value for the interval between successive runs and choose the required
unit of time (minutes, hours, or days).
Note: After each change, the next time that the discovery activity runs is the
current time plus the interval, that is, the discovery activity does not start
immediately.
Start at (Does not appear when you select Once). Choose the date and time when the
discovery activity must begin running by selecting the Start at check box, opening
the calendar, selecting the date and time, and clicking OK.
Note:
l When selecting the start time, the time zone in the start time is set
UI Element
(A–Z) Description
according to the client machine’s location, although it may not match the
value selected in Time Zone.
l This step is optional. If you do not want to specify a beginning time, leave
the Start at check box unselected.
Time zone Select the time zone according to which the Probe must schedule jobs.
The default is <<Data Flow Probe Time Zone>>: the Probe uses its own
system-defined time zone. This enables scheduling to take place at different times
in different geographical locations.
For all Probes to start working at the same time, select a specific time zone. (This
assumes that the Probes' system date/time and time zone are correctly
configured.)
Summary Page
Enables you to review all configurations and parameter values before running the Oracle LMS Audit
activity.
Summary Page
Important Review configurations and decide whether to run the activity or go back and
Information make changes.
General information about the activity is available in "Oracle LMS Audit Activity
User Interface" on page 27.
Wizard Map The "Oracle LMS Audit Activity User Interface" contains:
"Activity Name Page" > "Preferences Page" > "Schedule Discovery Page" >
Summary Page
UI Element
(A–Z) Description
Finish l Creation mode: Closes the wizard and adds the activity to the Management Zone
tree.
Note: You cannot activate the activity from the wizard in Edit mode.
Adapter
This job uses the Oracle LMS data collection by SQL adapter.
Discovery Flow
1. Connect to the target Oracle database with Oracle SID or session ID using the Generic DB
protocol (SQL).
2. Run the SQL query in the target Oracle database and save the result to the probe database.
3. Send the collected data from the probe database to the UCMDB server.
Input CIT
Oracle
Triggered CI Data
Name Value
core_number ${Cpu.core_number:NA}
cpu_clock_speed ${Cpu.cpu_clock_speed:NA}
cpu_name ${Cpu.name:}
cpu_specifier ${Cpu.cpu_specifier:NA}
credentialsId ${SOURCE.credentials_id}
discovered_host_name ${HOST.name:NA}
discovered_model ${HOST.discovered_model:NA}
discovered_os_name ${HOST.discovered_os_name:NA}
discovered_vendor ${HOST.discovered_vendor:NA}
document_content ${AuditDocument.document_content:NA}
host_isvirtual ${HOST.host_isvirtual:NA}
ip_address ${SOURCE.application_ip}
logical_cpu_count ${Cpu.logical_cpu_count:NA}
port ${SOURCE.application_port:NA}
sid ${SOURCE.name:NA}
Used Scripts
l Oracle_LMS.py
l OracleLMSDbaUsers.py
l OracleLMSDetail.py
l OracleLMSOptions.py
l OracleLMSOverview.py
l OracleLMSUtils.py
l OracleLMSVLicense.py
l OracleLMSVSession.py
Discovered CITs
l AuditDocument
l Composition
l Oracle
Parameters
Name Description
group The relevant grouping as you define it. For example: region, or
department.
Name Description
oracleCSI The Oracle Customer Support Identifier that you use when
dealing with Oracle Support Services.
serverNameInTheCluster If the servers are clustered, the names of the servers in the
cluster.
Adapter
This job uses the Oracle LMS CPU Data Collection by Shell adapter.
Discovery Flow
1. Connect to the target server using the Shell Protocol.
Input CIT
Shell
Triggered CI Data
Name Value
Protocol ${SOURCE.root_class}
codepage ${SOURCE.codepage:NA}
credentialsId ${SOURCE.credentials_id:NA}
host_id ${NODE.root_id:}
host_server_audit_document ${AuditDocument.root_id:}
host_server_id ${NODE_HOST.root_id:}
ip_address ${SOURCE.application_ip}
language ${SOURCE.language:NA}
Used Scripts
l OracleLMSCPUDiscoverer.py
l OracleLMSCPU.py
Discovered CITs
l AuditDocument
l Composition
l Node
Solution: Increase the size parameter in the Oracle LMS Data Collection by SQL adapter to be
greater than Y. You should leave some margin (for example, by making the size 10% larger than Y)
to prevent reoccurrence of this problem in subsequent runs.
l Problem: The following warning message appears when running the Oracle LMS Data Collection
by SQL job:
"TotalPhysicalCores is not discovered. You should run an Inventory Activity to discover this data.
For details, see Inventory Activity in the HP Universal CMDB Discovery and Integration Content
Guide."
Solution: Run an Inventory Discovery or Virtualization Discovery, then re-run Oracle LMS Data
Collection by SQL.
l Problem: The auditing data are missing in the Oracle LMS report for STANDBY Oracle instances.
Because the Oracle Database Connection by SQL job cannot connect to STANDBY Oracle
instances.
Solution:To fix the issue, Oracle Connection by Shell job is introduced to discover all Oracle
database servers using the Shell protocol starting with CP19. To have the auditing data in the
Oracle LMS report, make sure you upgrade your Content Pack to CP19 or later.
Note:
o The Oracle Connection by Shell discovery requires UCMDB version 10.22 CUP1 or later.
o The account that is used to connect to Oracle should have the privilege to run SQL*Plus as
SYSDBA.
For details, see the "How to Discover Oracle Data Guard" section in the HPE UCMDB
Discovery and Integrations Content Guide - Discovery Modules.