Netsoftmate

Category: Uncategorized

  • Storage Server Flash Memory is not Configured as Exadata Smart Flash Cache

    While working on an Exadata database machine X4-2 half rack we found that the Smart Flash Cache on a storage cell was missing. We ran an Exachk and found the Smart Flash cache was indeed missing on Storage Cell 05.


    Here is the message printed in the Exachk report.


    FAIL Storage Server Check Storage Server Flash Memory is not configured as Exadata Smart Flash Cache dm01cel05 


    Exadata Smart Flash Cache:


    Oracle first introduced Exadata Flash Cache in the version Exadata V2. Exadata Smart Flash Cache, caches the data on flash based Storage. Exadata uses a caching algorithm to cache data intelligently in the flash card on the Storage cells. It improves the performance for OLTP databases. Exadata Flash Cache is used for Smart Flash Cache and Smart Flash log features. 


    Courtesy Oracle



    In this article we will demonstrate how to create a missing Smart Flash Cache on Exadata Storage cell.


    Step to create/configure Smart Flash Cache


    • List the Flash cache

    From the output below we can clearly see that the storge cell 05 is missing.


    [root@dm01db01 ~]# dcli -g ~/cell_group -l root cellcli -e list flashcache attributes name,size,status
    dm01cel01: dm01cel01_FLASHCACHE  2978.75G        normal
    dm01cel02: dm01cel02_FLASHCACHE  2978.75G        normal
    dm01cel03: dm01cel03_FLASHCACHE  2978.75G        normal
    dm01cel04: dm01cel04_FLASHCACHE  2978.75G        normal
    dm01cel06: dm01cel06_FLASHCACHE  2978.75G        normal
    dm01cel07: dm01cel07_FLASHCACHE  2978.75G        normal


    • List the Flash log. Flash Log are is fine

    [root@dm01db01 ~]# dcli -g ~/cell_group -l root cellcli -e list flashlog attributes name,size
    dm01cel01: dm01cel01_FLASHLOG    512M
    dm01cel02: dm01cel02_FLASHLOG    512M
    dm01cel03: dm01cel03_FLASHLOG    512M
    dm01cel04: dm01cel04_FLASHLOG    512M
    dm01cel05: dm01cel05_FLASHLOG    512M
    dm01cel06: dm01cel06_FLASHLOG    512M
    dm01cel07: dm01cel07_FLASHLOG    512M


    • Connect to Storage cell 05 and list the flash cache

    [root@dm01cel05 ~]# cellcli
    CellCLI: Release 12.2.1.1.6 – Production on Tue Jun 16 03:57:24 CDT 2018


    Copyright (c) 2007, 2013, Oracle.  All rights reserved.
    Cell Efficiency Ratio: 1,656


    • List flash cache. We can’t find flash cache on it as there is no output of the command reported

    CellCLI> list flashcache detail


    • Create Flash Cache as shown below

    CellCLI> create flashcache all
    Flash cache dm01cel05_FLASHCACHE successfully created


    • List flash cache

    CellCLI>  list flashcache detail
             name:                   dm01cel05_FLASHCACHE
             cellDisk:               FD_04_dm01cel05,FD_05_dm01cel05,FD_10_dm01cel05,FD_06_dm01cel05,FD_11_dm01cel05,FD_13_dm01cel05,FD_08_dm01cel05,FD_15_dm01cel05,FD_12_dm01cel05,FD_01_dm01cel05,FD_00_dm01cel05,FD_07_dm01cel05,FD_09_dm01cel05,FD_14_dm01cel05,FD_02_dm01cel05,FD_03_dm01cel05
             creationTime:           2015-06-16T04:03:21-05:00
             degradedCelldisks:
             effectiveCacheSize:     2978.75G
             id:                     ce4589c7-183c-4346-965d-3f43a4e47de5
             size:                   2978.75G
             status:                 normal


    • List flash cache for all cells now. From compute node 1 , execute the following command

    [root@dm01db01 ~]# dcli -g ~/cell_group -l root cellcli -e list flashcache attributes name,size,status
    dm01cel01: dm01cel01_FLASHCACHE  2978.75G        normal
    dm01cel02: dm01cel02_FLASHCACHE  2978.75G        normal
    dm01cel03: dm01cel03_FLASHCACHE  2978.75G        normal
    dm01cel04: dm01cel04_FLASHCACHE  2978.75G        normal
    dm01cel05: dm01cel05_FLASHCACHE  2978.75G        normal
    dm01cel06: dm01cel06_FLASHCACHE  2978.75G        normal
    dm01cel07: dm01cel07_FLASHCACHE  2978.75G        normal




    Conclusion


    In this article we have learned how to create missing flash cache on  Exadata Storage cell. Exadata Smart Flash Cache, caches the data on flash based Storage. Exadata Flash Cache is used for Smart Flash Cache and Smart Flash log features. Exachk utility helps you diagnose and report the hardware problems and it also recommends the solution,

  • Oracle Database Appliance: Resize CloudFS ACFS File System Using ASMCA

    During the Oracle Database Appliance Deployment you can optionally configure CloudFS file system. The default mount point is /cloudfs and set to default size of 50GB. Oracle Database Appliance uses the Oracle Automatic Storage Management Cluster File System (Oracle ACFS) for database and virtual machine files storage. ACFS can only be used to configure shared storage file system on ODA. Oracle ACFS provides both servers with concurrent access to /cloudfs shared file system. The default size of 50GB may not sufficient and must be increased to store big files for business requirement.




    In this article we will demonstrate how to resize the /cloudfs file system using ASMCA GUI interface




    Steps to resize the /cloudfs file system using asmca GUI Interface


    Step 1: Get the current /cloudfs file system size



    Step 2: Start VNC on node 1. Here I am starting VNC as root user. You can choose to start it as Grid or Oracle user.


    [root@odanode1 ~]# rpm -qa *vnc*
    tigervnc-1.1.0-18.el6.x86_64
    tigervnc-server-1.1.0-18.el6.x86_64
    [root@odanode1 ~]# ps -ef|grep vnc
    root     23281 20754  0 13:32 pts/1    00:00:00 grep vnc

    [root@odanode1 ~]# vncserver :1


    You will require a password to access your desktops.


    Password:
    Verify:


    New ‘odanode1:1 (root)’ desktop is odanode1:1


    Creating default startup script /root/.vnc/xstartup
    Starting applications specified in /root/.vnc/xstartup
    Log file is /root/.vnc/odanode1:1.log


    [root@odanode1 ~]# ps -ef|grep vnc
    root     23399     1  1 13:32 pts/1    00:00:00 /usr/bin/Xvnc :1 -desktop odanode1:1 (root) -auth /root/.Xauthority -geometry 1024×768 -rfbwait 30000 -rfbauth /root/.vnc/passwd -rfbport 5901 -fp catalogue:/etc/X11/fontpath.d -pn
    root     23481 23480  0 13:33 pts/1    00:00:00 vncconfig -iconic
    root     23636 20754  0 13:33 pts/1    00:00:00 grep vnc

    Step 3: Start VNC viewer on desktop and enter the hostname/IP address on node 1. Enter the root password as we have started the VNC server using root user.




    Step 4: Switch to grid user and verify the Grid Home



    Step 5: Set Oracle Home to Grid home and start asmca



    Step 6: Click on ASM Cluster File System Tab



    Step 7: Right Click on /cloudfs and select Resize option



    Step 8: Enter the desired new size. Here I am resizing the /cloudfs to 200GB



    Step 9: Resize in progress



    Step 10: Resize completed



    Step 11: Verify the /cloudfs size





    Conclusion


    In this article we have learned how to resize/increase the size of /cloudfs ACFS file system on ODA using ASMCA GUI utility. The cloudfs file system is configured during the ODA deployment and it is set to 50GB which is not sufficient for storing the big files. The cloudfs is build using ACFS and it can be resized easily using ASMCA graphical interface.

  • Oracle Database Appliance : Monitor Hardware Components

    Oracle Database Appliance (ODA) is an entry level Engineered System. ODA is a pre-configured, highly available Oracle Database Engineered system. ODA system consists of hardware, software, storage and networking. The hardware configuration is designed to provide redundancy and protection against single points of failures in the system.


    ODA consists of two physical servers (Node 0 and Node 1), a storage shelf and optionally an additional storage shelf. The two independent physical servers are interconnected and direct attached to SAS and SSD storage.


    ODA is basically a 2-node RAC cluster database system running Oracle Linux operating (OEL), Oracle Database Enterprise Edition, Oracle Grid Infrastructure (Clusterware and ASM). All these together provides the Oracle Database high availability running on ODA.


    ODA consists of several hardware components such as Mother Board, Processor, Memory, Power Supply, FAN, Network cards and so on. You can monitor the hardware status of these components using OAKCLI command for both Bare Metal and Virtualized platform.


    Note: ODACLI is used for Hardware monitoring and administrative tasks on the Oracle Database Appliance on X6-2 S/M/L & X7-2 S/M.



    In this article we will demonstrate how to monitor different hardware component status on ODA nodes.


    Using OAKCLI command to Get Hardware Status


    • Execute the following command to display ODA server details

    [root@odanoden1 ~]# oakcli show server


            Power State              : On
            Open Problems            : 0
            Model                    : ODA X4-2
            Type                     : Rack Mount
            Part Number              : 33060862+1+1
            Serial Number            : 1440XXXXXX
            Primary OS               : Not Available
            ILOM Address             : 10.10.20.1
            ILOM MAC Address         : 00:10:E0:62:3F:F6
            Description              : Oracle Database Appliance X4-2 1440XXXXX
            Locator Light            : Off
            Actual Power Consumption : 261 watts
            Ambient Temperature      : 18.500 degree C
            Open Problems Report     : System is healthy


    [root@odanoden2 ~]# oakcli show server


            Power State              : On
            Open Problems            : 0
            Model                    : ODA X4-2
            Type                     : Rack Mount
            Part Number              : 33060862+1+1
            Serial Number            : 1440XXXXXX
            Primary OS               : Not Available
            ILOM Address             : 10.10.20.2
            ILOM MAC Address         : 00:10:E0:62:41:D6
            Description              : Oracle Database Appliance X4-2 1440XXXXX
            Locator Light            : Off
            Actual Power Consumption : 269 watts
            Ambient Temperature      : 17.750 degree C
            Open Problems Report     : System is healthy


    • Execute the following command to display ODA model

    [root@odanoden1 ~]# oakcli show env_hw
    BM ODA X4-2
    Public interface : COPPER


    • Execute the following command to display ODA software version details

    [root@odanoden1 ~]# oakcli show version -detail
    Reading the metadata. It takes a while…
    System Version  Component Name            Installed Version         Supported Version
    ————–  —————           ——————        —————–
    12.1.2.10.0
                    Controller_INT            11.05.03.00               Up-to-date
                    Controller_EXT            11.05.03.00               Up-to-date
                    Expander                  0018                      Up-to-date
                    SSD_SHARED                944A                      Up-to-date
                    HDD_LOCAL                 A72A                      Up-to-date
                    HDD_SHARED                A72A                      Up-to-date
                    ILOM                      3.2.8.25 r114493          Up-to-date
                    BIOS                      25040100                  Up-to-date
                    IPMI                      1.8.12.4                  Up-to-date
                    HMP                       2.3.5.2.8                 Up-to-date
                    OAK                       12.1.2.10.0               Up-to-date
                    OL                        6.8                       Up-to-date
                    GI_HOME                   12.1.0.2.170117(2473      Up-to-date
                                              2082,24828633)
                    DB_HOME                   12.1.0.2.170117(2473      Up-to-date
                                              2082,24828633)


    • Execute the following command to display ‘oakcli show’ help

    [root@odanoden1 ~]# oakcli show -h
    Usage:
    oakcli show {disk|diskgroup|expander|fs|raidsycstatus|controller|server|processor|memory|power|cooling|network|enclosure|storage|core_config_key|version|dbhomes|dbstorage|databases|db_config_params|asr|env_hw} [<options>]
    where:
            disk                     – About the disk
            diskgroup                – ASM disk group
            expander                 – Expander
            fs                       – Filesystem
            controller               – Controller
            storage                  – All storage components
            version                  – Running software version
            dbhomes                  – Installed oracle database homes
            dbstorage                – Details of ACFS storage setup for the databases
            databases                – Database names
            db_config_params         – db_config_params file
            asr                      – ASR configuration
            env_hw                   – Environment and Hardware information
            server                   – Details of server sub-system
            processor                – Details of processor sub-system
            memory                   – Details of memory sub-system
            power                    – Details of power supply sub-system
            cooling                  – Details of cooling sub-system
            network                  – Details of network sub-system
            enclosure                – Details of enclosure sub-system
            raidsyncstatus           – RAID sync status information
            core_config_key          – Core configuration
    For detailed help on each command and object and its options use:
    oakcli <command> <object> -h


    • Execute the following command to monitor the Processor Status

    [root@odanoden1 ~]# oakcli show processor


            NAME  HEALTH HEALTH_DETAILS PART_NO. LOCATION   MODEL                         MAX_CLK_SPEED TOTAL_CORES ENABLED_CORES


            CPU_0 OK     –              060E     P0 (CPU 0) Intel(R) Xeon(R) CPU E5-2697  2.700 GHz       12        NA
            CPU_1 OK     –              060E     P1 (CPU 1) Intel(R) Xeon(R) CPU E5-2697  2.700 GHz       12        NA


    • Execute the following command to monitor the Memory Status

    [root@odanoden1 ~]# oakcli show memory


            NAME    HEALTH HEALTH_DETAILS PART_NO.         SERIAL_NO.         LOCATION MANUFACTURER MEMORY_SIZE CURR_CLK_SPEED ECC_Errors


            DIMM_0  OK     –              M393B2G70DB0-YK0 00CE03143317593248 P0/D0    Samsung      16 GB       1600 MHz       0
            DIMM_1  OK     –              M393B2G70DB0-YK0 00CE0314331759238B P0/D1    Samsung      16 GB       1600 MHz       0
            DIMM_10 OK     –              M393B2G70DB0-YK0 00CE031433175926CD P1/D2    Samsung      16 GB       1600 MHz       0
            DIMM_11 OK     –              M393B2G70DB0-YK0 00CE031433175927AD P1/D3    Samsung      16 GB       1600 MHz       0
            DIMM_12 OK     –              M393B2G70DB0-YK0 00CE031433175922C3 P1/D4    Samsung      16 GB       1600 MHz       0
            DIMM_13 OK     –              M393B2G70DB0-YK0 00CE03143317593250 P1/D5    Samsung      16 GB       1600 MHz       0
            DIMM_14 OK     –              M393B2G70DB0-YK0 00CE0314331759367A P1/D6    Samsung      16 GB       1600 MHz       0
            DIMM_15 OK     –              M393B2G70DB0-YK0 00CE03143317593319 P1/D7    Samsung      16 GB       1600 MHz       0
            DIMM_2  OK     –              M393B2G70DB0-YK0 00CE031433175927A8 P0/D2    Samsung      16 GB       1600 MHz       0
            DIMM_3  OK     –              M393B2G70DB0-YK0 00CE03143317592B31 P0/D3    Samsung      16 GB       1600 MHz       0
            DIMM_4  OK     –              M393B2G70DB0-YK0 00CE03143317592B35 P0/D4    Samsung      16 GB       1600 MHz       0
            DIMM_5  OK     –              M393B2G70DB0-YK0 00CE03143317591C3C P0/D5    Samsung      16 GB       1600 MHz       0
            DIMM_6  OK     –              M393B2G70DB0-YK0 00CE031433175922C7 P0/D6    Samsung      16 GB       1600 MHz       0
            DIMM_7  OK     –              M393B2G70DB0-YK0 00CE0314331759324E P0/D7    Samsung      16 GB       1600 MHz       0
            DIMM_8  OK     –              M393B2G70DB0-YK0 00CE0314331759324B P1/D0    Samsung      16 GB       1600 MHz       0
            DIMM_9  OK     –              M393B2G70DB0-YK0 00CE0314331759331A P1/D1    Samsung      16 GB       1600 MHz       0


    • Execute the following command to monitor Power Status

    [root@odanoden1 ~]# oakcli show power


            NAME            HEALTH HEALTH_DETAILS PART_NO. SERIAL_NO.         LOCATION INPUT_POWER OUTPUT_POWER INLET_TEMP     EXHAUST_TEMP


            Power_Supply_0  OK     –              7079395  476856Z+1435CE00EU PS0      Present     119 watts    32.250 degree C 36.562 degree C
            Power_Supply_1  OK     –              7079395  476856Z+1435CE00F6 PS1      Present     112 watts    37.000 degree C 40.375 degree C


    • Execute the following command to monitor Network Status

    [root@odanoden1 ~]# oakcli show network


            NAME           HEALTH HEALTH_DETAILS LOCATION PART_NO MANUFACTURER MAC_ADDRESS        LINK_DETECTED DIE_TEMP


            Ethernet_NIC_0 OK     –              NET0     X540    INTEL        00:10:E0:62:3F:F2  yes (eth2)    46.250 degree C
            Ethernet_NIC_1 OK     –              NET1     X540    INTEL        00:10:E0:62:3F:F3  no (eth3)     46.250 degree C
            Ethernet_NIC_2 OK     –              NET2     X540    INTEL        00:10:E0:62:3F:F4  no (eth4)     51.000 degree C
            Ethernet_NIC_3 OK     –              NET3     X540    INTEL        00:10:E0:62:3F:F5  no (eth5)     51.500 degree C
            Ethernet_NIC_4 –      –              NET4     X540    INTEL        90:E2:BA:81:2B:B4  yes (eth0)    –
            Ethernet_NIC_5 –      –              NET5     X540    INTEL        90:E2:BA:81:2B:B5  yes (eth1)    –


    • Execute the following command to monitor Storage Status

    [root@odanoden1 ~]# oakcli show storage
    ==== BEGIN STORAGE DUMP ========
    Host Description: Oracle Corporation:SUN SERVER X4-2
    Total number of controllers: 3
            Id         = 1
            Serial Num = 500605b008030030
            Vendor     = LSI Logic
            Model      = SGX-SAS6-EXT-Z
            FwVers     = 11.05.03.00
            strId      = mpt2sas:30:00.0


            Id         = 2
            Serial Num = 500605b00802fbc0
            Vendor     = LSI Logic
            Model      = SGX-SAS6-EXT-Z
            FwVers     = 11.05.03.00
            strId      = mpt2sas:40:00.0


            Id         = 0
            Serial Num = 500605b008071240
            Vendor     = LSI Logic
            Model      = SGX-SAS6-INT-Z
            FwVers     = 11.05.03.00
            strId      = mpt2sas:50:00.0


    Total number of expanders: 2
            Id         = 1
            Serial Num = 50800200019f0002
            Vendor     = ORACLE
            Model      = DE2-24P
            FwVers     = 0018
            strId      = Primary
            WWN        = 5080020001a6b97e


            Id         = 0
            Serial Num = 50800200019f0002
            Vendor     = ORACLE
            Model      = DE2-24P
            FwVers     = 0018
            strId      = Secondary
            WWN        = 5080020001a6babe


    Total number of PDs: 24
            /dev/sdl        LSI Logic         HDD  900gb slot:  0  exp:  0
            /dev/sdn        LSI Logic         HDD  900gb slot:  1  exp:  0
            /dev/sdah       LSI Logic         HDD  900gb slot:  2  exp:  0
            /dev/sdai       LSI Logic         HDD  900gb slot:  3  exp:  0
            /dev/sdaj       LSI Logic         HDD  900gb slot:  4  exp:  0
            /dev/sdak       LSI Logic         HDD  900gb slot:  5  exp:  0
            /dev/sdal       LSI Logic         HDD  900gb slot:  6  exp:  0
            /dev/sdam       LSI Logic         HDD  900gb slot:  7  exp:  0
            /dev/sdan       LSI Logic         HDD  900gb slot:  8  exp:  0
            /dev/sdao       LSI Logic         HDD  900gb slot:  9  exp:  0
            /dev/sdap       LSI Logic         HDD  900gb slot: 10  exp:  0
            /dev/sdaq       LSI Logic         HDD  900gb slot: 11  exp:  0
            /dev/sdar       LSI Logic         HDD  900gb slot: 12  exp:  0
            /dev/sdaa       LSI Logic         HDD  900gb slot: 13  exp:  0
            /dev/sdab       LSI Logic         HDD  900gb slot: 14  exp:  0
            /dev/sdac       LSI Logic         HDD  900gb slot: 15  exp:  0
            /dev/sdad       LSI Logic         HDD  900gb slot: 16  exp:  0
            /dev/sdae       LSI Logic         HDD  900gb slot: 17  exp:  0
            /dev/sdaf       LSI Logic         HDD  900gb slot: 18  exp:  0
            /dev/sdag       LSI Logic         HDD  900gb slot: 19  exp:  0
            /dev/sda        LSI Logic         SSD  200gb slot: 20  exp:  0
            /dev/sdb        LSI Logic         SSD  200gb slot: 21  exp:  0
            /dev/sdc        LSI Logic         SSD  200gb slot: 22  exp:  0
            /dev/sdd        LSI Logic         SSD  200gb slot: 23  exp:  0
    ==== END STORAGE DUMP =========


    • Execute the following command to monitor Shared Disk Status

    [root@odanoden1 ~]# oakcli show disk
            NAME            PATH            TYPE            STATE           STATE_DETAILS


            e0_pd_00        /dev/sdl        HDD             ONLINE          Good
            e0_pd_01        /dev/sdn        HDD             ONLINE          Good
            e0_pd_02        /dev/sdah       HDD             ONLINE          Good
            e0_pd_03        /dev/sdai       HDD             ONLINE          Good
            e0_pd_04        /dev/sdaj       HDD             ONLINE          Good
            e0_pd_05        /dev/sdak       HDD             ONLINE          Good
            e0_pd_06        /dev/sdal       HDD             ONLINE          Good
            e0_pd_07        /dev/sdam       HDD             ONLINE          Good
            e0_pd_08        /dev/sdan       HDD             ONLINE          Good
            e0_pd_09        /dev/sdao       HDD             ONLINE          Good
            e0_pd_10        /dev/sdap       HDD             ONLINE          Good
            e0_pd_11        /dev/sdaq       HDD             ONLINE          Good
            e0_pd_12        /dev/sdar       HDD             ONLINE          Good
            e0_pd_13        /dev/sdaa       HDD             ONLINE          Good
            e0_pd_14        /dev/sdab       HDD             ONLINE          Good
            e0_pd_15        /dev/sdac       HDD             ONLINE          Good
            e0_pd_16        /dev/sdad       HDD             ONLINE          Good
            e0_pd_17        /dev/sdae       HDD             ONLINE          Good
            e0_pd_18        /dev/sdaf       HDD             ONLINE          Good
            e0_pd_19        /dev/sdag       HDD             ONLINE          Good
            e0_pd_20        /dev/sda        SSD             ONLINE          Good
            e0_pd_21        /dev/sdb        SSD             ONLINE          Good
            e0_pd_22        /dev/sdc        SSD             ONLINE          Good
            e0_pd_23        /dev/sdd        SSD             ONLINE          Good


    • Execute the following command to monitor ODA server enclosure

    [root@odanoden1 ~]# oakcli show enclosure


            NAME        SUBSYSTEM         STATUS      METRIC


            E0_FAN0     Cooling           OK          3450 rpm
            E0_FAN1     Cooling           OK          3070 rpm
            E0_FAN2     Cooling           OK          3070 rpm
            E0_FAN3     Cooling           OK          3070 rpm
            E0_IOM0     Encl_Electronics  OK          –
            E0_IOM1     Encl_Electronics  OK          –
            E0_PSU0     Power_Supply      OK          –
            E0_PSU1     Power_Supply      OK          –
            E0_TEMP0    Amb_Temp          OK          19 C
            E0_TEMP1    Midplane_Temp     OK          27 C
            E0_TEMP2    PCM0_Inlet_Temp   OK          32 C
            E0_TEMP3    PCM0_Hotspot_Temp OK          38 C
            E0_TEMP4    PCM1_Inlet_Temp   OK          27 C
            E0_TEMP5    PCM1_Hotspot_Temp OK          36 C
            E0_TEMP6    IOM0_Temp         OK          38 C
            E0_TEMP7    IOM1_Temp         OK          45 C




    Using ILOM CLI to Get the Hardware Status


    • Execute the following command to connect to ILOM and monitor Hardware Status

    [root@odanoden2 ~]# ssh odanoden2-ilom
    Password:


    Oracle(R) Integrated Lights Out Manager


    Version 3.2.8.25 r114493


    Copyright (c) 2016, Oracle and/or its affiliates. All rights reserved.


    Warning: password is set to factory default.


    Warning: HTTPS certificate is set to factory default.


    Hostname: odanoden2-ilom


    -> show -level all -output table /SP/faultmgmt
    Target                          | Property                             | Value
    ——————————–+————————————–+———————————————————


    -> show -l all /SYS type==’Hard Disk’


     /SYS/DBP0/HDD0
        Targets:
            OK2RM
            PRSNT
            SERVICE
            STATE


        Properties:
            type = Hard Disk
            ipmi_name = HDD0


        Commands:
            cd
            show


     /SYS/DBP0/HDD1
        Targets:
            OK2RM
            PRSNT
            SERVICE
            STATE


        Properties:
            type = Hard Disk
            ipmi_name = HDD1


        Commands:
            cd
            show



    Using ILOM GUI to Get the Hardware Status





    Conclusion


    In this article we have learned how to monitor various hardware components status on ODA nodes using oakcli and ILOM. ODA server comes with different hardware components and monitoring them is key for ODA availability.

  • Oracle Database Appliance: Resize CloudFS ACFS File System Manually

    During Oracle Database Appliance Deployment you can optionally configure CloudFS file system. The default mount point is /cloudfs and set to default size of 50GB. Oracle Database Appliance uses the Oracle Automatic Storage Management Cluster File System (Oracle ACFS) for database and virtual machine files storage. ACFS can only be used to configure shared storage file system on ODA. Oracle ACFS provides both servers with concurrent access to /cloudfs shared file system. The default size of 50GB may not sufficient and must be increased to store big files for business requirement.








    In this article we will demonstrate how to resize the /cloudfs file system manually using ACFS commands.




    Steps to resize the /cloudfs file system




    Step 1: Login to node 1 as grid user the owner of Grid Infrastructure software


    [grid@odanoden1 ~]$ id
    uid=1000(grid) gid=1001(oinstall) groups=1001(oinstall),1003(racoper),1004(asmdba),1005(asmoper),1006(asmadmin)


    Step 2: Verify the existing size of /cloudfs. Here is my case the /cloufs is 200GB and it was resized in the past from 50GB to 200GB


    [grid@odanoden1 ~]$ df -h /cloudfs
    Filesystem           Size  Used Avail Use% Mounted on
    /dev/asm/acfsvol-23  200G  483M  200G   1% /cloudfs


    Step 3: Set the ORACLE SID to +ASM1


    [grid@odanoden1 ~]$ echo $ORACLE_SID


    [grid@odanoden1 ~]$ . oraenv
    ORACLE_SID = [grid] ? +ASM1
    The Oracle base has been set to /u01/app/grid


    [grid@odanoden1 ~]$ echo $ORACLE_SID
    +ASM1


    Step 4: List the ACFS Mounts. Here we can see that /cloudfs volume is /dev/asm/acfsvol-23


    [grid@odanoden1 ~]$ mount |grep asm
    /dev/asm/acfsvol-23 on /cloudfs type acfs (rw)
    /dev/asm/datastore-272 on /u01/app/oracle/oradata/datastore type acfs (rw)
    /dev/asm/datastore-97 on /u02/app/oracle/oradata/datastore type acfs (rw)
    /dev/asm/datastore-23 on /u01/app/oracle/fast_recovery_area/datastore type acfs (rw)


    Step 5: Get the size of the volume /dev/asm/acfsvol-23


    [grid@odanoden1 ~]$ /sbin/advmutil volinfo /dev/asm/acfsvol-23
    Device: /dev/asm/acfsvol-23
    Interface Version: 1
    Size (MB): 204800
    Resize Increment (MB): 64
    Redundancy: high
    Stripe Columns: 8
    Stripe Width (KB): 1024
    Disk Group: RECO
    Volume: ACFSVOL
    Compatible.advm: 12.1.0.2.0


    Step 6: Resize the /cloudfs as follows. Here we are increasing /cloudfs by 50GB


    [grid@odanoden1 ~]$ /sbin/acfsutil size +50g /cloudfs
    acfsutil size: new file system size: 268435456000 (256000MB)


    Step 7: Verify the new size of the volume /dev/asm/acfsvol-23


    [grid@odanoden1 ~]$ /sbin/advmutil volinfo /dev/asm/acfsvol-23
    Device: /dev/asm/acfsvol-23
    Interface Version: 1
    Size (MB): 256000
    Resize Increment (MB): 64
    Redundancy: high
    Stripe Columns: 8
    Stripe Width (KB): 1024
    Disk Group: RECO
    Volume: ACFSVOL
    Compatible.advm: 12.1.0.2.0


    Step 8: Verify the new size of /cloudfs file system


    [grid@odanoden1 ~]$ df -h /cloudfs
    Filesystem           Size  Used Avail Use% Mounted on
    /dev/asm/acfsvol-23  250G  585M  250G   1% /cloudfs




    Conclusion


    In this article we have learned how to resize/increase the size of /cloudfs shared file system on ODA. The cloudfs file system is configured during the ODA deployment and it is set to 50GB which is not sufficient for storing the big files. The cloudfs is build using ACFS and it can be resized easily using ACFS commands.

  • Oracle Database Appliance : Create Snapshot Database Using OAKCLI

    About ODA Snapshot Database


    • ODA Snapshot Database is created using oakcli command line utility
    • ODA automates the entire snapshot database creation process
    • Snapshot Database is created by taking a snapshot of the Oracle ASM Cluster File System (ACFS) where the source data files reside
    • The Source Database can be:
      • Non-RAC
      • RAC
      • RAC One Node
    • Snapshot Database requires less time and Storage
    • No downtime for source database for creating snapshot database
    • You can create an Oracle RAC database from an Oracle RAC One Node database
    • Create snapshot database feature is not available in ODA X6 – S / M / L
    • Create snapshot database feature is planned for 12.2 ODA X6 – S / M / L  RDBMS


    Prerequisites



    The Source Database must meet the following requirement to create Snapshot Database

    • It shouldn’t be a Standby database
    • It shouldn’t be a Container database
    • It shouldn’t be in READ-ONLY, RESTRICTED or ONLINE BACKUP Mode
    • It must be in ARCHIVE LOG Mode
    • All datafiles should be ONLINE
    • It shouldn’t use centralized wallet with TDE
    • It should be 11.2.0.4 and above



    Important Note


    • Both the Compute Nodes in ODA cluster must have system clock synchronized. The create snapshot database command may fail if the clocks are not synchronized.
    • You can’t create a RAC snapshot database from Non-RAC source database and vice versa
    • You can create Non-RAC snapshot Database from a Non-RAC Snapshot database



    Courtesy Oracle



    Steps to Create Snapshot Database Using oakcli utility


    • List existing databases

    [root@odanode1 ~]# oakcli show databases
    Name     Type       Storage   HomeName             HomeLocation                               Version
    —–    ——     ——–  ————–       —————-                           ———-
    orcldb   RAC        ACFS      OraDb12102_home1     /u01/app/oracle/product/12.1.0.2/dbhome_1  12.1.0.2.170117(24732082,24828633)
    odatest  RAC        ACFS      OraDb12102_home1     /u01/app/oracle/product/12.1.0.2/dbhome_1  12.1.0.2.170117(24732082,24828633)


    • Make source database is ARCHIVE LOG Mode

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


    NAME      OPEN_MODE            DATABASE_ROLE    LOG_MODE
    ——— ——————– —————- ————
    ODATEST   READ WRITE           PRIMARY          ARCHIVELOG
    ODATEST   READ WRITE           PRIMARY          ARCHIVELOG


    SQL> archive log list;
    Database log mode              Archive Mode
    Automatic archival             Disabled
    Archive destination            USE_DB_RECOVERY_FILE_DEST
    Oldest online log sequence     53
    Current log sequence           54


    • List the database files

    SQL> set lines 400 pages 200
    SQL> col name for a120
    SQL> select name, status from v$datafile;


    NAME                                                                                                                     STATUS
    ———————————————————————————————————————— ——-
    /u02/app/oracle/oradata/datastore/.ACFS/snaps/odatest/ODATEST/datafile/o1_mf_system_doqhbjop_.dbf                        SYSTEM
    /u02/app/oracle/oradata/datastore/.ACFS/snaps/odatest/ODATEST/datafile/o1_mf_sysaux_doqhbnkx_.dbf                        ONLINE
    /u02/app/oracle/oradata/datastore/.ACFS/snaps/odatest/ODATEST/datafile/o1_mf_undotbs1_doqhbq7b_.dbf                      ONLINE
    /u02/app/oracle/oradata/datastore/.ACFS/snaps/odatest/ODATEST/datafile/o1_mf_undotbs2_doqhbzyd_.dbf                      ONLINE
    /u02/app/oracle/oradata/datastore/.ACFS/snaps/odatest/ODATEST/datafile/o1_mf_users_doqhc0tz_.dbf                         ONLINE
    /u02/app/oracle/oradata/datastore/.ACFS/snaps/odatest/ODATEST/datafile/o1_mf_test_ffsnh1x9_.dbf                          ONLINE


    6 rows selected.


    • Syntax for oakcli create command

    [root@odanode1 ~]# oakcli create -h
    Usage:
    oakcli create {database | dbstorage | snapshotdb| dbhome | db_config_params } [<options>]
    Where:
             database            – Creates the Database
             snapshotdb          – Creates the Snapshot Database
             dbhome              – Creates the Database Home
             dbstorage           – Creates Storage for a given Database
             db_config_params    – Creates the Database configuration parameter file
    [root@odanode1 ~]# oakcli create snapshotdb -h
    Usage:
          oakcli create snapshotdb  -db <db_name> -from <db_name>


          where:
             db_name      – Name of the database to be created.
             from         – Source database for creating  the snapshot database.


    • Execute the following command to create snapshot database

    Here we are creating a snapshot database newdb from source database odatest


    [root@odanode1 ~]# oakcli create snapshotdb -db newdb -from odatest
    INFO: 2018-04-22 14:51:11: Please check the logfile  ‘/opt/oracle/oak/log/odanode1/tools/12.1.2.10.0/createdb_newdb_56401.log’ for more details


    Please enter the ‘root’  password :
    Please re-enter the ‘root’ password:


    Please enter the ‘SYS’  password for the Database odatest:
    Please re-enter the ‘SYS’ password:
    Please select one of the following for Database Deployment  [1 .. 2] :
    1    => RACONE
    2    => RAC
    2
    The selected value is : RAC


    Specify the  Database Class (1. odb-01 ‘1 core, 8 GB memory’   2. Others) [1] :
    The selected value is : odb-01 ‘1 core, 8 GB memory’
    ……….Completed
    …
    SUCCESS: All nodes in /opt/oracle/oak/temp_clunodes.txt are pingable and alive.
    ……
    SUCCESS: All nodes in /opt/oracle/oak/temp_clunodes.txt are pingable and alive.
    INFO: 2018-04-22 14:54:03: Creating the SNAP Database ‘newdb’ from the source Database ‘odatest’
    INFO: 2018-04-22 14:54:11: Do not perform any Structural change to Database ‘odatest’ till SNAP Database ‘newdb’ is created
    INFO: 2018-04-22 14:54:31: Taking SNAP of the Database ‘odatest’
    INFO: 2018-04-22 14:54:32: Successfully took  the SNAP of database: odatest
    INFO: 2018-04-22 14:55:24: Creating controlfile for database: newdb
    INFO: 2018-04-22 14:56:05: Successfully created the control file for the database : newdb
    INFO: 2018-04-22 14:56:05: Adding log files for the second thread for the database : newdb
    INFO: 2018-04-22 14:56:11: Successfully added the log files for second thread
    INFO: 2018-04-22 14:56:15: Recovering the database: newdb,  snapshot time : ‘2018-04-22:14:54:32’ , until time : ‘2018-04-22:14:54:49’
    INFO: 2018-04-22 14:56:17: Successfully recovered the database
    INFO: 2018-04-22 14:56:17: Opening the database with resetlogs
    INFO: 2018-04-22 14:56:27: Successfully opened the database after recovery
    INFO: 2018-04-22 14:56:31: Setting the temporary tablespace for database : newdb
    INFO: 2018-04-22 14:56:33: Successfully set the temporary tablespace for the database : newdb
    INFO: 2018-04-22 14:57:35: Successfully changed the Database ID
    INFO: 2018-04-22 14:58:51: Adding the Database resource to the clusterware
    INFO: 2018-04-22 14:59:48: Successfully started the database
    INFO: 2018-04-22 14:59:48: Updating the TNS entries for the database newdb
    INFO: 2018-04-22 15:00:24: Successfully set the RMAN SNAPSHOT control file
    INFO: 2018-04-22 15:00:34: Disabling the external references in the database ‘newdb’ inherited from ‘odatest’
    INFO: 2018-04-22 15:00:35: Successfully disabled the external references
    INFO: 2018-04-22 15:00:59: Run the SQL script ‘/u01/app/oracle/product/12.1.0.2/dbhome_1/enable_external_refs_newdb_oMj0.sql’ on the 
    database ‘newdb’ to enable these external references
     Also need to restart the database after running the SQL script
    SUCCESS: 2018-04-22 15:01:57: Successfully created the Database ‘newdb’ from ‘odatest’


    • List the databases

    We can now see the newdb database created and it using ACFS file system


    [root@odanode1 ~]# oakcli show databases
    Name     Type       Storage   HomeName             HomeLocation                               Version                     
    —–    ——     ——–  ————–       —————-                           ———-                  
    orcldb   RAC        ACFS      OraDb12102_home1     /u01/app/oracle/product/12.1.0.2/dbhome_1  12.1.0.2.170117(24732082,24828633)
    newdb    RAC        ACFS      OraDb12102_home1     /u01/app/oracle/product/12.1.0.2/dbhome_1  12.1.0.2.170117(24732082,24828633)
    odatest  RAC        ACFS      OraDb12102_home1     /u01/app/oracle/product/12.1.0.2/dbhome_1  12.1.0.2.170117(24732082,24828633)


    • Verify the newly create snapshot database

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


    NAME      OPEN_MODE            DATABASE_ROLE    LOG_MODE
    ——— ——————– —————- ————
    NEWDB     READ WRITE           PRIMARY          ARCHIVELOG
    NEWDB     READ WRITE           PRIMARY          ARCHIVELOG


    SQL> archive log list;
    Database log mode              Archive Mode
    Automatic archival             Enabled
    Archive destination            USE_DB_RECOVERY_FILE_DEST
    Oldest online log sequence     2
    Next log sequence to archive   3
    Current log sequence           3
    SQL> set lines 400 pages 200
    SQL> col name for a100
    SQL> select name, status from v$datafile;


    NAME                                                                                                 STATUS
    —————————————————————————————————- ——-
    /u02/app/oracle/oradata/datastore/.ACFS/snaps/newdb/NEWDB/datafile/o1_mf_system_doqhbjop_.dbf        SYSTEM
    /u02/app/oracle/oradata/datastore/.ACFS/snaps/newdb/NEWDB/datafile/o1_mf_sysaux_doqhbnkx_.dbf        ONLINE
    /u02/app/oracle/oradata/datastore/.ACFS/snaps/newdb/NEWDB/datafile/o1_mf_undotbs1_doqhbq7b_.dbf      ONLINE
    /u02/app/oracle/oradata/datastore/.ACFS/snaps/newdb/NEWDB/datafile/o1_mf_undotbs2_doqhbzyd_.dbf      ONLINE
    /u02/app/oracle/oradata/datastore/.ACFS/snaps/newdb/NEWDB/datafile/o1_mf_users_doqhc0tz_.dbf         ONLINE
    /u02/app/oracle/oradata/datastore/.ACFS/snaps/newdb/NEWDB/datafile/o1_mf_test_ffsnh1x9_.dbf          ONLINE


    6 rows selected.


    [root@odanode1 ~]# cd /u02/app/oracle/oradata/datastore/.ACFS/snaps/newdb/NEWDB/datafile
    [root@odanode1 datafile]# ls -ltr
    total 3676440
    -rw-r—– 1 oracle asmadmin   23076864 Apr 21 06:00 o1_mf_temp_doqhbr2n_.tmp
    -rw-r—– 1 oracle asmadmin  387981312 Apr 22 14:54 o1_mf_undotbs2_doqhbzyd_.dbf
    -rw-r—– 1 oracle asmadmin    5251072 Apr 22 14:54 o1_mf_users_doqhc0tz_.dbf
    -rw-r—– 1 oracle asmadmin 1073750016 Apr 22 14:54 o1_mf_test_ffsnh1x9_.dbf
    -rw-rw—- 1 oracle asmadmin   23076864 Apr 22 15:01 o1_mf_temp_ffspq06s_.tmp
    -rw-r—– 1 oracle asmadmin  734011392 Apr 22 15:21 o1_mf_system_doqhbjop_.dbf
    -rw-r—– 1 oracle asmadmin  319823872 Apr 22 15:21 o1_mf_undotbs1_doqhbq7b_.dbf
    -rw-r—– 1 oracle asmadmin 1216356352 Apr 22 15:21 o1_mf_sysaux_doqhbnkx_.dbf




    Conclusion


    In this article we have demonstrated how to create snapshot database using oakcli. Using oakcli automates the entire snapshot database creating process. Snapshot Database is created by taking a snapshot of the Oracle ASM Cluster File System (ACFS) where the source data files reside.

  • Oracle Database Appliance: Create Database Using Database Configuration Parameter File

    Introduction


    In my previous articles, we have learned how to Create Oracle Database Appliance Database Configuration Parameter file. 


    If you want to create a database with different database configuration parameter then you must create a database configuration file with your desired parameters. You can use the ‘oakcli create db_config_params’ command to create a database configuration file. The configuration files are created under the locatoin ‘/opt/oracle/oak/install/dbconf’ with a default extension of ‘.dbconf’.


    Refer to the blog post at on how to create a databsae configuration file
    http://netsoftmate.blogspot.com/2018/05/oracle-database-appliance-database-configuration-file.html


    In this article we will demonstrate how to create a database using custom configuration parameter file.


    One can use OAKCLI or DBCA utility to create the database on ODA. But it is recommended to use OAKCLI on ODA to create the database. With OAKCLI, creating database is very easy and it is just one command.


    Courtesy Oracle



    Steps to Create a Database Using Configuration File


    • Login to Compute node 1 as root user and execute the following command:

    [root@odanode1]# oakcli create database -db testdb -oh OraDb12102_home1 -params ayx.conf
    INFO: 2018-04-23 16:13:42: Please check the logfile  ‘/opt/oracle/oak/log/odanode1/tools/12.1.2.10.0/createdb_testdb_94038.log’ for more details


    Please enter the ‘root’  password :
    Please re-enter the ‘root’ password:


    Please enter the ‘SYSASM’  password : (During deployment we set the SYSASM password to ‘welcome1’):
    Please re-enter the ‘SYSASM’ password:


    Please select one of the following for Database type  [1 .. 3] :
    1    => OLTP
    2    => DSS
    3    => In-Memory
    1 –> Enter 1 for OLTP and hit return
    The selected value is : OLTP
    Please select one of the following for Database Deployment  [1 .. 3] :
    1    => EE : Enterprise Edition
    2    => RACONE
    3    => RAC
    3 –> Enter 3 for RAC and hit return
    The selected value is : RAC


    Specify the  Database Class (1. odb-01 ‘1 core, 8 GB memory’   2. Others) [1] : 2 –> Enter 2 for Others and hit return


    Please select one of the following for Database Class [1 .. 9] :
    1    => odb-01s  (   1 cores ,     4 GB memory)
    2    =>  odb-01  (   1 cores ,     8 GB memory)
    3    =>  odb-02  (   2 cores ,    16 GB memory)
    4    =>  odb-04  (   4 cores ,    32 GB memory)
    5    =>  odb-06  (   6 cores ,    48 GB memory)
    6    =>  odb-12  (  12 cores ,    96 GB memory)
    7    =>  odb-16  (  16 cores ,   128 GB memory)
    8    =>  odb-20  (  20 cores ,   160 GB memory)
    9    =>  odb-24  (  24 cores ,   192 GB memory)
    3 –> Enter 3 for odb-02
    The selected value is : odb-02  (   2 cores ,    16 GB memory)
    INFO   : Logging all actions in the file /opt/oracle/oak/onecmd/tmp/odanode1-20180423161500.log and traces in the file /opt/oracle/oak/onecmd/tmp/odanode1-20180423161500.trc
    INFO   : Loading the configuration file /opt/oracle/oak/onecmd/create_database.params…
    INFO   : Creating the node list files…
    INFO   : Setting up ssh for root…
    INFO   : Setting up SSH across the Private Network…


    …………Completed
    INFO   : Running as root: /usr/bin/ssh -l root 192.168.16.24 /root/DoAllcmds.sh
    INFO   : Background process 99086 (node: 192.168.16.24) gets done with the exit code 0
    INFO   : Running as root: /usr/bin/ssh -l root 192.168.16.25 /root/DoAllcmds.sh
    INFO   : Background process 99132 (node: 192.168.16.25) gets done with the exit code 0
    INFO   : Setting up SSH completed successfully
    INFO   : Running the command /usr/bin/rsync -tarqvz /opt/oracle/oak/onecmd/ root@192.168.16.25:/opt/oracle/oak/onecmd –exclude=*zip –exclude=*gz –exclude=*log –exclude=*trc –exclude=*rpm to sync directory</opt/oracle/oak/onecmd> on node <192.168.16.25>
    SUCCESS: Ran /usr/bin/rsync -tarqvz /opt/oracle/oak/onecmd/ root@192.168.16.25:/opt/oracle/oak/onecmd –exclude=*zip –exclude=*gz —exclude=*log –exclude=*trc –exclude=*rpm and it returned: RC=0


    ……….Completed
    INFO   : Did not do scp for node : odanode1
    INFO   : Running as root: /usr/bin/ssh -l root odanode1 /root/DoAllcmds.sh
    INFO   : Background process 99840 (node: odanode1) gets done with the exit code 0
    INFO   : Running as root: /usr/bin/ssh -l root odanode2 /root/DoAllcmds.sh
    INFO   : Background process 99887 (node: odanode2) gets done with the exit code 0
    INFO   : Did not do scp for node : odanode1
    INFO   : Running as root: /usr/bin/ssh -l root odanode1 /opt/oracle/oak/onecmd/tmp/DoAllcmds-20180423161544.sh
    INFO   : Background process 99960 (node: odanode1) gets done with the exit code 0
    INFO   : Running as root: /usr/bin/ssh -l root odanode2 /opt/oracle/oak/onecmd/tmp/DoAllcmds-20180423161544.sh
    INFO   : Background process 307 (node: odanode2) gets done with the exit code 0
    INFO   : Setting up SSH for user oracle…
    …INFO   : checking nodes in /opt/oracle/oak/onecmd/tmp/db_nodes…
    …
    SUCCESS: All nodes in /opt/oracle/oak/onecmd/tmp/db_nodes are pingable and alive.
    INFO   : Checking SSH setup for user (oracle) on nodes in /opt/oracle/oak/onecmd/tmp/db_nodes…
    INFO   : Did not do scp for node : odanode1
    INFO   : This is root, will become oracle and run: /bin/su oracle -c /usr/bin/ssh -l oracle odanode1 /opt/oracle/oak/onecmd/tmp/DoAllcmds-20180423161609.sh
    INFO   : Running on the local node: /bin/su oracle -c /opt/oracle/oak/onecmd/tmp/DoAllcmds-20180423161609.sh
    INFO   : Background process 1220 (node: odanode1) gets done with the exit code 0
    INFO   : This is root, will become oracle and run: /bin/su oracle -c /usr/bin/ssh -l oracle odanode2 /opt/oracle/oak/onecmd/tmp/DoAllcmds-20180423161609.sh
    INFO   : Background process 1266 (node: odanode2) gets done with the exit code 0
    INFO   : Setting up ACFS storage
    INFO   : Did not do scp for node : odanode1
    INFO   : Running as root: /usr/bin/ssh -l root odanode1 /opt/oracle/oak/onecmd/tmp/acfsm_94038.sh
    INFO   : Running as root: /usr/bin/ssh -l root odanode2 /opt/oracle/oak/onecmd/tmp/acfsm_94038.sh
    INFO   : Background process 1669 (node: odanode1) gets done with the exit code 0
    INFO   : Background process 1715 (node: odanode2) gets done with the exit code 0
    INFO: 2018-04-23 16:16:27: Successfully setup the storage structure for the database ‘testdb’
    SUCCESS: Successfully setup ACFS storage for the database testdb
    INFO   : Creating Database using DBCA…
    INFO   : Did not do scp for node : odanode1
    INFO   : Running as root: /usr/bin/ssh -l root odanode1 /opt/oracle/oak/onecmd/tmp/DoAllcmds-20180423161627.sh
    INFO   : Background process 4974 (node: odanode1) gets done with the exit code 0
    INFO   : Running as root: /usr/bin/ssh -l root odanode2 /opt/oracle/oak/onecmd/tmp/DoAllcmds-20180423161627.sh
    INFO   : Background process 5026 (node: odanode2) gets done with the exit code 0
    INFO   : Running DBCA using /opt/oracle/oak/onecmd/tmp/dbca-testdb.sh on odanode1 as oracle…
    INFO   : Check output in /opt/oracle/oak/onecmd/tmp/dbca-testdb-20180423161500.log on odanode1
    INFO   : This is root, will become oracle and run: /bin/su oracle -c /usr/bin/ssh -l oracle odanode1 /opt/oracle/oak/onecmd/tmp/dbca-testdb.sh
    INFO   : Running on the local node: /bin/su oracle -c /opt/oracle/oak/onecmd/tmp/dbca-testdb.sh
             Instance testdb1 is running on node odanode1
             Instance testdb2 is running on node odanode2
    INFO   : One or more Instances running on the cluster nodes.
    INFO   : Running export ORACLE_HOME=/u01/app/oracle/product/12.1.0.2/dbhome_1;/u01/app/oracle/product/12.1.0.2/dbhome_1/bin/srvctl setenv database -d testdb -t ‘TZ=America/New_York’ to set DB timezone
    INFO   : Running the command /u01/app/12.1.0.2/grid/bin/crsctl stat resource ora.testdb.db -p
    .INFO   : Did not do scp for node : odanode1
    ..
    INFO   : This is root, will become oracle and run: /bin/su oracle -c /usr/bin/ssh -l oracle odanode1 /opt/oracle/oak/onecmd/tmp/dbupdates-testdb.sh
    INFO   : Running on the local node: /bin/su oracle -c /opt/oracle/oak/onecmd/tmp/dbupdates-testdb.sh
    INFO   : Running export ORACLE_HOME=/u01/app/oracle/product/12.1.0.2/dbhome_1;/u01/app/oracle/product/12.1.0.2/dbhome_1/bin/srvctl stop database -d testdb
    INFO   : Running export ORACLE_HOME=/u01/app/oracle/product/12.1.0.2/dbhome_1;/u01/app/oracle/product/12.1.0.2/dbhome_1/bin/srvctl start database -d testdb
    INFO: 2018-04-23 16:31:42: Successfully set the RMAN SNAPSHOT control file
    .INFO   : Did not do scp for node : odanode1
    ..
    INFO   : This is root, will become oracle and run: /bin/su oracle -c /usr/bin/ssh -l oracle odanode1 /opt/oracle/oak/onecmd/tmp/runDatapatch.sh
    INFO   : Running on the local node: /bin/su oracle -c /opt/oracle/oak/onecmd/tmp/runDatapatch.sh
    SUCCESS: 2018-04-23 16:32:13: Successfully created the Database : testdb
    INFO   : Resecuring the environment… odanode1 odanode2
    INFO   : Removing the SSH setup for root…
    INFO   : Running as root: /usr/bin/ssh -l root odanode1 chmod 751 /opt/oracle/oak/onecmd/tmp
    INFO   : Running as root: /usr/bin/ssh -l root odanode2 chmod 751 /opt/oracle/oak/onecmd/tmp
    INFO   : Running as root: /usr/bin/ssh -l root odanode2 /bin/rm -rf /root/.ssh
    INFO   : Running as root: /usr/bin/ssh -l root odanode1 /bin/rm -rf /root/.ssh




    Conclusion
    In this article we have learned how to create a database on Oracle Database Appliance using Database Configuration parameter file. If you want to create a database with different database configuration parameter then you must create a database configuration file first with your desired parameters. Creating an Oracle Database on ODA is just one step process. OAKCLI utility takes care of everything for you to create the database.

  • How to fix “ORA-15001”, “ORA-17502”, “ORA-01119”

    How to fix “ORA-15001”, “ORA-17502”, “ORA-01119”

    While creating a tablespace on Oracle Database 11g I ran into a issue related to DB_CREATE_FILE_DEST (OMF parameter).  The DB_CREATE_FILE_DEST parameter was pointing to incorrect ASM Disk Group name which doesn’t existing. The issues was fixed by correcting the DB_CREATE_FILE_DEST parameter to point to the correct ASM Disk Group name.

     In this article I would like to demonstrate how to fix create tablespace error which is to incorrect DB_CREATE_FILE_DEST parameter.

     Create Tablespace ran the into the issue as below:

    The create tablespace failed as the ASM Disk Group +DATA doesn’t existing.

    ORA Errors:
     
    ORA-01119: error in creating database file ‘+DATA’
    ORA-17502: ksfdcre:4 Failed to create file +DATA
    ORA-15001: diskgroup “DATA” does not exist or is not mounted
     
    Reason for above error:

     The above error is due to initialization parameter DB_CREATE_FILE_DEST pointing to incorrect value. Change/Modify the parameter to fix the issue. 
     

    Check  parameter db_create_file_dest Value:


     About DB_CREATE_FILE_DEST

     DB_CREATE_FILE_DEST specifies the default location for Oracle-managed datafiles.

     DB_CREATE_FILE_DEST : directory or disk group
    Default value : NO Default value.
    Modifiable :  ALTER SESSION, ALTER SYSTEM

     Identify the ASM Disk Group


     Here the Data Disk Group name is +DATA_DM01

     

    Modify the parameter DB_CREATE_FILE_DEST parameter to point it to correct ASM Disk Group name. You can use ALTER SYSTEM SET command to make it permanent as well.

     

     Now you can Create a Tablespace again as follows:


     This time the tablespace was created successfully without errors as the default OMF datafile location is pointing to correct ASM Disk Group

    Conclusion:

    In this article we have demonstrated how to fix ORA errors “ORA-15001”, “ORA-17502″,”ORA-01119” which due to incorrect defualt ASM Diskgroup set at Database using parameter DB_CREATE_FILE_DEST. 

    eBook - Oracle Exadata X8M Patching Recipes | Netsoftmate

  • RMAN Duplicate With Same Database Name and Same Directory Structure

    Overview


    Oracle Recovery Manager (RMAN) provides a comprehensive foundation for efficiently backing up and recovering the Oracle databases, it provides a common interface, via command line and Enterprise Manager, for backup tasks across different host operating systems, automates administration of your backup strategies.
    Environment Details
    Target (Source) details
    Database Name
    prod
    Hostname
    Snsm-linux02
    Ip Address
    172.16.110.18
    OS
    Linux
    Version
    x86_64
    Datafile Location
    /data2/prod
    Backup Location
    /backup/rman_backup
    Tns details:
    PROD =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP)(HOST = 172.16.110.18)(PORT = 1521))
        (CONNECT_DATA =
          (SERVER = DEDICATED)
          (SERVICE_NAME = prod)
        )
      )
    Destination (Auxiliary) details:
    Database Name
    Prod
    Hostname
    Nsm-linux01
    Ip Address
    172.16.110.16
    OS
    Linux
    Version
    x86_64
    Datafile Location
    /data2/prod
    Backup Location
    /backup/rman_backup
    Tns details:
    DUP =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP)(HOST = 172.16.110.16)(PORT = 1521))
        (CONNECT_DATA =
          (SERVER = DEDICATED)
          (SERVICE_NAME = dup)
        )
      )

    Pre-requisites

    • Oracle net configuration
    • Both target and destination server should have tns entries
    • Static listener registration on auxiliary site
    • Service should be register on aux listener
    • Password files from target database
    • Sqlnet.ora should have correct parameters
    • Target database should be running through spfile
    • Check connectivity between target and destination server
    Steps on target (source) server

    • Put tns entry of auxiliary database into target $ORACLE_HOME/network/admin directory
    [oracle@Snsm-linux02 admin]$ cd /data2/app/oracle/product/11.2.0/network/admin
    [oracle@Snsm-linux02 admin]$ vi tnsnames.ora
    DUP =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP)(HOST = 172.16.110.16)(PORT = 1521))
        (CONNECT_DATA =
          (SERVER = DEDICATED)
          (SERVICE_NAME = dup)
        )
      )
    [oracle@Snsm-linux02 admin]$ tnsping dup
    TNS Ping Utility for Linux: Version 11.2.0.1.0 – Production on 01-APR-2015 12:34:19
    Copyright (c) 1997, 2009, Oracle.  All rights reserved.
    Used parameter files:
    /data2/app/oracle/product/11.2.0/network/admin/sqlnet.ora
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 172.16.110.16)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED)
    (SERVICE_NAME = dup)))
    OK (0 msec)
    •  Check database whether it is running in archive log mode.
    SQL> select name, open_mode, log_mode from v$database;
    NAME       OPEN_MODE            LOG_MODE
    ———- ——————– —————
    PROD       READ WRITE           ARCHIVELOG
    • Check database is running from spfile.
    SQL> select value from v$parameter where name=’spfile’;
    VALUE
    —————————————————————–
    /data2/app/oracle/product/11.2.0/dbs/spfileprod.ora
    or
    SQL> show parameter pfile
    NAME                                 TYPE                              VALUE
    ———————————— ——————————— ——————————
    spfile                               string                            /data2/app/oracle/product/11.2
                                                                           .0/dbs/spfileprod.ora
    • Create pfile from spfile.
    SQL> create pfile=’/backup/rman_backup/initprod.ora’ from spfile;
    File created.
    • Create password file.
    [oracle@Snsm-linux02 dbs]$ pwd
    /data2/app/oracle/product/11.2.0/dbs
    [oracle@Snsm-linux02 dbs]$orapwd file=orapwprod password=oracle
    • Copy the password file and init file to destination $ORACLE_HOME/dbs directory using scp or ftp
    scp orapwprod oracle@172.16.110.18:/data2/app/oracle/product/11.2.0/dbs/
    scp /backup/rman_backup/initprod.ora oracle@172.16.110.18:/data2/app/oracle/product/11.2.0/dbs/
    Steps on destination server
    • Put static listener entry into listener.ora file in $ORACLE_HOME/network/admin directory.
    [oracle@Nsm-linux01 admin]$ cd /data2/app/oracle/product/11.2.0/network/admin
    [oracle@Nsm-linux01 admin]$
    SID_LIST_LISTENER =
      (SID_LIST =
        (SID_DESC =
          (GLOBAL_DBNAME = dup)
          (ORACLE_HOME = /data2/app/oracle/product/11.2.0)
          (SID_NAME = prod)
        )
      )
    LISTENER =
      (DESCRIPTION_LIST =
        (DESCRIPTION =
          (ADDRESS = (PROTOCOL = TCP)(HOST = 172.16.110.16)(PORT = 1521))
        )
        (DESCRIPTION =
          (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
        )
      )
    Here global_name is nothing but service name and sid_name is instance name
    Now reload the listener and check the services
    [oracle@Nsm-linux01 admin]$ lsnrctl
    LSNRCTL for Linux: Version 11.2.0.1.0 – Production on 01-APR-2015 12:46:41
    Copyright (c) 1991, 2009, Oracle.  All rights reserved.
    Welcome to LSNRCTL, type “help” for information.
    LSNRCTL> reload
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=172.16.110.16)(PORT=1521)))
    The command completed successfully
    LSNRCTL> services
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=172.16.110.16)(PORT=1521)))
    Services Summary…
    Service “dup” has 1 instance(s).
      Instance “prod”, status UNKNOWN, has 1 handler(s) for this service…
        Handler(s):
          “DEDICATED” established:0 refused:0
             LOCAL SERVER
    Service “prod” has 1 instance(s).
          “DEDICATED” established:0 refused:0 state:ready
             LOCAL SERVER
    The command completed successfully
    • Put Tns entry for target (source) database in $ORACLE_HOME/network/admin directory
    [oracle@Nsm-linux01 admin]$ vi tnsnames.ora
    PROD =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP)(HOST = 172.16.110.18)(PORT = 1521))
        (CONNECT_DATA =
          (SERVER = DEDICATED)
          (SERVICE_NAME = prod)
        )
      )
    [oracle@Nsm-linux01 admin]$ tnsping prod
    TNS Ping Utility for Linux: Version 11.2.0.1.0 – Production on 01-APR-2015 12:49:28
    Copyright (c) 1997, 2009, Oracle.  All rights reserved.
    Used parameter files:
    /data2/app/oracle/product/11.2.0/network/admin/sqlnet.ora
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 172.16.110.18)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED)
    (SERVICE_NAME = prod)))
    OK (10 msec)
    • Create the directory structure same as target(source) server.
    [oracle@Nsm-linux01 admin]$ mkdir -p /data2/prod
    [oracle@Nsm-linux01 admin]$ mkdir -p /backup/archive
    • Set the oracle Sid and start the instance in no mount stage.
    [oracle@Nsm-linux01 admin]$ export ORACLE_SID=prod
    [oracle@Nsm-linux01 admin]$ sqlplus
    SQL*Plus: Release 11.2.0.1.0 Production on Wed Apr 1 12:54:37 2015
    Copyright (c) 1982, 2009, Oracle.  All rights reserved.
    Enter user-name: sys as sysdba
    Enter password:
    Connected to an idle instance.
    SQL> startup nomount
    ORACLE instance started.
    Total System Global Area 1152450560 bytes
    Fixed Size                  2212696 bytes
    Variable Size             335547560 bytes
    Database Buffers          805306368 bytes
    Redo Buffers                9383936 bytes
    SQL>
    • Now connect to Rman
    [oracle@Nsm-linux01 admin]$ rman target sys/oracle@prod auxiliary sys/oracle@dup
    Recovery Manager: Release 11.2.0.1.0 – Production on Wed Apr 1 12:56:39 2015
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: PROD (DBID=284539893)
    connected to auxiliary database: PROD (not mounted)
    RMAN>

    • Issue the command to duplicate the database

    RMAN> DUPLICATE TARGET DATABASE TO prod FROM ACTIVE DATABASE NOFILENAMECHECK;
    Starting Duplicate Db at 01-APR-15
    using target database control file instead of recovery catalog
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: SID=63 device type=DISK
    Following is the output.
    contents of Memory Script:
    {
       sql clone “alter system set  db_name =
    ”PROD” comment=
    ”Modified by RMAN duplicate” scope=spfile”;
       sql clone “alter system set  db_unique_name =
    ”PROD” comment=
    ”Modified by RMAN duplicate” scope=spfile”;
       shutdown clone immediate;
       startup clone force nomount
       backup as copy current controlfile auxiliary format  ‘/data2/prod/control01.ctl’;
       restore clone controlfile to  ‘/data2/prod/control02.ctl’ from
    ‘/data2/prod/control01.ctl’;
       alter clone database mount;
    }
    executing Memory Script
    sql statement: alter system set  db_name =  ”PROD” comment= ”Modified by RMAN duplicate” scope=spfile
    sql statement: alter system set  db_unique_name =  ”PROD” comment= ”Modified by RMAN duplicate” scope=spfile
    Oracle instance shut down
    Oracle instance started
    Total System Global Area    1152450560 bytes
    Fixed Size                     2212696 bytes
    Variable Size                335547560 bytes
    Database Buffers             805306368 bytes
    Redo Buffers                   9383936 bytes
    Starting backup at 01-APR-15
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=76 device type=DISK
    channel ORA_DISK_1: starting datafile copy
    copying current control file
    output file name=/data2/app/oracle/product/11.2.0/dbs/snapcf_prod.f tag=TAG20150401T124940 RECID=4 STAMP=875882981
    channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:03
    Finished backup at 01-APR-15
    Starting restore at 01-APR-15
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: SID=63 device type=DISK
    channel ORA_AUX_DISK_1: copied control file copy
    Finished restore at 01-APR-15
    database mounted
    contents of Memory Script:
    {
       set newname for datafile  1 to
    “/data2/prod/system01.dbf”;
       set newname for datafile  2 to
    “/data2/prod/sysaux01.dbf”;
       set newname for datafile  3 to
    “/data2/prod/undotbs01.dbf”;
       set newname for datafile  4 to
    “/data2/prod/users01.dbf”;
       set newname for datafile  5 to
    “/data2/prod/example01.dbf”;
       backup as copy reuse
       datafile  1 auxiliary format
    “/data2/prod/system01.dbf”   datafile
    2 auxiliary format
    “/data2/prod/sysaux01.dbf”   datafile
    3 auxiliary format
    “/data2/prod/undotbs01.dbf”   datafile
    4 auxiliary format
    “/data2/prod/users01.dbf”   datafile
    5 auxiliary format
    “/data2/prod/example01.dbf”   ;
       sql ‘alter system archive log current’;
    }
    executing Memory Script
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    Starting backup at 01-APR-15
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile copy
    input datafile file number=00001 name=/data2/prod/system01.dbf
    output file name=/data2/prod/system01.dbf tag=TAG20150401T124955
    channel ORA_DISK_1: datafile copy complete, elapsed time: 00:01:15
    channel ORA_DISK_1: starting datafile copy
    input datafile file number=00002 name=/data2/prod/sysaux01.dbf
    output file name=/data2/prod/sysaux01.dbf tag=TAG20150401T124955
    channel ORA_DISK_1: datafile copy complete, elapsed time: 00:01:05
    channel ORA_DISK_1: starting datafile copy
    input datafile file number=00005 name=/data2/prod/example01.dbf
    output file name=/data2/prod/example01.dbf tag=TAG20150401T124955
    channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:15
    channel ORA_DISK_1: starting datafile copy
    input datafile file number=00003 name=/data2/prod/undotbs01.dbf
    output file name=/data2/prod/undotbs01.dbf tag=TAG20150401T124955
    channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:07
    channel ORA_DISK_1: starting datafile copy
    input datafile file number=00004 name=/data2/prod/users01.dbf
    output file name=/data2/prod/users01.dbf tag=TAG20150401T124955
    channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:01
    Finished backup at 01-APR-15
    sql statement: alter system archive log current
    contents of Memory Script:
    {
       backup as copy reuse
       archivelog like  “/backup/archive/1_116_872701561.dbf” auxiliary format
    “/backup/archive/1_116_872701561.dbf”   ;
       catalog clone archivelog  “/backup/archive/1_116_872701561.dbf”;
       switch clone datafile all;
    }
    executing Memory Script
    Starting backup at 01-APR-15
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting archived log copy
    input archived log thread=1 sequence=116 RECID=112 STAMP=875883160
    output file name=/backup/archive/1_116_872701561.dbf RECID=0 STAMP=0
    channel ORA_DISK_1: archived log copy complete, elapsed time: 00:00:03
    Finished backup at 01-APR-15
    cataloged archived log
    archived log file name=/backup/archive/1_116_872701561.dbf RECID=112 STAMP=875883644
    datafile 1 switched to datafile copy
    input datafile copy RECID=4 STAMP=875883644 file name=/data2/prod/system01.dbf
    datafile 2 switched to datafile copy
    input datafile copy RECID=5 STAMP=875883644 file name=/data2/prod/sysaux01.dbf
    datafile 3 switched to datafile copy
    input datafile copy RECID=6 STAMP=875883645 file name=/data2/prod/undotbs01.dbf
    datafile 4 switched to datafile copy
    input datafile copy RECID=7 STAMP=875883645 file name=/data2/prod/users01.dbf
    datafile 5 switched to datafile copy
    input datafile copy RECID=8 STAMP=875883645 file name=/data2/prod/example01.dbf
    contents of Memory Script:
    {
       set until scn  4529390;
       recover
       clone database
        delete archivelog
       ;
    }
    executing Memory Script
    executing command: SET until clause
    Starting recover at 01-APR-15
    using channel ORA_AUX_DISK_1
    starting media recovery
    archived log for thread 1 with sequence 116 is already on disk as file /backup/archive/1_116_872701561.dbf
    archived log file name=/backup/archive/1_116_872701561.dbf thread=1 sequence=116
    media recovery complete, elapsed time: 00:00:02
    Finished recover at 01-APR-15
    contents of Memory Script:
    {
       shutdown clone immediate;
       startup clone nomount;
       sql clone “alter system set  db_name =
    ”PROD” comment=
    ”Reset to original value by RMAN” scope=spfile”;
       sql clone “alter system reset  db_unique_name scope=spfile”;
       shutdown clone immediate;
       startup clone nomount;
    }
    executing Memory Script
    database dismounted
    Oracle instance shut down
    connected to auxiliary database (not started)
    Oracle instance started
    Total System Global Area    1152450560 bytes
    Fixed Size                     2212696 bytes
    Variable Size                335547560 bytes
    Database Buffers             805306368 bytes
    Redo Buffers                   9383936 bytes
    sql statement: alter system set  db_name =  ”PROD” comment= ”Reset to original value by RMAN” scope=spfile
    sql statement: alter system reset  db_unique_name scope=spfile
    Oracle instance shut down
    connected to auxiliary database (not started)
    Oracle instance started
    Total System Global Area    1152450560 bytes
    Fixed Size                     2212696 bytes
    Variable Size                335547560 bytes
    Database Buffers             805306368 bytes
    Redo Buffers                   9383936 bytes
    sql statement: CREATE CONTROLFILE REUSE SET DATABASE “PROD” RESETLOGS ARCHIVELOG
      MAXLOGFILES     16
      MAXLOGMEMBERS      3
      MAXDATAFILES      100
      MAXINSTANCES     8
      MAXLOGHISTORY      292
    LOGFILE
      GROUP  1 ( ‘/data2/prod/redo01.log’ ) SIZE 50 M  REUSE,
      GROUP  2 ( ‘/data2/prod/redo02.log’ ) SIZE 50 M  REUSE,
      GROUP  3 ( ‘/data2/prod/redo03.log’ ) SIZE 50 M  REUSE
    DATAFILE
      ‘/data2/prod/system01.dbf’
    CHARACTER SET WE8MSWIN1252
    contents of Memory Script:
    {
       set newname for tempfile  1 to
    “/data2/prod/temp01.dbf”;
       switch clone tempfile all;
       catalog clone datafilecopy  “/data2/prod/sysaux01.dbf”,
    “/data2/prod/undotbs01.dbf”,
    “/data2/prod/users01.dbf”,
    “/data2/prod/example01.dbf”;
       switch clone datafile all;
    }
    executing Memory Script
    executing command: SET NEWNAME
    renamed tempfile 1 to /data2/prod/temp01.dbf in control file
    cataloged datafile copy
    datafile copy file name=/data2/prod/sysaux01.dbf RECID=1 STAMP=875883671
    cataloged datafile copy
    datafile copy file name=/data2/prod/undotbs01.dbf RECID=2 STAMP=875883671
    cataloged datafile copy
    datafile copy file name=/data2/prod/users01.dbf RECID=3 STAMP=875883671
    cataloged datafile copy
    datafile copy file name=/data2/prod/example01.dbf RECID=4 STAMP=875883672
    datafile 2 switched to datafile copy
    input datafile copy RECID=1 STAMP=875883671 file name=/data2/prod/sysaux01.dbf
    datafile 3 switched to datafile copy
    input datafile copy RECID=2 STAMP=875883671 file name=/data2/prod/undotbs01.dbf
    datafile 4 switched to datafile copy
    input datafile copy RECID=3 STAMP=875883671 file name=/data2/prod/users01.dbf
    datafile 5 switched to datafile copy
    input datafile copy RECID=4 STAMP=875883672 file name=/data2/prod/example01.dbf
    contents of Memory Script:
    {
       Alter clone database open resetlogs;
    }
    executing Memory Script
    database opened
    Finished Duplicate Db at 01-APR-15
     Issues which we have faced are as follows              

    Everything has went well listener services were also worked fine, RMAN connectivity from auxiliary server also fine using net service name but  When issue the duplicate database command from RMAN> prompt it has thrown following error.
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 03/31/2015 16:01:01
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/31/2015 16:01:01
    ORA-17629: Cannot connect to the remote database server
    ORA-17627: ORA-12154: TNS:could not resolve the connect identifier specified
    ORA-17629: Cannot connect to the remote database server
    Then we have searched for solutions, we get one MOS note 1144273.1
    This note gives some idea like causes and solutions from that we have checked in our databases on destination server there are wrong parameters in sqlnet.ora then we have corrected the sqlnet.ora file as follows
    [oracle@Nsm-linux01 admin]$ cat sqlnet.ora
    # sqlnet.ora Network Configuration File: /data2/app/oracle/product/11.2.0/network/admin/sqlnet.ora
    # Generated by Oracle configuration tools.
    SQLNET.AUTHENTICATION_SERVICES = (NTS,NONE)
    #NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)
    ADR_BASE = /data2/app/oracle
    Now we have executed again, this time we get different error, check below.
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 03/31/2015 16:23:02
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/31/2015 16:23:02
    ORA-17628: Oracle error 19505 returned by remote Oracle server
    After dig out the error we get to know that there is no directory structure is available on destination server to accommodate data files and control  Files, we have created the directory structure and execute the duplicate command again, this time has successful.
     Additionally there is one more MOS note for known issues while duplicating RMAN. 1366290.1





    Conclusion

    In the above article, we have learned that Active Duplication using Rman utility with same database name and same directory structure, and we have faced some errors and their work around.

    BY
    Name: Omer
    Designation: Senior Database Engineer
    Organization: Netsoftmate IT Solutions.
    Email: info@netsoftmate.com

    Avast logo
    This email has been checked for viruses by Avast antivirus software.
    www.avast.com

  • How to find Hostname from AWS console

    Overview

    All AWS RDS Instances has DNS name and port number which is also known as endpoint, to establish connection to your AWS DB Instance you require DNS names and port number, we can find endpoint details of AWS RDS Instance through AWS console.

    In this article we will demonstrate, how to find endpoint details from AWS console.

    Steps to find endpoint of AWS RDS Instance


    • Login to AWS console
    please check previous article on how to login AWS console by click on following link


    • From console got to services then RDS


    • Click on RDS


    • Click on Instances


    • Choose oracle database instance and see database properties from Instance action tab.



    • Click on see details to display database instance properties.
    Conclusion
    In preceding article we have learned that how to find endpoint details from AWS console.




    Next, How to establish connection between on-premises and AWS Cloud…







    By
    Name : Omer
    Designation : Senior Database Engineer
    Organization: Netsoftmate IT Solutions    . 

  • How to Create AWS RDS Instance

    Amazon Web Services (AWS) is a secure cloud services platform, It offers compute power, database storage, evolving cloud computing platform provided by Amazon, content delivery and other functionality to help businesses scale up 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 visit https://aws.amazon.com/rds/

    In this article we will demonstrate how to create an AWS RDS Instance.

    Steps to create AWS RDS Instance (Oracle EE)


    • Login to AWS console, click here to know more about how to login to console
    • On AWS console click on RDS dashboard


    • Click on Get started now,  then on next page select engine
    • Click on Oracle Engine to create Oracle Database Instance


    • Select edition, here we are selecting enterprise edition,then another window appear where we have to provide more details, here choose license model as bring your own license

    • Now choose DB version, we have selected latest version


    • Now choose db instance class, we have choose DB instance class as db.r4.xlarge – this class has 4 cpu, 30 GB memory, to know more about Db instance class check this

    • Provide storage type, we have selected IOPS to learn more about AWS storage type please check following link.


    • Provide database settings, like DB name, master username credentials this master username we will use for connecting to database through back end.


    • After specifying DB details now move next window to provide advance configuration settings, like VPC details, security group


    To learn more about VPC(virtual private cloud) check this link

    To Learn about RDS Security group, please follow this link

    • Provide VPC, security group, database name and port details


    • Under Database options, provide database details character set, option group and parameter group

    • After provide all details click on Launch DB instance


    • Check progress, instance creation is in progress


    • Instance created and backup is in progress


    • Now Database is available for use



    Conclusion
    In this article  we have learned how to Create AWS RDS Instance. We have touch base about virtual private cloud(VPC), RDS security group, DB Instance class and storage types.




    Next, How to find Host name of AWS RDS Instance….


    By
    Name : Omer
    Designation : Senior Database Engineer
    Organization: Netsoftmate IT Solutions    .