| Oracle® Database Installation Guide 11g Release 2 (11.2) for HP-UX Part Number E10851-04 |
|
|
View PDF |
| Oracle® Database Installation Guide 11g Release 2 (11.2) for HP-UX Part Number E10851-04 |
|
|
View PDF |
The Oracle grid infrastructure for a standalone server is the Oracle software that provides system support for an Oracle database including volume management, file system, and automatic restart capabilities. If you plan to use Oracle Restart or Automatic Storage Management, you must install the grid infrastructure before installing your database. The grid infrastructure for a standalone server is the software that includes Oracle Restart and Automatic Storage Management. Oracle combined the two infrastructure products into a single set of binaries that is installed as the grid infrastructure home. The grid infrastructure should be installed before installing Oracle Database 11g Release 2.
Automatic Storage Management is a volume manager and a file system for Oracle database files that supports single-instance Oracle Database and Oracle Real Application Clusters (Oracle RAC) configurations. Automatic Storage Management also supports a general purpose file system for your application needs including Oracle Database binaries. Automatic Storage Management is Oracle's recommended storage management solution that provides an alternative to conventional volume managers, file systems, and raw devices.
Oracle Restart improves the availability of your Oracle database by providing the following:
When there is a hardware or a software failure, Oracle Restart automatically starts all Oracle components, including Oracle database instance, Oracle Net Listener, database services, and Automatic Storage Management.
Oracle Restart starts up components in the proper order when the database host is restarted.
Oracle Restart runs periodic checks to monitor the health of Oracle components. If a check operation fails for a component, then the component is shut down and restarted.
Note:
If you want to use Automatic Storage Management or Oracle Restart, then you must first install Oracle grid infrastructure for a standalone server and then install Oracle Database.
Oracle Restart is used in single-instance (non-clustered) environments only.
This chapter contains the following sections:
Preparing Disks for an Automatic Storage Management Installation
Installing and Configuring Grid Infrastructure for a Standalone Server
Modifying Oracle Grid Infrastructure Binaries After Installation
Manually Configuring Oracle Automatic Storage Management Disk Groups
The system must meet the following requirements:
The following are the memory requirements for installing Oracle grid infrastructure:
At least 4 GB of RAM
To determine the RAM size, enter the following command:
On HP-UX PA-RISC
# grep "Physical:" /var/adm/syslog/syslog.log
On HP-UX Itanium
# /usr/contrib/bin/machinfo | grep -i Memory
If the size of the RAM is less than the required size, then you must install more memory before continuing.
The following table describes the relationship between installed RAM and the configured swap space requirement:
| RAM | Swap Space |
|---|---|
| Between 4 GB and 8 GB | 2 times the size of RAM |
| Between 8 GB and 32 GB | 1.5 times the size of RAM |
| More than 32 GB | 32 GB |
To determine the size of the configured swap space, enter the following command:
# /usr/sbin/swapinfo -a
If necessary, refer to the operating system documentation for information about how to configure additional swap space.
The following are the disk space requirements for installing grid infrastructure:
For HP Itanium: At least 5 GB of disk space.
For HP-UX PA-RISC: At least 4 GB of disk space.
At least 1 GB of disk space in the /tmp directory.
To determine the amount of free disk space available in the /tmp directory, enter the following command:
# bdf /tmp
If there is less than 1 GB of free disk space available in the /tmp directory, then complete one of the following steps:
Delete unnecessary files from the /tmp directory to meet the disk space requirement.
Set the TMP and TMPDIR environment variables to specify a temporary directory when setting the oracle user's environment.
See Also:
"Configuring the oracle User's Environment" for more information on setting
TMP and TMPDIRExtend the file system that contains the /tmp directory. If necessary, contact the system administrator for information about extending file systems.
Complete the following tasks to set the Oracle grid infrastructure software owner user's environment:
Review the information in "Logging In to the System as root" section.
Ensure that you set the path to the Oracle base directory. Oracle Restart and Oracle Database reside under the same Oracle base. For example:
# ORACLE_BASE=/u01/app/oracle; # export ORACLE_BASE
Set the Oracle grid infrastructure software owner user default file mode creation mask (umask) to 022 in the shell startup file. Setting the mask to 022 ensures that the user performing the software installation creates files with 755 permissions.
Set ulimit settings for file descriptors and processes for the Oracle grid infrastructure installation software owner.
Set the DISPLAY environment variable in preparation for installation.
If you have an Automatic Storage Management (ASM) installation from a prior release installed on your server, or in an existing Oracle grid infrastructure installation, you can use Oracle Automatic Storage Management Configuration Assistant (ASMCA) to upgrade the existing Automatic Storage Management instance to 11g Release 2 (11.2), and subsequently configure disk groups, Automatic Storage Management volumes and Automatic Storage Management file systems.
Note:
You must first shut down all databases and applications using an existing Automatic Storage Management instance before upgrading it.During installation, if you chose to use Automatic Storage Management and Oracle Automatic Storage Management Configuration Assistant detects that there is a prior Automatic Storage Management version installed in another Automatic Storage Management home, then after installing the Automatic Storage Management 11g Release 2 (11.2) binaries, you can start Oracle Automatic Storage Management Configuration Assistant to upgrade the existing Automatic Storage Management instance.
In previous releases, Oracle Automatic Storage Management (ASM) was installed as part of the Oracle Database installation. With Oracle Database 11g Release 2 (11.2), Automatic Storage Management is part of an Oracle grid infrastructure installation, either for a cluster, or for a standalone server.
If you want to upgrade an existing Automatic Storage Management installation, then you must upgrade Automatic Storage Management by running an Oracle grid infrastructure upgrade (upgrades of existing Automatic Storage Management installations). If you do not have Automatic Storage Management installed and you want to use Automatic Storage Management as your storage option, then you must complete an Oracle grid infrastructure installation before you start your Oracle Database installation.
You must run Oracle Automatic Storage Management Configuration Assistant for installing and configuring Oracle ASM instances, disk groups, volumes, and Oracle Automatic Storage Management Cluster File System (Oracle ACFS). In addition, you can use the ASMCA command-line interface as a non-GUI utility.
See Also:
Chapter 11, "Oracle ASM Configuration Assistant" in Oracle Database Storage Administrator's Guide for information on Oracle ASMCAApply the following guidelines when you install Automatic Storage Management:
You must complete the steps listed under "Preparing Disks for an Automatic Storage Management Installation" to prepare a disk partition to use for the Automatic Storage Management disk groups.
Ensure that at least one disk is configured appropriately for use in an Automatic Storage Management diskgroup before beginning the installation.
When you install Automatic Storage Management, Oracle Automatic Storage Management Configuration Assistant (Oracle ASMCA) creates a separate server parameter file (SPFILE) and password file for the Automatic Storage Management instance. As soon as Oracle Automatic Storage Management is installed, the ASMSNMP schema and user are created. See Oracle Database Storage Administrator's Guide for more information.
The Automatic Storage Management instance that manages the existing disk group will be running in the grid infrastructure Oracle home directory.
This section describes how to configure disks for use with Automatic Storage Management. The following sections describe how to identify the requirements and configure the disks on each platform:
Step 1: Identifying Storage Requirements for Automatic Storage Management
Step 2: Creating DAS or SAN Disk Partitions for Automatic Storage Management
Note:
Oracle does not recommend using identifiers for database object names that must be quoted. While these quoted identifiers may be valid as names in theSQL CREATE statement, such as CREATE DISKGROUP "1data" ..., the names may not be valid when using other tools that manage the database object.See Also:
"Creating Disk Groups for a New Oracle Installation", in Oracle Database Storage Administrator's Guide for information on creating and managing disk groupsThe following are the general steps to configure Automatic Storage Management:
Identify the storage requirements of the site.
If you are creating a new Automatic Storage Management disk group, create partitions for DAS or SAN disks.
Configure the disks for use with Automatic Storage Management. You will need to provide the Automatic Storage Management disk configuration information during the grid infrastructure installation.
To identify the storage requirements for using Automatic Storage Management, you must determine the number of devices and the amount of free disk space that you require. To complete this task:
Determine whether you want to use Automatic Storage Management for Oracle Database files, recovery files, or both.
Note:
You do not have to use the same storage mechanism for , Oracle Database files, and recovery files. You can use a file system for one file type and Automatic Storage Management for the other.If you choose to enable automated backups and you do not have a shared file system available, then you must choose Automatic Storage Management for recovery file storage.
During the database installation, if you plan to enable automated backups, then you can choose Automatic Storage Management as the storage mechanism for recovery files by specifying an Automatic Storage Management disk group for the fast recovery area. Depending on how you choose to create a database during the database installation, you have the following options:
You can run Oracle Automatic Storage Management Configuration Assistant in interactive mode to create and configure the required disk groups.
During the database installation, if you select an installation method that runs Database Configuration Assistant in interactive mode (Advanced Installation type), then you can select the diskgroups that you created using Oracle ASMCA.
You have the option to use the disk groups you created using Oracle ASMCA both for database files and recovery files, or you can choose to use different disk groups for each file type. Ideally, you should create separate Automatic Storage Management disk groups for data files and for recovery files.
If you run Oracle ASMCA in noninteractive mode, then you must use the same Automatic Storage Management disk group for data files and recovery files. During the database installation (Typical Installation type), you will have to select the same disk group for both data files and recovery files..
See Also:
"Oracle ASM Configuration Assistant Command-Line Interface" section in Oracle Database Storage Administrator's Guide
Choose the Automatic Storage Management redundancy level that you want to use for each Automatic Storage Management disk group that you create.
The redundancy level that you choose for the Automatic Storage Management disk group determines how Automatic Storage Management mirrors files in the disk group and determines the number of disks and amount of disk space that you require, as follows:
External redundancy
This option does not allow Automatic Storage Management to mirror the contents of the disk group. Oracle recommends that you select this redundancy level either when the disk group contains devices, such as RAID devices, that provide their own data protection or when the database does not require an uninterrupted access to data.
Normal redundancy
To optimize performance and reliability in a normal redundancy disk group, Automatic Storage Management uses two-way mirroring for data files and three-way mirroring for control files, by default. In addition, you can choose the mirroring characteristics for individual files in a disk group. Alternatively, you can use two-way mirroring or no mirroring.
A normal redundancy disk group requires a minimum of two failure groups (or two disk devices) if you are using two-way mirroring. The effective disk space in a normal redundancy disk group is half the sum of the disk space in all of its devices.
For most installations, Oracle recommends that you use normal redundancy disk groups.
High redundancy
The contents of the disk group are three-way mirrored by default. To create a disk group with high redundancy, you must specify at least three failure groups (a minimum of 3 devices).
Although high-redundancy disk groups provide a high level of data protection, you must consider the higher cost of additional storage devices before deciding to use this redundancy level.
Determine the total amount of disk space that you require for the database files and recovery files.
If an Automatic Storage Management instance is already running on the system, then you can use an existing disk group to meet these storage requirements. If necessary, you can add disks to an existing disk group during the database installation.
Use the following table to determine the minimum number of disks and the minimum disk space requirements for the installation:
| Redundancy Level | Minimum Number of Disks | Data Files | Recovery Files | Both File Types |
|---|---|---|---|---|
| External | 1 | 1.8 GB | 3.6 GB | 5.4 GB |
| Normal | 2 | 3.6 GB | 7.2 GB | 10.8 GB |
| High | 3 | 5.4 GB | 10.8 GB | 16.2 GB |
Optionally, identify failure groups for the Automatic Storage Management disk group devices.
If you intend to use a normal or high redundancy disk group, then you can further protect the database against hardware failure by associating a set of disk devices in a custom failure group. By default, each device comprises its failure group. However, if two disk devices in a normal redundancy disk group are attached to the same SCSI controller, then the disk group becomes unavailable if the controller fails. The controller in this example is a single point of failure.
For instance, to avoid failures of this type, you can use two SCSI controllers, each with two disks, and define a failure group for the disks attached to each controller. This configuration would enable the disk group to tolerate the failure of one SCSI controller.
Note:
If you define custom failure groups, then you must specify a minimum of two failure groups for normal redundancy disk groups and three failure groups for high redundancy disk groups.If you are sure that a suitable disk group does not exist on the system, then install or identify appropriate disk devices to add to a new disk group. Apply the following guidelines when identifying appropriate disk devices:
The disk devices must be owned by the user performing the grid installation.
All the devices in an Automatic Storage Management disk group should be the same size and have the same performance characteristics.
Do not specify multiple partitions on a single physical disk as a disk group device. Automatic Storage Management expects each disk group device to be on a separate physical disk.
Oracle does not recommend the use of a logical volume as a device in Automatic Storage Management because the logical volume is capable of hiding the physical disk architecture which prevents Automatic Storage Management from optimizing I/O across physical devices.
See Also:
"Step 3: Configuring Disks for Automatic Storage Management" for information about completing this task
"Preparing Storage for ASM" in Oracle Database Storage Administrator's Guide for information on configuring Automatic Storage Management disk groups
In order to use a DAS or SAN disk in Automatic Storage Management, the disk must have a partition table. Oracle recommends creating exactly one partition for each disk containing the entire disk.
To configure disks for use with Automatic Storage Management:
If necessary, install the disks that you intend to use for the Automatic Storage Management disk group.
To ensure that the disks are available, enter the following command:
# /usr/sbin/ioscan -fun -C disk
The output from this command is similar to the following:
Class I H/W Path Driver S/W State H/W Type Description
==========================================================================
disk 0 0/0/1/0.6.0 sdisk CLAIMED DEVICE HP DVD 6x/32x
/dev/dsk/c0t6d0 /dev/rdsk/c0t6d0
disk 1 0/0/1/1.2.0 sdisk CLAIMED DEVICE SEAGATE ST39103LC
/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0
This command displays information about each disk attached to the system, including the block device name (/dev/dsk/cxtydz).
Note:
On HP-UX 11i v.3, you can also use agile view to review mass storage devices, including block devices (/dev/disk/diskxyz), or character raw devices (/dev/rdisk/diskxyz). For example:
#>ioscan -funN -C disk
Class I H/W Path Driver S/W State H/W Type Desc
===================================================================
disk 4 64000/0xfa00/0x1 esdisk CLAIMED DEVICE HP73.4GST373454LC
/dev/disk/disk4 /dev/rdisk/disk4
disk 907 64000/0xfa00/0x2f esdisk CLAIMED DEVICE COMPAQ MSA1000 VOLUME
/dev/disk/disk907 /dev/rdisk/disk907
If the ioscan command does not display device name information for a device that you want to use, then enter the following command to install the special device files for any new devices:
# /usr/sbin/insf -e
For each disk that you want to add to a disk group, enter the following command to verify that it is not already part of an LVM volume group:
# /sbin/pvdisplay /dev/dsk/cxtydz
If this command displays volume group information, then the disk is already part of a volume group. The disks that you choose must not be part of an LVM volume group.
Note:
If you are using different volume management software, for example VERITAS Volume Manager, then refer to the appropriate documentation for information about verifying that a disk is not in use.Enter commands similar to the following to change the owner, group, and permissions on the character file for each disk that you want to add to a disk group:
# chown oracle:dba /dev/rdsk/cxtydz # chmod 660 /dev/rdsk/cxtydz
Note:
For DSF (agile view) paths, enter commands using paths similar to the following:# chmod 660 /dev/rdisk/diskxyz
Note:
If you are using a multi-pathing disk driver with Automatic Storage Management, then ensure that you set the permissions only on the correct logical device name for the disk.If you install Oracle grid infrastructure and then create your database, the database is automatically added to the Oracle grid infrastructure configuration, and is then automatically restarted when required. However, if you install Oracle grid infrastructure on a host computer on which a database already exists, you must manually add the database, the listener, the Oracle Automatic Storage Management instance, and other components to the Oracle grid infrastructure configuration.
Note:
Oracle grid infrastructure can accommodate multiple single-instance databases on a single host computer.This section includes the following topics:
Perform the following steps to install the grid infrastructure and then create a database that is managed by Oracle Restart. First install grid infrastructure, which installs Oracle Restart and Automatic Storage Management, then configure Automatic Storage Management with at least one disk group, and then install Oracle database that stores database files in Automatic Storage Management disk groups. Click the help button on the Oracle Universal Installer page for page level assistance.
You may need to shut down existing Oracle processes before you proceed with the grid infrastructure installation. Refer to "Stopping Existing Oracle Processes" for more information.
To install Oracle grid infrastructure for a standalone server with a new database installation:
Start Oracle Universal Installer as the grid infrastructure software owner user. Complete one of the following steps depending on the location of the installation files:
If the installation files are on installation media, enter commands similar to the following, where directory_path is the path of the grid infrastructure directory on the installation media:
$ /directory_path/runInstaller
Note:
You must install Oracle grid infrastructure for a standalone server from the grid infrastructure media.If the installation files are on the hard disk, change the directory to the path of the grid infrastructure (clusterware) directory and enter the following command:
$ ./runInstaller
Note:
Start Oracle Universal Installer from the terminal session where you logged in as the grid infrastructure software owner user and set the user's environment.See Also:
"Configuring the User's Environment" for information about setting the grid infrastructure software owner user's environmentIf Oracle Universal Installer is not displayed, refer to "X Window Display Errors" and "Remote Terminal Installation Error" for information about troubleshooting.
The Select Installation Option screen appears. Select Install and Configure Grid Infrastructure for a Standalone Server option, to install and configure Oracle Restart and Oracle Automatic Storage Management. Click Next.
On the Select Product Languages screen, select one or more languages. Move the languages from the Available Languages list to the Selected Languages list. Click Next.
The Create ASM Disk Group screen, lists all the Automatic Storage Management disks under ORCLDISK:*
Click Change Disk Discovery Path to select any devices that will be used by Automatic Storage Management but are not listed. In the Change Disk Discovery Path window, enter a string to use to search for devices that Automatic Storage Management will use. If the diskstring is set to ORCLDISK:* or is left empty (""), then the installer discovers these disks. Click OK.
After you finish selecting the disks to be used by Automatic Storage Management, click Next.
Note:
During installation, disk paths mounted on ASM and registered on ASMLIB with the stringORCLDISK:* are listed as default database storage candidate disks.Consider the following information about disk devices while performing this step:
The Disk Group Name default is DATA. You can enter a new name for the disk group, or use the default name.
The disk devices must be owned by the user performing the grid installation.
Check with your system administrator to determine if the disks used by Automatic Storage Management are mirrored at the storage level. If so, select External for the redundancy. If the disks are not mirrored at the storage level, then choose Normal for the redundancy.
Note:
For normal redundancy, you require twice as much disk space to hold the same amount of data. For example, if your database is 100 GB, then you require approximately 200 GB of storage.In the Specify ASM Password screen, enter SYSASM password required to connect to the Automatic Storage Management instance. The Oracle Automatic Storage Management instance is managed by a privileged role called SYSASM, which grants full access to Automatic Storage Management disk groups. Oracle recommends that you create a less privileged user, ASMSNMP, with SYSDBA privileges to monitor the Oracle Automatic Storage Management instance.
Enter passwords for the SYS and ASMSNMP user accounts. The passwords should be at least eight characters in length and include at least one alphabetic and one numeric character.
On the Privileged Operating System Groups screen, select the name of the operating system group you created for the OSDBA group, the OSASM group, and the database operator group OSOPER. If you choose to create only the dba group, then you can use that group for all three privileged groups. If you created a separate asmadmin group, then use that value for the OSASM group. Click Next.
On the Specify Installation Location screen, enter the following details and click Next:
Oracle Base: Enter the directory location for Oracle base. Do not include spaces in the path name.
Software Location: This field is populated by default in concurrence with Oracle base location.
See Also:
"Naming Directories" for directory naming conventionsIf you have not installed any Oracle software previously on this server, the Create Inventory screen appears.
Change the path for the Inventory Directory, if required. Select oinstall for the oraInventory Group Name, if required. Click Next.
The Perform Prerequisite Checks screen, checks if the minimum system requirements are met to carry out the grid infrastructure installation. If all the system requirements are met, then you will be directed to the Summary screen. However, in case of a failed installation, you can review the error.
If you click Check Again, then you can run the prerequisite check again to see if the minimum requirements are met to carry on with the database installation.
Click Fix & Check Again, if you want the installer to fix the problem and check the system requirements once more.
Note:
The Fix & Check Again option generates a script that you need to run as theroot user. This generated script sets some of the system parameters to Oracle-recommended values. Oracle recommends that you do not modify the contents of this script. Refer to "Installation Fixup Scripts" for more information on fixup scripts.To get a list of failed requirements, select ShowFailed from the list. To get a list of all the prerequirement checks run by the OUI, select Show All. To get a list of the prerequirement checks that are successful, select Show Succeeded.
Note:
To ignore all the errors and proceed with the database installation, check Ignore All.Review the contents of the Summary screen, and click Finish.
The Setup screen displays the progress of the grid infrastructure installation. During the installation process, the Execute Configuration Scripts window appears. Do not click OK until you have run the scripts mentioned in this screen.
Run the root.sh and, if required, the orainstRoot.sh configuration scripts as the root user.
The Finish screen displays the installation status. Click Close to end the installation, then Yes to confirm that you want to exit Oracle Universal Installer.
If you encounter any problems, refer to the configuration log for information. The path to the configuration log is displayed on the Configuration Assistants window.
If you want to create additional disk groups, then run the Oracle Automatic Storage Management Configuration Assistant (ASMCA) utility. For example, you can create another disk group named RECOVERY to store the fast recovery area.
Note:
To check if the Oracle High Availability Service is installed properly, run./crsctl check has command from Grid_home/bin directory.
Grid_home is the path to the Oracle grid infrastructure home for a standalone server. Ohasd is a daemon installed with Oracle grid infrastructure that starts software services, such as Oracle Automatic Storage Management.
Install Oracle database.
Because you have already installed Oracle grid infrastructure, Oracle Universal Installer will automatically add the database instance to the Oracle grid infrastructure configuration if you choose to create a database as part of the installation.
See Also:
"Installing the Oracle Database Software" for information about installing Oracle databaseNote:
If a new database is installed after a grid infrastructure installation, then the listener runs from the grid infrastructure home. Because Oracle Automatic Storage Management is installed as part of the grid infrastructure, the default listener is created and runs from the grid infrastructure home. If you perform a database installation, then the database must use the same listener created during the grid infrastructure installation.
If you are using Oracle Restart, then the default listener and any additional listeners must run from the grid infrastructure home.
Follow the high-level instructions in this section to install Oracle grid infrastructure and configure it for an existing Oracle database. Please note that Oracle Restart can only manage existing 11.2 resources and hence you can install Oracle grid infrastructure only for an existing 11.2 database. However, Oracle database releases prior to 11.2 can coexist on the same server without being managed by Oracle Restart.
To install Oracle grid infrastructure for an existing database:
On the same host computer as the database, use Oracle Universal Installer to install the grid infrastructure, and select Install and Configure Grid Infrastructure for a Standalone Server as the installation option.
The grid infrastructure components are installed in a separate Oracle home.
Refer to "Installing Grid Infrastructure with a New Database Installation" for detailed instructions.
Go to the Grid home's bin directory. Use the srvctl add database command to manually add the database, the listener, the Automatic Storage Management instance, all Automatic Storage Management disk groups, and any database services to the Oracle grid infrastructure configuration.
See Also:
"srvctl add database" in Oracle Database Administrator's Guide for more information about thesrvctl add database commandAfter installation, you must first stop the Oracle Restart stack to modify the software installed in your Grid home. For example, if you want to apply a one-off patch or modify any of the DLLs used by Oracle Restart or Oracle ASM, then you must follow these steps to stop and restart the Oracle Restart stack.
Caution:
Before relinking executables, you must shut down all executables that run in the Oracle home directory that you are relinking. In addition, shut down applications linked with Oracle shared libraries.Prepare the Oracle grid infrastructure home for modification using the following procedure:
Log in as the grid infrastructure software owner user and change the directory to the path Grid_home\bin, where Grid_home is the path to the Oracle grid infrastructure home:
$ cd Grid_home/bin
Shut down the Oracle Restart stack using the following command:
$ crsctl stop has -f
After the Oracle Restart stack is completely shut down, perform the updates to the software installed in the Grid home.
Use the following command to restart the Oracle Restart stack:
$ crsctl start has
The Oracle Automatic Storage Management Configuration Assistant utility creates a new Automatic Storage Management instance if there is no Automatic Storage Management instance currently configured on the computer.
If you want to create additional disk groups or manually configure Automatic Storage Management disks, then you can run the Oracle Automatic Storage Management Configuration Assistant as follows:
$ cd Grid_home/bin
$ ./asmca
Where Grid_home is the path to the Oracle grid infrastructure home for a standalone server.
See Also:
Oracle Database Storage Administrator's Guide for further information on Oracle Automatic Storage Management Configuration AssistantTo test the Automatic Storage Management installation, try logging in by using the asmcmd command-line utility, which lets you manage Automatic Storage Management disk group files and directories. To do this:
Open a shell window, and temporarily set the ORACLE_SID and ORACLE_HOME environment variables to specify the appropriate values for the Automatic Storage Management instance that you want to use.
For example, if the Automatic Storage Management SID is named +ASM and the Oracle home is located in the grid subdirectory of the ORACLE_BASE directory, then enter the following commands to create the required settings:
Bourne, Bash, or Korn shell:
$ ORACLE_SID=+ASM $ export ORACLE_SID $ ORACLE_HOME=/u01/app/oracle/product/11.2.0/grid $ export ORACLE_HOME
C shell:
% setenv ORACLE_SID +ASM % setenv ORACLE_HOME /u01/app/oracle/product/11.2.0/grid
Use asmcd to connect to the Automatic Storage Management instance as the SYS user with SYSASM privilege and start the instance if necessary:
$ORACLE_HOME/bin/asmcmd lsdg
See Also:
Oracle Database Utilities for more information about asmcmd
Oracle Database Storage Administrator's Guide for a more detailed description of Automatic Storage Management
|
 Copyright © 1996, 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|