Thursday 27 July 2017

Install and Configure DBvisit Standby on Oracle Database Appliance (ODA X6-2S) Part 2

Install and Configure DBvisit Standby on Oracle Database Appliance (ODA X6-2S) Part 1

Install DBvisit on Second Machine (Standby ODA).


1.Download DBvisit Standby from http://www.dbvisit.com/

2.Transfer the files to ODA .
Use scp or winscp

3. Unzip and tar the downloaded file.
 unzip dbvisit-standby8.0.12-el6.zip; tar -xf dbvisit-standby8.0.12-el6.tar

4.create directory for DBvisit Base and change ownership to Oracle and grant  appropriate permissions.
mkdir -p /usr/dbvisit/
chown -R oracle:oinstall /usr/dbvisit/
chmod -R 775 /usr/dbvisit/

5. Install Dbvisit as Oracle user. Its will prompt for information for source and remote hosts.
a. specify the Dbvisit installation directory
b. Choose action (Install, uninstall or terminate)
c. Choose which components to install (Core and central console etc.)
d. specify the Local host name
e. specify the Local Dbvnet PORT
f. specify the Remote host name
g. specify the Remote Dbvnet PORT
h. specify the Dbvnet Passphrase
i. specify the host name to be used for the Dbvisit Agent
j. specify the listening PORT number for Dbvagent
k. specify passphrase for Dbvagent

6. Install Central Console on Standby
a. At end of installation, choose 1 Install component(s).
b. Choose 5 Dbvserver (Dbvisit Central Console)
c. specify the host name to be used for Dbvserver
d. specify the listening port number for Dbvserver

[oracle@ODA2 installer]$ ./install-dbvisit

-----------------------------------------------------------
    Welcome to the Dbvisit software installer.
-----------------------------------------------------------

    It is recommended to make a backup of our current Dbvisit software
    location (Dbvisit Base location) for rollback purposes.

    Installer Directory /u01/dbvisit

>>> Please specify the Dbvisit installation directory (Dbvisit Base).

    The various Dbvisit products and components - such as Dbvisit Standby,
    Dbvisit Dbvnet will be installed in the appropriate subdirectories of
    this path.

    Enter a custom value or press ENTER to accept default [/usr/dbvisit]:
     >
    DBVISIT_BASE = /usr/dbvisit

    -----------------------------------------------------------
    Component      Installer Version   Installed Version
    -----------------------------------------------------------
    standby        8.0.14.19191        not installed
    dbvnet         2.0.14.19191        not installed
    dbvagent       2.0.14.19191        not installed
    dbvserver      2.0.14.19191        not installed

    -----------------------------------------------------------

    What action would you like to perform?
       1 - Install component(s)
       2 - Uninstall component(s)
       3 - Terminate

    Your choice: 1

    Which component do you want to install?
       1 - Core Components (Dbvisit Standby Cli, Dbvnet, Dbvagent)
       2 - Dbvisit Standby Core (Command Line Interface)
       3 - Dbvnet (Dbvisit Network Communication)
       4 - Dbvagent (Dbvisit Agent)
       5 - Dbvserver (Dbvisit Central Console)
       6 - Exit Installer

    Your choice: 1

-----------------------------------------------------------
    Summary of the Dbvisit STANDBY configuration
-----------------------------------------------------------
    DBVISIT_BASE /usr/dbvisit

    Press ENTER to continue

-----------------------------------------------------------
    About to configure DBVISIT DBVNET
-----------------------------------------------------------

>>> Please specify the Local host name to be used by Dbvnet on this server.

    Dbvnet will be listening on the local IP Address on this server which
    resolve to the host name specified here.
    If using a cluster or virtual IP make sure the host name or alias
    specified here resolve to the IP address local to where dbvnet is
    installed.

    Enter a custom value or press ENTER to accept default [ODA2]:
     >

>>> Please specify the Local Dbvnet PORT to be used.

    Dbvnet will be listening on the specified port for incoming connections
    from remote dbvnet connections.  Please make sure that this port is not
    already in use or blocked by any firewall.  You may choose any value
    between 1024 and 65535, however the default of 7890 is recommended.

    Enter a custom value or press ENTER to accept default [7890]:
     >


>>> Please specify the Remote host name to be used by Dbvnet.

    By default Dbvnet will use this remote hostname for any remote
    connections.  Dbvnet must be installed and configured on the specified
    remote host. If using a cluster or virtual IP make sure the host name
    or alias specified here resolve to the IP address local to where dbvnet
    is installed.
    If you are unsure about the remote host name during installation, use
    the default value which will be the current local hostname.

    Enter a custom value or press ENTER to accept default [ODA2]:
     > ODA1


>>> Please specify the Remote Dbvnet PORT to be used.

    Dbvnet will connect to the remote server on this specified port.
    On the remote host Dbvnet will be listening on the specified port for
    incoming connections. Please make sure that this port is not already in
    use or blocked by any firewall.  You may choose any value between 1024
    and 65535, however the default of 7890 is recommended.

    Enter a custom value or press ENTER to accept default [7890]:
     >


>>> Please specify the Dbvnet Passphrase to be used for secure connections.

    The passphrase provided must be the same in both the local and remote
    Dbvnet installations.  It is used to establish a secure (encrypted)
    Dbvnet connections

    Enter a custom value:
     > welcome1

-----------------------------------------------------------
    Summary of the Dbvisit DBVNET configuration
-----------------------------------------------------------
    DBVISIT_BASE /usr/dbvisit
    DBVNET_LOCAL_HOST ODA2
    DBVNET_LOCAL_PORT 7890
    DBVNET_REMOTE_HOST ODA1
    DBVNET_REMOTE_PORT 7890
    DBVNET_PASSPHRASE welcome1

    Press ENTER to continue

-----------------------------------------------------------
    About to configure DBVISIT DBVAGENT
-----------------------------------------------------------


>>> Please specify the host name to be used for the Dbvisit Agent.

    The Dbvisit Agent (Dbvagent) will be listening on this local address.
    If you are using the Dbvserver (GUI) - connections from the GUI will be
    established to the Dbvisit Agent. The Dbvisit Agent address must be
    visible from the Dbvserver (GUI) installation.
    If using a cluster or virtual IP make sure the host name or alias
    specified here resolve to the IP address local to where dbvnet is
    installed.

    Enter a custom value or press ENTER to accept default [ODA2]:
     >


