Thursday 21 June 2018

How to Login AWS Console

Overview

 Amazon Web Services (AWS) is a secure cloud services platform, offering compute power, database storage, evolving cloud computing platform provided by Amazon, content delivery and other functionality to help businesses scale and grow.

 Amazon Relational Database Service (Amazon RDS) is a web service that makes it easier to set up, operate, and scale a relational database in the cloud. It provides cost-efficient, resizable capacity for an industry-standard relational database and manages common database administration tasks.

To know more about Amazon RDS please click here AWS RDS

 In this article we will demonstrate how to login to AWS Console

Steps to Login AWS console

  • Open link in browser and click on Sign in to the console

  • Enter your Credentials

  • After click on sign in, AWS console open as follows
  • Click on services then RDS
We are on the AWS RDS page.
conclusion

 In this blog we have learned how to login to AWS console then from console to Relational Database service(RDS).
Next, How to Create AWS RDS Instance...
By
Name : omer
Designation : Senior Database Engineer
Organization: NetSoftMate IT Solutions. 
By at 89 comments:
Labels: , , , , , , , ,

Sunday 10 June 2018

Oracle SuperCluster Health Check Using Exachk Utility

Oracle provides "Exachk" utility to conduct a comprehensive Health Check on Oracle SuperCluster to validate hardware, firmware and configuration. Exachk Utility is available for Oracle Engineered Systems such as Exadata (V2 and above), Exalogic, Exalytics, SuperCluster, MiniCluster, ZDLRA & Big Data. 

 When Exachk is run from the primary LDOM as user 'root' it will discover and run exachk utility for each component:
  • Configuration checks for Compute nodes, Storage cells and InfiniBand Switches
  • Grid Infrastructure, Database and ASM and Operating System software checks

When Exachk is run in a Database zone or Virtualized environment it will collect data for:
  • All RAC Node
  • All Database Instance
  • Grid Infrastructure

You can also run Exachk on a specific component such as:
  • Database Servers
  • Storage Cells
  • Infiniband Switches
  • Grid Infrastructure, Database & ASM and so on

It is recommended to run Exachk as root user and have SSH equivalence setup in the SuperCluster. But you can run Exachk as ordinary user and without having root ssh setup.

 It is recommended to execute the latest exachk at the following situation:
  • Monthly
  • Before any planned maintenance activity
  • Immediately after completion of planned maintenance activity
  • Immediately after an outage or incident

Exachk Binary and output file location:
  • Default Exachk Location: /opt/oracle.SupportTools/exachk
  • Defautl Exachk Output Location: /opt/oracle.SupportTools/exachk


Courtesy Oracle


Steps to Deploy and Execute Exachk utility on SuperCluster
  • Download Latest Exachk Utility
You can download the latest Exachk from MOS note 1070954.1

  • Download deploy_exachk.sh script to deploy and install Exachk in all Primary LDOM and in each Zone

  • Copy the downloaded Exachk utility and deploy_exachk.sh into /opt/oracle.SupportTools
# cd /opt/oracle.SupportTools
# mv exachk Exachk-bkp

  • Deploy Exachk as follows
# cd /opt/oracle.SupportTools/
# ./deploy_exachk.sh exachk.zip
# ls -ltr
# cd exachk
# ls -l exachk

 As of writing the latest Exachk available is 18.2.0_20180518

  • Verify Exachk Version on LDOM
# cd /opt/oracle.SupportTools/exachk
# ./exachk -v

  • To verify Exachk version on all zones in a LDOM
# zoneadm list | grep -v global > zone_list
# hostname >> zone_list
# /opt/oracle.supercluster/bin/dcli -g zone_list -l root /opt/oracle.SupportTools/exachk/exachk -v

 Note: root RSA keys should be set up for SSH

  • Execute Exachk on Primary LDOM or Global Zone
# cd /opt/oracle.SupportTools/exachk
# ./exachk

  • Execute Exachk in non-global zone local zone
Login to non-global zone local zone using zlogin and execute the following commands

 # zlogin <hostname>
# cd /opt/oracle.SupportTools/exachk
# ./exachk

 Important Note: In zones there is currently an issue with discovery, and so one must set the RAT_ORACLE_HOME and RAT_GRID_HOME environment variables in some cases.
Conclusion
In this article we have learned to perform Oracle SuperCluster Stack Health Check using Exachk utility. Exachk Utility is available for Oracle Engineered Systems such as Exadata (V2 and above), Exalogi, Exalytics, SuperCluster, MiniCluster, ZDLRA & Big Data.

By at 2 comments:
Labels: , , , , , , , , , , , , ,

Wednesday 6 June 2018

ASRexacheck Utility - Validate Exadata Oracle ASR Deployment

ASRexacheck utility can be executed to verify the ASR deployment. Oracle Auto Service Request (ASR) is a secure, scalable, customer-installable software feature of warranty and Oracle Support Services that provides auto-case generation when common hardware component faults occur.

 It is important to note that, ASR is not a system management or monitoring tool. It is developed & designed to open Oracle Automatic Service Requests when specific hardware faults are detected on Oracle products that are qualified for ASR. Oracle Exadata Database Machine is a qualified production for Oracle ASR.

 You can execute ASRexacheck in any of the following 2 ways:
  • As part of the Oracle Exadata Database Machine exachk
  • Stand-alone mode on a single node or multiple nodes

In this article we will demonstrate how to execute ASRexacheck on in Stand-alone mode on a single server and mutliple servers using dcli.
  • Ensure that the ASRexacheck verison is 4.x. If is is older than 4.x, then download the latest ASRexacheck from the MOS note below.

Engineered Systems ASR Configuration Check tool (asrexacheck version 4.x) (Doc ID 2103715.1)

  • ASRexacheck Download and & Upgrade steps
    • Download the asrexacheck zip file from the MOS note.
    • Copy the asrexacheck zip to the following directory: /opt/oracle.SupportTools/
    • Unzip the asrexacheck utility
          # cd /opt/oracle.SupportTools/
          # unzip asrexacheck_43.zip
    • Change the running permissions to execute
                    # chmod 755 /opt/oracle.SupportTools/asrexacheck
    • Verify the asrexacheck version
                    # /opt/oracle.SupportTools/asrexacheck –v
  • ASRexacheck execution On a single Exadata server

[root@dm01db01 oracle.SupportTools]# /opt/oracle.SupportTools/asrexacheck
asrexacheck version: 4.0
Current time: 2018-04-09 10:42:51

 ================================================================================
