Skip to main content

How to Install and Configure Oracle ASM


<<Back to Oracle ASM Main Page

Installing Grid Infrastructure for a Standalone Server and Configuring ASM Instance in Silent Mode

Installing Grid Infrastructure for a Standalone Server in Silent Mode
Step1> Download GI Binary
Download oracle database clusterware binaries from here. This post is based on oracle 12.2.0.1 (12cR2)
Step2> create required group, user and directories as root user
#groupadd asmadmin
#groupadd oinstall
#useradd -g oinstall -G asmadmin oragrid
#chown -R oragrid:oinstall /u01/oragrid
#chmod -R 755 /u01/oragrid
#mkdir -p /u01/oragrid/12.2.0.1/grid
GRID_HOME=/u01/oragrid/12.2.0.1/grid<= this is the location where I am installing oracle grid binary
Step3> Transfer the GI Software
Transfer the binaries to the server where you want to install it using winscp or tool you prefer
Step4>unzip the GI Software in GRID_HOME
unzip the file (in my case linuxx64_12201_grid_home.zip) you need minimum 10G space.
Note:- Unzip the oracle gird binary in GRID_HOME (in my case it is /u01/oragrid/12.2.0.1/grid). You just need to run gridSetup.sh from GRID_HOME  to proceed the installation. Detail steps are below.
Step5> Perform PreCheck
Ensure that you complete all the storage and server preinstallation requirements. Verify that your server meets the installation requirements using the following command
$ cd /u01/oragrid/12.2.0.1/grid
$ ./runcluvfy.sh stage -pre hacfg
Note:- If above command reports any failure, ensure to fix the issues before proceeding further
Step6>Run gridSetup.sh
Run gridSetup.sh to start the Oracle Grid Infrastructure installation wizard if you wish to start the installation in GUI mode. However in this post I will demonstrate you silent installation.
Step7> Response Files for Silent Installation.
Oracle provides response file templates for each product and installation type, and for each configuration tool.
Edit the response file templates located in the Grid_home/install/response directory.
Caution:When you modify a response file template and save a file for use, the response file may contain plain text passwords. Ownership of the response file should be given to the Oracle software installation owner only, and permissions on the response file should be changed to 600.
Step8>Prepare Response File

Preparing Response Files for Software Only Silent Installation

Backup the original response file before you modify it
$ cp /u01/oragrid/12.2.0.1/grid/install/response/gridsetup.rsp /u01/oragrid/12.2.0.1/grid/install/response/gridsetup.rsp.orig
Change responce file permission
$ chmod 600 /u01/oragrid/12.2.0.1/grid/install/response/gridsetup.rsp
Edit /u01/oragrid/12.2.0.1/grid/install/response/gridsetup.rsp using vi and modify the parameter as shown below
The response file is pretty much self explaining. Change the following parameters according to your environment and keep the rest untouched in case you don't need to configure anything else than just software only installation
INVENTORY_LOCATION=/u01/oraInventory
oracle.install.option=CRS_SWONLY
ORACLE_BASE=/u01/oragrid/oraBase
oracle.install.asm.OSDBA=oinstall
oracle.install.asm.OSOPER=
oracle.install.asm.OSASM=asmadmin
NOTE:- The installer or configuration assistant fails if you do not correctly configure the response file. Also, ensure that your response file name has the .rsp suffix
Step9>Install the binaries in silent mode

Installing Software Binaries for Oracle Grid Infrastructure for a Standalone Server- Software Only

Log in as the software installation owner user and run the installer using a response file


