Skip to content

Commit 8a1a9d9

Browse files
OraGitPush1OraGitPush1
authored
WMS ID: 11796 Title: Introduction to Oracle Global Data Services (GDS) (#770)
* WMS ID: 11796 Introduction to Oracle Global Data Services (GDS) initial check-in WMS ID: 11796 Introduction to Oracle Global Data Services (GDS) initial check-in. * WMS ID: 11796 Introduction to Oracle Global Data Services (GDS) initial checkins WMS ID: 11796 Introduction to Oracle Global Data Services (GDS) initial checkins for Setup Graphical Remote Desktop * WMS ID: 11796 WMS ID: 11796 graphical-remote-desktop formatting * WMS ID: 11796 WMS ID: 11796 Introduction to Oracle Global Data Services (GDS) formatting updates for setup-graphical-remote-desktop * WMS ID: 11796 WMS ID: 11796 Introduction to Oracle Global Data Services (GDS) formatting updates for setup-graphical-remote-desktop * WMS ID: 11796 formatting updates WMS ID: 11796 Introduction to Oracle Global Data Services (GDS) formatting updates for setup-graphical-remote-desktop * WMS ID: 11796 formatting updates WMS ID: 11796 Introduction to Oracle Global Data Services (GDS) formatting updates for setup-graphical-remote-desktop * WMS ID: 11796 Title: Introduction to Oracle Global Data Services (GDS) WMS ID: 11796 Title: Introduction to Oracle Global Data Services (GDS) Content updates with additional steps and formatting updates * WMS ID: 11796 Title: Introduction to Oracle Global Data Services (GDS) WMS ID: 11796 Title: Introduction to Oracle Global Data Services (GDS) Modified Steps and formatting updates. * WMS ID: 11796 Title: Introduction to Oracle Global Data Services (GDS) WMS ID: 11796 Title: Introduction to Oracle Global Data Services (GDS) Estimated Time section update, additional contents update for Bold / non-bold chars.
1 parent 737c462 commit 8a1a9d9

File tree

9 files changed

+1228
-754
lines changed

9 files changed

+1228
-754
lines changed

‎gds/gds-introduction/gds-configuration/gds-service-configuration.md‎

Lines changed: 388 additions & 229 deletions
Large diffs are not rendered by default.

‎gds/gds-introduction/gds-dbs-configuration/gds-dbs-configuration.md‎

Lines changed: 138 additions & 73 deletions
Original file line numberDiff line numberDiff line change
@@ -1,93 +1,158 @@
1-
# Database updates for enabling GDS
1+
# Database Updates for Enabling GDS
22

3-
Database(s) needs to be GDS enabled before configuring GDS using GDSCTL. In this lab, we'll run the shell scripts which has the SQL commands for database configurations.
4-
*Estimated Time*: 15 minutes
3+
## Introduction
54

6-
### Objectives
5+
Before configuring GDS using GDSCTL, each database must be GDS-enabled. In this lab, we will execute shell scripts containing the necessary SQL commands for database configuration.
76

8-
In this lab, you will:
7+
Estimated Time: 15 Minutes
98

10-
* Configure each Database for commands to be run using sysdba.
11-
* Verify Database are ready, so that we can start GDS configuration using GDSCTL in the next lab.
12-
### Prerequisites
13-
This lab assumes you have:
14-
* A Free Tier, Paid or LiveLabs Oracle Cloud account
15-
* You have completed:
16-
* Lab: Validate workshop environment
17-
* Lab: GDS Installation
9+
**Objectives**
1810

19-
##
20-
## Task 1: Connect to Podman instance of Catalog Primary DB
11+
In this lab, you will:
2112

22-
1. Apply Database Configuration for Catalog which will be used in "create gdscatalog.." at the later stage from gsm1 to apply GDS configuration steps.
13+
* Configure each database by executing the required commands as SYSDBA.
14+
* Verify that the databases are ready for GDS configuration, which will be performed using GDSCTL in the next lab.
2315

24-
You will run "configure_catalog.sh" which mainly:
25-
* Unlocks GSMCATUSER on both CDB and PDB of the catalog database.
26-
* Enables ARCHIVELOG, FLASHBACK, and FORCE LOGGING if not enabled.
27-
* Restarts database in READ WRITE mode.
16+
**Prerequisites**
17+
18+
Before starting this lab, ensure that you have:
19+
* A Free Tier, Paid, or LiveLabs Oracle Cloud account.
20+
* Successfully completed the following prerequisite labs:
21+
* Lab: Validate Workshop Environment
22+
* Lab: GDS Installation
2823

29-
```
30-
<copy>
31-
sudo podman exec -it catalog /bin/bash
32-
# View the contents of "configure_catalog.sh". This file doesn't need any updates for this LiveLab task.
33-
cat configure_catalog.sh
24+
## Task 1: Configure the Catalog Database
25+
Before proceeding with GDS configuration, the GDS Catalog Database must be prepared. The GDS Catalog database can be a standalone or shared database and will contain the GDS catalog (a repository of metadata about the GDS configuration such as regions, database pools, global services, etc.).
3426

35-
# Run the script
36-
./configure_catalog.sh
37-
exit
38-
</copy>
39-
```
27+
This task ensures that the database is properly configured before running the CREATE GDSCATALOG command, which will be executed later from gsm1.
4028

41-
## Task 2: Connect to Podman instance of Primary Database for Application
4229

43-
1. Prepare Primary Database for the application. This primary database will be used in "add database" at later stage from gsm1 to apply GDS configuration steps.
30+
**What This Configuration Does**
4431

45-
You will run "configure_primary.sh" which mainly:
46-
* Unlocks GSMUSER on both CDB and PDB of the primary database.
47-
* Unlocks GSMROOTUSER on CDB only of the primary database.
32+
You will run the script configure_catalog.sh. This script performs the following tasks on the GDS Catalog database:
33+
* Unlocks GSMCATUSER on both CDB and PDB of the catalog database.
4834
* Enables ARCHIVELOG, FLASHBACK, and FORCE LOGGING if not enabled.
4935
* Restarts database in READ WRITE mode.
5036

51-
```
52-
<copy>
53-
sudo podman exec -it primary /bin/bash
54-
# View the contents of "configure_primary.sh". This file doesn't need updates for this LiveLab task.
55-
cat configure_primary.sh
5637

57-
# Run the script
58-
./configure_primary.sh
59-
exit
60-
</copy>
61-
```
62-
63-
## Task 3: Connection to Podman instance of StandBy Database for Application Data
64-
65-
1. Though no updates needed at this time for the standby database, you can still verify its PDB is in READ ONLY mode.
66-
67-
```nohighlighting
68-
<copy>
69-
sudo podman exec -it standby /bin/bash
70-
# Login as sysDBA and Verify that PDBs are in READ ONLY OPEN MODE
71-
sqlplus / as sysdba;
72-
show pdbs;
73-
select open_mode from v$database;
74-
# To exit from standby container and return to opc@oraclegdshost
75-
exit
76-
exit
77-
</copy>
78-
```
79-
80-
![standby-verify](./images/standby-verify.png " ")
81-
82-
This completes database tasks.
83-
84-
Note: Review the contents of each of the database scripts to get familiar with the necessary steps needed prior to GDSCTL configuration steps.
85-
86-
Since You have installed GSM already, now you can perform the next Lab **GDS Configuration using GDSCTL**
38+
**Steps to Configure the Catalog Database**
39+
40+
1. Access the Catalog Database container:
41+
```nohighlighting
42+
<copy>
43+
sudo podman exec -it catalog /bin/bash
44+
</copy>
45+
```
46+
2. View the contents of configure_catalog.sh (No modifications are required for this LiveLab task):
47+
```nohighlighting
48+
<copy>
49+
cat configure_catalog.sh
50+
</copy>
51+
```
52+
3. Execute the script to apply the necessary configurations:
53+
```nohighlighting
54+
<copy>
55+
./configure_catalog.sh
56+
</copy>
57+
```
58+
4. Exit the container session:
59+
```nohighlighting
60+
<copy>
61+
exit
62+
</copy>
63+
```
64+
65+
## Task 2: Configure the Primary Database for the Application
66+
Before proceeding with GDS configuration, the Primary Database must be prepared. This task ensures that the database is properly configured before the ADD DATABASE command is executed later from gsm1.
67+
68+
69+
**What This Configuration Does**
70+
71+
You will run the script configure_primary.sh, which performs the following tasks:
72+
73+
* Unlocks GSMUSER in both the CDB and PDB of the primary database.
74+
* Unlocks GSMROOTUSER in the CDB only of the primary database.
75+
* Enables ARCHIVELOG, FLASHBACK, and FORCE LOGGING (if not already enabled).
76+
* Restarts the database in READ WRITE mode.
77+
78+
79+
**Steps to Configure the Primary Database**
80+
81+
1. Access the Primary Database container:
82+
```nohighlighting
83+
<copy>
84+
sudo podman exec -it primary /bin/bash
85+
</copy>
86+
```
87+
2. View the contents of configure_primary.sh (No modifications are required for this LiveLab task):
88+
```nohighlighting
89+
<copy>
90+
cat configure_primary.sh
91+
</copy>
92+
```
93+
3. Execute the script to apply the necessary configurations:
94+
```nohighlighting
95+
<copy>
96+
./configure_primary.sh
97+
</copy>
98+
```
99+
4. Exit the container session:
100+
```nohighlighting
101+
<copy>
102+
exit
103+
</copy>
104+
```
105+
106+
## Task 3: Verify the Standby Database for Application Data
107+
108+
Although no updates are required for the standby database at this stage, you can verify that its PDB is in READ ONLY mode.
109+
110+
**Steps to Verify the Standby Database**
111+
112+
1. Access the Standby Database container:
113+
```nohighlighting
114+
<copy>
115+
sudo podman exec -it standby /bin/bash
116+
</copy>
117+
```
118+
2. Log in as SYSDBA and verify the PDB open mode:
119+
```nohighlighting
120+
<copy>
121+
sqlplus / as sysdba
122+
</copy>
123+
```
124+
3. Check the status of all PDBs:
125+
```nohighlighting
126+
<copy>
127+
show pdbs
128+
</copy>
129+
```
130+
4. Confirm that the database is in READ ONLY mode:
131+
```nohighlighting
132+
<copy>
133+
select open_mode from v$database;
134+
</copy>
135+
```
136+
5. Exit the SQL session and container:
137+
```nohighlighting
138+
<copy>
139+
exit
140+
</copy>
141+
```
142+
![standby-verify](./images/standby-verify.png " ")
143+
144+
## Conclusion
145+
146+
Database Configuration Completed.
147+
148+
This concludes the database configuration tasks.
149+
150+
**Note**: It is recommended to review the contents of each database script to understand the key configuration elements required before proceeding with GDSCTL setup. Now that GSM is installed, you are ready to move on to the next lab: Oracle GDS Configuration
87151

88152
You may now **proceed to the next lab**
89153

154+
90155
## Acknowledgements
91-
* **Author** - Ajay Joshi, Distributed Database Product Management
92-
* **Contributors** - Ravi Sharma, Vibhor Sharma, Jyoti Verma, Param Saini, Distributed Database Product Management
93-
* **Last Updated By/Date** - Ajay Joshi, February 2025
156+
* **Authors** - Ajay Joshi, Ravi Sharma, Distributed Database Product Management
157+
* **Contributors** - Vibhor Sharma, Jyoti Verma, Param Saini, Distributed Database Product Management
158+
* **Last Updated By/Date** - Ajay Joshi, March 2025

0 commit comments

Comments
 (0)