SYSTEM CONFIGURATION
================================================================================
Product name           : Exadata X5-2
Product serial         : AK003XXXXX
Component name         : ORACLE SERVER X5-2
Component serial       : 1546XX111X
Engineered System type : Exadata
Server type            : COMPUTE
Image version          : 18.1.4.0.0.180125.3
OS IP Address          : 10.10.10.1
OS Hostname            : dm01db01
OS version             : 4.1.12-94.7.8.el6uek.x86_64
ILOM IP Address        : 10.10.10.14
ILOM Hostname          : dm01db01-ilom
ILOM version           : 4.0.0.24

 ================================================================================
NETWORK
================================================================================
Interface  IP Address                      Hostname        Route   fromIP
--------------------------------------------------------------------------------
bondeth0   10.20.16.1                     dm0101          NO
eth0       10.10.10.1                     dm01db01        YES

 ================================================================================
ASR
================================================================================
Destination     Hostname        Rule Type  DBMCLI Port Level   Community Version
--------------------------------------------------------------------------------
10.10.10.1     dm01db01          1               8162 minor   LocalMSV3user       3
192.168.10.1  oragwserver                   YES   162           public
192.168.10.1  oragwserver        2                162 minor     public      2c

 [OK] Exactly one OS and ILOM IP coincide (192.168.10.1)
* Validation:
[OK] OS Test event sent to 192.168.10.1:162
[OK] ILOM Test event sent to 192.168.10.1:162

 Time elapsed script execution: 00:04:44
Zipfile /var/log/asrexacheck/asrexacheck_dm01db01_20180409T154251.zip of the outputs created
  • ASRexacheck execution on all Exadata Compute nodes

[root@dm01db01 oracle.SupportTools]# dcli -g ~/dbs_group -l root '/opt/oracle.SupportTools/asrexacheck'
dm01db01: asrexacheck version: 4.0
dm01db01: Current time: 2018-04-09 10:42:51
dm01db01:
dm01db01: ================================================================================
dm01db01: SYSTEM CONFIGURATION
dm01db01: ================================================================================
dm01db01: Product name           : Exadata X5-2
dm01db01: Product serial         : AK003XXXXX
dm01db01: Component name         : ORACLE SERVER X5-2
dm01db01: Component serial       : 1546XX111X
dm01db01: Engineered System type : Exadata
dm01db01: Server type            : COMPUTE
dm01db01: Image version          : 18.1.4.0.0.180125.3
dm01db01: OS IP Address          : 10.10.10.1
dm01db01: OS Hostname            : dm01db01
dm01db01: OS version             : 4.1.12-94.7.8.el6uek.x86_64
dm01db01: ILOM IP Address        : 10.10.10.14
dm01db01: ILOM Hostname          : dm01db01-ilom
dm01db01: ILOM version           : 4.0.0.24
dm01db01:
dm01db01: ================================================================================
dm01db01: NETWORK
dm01db01: ================================================================================
dm01db01: Interface  IP Address                      Hostname        Route   fromIP
dm01db01: --------------------------------------------------------------------------------
dm01db01: bondeth0   10.20.16.1                     dm0101          NO
dm01db01: eth0       10.10.10.1                     dm01db01        YES
dm01db01:
dm01db01: ================================================================================
dm01db01: ASR
dm01db01: ================================================================================
dm01db01: Destination     Hostname        Rule Type  DBMCLI Port Level   Community Version
dm01db01: --------------------------------------------------------------------------------
dm01db01: 10.10.10.1     dm01db01          1               8162 minor   LocalMSV3user       3
dm01db01: 192.168.10.1  oragwserver                   YES   162           public
dm01db01: 192.168.10.1  oragwserver        2                162 minor     public      2c
dm01db01:
dm01db01: [OK] Exactly one OS and ILOM IP coincide (192.168.10.1)
dm01db01: * Validation:
dm01db01: [OK] OS Test event sent to 192.168.10.1:162
dm01db01: [OK] ILOM Test event sent to 192.168.10.1:162
dm01db01:
dm01db01: Time elapsed script execution: 00:04:44
dm01db01: Zipfile /var/log/asrexacheck/asrexacheck_dm01db01_20180409T154251.zip of the outputs created
dm01db02: asrexacheck version: 4.0
dm01db02: Current time: 2018-04-09 10:42:51
dm01db02:
dm01db02: ================================================================================
dm01db02: SYSTEM CONFIGURATION
dm01db02: ================================================================================
dm01db02: Product name           : Exadata X5-2
dm01db02: Product serial         : AK003XXXXX
dm01db02: Component name         : ORACLE SERVER X5-2
dm01db02: Component serial       : 1546XX11XX
dm01db02: Engineered System type : Exadata
dm01db02: Server type            : COMPUTE
dm01db02: Image version          : 18.1.4.0.0.180125.3
dm01db02: OS IP Address          : 10.10.10.2
dm01db02: OS Hostname            : dm01db02
dm01db02: OS version             : 4.1.12-94.7.8.el6uek.x86_64
dm01db02: ILOM IP Address        : 10.10.10.15
dm01db02: ILOM Hostname          : dm01db02-ilom
dm01db02: ILOM version           : 4.0.0.24
dm01db02:
dm01db02: ================================================================================
dm01db02: NETWORK
dm01db02: ================================================================================
dm01db02: Interface  IP Address                      Hostname        Route   fromIP
dm01db02: --------------------------------------------------------------------------------
dm01db02: bondeth0   10.20.16.3                     dm0102          NO
dm01db02: eth0       10.10.10.2                     dm01db02        YES
dm01db02:
dm01db02: ================================================================================
dm01db02: ASR
dm01db02: ================================================================================
dm01db02: Destination     Hostname        Rule Type  DBMCLI Port Level   Community Version
dm01db02: --------------------------------------------------------------------------------
dm01db02: 10.10.10.2     dm01db02          1               8162 minor   LocalMSV3user       3
dm01db02: 192.168.10.1  oragwserver                   YES   162           public
dm01db02: 192.168.10.1  oragwserver        2                162 minor     public      2c
dm01db02:
dm01db02: [OK] Exactly one OS and ILOM IP coincide (192.168.10.1)
dm01db02: * Validation:
dm01db02: [OK] OS Test event sent to 192.168.10.1:162
dm01db02: [OK] ILOM Test event sent to 192.168.10.1:162
dm01db02:
dm01db02: Time elapsed script execution: 00:04:46
dm01db02: Zipfile /var/log/asrexacheck/asrexacheck_dm01db02_20180409T154251.zip of the outputs created
dm01db03: asrexacheck version: 4.0
dm01db03: Current time: 2018-04-09 10:42:51
dm01db03:
dm01db03: ================================================================================
dm01db03: SYSTEM CONFIGURATION
dm01db03: ================================================================================
dm01db03: Product name           : Exadata X5-2
dm01db03: Product serial         : AK003XXXXX
dm01db03: Component name         : ORACLE SERVER X5-2
dm01db03: Component serial       : 1547XX10XX
dm01db03: Engineered System type : Exadata
dm01db03: Server type            : COMPUTE
dm01db03: Image version          : 18.1.4.0.0.180125.3
dm01db03: OS IP Address          : 10.10.10.3
dm01db03: OS Hostname            : dm01db03
dm01db03: OS version             : 4.1.12-94.7.8.el6uek.x86_64
dm01db03: ILOM IP Address        : 10.10.10.16
dm01db03: ILOM Hostname          : dm01db03-ilom
dm01db03: ILOM version           : 4.0.0.24
dm01db03:
dm01db03: ================================================================================
dm01db03: NETWORK
dm01db03: ================================================================================
dm01db03: Interface  IP Address                      Hostname        Route   fromIP
dm01db03: --------------------------------------------------------------------------------
dm01db03: bondeth0   10.20.16.5                     dm0103          NO
dm01db03: eth0       10.10.10.3                     dm01db03        YES
dm01db03:
dm01db03: ================================================================================
dm01db03: ASR
dm01db03: ================================================================================
dm01db03: Destination     Hostname        Rule Type  DBMCLI Port Level   Community Version
dm01db03: --------------------------------------------------------------------------------
dm01db03: 10.10.10.3     dm01db03          1               8162 minor   LocalMSV3user       3
dm01db03: 192.168.10.1  oragwserver                   YES   162           public
dm01db03: 192.168.10.1  oragwserver        2                162 minor     public      2c
dm01db03:
dm01db03: [OK] Exactly one OS and ILOM IP coincide (192.168.10.1)
dm01db03: * Validation:
dm01db03: [OK] OS Test event sent to 192.168.10.1:162
dm01db03: [OK] ILOM Test event sent to 192.168.10.1:162
dm01db03:
dm01db03: Time elapsed script execution: 00:04:43
dm01db03: Zipfile /var/log/asrexacheck/asrexacheck_dm01db03_20180409T154251.zip of the outputs created
  • At the end of successful ASRexacheck execution, you will receive 2 Test ASR emails, one from Management host and another from Management ILOM host. If you don't receive the Test ASR emails then you must work with Oracle ASR Management team to resolve the ASR Manager issue.




  • You can also execute ASRexacheck on Exadata Storage cells using below commands.