$ /u01/oragrid/12.2.0.1/grid/gridSetup.sh -silent -noconfig -ignorePrereqFailure  -responseFile /u01/oragrid/12.2.0.1/grid/install/response/gridsetup.rsp
Note:- I am ignoring the PrereqFailure because I don't have sufficient RAM. Its not advised to do so as long as you are not aware of the consequences of the same.
Step10> Execute below script as root user when prompted by gridSetup.sh
# ./orainstRoot.sh
Changing permissions of /u01/oraInventory.
Adding read,write permissions for group.
Removing read,write,execute permissions for world.
Changing groupname of /u01/oraInventory to oinstall.
The execution of the script is complete.
# ./root.sh
Check /u01/oragrid/12.2.0.1/grid/install/root_test05_2018-05-30_10-22-04-433377022.log for the output of root script
# cat /u01/oragrid/12.2.0.1/grid/install/root_test05_2018-05-30_10-22-04-433377022.log
Performing root user operation.
The following environment variables are set as:
    ORACLE_OWNER= oragrid
    ORACLE_HOME=  /u01/oragrid/12.2.0.1/grid
   Copying dbhome to /usr/local/bin ...
   Copying oraenv to /usr/local/bin ...
   Copying coraenv to /usr/local/bin ...
Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root script.
Now product-specific root actions will be performed.
To configure Grid Infrastructure for a Cluster or Grid Infrastructure for a Stand-Alone Server execute the following command as oragrid user:
/u01/oragrid/12.2.0.1/grid/gridSetup.sh
This command launches the Grid Infrastructure Setup Wizard. The wizard also supports silent operation, and the parameters can be passed through the response file that is available in the installation media.
Note:- At this point Oracle Grid Infrastructure Binaries for Standalone Server is installed. Next step is to configure the Grid Infrastructure
Step11> Configure Grid Infrastructure for Standalone Server

Configuring Oracle Grid Infrastructure for a Standalone Serve After Software Only Installation

After successful installation of software you are ready to configure the GI for standalone server. Execute below command as root
# /u01/oragrid/12.2.0.1/grid/perl/bin/perl -I /u01/oragrid/12.2.0.1/grid/perl/lib -I /u01/oragrid/12.2.0.1/grid/crs/install /u01/oragrid/12.2.0.1/grid/crs/install/roothas.pl
Using configuration parameter file: /u01/oragrid/12.2.0.1/grid/crs/install/crsconfig_params
The log of current session can be found at:
  /u01/oragrid/oraBase/crsdata/test05/crsconfig/roothas_2018-06-04_01-13-50PM.log
2018/06/04 13:13:53 CLSRSC-363: User ignored prerequisites during installation
LOCAL ADD MODE
Creating OCR keys for user 'oragrid', privgrp 'oinstall'..
Operation successful.
LOCAL ONLY MODE
Successfully accumulated necessary OCR keys.
Creating OCR keys for user 'root', privgrp 'root'..
Operation successful.
CRS-4664: Node test05 successfully pinned.
2018/06/04 13:15:12 CLSRSC-330: Adding Clusterware entries to file 'oracle-ohasd.service'
CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'test05'
CRS-2673: Attempting to stop 'ora.evmd' on 'test05'
CRS-2677: Stop of 'ora.evmd' on 'test05' succeeded
CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'test05' has completed
CRS-4133: Oracle High Availability Services has been stopped.
CRS-4123: Oracle High Availability Services has been started.
test05     2018/06/04 13:17:14     /u01/oragrid/12.2.0.1/grid/cdata/test05/backup_20180604_131714.olr     0
2018/06/04 13:17:14 CLSRSC-327: Successfully configured Oracle Restart for a standalone server
Step12>As Grid owner update the node list
$cd /u01/oragrid/12.2.0.1/grid/oui/bin
$./runInstaller -updateNodeList ORACLE_HOME=/u01/oragrid/12.2.0.1/grid -defaultHomeName CLUSTER_NODES= CRS=TRUE

Starting Oracle Universal Installer...
Checking swap space: must be greater than 500 MB.   Actual 4095 MB    Passed
The inventory pointer is located at /etc/oraInst.loc
'UpdateNodeList' was successful.
$ crsctl check has
CRS-4638: Oracle High Availability Services is online
Step13>Apply Latest PSU
Next step is to patch GI software to get the latest version for AFD. Download and install the latest available patch for your environment
Step14>Add Listener
As final step it is recommend to create at least the default listener. After settting the environment (e.g. ORACLE_HOME, PATH etc), run netca with the default response file netca_typ.rsp.
export ORACLE_BASE=/u01/oragrid/oraBase
export ORACLE_HOME=/u01/oragrid/12.2.0.1/grid
export LD_LIBRARY_PATH=$ORACLE_HOME/lib:$LD_LIBRARY_PATH
export PATH=$ORACLE_HOME/bin:$PATH
$ netca -silent -responseFile $ORACLE_HOME/network/install/netca_typ.rsp
Parsing command line arguments:
    Parameter "silent" = true
    Parameter "responsefile" = /u01/oragrid/12.2.0.1/grid/network/install/netca_typ.rsp
