In this Blog, we will learn how to use the Oracle Data Pump Export and Import utility in Oracle 19c database
A table-mode import is specified using the TABLES parameter. In table mode, only the specified set of tables, partitions, and their dependent objects are loaded. The source can be a full, schema, table space, or table-mode export dump file set or another database.
Create a table with an encrypted column and insert rows:
SQL> select * from table01;
ID NAME
---------- ------------------------------
1 aaa
2 bbb
3 ccc
4 ddd
5 eee
Before start the Export Process, we need to create a Directory which is used to store the dump file.Data Pump is a server-based technology, so it typically deals with directory objects pointing to physical directories on the database server.
Dumpfile: The name of the exported dump file.
Logfile: The name of the directory object that is used to store the log file of the export operation, i.e. the name of the log file
Export the dump file of the table:
Directory Name:MY_Dir
Table Name: Table01
[oracle@oracle19c ~]$ expdp directory=My_Dir dumpfile=table01.dmp logfile=table01.log tables='table01';
Export: Release 19.0.0.0.0 - Production on Mon Jan 25 08:39:53 2021
Version 19.3.0.0.0
Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved.
Username: data
Password:
Connected to: Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Starting "DATA"."SYS_EXPORT_TABLE_01": data/******** directory=My_Dir dumpfile=table01.dmp logfile=table01.log tables=table01
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
Processing object type TABLE_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
Processing object type TABLE_EXPORT/TABLE/STATISTICS/MARKER
Processing object type TABLE_EXPORT/TABLE/TABLE
. . exported "DATA"."TABLE01" 5.515 KB 5 rows
Master table "DATA"."SYS_EXPORT_TABLE_01" successfully loaded/unloaded
******************************************************************************
Dump file set for DATA.SYS_EXPORT_TABLE_01 is:
/u01/app/oracle/oradata/table01.dmp
Job "DATA"."SYS_EXPORT_TABLE_01" successfully completed at Mon Jan 25 08:40:05 2021 elapsed 0 00:00:08
[oracle@oracle19c ~]$ !sq
sqlplus / as sysdba;
SQL*Plus: Release 19.0.0.0.0 - Production on Mon Jan 25 08:40:09 2021
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> conn data/pump
Connected.
Drop the table:
SQL> drop table table01;
Table dropped.
SQL> Disconnected from Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.3.0.0.0
[oracle@oracle19c ~]$ sqlplus / as sysdba
SQL*Plus: Release 19.0.0.0.0 - Production on Mon Jan 25 08:41:28 2021
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> conn data/pump
Connected.
SQL> Disconnected from Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.3.0.0.0
The Data Pump Import utility is started using the impdp command
The following example is a command to import Tables using Dump file.
Dumpfile:table01.dmp
[oracle@oracle19c ~]$ impdp directory=My_Dir dumpfile=table01.dmp logfile=table01.log;
Import: Release 19.0.0.0.0 - Production on Mon Jan 25 08:42:02 2021
Version 19.3.0.0.0
Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved.
Username: data
Password:
Connected to: Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Master table "DATA"."SYS_IMPORT_FULL_01" successfully loaded/unloaded
Starting "DATA"."SYS_IMPORT_FULL_01": data/******** directory=My_Dir dumpfile=table01.dmp logfile=table01.log
Processing object type TABLE_EXPORT/TABLE/TABLE
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
. . imported "DATA"."TABLE01" 5.515 KB 5 rows
Processing object type TABLE_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
Processing object type TABLE_EXPORT/TABLE/STATISTICS/MARKER
Job "DATA"."SYS_IMPORT_FULL_01" successfully completed at Mon Jan 25 08:42:21 2021 elapsed 0 00:00:14
[oracle@oracle19c ~]$ !sq
sqlplus / as sysdba
SQL*Plus: Release 19.0.0.0.0 - Production on Mon Jan 25 08:42:27 2021
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> conn data/pump
Connected.
Finally, verify the contents of the Imported table:
SQL> select * from table01;
ID NAME
---------- ------------------------------
1 aaa
2 bbb
3 ccc
4 ddd
5 eee
Thank you for giving your valuable time to read the above information.
If you want to be updated with all our articles send us the Invitation or Follow us:
Ramkumar’s LinkedIn: https://www.linkedin.com/in/ramkumardba/
LinkedIn Group: https://www.linkedin.com/in/ramkumar-m-0061a0204/
Facebook Page: https://www.facebook.com/Oracleagent-344577549964301
Ramkumar’s Twitter : https://twitter.com/ramkuma02877110
Ramkumar’s Telegram: https://t.me/oracleageant
Ramkumar’s Facebook: https://www.facebook.com/ramkumarram8
The multitenant option introduced in Oracle Database 12c allows a single container database (CDB) to host multiple separate pluggable databases (PDB). DBMS_PDB package permits to generate an XML metadata file from a non-CDB 12c database, Its like a unplug a Pluggable database. This is the article which will guide step-by-step Converting Non CDB to CDB in Oracle Database 12c Release.
Step 1: Check the database its properly up and running. shutdown the non-CDB and start it in read-only mode.
Non Container Database Name : NONCDB
Container database Name : ORA_CDB
Non Container Database (Noncdb)
[oracle@localhost ~]$ . ora12c.env
[oracle@localhost ~]$ sqlplus / as sysdba
SQL*Plus: Release 12.2.0.1.0 Production on Thu Jan 21 14:45:36 2021
Copyright (c) 1982, 2016, Oracle. All rights reserved.
Connected to:
Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 – 64bit Production
SQL> select name,open_mode from v$database;
NAME OPEN_MODE
NONCDB READ WRITE
SQL> SELECT name, open_mode FROM v$pdbs;
no rows selected
Container database Name (Ora_cdb)
[oracle@localhost ~]$ . oracdb.env
[oracle@localhost ~]$ sqlplus / as sysdba
SQL*Plus: Release 12.2.0.1.0 Production on Thu Jan 21 14:56:55 2021
Copyright (c) 1982, 2016, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 1258291200 bytes
Fixed Size 8792296 bytes
Variable Size 872417048 bytes
Database Buffers 369098752 bytes
Redo Buffers 7983104 bytes
Database mounted.
Database opened.
SQL> select name,open_mode from v$database;
NAME OPEN_MODE
ORA_CDB READ WRITE
SQL> col name for a20
SQL> select name, open_mode FROM v$pdbs;
NAME OPEN_MODE
PDB$SEED READ ONLY
CDB READ WRITE
[oracle@localhost ~]$ ps -ef | grep pmon
Step 2: Shutdown the non-CDB database and start it in read-only mode.
ORACLE instance started.
Total System Global Area 1258291200 bytes
Fixed Size 8620224 bytes
Variable Size 872417088 bytes
Database Buffers 369098752 bytes
Redo Buffers 8155136 bytes
Database mounted.
SQL> alter database open read only;
Database altered.
Step 3: Create the XML file needed for cdb conversion. the non-cdb database using the DBMS_PDB_DESCRIBE procedure creates an XML file in the same way that the unplug operation does for a PDB.
SQL> BEGIN
DBMS_PDB.DESCRIBE(
pdb_descr_file => ‘/tmp/noncdb.xml’);
END;
/
SQL*Plus: Release 12.2.0.1.0 Production on Tue Jan 19 20:36:39 2021
Copyright (c) 1982, 2016, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 1258291200 bytes
Fixed Size 8792296 bytes
Variable Size 872417048 bytes
Database Buffers 369098752 bytes
Redo Buffers 7983104 bytes
Database mounted.
Database opened.
SQL> select name,open_mode,cdb from v$database;
NAME OPEN_MODE CDB
ORA_CDB READ WRITE YES
Step 6: Check the compatibility of PDB in ( ORA_CDB).
SQL> SET SERVEROUTPUT ON;
DECLARE
compatible CONSTANT VARCHAR2(3) := CASE DBMS_PDB.CHECK_PLUG_COMPATIBILITY(pdb_descr_file => ‘/tmp/noncdb.xml’)
WHEN TRUE THEN ‘YES’
ELSE ‘NO’
END;
BEGIN
DBMS_OUTPUT.PUT_LINE(compatible);
END;
/
Step 7: Check the violationsof PDB in(ORA_CDB).
SQL> select name,cause,type,message,status from PDB_PLUG_IN_VIOLATIONS where name=’NONCDB’;
Step 8: Create pluggable database in container db (ORA_CDB).
SQL> create pluggable database pdb1 using ‘/tmp/noncdb.xml’ NOCOPY;
create pluggable database pdb1 using ‘/tmp/noncdb.xml’ NOCOPY
*ERROR at line 1:
ORA-27038: created file already exists
ORA-01119: error in creating database file
Note: As tempfile is already there, so mention tempfile reuse tag, to avoid this error.
SQL> create pluggable database pdb1 using ‘/tmp/noncdb.xml’ NOCOPY tempfile reuse;
Step 9: Switch to the PDB container and run the “$ORACLE_HOME/rdbms/admin/noncdb_to_pdb.sql” script to clean up the new PDB, removing any items that should not be present in a PDB.
SQL> ALTER SESSION SET CONTAINER=pdb1;
SQL> @$ORACLE_HOME/rdbms/admin/noncdb_to_pdb.sql
Step 10: Startup the PDB and check the open mode PDB.
SQL> alter Pluggable database pdb1 open;
SQL> SELECT name, open_mode FROM v$pdbs;
The non-cdb database has been converted to CDB now successfully.
Thank you for giving your valuable time to read the above information.
If you want to be updated with all our articles send us the Invitation or Follow us:
Ramkumar’s LinkedIn: https://www.linkedin.com/in/ramkumardba/
LinkedIn Group: https://www.linkedin.com/in/ramkumar-m-0061a0204/
Facebook Page: https://www.facebook.com/Oracleagent-344577549964301
Ramkumar’s Twitter : https://twitter.com/ramkuma02877110
Ramkumar’s Telegram: https://t.me/oracleageant
Ramkumar’s Facebook: https://www.facebook.com/ramkumarram8
The view v$sql contains almost of queries which are executed in your Oracle Database. I attached few sql queries which will be useful to check history of SQL.
1. Get latest query
select sql_txt from v$sql where first_load_time=(select max(1st_load_time) from v$sql);
2. Sort executed queries by load time
select sql_text, first_load_time from v$sql order by first_load_time desc;
3. Get executed queries in a schema which have special text and sort by load time
select * from v$sql where parsing_schema_name like 'YOUR_SCHEMA_DETAILS' and
sql_text like '%YOUR_SQLTEXT%' order by first_load_time desc;
4. Get 50 last executed queries
select sql_fulltext from (select * from v$sql where parsing_schema_name
like 'ORAAGENT' order by first_load_time desc) where rownum < 51;
5. Get 50 executed UPDATE or DELETE queries in a specific time period and sort by load time
select sql_text,sql_fulltext, first_load_time, parsing_schema_name from( select * from v$sql where parsing_schema_name like 'YOUR_SCHEMA' and (sql_text like '%UPDATE %' or sql_text like '%INSERT %')
and to_timestamp(first_load_time, 'YYYY-MM-DD/HH24:MI:SS') >
to_timestamp('2021-01-24/09:06:00', 'YYYY-MM-DD/HH24:MI:SS') order by first_load_time desc)where rownum < 51
You can create your own queries to find out what queries you need to check. Remember this view v$sql doesn’t store prepared statements.
Thank you for giving your valuable time to read the above information.
If you want to be updated with all our articles send us the Invitation or Follow us:
Ramkumar’s LinkedIn: https://www.linkedin.com/in/ramkumardba/
LinkedIn Group: https://www.linkedin.com/in/ramkumar-m-0061a0204/
Facebook Page: https://www.facebook.com/Oracleagent-344577549964301
Ramkumar’s Twitter : https://twitter.com/ramkuma02877110
Ramkumar’s Telegram: https://t.me/oracleageant
Ramkumar’s Facebook: https://www.facebook.com/ramkumarram8
The view v$sql contains almost of queries which are executed in your Oracle Database. I attached few sql queries which will be useful to check history of SQL.
1. Get latest query
select sql_txt from v$sql where first_load_time=(select max(1st_load_time) from v$sql);
2. Sort executed queries by load time
select sql_text, first_load_time from v$sql order by first_load_time desc;
3. Get executed queries in a schema which have special text and sort by load time
select * from v$sql where parsing_schema_name like 'YOUR_SCHEMA_DETAILS' and
sql_text like '%YOUR_SQLTEXT%' order by first_load_time desc;
4. Get 50 last executed queries
select sql_fulltext from (select * from v$sql where parsing_schema_name
like 'ORAAGENT' order by first_load_time desc) where rownum < 51;
5. Get 50 executed UPDATE or DELETE queries in a specific time period and sort by load time
select sql_text,sql_fulltext, first_load_time, parsing_schema_name from( select * from v$sql where parsing_schema_name like 'YOUR_SCHEMA' and (sql_text like '%UPDATE %' or sql_text like '%INSERT %')
and to_timestamp(first_load_time, 'YYYY-MM-DD/HH24:MI:SS') >
to_timestamp('2021-01-24/09:06:00', 'YYYY-MM-DD/HH24:MI:SS') order by first_load_time desc)where rownum < 51
You can create your own queries to find out what queries you need to check. Remember this view v$sql doesn’t store prepared statements.
Thank you for giving your valuable time to read the above information.
If you want to be updated with all our articles send us the Invitation or Follow us:
Ramkumar’s LinkedIn: https://www.linkedin.com/in/ramkumardba/
LinkedIn Group: https://www.linkedin.com/in/ramkumar-m-0061a0204/
Facebook Page: https://www.facebook.com/Oracleagent-344577549964301
Ramkumar’s Twitter : https://twitter.com/ramkuma02877110
Ramkumar’s Telegram: https://t.me/oracleageant
Ramkumar’s Facebook: https://www.facebook.com/ramkumarram8
SQL*Plus: Release 12.2.0.1.0 Production on Wed Jan 20 14:53:07 2021
Copyright (c) 1982, 2016, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 2483027968 bytes
Fixed Size 8623736 bytes
Variable Size 671091080 bytes
Database Buffers 1795162112 bytes
Redo Buffers 8151040 bytes
Database mounted.
Database opened.
SQL> Disconnected from Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 – 64bit Production
EXECUTE DATAPATCH FOR UPDATE THE PATCH DETAILS IN DATABASE SIDE.
[oracle@trichyOPatch]$ cd $ORACLE_HOME/OPatch
[oracle@trichyOPatch]$ ./datapatch -verbose
SQL Patching tool version 12.2.0.1.0 Production on Wed Jan 20 14:54:12 2021
Copyright (c) 2012, 2021, Oracle. All rights reserved.
Log file for this invocation: /u01/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_16800_2021_01_20_14_54_12/sqlpatch_invocation.log
Connecting to database…OK
Bootstrapping registry and package to current versions…done
Determining current state…done
Current state of SQL patches:
Bundle series DBRU:
ID 210119 in the binary registry and ID 200414 in the SQL registry
Adding patches to installation queue and performing prereq checks…
Installation queue:
Nothing to roll back
The following patches will be applied:
32228578 (DATABASE JAN 2021 RELEASE UPDATE 12.2.0.1.210119)
Installing patches…
Patch installation complete. Total patches installed: 1
Validating logfiles…
Patch 32228578 apply: SUCCESS
logfile: /u01/app/oracle/cfgtoollogs/sqlpatch/32228578/24008225/32228578_apply_BIJU1_2021Jan20_14_54_32.log (no errors)
SQL Patching tool complete on Wed Jan 20 14:55:10 2021
After installing the SQL portion of the patch, some packages could become INVALID. This will get recompiled upon access or you can run utlrp.sqlto get them back into a VALID state.
[oracle@trichyOPatch]$ cd $ORACLE_HOME/rdbms/admin
[oracle@trichyadmin]$ !sq
sqlplus / as sysdba
SQL*Plus: Release 12.2.0.1.0 Production on Wed Jan 20 15:00:48 2021
Copyright (c) 1982, 2016, Oracle. All rights reserved.
Connected to:
Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 – 64bit Production
SQL> @utlrp.sql
TIMESTAMP
COMP_TIMESTAMP UTLRP_BGN 2021-01-20 15:00:56
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> 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);
SQL> SELECT owner, object_name, object_type FROM all_objects WHERE status =’INVALID’;
no rows selected
CHECK PATCH INFORMATION IN DATABASE LEVEL
SQL> select DESCRIPTION,ACTION,ACTION_TIME,VERSION from dba_registry_sqlpatch;
DESCRIPTION ACTION ACTION_TIME VERSION ————————- ——————-———— ———————–————— ——————- DATABASE JAN 2021 APPLY20-JAN-21 02.55.10.831438 PM 12.2.0.1 RELEASEUPDATE
12.2.0.1.210119
Thank you for giving your valuable time to read the above information.
If you want to be updated with all our articles send us the Invitation or Follow us:
Ramkumar’s LinkedIn: https://www.linkedin.com/in/ramkumardba/
LinkedIn Group: https://www.linkedin.com/in/ramkumar-m-0061a0204/
Facebook Page: https://www.facebook.com/Oracleagent-344577549964301
Ramkumar’s Twitter : https://twitter.com/ramkuma02877110
Ramkumar’s Telegram: https://t.me/oracleageant
Ramkumar’s Facebook: https://www.facebook.com/ramkumarram8
In Putty session while we execute ./dbca command we will get this screen.
STEP 1:
select create database option then click next button
STEP 2:
We need to supply Global database name and password
STEP 3:
click finish button to complete database creation
Once progress completed we will get below screen
STEP 5:
Now the database has been created. We can check by logging in.
Thank you for giving your valuable time to read the above information.
If you want to be updated with all our articles send us the Invitation or Follow us:
Ramkumar’s LinkedIn: https://www.linkedin.com/in/ramkumardba/
LinkedIn Group: https://www.linkedin.com/in/ramkumar-m-0061a0204/
Facebook Page: https://www.facebook.com/Oracleagent-344577549964301
Ramkumar’s Twitter : https://twitter.com/ramkuma02877110
Ramkumar’s Telegram: https://t.me/oracleageant
Ramkumar’s Facebook: https://www.facebook.com/ramkumarram8
In Putty session while we execute ./dbca command we will get this screen.
STEP 1:
select create database option then click next button
STEP 2:
We need to supply Global database name and password
STEP 3:
click finish button to complete database creation
Once progress completed we will get below screen
STEP 5:
Now the database has been created. We can check by logging in.
Thank you for giving your valuable time to read the above information.
If you want to be updated with all our articles send us the Invitation or Follow us:
Ramkumar’s LinkedIn: https://www.linkedin.com/in/ramkumardba/
LinkedIn Group: https://www.linkedin.com/in/ramkumar-m-0061a0204/
Facebook Page: https://www.facebook.com/Oracleagent-344577549964301
Ramkumar’s Twitter : https://twitter.com/ramkuma02877110
Ramkumar’s Telegram: https://t.me/oracleageant
Ramkumar’s Facebook: https://www.facebook.com/ramkumarram8
In Putty session while we execute ./dbca command we will get this screen. In that screen we need to select manage Pluggable databases option to create new PDB database.
Select Create a Pluggable database option.
Click finish button to complete database creation.
Click on new Pluggable database
Enter Pluggable database name and passwords
We need to chose storage locations. click on next button
Check on the summary of inputs in Pluggable databases
Once all details confirmed click on finish button to progress on installation.
Once progress completed PDB100 plugged in.
We can check pluggable databases in putty session whether its installed properly.
Now we can see that pluggable databases installed successfully.
Thank you for giving your valuable time to read the above information.
If you want to be updated with all our articles send us the Invitation or Follow us:
Ramkumar’s LinkedIn: https://www.linkedin.com/in/ramkumardba/
LinkedIn Group: https://www.linkedin.com/in/ramkumar-m-0061a0204/
Facebook Page: https://www.facebook.com/Oracleagent-344577549964301
Ramkumar’s Twitter : https://twitter.com/ramkuma02877110
Ramkumar’s Telegram: https://t.me/oracleageant
Ramkumar’s Facebook: https://www.facebook.com/ramkumarram8
In Putty session while we execute ./dbca command we will get this screen. In that screen we need to select manage Pluggable databases option to create new PDB database.
Select Create a Pluggable database option.
Click finish button to complete database creation.
Click on new Pluggable database
Enter Pluggable database name and passwords
We need to chose storage locations. click on next button
Check on the summary of inputs in Pluggable databases
Once all details confirmed click on finish button to progress on installation.
Once progress completed PDB100 plugged in.
We can check pluggable databases in putty session whether its installed properly.
Now we can see that pluggable databases installed successfully.
Thank you for giving your valuable time to read the above information.
If you want to be updated with all our articles send us the Invitation or Follow us:
Ramkumar’s LinkedIn: https://www.linkedin.com/in/ramkumardba/
LinkedIn Group: https://www.linkedin.com/in/ramkumar-m-0061a0204/
Facebook Page: https://www.facebook.com/Oracleagent-344577549964301
Ramkumar’s Twitter : https://twitter.com/ramkuma02877110
Ramkumar’s Telegram: https://t.me/oracleageant
Ramkumar’s Facebook: https://www.facebook.com/ramkumarram8
[oracle@oracleagent 30886680]$ opatch lsinventory Oracle Interim Patch Installer version 12.2.0.1.19 Copyright (c) 2021, Oracle Corporation. All rights reserved.
Oracle Home : /u01/app/oracle/product/12.2.0.1/db_1 Central Inventory : /u01/app/oraInventory from : /u01/app/oracle/product/12.2.0.1/db_1/oraInst.loc OPatch version : 12.2.0.1.19 OUI version : 12.2.0.1.4 Log file location : /u01/app/oracle/product/12.2.0.1/db_1/cfgtoollogs/opatch/opatch2021-01-18_10-27-13AM_1.log
Here we are going to apply patch with opatch apply.
User need to give Y to proceed Patch.
[oracle@oracleagent 30886680]$ opatch apply Oracle Interim Patch Installer version 12.2.0.1.19 Copyright (c) 2021, Oracle Corporation. All rights reserved.
Oracle Home : /u01/app/oracle/product/12.2.0.1/db_1 Central Inventory : /u01/app/oraInventory from : /u01/app/oracle/product/12.2.0.1/db_1/oraInst.loc OPatch version : 12.2.0.1.19 OUI version : 12.2.0.1.4 Log file location : /u01/app/oracle/product/12.2.0.1/db_1/cfgtoollogs/opatch/opatch2021-01-18_10-03-10AM_1.log
Verifying environment and performing prerequisite checks… OPatch continues with these patches: 30886680
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 = '/u01/app/oracle/product/12.2.0.1/db_1')
Is the local system ready for patching? [y|n] y User Responded with: Y Backing up files… Applying interim patch '30886680' to OH '/u01/app/oracle/product/12.2.0.1/db_1' ApplySession: Optional component(s) [ oracle.swd.oui, 12.2.0.1.0 ] , [ oracle.oid.client, 12.2.0.1.0 ] , [ oracle.has.crs, 12.2.0.1.0 ] , [ oracle.rdbms.drdaas, 12.2.0.1.0 ] , [ oracle.ons.daemon, 12.2.0.1.0 ] , [ oracle.network.cman, 12.2.0.1.0 ] not present in the Oracle Home or a higher version is found.
Bringing up the instance and execute the datapatch verbose.
SQL> startup ORACLE instance started. Total System Global Area 1883107968 bytes Fixed Size 8623736 bytes Variable Size 671011080 bytes Database Buffers 1795162112 bytes Redo Buffers 8151040 bytes Database mounted. Database opened. SQL> Disconnected from Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production
[oracle@oracleagent 30886680]$ cd $ORACLE_HOME/OPatch [oracle@oracleagent OPatch]$ ./datapatch -verbose SQL Patching tool version 12.2.0.1.0 Production on Mon Jan 18 10:33:28 2021 Copyright (c) 2012, 2021, Oracle. All rights reserved.
Log file for this invocation: /u01/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_30825_2021_01_18_10_33_28/sqlpatch_invocation.log Connecting to database…OK Bootstrapping registry and package to current versions…done Determining current state…done Current state of SQL patches: Bundle series DBRU: ID 200414 in the binary registry and not installed in the SQL registry
Adding patches to installation queue and performing prereq checks… Installation queue: Nothing to roll back The following patches will be applied: 30886680 (DATABASE APR 2021 RELEASE UPDATE 12.2.0.1.200414)
Installing patches… Patch installation complete. Total patches installed: 1
Validating logfiles… Patch 30886680 apply: SUCCESS logfile: /u01/app/oracle/cfgtoollogs/sqlpatch/30886680/23474251/30886680_apply_BIJU1_2021Jan18_10_34_01.log (no errors) SQL Patching tool complete on Mon Jan 18 10:37:30 2021
[oracle@oracleagent OPatch]$ sqlplus / as sysdba SQL*Plus: Release 12.2.0.1.0 Production on Mon Jan 18 10:38:48 2021 Copyright (c) 1982, 2016, Oracle. All rights reserved. Connected to: Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production
SQL> SELECT owner, object_name, object_type FROM all_objects WHERE status ='INVALID'; no rows selected
SQL> set line 1000 col action form a12 col version form a40 col description form a85 col action_date form a20 select description, action, to_char(action_time,'DD/MM/RR HH18:MI:SS') action_date, ' ' version from dba_registry_sqlpatch;
Thank you for giving your valuable time to read the above information. If you want to be updated with all our articles send us the Invitation or Follow us: Ramkumar’s LinkedIn: https://www.linkedin.com/in/ramkumardba/ LinkedIn Group: https://www.linkedin.com/in/ramkumar-m-0061a0204/ Facebook Page: https://www.facebook.com/Oracleagent-344577549964301 Ramkumar’s Twitter : https://twitter.com/ramkuma02877110 Ramkumar’s Telegram: https://t.me/oracleageant Ramkumar’s Facebook: https://www.facebook.com/ramkumarram8