[root@dm01cel01 ~]# /opt/oracle.SupportTools/asrexacheck
[root@dm01db01 ~]# dcli -g ~/cell_group -l root '/opt/oracle.SupportTools/asrexacheck'

 Conclusion

 In this article we have learned how to verify ASR deployment using ASRexacheck utility. ASR is not a monitoring tool, it is designed to open ASR when specific hardware faults are detected on Oracle products that are qualified for ASR. Oracle Exadata Database Machine is a qualified production for Oracle ASR.

By at No comments:
Labels: , , , , , , , , , , , , , , ,

Tuesday 5 June 2018

Rename Oracle ASM Disk Group On Exadata

When Oracle ACS build Exadata Database Machine, they use the OEDA file that you sent them over for Exadata Install. The Exadata is built with default ASM Disk Group name DATAC1, RECOC1 & DBFS_DG. If you want to rename the DATAC1 and RECOC1 to something different to match your Organization standards you can do that by using the Oracle renamedg utility. The number Database version required to rename an ASM Disk Group is 11.2.

 In this article we will demonstrate how to rename ASM Disk Group on Exadata Database Machine running Oracle Database 11.2

 Here we want to change the following ASM Disk Group Names:
DATAC1 to DATA
RECOC1 to RECO

 Steps to rename ASM Disk Group
  • Get the Database version

ORACLE_SID = [+ASM1] ? dbm011
The Oracle base remains unchanged with value /u01/app/oracle

 [oracle@dm01db01 ~]$ sqlplus / as sysdba

 SQL*Plus: Release 11.2.0.4.0 Production on Thu May 24 16:36:34 2018
Copyright (c) 1982, 2013, Oracle.  All rights reserved.

 Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options

 SQL> select * from v$version;

 BANNER
--------------------------------------------------------------------------------
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
PL/SQL Release 11.2.0.4.0 - Production
CORE    11.2.0.4.0      Production
TNS for Linux: Version 11.2.0.4.0 - Production
NLSRTL Version 11.2.0.4.0 - Production

  • Connect to asmcmd and make a note of the Disk Group Names

[oracle@dm01db01 ~]$ . oraenv

 ORACLE_SID = [oracle] ? +ASM1
The Oracle base has been set to /u01/app/oracle

 [oracle@dm01db01 ~]$ asmcmd -p

 ASMCMD [+] > lsdg
State    Type    Rebal  Sector  Block       AU   Total_MB    Free_MB  Req_mir_free_MB  Usable_file_MB  Offline_disks  Voting_files  Name
MOUNTED  HIGH    N         512   4096  4194304  272154624  271558968          6479872        88359698              0             N  DATAC1/
MOUNTED  HIGH    N         512   4096  4194304    2404640    2402468            68704          777921              0             Y  DBFS_DG/
MOUNTED  NORMAL  N         512   4096  4194304   45389568   45386648           540352        22423148              0             N  RECOC1/

  • Check the versions

ASMCMD [+] > lsct
DB_Name  Status     Software_Version  Compatible_version  Instance_Name  Disk_Group
+ASM     CONNECTED        11.2.0.4.0          11.2.0.4.0  +ASM1          DBFS_DG
DBM01    CONNECTED        11.2.0.4.0          11.2.0.4.0  dbm011         DATAC1

  • Check the database status

[oracle@dm01db01 ~]$ srvctl status database -d dbm01
Instance dbm011 is running on node dm01db01
Instance dbm012 is running on node dm01db02
Instance dbm013 is running on node dm01db03
Instance dbm014 is running on node dm01db04

  • Make a note of the control files, Datafiles, Redo logfiles before stopping the database.

SQL> select name from v$controlfile;
SQL> select name from v$datafile;
SQL> select member from v$logfile;
SQL> select * from v$block_change_tracking;

  • Stop database database

[oracle@dm01db01 ~]$ srvctl stop database -d dbm01

 [oracle@dm01db01 ~]$ srvctl status database -d dbm01
Instance dbm011 is not running on node dm01db01
Instance dbm012 is not running on node dm01db02
Instance dbm013 is not running on node dm01db03
Instance dbm014 is not running on node dm01db04

  • Umount the ASM disk group(s) that you want to rename. Connect to ASM command prompt and umount the disk group. umount the disk group from all nodes.

