Description:-
This article we are going to see steps used to apply the latest Oracle 19c Database Release Update 19.8.0.0.200714 (Patch 31281355)
The environment is single instance database.
Note:-
1)Review readme file on Patch 31281355 – Database Release Update 19.8.0.0.200714
2)Download patch p31281355_190000_Linux-x86-64.zip
3)Make sure the opatch version is minimum 12.2.0.1.21
Step:-1 Download the Patch from oracle support
p31281355_190000_Linux-x86-64.zip p6880880_122010_Linux-x86-64.zip
Step:-2 Copied the patch to DB Server
[oracle@oem021 u02]$ cd patch
[oracle@oem021 patch]$ ls -lrt
total 1443617
-rw-r–r– 1 oracle oinstall 118408624 Apr 30 04:07 p6880880_122010_Linux-x86-64.zip
-rw-r–r– 1 oracle oinstall 1358248745 Jul 9 21:41 p31281355_190000_Linux-x86-64.zip
Step:-3 Upgrade Opatch Tool from 12.2.0.1.17 to 12.2.0.1.21
[oracle@oem021 u02]$ echo $ORACLE_HOME
/u02/app/oracle/product/19.0.0/dbhome_1
[oracle@oem021 u02]$ export ORACLE_HOME=/u02/app/oracle/product/19.0.0/dbhome_1
[oracle@oem021 u02]$ export PATH=/u02/app/oracle/product/19.0.0/dbhome_1/OPatch:$PATH
[oracle@oem021 u02]$ opatch version
OPatch Version: 12.2.0.1.17
OPatch succeeded.
[oracle@oem021 dbhome_1]$ unzip p6880880_122010_Linux-x86-64.zip
[oracle@oem021 dbhome_1]$ mv OPatch/ OPatch_BKP
[oracle@oem021 patch]$ cp p6880880_122010_Linux-x86-64.zip /u02/app/oracle/product/19.0.0/dbhome_1/
[oracle@oem021 dbhome_1]$ export ORACLE_HOME=/u02/app/oracle/product/19.0.0/dbhome_1
[oracle@oem021 dbhome_1]$ export PATH=/u02/app/oracle/product/19.0.0/dbhome_1/OPatch:$PATH
[oracle@oem021 dbhome_1]$ opatch version
OPatch Version: 12.2.0.1.21
OPatch succeeded.
Step:-4 Check Patches status before apply using below query
SQL> SET LINESIZE 500
SQL> SET PAGESIZE 1000
SQL> SET SERVEROUT ON
SET LONG 2000000
SQL> SQL>
SQL> COLUMN action_time FORMAT A12
SQL> COLUMN action FORMAT A10
SQL> COLUMN comments FORMAT A30
SQL> COLUMN description FORMAT A60
SQL> COLUMN namespace FORMAT A20
SQL> COLUMN status FORMAT A10
SQL>
SQL> SELECT TO_CHAR(action_time, ‘YYYY-MM-DD’) AS action_time,
action,
status,
description,
patch_id
FROM sys.dba_registry_sqlpatch
ORDER by action_time;
ACTION_TIME ACTION STATUS DESCRIPTION PATCH_ID
———— ———- ———- ———————————————————— ———-
2020-09-02 APPLY WITH ERROR Database Release Update : 19.3.0.0.190416 (29517242) 29517242
S (RU)
2020-09-02 APPLY WITH ERROR Database Release Update : 19.3.0.0.190416 (29517242) 29517242
S (RU)
SQL> col comp_id for a10
col version for a11
col status for a10
col comp_name for a37
select comp_id,comp_name,version,status from dba_registry;
COMP_ID COMP_NAME VERSION STATUS ---------- ------------------------------------- ----------- ---------- CATALOG Oracle Database Catalog Views 19.0.0.0.0 VALID CATPROC Oracle Database Packages and Types 19.0.0.0.0 VALID RAC Oracle Real Application Clusters 19.0.0.0.0 OPTION OFF JAVAVM JServer JAVA Virtual Machine 19.0.0.0.0 VALID XML Oracle XDK 19.0.0.0.0 VALID CATJAVA Oracle Database Java Packages 19.0.0.0.0 VALID XDB Oracle XML Database 19.0.0.0.0 VALID OWM Oracle Workspace Manager 19.0.0.0.0 VALID
8 rows selected.
Identifying Invalid Objects before patching
COLUMN object_name FORMAT A30
SELECT owner,
object_type,
object_name,
status
FROM dba_objects
WHERE status = ‘INVALID’
ORDER BY owner, object_type, object_name;
Step 5:- Shutdown Database and Listener
[oracle@oem021 patch]$ sqlplus / as sysdba
SQL*Plus: Release 19.0.0.0.0 – Production on Fri Sep 4 03:24:11 2020
Version 19.3.0.0.0
Copyright (c) 1982, 2019, Oracle. All rights reserved.
Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production
Version 19.3.0.0.0
SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> exit
Disconnected from Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production
Version 19.3.0.0.0
[oracle@oem021 patch]$ lsnrctl stop
LSNRCTL for Linux: Version 19.0.0.0.0 – Production on 04-SEP-2020 03:24:53
Copyright (c) 1991, 2019, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=oem021)(PORT=1521)))
The command completed successfully
Step:-6 Take Backup of ORACLE_HOME and Database (Rollback plan)
cd $ORACLE_HOME
tar -cvf oracle_home_04SEP_2020.tar $ORACLE_HOME
Connect with rman take full backup
Step:-7 Apply RU patch on ORACLE_HOME 19c
[oracle@oem021 patch]$ unzip p31281355_190000_Linux-x86-64.zip
[oracle@oem021 patch]$ ls -lrt
total 1444146
-rw-r–r– 1 oracle oinstall 118408624 Apr 30 04:07 p6880880_122010_Linux-x86-64.zip
drwxr-xr-x 5 oracle oinstall 7 Jul 6 13:18 31281355
-rw-rw-r– 1 oracle oinstall 409159 Jul 9 21:39 PatchSearch.xml
-rw-r–r– 1 oracle oinstall 1358248745 Jul 9 21:41 p31281355_190000_Linux-x86-64.zip
[oracle@prd-oem021 patch]$ cd 31281355
[oracle@oem021 31281355]$ export ORACLE_HOME=/u02/app/oracle/product/19.0.0/
[oracle@oem021 31281355]$ export PATH=/u02/app/oracle/product/19.0.0/dbhome_
[oracle@oem021 31281355]$ opatch apply
Oracle Interim Patch Installer version 12.2.0.1.21
Copyright (c) 2020, Oracle Corporation. All rights reserved.
Oracle Home : /u02/app/oracle/product/19.0.0/dbhome_1
Central Inventory : /u01/app/oraInventory
from : /u02/app/oracle/product/19.0.0/dbhome_1/oraInst.loc
OPatch version : 12.2.0.1.21
OUI version : 12.2.0.7.0
Log file location : /u02/app/oracle/product/19.0.0/dbhome_1/cfgtoollogs/opatch/opatch2020-09-04_03-26-43AM_1.log
Verifying environment and performing prerequisite checks…
OPatch continues with these patches: 31281355
Do you want to proceed? [y|n]
y
User Responded with: Y
All checks passed.
Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home = ‘/u02/app/oracle/product/19.0.0/dbhome_1’)
Is the local system ready for patching? [y|n]
y
User Responded with: Y
Backing up files…
Applying interim patch ‘31281355’ to OH ‘/u02/app/oracle/product/19.0.0/dbhome_1’
ApplySession: Optional component(s) [ oracle.network.gsm, 19.0.0.0.0 ] , [ oracle.rdbms.ic, 19.0.0.0.0 ] , [ oracle.rdbms.tg4db2, 19.0.0.0.0 ] , [ oracle.tfa, 19.0.0.0.0 ] , [ oracle.oraolap.mgmt, 19.0.0.0.0 ] , [ oracle.xdk.parser.java.jaxb2, 19.0.0.0.0 ] , [ oracle.options.olap.awm, 19.0.0.0.0 ] , [ oracle.net.cman, 19.0.0.0.0 ] , [ oracle.assistants.asm, 19.0.0.0.0 ] , [ oracle.network.cman, 19.0.0.0.0 ] , [ oracle.sqlj, 19.0.0.0.0 ] , [ oracle.assistants.usm, 19.0.0.0.0 ] , [ oracle.options.olap, 19.0.0.0.0 ] , [ oracle.jdk, 1.8.0.191.0 ] not present in the Oracle Home or a higher version is found.
Patching component oracle.rdbms, 19.0.0.0.0…
Patching component oracle.rdbms.util, 19.0.0.0.0…
Patching component oracle.rdbms.rsf, 19.0.0.0.0…
Patching component oracle.assistants.acf, 19.0.0.0.0…
Patching component oracle.assistants.deconfig, 19.0.0.0.0…
Patching component oracle.assistants.server, 19.0.0.0.0…
Patching component oracle.buildtools.rsf, 19.0.0.0.0…
Patching component oracle.ctx, 19.0.0.0.0…
Patching component oracle.dbjava.ic, 19.0.0.0.0…
Patching component oracle.ldap.rsf, 19.0.0.0.0…
Patching component oracle.network.rsf, 19.0.0.0.0…
Patching component oracle.rdbms.dbscripts, 19.0.0.0.0…
Patching component oracle.rdbms.deconfig, 19.0.0.0.0…
Patching component oracle.sdo, 19.0.0.0.0…
Patching component oracle.sdo.locator.jrf, 19.0.0.0.0…
Patching component oracle.sqlplus, 19.0.0.0.0…
Patching component oracle.xdk, 19.0.0.0.0…
Patching component oracle.rdbms.crs, 19.0.0.0.0…
Patching component oracle.install.deinstalltool, 19.0.0.0.0…
Patching component oracle.dbjava.ucp, 19.0.0.0.0…
Patching component oracle.oraolap.dbscripts, 19.0.0.0.0…
Patching component oracle.rdbms.lbac, 19.0.0.0.0…
Patching component oracle.dbdev, 19.0.0.0.0…
Patching component oracle.marvel, 19.0.0.0.0…
Patching component oracle.network.listener, 19.0.0.0.0…
Patching component oracle.precomp.rsf, 19.0.0.0.0…
Patching component oracle.javavm.client, 19.0.0.0.0…
Patching component oracle.precomp.common.core, 19.0.0.0.0…
Patching component oracle.ldap.rsf.ic, 19.0.0.0.0…
Patching component oracle.network.client, 19.0.0.0.0…
Patching component oracle.ctx.atg, 19.0.0.0.0…
Patching component oracle.ctx.rsf, 19.0.0.0.0…
Patching component oracle.rdbms.drdaas, 19.0.0.0.0…
Patching component oracle.duma, 19.0.0.0.0…
Patching component oracle.javavm.server, 19.0.0.0.0…
Patching component oracle.odbc, 19.0.0.0.0…
Patching component oracle.rdbms.oci, 19.0.0.0.0…
Patching component oracle.rdbms.rman, 19.0.0.0.0…
Patching component oracle.rdbms.dv, 19.0.0.0.0…
Patching component oracle.bali.ice, 11.1.1.7.0…
Patching component oracle.ovm, 19.0.0.0.0…
Patching component oracle.dbjava.jdbc, 19.0.0.0.0…
Patching component oracle.oracore.rsf, 19.0.0.0.0…
Patching component oracle.rdbms.scheduler, 19.0.0.0.0…
Patching component oracle.rdbms.install.common, 19.0.0.0.0…
Patching component oracle.ldap.owm, 19.0.0.0.0…
Patching component oracle.ldap.security.osdt, 19.0.0.0.0…
Patching component oracle.ons, 19.0.0.0.0…
Patching component oracle.rdbms.install.plugins, 19.0.0.0.0…
Patching component oracle.sdo.locator, 19.0.0.0.0…
Patching component oracle.nlsrtl.rsf, 19.0.0.0.0…
Patching component oracle.xdk.rsf, 19.0.0.0.0…
Patching component oracle.sqlplus.ic, 19.0.0.0.0…
Patching component oracle.oraolap, 19.0.0.0.0…
Patching component oracle.xdk.parser.java, 19.0.0.0.0…
Patching component oracle.rdbms.rsf.ic, 19.0.0.0.0…
Patching component oracle.precomp.common, 19.0.0.0.0…
Patching component oracle.precomp.lang, 19.0.0.0.0…
Patching component oracle.jdk, 1.8.0.201.0…
Patch 31281355 successfully applied.
Sub-set patch [29517242] has become inactive due to the application of a super-set patch [31281355].
Please refer to Doc ID 2161861.1 for any possible further required actions.
Log file location: /u02/app/oracle/product/19.0.0/dbhome_1/cfgtoollogs/opatch/opatch2020-09-04_03-26-43AM_1.log
OPatch succeeded.
Step:-8 Startup the Database and Listener
[oracle@oem021 31281355]$ lsnrctl start
LSNRCTL for Linux: Version 19.0.0.0.0 – Production on 04-SEP-2020 03:40:27
Copyright (c) 1991, 2020, Oracle. All rights reserved.
Starting /u02/app/oracle/product/19.0.0/dbhome_1/bin/tnslsnr: please wait…
TNSLSNR for Linux: Version 19.0.0.0.0 – Production
System parameter file is /u02/app/oracle/product/19.0.0/dbhome_1/network/admin/listener.ora
Log messages written to /u02/app/oracle/diag/tnslsnr/prd-oem021/listener/alert/log.xml
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oem021.ohdc.com)(PORT=1521)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=prd-oem021)(PORT=1521)))
STATUS of the LISTENER
————————
Alias LISTENER
Version TNSLSNR for Linux: Version 19.0.0.0.0 – Production
Start Date 04-SEP-2020 03:40:27
Uptime 0 days 0 hr. 0 min. 0 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u02/app/oracle/product/19.0.0/dbhome_1/network/admin/listener.ora
Listener Log File /u02/app/oracle/diag/tnslsnr/oem021/listener/alert/log.xml
Listening Endpoints Summary…
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oem021.ohdc.com)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
The listener supports no services
The command completed successfully
[oracle@prd-oem021 31281355]$ sqlplus / as sysdba
SQL*Plus: Release 19.0.0.0.0 – Production on Fri Sep 4 03:40:36 2020
Version 19.8.0.0.0
Copyright (c) 1982, 2020, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 1.1039E+10 bytes
Fixed Size 12447232 bytes
Variable Size 1811939328 bytes
Database Buffers 9193914368 bytes
Redo Buffers 21106688 bytes
Database mounted.
Database opened.
Step:-9 Execute post patch steps and run datapatch command
[oracle@oem021 31281355]$ cd $ORACLE_HOME/OPatch
[oracle@oem021 OPatch]$ ./datapatch -verbose
SQL Patching tool version 19.8.0.0.0 Production on Fri Sep 4 03:41:31 2020
Copyright (c) 2012, 2020, Oracle. All rights reserved.
Log file for this invocation: /u02/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_39706_2020_09_04_03_41_31/sqlpatch_invocation.log
Connecting to database…OK
Gathering database info…done
Bootstrapping registry and package to current versions…done
Determining current state…done
Current state of interim SQL patches:
No interim patches found
Current state of release update SQL patches:
Binary registry:
19.8.0.0.0 Release_Update 200703031501: Installed
SQL registry:
Applied 19.3.0.0.0 Release_Update 190410122720 with errors on 02-SEP-20 12.56.20.851805 AM
Adding patches to installation queue and performing prereq checks…done
Installation queue:
No interim patches need to be rolled back
Patch 29517242 (Database Release Update : 19.3.0.0.190416 (29517242)):
Rollback from 19.3.0.0.0 Release_Update 190410122720 to 19.1.0.0.0 Feature Release
Patch 31281355 (Database Release Update : 19.8.0.0.200714 (31281355)):
Apply from 19.1.0.0.0 Feature Release to 19.8.0.0.0 Release_Update 200703031501
No interim patches need to be applied
Installing patches…
Patch installation complete. Total patches installed: 2
Validating logfiles…done
Patch 29517242 rollback: SUCCESS
logfile: /u02/app/oracle/cfgtoollogs/sqlpatch/29517242/22862832/29517242_rollback_OEMPROD_2020Sep04_03_42_02.log (no errors)
Patch 31281355 apply: SUCCESS
logfile: /u02/app/oracle/cfgtoollogs/sqlpatch/31281355/23688465/31281355_apply_OEMPROD_2020Sep04_03_42_27.log (no errors)
SQL Patching tool complete on Fri Sep 4 03:44:05 2020
Step:-10 After applying RU patch,Check the DBA_REGISTRY_SQLPATCH
[oracle@prd-oem021 OPatch]$ sqlplus / as sysdba
SQL*Plus: Release 19.0.0.0.0 – Production on Fri Sep 4 03:44:59 2020
Version 19.8.0.0.0
Copyright (c) 1982, 2020, Oracle. All rights reserved.
Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production
Version 19.8.0.0.0
SQL> col comp_id for a10
col version for a11
col status for a10
col comp_name for a37
select comp_id,comp_name,version,status from dba_registry;SQL> SQL> SQL> SQL>
COMP_ID COMP_NAME VERSION STATUS ---------- ------------------------------------- ----------- ---------- CATALOG Oracle Database Catalog Views 19.0.0.0.0 VALID CATPROC Oracle Database Packages and Types 19.0.0.0.0 VALID RAC Oracle Real Application Clusters 19.0.0.0.0 OPTION OFF JAVAVM JServer JAVA Virtual Machine 19.0.0.0.0 VALID XML Oracle XDK 19.0.0.0.0 VALID CATJAVA Oracle Database Java Packages 19.0.0.0.0 VALID XDB Oracle XML Database 19.0.0.0.0 VALID OWM Oracle Workspace Manager 19.0.0.0.0 VALID
8 rows selected.
SQL> SET LINESIZE 500
SET PAGESIZE 1000
SQL> SQL> SET SERVEROUT ON
SET LONG 2000000
COLUMN action_time FORMAT A12
SQL> SQL> SQL> SQL> COLUMN action FORMAT A10
SQL> COLUMN comments FORMAT A30
SQL> COLUMN description FORMAT A60
SQL> COLUMN namespace FORMAT A20
SQL> COLUMN status FORMAT A10
SQL>
SQL> SELECT TO_CHAR(action_time, ‘YYYY-MM-DD’) AS action_time,
2 action,
3 status,
4 description,
5 patch_id
6 FROM sys.dba_registry_sqlpatch
7 ORDER by action_time;
ACTION_TIME ACTION STATUS DESCRIPTION PATCH_ID
———— ———- ———- ———————————————————— ———-
2020-09-02 APPLY WITH ERROR Database Release Update : 19.3.0.0.190416 (29517242) 29517242
S (RU)
2020-09-02 APPLY WITH ERROR Database Release Update : 19.3.0.0.190416 (29517242) 29517242
S (RU)
2020-09-04 ROLLBACK SUCCESS Database Release Update : 19.3.0.0.190416 (29517242) 29517242
2020-09-04 APPLY SUCCESS Database Release Update : 19.8.0.0.200714 (31281355) 31281355
Step:-11 Check opatch lsinventory and list of patches applied in ORACLE_HOME
[oracle@oem021 ~]$ export ORACLE_HOME=/u02/app/oracle/product/19.0.0/dbhome_1
[oracle@oem021 ~]$ export PATH=/u02/app/oracle/product/19.0.0/dbhome_1/OPatch:$PATH
[oracle@oem021 ~]$ opatch lspatches
31281355;Database Release Update : 19.8.0.0.200714 (31281355)
29585399;OCW RELEASE UPDATE 19.3.0.0.0 (29585399)
OPatch succeeded.
Step:-12 Any databases that have invalid objects after the execution of datapatch should have utlrp.sql run to revalidate those objects.
SQL> COLUMN object_name FORMAT A30
SELECT owner,
object_type,
object_name,
status
FROM dba_objects
WHERE status = ‘INVALID’
ORDER BY owner, object_type, object_name;
OWNER OBJECT_TYPE OBJECT_NAME STATUS --------------- ----------------------- ------------------------------ ---------- SYSMAN PACKAGE BODY ECM_CT INVALID SYSMAN PACKAGE BODY EMD_LOADER INVALID SYSMAN PACKAGE BODY EM_ECM_MD_UPG_PKG INVALID
SQL> @?/rdbms/admin/utlrp.sql
Session altered.
TIMESTAMP
——————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————–
COMP_TIMESTAMP UTLRP_BGN 2020-09-04 03:48:49
DOC> The following PL/SQL block invokes UTL_RECOMP to recompile invalid
DOC> objects in the database. Recompilation time is proportional to the
DOC> number of invalid objects in the database, so this command may take
DOC> a long time to execute on a database with a large number of invalid
DOC> objects.
DOC> Use the following queries to track recompilation progress:
DOC>
DOC> 1. Query returning the number of invalid objects remaining. This
DOC> number should decrease with time.
DOC> SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);
DOC> 2. Query returning the number of objects compiled so far. This number
DOC> should increase with time.
DOC> SELECT COUNT(*) FROM UTL_RECOMP_COMPILED;
DOC> This script automatically chooses serial or parallel recompilation
DOC> based on the number of CPUs available (parameter cpu_count) multiplied
DOC> by the number of threads per CPU (parameter parallel_threads_per_cpu).
DOC> On RAC, this number is added across all RAC nodes.
DOC> UTL_RECOMP uses DBMS_SCHEDULER to create jobs for parallel
DOC> recompilation. Jobs are created without instance affinity so that they
DOC> can migrate across RAC nodes. Use the following queries to verify
DOC> whether UTL_RECOMP jobs are being created and run correctly:
DOC> 1. Query showing jobs created by UTL_RECOMP
DOC> SELECT job_name FROM dba_scheduler_jobs
DOC> WHERE job_name like ‘UTL_RECOMP_SLAVE_%’;
DOC> 2. Query showing UTL_RECOMP jobs that are running
DOC> SELECT job_name FROM dba_scheduler_running_jobs
DOC> WHERE job_name like ‘UTL_RECOMP_SLAVE_%’;
PL/SQL procedure successfully completed.
TIMESTAMP
——————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————–
COMP_TIMESTAMP UTLRP_END 2020-09-04 03:48:51
DOC> The following query reports the number of invalid objects.
DOC> If the number is higher than expected, please examine the error
DOC> messages reported with each object (using SHOW ERRORS) to see if they
DOC> point to system misconfiguration or resource constraints that must be
DOC> fixed before attempting to recompile these objects.
OBJECTS WITH ERRORS
——————-
0
DOC> The following query reports the number of exceptions caught during
DOC> recompilation. If this number is non-zero, please query the error
DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors
DOC> are due to misconfiguration or resource constraints that must be
DOC> fixed before objects can compile successfully.
DOC> Note: Typical compilation errors (due to coding errors) are not
DOC> logged into this table: they go into DBA_ERRORS instead.
ERRORS DURING RECOMPILATION
—————————
0
Function created.
PL/SQL procedure successfully completed.
Function dropped.
PL/SQL procedure successfully completed.
SQL> COLUMN object_name FORMAT A30
SELECT owner,
object_type,
object_name,
status
FROM dba_objects
WHERE status = ‘INVALID’
ORDER BY owner, object_type, object_name;
no rows selected
Connect with me:-
Telegram App:https://t.me/oracledbwr
LinkedIn:https://www.linkedin.com/in/hariprasathdba
Facebook:https://www.facebook.com/HariPrasathdba
FB Group:https://www.facebook.com/groups/894402327369506/
FB Page : https://www.facebook.com/dbahariprasath/?
Twitter : https://twitter.com/oracledbwr