>>> Please specify the listening PORT number for Dbvagent.

    The Dbvisit Agent (Dbvagent) will listening on the specified port for
    incoming requests from the GUI (Dbvserver).  Please make sure that this
    port is not already in use or blocked by any firewall.  You may choose
    any value between 1024 and 65535, however the default of 7891 is
    recommended.

    Enter a custom value or press ENTER to accept default [7891]:
     >


>>> Please specify passphrase for Dbvagent

    Each Dbvisit Agent must have a passpharse specified.  This passphrase
    does not have to match between all the servers.  It will be used to
    establish a secure connection between the GUI (Dbvserver) and the
    Dbvisit Agent.

    Enter a custom value:
     > welcome1

-----------------------------------------------------------
    Summary of the Dbvisit DBVAGENT configuration
-----------------------------------------------------------
    DBVISIT_BASE /usr/dbvisit
    DBVAGENT_LOCAL_HOST ODA2
    DBVAGENT_LOCAL_PORT 7891
    DBVAGENT_PASSPHRASE welcome1
    Press ENTER to continue

-----------------------------------------------------------
    About to install Dbvisit STANDBY
-----------------------------------------------------------
    Component standby installed.

    Press ENTER to continue

-----------------------------------------------------------
    About to install Dbvisit DBVNET
-----------------------------------------------------------
    Component dbvnet installed.

    Press ENTER to continue

-----------------------------------------------------------
    About to install Dbvisit DBVAGENT
-----------------------------------------------------------
    Component dbvagent installed.

    Press ENTER to continue

    -----------------------------------------------------------
    Component      Installer Version   Installed Version
    -----------------------------------------------------------
    standby        8.0.14.19191        8.0.14.19191
    dbvnet         2.0.14.19191        2.0.14.19191
    dbvagent       2.0.14.19191        2.0.14.19191
    dbvserver      2.0.14.19191        not installed

    -----------------------------------------------------------

    What action would you like to perform?
       1 - Install component(s)
       2 - Uninstall component(s)
       3 - Terminate

    Your choice: 1

    Which component do you want to install?
       1 - Core Components (Dbvisit Standby Cli, Dbvnet, Dbvagent)
       2 - Dbvisit Standby Core (Command Line Interface)
       3 - Dbvnet (Dbvisit Network Communication)
       4 - Dbvagent (Dbvisit Agent)
       5 - Dbvserver (Dbvisit Central Console)
       6 - Exit Installer

    Your choice: 5

-----------------------------------------------------------
    About to configure DBVISIT DBVSERVER
-----------------------------------------------------------


>>> Please specify the host name to be used for Dbvserver


    The Dbvisit Web Server (Dbvserver) will be listening on this local
    address. If using a cluster or virtual IP make sure the host name or
    alias specified here resolve to the IP address local to where Dbvserver
    is installed.
    If you are unsure about the remote host name during installation, use
    the default value which will be the current local hostname.

    Enter a custom value or press ENTER to accept default [ODA2]:
     >


>>> Please specify the listening port number for Dbvserver on the local server

    You may choose any value between 1024 and 65535.  The default recommended
    value is 4433.

    Note: if you can not access this port after the installation has
    finished, then please double-check your server firewall settings
    to ensure the selected port is open.
    Enter a custom value or press ENTER to accept default [4433]:
     >

-----------------------------------------------------------
    Summary of the Dbvisit DBVSERVER configuration
-----------------------------------------------------------
    DBVISIT_BASE /usr/dbvisit
    DBVSERVER_LOCAL_HOST ODA2
    DBVSERVER_LOCAL_PORT 4433

    Press ENTER to continue

-----------------------------------------------------------
    About to install Dbvisit DBVSERVER
-----------------------------------------------------------
    Component dbvserver installed.

    Press ENTER to continue

    -----------------------------------------------------------
    Component      Installer Version   Installed Version
    -----------------------------------------------------------
    standby        8.0.14.19191        8.0.14.19191
    dbvnet         2.0.14.19191        2.0.14.19191
    dbvagent       2.0.14.19191        2.0.14.19191
    dbvserver      2.0.14.19191        2.0.14.19191

    -----------------------------------------------------------

    What action would you like to perform?
       1 - Install component(s)
       2 - Uninstall component(s)
       3 - Terminate

    Your choice: 3

>>> Installation completed
    Install log /tmp/dbvisit_install.log.201706211207.


7. Goto DBvisit home and start the processes.

[oracle@ODA2 dbvisit]$ ls -l
total 16
drwxrwx---  6 oracle oinstall 4096 Jun 21 12:08 dbvagent
drwxrwx---  5 oracle oinstall 4096 Jun 21 12:08 dbvnet
drwxrwx---  5 oracle oinstall 4096 Jun 21 12:08 dbvserver
drwxrwx--- 10 oracle oinstall 4096 Jun 21 12:08 standby


[oracle@ODA2 dbvisit]$ cd dbvnet/
[oracle@ODA2 dbvnet]$ ./dbvnet -d start
[oracle@ODA2 dbvnet]$ cd ../dbvagent/
[oracle@ODA2 dbvagent]$ ./dbvagent -d start
[oracle@ODA2 dbvagent]$ cd ../dbvserver/
[oracle@ODA2 dbvserver]$ ./dbvserver -d start

8. Check if all DBvisit processes are up and running.

[oracle@ODA2 dbvserver]$ ps -ef | grep dbv
oracle   34384     1  0 12:09 ?        00:00:00 ./dbvnet -d start
oracle   34977     1  0 12:10 ?        00:00:00 ./dbvagent -d start
oracle   35680     1  0 12:10 ?        00:00:00 ./dbvserver -d start
oracle   35870 25380  0 12:10 pts/1    00:00:00 grep dbv

Install and Configure DBvisit Standby on Oracle Database Appliance (ODA X6-2S) Part 1

DBvisit Standby is Disaster Recovery Solution for Oracle Database Stardard Edition.
DBvisit Standby is Software for easy creation and management of standby databases for Oracle Database Standard Edition.
DBVISIT STANDBY uses physical database replication to provide a cost-effective, reliable and proven business continuity solution for all Oracle databases, including Standard Edition.

This doc will describe the step by step procedure to install and configure DBvisit Standby on Oracle Database Appliance(ODA)

Install DBvisit Standby on PROD Machine.(ODA)

1.Download DBvisit Standby from http://www.dbvisit.com/

