You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: manageability-and-operations/observability-and-manageability/database-management/LZ-addons/steps_to_enable_DBM.md
-155Lines changed: 0 additions & 155 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -177,161 +177,6 @@ Click the 'Enable Database Management' button. Then, go to the work request and
177
177
</table>
178
178
179
179
180
-
## **Operation Insights Enabling Steps**
181
-
182
-
183
-
<table>
184
-
<tbody>
185
-
<tr>
186
-
<thalign="left">Steps</th>
187
-
<thalign="left">Descriptón</th>
188
-
<thalign="left">Notes</th>
189
-
</tr>
190
-
<tr>
191
-
192
-
<tdalign="left">1</td>
193
-
<tdalign="left">
194
-
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.
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.
205
-
206
-
All resources needed like compartments, subnets and Network Security Groups (NSGs) were previously provisioned by the LZ
207
-
</td>
208
-
</tr>
209
-
<tr>
210
-
211
-
<tr>
212
-
<tdalign="left"rowspan="2" >2</td>
213
-
214
-
<tdalign="left">
215
-
Create the OPSI private endpoint.
216
-
217
-
* 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.
225
-
226
-
This operation can be easily automated with [Terraform](https://registry.terraform.io/providers/oracle/oci/latest/docs/data-sources/opsi_operations_insights_private_endpoints).
227
-
</td>
228
-
</tr>
229
-
230
-
231
-
<tr>
232
-
<tdalign="left">
233
-
234
-
* 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.
**Note**: If you have already completed this step to enable Database Management, you can skip this step.
246
-
247
-
```
248
-
ALTER USER adbsnmp ACCOUNT UNLOCK;
249
-
ALTER USER adbsnmp IDENTIFIED BY adbsnmp_password;
250
-
grant SELECT ANY DICTIONARY to adbsnmp;
251
-
grant SELECT_CATALOG_ROLE to adbsnmp;
252
-
grant read on awr_pdb_snapshot to adbsnmp;
253
-
grant execute on dbms_workload_repository to adbsnmp;
254
-
```
255
-
256
-
</td>
257
-
<tdalign="left">
258
-
259
-
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)
260
-
261
-
</td>
262
-
</tr>
263
-
264
-
<tdalign="left">4</td>
265
-
<tdalign="left">
266
-
Create a secret in vlt-lzp-shared-mon-security vault that is place in cmp-landingzone-p:cmp-lzp-security compartment.
267
-
268
-
**Note**: If you have already completed this step to enable Database Management, you can skip this step.
269
-
270
-
</td>
271
-
<tdalign="left">
272
-
All resources needed like the dedicated Vault and required policies was previously provisioned by the LZ.
0 commit comments