Done parsing command line arguments.
Oracle Net Services Configuration:
Profile configuration complete.
Oracle Net Listener Startup:
    Listener started successfully.
Listener configuration complete.
Oracle Net Services configuration successful. The exit code is 0
$srvctl status listener
Listener LISTENER is enabled
Listener LISTENER is running on node(s): test05
Step15>Configure AFD and Prepare ASM Disks 
Follow the steps from Configure AFD (ASM Filter Driver) and Prepare Disks for ASM 
Step16>Create and Start ASM Instance
Run following command from GI/bin directory
cd /u01/oragrid/12.2.0.1/grid/bin
./asmca -silent -configureASM -diskString '/dev/xvd*' -sysAsmPassword ****** -asmsnmpPassword ******  -diskGroupName DG_TEST_DATA -diskList /dev/xvdg -redundancy EXTERNAL
Disk label(s) created successfully. Check /u01/oragrid/oraBase/cfgtoollogs/asmca/asmca-180605PM043225.log for details.
Disk groups created successfully. Check /u01/oragrid/oraBase/cfgtoollogs/asmca/asmca-180605PM043225.log for details.
Step17>Create Additional Diskgroups

How to Create DISK GROUP using asmca in silent mode

$asmca -silent -createDiskGroup -diskGroupName DG_TEST_FRA -diskList AFD:FRA01 -redundancy EXTERNAL

OR

$asmca -silent -createDiskGroup -diskString 'AFD:*' -diskGroupName DG_TEST_REDO -diskList AFD:REDO01 -redundancy EXTERNAL

Step18> Verify the Installation
$ crsctl status res -t
--------------------------------------------------------------------------------
Name           Target  State        Server                   State details
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
ora.DG_TEST_DATA.dg
               ONLINE  ONLINE       test05                 STABLE
ora.DG_TEST_FRA.dg
               ONLINE  ONLINE       test05                 STABLE
ora.DG_TEST_REDO.dg
               ONLINE  ONLINE       test05                 STABLE
ora.LISTENER.lsnr
               ONLINE  ONLINE       test05                 STABLE
ora.asm
               ONLINE  ONLINE       test05                 Started,STABLE
ora.ons
               OFFLINE OFFLINE      test05                 STABLE
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.cssd
      1        ONLINE  ONLINE       test05                 STABLE
ora.diskmon
      1        OFFLINE OFFLINE                               STABLE
ora.driver.afd
      1        ONLINE  ONLINE       test05                 STABLE
ora.evmd
      1        ONLINE  ONLINE       test05                 STABLE
--------------------------------------------------------------------------------
$ crsctl check has
CRS-4638: Oracle High Availability Services is online
$ srvctl status listener
Listener LISTENER is enabled
Listener LISTENER is running on node(s): test05
$srvctl status asm
ASM is running on test05
$ asmcmd lsdg
State    Type    Rebal  Sector  Logical_Sector  Block       AU  Total_MB  Free_MB  Req_mir_free_MB  Usable_file_MB  Offline_disks  Voting_files  Name
MOUNTED  EXTERN  N         512             512   4096  1048576     30720    30657                0           30657              0             N  DG_TEST_DATA/
MOUNTED  EXTERN  N         512             512   4096  1048576     30720    30666                0           30666              0             N  DG_TEST_FRA/
MOUNTED  EXTERN  N         512             512   4096  1048576     30720    30666                0           30666              0             N  DG_TEST_REDO/

Comments

Post a Comment

Popular posts from this blog

How to Power On/off Oracle Exadata Machine

