How to Disable IPV6 on Oracle Linux 7

 Applies To: 

Linux OS - Version Oracle Linux 7.0 and later

Target: 

Disable IPV6 on Oracle Linux 7. 

Solution

Method 1: 

Append below lines in /etc/sysctl.conf then reboot:

net.ipv6.conf.all.disable_ipv6 = 1

net.ipv6.conf.default.disable_ipv6 = 1

Then make the settings effective:

# sysctl -p

Method 2: 

Edit /etc/default/grub and add ipv6.disable=1 in line GRUB_CMDLINE_LINUX, e.g.:

# cat /etc/default/grub
GRUB_TIMEOUT=5
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="ipv6.disable=1 crashkernel=auto rhgb quiet"
GRUB_DISABLE_RECOVERY="true"

Regenerate a GRUB configuration file and overwrite existing one:

# grub2-mkconfig -o /boot/grub2/grub.cfg

Restart the system and verify no line "inet6" in "# ip addr show" output.

Ref: Doc ID 2078115.1

Upgrade Oracle database 11.2.0.4 to 12.2.0.1 using DBUA

Make sure that you have installed Oracle 12c binary on the same server which Oracle 11g database you want to upgrade.

If you have not installed the binary of 12c please follow this link "How to install oracle 12c binary only"

Please follow the below steps to accomplish the task.

1. Environment

Hostname : ora-test.localhost Database Name : TESTDB Database version : 11.2.0.4 Database Home path : /u01/app/oracle/product/11.2.0.4/db_1 Target Database Version : 12.2.0.1 Target Database Path : /u01/app/oracle/product/12.2.0.1/db_1 Upgrade Method : Database Upgrade Assistant

2. Run preupgrade script

/u01/app/oracle/product/11.2.0.4/db_1/jdk/bin/java -jar \ /u01/app/oracle/product/12.2.0.1/db_1/rdbms/admin/preupgrade.jar FILE DIR /home/oracle/preupgrade

3. View Preupgrade log

