Join us at the CMS Virtual Customer Forum December 9th
Please join us at the CMS Virtual Customer Forum December 9, 2020 | 7:30 a.m. PDT | 4:30 p.m. CEST

Review of the UDM Oracle Topology to regroup objects based on the Oracle architecture/documentation

Idea ID 2836115

Review of the UDM Oracle Topology to regroup objects based on the Oracle architecture/documentation

We'd like to present this Idea to suggest a new way to regroup Oracle objects. The reasons are:

  • Align with normal Instance and Database split of resources, as documented by Oracle
  • To be able to limit duplicates in databases served on multiple instances (ie. Clusters)
  • To be able to match properly with existing DBA inventory information
  • To enable DBA to review and trust the information within UCMDB based on their knowledge of the Oracle architecture
  • To align Oracle objects based on running software (processes) versus resources (static files)

The approach we propose is:

  • Review and adjust current UDM and discovery scripts
  • To create an Oracle Instance CIT, it would contain
    • Processes like: ora_ckpt, ora_lgwr, ora_pmon, ora_smon, …
    • IpServiceEndpoints on port 1521
  • To create an Oracle Database CIT, to contain
    • Objects like: DB Link Object, DB Scheduler Job, DB Tablespace, DB User, DB_Control-File, DB_Re-do File, DB_Re-do File group, Oracle Schema, DB Data File, …
  • To change some CIT locations in the UDM : Oracle CDB, Oracle PDB, Oracle, all CI Types under “Database Schema”

The Oracle architecure and documentation represents the Instance and the Database in the following manner. We can see the top part (Instance) contains Running Software CIT, like processes. The bottom part (Database) contains more static information found on the server.
Idea Oracle doc.jpg

What we propose in the following picture (before and after) is to split the current Oracle CIT into an Instance and a Database:

Idea before after Oracle.jpg

To enable that transformation, the following table shows the new CIT to be created and existing ones to be modified:

 

CI Name (internal name)

Change/Action

CI Type

Description

Current location

New location

Database Instance (new)

Create new CI Type

Internal name: (instance)

Application Resource

New folder to regroup all instances

None

Running Software

Oracle Instance (new)

Create new CI Type

Internal name: (instance_oracle)

 

None

Running Software\Database Instance

Oracle Database (new)

Create new CI Type

Internal name: (oracle_database)

Application Resource

New CI Type to regroup Oracle Database objects

None

Database

Database (database)

Parent CIT

Move to new location: Database

New folder to regroup all databases

Running Software

Application Resource

Oracle (oracle)

Rename display label

Oracle Instance (oracle)

 

<Running Software/Database>

And using new Display label

<Running Software/Database  Instance>

Oracle CDB (oracle_cdb)

Move to new location:

 

Database Resource

Database Resource/Database/Oracle Database

Oracle PDB (oracle_pdb)

Move to new location:

 

Database Resource

Database Resource/Database/Oracle Database

 

 

 

 

 

 

Some impact and changes to consider:

  • Oracle Topology/Connection will need to change to
  • use new “Oracle Database” as the parent for Oracle objects
  • Use old Oracle instances processes to use the new “Oracle Instance” CIT
  • New relationships will need to be put into place
  • Scripts will need to created to move current CIs into the new locations
  •  
  • A side impact, will need to review other databases and instances also.

 

Please consider this Idea, as it would considerably help with the maintenance of Oracle database and trust in the discovered data.

 

Regards

Stéphane Bourgouin

3 Comments
Commander
Commander

This is a “new and improved” idea that covers the elements of the original idea we suggested (link below) as well as new elements like CDB and PDB.

The former idea is https://community.microfocus.com/t5/CMS-Idea-Exchange/Duplicate-Application-Resources-like-Oracle-Schema/idi-p/2773459

We think this new idea with an improved documentation should be used for your review with R&D.

Let us know what comes out of it. If you need to have a discussion with us, please let us know.

Micro Focus Expert
Micro Focus Expert
Thank you for sharing your idea! It’s open for comments and kudos, and we’re looking forward to input from the community. Once there is enough community traction, it will be further reviewed by the product team
Micro Focus Expert
Micro Focus Expert
Status changed to: Waiting for Votes
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.