ASMCMD [+] > umount DATAC1

 ASMCMD [+] > umount RECOC1

 ASMCMD [+] > lsdg
State    Type  Rebal  Sector  Block       AU  Total_MB  Free_MB  Req_mir_free_MB  Usable_file_MB  Offline_disks  Voting_files  Name
MOUNTED  HIGH  N         512   4096  4194304   2404640  2402468            68704          777921              0             Y  DBFS_DG/

 Note: If you don't stop the databases using ASM disk group you will get the following error message:

 ASMCMD [+] > umount DATAC1
ORA-15032: not all alterations performed
ORA-15027: active use of diskgroup "DATAC1" precludes its dismount (DBD ERROR: OCIStmtExecute)

 *** Repeat the above steps on all the remaining nodes in the Cluster***

 [oracle@dm01db01 ~]$ ssh dm01db02
Last login: Thu May 17 15:23:31 2018 from dm01db01

 [oracle@dm01db02 ~]$ . oraenv
ORACLE_SID = [oracle] ? +ASM2
The Oracle base has been set to /u01/app/oracle

 [oracle@dm01db02 ~]$ asmcmd lsdg
State    Type    Rebal  Sector  Block       AU   Total_MB    Free_MB  Req_mir_free_MB  Usable_file_MB  Offline_disks  Voting_files  Name
MOUNTED  HIGH    N         512   4096  4194304  272154624  271558968          6479872        88359698              0             N  DATAC1/
MOUNTED  HIGH    N         512   4096  4194304    2404640    2402468            68704          777921              0             Y  DBFS_DG/
MOUNTED  NORMAL  N         512   4096  4194304   45389568   45385040           540352        22422344              0             N  RECOC1/

 [oracle@dm01db02 ~]$ asmcmd umount DATAC1

 [oracle@dm01db02 ~]$ asmcmd umount RECOC1

 [oracle@dm01db02 ~]$ asmcmd lsdg
State    Type  Rebal  Sector  Block       AU  Total_MB  Free_MB  Req_mir_free_MB  Usable_file_MB  Offline_disks  Voting_files  Name
MOUNTED  HIGH  N         512   4096  4194304   2404640  2402468            68704          777921              0             Y  DBFS_DG/

 [oracle@dm01db01 ~]$ ssh dm01db03
Last login: Thu May 17 15:23:31 2018 from dm01db01

 [oracle@dm01db03 ~]$ . oraenv
ORACLE_SID = [oracle] ? +ASM3
The Oracle base has been set to /u01/app/oracle

 [oracle@dm01db03 ~]$ asmcmd umount DATAC1

 [oracle@dm01db03 ~]$ asmcmd umount RECOC1

 [oracle@dm01db03 ~]$ asmcmd lsdg
State    Type  Rebal  Sector  Block       AU  Total_MB  Free_MB  Req_mir_free_MB  Usable_file_MB  Offline_disks  Voting_files  Name
MOUNTED  HIGH  N         512   4096  4194304   2404640  2402468            68704          777921              0             Y  DBFS_DG/

 [oracle@dm01db01 ~]$ ssh dm01db04
Last login: Thu May 17 15:23:31 2018 from dm01db01

 [oracle@dm01db04 ~]$ . oraenv
ORACLE_SID = [oracle] ? +ASM4
The Oracle base has been set to /u01/app/oracle

 [oracle@dm01db04 ~]$ asmcmd umount DATAC1

 [oracle@dm01db04 ~]$ asmcmd umount RECOC1

 [oracle@dm01db04 ~]$ asmcmd lsdg
State    Type  Rebal  Sector  Block       AU  Total_MB  Free_MB  Req_mir_free_MB  Usable_file_MB  Offline_disks  Voting_files  Name
MOUNTED  HIGH  N         512   4096  4194304   2404640  2402468            68704          777921              0             Y  DBFS_DG/

  • Verify that renamedg is in PATH

[oracle@dm01db01 ~]$ which renamedg
/u01/app/11.2.0.4/grid/bin/renamedg

  • As owner of the Grid Infrastruture software execute the renamdg command. Here the owner of GI home is 'oracle' user. First I am renaming DATAC1 disk group to DATA

[oracle@dm01db01 ~]$ renamedg phase=both dgname=DATAC1 newdgname=DATA verbose=true

 NOTE: No asm libraries found in the system
Parsing parameters..
Parameters in effect:

          Old DG name       : DATAC1
         New DG name       : DATA
         Phases            :
                 Phase 1
                 Phase 2
         Discovery str      : (null)
         Clean              : TRUE
         Raw only           : TRUE
