- 论坛徽章:
- 0
|
Step-By-Step Installation of RAC on Windows NT/2000
--------------------------------------------------------------------------------
Purpose
This document will provide the reader with step-by-step instructions on how to install and configure an Oracle9i Real Application Clusters (RAC) database on a Windows NT or 2000 cluster. For additional explanation or information on any of these steps, please see the references listed at the end of this document.
Disclaimer: If there are any errors or issues prior to step 3.2, please contact your cluster hardware vendor’s support.
1. Configuring the Cluster Hardware
1.1 Minimal Hardware List / System Requirements
1.2 Installing the Shared Disk Array
1.3 Installing Cluster Interconnect and Public Network Hardware
1.4 Checking the Temp and Tmp Directories Defined Within Windows
1.5 Checking Access to Other Nodes Within Windows
2. Pre-Installation Steps: Configuring the Shared Disks
2.1 Logical Partition Configuration
2.2 Oracle Cluster File System Configuration
2.3 Overview of Creating Partitions in Windows
2.4 Verify Changes Are Visible on All Nodes in the Cluster
3. Configure the Cluster using the Oracle OSD Cluster software
3.1 Perform a Final Cluster Check
3.2 Installing the Oracle OSD Software
3.2.1 Installing OSD for Logical Partitions Configurations
3.2.2 Installing OSD for OCFS Configurations
3.3 Check the Cluster Install on All Nodes
4. Using the Oracle Universal Installer for Real Application Clusters
5. Create a RAC Database using the Oracle Database Configuration Assistant
6. Using SRVCTL for the Administration and Maintenance of a RAC Database
7. References
--------------------------------------------------------------------------------
1. Configuring the Cluster Hardware
1.1 Minimal Hardware List / System Requirements
Certified cluster configurations are listed in Note 184875.1. Note that there are different configurations for Windows NT and 2000. Please consult this listing for specific Hardware/Software/Variance information provided by your Cluster vendor. In general, each node will require the following:
1.1.1. Hardware:
External shared hard disks
Certified hardware configurations
1.1.2. Software:
Certified vendor-supplied operating system dependent clusterware layer (Step 1.3)
Oracle Operating System Dependent (OSD) clusterware layer (Step 3.1)
1.1.3. RAM:
256 MB for each instance running on that node
The above information is contained within the Oracle9i Database Installation Guide for Windows. See the section “Oracle9i Database System Requirements” for additional information on hardware/system sizing for other options of the RDBMS.
1.2 Installing Shared Disk Array
Follow the procedures provided by your Cluster vendor. Verify that all nodes can view the shared partitions within the Windows NT Disk Administrator or within the Disk Manager in Windows 2000.
1.3 Installing Cluster Interconnect and Public Network Hardware
Follow the procedures provided by your Cluster vendor. In general, you will setup the following Hostname and IP information before running the Cluster setup:
1.3.1. Setup the External and Internal Network Interface Cards (NIC):
Within the Network settings of Windows, create at least two entries for the NICs you have installed.
When assigning the Bindings of the NICs within the Windows Networking Properties, ensure that the Public IP is listed at the top for all settings. The Private NIC(s) should be listed below the public NIC settings. You can verify this at the command prompt by running the command ipconfig /all to verify that the public IP address is listed first.
It is strongly recommended that a network switch is used for the interconnect between nodes rather than a crossover cable. Most cluster hardware vendors will have this as a requirement.
1.3.2. Resolution of External and Internal Hostnames:
Ensure that the External or Public Hostnames are defined in your Directory Network Services (DNS) and that the correct IP addresses resolve for all nodes in the cluster.
Ensure that the Internal or Private Hostnames are defined in the HOST file on all nodes of the cluster. This file is located in the WINDOWS_HOME\System32\drivers\etc directory.
Test your cluster configuration by pinging the hostnames from each node and check for proper names resolution.
1.4 Checking the Temp and Tmp Directories Defined within Windows
To install properly across all nodes, the Oracle Universal Installer will need to use the temporary folders defined within Windows. The TEMP and TMP folders should be the same across all nodes in the cluster. By default these settings are defined as %USERPROFILE%\Local Settings\Temp and %USERPROFILE%\Local Settings\Tmp in the Environment Settings of My Computer. It is recommended to explicitly redefine these as WIN_DRIVE:\temp and WIN_DRIVE:\tmp ; for example: C:\temp and C:\tmp.
1.5 Checking Access to Other Nodes Within Windows
To install and perform administrative tasks, Oracle Corporation recommends using the same username and password on each node in a cluster, or a domain username with administrative privileges on all local nodes. All nodes must be in the same domain.
Ensure that each node has administrative access to all these directories within the Windows environment by running the following at the command prompt:
NET USE \\host_name\C$
where host_name is the public network name for the other nodes. If you plan to install the ORACLE_HOME onto another drive location than C, check that administrative share as well.
For example, if your WIN_HOME is on the C drive and you were installing the ORACLE_HOME onto the E drive of all nodes, you would run the following from a command prompt on node 1 of a four-node cluster:
NET USE \\node2\C$
NET USE \\node3\C$
NET USE \\node4\C$
NET USE \\node2\E$
NET USE \\node3\E$
NET USE \\node4\E$
You would then repeat these commands on all nodes within the cluster. If the following appears for each command, the privileges are correct:
The command completed successfully.
If you receive errors, resolve these within the Windows environment before proceeding.
Back to top
--------------------------------------------------------------------------------
2. Pre-Installation Steps: Configuring the Shared Disks
If you are installing Oracle9i Release 1 (9.0.1.0.0), you must use Logical Partitions (otherwise known as RAW Partitions) for the shared disks. Please proceed to section 2.1 Logical Partitions Configuration.
If you are installing Oracle9i Release 2 (9.2.0.1.0), choose whether you will be using Logical Partitions or the Oracle Clustered File System (OCFS). OCFS is available for download on Oracle Technical Network at http://otn.oracle.com for use with Oracle9i Release 2 (9.2.0.1.0) for Windows Platforms. Later versions of the Oracle9i Release 2 for Windows CD Packs may include an OCFS installation disk. Either of these will provide the same product distribution and will be referred to as the OCFS distribution media for this note.
Note: OCFS is not supported with Oracle9i Release 1 (9.0.1.0.0)
To configure Logical Partitions, continue to section 2.1 Logical Partitions Configuration.
To configure OCFS, please skip to section 2.2 Oracle Clustered File System Configuration.
For more information about Raw Devices and Cluster File Systems with Real Application Clusters, please see Note 183408.1 .
Back to top
2.1 Logical Partitions Configuration
Real Application Clusters requires that all each instance be able to access a set of unformatted devices on a shared disk subsystem. These shared disks are also referred to as raw devices. The Oracle instances in Real Application Clusters write data onto the raw devices to update the control file, server parameter file, each datafile, and each redo log file. All instances in the cluster share these files.
The Oracle Database Configuration Assistant (DBCA) will create a seed database expecting a particular configuration for a two-node cluster. For the seed database that will be created by the DBCA, it is recommended you create the Logical Partition at least 1M larger than the desired datafile size. The following table contains a listing of the tablespaces, minimum datafile size, and expected symbolic link names for Oracle9i Release 2 (9.2.0.1.0):
Tablespaces Minimum File Size
Expected File Name
SYSTEM tablespace
400 MB
\\.\db_name_system1
USERS tablespace
120 MB
\\.\db_name_users1
TEMP tablespace
100 MB
\\.\db_name_temp1
UNDOTBS tablespace Thread 1
250 MB
\\.\db_name_undotbs1
UNDOTBS tablespace Thread 2
250 MB
\\.\db_name_undotbs2
CWMLITE tablespace
100 MB
\\.\db_name_cwmlite1
EXAMPLE
160 MB
\\.\db_name_example1
INDX tablespace
70 MB
\\.\db_name_indx1
TOOLS tablespace
12 MB
\\.\db_name_tools1
DRSYS tablespace
90 MB
\\.\db_name_drsys1
XML tablespace 50 MB \\.\db_name_xml1
ODM tablespace 20 MB \\.\db_name_odm1
First control file
110 MB
\\.\db_name_control1
Second control file
110 MB
\\.\db_name_control2
Redo Thread 1 Log 1
120 MB
\\.\db_name_redo1_1
Redo Thread 1 Log 2
120 MB
\\.\db_name_redo1_2
Redo Thread 2 Log 1
120 MB
\\.\db_name_redo2_1
Redo Thread 2 Log 2
120 MB
\\.\db_name_redo2_2
spfile
5 MB
\\.\db_name_spfile1
srvcfg
100 MB
\\.\srvcfg
Notes on Table: Automatic Undo Management requires an undo tablespace per instance; therefore, you would require a minimum of 2 tablespaces as described above. In the sample names listed in the table, the string db_name should be replaced with the actual database name. The logical partition files within Windows are identified with the ‘\\.\’ notation and usually do not have an extension in the filename.
Please see the corresponding Oracle9i Release 1 documentation for the expected files in 9.0.1.0.0 version RDBMS.
The basic procedure is to first create the Extended Partitions for the hard disks in the array, then create as many Logical Partitions as required for the database files. Only one extended partition can be created for each disk. Oracle Corporation recommends creating the extended partition on an unpartitioned disk and using the entire disk for the extended partition.
Please refer to the section “Planning Your Logical Drives Configuration” in Appendix B of the Oracle9i Database Installation Guide for Windows for more guidelines on this.
Note: Creating a large number of logical partitions may cause a significant increase in the time needed to reboot and start the disk administration tools. Oracle Corporation recommends you do not create more than 120 logical drives in an extended partition. Please refer to the following Microsoft Knowledge Base articles for more information:
Q321685 - Disk Management Console does not start with Large# of partitions
Q317633 - Boot process is slow on Windows 2000 with Large # of Partitions.
Go to Section 2.3 for information on creating these partitions. Then go to section 2.4 to finish the pre-installation steps.
Back to top
2.2 Oracle Clustered File System Configuration
This note contains an abbreviated version of the instructions provided in the OCFS Release Notes. This configuration will install the Oracle Home on the local drive of each node and install the Oracle Datafiles on the shared OCFS Partitions. For more information about the concepts and different configurations of OCFS, please refer to the Release notes provided with the OCFS product.
The basic configuration procedure for OCFS is to create Logical Partitions containing the Oracle home, the Oracle database files or both. You may use additional Logical Partitions for more datafiles; however, since the number of partitions effects performance, it is recommended to use the minimum number of partitions needed. The Cluster Wizard will format these drives during setup.
You will not need to create a partition for the voting disk since OCFS stores the voting device in a file.
Go to Section 2.3 for information on creating these partitions. Then go to section 2.4 to finish the pre-installation steps.
Back to top
2.3 Overview of Creating Partitions in Windows
Use the following steps to create partitions within the Windows OS you are running.
2.3.1 Creating an Extended Partition on Windows 2000
Log in as member of the Local Administrators Group.
Choose Settings >; Control Panel. Double click on the Administrative Tools >; Computer Management. In the console tree, select Disk Management.
To create the Extended Partitions, right-click the unallocated region of a basic disk, and choose Create Partition.
In the Create Partition wizard, choose Next >; Extended Partition
Choose Extended Partition. Choose Next.
Choose the maximum amount of space and click Next.
A summary screen will come up. Choose Finish.
Repeat until all Extended Partitions are complete.
2.3.2 Creating a Logical Partition on Windows 2000
To create the Logical Partitions, right-click again on the Extended Partition and choose Create Logical Drive.
Follow the instructions in the wizard, choosing the appropriate size for your desired partition, choosing to not assign any drive letters, and choosing no format.
Repeat until all Logical Drives are complete.
Note: If the Disk Management window is open during any disk management modifications, such as creating symbolic links or adding logical partitions, you need to close and open the window to view any changes you applied.
2.3.3 Creating an Extended Partitions on Windows NT
Log in as member of the Local Administrators Group.
Choose Start >; Programs >; Administrative Tools >; Disk Administrator for Windows NT. The Disk Administrator window appears, showing all the disks in your shared array. Note that the lines display diagonally from top right to bottom left, indicating unpartitioned devices.
To create the Extended Partitions, right-click the unpartitioned disk and choose the Disk Administrator Create Extended option in the menu.
Select Create Extended. The Disk Administrator displays the maximum sizes for the extended partition. Accept and choose OK.
Repeat until all Extended Partitions are complete.
2.3.4 Creating a Logical Partition on Windows NT
To create the Logical Partitions, select an area of free space in the extended partition and right-click. Choose Partition >; Create.
Enter the desired size for the partition and click OK.
Right-click on the Logical Drive and choose Tools >; Assign Drive Letter. Click the Do Not Assign Letter option.
Repeat until all Logical Drives are complete.
Note: Changes are not saved until you choose Commit Changes Now or exit Disk Administrator.
Back to top
2.4 Verify Changes Are Visible on All Nodes in the Cluster
Open the Disk Administrator or Disk Management tool on all nodes. Note that the Windows OS on the other nodes will sometimes automatically assign drive letters to new partitions as they are created. Ensure there are no drive letters assigned by Windows since the Oracle OSD software will assign these later. Use either Disk Manager or Administrator to remove the drive letters or run the LetterDelete utility provided in the Oracle OSD software under the Disk1\preinstall_rac\olm directory.
If you have created more than 26 partitions, you may have to remove drive letters multiple times. This is due to Windows reassigning the letter you just deleted on one partition to another that had not received a letter in an initial assignment (after Z was assigned).
If there are any anomalies, correct within the Windows environment before proceeding.
Back to top
--------------------------------------------------------------------------------
3. Configuring the Cluster using the Oracle OSD Software
Note: Due to known issues with the GSD Service and the Server Control Utility (in following sections), you will have to apply patches to provided in the OCFS distribution media. This is regardless of whether you are using Logical Partitions or OCFS.
If this is a new installation: please use the OCFS media for installing the OSD software until a separate cluster patch is uploaded into Metalink.
If you have already installed the OSD software: The patch installation instructions are contained within the srvm.txt and dbca.txt files and are located in the \patch directory of the OCFS distribution media or in the %ORACLE_HOME%\cfspatch directory of the Oracle home. If you have documents in both locations, check the timestamps and use the newer version.
If you intend to use vendor operating system dependent clusterware instead of Oracle9i operating system dependent clusterware, then you can temporarily install the utilities located in the Disk1\preinstall_rac\olm directory. See the readme.txt for a description of each utility. See the section "Installing the Raw Devices Management Utilities Manually" in the Oracle9i Database Installation Guide for Windows for installation instructions.
3.1 Perform a Final Cluster Check
Note: Due to bug 2374197, the 9.2 version of the clustercheck utility does not work properly. Please use the 9.0.1 version as a workaround or obtain the fixed executable from Oracle Support.
At the command prompt, run the clustercheck.exe program located in the Disk1\preinstall_rac\clustercheck directory.
Note if using OCFS: run the clustercheck.exe program location in the Disk1\preinstall_rac\clustercheck directory of the OCFS media distribution.
This tool will prompt for the public and private hostnames and have you verify the IP address resolution. If that passes, then it will perform a check the health of the shared disk array and other environment variables and permissions necessary for proper cluster installation and operation. It will create a subdirectory called opsm in the temporary directory specified by your environment settings (WIN_DRIVE:\Documents and Settings\Administrator\Local Settings\Temp by default) and log file called OraInfoCoord.log. This log will contain any errors encountered in the check. You should see the following at the bottom of the log file and within the command prompt window when you run the clustercheck.exe program:
ORACLE CLUSTER CHECK WAS SUCCESSFUL
You must correct any errors that occur before proceeding with the Oracle OSD Software installation. Please contact your Cluster Hardware Vendor if you need assistance.
If you have any issues with Clustercheck, please see Note 186130.1 Clustercheck.exe fails with Windows error 183 .
Back to top
3.2 Installing the Oracle OSD Software
The Oracle Cluster Setup Wizard installs and starts Oracle9i operating system dependent clusterware required for Real Application Clusters databases. Please follow either the Logical Partition or OCFS configuration Steps.
3.2.1 Installing the OSD for Logical Partition Configurations
Navigate to the Disk1\preinstall_rac\clustersetup directory on the Oracle9i Server Installation CD.
Launch the Oracle Cluster Setup Wizard by double-clicking on clustersetup.exe. Then choose Next on the Welcome page.
The first time the Wizard is run, the only option will be to Create a cluster. Choose Next.
The Disk Configuration screen appears. Click on the Create Oracle Symbolic Links button.
The Oracle Object Link Manager window appears:
From the Symbolic Link column, select an empty row. The cursor starts blinking.
Enter the desired datafile link name and hit Enter to save.
Repeat steps 1 and 2 to assign all symbolic link names required (as outlined in the table in section 2.1).
Click on the Apply button to commit the changes.
When the progress bar at the bottom of the screen stops moving, choose Close.
From the Disk Configuration screen, assign a Voting disk, labeled as srvcfg, by highlighting the corresponding row. Choose Next.
The VIA Detection screen appears stating whether Virtual Interface Architecture (VIA) hardware was detected. Choose yes or no depending on your configuration. Please contact your cluster hardware vendor if you are unsure. Click Next.
The Network Selection screen appears. Choose Use private network for interconnect. Click Next.
The Network Configuration screen appears. Enter the public hostnames for all nodes. The private hostnames will be automatically entered as public_name.san. Accept the default or change as appropriate for your cluster configuration. Click Next.
The Install Location screen appears. It will default to the WIN_HOME\system32\osd9i directory. Accept the default and click Finish.
The Cluster Setup window will appear. This will show the progress with installing the cluster files and creating the cluster services on all nodes. If no errors occur, the Oracle Cluster Setup Wizard application will complete and close automatically.
3.2.2 Installing the OSD for OCFS Configurations
Navigate to the Disk1\preinstall_rac\clustersetup directory on the OCFS distribution media.
Launch the Oracle Cluster Setup Wizard by double-clicking on clustersetup.exe. Then choose Next on the Welcome page.
The first time the Wizard is run, the only option will be to Create a cluster. Choose Next.
Choose Use private network for interconnect and click Next.
The Network Configuration page appears. Enter the public hostnames for all nodes. The private hostnames will be automatically entered as public_name.san. Accept the default or change as appropriate for your cluster configuration. Click Next.
The Cluster File System Options page appears. Choose CFS for Datafiles. Click Next.
The CFS for Datafiles page appears. Choose another partition and click Next.
The VIA Detection screen appears stating whether Virtual Interface Architecture (VIA) hardware was detected. Choose yes or no depending on your configuration. Please contact your cluster hardware vendor if you are unsure. Click Next.
The Install Location screen appears. It will default to the WIN_HOME\system32\osd9i directory. Accept the default and click Finish.
The Cluster Setup window will appear. This will show the progress with installing the cluster files and creating the cluster services on all nodes. If no errors occur, the Oracle Cluster Setup Wizard application will complete and close automatically.
Back to top
3.3 Check the Cluster Install on All Nodes
Verify that all nodes have the following services running and set to Automatic startup within Control Panel >; Services:
o Oracle Object Service
o OracleCMService9i
o OracleClusterVolumeService (for OCFS only)
Verify that all nodes have an osd9i subdirectory in the WIN_HOME\system32 directory. Also verify all node registries contain the following key: HKEY_LOCAL_MACHINE\Software\Oracle\osd9i.
Back to top
--------------------------------------------------------------------------------
4. Using the Oracle Universal Installer for Real Application Clusters
The Oracle Universal Installer will install the Oracle9i Server Enterprise Edition and the Real Application Clusters software. Oracle9i Server Enterprise Edition for Windows is supplied in 3 CD-ROM disks.
For OCFS Configurations only: Perform the following steps first:
Navigate to the \install\win32 directory on the OCFS distribution media and run setup.exe. Oracle Universal Installer starts. Click Next at the Welcome page.
In the File Locations page, choose the drive that you created earlier for the Oracle Home and click Next. The OUI displays a summary page. Click Next.
Exit from this OUI session when it is successful. At the end of this OUI session, you will have installed the CFS support files in the %ORACLE_HOME%\cfspatch directory for the CFS Oracle home. This directory contains the srvm and dbca patches and the patch notes (srvm.txt and dbca.txt) for applying these patches.
4.1 Installation of the Database Software:
Insert the Oracle9i Server Enterprise Edition Disk 1. The Oracle Universal Installer should launch by Autostart. If not, navigate to the \install\win32 directory and run setup.exe. Oracle Universal Installer starts. Click Next at the Welcome page.
The Cluster Nodes Selection screen appears. Select the other nodes on to which the Oracle RDBMS software will be installed. It is not necessary to select the node on which the OUI is currently running. If all nodes are present, click Next.
NOTE: If not all nodes in the cluster are listed, there is something wrong with your cluster configuration � you will have to go back and troubleshoot your cluster install. You can perform clusterware diagnostics by executing the ORACLE_HOME\bin\lsnodes -v command and analyzing its output. Refer to your vendor's clusterware documentation if the output indicates that your clusterware is not properly installed. Resolve the problem, rerun the Oracle Cluster Wizard, and then restart the Universal Installer.
A prompt will appear for the Source path where the products.jar file is located. If this is the first time that OUI has been run on this system, this should default to the CD. If not, browse to the stage directory on the CD and highlight the products.jar file. For the Destination section, enter a name and location for your Oracle9i Home. This is the base directory into which OUI will install files. Click Next and a bar at the top of the window will show the progress of loading the products list. When it reaches 100%, it will proceed to the next screen.
The Available Products screen appears. Select the Oracle9i Database, and then click Next.
The Installation Type screen appears. Choose the Enterprise Edition. The selection on this screen refers to the installation operation, not the database configuration. Click Next.
The Database Configuration screen appears. Choose to perform a Custom type. Click Next.
If Microsoft Transaction Server is detected, then the Oracle Services for Microsoft Transaction Server window appears. Enter a port number for this service and click Next. The Summary page appears.
Review the information in the Summary page. Double-check the temporary space available on the drive from which you are installing and then click Install.
Note: The OUI will install the Oracle9i software on to the local node, and then copy this information to the other nodes selected. This will take some time, an one hour or more depending on your computing and networking environment. During the installation process, the OUI does not display all the messages indicating components are being installed on other nodes, so the installation may appear to be hung. In this case, I/O activity may be the only indication that the process is continuing. If necessary, check each node’s activity using Task Manager.
The Configuration Tools page appears when this phase of the installation is complete and automatically starts the configuration tools and displays the name of the tools while they run. Cancel out of all tools as you will configure these later.
Verify that the install completed by checking for an OracleGSDService on all nodes. If the service did not get created and started, begin by typing the following at the command line on each node:
C:\>; gsdservice –start
This service must be running before starting the Oracle Database Configuration Assistant (DBCA).
Back to top
--------------------------------------------------------------------------------
5. Create a RAC Database Using the Oracle Database Configuration Assistant
The Oracle Database Configuration Assistant (DBCA) will create a database for you. Oracle Corporation recommends that you use the DBCA to create your database because the preconfigured database optimizes your environment to take advantage of Oracle9i features such as the server parameter file and automatic undo management. The DBCA also enables you to define arbitrary tablespaces as part of the database creation process. So even if you have datafile requirements that differ from those offered in one of the DBCA templates, use the DBCA. You can also execute user-specified scripts as part of the database creation process. The DBCA and the Oracle Net Configuration Assistant also accurately configure your Real Application Clusters environment for various Oracle high availability features and cluster administration tools.
For OCFS Configurations only: Perform the following steps first:
On the CFS drive that you created for Datafiles, create an oradata directory at the root. This directory should be visible from all nodes. For example: O:\>;md oradata.
Open a new MS-DOS window and run DBCA from the command prompt as follows: dbca -datafileDestination O:\oradata
Follow the steps below beginning with 2.
5.1 Using DBCA:
Manually launch the Oracle Database Creation Assistant by navigating to the Oracle Program group, then to Configuration and Migration Tools.
The Welcome Page displays with the selection to create a Cluster or Single Instance Database. Choose Oracle Cluster Database option and select Next.
The Operations page is displayed. Choose the option Create a Database and click Next.
The Node Selection page appears. Select the nodes that you want to configure as part of the RAC database and click Next. Please see this Note if not all nodes are listed. If the OracleGSDService is not running on any of the selected nodes, then the DBCA displays a dialog explaining how to start.
The Database Templates page is displayed. The templates other than New Database include preconfigured datafiles for file systems. Choose New Database and then click Next.
DBCA now displays the Database Identification page. Enter the Global Database Name and Oracle System Identifier (SID). The Global Database Name is typically of the form name.domain, for example mydb.us.oracle.com, while the SID is used to uniquely identify an instance (DBCA should insert a suggested SID, equivalent to name1 where name was entered in the Database Name field). In the RAC case, the SID specified will be used as a prefix for the instance number. For example, MYDB would become MYDB1 and MYDB2 for instances 1 and 2, respectively. Click Next.
The Database Options page is displayed. Select the options you wish to configure. The Additional database Configurations button displays the option to install Java and interMedia database features. Check all options you wish and then choose Next. Note: If you did not choose New Database from the Database Template page, you will not see this screen.
The Connection Options screen appears. Select either the dedicated server or shared server option for the default user connection type. Note: If you did not choose New Database from the Database Template page, you will not see this screen. Click Next.
DBCA now displays the Initialization Parameters page. This page comprises a number of pages which you navigate through by clicking on the tabs:
Modify the Memory settings if desired.
Change the Archivelog mode as necessary. In general, it is recommended you create your database in Noarchivelog mode, and then after the database is created, alter the database after performing a complete backup.
DB Sizing will specify your db_block_size, sort_area_size and database character set parameters.
Under the File Locations tab, the option Create persistent initialization parameter file is selected by default. The raw device name for the location of the server parameter file (spfile) must be entered. The button File Location Variables… displays variable information. Click OK.
The button All Initialization Parameters… displays the Initialization Parameters dialog box. This box presents values for all initialization parameters and indicates whether they are to be included in the spfile to be created through the check box, included (Y/N). Instance specific parameters have an instance value in the instance column. Complete entries in the All Initialization Parameters page and select Close.
Note: There are a few exceptions to what can be altered via this screen. Ensure all entries in the Initialization Parameters page are complete and select Next.
DBCA now displays the Database Storage Window. This page allows you to enter file names for each tablespace in your database. The file names are displayed in the Datafiles folder, but are entered by selecting the Tablespaces icon, and then selecting the tablespace object from the expanded tree. Any names displayed here can be changed. These should defined appropriately for your configuration using either the OCFS oradata drive or using the Logical Partition symbolic links created earlier. Complete the database storage information and click Next.
The Creation Options page is displayed. Ensure that the option Create Database is checked and click Finish. Check the Create template and save as a script boxes if desired.
The DBCA Summary window is displayed. Review this information and then click OK. Once the Summary screen is closed using the OK option, DBCA begins to create the database according to the values specified.
Note: The database creation can take a while, and the progress may seem slow or hung, especially during the creation of the java server components and at the end when the database service is created on the second node the second thread of redo is created. You can check the progress by checking Task Manager and seeing the CPU activity, or by checking the alert log for redo log switching.
A new database now exists. It can be accessed via Oracle SQLPlusWorksheet or other applications designed to work with an Oracle RAC database.
If you have issues with any service hangs, please see Note 213416.1 RAC: Troubleshooting Windows NT/2000 Service Hangs.
Back to top
--------------------------------------------------------------------------------
6. Using SRVCTL for the Administration and Maintenance of a RAC Database
Once your RAC database is created, you can use the Server Control (SRVCTL) utility to assist in administration and maintenance tasks. The Global Services Daemon (GSD) receives requests from SRVCTL to execute administrative jobs, such as startup or shutdown. The task is executed locally on all nodes, and the results are sent back to SRVCTL. SRVCTL also serves as a single point of control between the Oracle Intelligent Agent and the nodes in the cluster.
If you have issues with Oracle Agent hangs, please see the following notes:
Note 223554.1 Automatic Startup of the Intelligent Agent Fails in RAC Environment
Note 158295.1 How to Configure EM with 9i Real Application Clusters (RAC)
To see the online command syntax and options for each SRVCTL command, enter:
srvctl command option -h
Where command option is one of the valid options such as start, stop, or status.
The following are some examples of tasks you can perform with this utility. (Please see the corresponding Administration guide for more complete command details.)
o srvctl start
Use this command to start all instances or a subset of instances in your Real Application Clusters database. For example, to start all the instances use the syntax:
For 9.0.1.0.0: srvctl start -p db_name
For 9.2.0.1.0: srvctl start database -d db_name
Or you can start specific instances using the syntax:
For 9.0.1.0.0: srvctl start -p db_name -i instance_name
For 9.2.0.1.0: srvctl start instance -d db_name -i instance_name
This syntax starts the specific instance that you name. Using srvctl start also starts all listeners associated with an instance.
o srvctl stop
Use this command to stop all instances or a subset of instances in your Real Application Clusters database. For example, to stop all instances use the syntax:
For 9.0.1.0.0: srvctl stop -p db_name
For 9.2.0.1.0: srvctl stop database -d db_name
Or you can stop specific instances using:
For 9.0.1.0.0: srvctl stop -p db_name -i instance_name
For 9.2.0.1.0: srvctl stop instance -d db_name -i instance_name
Using srvctl stop also stops all listeners associated with an instance.
o srvctl status
Use the srvctl status command to determine what instances are running. For example, use the output from the following syntax to identify which instances are running:
For 9.0.1.0.0: srvctl status -p db_name -i instance_name
For 9.2.0.1.0: srvctl status instance -d db_name -i instance_name
o srvctl config
Use the srvctl config command to identify the existing Real Application Clusters databases. You can use two syntaxes for srvctl config. For example, the following syntax lists all the Real Application Clusters databases in your environment:
srvctl config
The following syntax lists the instances for the Real Application Clusters database name that you provide:
For 9.0.1.0.0: srvctl config -p db_name
For 9.2.0.1.0: srvctl config database -d db_name
The Oracle Enterprise Manager auto-discovery process also uses output from this command to discover the configurations for databases in your Real Application Clusters.
o srvctl getenv or get env
Use the srvctl get env command to obtain environment information for either a specific instance or for an entire Real Application Clusters database. For example, the output from the following syntax displays environment information for the entire Real Application Clusters database identified by the name you provide:
For 9.0.1.0.0: srvctl get env -p db_name
For 9.2.0.1.0: srvctl getenv database -d db_name
The following syntax displays environment information for a specific instance:
For 9.0.1.0.0: srvctl get env -p db_name -i instance_name
For 9.2.0.1.0: srvctl getenv instance -d db_name -i instance_name
Back to top
--------------------------------------------------------------------------------
7. References
The following are references used from the Oracle online documentation for both Release 1 and Release 2:
Oracle9i Database Installation Guide for Windows
Oracle9i Real Application Clusters Installation and Configuration
Oracle9i Real Application Clusters Concepts
Oracle9i Real Application Clusters Administration
Oracle9i Real Application Clusters Deployment and Performance
Oracle9i Release Notes
In addition, the following references were used:
Oracle9i for Windows 2000 Tips and Techniques: Best Practices from Oracle Experts Oracle Press - McGraw-Hill/Osborne (ISBN 0-07-219462-6) |
|
免费注册
发表于 2003-02-13 10:34