2.Transfer the files to ODA .
Use scp or winscp

3. Unzip and tar the downloaded file.
 unzip dbvisit-standby8.0.12-el6.zip; tar -xf dbvisit-standby8.0.12-el6.tar

4.create directory for DBvisit Base and change ownership to Oracle and grant  appropriate permissions.
mkdir -p /usr/dbvisit/
chown -R oracle:oinstall /usr/dbvisit/
chmod -R 775 /usr/dbvisit/

5. Install Dbvisit as Oracle user. Its will prompt for information for source and remote hosts.
a. specify the Dbvisit installation directory
b. Choose action (Install, uninstall or terminate)
c. Choose which components to install (Core and central console etc.)
d. specify the Local host name
e. specify the Local Dbvnet PORT
f. specify the Remote host name
g. specify the Remote Dbvnet PORT
h. specify the Dbvnet Passphrase
i. specify the host name to be used for the Dbvisit Agent
j. specify the listening PORT number for Dbvagent
k. specify passphrase for Dbvagent


[oracle@ODA1 installer]$ ./install-dbvisit

-----------------------------------------------------------
    Welcome to the Dbvisit software installer.
-----------------------------------------------------------

    It is recommended to make a backup of our current Dbvisit software
    location (Dbvisit Base location) for rollback purposes.

    Installer Directory /u01/dbvisit

>>> Please specify the Dbvisit installation directory (Dbvisit Base).

    The various Dbvisit products and components - such as Dbvisit Standby,
    Dbvisit Dbvnet will be installed in the appropriate subdirectories of
    this path.

    Enter a custom value or press ENTER to accept default [/usr/dbvisit]:
     >
    DBVISIT_BASE = /usr/dbvisit

    -----------------------------------------------------------
    Component      Installer Version   Installed Version
    -----------------------------------------------------------
    standby        8.0.14.19191        not installed
    dbvnet         2.0.14.19191        not installed
    dbvagent       2.0.14.19191        not installed
    dbvserver      2.0.14.19191        not installed

    -----------------------------------------------------------

    What action would you like to perform?
       1 - Install component(s)
       2 - Uninstall component(s)
       3 - Terminate

    Your choice: 1

    Which component do you want to install?
       1 - Core Components (Dbvisit Standby Cli, Dbvnet, Dbvagent)
       2 - Dbvisit Standby Core (Command Line Interface)
       3 - Dbvnet (Dbvisit Network Communication)
       4 - Dbvagent (Dbvisit Agent)
       5 - Dbvserver (Dbvisit Central Console)
       6 - Exit Installer

    Your choice: 1

-----------------------------------------------------------
    Summary of the Dbvisit STANDBY configuration
-----------------------------------------------------------
    DBVISIT_BASE /usr/dbvisit

    Press ENTER to continue

-----------------------------------------------------------
    About to configure DBVISIT DBVNET
-----------------------------------------------------------

>>> Please specify the Local host name to be used by Dbvnet on this server.

    Dbvnet will be listening on the local IP Address on this server which
    resolve to the host name specified here.
    If using a cluster or virtual IP make sure the host name or alias
    specified here resolve to the IP address local to where dbvnet is
    installed.

    Enter a custom value or press ENTER to accept default [ODA1]:
     >

>>> Please specify the Local Dbvnet PORT to be used.

    Dbvnet will be listening on the specified port for incoming connections
    from remote dbvnet connections.  Please make sure that this port is not
    already in use or blocked by any firewall.  You may choose any value
    between 1024 and 65535, however the default of 7890 is recommended.

    Enter a custom value or press ENTER to accept default [7890]:
     >


>>> Please specify the Remote host name to be used by Dbvnet.

    By default Dbvnet will use this remote hostname for any remote
    connections.  Dbvnet must be installed and configured on the specified
    remote host. If using a cluster or virtual IP make sure the host name
    or alias specified here resolve to the IP address local to where dbvnet
    is installed.
    If you are unsure about the remote host name during installation, use
    the default value which will be the current local hostname.

    Enter a custom value or press ENTER to accept default [ODA1]:
     > ODA2


>>> Please specify the Remote Dbvnet PORT to be used.

    Dbvnet will connect to the remote server on this specified port.
    On the remote host Dbvnet will be listening on the specified port for
    incoming connections. Please make sure that this port is not already in
    use or blocked by any firewall.  You may choose any value between 1024
    and 65535, however the default of 7890 is recommended.

    Enter a custom value or press ENTER to accept default [7890]:
     >


>>> Please specify the Dbvnet Passphrase to be used for secure connections.

    The passphrase provided must be the same in both the local and remote
    Dbvnet installations.  It is used to establish a secure (encrypted)
    Dbvnet connections

    Enter a custom value:
     > welcome1

-----------------------------------------------------------
    Summary of the Dbvisit DBVNET configuration
-----------------------------------------------------------
    DBVISIT_BASE /usr/dbvisit
    DBVNET_LOCAL_HOST ODA1
    DBVNET_LOCAL_PORT 7890
    DBVNET_REMOTE_HOST ODA2
    DBVNET_REMOTE_PORT 7890
    DBVNET_PASSPHRASE welcome1

    Press ENTER to continue

-----------------------------------------------------------
    About to configure DBVISIT DBVAGENT
-----------------------------------------------------------


>>> Please specify the host name to be used for the Dbvisit Agent.

    The Dbvisit Agent (Dbvagent) will be listening on this local address.
    If you are using the Dbvserver (GUI) - connections from the GUI will be
    established to the Dbvisit Agent. The Dbvisit Agent address must be
    visible from the Dbvserver (GUI) installation.
    If using a cluster or virtual IP make sure the host name or alias
    specified here resolve to the IP address local to where dbvnet is
    installed.

    Enter a custom value or press ENTER to accept default [ODA1]:
     >


>>> Please specify the listening PORT number for Dbvagent.

    The Dbvisit Agent (Dbvagent) will listening on the specified port for
    incoming requests from the GUI (Dbvserver).  Please make sure that this
    port is not already in use or blocked by any firewall.  You may choose
    any value between 1024 and 65535, however the default of 7891 is
    recommended.

    Enter a custom value or press ENTER to accept default [7891]:
     >


>>> Please specify passphrase for Dbvagent

    Each Dbvisit Agent must have a passpharse specified.  This passphrase
    does not have to match between all the servers.  It will be used to
    establish a secure connection between the GUI (Dbvserver) and the
    Dbvisit Agent.

    Enter a custom value:
     >welcome1