<<Back to Exadata Main Page How to Power On/off Oracle Exadata Machine Oracle Exadata machines can be powered on/off either by pressing the power button on front of the server or by logging in to the ILOM interface. Powering on servers using  button on front of the server The power on sequence is as follows. 1. Start Rack, including switches  Note:- Ensure the switches have had power applied for a few minutes to complete power on  configuration before starting Exadata Storage Servers 2.Start Exadata Storage Servers  Note:- Ensure all Exadata Storage Servers complete the boot process before starting the   database servers 3. Start Database Servers Powering On Servers Remotely using ILOM The ILOM can be accessed using the Web console, the command-line interface (CLI), IPMI, or SNMP. For example, to apply power to server dm01cel01 using IPMI, where dm01cel01-ilom is the host name of the ILOM for the serve...
Post a Comment
Read more

ORA-28374: typed master key not found in wallet

<<Back to Oracle DB Security Main Page ORA-46665: master keys not activated for all PDBs during REKEY SQL> ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL ; ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL * ERROR at line 1: ORA-46665: master keys not activated for all PDBs during REKEY I found following in the trace file REKEY: Create Key in PDB 3 resulted in error 46658 *** 2019-02-06T15:27:04.667485+01:00 (CDB$ROOT(1)) REKEY: Activation of Key AdnU5OzNP08Qv1mIyXhP/64AAAAAAAAAAAAAAAAAAAAAAAAAAAAA in PDB 3 resulted in error 28374 REKEY: Keystore needs to be restored from the REKEY backup.Aborting REKEY! Cause: All this hassle started because I accidently deleted the wallet and all wallet backup files too and also forgot the keystore password. There was no way to restore the wallet back. Fortunately in my case the PDB which had encrypted data was supposed to be deco...
7 comments
Read more

How to Find VIP of an Oracle RAC Cluster

<<Back to Oracle RAC Main Page How to Find Out VIP of an Oracle RAC Cluster Login clusterware owner (oracle) and execute the below command to find out the VIP hostname used in Oracle RAC $ olsnodes -i node1     node1-vip node2     node2-vip OR $ srvctl config nodeapps -viponly Network 1 exists Subnet IPv4: 10.0.0.0/255.255.0.0/bondeth0, static Subnet IPv6: Ping Targets: Network is enabled Network is individually enabled on nodes: Network is individually disabled on nodes: VIP exists: network number 1, hosting node node1 VIP Name: node1-vip VIP IPv4 Address: 10.0.0.1 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes: VIP exists: network number 1, hosting node node2 VIP Name: node2-vip VIP IPv4 Address: 10.0.0.2 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes:
1 comment
Read more

ORA-46630: keystore cannot be created at the specified location

<<Back to DB Administration Main Page ORA-46630: keystore cannot be created at the specified location CDB011> ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "xxxxxxx"; ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "EncTest123" * ERROR at line 1: ORA-46630: keystore cannot be created at the specified location Cause  Creating a keystore at a location where there is already a keystore exists Solution To solve the problem, use a different location to create a keystore (use ENCRYPTION_WALLET_LOCATION in sqlnet.ora file to specify the keystore location), or move this ewallet.p12 file to some other location. Note: Oracle does not recommend deleting keystore file (ewallet.p12) that belongs to a database. If you have multiple keystores, you can choose to merge them rather than deleting either of them.
Post a Comment
Read more

ORA-65104: operation not allowed on an inactive pluggable database alter pluggable database open

<<Back to DB Administration Main Page ORA-65104: operation not allowed on an inactive pluggable database SQL> alter pluggable database TEST_CLON open; alter pluggable database TEST_CLON open * ERROR at line 1: ORA-65104: operation not allowed on an inactive pluggable database Cause The pluggable database status was UNUSABLE. It was still being created or there was an error during the create operation. A PDB can only be opened if it is successfully created and its status is marked as NEW in cdb_pdbs.status column SQL> select PDB_NAME,STATUS from cdb_pdbs; PDB_NAME             STATUS -------------------- --------------------------- PDB$SEED             NORMAL TEST_CLON            UNUSABLE Solution:  Drop the PDB and create it again. Related Posts How to Clone Oracle PDB (Pluggable Database) with in the Same Container
Post a Comment
Read more

ORA-16905: The member was not enabled yet

