Skip to content

Commit b88f807

Browse files
NicolaCimitileNicolaCimitile
authored
Update steps_to_enable_OPSI.md
1 parent 00533e0 commit b88f807

File tree

1 file changed

+0
-178
lines changed
  • manageability-and-operations/observability-and-manageability/operations-insights/LZ-addons/LZ-autonomous-databases

1 file changed

+0
-178
lines changed

‎manageability-and-operations/observability-and-manageability/operations-insights/LZ-addons/LZ-autonomous-databases/steps_to_enable_OPSI.md‎

Lines changed: 0 additions & 178 deletions
Original file line numberDiff line numberDiff line change
@@ -1,182 +1,4 @@
11

2-
## **Database Management Enabling Steps**
3-
4-
5-
<table>
6-
<tbody>
7-
<tr>
8-
<th align="left">Steps</th>
9-
<th align="left">Description</th>
10-
<th align="left">Notes</th>
11-
</tr>
12-
<tr>
13-
14-
<td align="left" >1</td>
15-
<td align="left">
16-
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.
17-
18-
Example for Prod database:
19-
20-
* **Compartment**-> cmp-landingzone-p:cmp-lzp-prod:cmp-lzp-p-projects:cmp-lzp-p-proj1:cmp-lzp-p-proj1-db
21-
* **Network**-> vnc:vcn-fra-lzp-p-projects; subnet:ssn-fra-lzp-p-db
22-
* **nsg**-> nsg-lzp-p-projects-mon-pe-db1
23-
24-
25-
<img src="../images/DB_CMP.png" height="100" width="200" align="left">
26-
27-
&nbsp;
28-
29-
<img src="../images/DB_NET.png" height="100" width="200" align="left">
30-
31-
&nbsp;
32-
33-
<img src="../images/DB_NSG.png" height="100" width="200" align="left">
34-
35-
&nbsp;
36-
37-
</td>
38-
<td align="left">
39-
40-
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.
41-
42-
All resources needed like compartments, subnets and Network Security Groups (NSGs) were previously provisioned by the LZ.
43-
</td>
44-
</tr>
45-
46-
<tr>
47-
<td align="left" rowspan="2" >2</td>
48-
49-
50-
<td align="left">
51-
Create the DMA private endpoint.
52-
53-
* 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.
54-
55-
&nbsp;
56-
<img src="../images/GLOBAL_PE.png" height="100" width="200" align="left">
57-
</td>
58-
59-
60-
<td align="left" rowspan="2">
61-
All resources needed like Subnets, route tables (RT), Gateways (RT),security lists (SL), and Network Security Groups (NSGs) were previously provisioned by the LZ.
62-
63-
This operation can be easily automated with [Terraform](https://registry.terraform.io/providers/oracle/oci/latest/docs/resources/database_management_db_management_private_endpoint).
64-
</td>
65-
</tr>
66-
67-
<tr>
68-
69-
<td align="left">
70-
71-
* 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.
72-
73-
&nbsp;
74-
<img src="../images/LOCAL_PE.png" height="100" width="200" align="left">
75-
</td>
76-
</tr>
77-
78-
79-
80-
<td align="left">3</td>
81-
<td align="left">
82-
Unlock and change the password for adbsnmp.
83-
84-
```
85-
ALTER USER adbsnmp ACCOUNT UNLOCK;
86-
ALTER USER adbsnmp IDENTIFIED BY adbsnmp_password; 
87-
grant SELECT ANY DICTIONARY to adbsnmp;
88-
grant SELECT_CATALOG_ROLE to adbsnmp;
89-
grant read on awr_pdb_snapshot to adbsnmp;
90-
grant execute on dbms_workload_repository to adbsnmp;
91-
```
92-
93-
</td>
94-
<td align="left">
95-
96-
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).
97-
</td>
98-
</tr>
99-
100-
<td align="left">4</td>
101-
<td align="left">
102-
103-
Create a secret in the vlt-lzp-shared-mon-security vault located within the cmp-landingzone-p:cmp-lzp-security compartment.
104-
105-
<img src="../images/SECRET.png" height="100" width="200" align="left">
106-
107-
</td>
108-
<td align="left">
109-
All resources needed like the dedicated Vault and required policies was previously provisioned by the LZ.
110-
</td>
111-
</tr>
112-
113-
114-
115-
<tr>
116-
<td align="left" rowspan="2" >5</td>
117-
<td align="left">
118-
119-
Enable [Database Management](https://docs.oracle.com/en-us/iaas/database-management/doc/enable-database-management-autonomous-databases.html).
120-
121-
<img src="../images/ENABLE.png" height="100" align="left"></img>
122-
&nbsp;
123-
</td>
124-
125-
<td align="left" rowspan="2">
126-
Remember to select the private DMA endpoint created in step2.
127-
128-
</td>
129-
</tr>
130-
131-
<tr>
132-
<td align="left">
133-
134-
<img src="../images/DM_1.png" height="100" width="200" align="left"></img>
135-
&nbsp;
136-
137-
<img src="../images/DM_2.png" height="100" width="200" align="left"></img>
138-
&nbsp;
139-
140-
<img src="../images/DM_3.png" height="100" width="200" align="left"></img>
141-
&nbsp;
142-
</td>
143-
</tr>
144-
145-
146-
<td align="left">6</td>
147-
<td align="left">
148-
149-
Click the 'Enable Database Management' button. Then, go to the work request and check the progress.
150-
151-
&nbsp;
152-
<img src="../images/50.png" height="100" width="600" align="left"></img>
153-
&nbsp;
154-
&nbsp;
155-
&nbsp;
156-
157-
<img src="../images/100.png" height="100" width="600" align="left"></img>
158-
&nbsp;
159-
&nbsp;
160-
&nbsp;
161-
162-
<img src="../images/CONSOLE.png" height="100" align="left" > </img>
163-
&nbsp;
164-
&nbsp;
165-
&nbsp;
166-
167-
<img src="../images/DMA.png" align="left"> </img>
168-
&nbsp;
169-
&nbsp;
170-
171-
</td>
172-
<td align="left">
173-
</td>
174-
</tr>
175-
176-
</tbody>
177-
</table>
178-
179-
1802
## **Operation Insights Enabling Steps**
1813

1824

0 commit comments

Comments
 (0)