renamedg operation: phase=both dgname=DATAC1 newdgname=DATA verbose=true
Executing phase 1
Discovering the group
Performing discovery with string:
Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_02_dm01cel01 with disk number:74 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_11_dm01cel01 with disk number:83 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_07_dm01cel01 with disk number:79 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_04_dm01cel01 with disk number:76 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_05_dm01cel01 with disk number:77 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_10_dm01cel01 with disk number:82 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_06_dm01cel01 with disk number:78 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_03_dm01cel01 with disk number:75 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_00_dm01cel01 with disk number:72 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_08_dm01cel01 with disk number:80 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_01_dm01cel01 with disk number:73 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_09_dm01cel01 with disk number:81 and timestamp (33068591 612262912)
...
...
...
Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_09_dm01cel07 with disk number:69 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_03_dm01cel07 with disk number:63 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_06_dm01cel07 with disk number:66 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_08_dm01cel07 with disk number:68 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_04_dm01cel07 with disk number:64 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_07_dm01cel07 with disk number:67 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_01_dm01cel07 with disk number:61 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_05_dm01cel07 with disk number:65 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_02_dm01cel07 with disk number:62 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_00_dm01cel07 with disk number:60 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_11_dm01cel07 with disk number:71 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_10_dm01cel07 with disk number:70 and timestamp (33068591 612262912)
Checking for hearbeat...
Re-discovering the group
Performing discovery with string:
Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_02_dm01cel01 with disk number:74 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_11_dm01cel01 with disk number:83 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_07_dm01cel01 with disk number:79 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_04_dm01cel01 with disk number:76 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_05_dm01cel01 with disk number:77 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_10_dm01cel01 with disk number:82 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_06_dm01cel01 with disk number:78 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_03_dm01cel01 with disk number:75 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_00_dm01cel01 with disk number:72 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_08_dm01cel01 with disk number:80 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_01_dm01cel01 with disk number:73 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_09_dm01cel01 with disk number:81 and timestamp (33068591 612262912)
...
...
...
Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_09_dm01cel07 with disk number:69 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_03_dm01cel07 with disk number:63 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_06_dm01cel07 with disk number:66 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_08_dm01cel07 with disk number:68 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_04_dm01cel07 with disk number:64 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_07_dm01cel07 with disk number:67 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_01_dm01cel07 with disk number:61 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_05_dm01cel07 with disk number:65 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_02_dm01cel07 with disk number:62 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_00_dm01cel07 with disk number:60 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_11_dm01cel07 with disk number:71 and timestamp (33068591 612262912)
Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_10_dm01cel07 with disk number:70 and timestamp (33068591 612262912)
Checking if the diskgroup is mounted or used by CSS
Checking disk number:74
Checking disk number:83
Checking disk number:79
Checking disk number:76
Checking disk number:77
Checking disk number:82
Checking disk number:78
Checking disk number:75
Checking disk number:72
Checking disk number:80
Checking disk number:73
Checking disk number:81
Checking disk number:69
Checking disk number:63
Checking disk number:66
Checking disk number:68
Checking disk number:64
Checking disk number:67
Checking disk number:61
Checking disk number:65
Checking disk number:62
Checking disk number:60
...
...
Generating configuration file..
Completed phase 1
Executing phase 2
Looking for o/192.168.10.9;192.168.10.10/DATAC1_CD_02_dm01cel01
Modifying the header
Looking for o/192.168.10.9;192.168.10.10/DATAC1_CD_11_dm01cel01
Modifying the header
Looking for o/192.168.10.9;192.168.10.10/DATAC1_CD_07_dm01cel01
Modifying the header
Looking for o/192.168.10.9;192.168.10.10/DATAC1_CD_04_dm01cel01
Modifying the header
Looking for o/192.168.10.9;192.168.10.10/DATAC1_CD_05_dm01cel01
Modifying the header
Looking for o/192.168.10.9;192.168.10.10/DATAC1_CD_10_dm01cel01
Modifying the header
Looking for o/192.168.10.9;192.168.10.10/DATAC1_CD_06_dm01cel01
Modifying the header
Looking for o/192.168.10.9;192.168.10.10/DATAC1_CD_03_dm01cel01
Modifying the header
Looking for o/192.168.10.9;192.168.10.10/DATAC1_CD_00_dm01cel01
Modifying the header
Looking for o/192.168.10.9;192.168.10.10/DATAC1_CD_08_dm01cel01
Modifying the header
Looking for o/192.168.10.9;192.168.10.10/DATAC1_CD_01_dm01cel01
Modifying the header
...
...
Modifying the header
Completed phase 2
Terminating kgfd context 0x7f9d346240a0

  • Now rename RECOC1 ASM disk group to RECO using renamdg command

[oracle@dm01db01 ~]$ renamedg phase=both dgname=RECOC1 newdgname=RECO verbose=true

 NOTE: No asm libraries found in the system
Parsing parameters..
Parameters in effect:

          Old DG name       : RECOC1
         New DG name       : RECO
         Phases            :
                 Phase 1
                 Phase 2
         Discovery str      : (null)
         Clean              : TRUE
         Raw only           : TRUE
renamedg operation: phase=both dgname=RECOC1 newdgname=RECO verbose=true
Executing phase 1
Discovering the group
Performing discovery with string:
Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_03_dm01cel01 with disk number:75 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_04_dm01cel01 with disk number:76 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_05_dm01cel01 with disk number:77 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_00_dm01cel01 with disk number:72 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_10_dm01cel01 with disk number:82 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_07_dm01cel01 with disk number:79 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_02_dm01cel01 with disk number:74 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_01_dm01cel01 with disk number:73 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_11_dm01cel01 with disk number:83 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_08_dm01cel01 with disk number:80 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_09_dm01cel01 with disk number:81 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_06_dm01cel01 with disk number:78 and timestamp (33068591 628813824)
...
...
Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_01_dm01cel07 with disk number:61 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_08_dm01cel07 with disk number:68 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_06_dm01cel07 with disk number:66 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_11_dm01cel07 with disk number:71 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_10_dm01cel07 with disk number:70 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_05_dm01cel07 with disk number:65 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_00_dm01cel07 with disk number:60 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_03_dm01cel07 with disk number:63 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_09_dm01cel07 with disk number:69 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_07_dm01cel07 with disk number:67 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_02_dm01cel07 with disk number:62 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_04_dm01cel07 with disk number:64 and timestamp (33068591 628813824)
Checking for hearbeat...
Re-discovering the group
Performing discovery with string:
Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_03_dm01cel01 with disk number:75 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_04_dm01cel01 with disk number:76 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_05_dm01cel01 with disk number:77 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_00_dm01cel01 with disk number:72 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_10_dm01cel01 with disk number:82 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_07_dm01cel01 with disk number:79 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_02_dm01cel01 with disk number:74 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_01_dm01cel01 with disk number:73 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_11_dm01cel01 with disk number:83 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_08_dm01cel01 with disk number:80 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_09_dm01cel01 with disk number:81 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_06_dm01cel01 with disk number:78 and timestamp (33068591 628813824)
...
...
Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_01_dm01cel07 with disk number:61 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_08_dm01cel07 with disk number:68 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_06_dm01cel07 with disk number:66 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_11_dm01cel07 with disk number:71 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_10_dm01cel07 with disk number:70 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_05_dm01cel07 with disk number:65 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_00_dm01cel07 with disk number:60 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_03_dm01cel07 with disk number:63 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_09_dm01cel07 with disk number:69 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_07_dm01cel07 with disk number:67 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_02_dm01cel07 with disk number:62 and timestamp (33068591 628813824)
Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_04_dm01cel07 with disk number:64 and timestamp (33068591 628813824)
...
...
Checking if the diskgroup is mounted or used by CSS
Checking disk number:75
Checking disk number:76
Checking disk number:77
Checking disk number:72
Checking disk number:82
Checking disk number:79
Checking disk number:74
Checking disk number:73
Checking disk number:83
Checking disk number:80
Checking disk number:81
Checking disk number:78
Checking disk number:61
Checking disk number:68
Checking disk number:66
Checking disk number:71
Checking disk number:70
Checking disk number:65
Checking disk number:60
Checking disk number:63
Checking disk number:69
Checking disk number:67
Checking disk number:62
Checking disk number:64
Checking disk number:49
...
...
Generating configuration file..
Completed phase 1
Executing phase 2
Looking for o/192.168.10.9;192.168.10.10/RECOC1_CD_03_dm01cel01
Modifying the header
Looking for o/192.168.10.9;192.168.10.10/RECOC1_CD_04_dm01cel01
Modifying the header
Looking for o/192.168.10.9;192.168.10.10/RECOC1_CD_05_dm01cel01
Modifying the header
Looking for o/192.168.10.9;192.168.10.10/RECOC1_CD_00_dm01cel01
Modifying the header
Looking for o/192.168.10.9;192.168.10.10/RECOC1_CD_10_dm01cel01
Modifying the header
Looking for o/192.168.10.9;192.168.10.10/RECOC1_CD_07_dm01cel01
Modifying the header
Looking for o/192.168.10.9;192.168.10.10/RECOC1_CD_02_dm01cel01
Modifying the header
Looking for o/192.168.10.9;192.168.10.10/RECOC1_CD_01_dm01cel01
Modifying the header
Looking for o/192.168.10.9;192.168.10.10/RECOC1_CD_11_dm01cel01
Modifying the header
Looking for o/192.168.10.9;192.168.10.10/RECOC1_CD_08_dm01cel01
Modifying the header
Looking for o/192.168.10.9;192.168.10.10/RECOC1_CD_09_dm01cel01
Modifying the header
Looking for o/192.168.10.9;192.168.10.10/RECOC1_CD_06_dm01cel01
Modifying the header
...
...
Modifying the header
Completed phase 2
Terminating kgfd context 0x7f8d42f6c0a0

  • Mount the DATA and RECO ASM disk groups on all the nodes.

