+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+| Steps | +Description | +Notes | +
|---|---|---|
| 1 | +
+The database should be created in the appropriate project compartment at the database layer. Ensure that the 'Network Access' option is set to 'Private Endpoint Access Only.' Then, assign the database subnet and select the NSGs provisioned in the database compartment.
+
+Example for Prod database:
+
+* **Compartment**-> cmp-landingzone-p:cmp-lzp-prod:cmp-lzp-p-projects:cmp-lzp-p-proj1:cmp-lzp-p-proj1-db
+* **Network**-> vnc:vcn-fra-lzp-p-projects; subnet:ssn-fra-lzp-p-db
+* **nsg**-> nsg-lzp-p-projects-mon-pe-db1
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ |
++ +If the database was created previously, ensure it is placed in the correct cmp, assigned to the proper subnet, and configured with the appropriate NSG. + +All resources needed like compartments, subnets and Network Security Groups (NSGs) were previously provisioned by the LZ. + | +
| 2 | + + +
+Create the DMA private endpoint.
+
+* In a **global approach**, DMA PEs will be placed in the monitoring subnet (sn-fra-lzp-hub-mon) in the hub vcn and should be assigned to the GLOBAL PE NSGs (nsg-fra-lzp-hub-global-mon-pe). Example: pe_lz_global_dma.
+
+
+
+ |
+
+
++All resources needed like Subnets, route tables (RT), Gateways (RT),security lists (SL), and Network Security Groups (NSGs) were previously provisioned by the LZ. + +This operation can be easily automated with [Terraform](https://registry.terraform.io/providers/oracle/oci/latest/docs/resources/database_management_db_management_private_endpoint). + | +
|
+
+* In a **local approach**, DMA PEs and the ATP PE will reside in the same database subnet (ssn-fra-lzp-p-db), and the nsg-lzp-p-projects-mon-pe-db1 NSGs will allow communication between them. Example: pe_lz_p_dma.
+
+
+
+ |
+3 | ++Unlock and change the password for adbsnmp. + +``` +ALTER USER adbsnmp ACCOUNT UNLOCK; +ALTER USER adbsnmp IDENTIFIED BY adbsnmp_password; +grant SELECT ANY DICTIONARY to adbsnmp; +grant SELECT_CATALOG_ROLE to adbsnmp; +grant read on awr_pdb_snapshot to adbsnmp; +grant execute on dbms_workload_repository to adbsnmp; +``` + + | ++ +To connect to a database placed in a private subnet you can follow this [blog](https://blogs.oracle.com/datawarehousing/post/4-ways-to-connect-to-autonomous-database-on-a-private-network). + | + + +4 | +
+
+Create a secret in the vlt-lzp-shared-mon-security vault located within the cmp-landingzone-p:cmp-lzp-security compartment.
+
+
+
+ |
++All resources needed like the dedicated Vault and required policies was previously provisioned by the LZ. + | + + + + +
| 5 | +
+
+Enable [Database Management](https://docs.oracle.com/en-us/iaas/database-management/doc/enable-database-management-autonomous-databases.html).
+
+
+
+ |
+
++Remember to select the private DMA endpoint created in step2. + + | +
|
+
+
+
+
+
+
+
+
+
+ |
+6 | +
+
+Click the 'Enable Database Management' button. Then, go to the work request and check the progress.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ |
++ | + + + +
|
+| Using Local PEs | 
|
+
+
+# License
+
+Copyright (c) 2025 Oracle and/or its affiliates.
+
+Licensed under the Universal Permissive License (UPL), Version 1.0.
+
+See [LICENSE](/LICENSE) for more details.
+
+
+
diff --git a/manageability-and-operations/observability-and-manageability/database-management/LZ-addons/steps_to_enable_DBM_ExaCC.md b/manageability-and-operations/observability-and-manageability/database-management/LZ-addons/steps_to_enable_DBM_ExaCC.md
new file mode 100644
index 000000000..f58871238
--- /dev/null
+++ b/manageability-and-operations/observability-and-manageability/database-management/LZ-addons/steps_to_enable_DBM_ExaCC.md
@@ -0,0 +1,159 @@
+## **Database Management Enabling Steps for ExaCC**
+
+
+| Steps | +Description | +Notes | +
|---|---|---|
| 1 | +
+
+__Management Agent Installation__
+
+On each VMCluster Node:
+
+
+Download the agent from OCI Console Observability and Managment to each single box
+
+
+
+On the box install the agent Doc ID [3015115.1](https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=455266221038386&id=3015115.1&_afrWindowMode=0&_adf.ctrl-state=78xw71hh9_4)
+
+```
+sudo mkdir -p /devext/oracle/mgmt_agent
+cat<
+
+ |
++ + + | +
| 2 | + + +
+
+__Create the Monitor user__
+
+Creeate a user on each CDB
+Download grantPrivileges.sql MOS Doc ID [2857604.1](https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=1dhr4uuluw_4&_afrLoop=105039164570647#BODYTEXT) \
+and run on the Container Database
+```
+sqlplus sys/ |
+
+
+|
| 3 | +
+
+Create a secret key for C##OCI_MON_USER password (No for Autonomous)
+>Go to Identity&Security → Key Management →Secret Management
+
+
+
+
+
+Create a secret for C##OCI_MON_USER password
+>Go to Identity&Security → Key Management & Secret Management → Create a key → Create a secret
+
+
+
+ |
++ + + | + + +4 | +
+
+__Enable Database Management__
+>Go to Observability →Database Management →Administration → Managed databases
+
+
+
+Select the user secret key you have just created
+
+
+
+First you need to register CDB after that you repeat the steps for each PDB.
+ |
++ + | + + + + +
| Steps | +Description | +Notes | +
|---|---|---|
| 1 | ++The database should be created in the appropriate project compartment at the DB layer, using the DB subnet and assign the NSGs to the database. + +Example for Prod database: + +* **Compartment**-> cmp-landingzone-p:cmp-lzp-prod:cmp-lzp-p-projects:cmp-lzp-p-proj1:cmp-lzp-p-proj1-db +* **Network**-> vnc:vcn-fra-lzp-p-projects; subnet:ssn-fra-lzp-p-db +* **nsg**-> nsg-lzp-p-projects-mon-pe-db1 + | ++ +If the database was created previously, ensure it is placed in the correct CMP, assigned to the proper subnet, and configured with the appropriate NSG. + +All resources needed like compartments, subnets and Network Security Groups (NSGs) were previously provisioned by the LZ + | +
| 2 | + +
+Create the OPSI private endpoint.
+
+* In a **global approach**, OPSI PEs will be placed in the monitoring subnet (sn-fra-lzp-hub-mon) in the hub and should be assigned to the PE NSGs (nsg-fra-lzp-hub-global-mon-pe). Example: pe_lz_global_opsi.
+
+
+
+
+ |
++All resources needed like Subnets, route tables (RT), Gateways (RT),security lists (SL), and Network Security Groups (NSGs) were previously provisioned by the LZ. + +This operation can be easily automated with [Terraform](https://registry.terraform.io/providers/oracle/oci/latest/docs/data-sources/opsi_operations_insights_private_endpoints). + | +
+
+* In a **local approach**, OPSI PEs and the ATP PE will reside in the same database subnet (ssn-fra-lzp-p-db), and the nsg-lzp-p-projects-mon-pe-db1 NSGs will allow communication between them. Example: pe_lz_p_opsi.
+
+
+
+ |
+3 | ++Unlock and change the password for adbsnmp. + +**Note**: If you have already completed this step to enable Database Management, you can skip this step. + +``` +ALTER USER adbsnmp ACCOUNT UNLOCK; +ALTER USER adbsnmp IDENTIFIED BY adbsnmp_password; +grant SELECT ANY DICTIONARY to adbsnmp; +grant SELECT_CATALOG_ROLE to adbsnmp; +grant read on awr_pdb_snapshot to adbsnmp; +grant execute on dbms_workload_repository to adbsnmp; +``` + + | ++ +To connect to a database placed in a private subnet you can follow this [blog](https://blogs.oracle.com/datawarehousing/post/4-ways-to-connect-to-autonomous-database-on-a-private-network) + + | + + +4 | ++Create a secret in vlt-lzp-shared-mon-security vault that is place in cmp-landingzone-p:cmp-lzp-security compartment. + +**Note**: If you have already completed this step to enable Database Management, you can skip this step. + + | ++All resources needed like the dedicated Vault and required policies was previously provisioned by the LZ. + | + + + +
| 5 | +
+
+Enable [Ops Insights](https://docs.oracle.com/en-us/iaas/autonomous-database/doc/enable-operations-insights-dedicated-autonomous-database.html).
+
+
+
+ |
+
++ +Remember to select the private OPSI endpoint created in Step 2. Choose the appropriate PE based on whether you're using a Global or Local approach. + + | +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ |
+6 | +
+
+Click the 'Add database' button. Then, go to the work request and check the progress.
+
+
+
+
+ |
++ | + + + + +
|
+| Using Local PEs | |
+
+
+# License
+
+Copyright (c) 2025 Oracle and/or its affiliates.
+
+Licensed under the Universal Permissive License (UPL), Version 1.0.
+
+See [LICENSE](/LICENSE) for more details.
+
+
+
diff --git a/manageability-and-operations/observability-and-manageability/operations-insights/LZ-addons/steps_to_enable_OPSI_ExaCC.md b/manageability-and-operations/observability-and-manageability/operations-insights/LZ-addons/steps_to_enable_OPSI_ExaCC.md
new file mode 100644
index 000000000..7a786de17
--- /dev/null
+++ b/manageability-and-operations/observability-and-manageability/operations-insights/LZ-addons/steps_to_enable_OPSI_ExaCC.md
@@ -0,0 +1,147 @@
+## **OPSI Enabling Steps for ExaCC**
+
+
+| Steps | +Description | +Notes | +
|---|---|---|
| 1 | +
+
+__Management Agent Installation__
+
+On each VMCluster Node:
+
+
+Download the agent from OCI Console Observability and Managment to each single box
+
+
+
+On the box install the agent Doc ID [3015115.1](https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=455266221038386&id=3015115.1&_afrWindowMode=0&_adf.ctrl-state=78xw71hh9_4)
+
+```
+sudo mkdir -p /devext/oracle/mgmt_agent
+cat<
+
+ |
++ + + | +
| 2 | + + +
+
+__Create the Monitor user__
+
+Creeate a user on each CDB
+Download grantPrivileges.sql MOS Doc ID [2857604.1](https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=1dhr4uuluw_4&_afrLoop=105039164570647#BODYTEXT) and run on the Container Database
+```
+sqlplus sys/ |
+
+
+|
| 3 | +
+
+Create a secret key for C##OCI_MON_USER password (No for Autonomous)
+>Go to Identity&Security → Key Management →Secret Management
+
+
+
+
+>Go to Identity&Security → Key Management & Secret Management → Create a key → Create a secret for C##OCI_MON_USER password
+
+
+
+ |
++ + + | + + +4 | +
+
+__Enable OpsInsight__
+>Go to Observability →OpsInsight→Administration → Exadata Fleet. Select Cloud Infrastructure, ExaDB-C@C
+
+
+Specify the same credentiols you use for Database management. OpsInsight will be enabled on all PDB of the specified CDB.
+
+ |
++ + | + + + + +