Skip to content

Commit 484289a

Browse files
the below -> the following
1 parent cb16c5f commit 484289a

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/multitenant/README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -88,14 +88,14 @@ Before you want to manage the life cycle of a PDB in a CDB using the Oracle DB O
8888

8989
Pluggable Database management operation is performed in the Container Database (CDB) and it includes create, clone, plug, unplug, delete, modify and map operations.
9090

91-
You cannot have an ORDS enabled schema in the container database. To perform the PDB lifecycle management operations, the default CDB administrator credentials must be defined by performing the below steps on the target CDB(s):
91+
You cannot have an ORDS enabled schema in the container database. To perform the PDB lifecycle management operations, the default CDB administrator credentials must be defined by performing following steps on the target CDB(s):
9292

9393
Create the CDB administrator user and grant the required privileges. In this example, the user is `C##DBAPI_CDB_ADMIN`. However, any suitable common user name can be used.
9494

9595
```SQL
9696
SQL> conn /as sysdba
9797

98-
-- Create the below users at the database level:
98+
-- Create following users at the database level:
9999

100100
ALTER SESSION SET "_oracle_script"=true;
101101
DROP USER C##DBAPI_CDB_ADMIN cascade;
@@ -105,7 +105,7 @@ GRANT SYSDBA TO C##DBAPI_CDB_ADMIN CONTAINER = ALL;
105105
GRANT CREATE SESSION TO C##DBAPI_CDB_ADMIN CONTAINER = ALL;
106106

107107

108-
-- Verify the account status of the below usernames. They should not be in locked status:
108+
-- Verify the account status of the following usernames. They should not be in locked status:
109109

110110
col username for a30
111111
col account_status for a30
@@ -138,7 +138,7 @@ Please refer [here](./provisioning/ords_image.md) for the steps to build ORDS Do
138138
kubectl apply -f cdb_secret.yaml
139139
```
140140

141-
**Note:** In order to get the base64 encoded value for a password, please use the below command like below at the command prompt. The value you get is the base64 encoded value for that password string.
141+
**Note:** In order to get the base64 encoded value for a password, please use the following command like below at the command prompt. The value you get is the base64 encoded value for that password string.
142142

143143
```bash
144144
echo -n "<password to be encoded using base64>" | base64

0 commit comments

Comments
 (0)