<<Back to Oracle DataGuard Main Page ORA-16905 Physical Standby Database is disabled DGMGRL> show configuration; Configuration - DG_ORCL1P   Protection Mode: MaxPerformance   Members:   ORCL1PP - Primary database     ORCL1PS - Physical standby database (disabled)       ORA-16905: The member was not enabled yet. Fast-Start Failover:  Disabled Configuration Status: SUCCESS   (status updated 58 seconds ago) DGMGRL> DGMGRL> enable database 'ORCL1PS'; Enabled. DGMGRL>  show configuration; Configuration - DG_ORCL1P   Protection Mode: MaxPerformance   Members:   ORCL1PP - Primary database     ORCL1PS - Physical standby database Fast-Start Failover:  Disabled Configuration Status: SUCCESS   (status updated 38 seconds ago)
Post a Comment
Read more

How to Switch Log File from All Instances in RAC

<<Back to Oracle RAC Main Page Switch The Log File of All Instances in Oracle RAC. In many cases you need to switch the logfile of the database. You can switch logfile using alter system switch logfile command but if you want to switch the logfile from all the instances you need to execute the command on all the instances individually and therefore you must login on all the instances. You can avoid this and switch logfile of all instances by just running the below command from any of the instance in RAC database SQL> ALTER SYSTEM SWITCH ALL LOGFILE;   System altered.
Post a Comment
Read more

Starting RMAN and connecting to Database

  <<Back to Oracle Backup & Recovery Main Page Starting RMAN and connecting to Database Starting RMAN and connecting to Database To start RMAN you need to set the environment and type rman and press enter. You can connect to database either using connect command or using command line option. using command line option localhost:$ export ORACLE_HOME=/ora_app/product/18c/dbd2 localhost:$ export PATH=$ORACLE_HOME/bin:$PATH localhost:$ export ORACLE_SID=ORCL1P localhost:$ rman target / Recovery Manager: Release 18.0.0.0.0 - Production on Sun Apr 4 08:11:01 2021 Version 18.11.0.0.0 Copyright (c) 1982, 2018, Oracle and/or its affiliates.  All rights reserved. connected to target database: ORCL1P (DBID=4215484517) RMAN> using connect option localhost:$ rman RMAN> connect target sys@ORCL1P  target database Password:******** connected to target database: ORCL1P (DBID=4215484517) NOTE: To use connect command you need to ensure that  you have proper TNS sentry...
Post a Comment
Read more

How to Attach to a Datapump Job and Check Status of Export or Import

<<Back to Oracle DATAPUMP Main Page How to check the progress of  export or import Jobs You can attach to the export/import  job using ATTACH parameter of oracle datapump utility. Once you are attached to the job you check its status by typing STATUS command. Let us see how Step1>  Find the Export/Import Job Name You can find the datapump job information from  DBA_DATAPUMP_JOBS or  USER_DATAPUMP_JOBS view. SQL> SELECT OWNER_NAME,JOB_NAME,OPERATION,JOB_MODE,STATE from DBA_DATAPUMP_JOBS; OWNER_NAME JOB_NAME                       OPERATION            JOB_MODE   STATE ---------- ------------------------------ -------------------- ---------- ---------- SYSTEM     SYS_EXPORT_FULL_02          ...
7 comments
Read more

ORA-46655: no valid keys in the file from which keys are to be imported

<<Back to DB Administration Main Page SQL> administer key management import encryption keys with secret "xxxx" from '/tmp/pdb02_tde_key.exp' force keystore identified by "xxxx" with backup; administer key management import encryption keys with secret "xxxxxx" from '/tmp/pdb02_tde_key.exp' force keystore identified by "xxxxxx" with backup * ERROR at line 1: ORA-46655: no valid keys in the file from which keys are to be imported Cause: Either the keys to be imported already present in the target database or correct container (PDB) is not set. Solution: In my case I got the error because I attempted to import the keys for newly plugged database PDB02 from CDB$ROOT container. To Solve the issue just switched to the correct container and re run the import. SQL> show con_name CON_NAME ------------------------------ CDB$ROOT <===Wrong Container selected  SQL> alter session set container=PDB02; Session alt...
Post a Comment
Read more