Troubleshooting and Limitations – Oracle LMS Discovery

This section describes troubleshooting and limitations for Oracle LMS Discovery.

• Problem: The warning message "Configuration file X size (Y) is too big" appears when running the Oracle LMS Data Collection by SQL job.

  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.

• 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."

  Note Instead of TotalPhysicalCores, the message may show SocketsPopulatedPhys, ProcessorIdentifier, PartitioningMethod, and so on.

  Solution: Run an Inventory Discovery or Virtualization Discovery, then re-run Oracle LMS Data Collection by SQL.

• Problem: The auditing data are missing in the Oracle LMS report for STANDBY Oracle instances. This is 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  

  • The Oracle Connection by Shell discovery requires UCMDB version 10.22 CUP1 or later.

  • The account that is used to connect to Oracle should have the privilege to run SQL*Plus as SYSDBA.

  For details, see How to Discover Oracle Data Guard.