What's New

What's New in Version 1.31.1

Oracle LMS version 1.31.1 contains the following change:

Changed the date format to YYYY-MM-DD_HH:MM:SS (where the 24-hour time notation is used) on the auditing discovery data that is pushed from UCMDB to Asset Manager (AM) using AM Generic Adapter.

What's New in Version 1.31

Oracle LMS version 1.31 contains the following new features and changes:

  • Enhanced the discovery logic to use Oracle LMS scripts version 17.2. These scripts include the following new functionality:

    • Collected information on:

      • the primary and standby databases that are part of Data Guard architecture
      • the tables and related segments used by Flashback Data Archive
      • the tables enabled for Change Data Capture
      • the change sets queue tables and related segments used by Change Data Capture
      • Repository Creation Utility components
      • Spatial Option usage
    • Collected the list of:

      • redaction policies in the database
      • indexes using Advanced Index Compression
    • Collected the current user's authorization on Database Vault realms

  • The version for the CPU query scripts is 17.2.3.
  • Filled the data center name for ESX server that belongs to a cluster in the Oracle LMS VMware report.

What's New in Version 1.30

Oracle LMS version 1.30 contains the following new features and changes:

  • The existing Oracle LMS Report button Export LMS Data is renamed to Export LMS DB Options Data.
  • Added two new buttons in the Oracle LMS Report, allowing you to export more specific Oracle LMS data:

    • Oracle LMS VMware Data
    • Oracle LMS CPU Data
  • 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.

    The version for the CPU query scripts is 16.2.1.

    The CPU query scripts for different platforms are as follows:

    Operating System CPU Query Script
    Windows lms_cpuq.cmd
    Linux/UNIX lms_cpuq.sh

    The logic to run the scripts is as follows:

    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 SPARC Log in and run the lms_cpuq.sh script in the Control Domain.
    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 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.

Global ID Problem Solution
QCCR1H104072 The default size of the column PROCESS_IDENTIFIER in the Data Flow Probe DB Table LMS_OVERVIEW is 40, causing Oracle LMS data collection to fail when the insertion of longer strings is attempted. Fixed the issue by changing the size of the column PROCESS_IDENTIFIER to 255.
QCCR1H104190 Oracle LMS discovery fails with the following error message: "Failed save to LMS_OPTIONS.java.sql.
BatchUpdateException: Batch entry 80 INSERT INTO LMS_OPTIONS
".
Fixed the issue by increasing the size of the affected column col030 in the table lms_options to 1000.
QCCR1H104760 The Oracle LMS Data Collection by SQL job uses the wrong table name and should not use SYS.MODEL. Fixed the issue by changing the Oracle LMS related table name from SYS.MODEL to SYS.MODEL$.

QCCR1H104940

QCCR1H105118

Oracle LMS discovery does not show specific table names that are used in the SQL query. Fixed the issue by specifying the required database privileged in the details of adapter definition for Oracle LMS discovery.
QCCR1H106211 When running Oracle LMS Audit, the following error message occurs: "ORA-00904: invalid column name". Oracle 8 has no DATABASE_ROLE column in the table V$DATABASE. Just query the column CREATED if there is no DATABASE_ROLE.

QCCR1H109573

The OutOfMemory error occurs when exporting the Oracle LMS report.

If the OutOfMemory error occurs when exporting the Oracle LMS report through UCMDB UI, run the JMX method exportOracleLMSDataWithChunks to export the Oracle LMS report.

Note The maximum size of the Oracle LMS report handled through UCMDB UI is 1.4 GB only if a 32-bit JRE is used.

What's New in Version 1.20

The discovery logic has been enhanced to use Oracle LMS scripts version 15.1. These scripts include the following new functionality:

  • Usage detection of pluggable database (PDB)
  • Enhanced usage detection of Database Vault

  • Usage detection for Database In-Memory Option
  • Other bug fixes and enhancements

Fixed Defects

The following table lists the defects that were fixed in Oracle LMS 1.20.

Global ID Problem Solution
QCCR1H99330 The errors messages returned on the Oracle Database by SQL Job do not contain the Oracle error code anymore. Fixed the issue by adding none check for SID and return the Oracle error messages.
QCCR1H97800 Oracle displays a warning message that the CPU format built into the report is not matching what is expected. For example, currently "XEON" is returned instead of something like "Intel Xeon CPU X5675 @3.07Ghz". The information needed already exists on the CI level under the name attribute of the CPU CI type. Fixed the issue by using CPU.name instead of CPU.cpu_pecifier as processor identifier in LMS_DETAIL.csv and LMS_OVERVIEW.csv.
QCCR1H99367 When checking the option name / pack name in the shortcuts mapping table, it is a case-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. Fixed the issue by applying case sensitive mode.
QCCR1H96425 After upgrading Oracle LMS 1.0 to version 1.1 using management zone, "Can not create Oracle LMS tables" error occurs after a rerun of the Oracle LMS job.

Fixed the issue by using the alter table instead of the drop table to upgrade the database.

QCCR1H97058 The installed/enabled Oracle Database Options do not show up in the LMS_Overview.csv file. Fixed the issue by adding missing Options names and shortcut mapping to Oracle LMS.
QCCR1H92683

When performing LMS Oracle discovery to prepare for an audit, it is successful in discovering a majority of Oracle DB with their LMS files being created, but unable to discover others.

Fixed the issue by applying a code change.
QCCR1H100462

The Oracle LMS job failed on some host, because none check failed for pdb_credential when there is no Oracle Service Name CI linked to Oracle.

Fixed the issue by adding none check for pdb_credentials.

What's New in Version 1.10

New features for Oracle LMS version 1.10 are as follows:

The discovery logic has been enhanced to use Oracle LMS scripts version 14.1. These scripts include the following new functionality:

  • Usage detection for the 12c Multitenant Option.
  • 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.

  • Tuning Pack real usage measurement is also enhanced through the detection of SQL Tuning Advisor, SQL Access Advisor and SQL Tuning Sets features.
  • 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.