[oracle@dm01db01 ~]$ asmcmd -p

 ASMCMD [+] > lsdg
State    Type  Rebal  Sector  Block       AU  Total_MB  Free_MB  Req_mir_free_MB  Usable_file_MB  Offline_disks  Voting_files  Name
MOUNTED  HIGH  N         512   4096  4194304   2404640  2402468            68704          777921              0             Y  DBFS_DG/

 ASMCMD [+] > mount DATA

 ASMCMD [+] > mount RECO

 ASMCMD [+] > lsdg
State    Type    Rebal  Sector  Block       AU   Total_MB    Free_MB  Req_mir_free_MB  Usable_file_MB  Offline_disks  Voting_files  Name
MOUNTED  HIGH    N         512   4096  4194304  272154624  271558968          6479872        88359698              0             N  DATA/
MOUNTED  HIGH    N         512   4096  4194304    2404640    2402468            68704          777921              0             Y  DBFS_DG/
MOUNTED  NORMAL  N         512   4096  4194304   45389568   45385040           540352        22422344              0             N  RECO/

 *** Repeat the above steps on all the remaning compute nodes in the Cluster***

 Note: 

  • renamedg utility cannot rename the associated ASM/Grid disk disk name
  • renamedg utility cannot rename/update the control files, datafiles, redo log files and any other files that reference ASM DG for all databases


 Steps to rename control files, datafiles, redo log files and other database files
  • Update SPFILE location

[oracle@dm01db01 ~]$ cd $ORACLE_HOME/dbs

 [oracle@dm01db01 dbs]$ cat initdbm011.ora
SPFILE='+DATAC1/dbm01/spfiledbm01.ora'

 [oracle@dm01db01 dbs]$ vi initdbm011.ora

 [oracle@dm01db01 dbs]$ cat initdbm011.ora
SPFILE='+DATA/dbm01/spfiledbm01.ora'

 [oracle@dm01db01 dbs]$ scp initdbm011.ora dm01db02:/u01/app/oracle/product/11.2.0.4/dbhome/dbs/initdbm012.ora
initdbm011.ora                                                                                                                                             100%   42     0.0KB/s   00:00

 [oracle@dm01db01 dbs]$ scp initdbm011.ora dm01db03:/u01/app/oracle/product/11.2.0.4/dbhome/dbs/initdbm013.ora
initdbm011.ora                                                                                                                                             100%   42     0.0KB/s   00:00

 [oracle@dm01db01 dbs]$ scp initdbm011.ora dm01db04:/u01/app/oracle/product/11.2.0.4/dbhome/dbs/initdbm014.ora
initdbm011.ora                                                                                                                                             100%   42     0.0KB/s   00:00

  • Update control file location

[oracle@dm01db01 dbs]$ . oraenv
ORACLE_SID = [dbm011] ?
The Oracle base remains unchanged with value /u01/app/oracle

 [oracle@dm01db01 dbs]$ sqlplus / as sysdba

 SQL*Plus: Release 11.2.0.4.0 Production on Fri May 25 10:17:49 2018
Copyright (c) 1982, 2013, Oracle.  All rights reserved.
Connected to an idle instance.

 SQL> startup nomount;
ORACLE instance started.

 Total System Global Area 2.5655E+10 bytes
Fixed Size                  2265224 bytes
Variable Size            4160753528 bytes
Database Buffers         2.1341E+10 bytes
Redo Buffers              151113728 bytes

 SQL> show parameter control_files

 NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
control_files                        string      +DATAC1/dbm01/controlfile/current.256.976374731

 SQL> alter system set control_files='+DATA/dbm01/controlfile/current.256.976374731' scope=spfile;

 System altered.

 SQL> shutdown immediate;
ORA-01507: database not mounted
ORACLE instance shut down.
SQL> startup mount
ORACLE instance started.

 Total System Global Area 2.5655E+10 bytes
Fixed Size                  2265224 bytes
Variable Size            4160753528 bytes
Database Buffers         2.1341E+10 bytes
Redo Buffers              151113728 bytes
Database mounted.

 SQL> select name from v$controlfile;

 NAME
--------------------------------------------------------------------------------
+DATA/dbm01/controlfile/current.256.976374731

  • Update datafile and redo log file locations

SQL> select name from v$datafile;

 NAME
--------------------------------------------------------------------------------
+DATAC1/dbm01/datafile/system.259.976374739
+DATAC1/dbm01/datafile/sysaux.260.976374743
+DATAC1/dbm01/datafile/undotbs1.261.976374745
+DATAC1/dbm01/datafile/undotbs2.263.976374753
+DATAC1/dbm01/datafile/undotbs3.264.976374755
+DATAC1/dbm01/datafile/undotbs4.265.976374757
+DATAC1/dbm01/datafile/users.266.976374757

 7 rows selected.

 SQL> select member from v$logfile;

 MEMBER