-----------------------------------------------------------
    Summary of the Dbvisit DBVAGENT configuration
-----------------------------------------------------------
    DBVISIT_BASE /usr/dbvisit
    DBVAGENT_LOCAL_HOST ODA1
    DBVAGENT_LOCAL_PORT 7891
    DBVAGENT_PASSPHRASE welcome1

    Press ENTER to continue

-----------------------------------------------------------
    About to install Dbvisit STANDBY
-----------------------------------------------------------
    Component standby installed.

    Press ENTER to continue

-----------------------------------------------------------
    About to install Dbvisit DBVNET
-----------------------------------------------------------
    Component dbvnet installed.

    Press ENTER to continue

-----------------------------------------------------------
    About to install Dbvisit DBVAGENT
-----------------------------------------------------------
    Component dbvagent installed.

    Press ENTER to continue

    -----------------------------------------------------------
    Component      Installer Version   Installed Version
    -----------------------------------------------------------
    standby        8.0.14.19191        8.0.14.19191
    dbvnet         2.0.14.19191        2.0.14.19191
    dbvagent       2.0.14.19191        2.0.14.19191
    dbvserver      2.0.14.19191        not installed

    -----------------------------------------------------------

    What action would you like to perform?
       1 - Install component(s)
       2 - Uninstall component(s)
       3 - Terminate

    Your choice: 3

>>> Installation completed
    Install log /tmp/dbvisit_install.log.201706211130.




6. Goto DBvisit home and start the processes.

[oracle@ODA1 installer]$ cd /usr/dbvisit/
[oracle@ODA1 dbvisit]$ ls -l
total 12
drwxrwx---  6 oracle oinstall 4096 Jun 21 11:31 dbvagent
drwxrwx---  5 oracle oinstall 4096 Jun 21 11:31 dbvnet
drwxrwx--- 10 oracle oinstall 4096 Jun 21 11:31 standby
[oracle@ODA1 dbvisit]$ cd dbvnet/
[oracle@ODA1 dbvnet]$ ./dbvnet -d start
[oracle@ODA1 dbvnet]$ cd ../dbvagent/
[oracle@ODA1 dbvagent]$ ./dbvagent -d start

7. Check if all DBvisit processes are up and running.

[oracle@ODA1 dbvagent]$ ps -ef | grep dbv
oracle    7360 45918  0 11:27 pts/1    00:00:00 ./install-dbvisit
oracle   24484     1  0 11:33 ?        00:00:00 ./dbvnet -d start
oracle   25579     1  0 11:33 ?        00:00:00 ./dbvagent -d start
oracle   26151 15840  0 11:33 pts/3    00:00:00 grep dbv


Pls goto Part 2
Install and Configure DBvisit Standby on Oracle Database Appliance (ODA X6-2S) Part 2

Tuesday 25 July 2017

Resize ACFS File System on ODA (Oracle Database Appliance)

This doc describe the step by step procedure to resize the ACFS File System on ODA (Oracle Database Appliance) HA.


1. Check the current size of the DiskGroups.

[root@abc0 oak]# oakcli show dbstorage

All the DBs with DB TYPE as non-CDB share the same volumes

DB_NAMES           DB_TYPE    Filesystem                                        Size     Used    Available    AutoExtend Size  DiskGroup
-------            -------    ------------                                    ------    -----    ---------   ----------------   --------
orcl, test         non-CDB    /u01/app/oracle/oradata/datastore                   12G    10.16G       1.84G              1G        REDO
                              /u02/app/oracle/oradata/datastore                  338G   177.30G     160.70G             33G        DATA
                              /u01/app/oracle/fast_recovery_area/datastore       451G    73.51G     377.49G             45G        RECO


2. Resize the required Diskgroup

[root@abc0 oak]# oakcli resize dbstorage -redo 20
INFO: 2017-07-25 15:37:58: Please look at the log file '/opt/oracle/oak/log/abc0/tools/12.1.2.11.0/resizedbstorage_57737.log' for more details
INFO: 2017-07-25 15:38:15: Resizing the redo volume mounted at /u01/app/oracle/oradata/datastore by +20 GB
SUCCESS: 2017-07-25 15:38:16: Successfully extended the volume mounted at /u01/app/oracle/oradata/datastore
[root@abc0 oak]#

3. Verify the updated size of the DiskGroup.


[root@abc0 oak]# oakcli show dbstorage

All the DBs with DB TYPE as non-CDB share the same volumes

DB_NAMES           DB_TYPE    Filesystem                                        Size     Used    Available    AutoExtend Size  DiskGroup
-------            -------    ------------                                    ------    -----    ---------   ----------------   --------
orcl, test         non-CDB    /u01/app/oracle/oradata/datastore                   32G    10.20G      21.80G              1G        REDO
                              /u02/app/oracle/oradata/datastore                  338G   177.30G     160.70G             33G        DATA
                              /u01/app/oracle/fast_recovery_area/datastore       451G    73.51G     377.49G             45G        RECO



Reference MOS note:- 2221700.1

ODA (Oracle Database Appliance) Convert Single Instance Database to RAC

This doc describe step by step procedure to Convert Single Instance Database to RAC on ODA (Oracle Database Appliance) HA using Rconfig utility.


1.Verify the current configuration of the database to be going to covert to RAC.

[oracle@abc0 ~]$ srvctl config database -d boston
Database unique name: boston
Database name: boston
Oracle home: /u01/app/oracle/product/12.1.0.2/dbhome_5
Oracle user: oracle
Spfile: /u02/app/oracle/oradata/datastore/.ACFS/snaps/boston/boston/spfileboston.ora
Password file:
Domain:
Start options: open
Stop options: immediate
Database role: PRIMARY
Management policy: AUTOMATIC
Server pools:
Disk Groups:
Mount point paths: /u01/app/oracle/oradata/datastore,/u02/app/oracle/oradata/datastore,/u01/app/oracle/fast_recovery_area/datastore
Services:
Type: SINGLE
OSDBA group: dba
OSOPER group: racoper
Database instance: boston
Configured nodes: abc0
Database is administrator managed
[oracle@abc0 ~]$ srvctl status database -d boston
Instance boston is running on node abc0


2. List the current database and check type of database.

[root@abc0 oak]# oakcli show databases -detail
Name     Type       Storage   HomeName             HomeLocation                                       Version                             HostName                    
-----    ------     --------  --------------       -----------------                                  -----------                         --------------              

