Administration of ASM Parameter File (SPFILE)

Administration of ASM Initialization Parameter File

In this post, we will see how to Backup, Copy and Move an Oracle ASM Initialization Parameter File. Here are some important asmcmd commands used to administer ASM SPFILE
spget    <=Retrieves the location of the Oracle ASM SPFILE
spbackup <=Backs up an Oracle ASM SPFILE to a backup file
spcopy <=Copies an Oracle ASM SPFILE or an Oracle ASM backup file from source location to an Oracle ASM SPFILE in the destination location
spmove    <=Moves an Oracle ASM SPFILE from source to destination and automatically updates the GPnP profile or OLR
spset    <=Set the location of the ORACLE ASM SPFILE in Grid Plug and Play (GPnP) profile or OLR

How to Backup ASM SPFile

ASMCMD> spget
+DG_TEST_DATA/ASM/ASMPARAMETERFILE/registry.253.978021167
ASMCMD>spbackup +DG_TEST_DATA/ASM/ASMPARAMETERFILE/registry.253.978021167 +DG_TEST_FRA/spfileBackASM.bak
OR
ASMCMD>spcopy +DG_TEST_DATA/ASM/ASMPARAMETERFILE/registry.253.978021167 +DG_TEST_FRA/spfileBackASM.cpy
You can copy SPFILE or backup SPFILE from DG to file system as well
ASMCMD> spbackup +DG_TEST_DATA/ASM/ASMPARAMETERFILE/registry.253.978021167 /u01/oragrid/spfile/spfileBackASM.bak
ASMCMD> spcopy +DG_TEST_DATA/ASM/ASMPARAMETERFILE/registry.253.978021167 /u01/oragrid/spfile/spfileBackASM.cpy

How to Backup ASM SPFile as Text

Login to asm instance as sysasm, find the spfile and backup as text file as shown
SQL> show parameter spfile;
NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
spfile                               string      +DG_TEST_DATA/ASM/ASMPARAMETER
                                                 FILE/registry.253.978021167
SQL>
SQL> create pfile='/u01/oragrid/spfile/spfile+ASM.ora' from spfile='+DG_TEST_DATA/ASM/ASMPARAMETERFILE/registry.253.978021167';
File created.

How to Migrate ASM SPfile

Migrating of ASM SPFile requires restart of ASM Instance and therefore leading to downtime

Migrating ASM SPfile from Diskgroup to File System

$ asmcmd spget
+DG_TEST_FRA/spfileASM.ora

$ asmcmd spmove +DG_TEST_FRA/spfileASM.ora /u01/oragrid/spfile/spfileASM.ora
ORA-15032: not all alterations performed
ORA-15028: ASM file '+DG_TEST_FRA/spfileASM.ora' not dropped; currently being accessed (DBD ERROR: OCIStmtExecute)

Note:- Ignore the error message. Since ASM instance is using the SPFILE I am migrating its unable to move it. But if you check it has already created the target file and updated the OLR

$ls -lrt /u01/oragrid/spfile/spfileASM.ora
-rw-r----- 1 oragrid oinstall 1536 Jun 8 13:41 /u01/oragrid/spfile/spfileASM.ora
$ asmcmd spget
/u01/oragrid/spfile/spfileASM.ora

Restart ASM instance to start with SPFILE located at file system

Note: You can also use asmcmd spcopy instead of spmove. while using asmcmd spcopy you need to specify -u to update the OLR or GPnP profile about the new location of the spfile. notice the difference in below pic

Migrating ASM SPfile File System to Diskgroup.

the procedure of migrating the ASMSPFILE from file system to ASM is same as from ASM to file system with the mandatory requirement that that COMPATIBLE.ASM attribute of Diskgroup going to hold the SPFILE must be =>11.2

How to Restore the ASM SPFILE from Backup

Note:- The steps will work only if the ASM instance is up and running.

If you have taken the SPFILE backup either of the ways described above (spcopy, spcopy or create pfile from spfile) you can restore the spfile back if you have lost or corrupted the current spfile

The procedure is very simple.

Find SPFILE backup known to ASM

$ asmcmd find --type ASMPARAMETERFILE '*' '*'
+DG_TEST_DATA/ASM/ASMPARAMETERFILE/REGISTRY.253.978270727
+DG_TEST_DATA/ASM/spfileASM.ora
+DG_TEST_FRA/ASM/ASMPARAMETERFILE/REGISTRY.253.978263057
+DG_TEST_FRA/spfileASM.ora

Decide the backup you want to use to restore spfile and ensure the file is physically present

$ asmcmd spset +DG_TEST_DATA/ASM/spfileASM.ora
$ asmcmd spget
+DG_TEST_DATA/ASM/spfileASM.ora

Bounce the ASM instance

How to Restore ASM SPFILE In case ASM is completely down

In this scenario even the backup available on ASM diskgroup will no more be accessible and you can recreate the spfile from pfile if you have one

Else you locate the ASM alert log and find the latest restart entry in alert log and copy the non default parameter. Create a Pfile with having these parameters and then create spfile from this pfile

Comments

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 server to be powered on, run the

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:

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

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)

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.

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

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.

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 for database (ORCL

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 EXPORT FULL EXECUTING OR You can also find the job name for export/import in logfile in beginning itself. Step2>Attach to the Job and check status One you get the Export/Import Job Name attach the job and check its status. You can attach or det

ORA-15040: diskgroup is incomplete

<<Back to Oracle ASM Main Page ORA-15040: diskgroup is incomplete SQL> startup ORA-00099: warning: no parameter file specified for ASM instance ASM instance started Total System Global Area 1140850688 bytes Fixed Size 8629704 bytes Variable Size 1107055160 bytes ASM Cache 25165824 bytes ORA-15110: no diskgroups mounted Reason: The reason of this error is simply the ASM is not able to find the some or all the disks. Solution: Investigate and make all the disks available to ASM to mount the disk group. Make sure the disks has proper permissions. If you are using AFD check following services are online oracleacfs oracleadvm oracleoks oracleafd Source of Problem : Issue started after restart of the server After restarting the server when I tried to start the ASM instance its started throwing error. ORA-15110: no diskgroups mounted Investigation in my Case Step1> ASM Logfile Scanning Looked i

Online DBA

Search This Blog