--------------------------------------------------------------------------------
+DATAC1/dbm01/onlinelog/group_1.257.976374733
+DATAC1/dbm01/onlinelog/group_2.258.976374735
+DATAC1/dbm01/onlinelog/group_7.267.976375073
+DATAC1/dbm01/onlinelog/group_8.268.976375075
+DATAC1/dbm01/onlinelog/group_5.269.976375079
+DATAC1/dbm01/onlinelog/group_6.270.976375083
+DATAC1/dbm01/onlinelog/group_3.271.976375085
+DATAC1/dbm01/onlinelog/group_4.272.976375087
+DATAC1/dbm01/onlinelog/group_9.274.976375205
+DATAC1/dbm01/onlinelog/group_10.275.976375209
+DATAC1/dbm01/onlinelog/group_11.276.976375211
+DATAC1/dbm01/onlinelog/group_12.277.976375215
+DATAC1/dbm01/onlinelog/group_13.278.976375217
+DATAC1/dbm01/onlinelog/group_14.279.976375219
+DATAC1/dbm01/onlinelog/group_15.280.976375223
+DATAC1/dbm01/onlinelog/group_16.281.976375225

 16 rows selected.

 SQL> alter database rename file '+DATAC1/dbm01/datafile/system.259.976374739' to '+DATA/dbm01/datafile/system.259.976374739';

 Database altered.

 SQL> alter database rename file '+DATAC1/dbm01/datafile/sysaux.260.976374743' to '+DATA/dbm01/datafile/sysaux.260.976374743';

 Database altered.

 SQL> alter database rename file '+DATAC1/dbm01/datafile/undotbs1.261.976374745' to '+DATA/dbm01/datafile/undotbs1.261.976374745';

 Database altered.

 SQL> alter database rename file '+DATAC1/dbm01/datafile/undotbs2.263.976374753' to '+DATA/dbm01/datafile/undotbs2.263.976374753';

 Database altered.

 SQL> alter database rename file '+DATAC1/dbm01/datafile/undotbs3.264.976374755' to '+DATA/dbm01/datafile/undotbs3.264.976374755';

 Database altered.

 SQL> alter database rename file '+DATAC1/dbm01/datafile/undotbs4.265.976374757' to '+DATA/dbm01/datafile/undotbs4.265.976374757';

 Database altered.

 SQL> alter database rename file '+DATAC1/dbm01/datafile/users.266.976374757' to '+DATA/dbm01/datafile/users.266.976374757';

 Database altered.

 SQL> alter database rename file '+DATAC1/dbm01/onlinelog/group_1.257.976374733'  to '+DATA/dbm01/onlinelog/group_1.257.976374733';

 Database altered.

 SQL> alter database rename file '+DATAC1/dbm01/onlinelog/group_2.258.976374735'  to '+DATA/dbm01/onlinelog/group_2.258.976374735';

 Database altered.

 SQL> alter database rename file '+DATAC1/dbm01/onlinelog/group_7.267.976375073'  to '+DATA/dbm01/onlinelog/group_7.267.976375073';

 Database altered.

 SQL> alter database rename file '+DATAC1/dbm01/onlinelog/group_8.268.976375075'  to '+DATA/dbm01/onlinelog/group_8.268.976375075';

 Database altered.

 SQL> alter database rename file '+DATAC1/dbm01/onlinelog/group_5.269.976375079'  to '+DATA/dbm01/onlinelog/group_5.269.976375079';

 Database altered.

 SQL> alter database rename file '+DATAC1/dbm01/onlinelog/group_6.270.976375083'  to '+DATA/dbm01/onlinelog/group_6.270.976375083';

 Database altered.

 SQL> alter database rename file '+DATAC1/dbm01/onlinelog/group_3.271.976375085'  to '+DATA/dbm01/onlinelog/group_3.271.976375085';

 Database altered.

 SQL> alter database rename file '+DATAC1/dbm01/onlinelog/group_4.272.976375087'  to '+DATA/dbm01/onlinelog/group_4.272.976375087';

 Database altered.

 SQL> alter database rename file '+DATAC1/dbm01/onlinelog/group_9.274.976375205'  to '+DATA/dbm01/onlinelog/group_9.274.976375205';

 Database altered.

 SQL> alter database rename file '+DATAC1/dbm01/onlinelog/group_10.275.976375209' to '+DATA/dbm01/onlinelog/group_10.275.976375209';

 Database altered.

 SQL> alter database rename file '+DATAC1/dbm01/onlinelog/group_11.276.976375211' to '+DATA/dbm01/onlinelog/group_11.276.976375211';

 Database altered.

 SQL> alter database rename file '+DATAC1/dbm01/onlinelog/group_12.277.976375215' to '+DATA/dbm01/onlinelog/group_12.277.976375215';

 Database altered.

 SQL> alter database rename file '+DATAC1/dbm01/onlinelog/group_13.278.976375217' to '+DATA/dbm01/onlinelog/group_13.278.976375217';

 Database altered.

 SQL> alter database rename file '+DATAC1/dbm01/onlinelog/group_14.279.976375219' to '+DATA/dbm01/onlinelog/group_14.279.976375219';

 Database altered.

 SQL> alter database rename file '+DATAC1/dbm01/onlinelog/group_15.280.976375223' to '+DATA/dbm01/onlinelog/group_15.280.976375223';

 Database altered.

 SQL> alter database rename file '+DATAC1/dbm01/onlinelog/group_16.281.976375225' to '+DATA/dbm01/onlinelog/group_16.281.976375225';

 Database altered.

  • Verify the datafiles and redo log files names

SQL> select name from v$datafile;

 NAME
--------------------------------------------------------------------------------
+DATA/dbm01/datafile/system.259.976374739
+DATA/dbm01/datafile/sysaux.260.976374743
+DATA/dbm01/datafile/undotbs1.261.976374745
+DATA/dbm01/datafile/undotbs2.263.976374753
+DATA/dbm01/datafile/undotbs3.264.976374755
+DATA/dbm01/datafile/undotbs4.265.976374757
+DATA/dbm01/datafile/users.266.976374757

 7 rows selected.

 SQL> select member from v$logfile;

 MEMBER
--------------------------------------------------------------------------------
+DATA/dbm01/onlinelog/group_1.257.976374733
+DATA/dbm01/onlinelog/group_2.258.976374735
+DATA/dbm01/onlinelog/group_7.267.976375073
+DATA/dbm01/onlinelog/group_8.268.976375075
+DATA/dbm01/onlinelog/group_5.269.976375079
+DATA/dbm01/onlinelog/group_6.270.976375083
+DATA/dbm01/onlinelog/group_3.271.976375085
+DATA/dbm01/onlinelog/group_4.272.976375087
+DATA/dbm01/onlinelog/group_9.274.976375205
+DATA/dbm01/onlinelog/group_10.275.976375209
+DATA/dbm01/onlinelog/group_11.276.976375211
+DATA/dbm01/onlinelog/group_12.277.976375215
+DATA/dbm01/onlinelog/group_13.278.976375217
+DATA/dbm01/onlinelog/group_14.279.976375219
+DATA/dbm01/onlinelog/group_15.280.976375223
+DATA/dbm01/onlinelog/group_16.281.976375225

 16 rows selected.

  • Update block change tracking file location