cat /home/oracle/preupgrade/preupgrade.log Report generated by Oracle Database Pre-Upgrade Information Tool Version 12.2.0.1.0 Upgrade-To version: 12.2.0.1.0 ======================================= Status of the database prior to upgrade ======================================= Database Name: TESTDB Container Name: Not Applicable in Pre-12.1 database Container ID: Not Applicable in Pre-12.1 database Version: 11.2.0.4.0 Compatible: 11.2.0.4.0 Blocksize: 8192 Platform: Linux x86 64-bit Timezone File: 14 Database log mode: ARCHIVELOG Readonly: FALSE Edition: EE Oracle Component Upgrade Action Current Status ---------------- -------------- -------------- Oracle Server [to be upgraded] VALID JServer JAVA Virtual Machine [to be upgraded] VALID Oracle XDK for Java [to be upgraded] VALID Oracle Workspace Manager [to be upgraded] VALID OLAP Analytic Workspace [to be upgraded] VALID Oracle Enterprise Manager Repository [to be upgraded] VALID Oracle Text [to be upgraded] VALID Oracle XML Database [to be upgraded] VALID Oracle Java Packages [to be upgraded] VALID Oracle Multimedia [to be upgraded] VALID Oracle Spatial [to be upgraded] VALID Expression Filter [to be upgraded] VALID Rule Manager [to be upgraded] VALID Oracle Application Express [to be upgraded] VALID Oracle OLAP API [to be upgraded] VALID ============== BEFORE UPGRADE ============== Run <preupgradelogdirpath>/preupgrade_fixups.sql to complete all of the BEFORE UPGRADE action items below marked with '(AUTOFIXUP)'. REQUIRED ACTIONS ================ + Adjust TABLESPACE SIZES as needed. Auto 12.2.0.1.0 Tablespace Size Extend Min Size Action ---------- ---------- -------- ---------- ------ EXAMPLE 331 MB DISABLED 309 MB None SYSAUX 500 MB ENABLED 1414 MB None SYSTEM 750 MB ENABLED 1243 MB None TEMP 20 MB ENABLED 150 MB None UNDOTBS1 50 MB ENABLED 400 MB None Note that 12.2.0.1.0 minimum sizes are estimates. If you plan to upgrade multiple pluggable databases concurrently, then you must ensure that the UNDO tablespace size is equal to at least the number of pluggable databases that you upgrade concurrently, multiplied by that minimum. Failing to allocate sufficient space can cause the upgrade to fail. + Update NUMERIC INITIALIZATION PARAMETERS to meet estimated minimums. Parameter 12.2.0.1.0 minimum --------- ------------------ processes 300 + Set DB_RECOVERY_FILE_DEST_SIZE initialization parameter to at least 6480 MB. Check alert log during the upgrade to ensure there is remaining free space available in the recovery area. DB_RECOVERY_FILE_DEST_SIZE is set at 4182 MB. There is currently 3017 MB of free space remaining, which may not be adequate for the upgrade. Currently: Fast recovery area : /u01/app/oracle/fast_recovery_area Limit : 4182 MB Used : 1165 MB Available : 3017 MB The database has archivelog mode enabled, and the upgrade process will need free space to generate archived logs to the recovery area specified by initialization parameter DB_RECOVERY_FILE_DEST. The logs generated must not overflow the limit set by DB_RECOVERY_FILE_DEST_SIZE, as the upgrade may not proceed if the database stops responding. RECOMMENDED ACTIONS =================== + Remove the EM repository. - Copy the $ORACLE_HOME/rdbms/admin/emremove.sql script from the target 12.2.0.1.0 ORACLE_HOME into the source 11.2.0.4.0 ORACLE_HOME. Step 1: If database control is configured, stop EM Database Control, using the following command $> emctl stop dbconsole Step 2: Connect to the database using the SYS account AS SYSDBA SET ECHO ON; SET SERVEROUTPUT ON; @emremove.sql Without the set echo and serveroutput commands, you will not be able to follow the progress of the script. The database has an Enterprise Manager Database Control repository. Starting with Oracle Database 12c, the local Enterprise Manager Database Control does not exist anymore. The repository will be removed from your database during the upgrade. This step can be manually performed before the upgrade to reduce downtime. + Remove OLAP Catalog by running the 11.2.0.4.0 SQL script $ORACLE_HOME/olap/admin/catnoamd.sql script. The OLAP Catalog component, AMD, exists in the database. Starting with Oracle Database 12c, the OLAP Catalog (OLAP AMD) is desupported and will be automatically marked as OPTION OFF during the database upgrade if present. Oracle recommends removing OLAP Catalog (OLAP AMD) before database upgrade. + (AUTOFIXUP) Gather stale data dictionary statistics prior to database upgrade in off-peak time using: EXECUTE DBMS_STATS.GATHER_DICTIONARY_STATS; Dictionary statistics do not exist or are stale (not up-to-date). Dictionary statistics help the Oracle optimizer find efficient SQL execution plans and are essential for proper upgrade timing. Oracle recommends gathering dictionary statistics in the last 24 hours before database upgrade. For information on managing optimizer statistics, refer to the 11.2.0.4 Oracle Database Performance Tuning Guide. + Directly grant ADMINISTER DATABASE TRIGGER privilege to the owner of the trigger or drop and re-create the trigger with a user that was granted directly with such. You can list those triggers using "SELECT OWNER, TRIGGER_NAME FROM DBA_TRIGGERS WHERE BASE_OBJECT_TYPE=''DATABASE'' AND OWNER NOT IN (SELECT GRANTEE FROM DBA_SYS_PRIVS WHERE PRIVILEGE=''ADMINISTER DATABASE TRIGGER'')" SELECT OWNER, TRIGGER_NAME FROM DBA_TRIGGERS WHERE BASE_OBJECT_TYPE='DATABASE' AND OWNER NOT IN (SELECT GRANTEE FROM DBA_SYS_PRIVS WHERE PRIVILEGE='ADMINISTER DATABASE TRIGGER'); There is one or more database triggers whose owner does not have the right privilege on the database. The creation of database triggers must be done by users granted with ADMINISTER DATABASE TRIGGER privilege. Privilege must have been granted directly. + Please make sure that all the MVs are refreshed and sys.sumdelta$ becomes empty before doing upgrade, unless you have strong business reasons not to do so. You can use dbms_mview.refresh() to refresh the MVs except those stale ones to be kept due to business need. If there are any stale MVs depending on changes in sys.sumdelta$, do not truncate it, because doing so will cause wrong results after refresh. There is one or more non-fresh MV in the database or sumdelta$ is not empty. Oracle recommends that all materialized views (MV's) are refreshed before upgrading the database because this will clear the MV logs and the sumdelta$ table, and make the UPGRADE process faster. If you choose to not refresh some MVs, the change data for those MV's will be carried through the UPGRADE process. After UPGRADE, you can refresh the MV's and MV incremental refresh should work in normal cases. INFORMATION ONLY ================ + Consider upgrading APEX manually, before the database upgrade. The database contains APEX version 3.2.1.00.12 and will need to be upgraded to at least version 5.0.4.00.12. To reduce database upgrade time, you can upgrade APEX manually before the database upgrade. Refer to My Oracle Support Note 1088970.1 for information on APEX installation upgrades. ============= AFTER UPGRADE ============= Run <preupgradelogdirpath>/postupgrade_fixups.sql to complete all of the AFTER UPGRADE action items below marked with '(AUTOFIXUP)'. REQUIRED ACTIONS ================ None RECOMMENDED ACTIONS =================== + If you use the -T option for the database upgrade, then run $ORACLE_HOME/rdbms/admin/utluptabdata.sql after the upgrade is complete, to VALIDATE and UPGRADE any user tables affected by changes to Oracle-Maintained types. There are user tables dependent on Oracle-Maintained object types. If the -T option is used to set user tablespaces to READ ONLY during the upgrade, user tables in those tablespaces, that are dependent on Oracle-Maintained types, will not be automatically upgraded. If a type is evolved during the upgrade, any dependent tables need to be re-validated and upgraded to the latest type version AFTER the database upgrade completes. + Upgrade the database time zone version using the DBMS_DST package. The database is using timezone datafile version 14 and the target 12.2.0.1.0 database ships with timezone datafile version 26. Oracle recommends using the most recent timezone data. For further information, refer to My Oracle Support Note 1585343.1. + (AUTOFIXUP) Gather dictionary statistics after the upgrade using the command: EXECUTE DBMS_STATS.GATHER_DICTIONARY_STATS; Oracle recommends gathering dictionary statistics after upgrade. Dictionary statistics provide essential information to the Oracle optimizer to help it find efficient SQL execution plans. After a database upgrade, statistics need to be re-gathered as there can now be tables that have significantly changed during the upgrade or new tables that do not have statistics gathered yet. + Gather statistics on fixed objects two weeks after the upgrade using the command: EXECUTE DBMS_STATS.GATHER_FIXED_OBJECTS_STATS; This recommendation is given for all preupgrade runs. Fixed object statistics provide essential information to the Oracle optimizer to help it find efficient SQL execution plans. Those statistics are specific to the Oracle Database release that generates them, and can be stale upon database upgrade. INFORMATION ONLY ================ + Check the Oracle documentation for the identified components for their specific upgrade procedure. The database upgrade script will not upgrade the following Oracle components: OLAP Catalog,OWB The Oracle database upgrade script upgrades most, but not all Oracle Database components that may be installed. Some components that are not upgraded may have their own upgrade scripts, or they may be deprecated or obsolete.


4. Remove the EM repository

[oracle@ora-test ~]$ emctl stop dbconsole SQL> select name,open_mode,version from v$database,v$instance; NAME OPEN_MODE VERSION --------- -------------------- ----------------- TESTDB READ WRITE 11.2.0.4.0 SQL> SET ECHO ON; SQL> SET SERVEROUTPUT ON; SQL> !ls -ltr /u01/app/oracle/product/12.2.0.1/db_1/rdbms/admin/emremove.sql -rw-r--r-- 1 oracle oinstall 20740 Aug 8 2016 /u01/app/oracle/product/12.2.0.1/db_1/rdbms/admin/emremove.sql SQL> @/u01/app/oracle/product/12.2.0.1/db_1/rdbms/admin/emremove.sql Starting phase 6 : Dropping Oracle Enterprise Manager related other roles ... Process DBSNMP user Done processing DBSNMP user Finished phase 6 The Oracle Enterprise Manager related schemas and objects are dropped. Do the manual steps to stutdown the DB Control if not done before running this script and then delete the DB Control configuration files PL/SQL procedure successfully completed.

5. Remove OLAP Catalog

SQL> set echo on; SQL> set serveroutput on; SQL> !ls -ltr /u01/app/oracle/product/11.2.0.4/db_1/olap/admin/catnoamd.sql -rw-r--r--. 1 oracle oinstall 11916 Apr 13 2013 /u01/app/oracle/product/11.2.0.4/db_1/olap/admin/catnoamd.sql SQL> @/u01/app/oracle/product/11.2.0.4/db_1/olap/admin/catnoamd.sql SQL> rem SQL> rem drop OLAP_DBA role SQL> rem SQL> drop role OLAP_DBA 2 / Role dropped. SQL> SQL> execute sys.dbms_registry.removed('AMD'); PL/SQL procedure successfully completed. SQL> SQL> -- No longer show up in dba_registry SQL> delete from registry$ where cid='AMD' and status='99'; 1 row deleted.

6. Update initialization parameters

SQL> show parameter processes NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ processes integer 150 SQL> alter system set processes=300 scope=spfile; System altered.

7. Gather Dictionary Stats

SQL> set echo on; SQL> set serveroutput on; SQL> execute dbms_stats.gather_dictionary_stats; PL/SQL procedure successfully completed.

8. Purge Recyclebin

SQL> purge dba_recyclebin; DBA Recyclebin purged.


9. Refresh materialized views
SQL> declare 2 list_failures integer(3) :=0; 3 begin 4 DBMS_MVIEW.REFRESH_ALL_MVIEWS(list_failures,'C','', TRUE, FALSE); 5 end; 6 / PL/SQL procedure successfully completed.

10. Run preupgrade_fixups.sql

SQL> set echo on; SQL> set serveroutput on; SQL> @/home/oracle/preupgrade/preupgrade_fixups.sql SQL> REM SQL> REM Oracle PRE-Upgrade Fixup Script SQL> REM SQL> REM Auto-Generated by: Oracle Preupgrade Script SQL> REM Version: 12.2.0.1.0 Build: 1 SQL> REM Generated on: 2019-10-14 13:12:49 SQL> REM SQL> REM Source Database: TESTDB SQL> REM Source Database Version: 11.2.0.4.0 SQL> REM For Upgrade to Version: 12.2.0.1.0 SQL> REM SQL> SQL> REM SQL> REM Setup Environment SQL> REM SQL> SET ECHO OFF SERVEROUTPUT ON FORMAT WRAPPED TAB OFF LINESIZE 200; Executing Oracle PRE-Upgrade Fixup Script Auto-Generated by: Oracle Preupgrade Script Version: 12.2.0.1.0 Build: 1 Generated on: 2019-10-14 13:12:49 For Source Database: TESTDB Source Database Version: 11.2.0.4.0 For Upgrade to Version: 12.2.0.1.0 Fixup Check Name Status Further DBA Action ---------- ------ ------------------ min_recovery_area_size Failed Manual fixup required. em_present Passed None amd_exists Passed None dictionary_stats Passed None trgowner_no_admndbtrg Passed None mv_refresh Passed None apex_upgrade_msg Failed Manual fixup recommended. PL/SQL procedure successfully completed.

11.  Verify archive log dest size

SQL> archive log list Database log mode Archive Mode Automatic archival Enabled Archive destination USE_DB_RECOVERY_FILE_DEST Oldest online log sequence 12 Next log sequence to archive 14 Current log sequence 14 SQL> !df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/ol-root 73G 27G 47G 37% /

12. Create Flashback Guaranteed Restore point

*** NO need to enable Flashback Database from 11.2.0.1 onwards *** Database MUST be in Archive Log mode *** MUST NOT change the compatible parameter to higher version SQL> select flashback_on from v$database; FLASHBACK_ON ------------------ NO SQL> select name, open_mode, log_mode from v$database; NAME OPEN_MODE LOG_MODE --------- -------------------- ------------ TESTDB READ WRITE ARCHIVELOG SQL> show parameter compatible NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ compatible string 11.2.0.4.0 SQL> show parameter recovery NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ db_recovery_file_dest string /u01/app/oracle/fast_recovery_ area db_recovery_file_dest_size big integer 4182M recovery_parallelism integer 0 SQL> alter system set db_recovery_file_dest_size=8G; System altered. SQL> show parameter recovery NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ db_recovery_file_dest string /u01/app/oracle/fast_recovery_ area db_recovery_file_dest_size big integer 8G recovery_parallelism integer 0 SQL> select * from v$restore_point; no rows selected SQL> create restore point pre_upgrade guarantee flashback database; Restore point created. SQL> col name for a20 SQL> col guarantee_flashback_database for a10 SQL> col time for a60 SQL> set lines 190 SQL> select name,guarantee_flashback_database,time from v$restore_point; NAME GUARANTEE_ TIME -------------------- ---------- ------------------------------------------------------------ PRE_UPGRADE YES 14-OCT-19 02.31.10.000000000 PM SQL>

13. Run DBUA

export new DB Home and run DBUA

Select Database which you want to upgrade and click on "Next".

Prerequisite checks will run. If there is any missing, here will display. And we need to fix it.

Check "Enable Parallel Upgrade", "Recompile Invalid Objects", "Upgrade Timezone Data" and "Gather Statistics Before Update" and click "Next".

Check "Use Flashback and Guaranteed Restore Point" and Click "Next".

We have already a Listener and the upgraded version of database will be registered on it. If there is not any listener listed, create it. And click "Next".

Uncheck the "Configure Enterprise Manager (EM) database express" and click "Next".

Summary page will be displayed. Review the all parameter once and click "Next".

Database upgradation is on progress.

Once Upgradation is completed, it will shows "Upgrade Results" page.

14. Verify the oratab

[oracle@ora-test ~]$ cat /etc/oratab TESTDB:/u01/app/oracle/product/12.2.0.1/db_1:Y

15. Verify Timezone version

[oracle@ora-test ~]$ SQL> select version from v$timezone_file; VERSION ---------- 26

16. Verify INVALID objects

[oracle@ora-test ~]$ SQL> select count(1) from dba_objects where status='INVALID'; COUNT(1) ---------- 0

17. Verify DBA_REGISTRY

18. Run postupgrade_fixups.sql

SQL> @/u01/app/oracle/cfgtoollogs/dbua/upgrade2019-10-14_02-48-04-PM/TESTDB/postupgrade_fixups.sql Session altered. PL/SQL procedure successfully completed. PL/SQL procedure successfully completed. Package created. No errors. Package body created. No errors. Package created. No errors. Package body created. No errors. Executing Oracle POST-Upgrade Fixup Script Auto-Generated by: Oracle Preupgrade Script Version: 12.2.0.1.0 Build: 1 Generated on: 2019-10-14 14:56:41 For Source Database: TESTDB Source Database Version: 11.2.0.4.0 For Upgrade to Version: 12.2.0.1.0 Fixup Check Name Status Further DBA Action ---------- ------ ------------------ depend_usr_tables Failed Manual fixup recommended. old_time_zones_exist Passed None post_dictionary Passed None fixed_objects Passed None upg_by_std_upgrd Passed None PL/SQL procedure successfully completed. Session altered.

19.  verify and re-configure wallet encryption

SQL> select * from v$encryption_wallet; WRL_TYPE WRL_PARAMETER STATUS WALLET_TYPE WALLET_OR FULLY_BAC CON_ID ----------------------------------------------------------------------------------------------------------------------------------------- FILE /u01/app/oracle/admin/TESTDB/wallet NOT_AVAILABLE UNKNOWN SINGLE UNDEFINED 0 # checking from the User side [oracle@ora-test TESTDB]$ sqlplus test SQL*Plus: Release 12.2.0.1.0 Production on Mon Oct 14 16:45:13 2019 Copyright (c) 1982, 2016, Oracle. All rights reserved. Enter password: ERROR: ORA-01017: invalid username/password; logon denied Enter user-name: test Enter password: Connected to: Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production SQL> select * from tab; TNAME TABTYPE CLUSTERID -------------------------------------------------------------------------------- ENCRYPT_TEST TABLE SQL> select tname from tab; TNAME -------------------------------------------------------------------------------- ENCRYPT_TEST SQL> select * from encrypt_test; select * from encrypt_test * ERROR at line 1: ORA-28365: wallet is not open ### to enable encryption on 12c follow this steps # copy encryption parameter from 11g sqlnet.ora and paste to 12c sqlnet.ora ----- NAMES.DIRECTORY_PATH= (TNSNAMES) ADR_BASE = /u01/app/oracle # wallet configuration ENCRYPTION_WALLET_LOCATION= (SOURCE=(METHOD=FILE)(METHOD_DATA= (DIRECTORY=/u01/app/oracle/admin/TESTDB/encryption_wallet/))) ----- # Shutdown and startup database SQL> shutdown immediate Database closed. Database dismounted. ORACLE instance shut down. SQL> startup ORACLE instance started. Total System Global Area 1795162112 bytes Fixed Size 8621760 bytes Variable Size 553648448 bytes Database Buffers 1224736768 bytes Redo Buffers 8155136 bytes Database mounted. Database opened. SQL> select * from v$encryption_wallet; WRL_TYPE WRL_PARAMETER STATUS WALLET_TYPE WALLET_OR FULLY_BAC CON_ID -------------------------------------------------------------------------------------------------------------------------------------------- FILE /u01/app/oracle/admin/TESTDB/encryption_wallet/ CLOSED UNKNOWN SINGLE UNDEFINED 0 SQL> alter system set encryption wallet open identified by "oracle4U_"; System altered. SQL> select * from v$encryption_wallet; WRL_TYPE WRL_PARAMETER STATUS WALLET_TYPE WALLET_OR FULLY_BAC CON_ID ------------------------------------------------------------------------------------------------------------------------------------------------ FILE /u01/app/oracle/admin/TESTDB/encryption_wallet/ OPEN PASSWORD SINGLE NO 0 # verify from user side SQL> select * from encrypt_test; ID DATA ---------- --------------- 1 this is secret! 1 this is secret! 1 this is secret! 1 this is secret! 1 this is secret! 1 this is secret! 1 this is secret! 1 this is secret! 1 this is secret! 1 this is secret! 1 this is secret!

20. Drop Restore point

SQL> col name for a20 SQL> col guarantee_flashback_database for a10 SQL> col time for a60 SQL> set lines 190 SQL> select name, guarantee_flashback_database,time from v$restore_point; NAME GUARANTEE_ TIME -------------------- ---------- ------------------------------------------------------------ PRE_UPGRADE YES 14-OCT-19 02.31.10.000000000 PM SQL> !ls -l /u01/app/oracle/fast_recovery_area/TESTDB/flashback total 1116308 -rw-r----- 1 oracle oinstall 52436992 Oct 14 15:14 o1_mf_gt8fgl8m_.flb -rw-r----- 1 oracle oinstall 52436992 Oct 14 15:14 o1_mf_gt8fgn32_.flb -rw-r----- 1 oracle oinstall 52436992 Oct 14 15:15 o1_mf_gt8j0lsx_.flb -rw-r----- 1 oracle oinstall 52436992 Oct 14 15:15 o1_mf_gt8j0pgp_.flb -rw-r----- 1 oracle oinstall 52436992 Oct 14 15:16 o1_mf_gt8j103v_.flb -rw-r----- 1 oracle oinstall 52436992 Oct 14 15:17 o1_mf_gt8j1vnd_.flb -rw-r----- 1 oracle oinstall 52436992 Oct 14 15:19 o1_mf_gt8j3d79_.flb -rw-r----- 1 oracle oinstall 52436992 Oct 14 15:23 o1_mf_gt8j55w0_.flb -rw-r----- 1 oracle oinstall 52436992 Oct 14 15:25 o1_mf_gt8j8hoj_.flb -rw-r----- 1 oracle oinstall 52436992 Oct 14 15:26 o1_mf_gt8jj9wo_.flb -rw-r----- 1 oracle oinstall 52436992 Oct 14 15:27 o1_mf_gt8jn2qw_.flb -rw-r----- 1 oracle oinstall 52436992 Oct 14 15:27 o1_mf_gt8jq9lh_.flb -rw-r----- 1 oracle oinstall 52436992 Oct 14 15:28 o1_mf_gt8jqm9m_.flb -rw-r----- 1 oracle oinstall 52436992 Oct 14 15:30 o1_mf_gt8jr3wt_.flb -rw-r----- 1 oracle oinstall 52436992 Oct 14 15:33 o1_mf_gt8jtm2n_.flb -rw-r----- 1 oracle oinstall 104865792 Oct 14 15:41 o1_mf_gt8jx4v9_.flb -rw-r----- 1 oracle oinstall 125837312 Oct 14 17:11 o1_mf_gt8k3mwr_.flb -rw-r----- 1 oracle oinstall 125837312 Oct 14 15:41 o1_mf_gt8klmdb_.flb SQL> drop restore point PRE_UPGRADE; Restore point dropped. SQL> select NAME,GUARANTEE_FLASHBACK_DATABASE,TIME from V$restore_point; no rows selected SQL> !ls -l /u01/app/oracle/fast_recovery_area/TESTDB/flashback total 0 SQL>


21. verify compatible parameter and update if needed.

Warning: If the value of COMPATIBLE parameter is changed to 12.2.0.1 then if for some reasons database needs to be downgraded to 11.2.0.4 the DBA would not have any option other than export/import to downgrade the database. But if this parameter is left unchanged for sometime to see how the database performs after upgrade then it is very easy and fast to downgrade the database if for some reason it is required to be downgraded. If you change COMPATIBLE you can directly drop your restore points as they are useless. You can’t use Flashback Database to restore point back across a compatibility change of your database.
SQL> show parameter COMPATIBLE NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ compatible string 11.2.0.4.0 <--- noncdb_compatible boolean FALSE SQL> SQL> ALTER SYSTEM SET COMPATIBLE = '12.2.0' SCOPE=SPFILE; System altered. SQL> SQL> shut immediate; Database closed. Database dismounted. ORACLE instance shut down. SQL> SQL> startup; ORACLE instance started. Total System Global Area 1660944384 bytes Fixed Size 8621376 bytes Variable Size 1056965312 bytes Database Buffers 587202560 bytes Redo Buffers 8155136 bytes Database mounted. Database opened. SQL> SQL> show parameter COMPATIBLE NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ compatible string 12.2.0 <---- noncdb_compatible boolean FALSE SQL> SQL> select name,open_mode,version from v$database,v$instance; NAME OPEN_MODE VERSION -------------------- -------------------- ----------------- TESTDB READ WRITE 12.2.0.1.0