boston   SINGLE     ACFS      OraDb12102_home5     /u01/app/oracle/product/12.1.0.2/dbhome_5          12.1.0.2.170418(25171037,25942196)  abc0                        


[root@abc0 oak]# ps -ef | grep pmon
grid      9928     1  0 10:07 ?        00:00:00 apx_pmon_+APX1
grid      9930     1  0 10:07 ?        00:00:00 asm_pmon_+ASM1
oracle   14671     1  0 10:08 ?        00:00:00 ora_pmon_boston
root     27400 16049  0 10:23 pts/0    00:00:00 grep pmon


3. Edit the ConvertToRAC_AdminManaged.xml file

a. Specify the database current and expected home.
b. Specify the Database SID and credentials.
c. Specify the Node list, where RAC instances going to run.
d. Specify Instance prefix(Optional)
e. Specify sotrage type, ASM is default.
f. Leave the locations empty for Database files and Fast Recovery Area.


[oracle@abc0 ~]$ cat ConvertToRAC_AdminManaged.xml
<?xml version="1.0" encoding="UTF-8"?>
<n:RConfig xmlns:n="http://www.oracle.com/rconfig"
           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
           xsi:schemaLocation="http://www.oracle.com/rconfig rconfig.xsd">
    <n:ConvertToRAC>
<!-- Verify does a precheck to ensure all pre-requisites are met, before the conversion is attempted. Allowable values are: YES|NO|ONLY -->
        <n:Convert verify="NO">
<!--Specify current OracleHome of non-rac database for SourceDBHome -->
              <n:SourceDBHome>/u01/app/oracle/product/12.1.0.2/dbhome_5</n:SourceDBHome>
<!--Specify OracleHome where the rac database should be configured. It can be same as SourceDBHome -->
              <n:TargetDBHome>/u01/app/oracle/product/12.1.0.2/dbhome_5</n:TargetDBHome>
<!--Specify SID of non-rac database and credential. User with sysdba role is required to perform conversion -->
              <n:SourceDBInfo SID="boston">
                <n:Credentials>
                  <n:User>sys</n:User>
                  <n:Password>oracle</n:Password>
                  <n:Role>sysdba</n:Role>
                </n:Credentials>
<!--Specify Windows Secure Oracle Home Credentials if the Oracle Home was installed with Secure User option  -->
<!--
                <n:Credentials>
                  <n:User>UserDomain\SecureHomeUserName</n:User>
                  <n:Password>oracle</n:Password>
                  <n:Role>windows_svc</n:Role>
                </n:Credentials>
-->
              </n:SourceDBInfo>
<!--Specify the list of nodes that should have rac instances running for the Admin Managed Cluster Database. LocalNode should be the first node in this nodelist. -->
              <n:NodeList>
                <n:Node name="abc0"/>
                <n:Node name="abc1"/>
              </n:NodeList>
<!--Specify RacOneNode along with servicename to convert database to RACOne Node -->
              <!--n:RacOneNode  servicename="salesrac1service"/-->
<!--Instance Prefix tag is optional starting with 11.2. If left empty, it is derived from db_unique_name.-->
              <n:InstancePrefix>boston</n:InstancePrefix>
<!-- Listener details are no longer needed starting 11.2. Database is registered with default listener and SCAN listener running from Oracle Grid Infrastructure home.

-->
<!--Specify the type of storage to be used by rac database. Allowable values are CFS|ASM. The non-rac database should have same storage type. ASM credentials are no

needed for conversion. -->
              <n:SharedStorage type="ASM">
<!--Specify Database Area Location to be configured for rac database.If this field is left empty, current storage will be used for rac database. For CFS, this field

will have directory path. -->
                <n:TargetDatabaseArea> </n:TargetDatabaseArea>
<!--Specify Fast Recovery Area to be configured for rac database. If this field is left empty, current recovery area of non-rac database will be configured for rac

database. If current database is not using recovery Area, the resulting rac database will not have a recovery area. -->
                <n:TargetFlashRecoveryArea> </n:TargetFlashRecoveryArea>
              </n:SharedStorage>
        </n:Convert>
    </n:ConvertToRAC>
</n:RConfig>


4. Once XML file is ready, Set the environment variable for the Database to be going to convert.
then goto Database home, then bin directory.

[oracle@abc0 ~]$ . oraenv
ORACLE_SID = [oracle] ? boston
The Oracle base has been set to /u01/app/oracle
[oracle@abc0 ~]$ cd $ORACLE_HOME/bin


5. From Database home, bin directory, Execute the rconfig utility and specify the location of the XML file.


[oracle@abc0 bin]$ ./rconfig /home/oracle/ConvertToRAC_AdminManaged.xml
Converting Database "boston" to Cluster Database. Target Oracle Home: /u01/app/oracle/product/12.1.0.2/dbhome_5. Database Role: PRIMARY.
Setting Data Files and Control Files
Adding Trace files
Adding Database Instances
Adding Redo Logs
Enabling threads for all Database Instances
Setting TEMP tablespace
Adding UNDO tablespaces
Setting Fast Recovery Area
Updating Oratab
Creating Password file(s)
Configuring related CRS resources
Starting Cluster Database
<?xml version="1.0" ?>
<RConfig version="1.1" >
<ConvertToRAC>
    <Convert>
      <Response>
        <Result code="0" >
          Operation Succeeded
        </Result>
      </Response>
      <ReturnValue type="object">
<Oracle_Home>
         /u01/app/oracle/product/12.1.0.2/dbhome_5
       </Oracle_Home>
       <Database type="ADMIN_MANAGED"  >
         <InstanceList>
           <Instance SID="boston1" Node="abc0"  >
           </Instance>
           <Instance SID="boston2" Node="abc1"  >
           </Instance>
         </InstanceList>
       </Database>     </ReturnValue>
    </Convert>
  </ConvertToRAC></RConfig>



6. Once conversion completed successfully, List the databases to check if database converted to RAC.

[root@abc0 oak]# oakcli show databases -detail
Name     Type       Storage   HomeName             HomeLocation                                       Version                             HostName                    
-----    ------     --------  --------------       -----------------                                  -----------                         --------------              
boston   RAC        ACFS      OraDb12102_home5     /u01/app/oracle/product/12.1.0.2/dbhome_5          12.1.0.2.170418(25171037,25942196)  abc0,abc1                    


