Srvctl Start Database open mode and role modification with Examples

In Oracle Grid Infrastructure, the srvctl command is used to manage Oracle Real Application Clusters (RAC) and Automatic Storage Management (ASM) components, including Oracle databases. To modify the open mode of an Oracle database using srvctl, you can follow these steps.

Step 1: Connect to the Server

Connect to the server where the database is located using SSH or a terminal session.

Step 2: Log in as the Oracle Software Owner

Log in as the Oracle software owner (typically, "oracle") or a user with the necessary privileges to modify the open mode of the database.

su - oracle

Step 3: Modify the Open Mode

Use the srvctl modify database command to change the open mode of the database. The command syntax is as follows:

srvctl modify database -db <DBUniqueName> -startoption <open_mode> -role <role>

-db <DBUniqueName>: Replace <DBUniqueName> with the unique name of your Oracle database.

-startoption <open_mode>: Specify the desired open mode for the database. The available options are "mount" (to start the database in a mounted state) and "read-write" (to open the database for read-write operations).

-role <DB role>: Role of the database in an Oracle Data Guard configuration (PRIMARY, PHYSICAL_STANDBY, LOGICAL_STANDBY, or SNAPSHOT_STANDBY)

Short Form	Long Form
-d	-db
-s	-startoption
-r	-role

Example 1: Modifying the Database to Mount Mode

To modify the database to mount mode, use the following command:

srvctl modify database -db FOADB -s mount

This command changes the database named "FOADB" to mount mode, making it available for various administrative tasks, such as applying redo logs or performing backups.

Example 2: Modifying the Database to Read-Write Mode

To modify the database to read-write mode, use the following command:

srvctl modify database -db FOADB -s read-write

This command opens the database "FOADB" for read-write operations. Be cautious when using this option, as read-write mode allows data modifications and should only be used when necessary.

Step 4: Verify the Database State

After running the srvctl command, you can verify the state of the database by using the srvctl status database command:

srvctl status database -db <DBUniqueName>

-db <DBUniqueName>: Replace <DBUniqueName> with the unique name of your database.

Example:

srvctl status database -db FOADB

This command displays the current state of the "FOADB" database, indicating whether it's in mounted or read-write mode.

If you like please follow and comment

Comments

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...

Rename a PDB in Oracle Database Multitenant Architecture in TDE and Non TDE Environment

Rename a PDB in Oracle Database Multitenant Architecture I am sharing a step-by-step guide to help you rename a PDB. This approach uses SQL commands. Without TDE or encryption Wallet Initial Check Check the Current Database Name and Open Mode: SQL > SELECT NAME, OPEN_MODE FROM V$DATABASE; NAME OPEN_MODE --------- -------------------- BEECDB READ WRITE List Current PDBs: SQL > SHOW PDBS; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 FUAT READ WRITE NO We need to RENAME FUAT to BEE Steps to Rename the PDB Step 1: Export ORACLE_SID Set the Oracle SID to the Container Database (CDB): export ORACLE_SID=BEECDB Step 2: Verify Target PDB Name Availability If the target PDB name is different from the current PDB name, ensure no service exists with the target PDB name. Run SQL to Check Exi...

foalabs

Search This Blog