Database Reference
In-Depth Information
Managing RAC One Node Database
This section focuses on RAC One Node database administration concepts. You will learn how to extract RAC One
Node database configuration details and identify the predefined candidate server list for instance failover or online
migration. You'll also learn to distinguish the type of database and relocate the database online.
Verifying Configuration Details
Verify the RAC One Node database configuration details after creating the database. The following example extracts
useful information about the RAC One Database configuration:
$ srvctl config database -d RONDB
Database unique name: RONDB
Database name: RONDB
Oracle home: /u01/app/oracle/product/12.1.0/ron
Oracle user: oracle
Spfile: +DG_RONDB/RONDB/spfileRONDB.ora
Password file: +DG_RONDB/rondb/orapwrondb
Domain:
Start options: open
Stop options: immediate
Database role: PRIMARY
Management policy: AUTOMATIC
Server pools: RONDB
Database instances:
Disk Groups: DG_RONDB
Mount point paths:
Services: RONDB_MAIN
Type: RACOneNode
Online relocation timeout: 30
Instance name prefix: RONDB
Candidate servers: rac1,rac2
Database is administrator managed
Let's have a closer look at some of the key configuration elements in the preceding listing.
Type
:
This is one of the vital parameters that require your attention. The parameter helps to
identify the database type: RAC or RAC One Node.
Online relocation timeout
:
Displays the default timeout duration (in minutes) to
complete any ongoing transactions of a session on the instance before it gets terminated on
the local node as part of an online database movement.
•
Typically, when online database relocation is initiated, the instance will wait for
the specified amount of time to allow active transactions to complete before it gets
terminated. If a session is unable to complete all its active transactions within the allotted
time frame, the transaction will then be canceled and the session will be terminated
subsequently. The
-w
parameter provides an option to specify a user-preferred timeout
duration of up to 720 minutes.