7. Verify the configuration of the database.

[oracle@abc0 ~]$ srvctl config  database -d boston
Database unique name: boston
Database name: boston
Oracle home: /u01/app/oracle/product/12.1.0.2/dbhome_5
Oracle user: oracle
Spfile: /u02/app/oracle/oradata/datastore/.ACFS/snaps/boston/boston/spfileboston.ora
Password file: /u02/app/oracle/oradata/datastore/.ACFS/snaps/boston/orapwboston
Domain:
Start options: open
Stop options: immediate
Database role: PRIMARY
Management policy: AUTOMATIC
Server pools:
Disk Groups:
Mount point paths:
Services:
Type: RAC
Start concurrency:
Stop concurrency:
OSDBA group: dba
OSOPER group: racoper
Database instances: boston1,boston2
Configured nodes: abc0,abc1
Database is administrator managed


8. Check the RAC processes.

ora.boston.db
      1        ONLINE  ONLINE       abc0                     Open,STABLE
      2        ONLINE  ONLINE       abc1                     Open,STABLE

[oracle@abc0 ~]$ ps -ef | grep pmon
grid      9928     1  0 10:07 ?        00:00:00 apx_pmon_+APX1
grid      9930     1  0 10:07 ?        00:00:00 asm_pmon_+ASM1
oracle   33427     1  0 10:34 ?        00:00:00 ora_pmon_boston1
oracle   39661 27639  0 10:52 pts/0    00:00:00 grep pmon

9. Check if instances are running on all nodes.

[oracle@abc0 ~]$ srvctl status database -d boston
Instance boston1 is running on node abc0
Instance boston2 is running on node abc1


Database is successfully converted to RAC.

Apply Bundle Patch on ODA HA

This doc describe the step by step procedure to apply patch on ODA HA.


Component SERVER to be patch :-
Operating System, ILOM,BIOS, Hardware Management Pack, IPMI, OAK, ASR and local disks.
For virtualized environment, it also includes the Dom0 updates.
Oracle Grid Infrastructure (GI) Stack including ASM, ACFS and TFA.

Component STORAGE to be patch:-
Shared storage including HDD, SSD, Controller, and Expander

Component DATABASE to be patch:-
RDBMS stack

The patch bundle must be applied to the SERVER components first, followed by STORAGE and then the DATABASE.


1. Download the latest bundle patch from MOS note 888888.1
ODA Patch 12.1.2.11.0 Patch 26080564

2. Copy the downloaded patch bundles to both the ODA nodes.
 On a virtualized environment, copy the patch bundle to the ODA_Base (Dom1).

use scp or winscp

3. Check the current version of all components of ODA.

[root@abc0 oak]# oakcli show version -detail
Reading the metadata. It takes a while...
System Version  Component Name            Installed Version         Supported Version
--------------  ---------------           ------------------        -----------------
12.1.2.9.0
                Controller                11.05.03.00               Up-to-date
                Expander                  0342                      Up-to-date
                SSD_SHARED                E12B                      Up-to-date
                HDD_LOCAL                 SF04                      Up-to-date
                HDD_SHARED                0B25                      Up-to-date
                ILOM                      3.0.16.22.d r83408        3.0.16.22.f r100119
                BIOS                      12010311                  Up-to-date
                IPMI                      1.8.12.4                  Up-to-date
                HMP                       2.3.5.2.5                 Up-to-date
                OAK                       12.1.2.9.0                Up-to-date
                OL                        6.8                       Up-to-date
                OVM                       3.2.11                    Up-to-date
                GI_HOME                   12.1.0.2.161018(2400      Up-to-date
                                          6101,23854735)
                DB_HOME                   12.1.0.2.161018(2400      Up-to-date
                                          6101,23854735)

4. Unpack both patch bundles on both Nodes.

[root@abc0 oak]# oakcli unpack -package /tmp/p26080564_1212110_Linux-x86-64_1of2.zip
Unpacking will take some time,  Please wait...
Successfully unpacked the files to repository.
[root@abc0 oak]# oakcli unpack -package /tmp/p26080564_1212110_Linux-x86-64_2of2.zip
Unpacking will take some time,  Please wait...
Successfully unpacked the files to repository.

5. Verify that existing system can be patched

[root@abc0 oak]# oakcli update -patch  12.1.2.11.0 --verify
INFO: 2017-07-19 07:52:47: Reading the metadata file now...
                Component Name            Installed Version         Proposed Patch Version
                ---------------           ------------------        -----------------
                Controller                11.05.03.00               Up-to-date
                Expander                  0342                      Up-to-date
                SSD_SHARED                E12B                      Up-to-date
                HDD_LOCAL                 SF04                      Up-to-date
                HDD_SHARED                0B25                      Up-to-date
                ILOM                      3.0.16.22.d r83408        3.0.16.22.f r100119
                BIOS                      12010311                  Up-to-date
                IPMI                      1.8.12.4                  Up-to-date
                HMP                       2.3.5.2.5                 2.3.5.2.8
                OAK                       12.1.2.9.0                12.1.2.11.0
                OL                        6.8                       Up-to-date
                OVM                       3.2.11                    3.4.3
                GI_HOME                   12.1.0.2.161018(2400      12.1.0.2.170418(2517
                                          6101,23854735)            1037,25942196)
                DB_HOME                   12.1.0.2.161018(2400      12.1.0.2.170418(2517
                                          6101,23854735)            1037,25942196)

6. Apply the patch for server components.This will patch the Infra and GI components.
At the end of the patching process it will re-boot the server. In no particular order which node can be patched first.  Do not run the commands on both nodes at the

same time.


[root@abc0 oak]# oakcli update -patch  12.1.2.11.0 --server --local
INFO: Local patch is running on the Node <0>
INFO: ***************************************************
INFO: ** Please do not patch both nodes simultaneously **
INFO: ***************************************************
INFO: DB, ASM, Clusterware may be stopped during the patch if required
INFO: Local Node may get rebooted automatically during the patch if necessary
Do you want to continue: [Y/N]?: Y
INFO: User has confirmed for the reboot
INFO: All the VMs except the ODABASE will be shutdown forcefully if needed
Do you want to continue : [Y/N]? : Y
INFO: Running pre-install scripts
INFO: Running prepatching on local node
INFO: Completed pre-install scripts
INFO: Running patching on local node
INFO: Stopping local VMs, repos and oakd...
INFO: Shutdown of local VM, Repo and OAKD on node <0>.
INFO: Stopping OAKD on the local node.
INFO: Stopped Oakd on local node
INFO: Waiting for processes to sync up...
INFO: Stopping local VMs...
INFO: Stopping local shared repos...
INFO: Patching ODABASE components
INFO: 2017-07-24 05:57:14: Patching ODABASE Server Components (including Grid software)