SQL> alter database rename file '+DATAC1/dbm01/changetracking/ctf.282.976375227' to '+DATA/dbm01/changetracking/ctf.282.976375227';

 Database altered.

 SQL> select * from v$block_change_tracking;

 STATUS
----------
FILENAME
--------------------------------------------------------------------------------
     BYTES
----------
ENABLED
+DATA/dbm01/changetracking/ctf.282.976375227
  11599872

  • Update OMF related parameters

SQL> show parameter db_create_online_log_dest_1

 NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
db_create_online_log_dest_1          string      +DATAC1

 SQL> alter system set db_create_online_log_dest_1='+DATA';

 System altered.

 SQL> show parameter db_create_online_log_dest_1

 NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
db_create_online_log_dest_1          string      +DATA

  • Update Fast Recovery Area location

SQL> show parameter db_recovery_file_dest

 NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
db_recovery_file_dest                string      +RECOC1
db_recovery_file_dest_size           big integer 20425000M

 SQL> alter system set db_recovery_file_dest='+RECO';

 System altered.

 SQL> show parameter db_recovery_file_dest

 NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
db_recovery_file_dest                string      +RECO
db_recovery_file_dest_size           big integer 20425000M

  • Shutdown the database

SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> exit

  • Update the database configuration

[oracle@dm01db01 dbs]$ srvctl config database -d dbm01
Database unique name: dbm01
Database name: dbm01
Oracle home: /u01/app/oracle/product/11.2.0.4/dbhome
Oracle user: oracle
Spfile: +DATAC1/dbm01/spfiledbm01.ora
Domain:
Start options: open
Stop options: immediate
Database role: PRIMARY
Management policy: AUTOMATIC
Server pools: dbm01
Database instances: dbm011,dbm012,dbm013,dbm014
Disk Groups: DATAC1,RECOC1,DATA
Mount point paths:
Services:
Type: RAC
Database is administrator managed

 [oracle@dm01db01 dbs]$ srvctl modify database -p +DATA/dbm01/spfiledbm01.ora -a DATA,RECO -d dbm01

 [oracle@dm01db01 dbs]$ srvctl config database -d dbm01
Database unique name: dbm01
Database name: dbm01
Oracle home: /u01/app/oracle/product/11.2.0.4/dbhome
Oracle user: oracle
Spfile: +DATA/dbm01/spfiledbm01.ora
Domain:
Start options: open
Stop options: immediate
Database role: PRIMARY
Management policy: AUTOMATIC
Server pools: dbm01
Database instances: dbm011,dbm012,dbm013,dbm014
Disk Groups: DATA,RECO
Mount point paths:
Services:
Type: RAC
Database is administrator managed

  • Start the database and verify

[oracle@dm01db01 dbs]$ srvctl start database -d dbm01

 [oracle@dm01db01 dbs]$ srvctl status database -d dbm01
Instance dbm011 is running on node dm01db01
Instance dbm012 is running on node dm01db02
Instance dbm013 is running on node dm01db03
Instance dbm014 is running on node dm01db04

 [oracle@dm01db01 dbs]$ sqlplus / as sysdba

 SQL*Plus: Release 11.2.0.4.0 Production on Fri May 25 10:40:34 2018
Copyright (c) 1982, 2013, Oracle.  All rights reserved.

 Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options

 SQL> select name, open_mode,database_role from gv$database;

 NAME      OPEN_MODE            DATABASE_ROLE
--------- -------------------- ----------------
DBM01     READ WRITE           PRIMARY
DBM01     READ WRITE           PRIMARY
DBM01     READ WRITE           PRIMARY
DBM01     READ WRITE           PRIMARY

 ORACLE_SID = [+ASM1] ? dbm011
The Oracle base remains unchanged with value /u01/app/oracle

 [oracle@dm01db01 ~]$ sqlplus / as sysdba

 SQL*Plus: Release 11.2.0.4.0 Production on Thu May 24 16:36:34 2018
Copyright (c) 1982, 2013, Oracle.  All rights reserved.

 Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options

 SQL> select * from v$version;

 BANNER
--------------------------------------------------------------------------------
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
PL/SQL Release 11.2.0.4.0 - Production
CORE    11.2.0.4.0      Production
TNS for Linux: Version 11.2.0.4.0 - Production
NLSRTL Version 11.2.0.4.0 - Production
[oracle@dm01db01 ~]$ . oraenv

 ORACLE_SID = [oracle] ? +ASM1
The Oracle base has been set to /u01/app/oracle

 [oracle@dm01db01 ~]$ asmcmd -p

 ASMCMD [+] > lsdg
State    Type    Rebal  Sector  Block       AU   Total_MB    Free_MB  Req_mir_free_MB  Usable_file_MB  Offline_disks  Voting_files  Name
MOUNTED  HIGH    N         512   4096  4194304  272154624  271558968          6479872        88359698              0             N  DATAC1/
MOUNTED  HIGH    N         512   4096  4194304    2404640    2402468            68704          777921              0             Y  DBFS_DG/
MOUNTED  NORMAL  N         512   4096  4194304   45389568   45386648           540352        22423148              0             N  RECOC1/

 ASMCMD [+] > lsct
DB_Name  Status     Software_Version  Compatible_version  Instance_Name  Disk_Group
+ASM     CONNECTED        11.2.0.4.0          11.2.0.4.0  +ASM1          DBFS_DG
DBM01    CONNECTED        11.2.0.4.0          11.2.0.4.0  dbm011         DATAC1

 [oracle@dm01db01 ~]$ srvctl status database -d dbm01
Instance dbm011 is running on node dm01db01
Instance dbm012 is running on node dm01db02
Instance dbm013 is running on node dm01db03
Instance dbm014 is running on node dm01db04
Conclusion

 In this article we have learned how to rename an ASM Disk group on Exadata running Oracle Database 11.2. Starting with Oracle Database 11.2 you can use the renamedg command to rename an ASM Disk Group. renamedg utility cannot rename the associated ASM/Grid disk disk name. Also renamedg cannot rename/update the control files, datafiles, redo log files and any other files that reference ASM DG for all databases. You must update database files manually after renaming ASM disk groups.

By at No comments:
Labels: , , , , , , , , , , , ,
Subscribe to: Posts (Atom)

Comparing Oracle Database Appliance X8-2 Model Family

September 2019 Oracle announced Oracle Database Appliance X8-2 (Small, Medium and HA). ODA X8-2 comes with more computing resources com...