Overview of SRVCTL Use SRVCTL to manage configuration information. You can use SRVCTL commands to add, remove, start, stop, modify, enable, and disable a number of entities, such as databases, instances, listeners, SCAN listeners, services, grid naming service (GNS), and Oracle ASM.
Some SRVCTL operations modify the configuration data stored in the Oracle Cluster Registry (OCR). SRVCTL performs other operations, such as starting and stopping instances, by sending requests to the Oracle Clusterware process (CRSD), which then starts or stops the Oracle Clusterware resources. Usage Information To use SRVCTL, log in to the operating system of a node and enter the SRVCTL command and its options in case-sensitive syntax as described in.
Guidelines for using SRVCTL are:. Only use the version of SRVCTL that is provided with Oracle Database 11 g on Oracle RAC databases that are created or upgraded for Oracle Database 11 g. The version of SRVCTL must be the same as the version of the object (listeners, Oracle ASM instances, Oracle RAC databases and their instances, and services) being managed. To ensure the versions are the same release, issue SRVCTL commands from the Oracle home of the database or object you are managing.
SRVCTL does not support concurrent executions of commands on the same object. Therefore, run only one SRVCTL command at a time for each database, service, or other object. Using Comma-Delimited Lists When specifying a comma-delimited list as part of a SRVCTL command, there should not be any spaces between the items in the list. For example: srvctl add database -g serverpool1,serverpool3 When you specify a comma-delimited list in a Windows environment, you must enclose the list in double quotation marks ( '). You can enclose a comma-delimited list in double quotation marks in a Linux or UNIX environment but they will be ignored. Specifying a Continuation of Command Line Entries If you are entering a SRVCTL command, and you want to continue the input on a new line, then you can use the operating system continuation character.
In Linux, this is the backslash ( ) symbol. SRVCTL Command Feedback A SRVCTL command that produces no output is a successful command. Not all SRVCTL commands return a message when it completes, successfully. However, if a SRVCTL command fails, then it always returns an error message. Table A-1 String Restrictions for SRVCTL Object Names Object Type Character Set Limitations Case Sensitive? Maximum Length dbdomain Alpha-numeric characters, underscore , and number sign (#) 128 characters dbuniquename Alpha-numeric characters, underscore , number sign (#), and dollar sign ($); the first 8 characters must be unique because those characters are used to form instance names for policy-managed databases No 30 characters but the first 8 characters must be unique relative to any other database in the same cluster diskgroupname Naming disk groups have the same limitations as naming other database objects. Summary of Tasks for Which SRVCTL Is Used SRVCTL is used to manage databases, instances, cluster databases, cluster database instances, Oracle ASM instance and disk groups, services, listeners, or other clusterware resources.
Cluster Database Configuration Tasks. Add, modify, and delete cluster database configuration information. Add an instance or a service to, and delete an instance or service from the configuration of a cluster database. Move instances and services in a cluster database configuration and modify service configurations. Set and unset the environment for an instance or service in a cluster database configuration.
Set and unset the environment for an entire cluster database in a cluster database configuration. Privileges and Security To use SRVCTL to change your Oracle RAC database configuration, log in to the operating system as the software owner of the home that you want to manage.
For example, if different users installed Oracle Database and the Oracle Grid Infrastructure, then log in as the database software owner (for example, oradb) to manage databases and log in as the Oracle Grid Infrastructure software owner (for example, oraasm) to manage the Oracle ASM instances. Users who are members of the OSDBA operating system group can start and stop the database. To stop and start an Oracle ASM instance, you must be a member of the OSASM operating system group. To create or register objects such as listeners, Oracle Notification Services, and services, you must be logged in to the operating system as the software owner of the Oracle home. The objects you create or register for that Oracle home will run under the user account of the owner of the Oracle home.
Databases run as the database installation owner of the home from which they run. To perform srvctl add operations on any object, you must be logged in as the Oracle account owner of the home on which the object runs. For some SRVCTL commands, on Linux and UNIX systems, you must be logged in as root, and on Windows systems, you must be logged in as a user with Administrator privileges to run them. In this appendix, those commands are preceded by the root prompt ( #) in the command examples.
SRVCTL Command Reference SRVCTL Command Syntax and Options SRVCTL commands, object names, and options are case sensitive. Database, instance, listener, and service names are case insensitive and case preserving. You cannot create listener names that differ only in case, such as LISTENER and listener. SRVCTL uses the following command syntax: srvctl command object options In SRVCTL syntax:. command is a verb such as start, stop, or remove. object is the target or object on which SRVCTL performs the command, such as database or instance. You can also use object abbreviations.
options extend the use of a preceding command combination to include additional parameters for the command. For example, the -i option indicates that a comma-delimited list of preferred instance names follows; sometimes the -i option only permits one value and not a list of names. The -n option indicates that a node name or a comma-delimited list of node names follows. Do not use spaces between the items in a comma-delimited list. Table A-3 Summary of SRVCTL Commands Command Description Adds node applications, databases, database instances, Grid Naming Service (GNS), listeners, single client access names (SCANs), Oracle ASM instances, server pools, services, or virtual IPs (VIPs). Lists the configuration for GNS, the node applications, database, Oracle ASM instance, or service. Converts a database either to or from an Oracle Real Application Clusters One Node (Oracle RAC One Node) database.
Disables the database, database instance, GNS, Oracle ASM instance, or service. Downgrades the database configuration after you manually downgrade the database. Enables the database, database instance, GNS, Oracle ASM instance, or service. Displays the environment variable in the configuration for the node applications, database, VIP, listener or Oracle ASM. Modifies the node applications, database, database instance, GNS, or service configuration. Relocates GNS, OC4J, SCANs, Oracle RAC One Node databases, servers, and VIPs from one node to another. Removes the node applications, database, database instance, GNS, Oracle ASM instance, or service.
Sets the environment variable in the configuration for the node applications, database, VIP, listener or Oracle ASM. Starts the node applications, database, database instance, GNS, Oracle ASM instance, or service.
Displays the status of the node applications, database, database instance, GNS, Oracle ASM instance, or service. Stops the node applications, database, database instance, GNS, Oracle ASM instance, or service. Unsets the environment variable in the configuration for the node applications, database, VIP, listener or Oracle ASM.
Upgrades the configuration to the version of the software on which it is running. SRVCTL Objects Summary lists the keywords that can be used for the object portion of SRVCTL commands. You can use either the full name or the abbreviation for each object keyword. The Purpose column describes the object and the actions that can be performed on that object. Table A-4 Object Keywords and Abbreviations Object Keyword Purpose Cluster Verification Utility cvu To add, modify, list the configuration of, enable, disable, start, stop, relocate, obtain the status of, and remove CVU resources. Database database To add, modify, manage environment variables for, list the configuration of, enable, disable, start, stop, and obtain the status of databases, and also to upgrade, downgrade, and remove database configuration information about databases.
Disk Group diskgroup To add, modify, list the configuration of, enable, disable, start, stop, obtain the status of, and remove Oracle ASM disk groups File system filesystem To add, modify, list the configuration of, enable, disable, stop, start, obtain the status of, and remove disk devices for Oracle Automatic Storage Management Cluster File System (Oracle ACFS). Grid Naming Service (GNS) gns To add, modify, list the configuration of, enable, disable, stop, start, obtain the status of, and remove a GNS daemon.
Home directory (for patching) home To start, stop, and obtain the status of all clusterware resources related to a Home directory.f Instance instance To add, modify, enable, disable, start, stop, obtain the status of, and remove database instances. Listener listener To add, modify, manage environment variables for, list the configuration of, enable, disable, start, stop, obtain the status of, and remove listeners. Network network To add, modify, list the configuration of, and remove a non-default Network. Note: The node applications object, and the and commands also manage the default network.
Node applications nodeapps To add, modify, manage environment variables for, list the configuration of, enable, disable, start, stop, obtain the status of, and remove node applications. Oracle Automatic Storage Management asm To add, modify, manage environment variables for, list the configuration of, enable, disable, start, stop, obtain the status of, and remove Oracle ASM instances. Add The srvctl add command adds the configuration and the Oracle Clusterware applications to OCR for the cluster database, named instances, named services, or for the named nodes. To perform srvctl add operations, you must be logged in as the database administrator and be the Oracle account owner on Linux and UNIX systems, or you must be logged on as a user with Administrator privileges on Windows systems. When adding an instance, the name that you specify with -i must match the ORACLESID parameter.
The database name given with -d dbuniquename must match the DBUNIQUENAME initialization parameter setting. If DBUNIQUENAME is unspecified, then match the DBNAME initialization parameter setting. The default setting for DBUNIQUENAME uses the setting for DBNAME.
Also, the domain name given with -m dbdomain must match the DBDOMAIN setting. Table A-5 srvctl add Summary Command Description Adds Oracle ASM instances Adds the Cluster Verification Utility resource to an Oracle Clusterware configuration Adds a database and configuration Adds a volume to Oracle ACFS Adds the Grid Naming Service (GNS) to a cluster Adds one or more instance and configuration Adds a listener to the node Adds a DHCP or static network Adds node applications Adds OC4J instances Adds Oracle Notification Service daemons Adds SCAN VIPs Adds SCAN listeners Adds services Adds a server pool to a cluster Adds a VIP to a node. Srvctl add filesystem Adds a disk device to Oracle ACFS.
This command needs to be run only one time from the Oracle Grid Infrastructure home. An Oracle ACFS file system resource is typically created for use with application resource dependency lists.
For example, if an Oracle ACFS file system is configured for use as an Oracle Database home, then a resource created for the file system can be included in the resource dependency list of the Oracle Database application. This will cause the file system and stack to be automatically mounted as a result of the start action of the database application.
Table A-11 srvctl add listener Options Option Description -l listenername Specify a listener name. If this option is not specified, the default name of LISTENER is used.o oraclehome Specify an Oracle home for the cluster database. If you do not include this option, then it uses the Grid home by default.p 'TCP: portlist /IPC: key /NMP: pipename /TCPS: sport /SDP: port Protocol specifications for the listener.
Portlist is a comma-delimited list of TCP ports or listener endpoints.k networknumber The optional network number from which VIPs are obtained. If not specified, the VIPs are obtained from the same default network from which the nodeapps VIP is obtained.s Indicates you want to skip the checking of ports. Table A-14 srvctl add ons Options Option Description -l onslocalport The Oracle Notification Service daemon listening port for local client connections Note: The local port and remote port must each be unique.r onsremoteport The Oracle Notification Service daemon listening port for connections from remote hosts Note: The local port and remote port must each be unique.t host: port, host: port.
A list of comma-delimited host: port pairs of remote hosts that are part of the Oracle Notification Service network but are not part of the Oracle Clusterware cluster Note: If port is not specified for a remote host, then onsremoteport is used.v Verbose output. Table A-18 srvctl add srvpool Options Option Description -g serverpool The name of the server pool.i importance The importance of the server pool (default is 0).l minsize The minimum size of the server pool (default is 0).u maxsize The maximum size of the server pool.
The default value is -1, which indicates that the size is unlimited.n ' nodenames' A comma-separated list of candidate node names enclosed in double quotation marks ( '). The server pool will only include nodes on the candidate list, but not all nodes on the candidate list will necessarily be in the server pool.f Add the server pool, even if requires stopping resources in other server pools. Note: If you disabled an object for which you are trying to obtain configuration information using the srvctl disable object -n nodename command, then bear in mind that using the srvctl disable object -n nodename command on a per-node basis in your cluster to disable an object throughout the cluster is not the same as globally disabling an object using the srvctl disable object command without the -n option. In the former case, the srvctl config object command may report that the object is still enabled. Table A-24 srvctl config gns Options Option Description -a Print detailed configuration information.d Display the subdomain served by GNS.k Display network on which GNS is listening.m Display the port on which the GNS daemon is listening for multicast requests.n nodename Display the configuration information for GNS on the specified node.p Display the port that the GNS daemon uses to communicate with the DNS server.s Display the status of GNS.V Display the version of GNS.q name Query GNS for the records belonging to a name.l List all records in GNS.v Verbose output.
Table A-29 srvctl convert database Options Option Description -d dbuniquename Unique name for the database. Note: If you specify a noncluster database, then command returns an error instructing you to use rconfig to convert the noncluster database to Oracle RAC or Oracle RAC One Node.c RACONENODE RAC The type of database to which you are converting, either Oracle RAC One Node or Oracle RAC. Note: If there is an ongoing or failed online database relocation, then the command returns an error instructing you to first complete or abort the online database relocation and then rerun the command.i instancename Instance name prefix for Oracle RAC One Node databases.
The default value for this option is the first 12 characters of the global unique name of the database. Notes:. You can use this option only when converting from an Oracle RAC database to an Oracle RAC One Node database. In order for the converted instance to come online, you must restart the database using the srvctl stop/start database commands.w timeout Online database relocation timeout, in minutes, for Oracle RAC One Node databases.
The default is 30.n nodename Name of the node for administrator-managed Oracle RAC database. The default is the first candidate. Note: If you do not specify a node name or you specify a node name where the database is not running, then the command returns an error instructing you specify the correct node. Example An example of this command is: $ srvctl convert database -d myDB -c RACONENODE -i instancename.
Disable Disables a specified object (cluster database, database instance, Oracle ASM instance, or service). Use the srvctl disable command when you must shut down an object for maintenance. The disabled object does not automatically restart.
When you issue the disable command, the object is disabled and unavailable to run under Oracle Clusterware for automatic startup, failover, or restart. Additionally, you cannot run the srvctl start command on a disabled object until you first re-enable the object. If you specify -i instancename or -n nodename, then SRVCTL only disables the object on the specified instance or node.
If you do not specify -i instancename or -n nodename, then the disable action applies to the object that you specified, globally, on all nodes in the cluster. Any object you disable globally is also disabled on any nodes you add to the cluster in the future. Disabling an object globally is not the same as disabling an object locally on each node in the cluster. For example, if you disable a database on several nodes, individually, in a cluster, then, when you run the srvctl start database command, the database starts only on nodes where the database is enabled. If, however, you disable the database globally, then the srvctl start database is rejected because the database is disabled, clusterwide. Note:.
To manage Oracle ASM on Oracle Database 11 g release 2 (11.2) installations, use the SRVCTL binary in the Oracle Grid Infrastructure home for a cluster (Grid home). If you have Oracle RAC or Oracle Database installed, then you cannot use the SRVCTL binary in the database home to manage Oracle ASM. Oracle ASM is part of the Oracle Clusterware stack and when OCR and voting disks are stored on Oracle ASM, then Oracle ASM starts when OHASD starts the Oracle Clusterware stack. The srvctl disable asm command does not prevent the Oracle ASM instance managed by OHASD from starting.
Oracle ASM, therefore, starts as needed by the Oracle Clusterware stack. The srvctl disable asm command prevents the Oracle ASM Oracle Clusterware proxy resource, and any resources that depend on it, from starting. So, the command prevents Oracle Clusterware-managed objects, such as databases, disk groups, and file systems that depend on Oracle ASM, from starting.
For example, the srvctl start database diskgroup filesystem command fails to start any of those objects on nodes where the Oracle ASM Oracle Clusterware proxy resource is disabled. The command also prevents the srvctl start asm command from starting Oracle ASM on remote nodes. Table A-41 srvctl disable service Options Option Description -d dbuniquename Unique name for the database -s 'servicenamelist' Comma-delimited list of service names, or a single service name -i instancename The name of the instance that you want to disable the service for. Note: Use this option with administrator-managed databases Note: This option is available only with Oracle Clusterware and Oracle RAC.n nodename The name of the node on which to disable the service Note: Use this option with policy-managed databases Note: This option is available only with Oracle Clusterware and Oracle RAC. Table A-55 srvctl enable service Options Option Description -d dbuniquename Unique name for the database -s servicenamelist Comma-delimited list of service names -i instancename Name of the database instance where you want the service to run Use this option for administrator-managed databases Note: This option is available only with Oracle Clusterware and Oracle RAC.n nodename Name of the node where you want the service to run Use this option for policy-managed databases Note: This option is available only with Oracle Clusterware and Oracle RAC.
Create Oracle RAC and Oracle RAC ONE Node Database using dbca in Oracle 11g R2 (11.2.0.2) Create Oracle RAC and Oracle RAC ONE Node Database using dbca in Oracle 11g R2 (11.2.0.2) In this article we will look at creating Oracle RAC and RAC ONE Node database using dbca. For install/upgrade to Oracle 11.2.0.2 look. Create Oracle RAC ONE Node database using dbca Start dbca and select Oracle RAC One Node database and press Next to continue. Select ‘Create a Database’ and press Next to continue. Select Custom Database and press Next to continue. Select Admin-Managed, enter database global name, SID prefix and service name and press Next to continue. DBCA will create one database with one instance which can be migrated across the nodes selected.
Enter and confirm the password(s) and press Next to continue. Specify storage type and storage location and press Next to continue. Specify the Fast recovery area (formerly flash recovery area) and press Next to continue. Select the database components and component location and press Next to continue. Select the init parameters. In this case use AMM is selected and the memory size is specified. Press Next to continue.
Keep the defaults and press Next to continue. Select the options for dbca to generate a template and generation scripts and press Next to continue. Review the summary and press OK to continue.
Wait for the dbca to complete. Optionally choose the password management to change the passwords and unlock the accounts and once done press Exit to exit from dbca. Create Oracle RAC database using dbca Start dbca and select Oracle RAC database and press Next to continue.
Select ‘Create a Database’ and press Next to continue. Select General Purpose or Transaction Processing Database and press Next to continue. Select Admin-Managed, enter database global name, SID prefix and press Next to continue. DBCA will create one database with two instances on each node respectively. Select Configure Enterprise Manager and select Automatic Maintenance Tasks Tab.
Select Enable automatic maintenance tasks and press Next to continue. Enter and confirm the password(s) and press Next to continue. Specify storage type and storage location and press Next to continue. Specify the Fast recovery area (formerly flash recovery area) and press Next to continue. Select the database components and component location and press Next to continue. Select the init parameters.
In this case use AMM is selected and the memory size is specified. Press Next to continue.
Keep the defaults and press Next to continue. Select the options for dbca to generate a template and generation scripts and press Next to continue. Review the summary and press OK to continue. Wait for the dbca to complete.
Wait for the dbca to complete. Wait for the dbca to complete. Optionally choose the password management to change the passwords and unlock the accounts and once done press Exit to exit from dbca.
About Guenadi Jilevski is a Senior Oracle Professional (OCP 7, 8, 8i, 9i, 10g, 11g, 12c OCE 10gR2 RAC, OCE Oracle RAC 11gR2 and Grid Infrastructure Administrator, Oracle Exadata 11g Certified Implementation Specialist,Oracle GoldenGate 10g/11g Certified Implementation Specialist and OCM 9i, OCM 11g) with more than 20 years of industrial experience in high end Oracle technology starting with Oracle RDBMS version 6 up to 11g. He has been involved with multi platform High Availability Solutions starting with OPS and Veritas and Sun cluster as well as complex multiple node RAC 9i, 10g and 11g implementations on AIX, Linux, Solaris and HP. He has experience in deploying disaster recovery solutions with standby databases compliant to Oracle MAA and third party solutions such as Shareplex and Goldengate.
As a former employee of Oracle Corporation Advanced Technology Solutions Consulting Practice in Americas, Guenadi has been involved in multiple visible high end projects for RAC enabling EBS, Peoplesoft, Siebel ERP applications, end to end performance tuning, architectured High Availability and Disaster Recovery solutions to name a few. Presently he is working as A Senior Oracle Consultant in EMEA. Guenadi Jilevski is Oracle OCP 7, 8, 8i, 9i, 10g, 11g, 12c OCE 10gR2 RAC, OCE Oracle RAC 11gR2 and Grid Infrastructure Administrator, Oracle Exadata 11g Certified Implementation Specialist,Oracle GoldenGate 10g/11g Certified Implementation Specialist and Oracle OCM9i, OCM 11g, Teradata Certified DBA, Informix Certified DBA.
Manually Creating a RAC Database ( RAC Database Creation without DBCA) The article assumes that you already have a clustered ASM installation up and running on Linux, so let's get going. My database is called DEMO, instances are DEMO1 and DEMO2.
. Oracle Database Configuration Assistant (DBCA) is a tool for creating and configuring an Oracle database. Oracle recommends that you use Oracle Database Configuration Assistant (DBCA) to create your Oracle RAC database, because preconfigured databases optimize your environment for features such as the server parameter file (SPFILE), and automatic undo management. If your system has an Oracle Database 10 g or 11 g installation, and you install Oracle Database 12 c Release 1 (12.1) either to coexist with or to upgrade the Oracle Database 10.1, 10.2, 11.1, or 11.2 installation, then most installation types automatically migrate the existing Oracle Database listener to the 12 c Release 1 (12.1) Oracle home. Use Cluster Verification Utility (CVU) to verify that your system is prepared for configuration changes.
To create a database with DBCA, you must have run the Oracle Net Configuration Assistant (NETCA) to configure your Oracle Net listener.ora file. There are different configuration processes you must perform when installing and create an Oracle RAC database that uses Direct NFS (dNFS) for the database files. If you have selected to install only the Oracle RAC software on cluster nodes, then you can use Oracle Database Configuration Assistant (DBCA) to configure Oracle RAC One Node.
Excel 2010 english version. Deleting an Oracle RAC database using Oracle Database Configuration Assistant (DBCA) involves deleting the database and database objects. During installation, if you select a multitenant container database (CDB), and configure pluggable databases (PDBs), then Oracle recommends that you add services to the PDBs after installation. Oracle recommends that you use Oracle Database Configuration Assistant (DBCA) to create your Oracle RAC database, because preconfigured databases optimize your environment for features such as the server parameter file (SPFILE), and automatic undo management. DBCA enables you to create both policy-managed and administrator-managed databases. With DBCA, you can create site-specific tablespaces as part of database creation.
If you have data file requirements that differ from those offered by DBCA templates, then create your database with DBCA and modify the data files later. You can also run user-specified scripts as part of your database creation process. DBCA also configures your Oracle RAC environment for various Oracle high availability features, such as cluster administration tools.
DBCA also starts any database instances required to support your defined configuration. You can use DBCA to create a database from templates supplied by Oracle, or from templates that you create. The templates contain settings optimized for a particular type of workload. Oracle ships templates for the following two workload types:. General purpose or transaction processing. Data warehouse For more complex environments, you can select the Custom Database option.
This option does not use templates and results in a more extensive interview, which means that it takes longer to create your database. Click Show Details to see the configuration for each type of database. Keane the night sky lyrics.
Select the template suited to the type of workload your database will support. If you are not sure which to choose, then select the default General Purpose or Transaction Processing template.
If your system has an Oracle Database 10 g or 11 g installation, and you install Oracle Database 12 c Release 1 (12.1) either to coexist with or to upgrade the Oracle Database 10.1, 10.2, 11.1, or 11.2 installation, then most installation types automatically migrate the existing Oracle Database listener to the 12 c Release 1 (12.1) Oracle home. During migration, the upgrade process configures and starts a default Oracle Net listener using the same TCP/IP port as the existing listener, with the IPC key value.
During the Oracle Clusterware upgrade, the default listener ( LISTENER NODENAME) was migrated to the Oracle Grid Infrastructure home (Grid home). DBCA always uses the default listener. The listener migration process stops the listener in the existing Oracle home, and restarts it in the new Oracle home. If the database was using the default listener ( LISTENER NODENAME), then Oracle Net Configuration Assistant (NETCA) migrates the listener automatically to the Grid home as part of the Oracle Grid Infrastructure upgrade. If the database was using a nondefault listener, then Database Upgrade Assistant (DBUA) migrates the nondefault listener to the Oracle Database home. The global database name for an Oracle RAC database must meet the naming requirements.
The global database name consists of the database name and the domain name. Before starting Oracle Database Configuration Assistant (DBCA) to configure an Oracle RAC database, you must install Oracle Grid Infrastructure for a cluster, and configure shared storage areas for Oracle RAC files. When you use Oracle Database Configuration Assistant to create an Oracle database or an Oracle RAC database, and specify an Oracle Home User during installation, then you need to enter the password for this user. The global database name for an Oracle RAC database must meet the naming requirements.
The global database name consists of the database name and the domain name. Choose a name for your database that has the following characteristics:. Up to 30 characters in length.
Begins with an alphabetic character. Determine the domain name portion of the global database name, that satisfies these requirements:. Is up to 128 characters in length. Contains only alphabetic and numeric characters, and the period (.) character. Determine the ORACLESID values for each instance.
Storage administration tasks require the SYSASM system privileges, which are granted to members of the OSASM operating system group. This group may not be the same as the OSDBA group, whose members are granted the SYSDBA system privileges.
On Windows-based systems, if you plan to use Oracle ASM storage, then before you use DBCA to create a database, you must perform the following steps:. Create logical partitions without primary partitions on the disk drives.
Delete the drive letters for these partitions on all nodes. You can either start the Oracle Database Configuration Assistant (DBCA) utility from the command line or from the Windows Start menu. When you start DBCA, it automatically shows options for Oracle RAC if it detects from the central Oracle Inventory that the Oracle Home is enabled for Oracle RAC. You can choose to use either Oracle ASM Disk groups or a shared file system as storage for Oracle RAC database files. Set the CLUSTERDATABASEINSTANCES parameter to the expected number of instances. Review this information to understand about Oracle Database Configuration Assistant (DBCA) actions during Oracle RAC database creation.
You are prompted to enter the password for the Oracle Home User if you are administering an Administrator-managed Oracle RAC database and chose not to store the password in an Oracle Wallet. To start DBCA from the command line:.
Open a command prompt window. Navigate to the Oraclehome bin directory. Enter the command dbca. To start DBCA from the Start menu:. Click Start.
Select Programs. Under Programs, select Oracle - Oraclehome name. Select Configuration and Migration Tools. Select Database Configuration Assistant. After you have started DBCA, to create an Oracle RAC database, you select the following. When you start DBCA, it automatically shows options for Oracle RAC if it detects from the central Oracle Inventory that the Oracle Home is enabled for Oracle RAC.
If DBCA does not detect the Oracle home as an Oracle RAC home, check that the OUI inventory is correctly located in the directory C: Program Files Oracle Inventory, and that the oraInventory file is not corrupted. Also, perform clusterware diagnostics by using the following CVU command syntax: Gridhome bin cluvfy cluvfy.bat stage -post crsinst -n nodelist When using DBCA, if nodes that are part of your cluster installation do not appear on the Node Selection page, then run the Opatch lsinventory command to perform inventory diagnostics. Also use CVU to perform clusterware diagnostics. Set the CLUSTERDATABASEINSTANCES parameter to the expected number of instances. On the Initialization Parameters page, if you intend to add more nodes in your cluster than you have during the current Oracle Database Configuration Assistant session, then click All Initialization Parameters, and change the parameter CLUSTERDATABASEINSTANCES to the total number of nodes that you plan to add to the cluster.
In addition, if you click All Initialization Parameters, note that if your global database name is longer than 8 characters, then the database name value (in the DBNAME parameter) is truncated to the first 8 characters, and the DBUNIQUENAME parameter value is set to the global name. Review this information to understand about Oracle Database Configuration Assistant (DBCA) actions during Oracle RAC database creation. After you respond to DBCA prompts, review the Summary dialog information and click OK, DBCA performs several actions. Creates an Oracle RAC database, and its instances. Creates the Oracle RAC data dictionary views. Starts the Oracle services if you are on a Windows-based platform. Starts the Oracle Clusterware high availability services.
Starts the database instances across cluster nodes. In a software-only installation you install the Oracle Database software but do not create a database as part of the installation process.
Oracle Automatic Storage Management Configuration Assistant (ASMCA) enables you to create an Oracle Automatic Storage Management Cluster File System (Oracle ACFS) mount point which is used in the 'common file location' step of Oracle Database Configuration Assistant (DBCA). Use Oracle Database Configuration Assistant (DBCA) to create an Oracle Real Application Clusters (Oracle RAC) database that uses Direct NFS for datafile storage. You must manually enable the Direct NFS option after installing the Oracle Database software. Now you have configured the mount point using Direct NFS, you can remove the Oracle Automatic Storage Management Cluster File System (Oracle ACFS) mount point using Oracle Automatic Storage Management Configuration Assistant (ASMCA). In a software-only installation you install the Oracle Database software but do not create a database as part of the installation process.
Start Oracle Universal Installer (OUI) by running setup.exe from the software staging location. On the Select Installation Option screen select Install database software only. On the Grid Installation Options screen, select the product to install, for example 'Oracle Real Application Clusters database software installation.'
. Select the nodes on which you want to install the database software.
Clone A Rac Database Using Em
Choose the languages to use with the installed software. Select the database edition to install. For Oracle RAC databases, you must choose Enterprise Edition. Specify an Oracle Home user, or choose to use a Windows-built in user for the software installation owner. On the Specify Installation Location screen, enter a path to the Oracle base directory and the software location (Oracle home directory). On the Summary screen, verify your selections, then click Install.
For the Configuration Type, you can choose either Policy-Managed or Administrator-Managed. Select the template most appropriate for the type of database you want to create. For the next four screen, make selections and provide information that best meet your business requirements.
Perform the following steps on the Storage Locations screen:. Select File System for the Database files Storage type. Select the option Use Common Location for All Database Files. In the File location field, specify the location of the mount point you created in ' for example, C: oradatamnt. On the Specify Database Options screen, choose any additional configuration you want for your database. On the Initialization Parameters screen, use the default settings, or provide customized values for the initialization parameters. On the Creation Options screen, select the option Generate Database Creation Scripts.
Specify a destination directory for the script file, or use the default value. After the Prerequisite checks complete, on the Summary screen, minimize the installation window. DO NOT click Finish at this point. Enable the Direct NFS option as described in '. Remove the virtual mount point you created with Oracle Automatic Storage Management Configuration Assistant (ASMCA), as described in '. Create all the directories needed locally on each node as well as on the NFS server.
When you click OK, DBCA continues the operation and deletes all the associated instances for this database. DBCA also removes the parameter files and password files.
At this point, you have accomplished the following:. Deleted the selected Oracle RAC database from the cluster. Deleted the selected Oracle RAC Database Oracle services on Windows-based platforms. Deleted high availability services assigned to the Oracle RAC database. Deleted the Oracle Net configuration for the Oracle RAC database. Deconfigured Oracle Enterprise Manager for the Oracle RAC database. Deleted the OFA directory structure for that Oracle RAC database from the cluster.
Deleted the Oracle RAC database data files. If you do not add services to PDBs, and then the Oracle RAC One Node CDB fails over to another node, or you manually relocate the CDB to another node, then by default, all PDBs associated with that CDB that do not have registered services are restarted in MOUNTED state. PDBs are opened in Read Write mode after failover or relocation only after you have configured the PDBs to have associated services.
If you have not associated services to PDBs, then the PDBs remains in MOUNTED state when the CDB instance restarts. Use the following srvctl command syntax, where cdbname is the name of the CDB, servicename is the name of the service, and pdbname is the name of the PDB.
Even if you are managing a non-RAC database, in 11g, it is recommended to use “srvctl” commands to start and stop the database. But, if the database is not created using DBCA or not upgraded using DBUA, the database will not be registered in the “” configuration automatically. Oracle Restart monitors the services registered and restarts if there is an abnormal end or can stop and start the databases during server reboot. Please read to learn more about Oracle Restart.
When the database is not configured in Oracle Restart, and if you attempt to start or query the configuration using srvctl, you will see this error. PRCR - 1001: Resource ora. Db does not exist You may add the database to Oracle Restart configuration using the minimal set of parameters. For complete set of options and various srvctl options, please refer to. Here adding the database information with database name (-d option), the Oracle home location (-o option) and database parameter file (-p option).
In the examples below, variables like $ORACLEHOME, $TNSADMIN are used, they are setup prior. If the variables are not defined, use full path of the directory or name.