INFO: 2017-07-24 05:57:14: ------------------Patching HMP-------------------------
INFO: 2017-07-24 05:57:16: HMP is already Up-to-date
INFO: 2017-07-24 05:57:16: /usr/lib64/sun-ssm already exists.

INFO: 2017-07-24 05:57:16: ----------------------Patching OAK---------------------
INFO: 2017-07-24 05:57:17: OAK is already upgraded or running with the latest version

INFO: 2017-07-24 05:57:20: ----------------------Patching JDK---------------------
INFO: 2017-07-24 05:57:20: JDK is already upgraded or running with the latest version

INFO: 2017-07-24 05:57:20: ----------------------Patching IPMI---------------------
INFO: 2017-07-24 05:57:21: IPMI is already upgraded or running with the latest version

INFO: 2017-07-24 05:57:21: ------------------Patching OS-------------------------
INFO: 2017-07-24 05:57:38: OS is already updated
INFO: 2017-07-24 05:57:43: Clusterware is running on local node
INFO: 2017-07-24 05:57:43: Attempting to stop clusterware and its resources locally
SUCCESS: 2017-07-24 05:59:00: Successfully stopped the clusterware on local node

INFO: 2017-07-24 05:59:00: ------------------Patching Grid-------------------------
INFO: 2017-07-24 05:59:02: Checking for available free space on /, /tmp, /u01
INFO: 2017-07-24 05:59:11: Shutting down Clusterware and CRS on local node.
INFO: 2017-07-24 05:59:11: Shutting down CRS on the node...
SUCCESS: 2017-07-24 05:59:14: Successfully stopped CRS processes on the node
INFO: 2017-07-24 05:59:14: Checking for running CRS processes on the node.
INFO: 2017-07-24 05:59:35: Starting up CRS and Clusterware on the node
INFO: 2017-07-24 05:59:35: Starting up CRS on the node...
SUCCESS: 2017-07-24 06:02:15: CRS has started on the node

INFO: 2017-07-24 06:02:20: Patching the GRID Home on the local node...
INFO: 2017-07-24 06:02:20: Updating OPATCH...
Verifying Opatch version for home:</u01/app/12.1.0.2/grid> on local node.
Expecting version:<12.2.0.1.8>
Opatch version on local node is <12.2.0.1.8>
INFO: 2017-07-24 06:02:24: Patching the GRID Home on the local Node...
INFO: 2017-07-24 06:02:24: Performing local patching...
INFO: 2017-07-24 06:03:11: Performing the conflict checks...
SUCCESS: 2017-07-24 06:03:31: Conflict checks passed for all the Homes
INFO: 2017-07-24 06:03:31: Checking if the patch is already applied to the GRID homes
INFO: 2017-07-24 06:04:01: Home is not Up-to-date
SUCCESS: 2017-07-24 06:05:14: Successfully stopped the Database consoles
SUCCESS: 2017-07-24 06:05:19: Successfully stopped the EM agents
INFO: 2017-07-24 06:05:25: Applying patch on /u01/app/12.1.0.2/grid Homes
INFO: 2017-07-24 06:05:25: It may take upto 15 mins. Please wait...
SUCCESS: 2017-07-24 06:22:05: Successfully applied the patch on the Home : /u01/app/12.1.0.2/grid
SUCCESS: 2017-07-24 06:22:24: Successfully started the Database consoles
SUCCESS: 2017-07-24 06:22:24: Successfully started the EM Agents
INFO: 2017-07-24 06:22:25: ASM is running in Flex mode
INFO: 2017-07-24 06:22:25: Patching DOM0 Server Components
INFO: 2017-07-24 06:22:25: Attempting to patch OS on Dom0...
INFO: 2017-07-24 06:22:46: Clusterware is running on local node
INFO: 2017-07-24 06:22:46: Attempting to stop clusterware and its resources locally
SUCCESS: 2017-07-24 06:23:51: Successfully stopped the clusterware on local node

SUCCESS: 2017-07-24 06:46:28: Successfully updated the device OVM to 3.4.3
INFO: 2017-07-24 06:46:28: Attempting to patch the HMP on Dom0...
INFO: 2017-07-24 06:46:53: The device HMP is already running with the version 2.3.5.2.8 on Dom0
INFO: 2017-07-24 06:46:53: Attempting to patch the IPMI on Dom0...
INFO: 2017-07-24 06:47:14: Successfully updated the IPMI on Dom0
INFO: 2017-07-24 06:47:18: Attempting to patch the local storage on Dom0...
INFO: 2017-07-24 06:47:18: Stopping clusterware on local node...
INFO: 2017-07-24 06:47:43: Disk : c0d0 is already running with ST95000N SF04
INFO: 2017-07-24 06:47:43: Disk : c0d1 is already running with ST95000N SF04
INFO: 2017-07-24 06:48:07: Patch not found for the Controller : c0
INFO: 2017-07-24 06:48:27: Attempting to patch the ILOM on Dom0...
SUCCESS: 2017-07-24 07:06:20: Successfully updated the device Ilom to 3.0.16.22.f r100119
SUCCESS: 2017-07-24 07:06:20: Successfully updated the device BIOS to 12010311

INFO:  patching summary on local node
INFO: 2017-07-24 07:06:20:  HMP is already updated
INFO: 2017-07-24 07:06:20:  OAK is already upgraded
INFO: 2017-07-24 07:06:20:  JDK is already upgraded
INFO: 2017-07-24 07:06:20:  IPMI is already upgraded
INFO: 2017-07-24 07:06:20:  OS is already updated
SUCCESS: 2017-07-24 07:06:20:  Successfully applied the patch on the Home /u01/app/12.1.0.2/grid
SUCCESS: 2017-07-24 07:06:20:  Successfully updated the device OVM
INFO: 2017-07-24 07:06:20:  Local storage patching summary on Dom0...
SUCCESS: 2017-07-24 07:06:20:  Successfully upgraded the local storage
SUCCESS: 2017-07-24 07:06:20:  Successfully updated the device Ilom
SUCCESS: 2017-07-24 07:06:20:  Successfully updated the device BIOS

