Configuring an Oracle RAC ASM Instance
If Oracle home of ASM instance and RAC instance are different, then make sure to separately configure an ASM instance on the physical RAC client. Make sure that the kfed utility resides under <Oracle ASM Home>/bin location. If the kfed utility do not exist, then build the kfed utility as shown in the following example:
- cd <Oracle ASM Home>/rdbms/lib
- make –f ins_rdbms.mk ikfed
Ensure that the ASM disk string is not empty.
Note: Create an ASM instance on the node on which you perform an IntelliSnap operation. The kfed utility needs to be configured on all the nodes.
This procedure assumes that you are using the first node for IntelliSnap and the first instance (+ASM1).
- From the CommCell Browser, navigate to Client Computers | <RAC Physical Client>.
- Right-click the <Oracle Agent>, point to All Tasks and then click New Instance (Oracle SID).
The Create New Instance dialog box appears.
- On the General tab, make the follow selections:
- In the Instance (ORACLE SID) box, type the Instance name (Ex:+ASM1).
- In the ORACLE USER box, type the user account name for ASM Instance.
- In the ORACLE HOME box, type the Oracle home path for ASM instance or click Browse to select the location.
- From the Storage Policy list, select the policy for the data of a default subclient.
- On the Details tab, make the following selections:
- In the Connect String box, type the Connect String. Use / as connect string.
- In the TNS_ADMIN Folder box, type the TNS ADMIN folder name. Alternatively, click Browse to select the location.
- On the Storage Device tab, from the Storage Policy used for user command backup of data list, select a storage policy.
- On the Log Backup tab, from the Storage Policy used for all Archive Log backups list, select a storage policy name.
- Click OK.
Last modified: 10/3/2018 5:56:23 PM