Skip to content

Commit c3a91fa

Browse files
Update steps_to_enable_DBM.md
1 parent b9af54c commit c3a91fa

File tree

1 file changed

+0
-155
lines changed
  • manageability-and-operations/observability-and-manageability/database-management/LZ-addons

1 file changed

+0
-155
lines changed

manageability-and-operations/observability-and-manageability/database-management/LZ-addons/steps_to_enable_DBM.md

Lines changed: 0 additions & 155 deletions
Original file line numberDiff line numberDiff line change
@@ -177,161 +177,6 @@ Click the 'Enable Database Management' button. Then, go to the work request and
177177
</table>
178178

179179

180-
## **Operation Insights Enabling Steps**
181-
182-
183-
<table>
184-
<tbody>
185-
<tr>
186-
<th align="left">Steps</th>
187-
<th align="left">Descriptón</th>
188-
<th align="left">Notes</th>
189-
</tr>
190-
<tr>
191-
192-
<td align="left">1</td>
193-
<td align="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.
195-
196-
Example for Prod database:
197-
198-
* **Compartment**-> cmp-landingzone-p:cmp-lzp-prod:cmp-lzp-p-projects:cmp-lzp-p-proj1:cmp-lzp-p-proj1-db
199-
* **Network**-> vnc:vcn-fra-lzp-p-projects; subnet:ssn-fra-lzp-p-db
200-
* **nsg**-> nsg-lzp-p-projects-mon-pe-db1
201-
</td>
202-
<td align="left">
203-
204-
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-
<td align="left" rowspan="2" >2</td>
213-
214-
<td align="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.
218-
219-
<img src="../images/PE_OPSI_GLOBAL.png" height="100" align="left" > </img>
220-
221-
222-
</td>
223-
<td align="left" rowspan="2">
224-
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-
<td align="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.
235-
236-
<img src="../images/PE_OPSI_LOCAL.png" height="100" align="left" > </img>
237-
238-
</td>
239-
</tr>
240-
241-
<td align="left">3</td>
242-
<td align="left">
243-
Unlock and change the password for adbsnmp.
244-
245-
**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-
<td align="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-
<td align="left">4</td>
265-
<td align="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-
<td align="left">
272-
All resources needed like the dedicated Vault and required policies was previously provisioned by the LZ.
273-
</td>
274-
</tr>
275-
276-
277-
<tr>
278-
<td align="left" rowspan="2" >5</td>
279-
<td align="left">
280-
281-
Enable [Operation Insights](https://docs.oracle.com/en-us/iaas/autonomous-database/doc/enable-operations-insights-dedicated-autonomous-database.html).
282-
283-
<img src="../images/ENABLE_OPSI.png" height="100" align="left"></img>
284-
&nbsp;
285-
</td>
286-
287-
<td align="left" rowspan="2">
288-
289-
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.
290-
291-
</td>
292-
</tr>
293-
294-
<tr>
295-
<td align="left">
296-
&nbsp;
297-
<img src="../images/OPSI_1.png" height="100" width="200" align="left"></img>
298-
&nbsp;
299-
&nbsp;
300-
&nbsp;
301-
302-
<img src="../images/OPSI_1.png" height="100" width="200" align="left"></img>
303-
&nbsp;
304-
&nbsp;
305-
&nbsp;
306-
307-
<img src="../images/OPSI_GLOBAL.png" height="100" width="200" align="left"></img>
308-
&nbsp;
309-
&nbsp;
310-
&nbsp;
311-
312-
313-
</td>
314-
</tr>
315-
316-
317-
<td align="left">6</td>
318-
<td align="left">
319-
320-
Click the 'Add database' button. Then, go to the work request and check the progress.
321-
322-
323-
<img src="../images/OPSI_VIEW.png" height="100" width="200" align="left"></img>
324-
325-
</td>
326-
<td align="left">
327-
</td>
328-
</tr>
329-
330-
331-
</tbody>
332-
</table>
333-
334-
335180

336181
These diagrams illustrate the final result:
337182

0 commit comments

Comments
 (0)