INFO: Running post-install scripts
INFO: Running postpatch on local node
INFO: restart OAKD on local node
INFO: 2017-07-24 07:14:04: Some of the components patched on node <192.168.16.27>
INFO: 2017-07-24 07:14:04: require node reboot. Rebooting the node
INFO: Rebooting Dom0 on local node
INFO: 2017-07-24 07:14:04: Running /tmp/dom0reboot on node 0
[root@abc0 oak]#
Broadcast message from root@abc0
        (unknown) at 7:18 ...

The system is going down for power off NOW!


7. Verify the updated version of the all components.

[root@abc0 oak]# oakcli show version -detail
Reading the metadata. It takes a while...
System Version  Component Name            Installed Version         Supported Version
--------------  ---------------           ------------------        -----------------
12.1.2.11.0
                Controller                11.05.03.00               Up-to-date
                Expander                  0342                      Up-to-date
                SSD_SHARED                E12B                      Up-to-date
                HDD_LOCAL                 SF04                      Up-to-date
                HDD_SHARED                0B25                      Up-to-date
                ILOM                      3.0.16.22.f r100119       Up-to-date
                BIOS                      12010311                  Up-to-date
                IPMI                      1.8.12.4                  Up-to-date
                HMP                       2.3.5.2.8                 Up-to-date
                OAK                       12.1.2.11.0               Up-to-date
                OL                        6.8                       Up-to-date
                OVM                       3.4.3                     Up-to-date
                GI_HOME                   12.1.0.2.170418(2517      Up-to-date
                                          1037,25942196)
                DB_HOME                   12.1.0.2.161018(2400      12.1.0.2.170418(2517
                                          6101,23854735)            1037,25942196)

8. Apply the patch to the storage components.
Storage patching should only be attempted after the server patching is successful.
No ‘-local’ option for storage.  If required, both nodes will be rebooted.
If ‘proposed patch version’ for storage components are all up-to-date from ‘oakcli update –patch 12.1.2.11 --verify’, then we can skip the storage update.

oakcli update -patch  12.1.2.11.0 --storage


9.Apply the database patch – to update databases to the latest PSU for the same release.
If patching database with ‘--local’ parameter, the order or which node to be patched does not matter.  Please do not run the command at the same time on both nodes.

The database patching is rolling upgradable.


[root@abc0 oak]# oakcli update -patch  12.1.2.11.0  --database --local
INFO: Local patch is running on the Node <0>
INFO: ***************************************************
INFO: ** Please do not patch both nodes simultaneously **
INFO: ***************************************************
INFO: DB, ASM, Clusterware may be stopped during the patch if required
INFO: Running pre-install scripts
INFO: Running prepatching on local node
INFO: Completed pre-install scripts
INFO: Running patching on local node
INFO: 2017-07-24 08:23:31: ------------------Patching DB-------------------------
INFO: 2017-07-24 08:23:31: Clusterware running on local node
INFO: 2017-07-24 08:23:31: Getting all the possible Database Homes for patching...
INFO: 2017-07-24 08:23:34: home version: 12.1.0.2.0
INFO: 2017-07-24 08:23:43: Patching 12.1.0.2 Database Homes on the local Node

Found the following 12.1.0.2 homes possible for patching:

HOME_NAME                      HOME_LOCATION
---------                      -------------
OraDb12102_home1               /u01/app/oracle/product/12.1.0.2/dbhome_1

[Please note that few of the above Database Homes may be already up-to-date. They will be automatically ignored]

Would you like to patch all the above homes: Y | N ? : Y
INFO: 2017-07-24 08:25:27: Updating OPATCH...
Verifying Opatch version for home:</u01/app/oracle/product/12.1.0.2/dbhome_1> on local node.
Expecting version:<12.2.0.1.8>
Opatch version on local node is <12.2.0.1.8>
INFO: 2017-07-24 08:25:34: Performing local patching...
INFO: 2017-07-24 08:29:31: Performing the conflict checks...
SUCCESS: 2017-07-24 08:29:52: Conflict checks passed for all the Homes
INFO: 2017-07-24 08:29:52: Checking if the patch is already applied on any of the Homes
INFO: 2017-07-24 08:30:01: Home is not Up-to-date
SUCCESS: 2017-07-24 08:30:03: Successfully stopped the Database consoles
SUCCESS: 2017-07-24 08:30:08: Successfully stopped the EM agents
INFO: 2017-07-24 08:30:14: Applying patch on /u01/app/oracle/product/12.1.0.2/dbhome_1 Homes
INFO: 2017-07-24 08:30:14: It may take upto 15 mins. Please wait...
SUCCESS: 2017-07-24 08:43:31: Successfully applied the patch on the Home : /u01/app/oracle/product/12.1.0.2/dbhome_1
SUCCESS: 2017-07-24 08:43:31: Successfully started the Database consoles
SUCCESS: 2017-07-24 08:43:31: Successfully started the EM Agents

INFO:  patching summary on local node
SUCCESS: 2017-07-24 08:43:32:  Successfully applied the patch on the Home /u01/app/oracle/product/12.1.0.2/dbhome_1

INFO: Executing /tmp/pending_actions on local node


10. Verify the Database updated version of the database.

[root@abc0 oak]# oakcli show version -detail
Reading the metadata. It takes a while...
System Version  Component Name            Installed Version         Supported Version
--------------  ---------------           ------------------        -----------------
12.1.2.11.0
                Controller                11.05.03.00               Up-to-date
                Expander                  0342                      Up-to-date
                SSD_SHARED                E12B                      Up-to-date
                HDD_LOCAL                 SF04                      Up-to-date
                HDD_SHARED                0B25                      Up-to-date
                ILOM                      3.0.16.22.f r100119       Up-to-date
                BIOS                      12010311                  Up-to-date
                IPMI                      1.8.12.4                  Up-to-date
                HMP                       2.3.5.2.8                 Up-to-date
                OAK                       12.1.2.11.0               Up-to-date
                OL                        6.8                       Up-to-date
                OVM                       3.4.3                     Up-to-date
                GI_HOME                   12.1.0.2.170418(2517      Up-to-date
                                          1037,25942196)
                DB_HOME                   12.1.0.2.170418(2517      Up-to-date
                                          1037,25942196)


For more details pls refer to README file attached to the bundle patch.