Oracledbwr – Page 2 – Oracle Updates by HariPrasath Rajaram

Oracle 18c Database Upgrade From 12.2.0.1 to 18.3.0.0 Using DBUA

Description:-

There are different ways of upgrading to the latest release of Oracle database and Oracle provides multiple methods to upgrade. Few are listed below:

Database Upgrade Assistant (DBUA)
Manual Upgrade
Transportable Tablespaces
Datapump export/import
Oracle Streams
Oracle GoldenGate

Here I am going to choose DBUA to upgrade my database,

Backup 12c database using RMAN

rman target /

run
{
backup database plus archivelog;
backup current controlfile;
backup spfile;
}

Ensure backup is complete before upgrade.

SQL> SELECT * FROM v$backup WHERE status != 'NOT ACTIVE';

no rows selected

Empty Recycle bin.

SQL> PURGE DBA_RECYCLEBIN ;

DBA Recyclebin purged.

Run Gather statistics to finish upgrade soon.

SQL> EXEC DBMS_STATS.GATHER_DICTIONARY_STATS;

PL/SQL procedure successfully completed.

Stop the running 12c listener

lsnrctl stop LISTENER

Run preupgrade tool and fixups

Oracle strongly recommends that you run the Pre-Upgrade Information Tool before starting the upgrade with DBUA. Although DBUA runs the Pre-Upgrade Information Tool as part of the pre-requisite checks, it is good practice to run the tool ahead of time in order to analyze the database and take actions that can decrease downtime for upgrading.

Connect to 12.2.0.1 database environment as SYS,

Pre-upgrade checks :

Run the preupgrade tool .

[oracle@ram admin]$ export ORACLE_SID=dbwr
[oracle@ram admin]$ export ORACLE_HOME=/u01/app/oracle/product/12.2.0.1/db_1
[oracle@ram admin]$ /u01/app/oracle/product/12.2.0.1/db_1/jdk/bin/java -jar /u01/app/oracle/product/18.0.0/db_1/rdbms/admin/preupgrade.jar TEXT TERMINAL
Report generated by Oracle Database Pre-Upgrade Information Tool Version
18.0.0.0.0 on 2019-02-12T00:53:56

Upgrade-To version: 18.0.0.0.0

=======================================
Status of the database prior to upgrade
=======================================
Database Name:     DBWR
Container Name:    DBWR
Container ID:      0
Version:           12.2.0.1.0
Compatible:        12.2.0
Blocksize:         8192
Platform:          Linux x86 64-bit
Timezone File:     26
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 
Real Application Clusters          [to be upgraded]   OPTION OFF 
Oracle Workspace Manager           [to be upgraded]   VALID 
OLAP Analytic Workspace            [to be upgraded]   VALID 
Oracle Label Security              [to be upgraded]   VALID 
Oracle Database Vault              [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 
Oracle OLAP API                    [to be upgraded]   VALID

==============
BEFORE UPGRADE
==============

REQUIRED ACTIONS
================
None

RECOMMENDED ACTIONS
===================
1. (AUTOFIXUP) Gather statistics on fixed objects prior the upgrade.

None of the fixed object tables have had stats collected.

Gathering statistics on fixed objects, if none have been gathered yet, is
recommended prior to upgrading.

For information on managing optimizer statistics, refer to the 12.2.0.1
Oracle Database SQL Tuning Guide.

INFORMATION ONLY
================
2. To help you keep track of your tablespace allocations, the following
AUTOEXTEND tablespaces are expected to successfully EXTEND during the
upgrade process.

                         Min Size
Tablespace    Size       For Upgrade
----------   --------    -----------
SYSAUX        460 MB      675 MB
SYSTEM        800 MB      1242 MB
TEMP          32 MB       150 MB
UNDOTBS1      65 MB       439 MB

Minimum tablespace sizes for upgrade are estimates.

ORACLE GENERATED FIXUP SCRIPT
=============================
All of the issues in database DBWR
which are identified above as BEFORE UPGRADE "(AUTOFIXUP)" can be resolved by
executing the following

SQL>@/u01/app/oracle/cfgtoollogs/dbwr/preupgrade/preupgrade_fixups.sql

=============
AFTER UPGRADE
=============

REQUIRED ACTIONS
================
None

RECOMMENDED ACTIONS
===================
3. Upgrade the database time zone file using the DBMS_DST package.

The database is using time zone file version 26 and the target 18.0.0.0.0
release ships with time zone file version 31.

Oracle recommends upgrading to the desired (latest) version of the time
zone file. For more information, refer to "Upgrading the Time Zone File
and Timestamp with Time Zone Data" in the 18.0.0.0.0 Oracle Database
Globalization Support Guide.

4. (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.

5. Gather statistics on fixed objects after the upgrade and when there is a
representative workload on the system 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.

For information on managing optimizer statistics, refer to the 12.2.0.1
Oracle Database SQL Tuning Guide.

ORACLE GENERATED FIXUP SCRIPT
=============================
All of the issues in database DBWR
which are identified above as AFTER UPGRADE "(AUTOFIXUP)" can be resolved by
executing the following

SQL>@/u01/app/oracle/cfgtoollogs/dbwr/preupgrade/postupgrade_fixups.sql


==================
PREUPGRADE SUMMARY
==================
/u01/app/oracle/cfgtoollogs/dbwr/preupgrade/preupgrade.log
/u01/app/oracle/cfgtoollogs/dbwr/preupgrade/preupgrade_fixups.sql
/u01/app/oracle/cfgtoollogs/dbwr/preupgrade/postupgrade_fixups.sql

Execute fixup scripts as indicated below:

Before upgrade log into the database and execute the preupgrade fixups
@/u01/app/oracle/cfgtoollogs/dbwr/preupgrade/preupgrade_fixups.sql

After the upgrade:

Log into the database and execute the postupgrade fixups
@/u01/app/oracle/cfgtoollogs/dbwr/preupgrade/postupgrade_fixups.sql

Preupgrade complete: 2019-02-12T00:53:56

Run the preupgrade_fixup.sql

SQL> @/u01/app/oracle/cfgtoollogs/dbwr/preupgrade/preupgrade_fixups.sql
Executing Oracle PRE-Upgrade Fixup Script

Auto-Generated by: Oracle Preupgrade Script
Version: 18.0.0.0.0 Build: 1
Generated on: 2019-02-12 00:53:50

For Source Database: DBWR
Source Database Version: 12.2.0.1.0
For Upgrade to Version: 18.0.0.0.0

Preup                               Preupgrade
Action                              Issue Is
Number      Preupgrade  Check Name  Remedied   Further DBA Action
------     -----------------------  ---------  -------------------
1.            pre_fixed_objects      YES                None.
2.            tablespaces_info       NO         Informational only.
Further action is optional.

The fixup scripts have been run and resolved what they can. However,
there are still issues originally identified by the preupgrade that
have not been remedied and are still present in the database.
Depending on the severity of the specific issue, and the nature of
the issue itself, that could mean that your database is not ready
for upgrade. To resolve the outstanding issues, start by reviewing
the preupgrade_fixups.sql and searching it for the name of
the failed CHECK NAME or Preupgrade Action Number listed above.
There you will find the original corresponding diagnostic message
from the preupgrade which explains in more detail what still needs
to be done.

PL/SQL procedure successfully completed.

UPGRADE:

At this stage, we are still connected to 12c database which is up and running.

Now run the dbua utility from 12c oracle_home location.

[oracle@ram ~]$ export PATH=$ORACLE_HOME/bin:$PATH
[oracle@ram ~]$ export ORACLE_SID=dbwr
[oracle@ram ~]$ export ORACLE_HOME=/u01/app/oracle/product/18.0.0/db_1
[oracle@ram ~]$ cd /u01/app/oracle/product/12.2.0.1/db_1/bin
[oracle@ram bin]$ ./dbua

DBUA performs some of the checks before actually starting the database upgrade. Some of the checks can be done manually to reduce downtime for the upgrade.

DBUA provides below options:

– Upgrade timezone.

– Gather dictionary statistics before upgrade.

– Make user tablespaces read only.

– Take RMAN backup before upgrade.

– Create Restore Point for Database Flashback

– Restore database backup to rollback upgrade

– Option to execute Custom scripts before and after upgrade

– show the location of DBUA logs and Alert log files.

– Option to upgrade existing listener to 18.x home or create a new listener in 18.x target home.

select the Upgrade Oracle Database option, then click the “Next” button.

If the prerequisite checks highlight any issues, take the appropriate action to fix the issues. If all the prerequisite checks are passed, click the “Next” button.

Amend the upgrade options if necessary, then click the “Next” button.

Select the recovery options for use in the event of an upgrade failure, then click the “Next” button.

If the database is using the 12c listener, accept the defaults, so the listener will be upgraded. If you prefer to manually define a new listener, you can do that now too and click the “Next” button.

Select the desired management options, then click the “Next” button

Post-upgrade checks:

Run “postupgrade_fixups.sql” to check post upgrade status.

SQL> @/u01/app/oracle/cfgtoollogs/dbwr/preupgrade/postupgrade_fixups.sql

Session altered.

PL/SQL procedure successfully completed.

Package created.

No errors.

Package body created.

PL/SQL procedure successfully completed.

No errors.

Executing Oracle POST-Upgrade Fixup Script

Auto-Generated by: Oracle Preupgrade Script
Version: 18.0.0.0.0 Build: 1
Generated on: 2019-02-12 00:53:56

For Source Database: DBWR
Source Database Version: 12.2.0.1.0
For Upgrade to Version: 18.0.0.0.0

Preup Preupgrade
Action Issue Is
Number Preupgrade Check Name Remedied Further DBA Action
------ ------------------------ ---------- ------------------
3. old_time_zones_exist YES None.
4. post_dictionary YES None.
5. post_fixed_objects NO Informational only.
Further action is optional.

The fixup scripts have been run and resovled what they can. However,
there are still issues originally identified by the preupgrade that
have not been remedied and are still present in the database.
Depending on the severity of the specific issue, and the nature of
the issue itself, that could mean that your database upgrade is not
fully complete. To resolve the outstanding issues, start by reviewing
the postupgrade_fixups.sql and searching it for the name of
the failed CHECK NAME or Preupgrade Action Number listed above.
There you will find the original corresponding diagnostic message
from the preupgrade which explains in more detail what still needs
to be done.

PL/SQL procedure successfully completed.

Session altered.

Now the database upgrade is complete and the database is ready for normal use.

SQL> select VERSION,name,open_mode from v$instance,v$database;

VERSION            NAME          OPEN_MODE
------------     ---------      -----------
18.0.0.0.0         DBWR          READ WRITE

SQL> SELECT * FROM v$timezone_file;

FILENAME              VERSION     CON_ID
-------------------- ---------- ----------
timezlrg_31.dat         31          0

SQL> select TZ_VERSION from registry$database;

TZ_VERSION
----------
    31

Catch Me On:- Hariprasath Rajaram 

Telegram:https://t.me/joinchat/I_f4DkeGfZuxgMIoJSpQZg 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/hariprasathdba

Oracle 19c Database Upgrade From 11.2.0.4 to 19.2.0.0 Using Manual Method

Description:-

A manual upgrade consists of running SQL scripts and utilities from a command line to upgrade a database to the new Oracle Database release.

Oracle Database Releases That Support Direct Upgrade
Review the supported options for direct upgrades to the latest Oracle Database release.
You can perform a direct upgrade to the new release from the following releases:
• 11.2.0.4
• 12.1.0.1 and 12.1.0.2
• 12.2.0.1

Presteps for db upgrade :-

Take RMAN full backups before upgrade.

rman target / 

run {
allocate channel test_backup_disk1 type disk format '/u01/backup/%d_%U';
backup incremental level 0 tag 'ORCL_BEFORE_UPG'  database;
backup format  tag 'ORCL_CONTROL_FILE' current controlfile;
release channel test_backup_disk1;
}

Ensure backup is complete before upgrade.

SQL> SELECT * FROM v$backup WHERE status != 'NOT ACTIVE';

no rows selected

Empty Recycle bin.

SQL> PURGE DBA_RECYCLEBIN ;

DBA Recyclebin purged.

Run Gather statistics to finish upgrade soon.

SQL> EXEC DBMS_STATS.GATHER_DICTIONARY_STATS;

PL/SQL procedure successfully completed.

Run the preupgrade tool:

The preupgrade.jar Pre-Upgrade Information Tool is supplied with Oracle Database 18c.This tool has reside in new oracle home.

/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/preupgrade.jar

[oracle@19c ~]$ /u01/app/oracle/product/11.2.0/dbhome_1/jdk/bin/java -jar /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/preupgrade.jar FILE DIR /u01/preupgrade/

==================
PREUPGRADE SUMMARY
==================
/u01/preupgrade/preupgrade.log
/u01/preupgrade/preupgrade_fixups.sql
/u01/preupgrade/postupgrade_fixups.sql

Execute fixup scripts as indicated below:

Before upgrade:

Log into the database and execute the preupgrade fixups
@/u01/preupgrade/preupgrade_fixups.sql

After the upgrade:

Log into the database and execute the postupgrade fixups
@/u01/preupgrade/postupgrade_fixups.sql

Preupgrade complete: 2019-03-21T21:12:31

Run preupgrade fixups.sql

SQL> @/u01/preupgrade/preupgrade_fixups.sql
Executing Oracle PRE-Upgrade Fixup Script

Auto-Generated by: Oracle Preupgrade Script
Version: 19.0.0.0.0 Build: 1
Generated on: 2019-03-21 21:12:27

For Source Database: MIG19C
Source Database Version: 11.2.0.4.0
For Upgrade to Version: 19.0.0.0.0

Preup Preupgrade
Action Issue Is
Number Preupgrade Check Name Remedied Further DBA Action
------ ------------------------ ---------- --------------------------------
1. parameter_min_val NO Manual fixup recommended.
2. em_present NO Manual fixup recommended.
3. amd_exists NO Manual fixup recommended.
4. apex_manual_upgrade NO Manual fixup recommended.
5. dictionary_stats YES None.
6. trgowner_no_admndbtrg YES None.
7. pre_fixed_objects YES None.
8. tablespaces_info NO Informational only.
Further action is optional.
9. exf_rul_exists NO Informational only.
Further action is optional.
10. rman_recovery_version NO Informational only.
Further action is optional.

The fixup scripts have been run and resolved what they can. However,
there are still issues originally identified by the preupgrade that
have not been remedied and are still present in the database.
Depending on the severity of the specific issue, and the nature of
the issue itself, that could mean that your database is not ready
for upgrade. To resolve the outstanding issues, start by reviewing
the preupgrade_fixups.sql and searching it for the name of
the failed CHECK NAME or Preupgrade Action Number listed above.
There you will find the original corresponding diagnostic message
from the preupgrade which explains in more detail what still needs
to be done.

PL/SQL procedure successfully completed.

Check Timezone version :

Check if target database’s time zone version is lower than the source database time zone version.

SQL> SELECT version FROM v$timezone_file;

VERSION
-------
14

SQL> SELECT PROPERTY_NAME, SUBSTR(property_value, 1, 30) value
FROM DATABASE_PROPERTIES
WHERE PROPERTY_NAME LIKE 'DST_%'
ORDER BY PROPERTY_NAME; 2 3 4

PROPERTY_NAME            VALUE
------------------------ -----
DST_PRIMARY_TT_VERSION   14
DST_SECONDARY_TT_VERSION 0
DST_UPGRADE_STATE        NONE

Upgrade Database from 11.2.0.4 to 19c :-

Shutdown the 11g database:

SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.

Copy the parameter and password file from the 11g home to the new 19c home.

[oracle@19c ~]$ cp /u01/app/oracle/product/11.2.0/dbhome_1/dbs/spfileMIG19C.ora /u01/app/oracle/product/19.0.0/dbhome_1
[oracle@19c ~]$ cp /u01/app/oracle/product/11.2.0/dbhome_1/dbs/orapwMIG19C /u01/app/oracle/product/19.0.0/dbhome_1

Set new ORACLE_HOME for 19c location and startup database in upgrade mode :

[oracle@19c ~]$ export ORACLE_SID=MIG19C
[oracle@19c ~]$ export ORACLE_HOME=/u01/app/oracle/product/19.0.0/dbhome_1
[oracle@19c ~]$ export PATH=/u01/app/oracle/product/19.0.0/dbhome_1:$PATH
[oracle@19c ~]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.4.0 Production on Thu Mar 21 21:33:54 2019

Copyright (c) 1982, 2013, Oracle. All rights reserved.

Connected to an idle instance.

SQL> startup upgrade
ORACLE instance started.

Total System Global Area 1543500136 bytes
Fixed Size 8896872 bytes
Variable Size 939524096 bytes
Database Buffers 587202560 bytes
Redo Buffers 7876608 bytes
Database mounted.
Database opened.

Run the dbupgrade utility :

[oracle@19c bin]$ export ORACLE_SID=MIG19C

[oracle@19c bin]$ ./dbupgrade

Argument list for [/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catctl.pl]
For Oracle internal use only A = 0
Run in c = 0
Do not run in C = 0
Input Directory d = 0
Echo OFF e = 1
Simulate E = 0
Forced cleanup F = 0
Log Id i = 0
Child Process I = 0
Log Dir l = 0
Priority List Name L = 0
Upgrade Mode active M = 0
SQL Process Count n = 0
SQL PDB Process Count N = 0
Open Mode Normal o = 0
Start Phase p = 0
End Phase P = 0
Reverse Order r = 0
AutoUpgrade Resume R = 0
Script s = 0
Serial Run S = 0
RO User Tablespaces T = 0
Display Phases y = 0
Debug catcon.pm z = 0
Debug catctl.pl Z = 0

catctl.pl VERSION: [19.0.0.0.0]
STATUS: [Production]
BUILD: [RDBMS_19.2.0.0.0_LINUX.X64_190204]

/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/orahome = [/u01/app/oracle/product/19.0.0/dbhome_1]
/u01/app/oracle/product/19.0.0/dbhome_1/bin/orabasehome = [/u01/app/oracle/product/19.0.0/dbhome_1]
catctlGetOraBaseLogDir = [/u01/app/oracle/product/19.0.0/dbhome_1]

Analyzing file /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catupgrd.sql

Log file directory = [/tmp/cfgtoollogs/upgrade20190321214707]

catcon::set_log_file_base_path: ALL catcon-related output will be written to [/tmp/cfgtoollogs/upgrade20190321214707/catupgrd_catcon_9390.lst]

catcon::set_log_file_base_path: catcon: See [/tmp/cfgtoollogs/upgrade20190321214707/catupgrd*.log] files for output generated by scripts

catcon::set_log_file_base_path: catcon: See [/tmp/cfgtoollogs/upgrade20190321214707/catupgrd_*.lst] files for spool files, if any

Number of Cpus = 1
Database Name = MIG19C
DataBase Version = 11.2.0.4.0
catcon::set_log_file_base_path: ALL catcon-related output will be written to [/u01/app/oracle/product/19.0.0/dbhome_1/cfgtoollogs/MIG19C/upgrade20190321214709/catupgrd_catcon_9390.lst]

catcon::set_log_file_base_path: catcon: See [/u01/app/oracle/product/19.0.0/dbhome_1/cfgtoollogs/MIG19C/upgrade20190321214709/catupgrd*.log] files for output generated by scripts

catcon::set_log_file_base_path: catcon: See [/u01/app/oracle/product/19.0.0/dbhome_1/cfgtoollogs/MIG19C/upgrade20190321214709/catupgrd_*.lst] files for spool files, if any

Log file directory = [/u01/app/oracle/product/19.0.0/dbhome_1/cfgtoollogs/MIG19C/upgrade20190321214709]

Components in [MIG19C]
Installed [APEX APS CATALOG CATJAVA CATPROC CONTEXT EM JAVAVM ORDIM OWM SDO XDB XML XOQ]
Not Installed [DV MGW ODM OLS RAC WK]
Parallel SQL Process Count = 4

------------------------------------------------------
Phases [0-107] Start Time:[2019_03_21 21:47:10]
------------------------------------------------------
*********** Executing Change Scripts ***********
Serial Phase #:0 [MIG19C] Files:1 [oracle@19c bin]$ export ORACLE_SID=MIG19C
[oracle@19c bin]$ ./dbupgrade

Argument list for [/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catctl.pl]
For Oracle internal use only A = 0
Run in c = 0
Do not run in C = 0
Input Directory d = 0
Echo OFF e = 1
Simulate E = 0
Forced cleanup F = 0
Log Id i = 0
Child Process I = 0
Log Dir l = 0
Priority List Name L = 0
Upgrade Mode active M = 0
SQL Process Count n = 0
SQL PDB Process Count N = 0
Open Mode Normal o = 0
Start Phase p = 0
End Phase P = 0
Reverse Order r = 0
AutoUpgrade Resume R = 0
Script s = 0
Serial Run S = 0
RO User Tablespaces T = 0
Display Phases y = 0
Debug catcon.pm z = 0
Debug catctl.pl Z = 0

catctl.pl VERSION: [19.0.0.0.0]
STATUS: [Production]
BUILD: [RDBMS_19.2.0.0.0_LINUX.X64_190204]

/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/orahome = [/u01/app/oracle/product/19.0.0/dbhome_1]
/u01/app/oracle/product/19.0.0/dbhome_1/bin/orabasehome = [/u01/app/oracle/product/19.0.0/dbhome_1]
catctlGetOraBaseLogDir = [/u01/app/oracle/product/19.0.0/dbhome_1]

Analyzing file /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catupgrd.sql

Log file directory = [/tmp/cfgtoollogs/upgrade20190321214707]

catcon::set_log_file_base_path: ALL catcon-related output will be written to [/tmp/cfgtoollogs/upgrade20190321214707/catupgrd_catcon_9390.lst]

catcon::set_log_file_base_path: catcon: See [/tmp/cfgtoollogs/upgrade20190321214707/catupgrd*.log] files for output generated by scripts

catcon::set_log_file_base_path: catcon: See [/tmp/cfgtoollogs/upgrade20190321214707/catupgrd_*.lst] files for spool files, if any

Number of Cpus = 1
Database Name = MIG19C
DataBase Version = 11.2.0.4.0
catcon::set_log_file_base_path: ALL catcon-related output will be written to [/u01/app/oracle/product/19.0.0/dbhome_1/cfgtoollogs/MIG19C/upgrade20190321214709/catupgrd_catcon_9390.lst]

catcon::set_log_file_base_path: catcon: See [/u01/app/oracle/product/19.0.0/dbhome_1/cfgtoollogs/MIG19C/upgrade20190321214709/catupgrd*.log] files for output generated by scripts

catcon::set_log_file_base_path: catcon: See [/u01/app/oracle/product/19.0.0/dbhome_1/cfgtoollogs/MIG19C/upgrade20190321214709/catupgrd_*.lst] files for spool files, if any

Log file directory = [/u01/app/oracle/product/19.0.0/dbhome_1/cfgtoollogs/MIG19C/upgrade20190321214709]

Components in [MIG19C]
Installed [APEX APS CATALOG CATJAVA CATPROC CONTEXT EM JAVAVM ORDIM OWM SDO XDB XML XOQ]
Not Installed [DV MGW ODM OLS RAC WK]
Parallel SQL Process Count = 4

------------------------------------------------------
Phases [0-107] Start Time:[2019_03_21 21:47:10]
------------------------------------------------------
*********** Executing Change Scripts ***********
Serial Phase #:0 [MIG19C] Files:1
Time: 68s
*************** Catalog Core SQL ***************
Serial Phase #:1 [MIG19C] Files:5 Time: 48s
Restart Phase #:2 [MIG19C] Files:1 Time: 1s
*********** Catalog Tables and Views ***********
Parallel Phase #:3 [MIG19C] Files:19 Time: 25s
Restart Phase #:4 [MIG19C] Files:1 Time: 1s
************* Catalog Final Scripts ************
Serial Phase #:5 [MIG19C] Files:7 Time: 24s
***************** Catproc Start ****************
Serial Phase #:6 [MIG19C] Files:1 Time: 12s
***************** Catproc Types ****************
Serial Phase #:7 [MIG19C] Files:2 Time: 10s
Restart Phase #:8 [MIG19C] Files:1 Time: 0s
**************** Catproc Tables ****************
Parallel Phase #:9 [MIG19C] Files:67 Time: 42s
Restart Phase #:10 [MIG19C] Files:1 Time: 1s
************* Catproc Package Specs ************
Serial Phase #:11 [MIG19C] Files:1 Time: 63s
Restart Phase #:12 [MIG19C] Files:1 Time: 0s
************** Catproc Procedures **************
Parallel Phase #:13 [MIG19C] Files:94 Time: 12s
Restart Phase #:14 [MIG19C] Files:1 Time: 1s
Parallel Phase #:15 [MIG19C] Files:120 Time: 21s
Restart Phase #:16 [MIG19C] Files:1 Time: 0s
Serial Phase #:17 [MIG19C] Files:22 Time: 3s
Restart Phase #:18 [MIG19C] Files:1 Time: 1s
***************** Catproc Views ****************
Parallel Phase #:19 [MIG19C] Files:32 Time: 28s
Restart Phase #:20 [MIG19C] Files:1 Time: 1s
Serial Phase #:21 [MIG19C] Files:3 Time: 11s
Restart Phase #:22 [MIG19C] Files:1 Time: 0s
Parallel Phase #:23 [MIG19C] Files:25 Time: 197s
Restart Phase #:24 [MIG19C] Files:1 Time: 1s
Parallel Phase #:25 [MIG19C] Files:12 Time: 106s
Restart Phase #:26 [MIG19C] Files:1 Time: 0s
Serial Phase #:27 [MIG19C] Files:1 Time: 0s
Serial Phase #:28 [MIG19C] Files:3 Time: 4s
Serial Phase #:29 [MIG19C] Files:1 Time: 0s
Restart Phase #:30 [MIG19C] Files:1 Time: 0s
*************** Catproc CDB Views **************
Serial Phase #:31 [MIG19C] Files:1 Time: 1s
Restart Phase #:32 [MIG19C] Files:1 Time: 1s
Serial Phase #:34 [MIG19C] Files:1 Time: 0s
***************** Catproc PLBs *****************
Serial Phase #:35 [MIG19C] Files:293 Time: 22s
Serial Phase #:36 [MIG19C] Files:1 Time: 0s
Restart Phase #:37 [MIG19C] Files:1 Time: 0s
Serial Phase #:38 [MIG19C] Files:6 Time: 5s
Restart Phase #:39 [MIG19C] Files:1 Time: 0s
*************** Catproc DataPump ***************
Serial Phase #:40 [MIG19C] Files:3 Time: 51s
Restart Phase #:41 [MIG19C] Files:1 Time: 1s
****************** Catproc SQL *****************
Parallel Phase #:42 [MIG19C] Files:13 Time: 117s
Restart Phase #:43 [MIG19C] Files:1 Time: 1s
Parallel Phase #:44 [MIG19C] Files:11 Time: 17s
Restart Phase #:45 [MIG19C] Files:1 Time: 0s
Parallel Phase #:46 [MIG19C] Files:3 Time: 2s
Restart Phase #:47 [MIG19C] Files:1 Time: 0s
************* Final Catproc scripts ************
Serial Phase #:48 [MIG19C] Files:1 Time: 9s
Restart Phase #:49 [MIG19C] Files:1 Time: 1s
************** Final RDBMS scripts *************
Serial Phase #:50 [MIG19C] Files:1 Time: 20s
************ Upgrade Component Start ***********
Serial Phase #:51 [MIG19C] Files:1 Time: 1s
Restart Phase #:52 [MIG19C] Files:1 Time: 0s
********** Upgrading Java and non-Java *********
Serial Phase #:53 [MIG19C] Files:2 Time: 587s
***************** Upgrading XDB ****************
Restart Phase #:54 [MIG19C] Files:1 Time: 1s
Serial Phase #:56 [MIG19C] Files:3 Time: 28s
Serial Phase #:57 [MIG19C] Files:3 Time: 4s
Parallel Phase #:58 [MIG19C] Files:10 Time: 3s
Parallel Phase #:59 [MIG19C] Files:25 Time: 4s
Serial Phase #:60 [MIG19C] Files:4 Time: 7s
Serial Phase #:61 [MIG19C] Files:1 Time: 0s
Serial Phase #:62 [MIG19C] Files:32 Time: 4s
Serial Phase #:63 [MIG19C] Files:1 Time: 0s
Parallel Phase #:64 [MIG19C] Files:6 Time: 6s
Serial Phase #:65 [MIG19C] Files:2 Time: 22s
Serial Phase #:66 [MIG19C] Files:3 Time: 80s
**************** Upgrading ORDIM ***************
Restart Phase #:67 [MIG19C] Files:1 Time: 1s
Serial Phase #:69 [MIG19C] Files:1 Time: 1s
Parallel Phase #:70 [MIG19C] Files:2 Time: 56s
Restart Phase #:71 [MIG19C] Files:1 Time: 0s
Parallel Phase #:72 [MIG19C] Files:2 Time: 1s
Serial Phase #:73 [MIG19C] Files:2 Time: 1s
***************** Upgrading SDO ****************
Restart Phase #:74 [MIG19C] Files:1 Time: 0s
Serial Phase #:76 [MIG19C] Files:1 Time: 85s
Serial Phase #:77 [MIG19C] Files:2 Time: 2s
Restart Phase #:78 [MIG19C] Files:1 Time: 1s
Serial Phase #:79 [MIG19C] Files:1 Time: 19s
Restart Phase #:80 [MIG19C] Files:1 Time: 0s
Parallel Phase #:81 [MIG19C] Files:3 Time: 82s
Restart Phase #:82 [MIG19C] Files:1 Time: 1s
Serial Phase #:83 [MIG19C] Files:1 Time: 5s
Restart Phase #:84 [MIG19C] Files:1 Time: 0s
Serial Phase #:85 [MIG19C] Files:1 Time: 11s
Restart Phase #:86 [MIG19C] Files:1 Time: 0s
Parallel Phase #:87 [MIG19C] Files:4 Time: 142s
Restart Phase #:88 [MIG19C] Files:1 Time: 1s
Serial Phase #:89 [MIG19C] Files:1 Time: 1s
Restart Phase #:90 [MIG19C] Files:1 Time: 0s
Serial Phase #:91 [MIG19C] Files:2 Time: 9s
Restart Phase #:92 [MIG19C] Files:1 Time: 0s
Serial Phase #:93 [MIG19C] Files:1 Time: 1s
Restart Phase #:94 [MIG19C] Files:1 Time: 1s
******* Upgrading ODM, WK, EXF, RUL, XOQ *******
Serial Phase #:95 [MIG19C] Files:1 Time: 31s
Restart Phase #:96 [MIG19C] Files:1 Time: 0s
*********** Final Component scripts ***********
Serial Phase #:97 [MIG19C] Files:1 Time: 2s
************* Final Upgrade scripts ************
Serial Phase #:98 [MIG19C] Files:1 Time: 24s
******************* Migration ******************
Serial Phase #:99 [MIG19C] Files:1 Time: 48s
*** End PDB Application Upgrade Pre-Shutdown ***
Serial Phase #:100 [MIG19C] Files:1 Time: 1s
Serial Phase #:101 [MIG19C] Files:1 Time: 0s
Serial Phase #:102 [MIG19C] Files:1 Time: 44s
***************** Post Upgrade *****************
Serial Phase #:103 [MIG19C] Files:1 Time: 38s
**************** Summary report ****************
Serial Phase #:104 [MIG19C] Files:1 Time: 2s
*** End PDB Application Upgrade Post-Shutdown **
Serial Phase #:105 [MIG19C] Files:1 Time: 0s
Serial Phase #:106 [MIG19C] Files:1 Time: 0s
Serial Phase #:107 [MIG19C] Files:1 Time: 32s

------------------------------------------------------
Phases [0-107] End Time:[2019_03_21 22:25:49]
------------------------------------------------------

Grand Total Time: 2320s

LOG FILES: (/u01/app/oracle/product/19.0.0/dbhome_1/cfgtoollogs/MIG19C/upgrade20190321214709/catupgrd*.log)

Upgrade Summary Report Located in:
/u01/app/oracle/product/19.0.0/dbhome_1/cfgtoollogs/MIG19C/upgrade20190321214709/upg_summary.log

Grand Total Upgrade Time: [0d:0h:38m:40s]

Startup database after upgrade completed.

SQL> startup
ORACLE instance started.

Total System Global Area 1543500136 bytes
Fixed Size                  8896872 bytes
Variable Size             939524096 bytes
Database Buffers          587202560 bytes
Redo Buffers                7876608 bytes
Database mounted.
Database opened.

SQL> @catuppst.sql

Session altered.


Session altered.


Session altered.


PL/SQL procedure successfully completed.


Session altered.


System altered.


PL/SQL procedure successfully completed.


Session altered.


TIMESTAMP
--------------------------------------------------------------------------------
COMP_TIMESTAMP DBRESTART 2019-03-21 23:05:38
DBUA_TIMESTAMP DBRESTART FINISHED 2019-03-21 23:05:38
DBUA_TIMESTAMP DBRESTART NONE 2019-03-21 23:05:38

TIMESTAMP
--------------------------------------------------------------------------------
DBUA_TIMESTAMP CATUPPST STARTED 2019-03-21 23:05:38


TIMESTAMP
--------------------------------------------------------------------------------
COMP_TIMESTAMP POSTUP_BGN 2019-03-21 23:05:38
DBUA_TIMESTAMP POSTUP_BGN FINISHED 2019-03-21 23:05:38
DBUA_TIMESTAMP POSTUP_BGN NONE 2019-03-21 23:05:38

TIMESTAMP
--------------------------------------------------------------------------------
COMP_TIMESTAMP CATREQ_BGN 2019-03-21 23:05:38
DBUA_TIMESTAMP CATREQ_BGN FINISHED 2019-03-21 23:05:38
DBUA_TIMESTAMP CATREQ_BGN NONE 2019-03-21 23:05:38

PL/SQL procedure successfully completed.

catrequtlmg: b_StatEvt = TRUE
catrequtlmg: b_SelProps = FALSE
catrequtlmg: b_UpgradeMode = FALSE
catrequtlmg: b_InUtlMig = FALSE

PL/SQL procedure successfully completed.


PL/SQL procedure successfully completed.


TIMESTAMP
--------------------------------------------------------------------------------
COMP_TIMESTAMP CATREQ_END 2019-03-21 23:05:39
DBUA_TIMESTAMP CATREQ_END FINISHED 2019-03-21 23:05:39
DBUA_TIMESTAMP CATREQ_END NONE 2019-03-21 23:05:39


catuppst: Dropping library DBMS_DDL_INTERNAL_LIB

PL/SQL procedure successfully completed.

catuppst: Dropping view _CURRENT_EDITION_OBJ_MIG

PL/SQL procedure successfully completed.

catuppst: Dropping view _ACTUAL_EDITION_OBJ_MIG

PL/SQL procedure successfully completed.

catuppst: Dropping view DBA_PART_KEY_COLUMNS_V$_MIG

PL/SQL procedure successfully completed.

catuppst: Dropping view DBA_SUBPART_KEY_COLUMNS_V$_MIG

PL/SQL procedure successfully completed.

catuppst: Dropping table OBJ$MIG
catuppst: Dropping table USER$MIG
catuppst: Dropping table COL$MIG
catuppst: Dropping table CLU$MIG
catuppst: Dropping table CON$MIG
catuppst: Dropping table BOOTSTRAP$MIG
catuppst: Dropping table TAB$MIG
catuppst: Dropping table TS$MIG
catuppst: Dropping table IND$MIG
catuppst: Dropping table ICOL$MIG
catuppst: Dropping table LOB$MIG
catuppst: Dropping table COLTYPE$MIG
catuppst: Dropping table SUBCOLTYPE$MIG
catuppst: Dropping table NTAB$MIG
catuppst: Dropping table REFCON$MIG
catuppst: Dropping table OPQTYPE$MIG
catuppst: Dropping table ICOLDEP$MIG
catuppst: Dropping table VIEWTRCOL$MIG
catuppst: Dropping table ATTRCOL$MIG
catuppst: Dropping table TYPE_MISC$MIG
catuppst: Dropping table LIBRARY$MIG
catuppst: Dropping table ASSEMBLY$MIG
catuppst: Dropping table TSQ$MIG
catuppst: Dropping table FET$MIG

PL/SQL procedure successfully completed.


PL/SQL procedure successfully completed.


PL/SQL procedure successfully completed.


TIMESTAMP
--------------------------------------------------------------------------------
COMP_TIMESTAMP POSTUP_END 2019-03-21 23:05:39
DBUA_TIMESTAMP POSTUP_END FINISHED 2019-03-21 23:05:39
DBUA_TIMESTAMP POSTUP_END NONE 2019-03-21 23:05:39

TIMESTAMP
--------------------------------------------------------------------------------
COMP_TIMESTAMP CATUPPST 2019-03-21 23:05:39
DBUA_TIMESTAMP CATUPPST FINISHED 2019-03-21 23:05:39
DBUA_TIMESTAMP CATUPPST NONE 2019-03-21 23:05:39

Session altered.

Compile Invalid objects :

SQL> @utlrp.sql

Session altered.


TIMESTAMP
--------------------------------------------------------------------------------
COMP_TIMESTAMP UTLRP_BGN 2019-03-21 23:07:30

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>
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>
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>
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>
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>
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>
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_%';
DOC>#

PL/SQL procedure successfully completed.


TIMESTAMP
--------------------------------------------------------------------------------
COMP_TIMESTAMP UTLRP_END 2019-03-21 23:18:13

DOC> The following query reports the number of invalid objects.
DOC>
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.
DOC>#

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.
DOC>#

ERRORS DURING RECOMPILATION
---------------------------
0


Function created.


PL/SQL procedure successfully completed.


Function dropped.


PL/SQL procedure successfully completed.

SQL> select count(*) from dba_objects where status='INVALID';

COUNT(*)
----------
0

Set COMPATIBLE parameter :

SQL> show parameter compatible;

NAME              TYPE    VALUE
----------------- -------- ---------
compatible        string  11.2.0.4.0
noncdb_compatible boolean FALSE


SQL> ALTER SYSTEM SET COMPATIBLE = '19.0.0' SCOPE=SPFILE;

System altered.

Restart the database :

SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.

Total System Global Area 2516580184 bytes
Fixed Size 8660824 bytes
Variable Size 671088640 bytes
Database Buffers 1828716544 bytes
Redo Buffers 8114176 bytes
Database mounted.
Database opened.
SQL> show parameter compatible;

NAME              TYPE     VALUE
----------------- -------- ---------
compatible        string   19.0.0
noncdb_compatible boolean  FALSE

Compile Fixed objects stats :

SQL> EXECUTE DBMS_STATS.GATHER_FIXED_OBJECTS_STATS;

PL/SQL procedure successfully completed.

Post-Upgrade Steps :-

Upgrade Time Zone version :

Startup database in Upgrade mode.

SQL> startup upgrade
ORACLE instance started.

Total System Global Area 1543500136 bytes
Fixed Size 8896872 bytes
Variable Size 1040187392 bytes
Database Buffers 486539264 bytes
Redo Buffers 7876608 bytes
Database mounted.
Database opened.

SQL> SET SERVEROUTPUT ON
DECLARE
l_tz_version PLS_INTEGER;
BEGIN
l_tz_version := DBMS_DST.get_latest_timezone_version;

DBMS_OUTPUT.put_line('l_tz_version=' || l_tz_version);
DBMS_DST.begin_upgrade(l_tz_version);
END;
/SQL> 2 3 4 5 6 7 8 9
l_tz_version=32
An upgrade window has been successfully started.

PL/SQL procedure successfully completed.

Shutdown and startup in normal mode :

SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.


SQL> startup
ORACLE instance started.

Total System Global Area 1543500136 bytes
Fixed Size 8896872 bytes
Variable Size 1040187392 bytes
Database Buffers 486539264 bytes
Redo Buffers 7876608 bytes
Database mounted.
Database opened.


SQL> SET SERVEROUTPUT ON
DECLARE
l_failures PLS_INTEGER;
BEGIN
DBMS_DST.upgrade_database(l_failures);
DBMS_OUTPUT.put_line('DBMS_DST.upgrade_database : l_failures=' || l_failures);
DBMS_DST.end_upgrade(l_failures);
DBMS_OUTPUT.put_line('DBMS_DST.end_upgrade : l_failures=' || l_failures);
END;
/SQL> 2 3 4 5 6 7 8 9
Table list: "MDSYS"."SDO_DIAG_MESSAGES_TABLE"
Number of failures: 0
Table list: "GSMADMIN_INTERNAL"."AQ$_CHANGE_LOG_QUEUE_TABLE_S"
Number of failures: 0
Table list: "GSMADMIN_INTERNAL"."AQ$_CHANGE_LOG_QUEUE_TABLE_L"
Number of failures: 0
DBMS_DST.upgrade_database : l_failures=0
An upgrade window has been successfully ended.
DBMS_DST.end_upgrade : l_failures=0

PL/SQL procedure successfully completed.

Check Time zone version :

SQL> SELECT * FROM v$timezone_file;

FILENAME             VERSION    CON_ID
-------------------- ---------- ----------
timezlrg_32.dat      32         0

SQL>COLUMN property_name FORMAT A30
COLUMN property_value FORMAT A20

SELECT property_name, property_value
FROM database_properties
WHERE property_name LIKE 'DST_%'
ORDER BY property_name;SQL> SQL> SQL> SQL> 2 3 4

PROPERTY_NAME              PROPERTY_VALUE
-------------------------- ---------------
DST_PRIMARY_TT_VERSION     32
DST_SECONDARY_TT_VERSION   0
DST_UPGRADE_STATE          NONE

Run postupgrade fixups :

SQL> @/u01/preupgrade/postupgrade_fixups.sql

Session altered.

PL/SQL procedure successfully completed.

PL/SQL procedure successfully completed.

PL/SQL procedure successfully completed.

Package created.

No errors.

Package body created.

PL/SQL procedure successfully completed.

No errors.

Package created.

No errors.

Package body created.

No errors.
Executing Oracle POST-Upgrade Fixup Script

Auto-Generated by: Oracle Preupgrade Script
Version: 19.0.0.0.0 Build: 1
Generated on: 2019-03-21 21:12:30

For Source Database: MIG19C
Source Database Version: 11.2.0.4.0
For Upgrade to Version: 19.0.0.0.0

Preup                        Preupgrade
Action                       Issue Is 
Number Preupgrade Check Name Remedied      Further DBA Action
------ ------------------------ ---------- ----------------------------
11. old_time_zones_exist YES None.
12. dir_symlinks YES None.
13. post_dictionary YES None.
14. post_fixed_objects NO Informational only.
Further action is optional.
15. upg_by_std_upgrd NO Informational only.
Further action is optional.

The fixup scripts have been run and resolved what they can. However,
there are still issues originally identified by the preupgrade that
have not been remedied and are still present in the database.
Depending on the severity of the specific issue, and the nature of
the issue itself, that could mean that your database upgrade is not
fully complete. To resolve the outstanding issues, start by reviewing
the postupgrade_fixups.sql and searching it for the name of
the failed CHECK NAME or Preupgrade Action Number listed above.
There you will find the original corresponding diagnostic message
from the preupgrade which explains in more detail what still needs
to be done.

PL/SQL procedure successfully completed.

Session altered.

Check database name and version :

SQL> select name,version,open_mode from v$database,v$instance;

NAME      VERSION           OPEN_MODE
--------- ----------------- ----------
MIG19C    19.0.0.0.0        READ WRITE

Catch Me On:- Hariprasath Rajaram

LinkedIn:https://www.linkedin.com/in/hari-prasath-aa65bb19/
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/hariprasathdba

Step By Step install Oracle 19cR2 Database on OEL 7.6 (64-Bit)

Basic Installation

Boot from the DVD. Use the up arrow to pick the “Install Oracle Linux 7.0” option and hit the return key.
Select the appropriate language and select the “Set keyboard to default layout for selected language” option, then click the “Continue” button.

Click the “I want to proceed.” button on the pre release software warning screen.

You are presented with the “Installation Summary” screen. You must complete any marked items before you can continue with the installation. Depending on your requirements, you may also want to alter the default settings by clicking on the relevant links.

Click the “Installation Destination” link.
If you are happy to use automatic partitioning of the whole disk, click the “Done” button to return to the previous screen.

If you want to modify the partitioning configuration, click the “Continue” button and work through the partitioning screens.
It would be advisable to click on the “Software Selection” link and pick the following options if you want a GUI console.
- Base Environment > Server with GUI
- Add-ons for Selected Environment > Compatibility Libraries
- Add-ons for Selected Environment > Development Tools
Once you have completed your selections, click the “Done” button.
Once you have completed your alterations to the default configuration, click the “Begin Installation” button.
Click the “Root Password” link.

Enter the root password and click the “Done” button.

Click the “User Creation” link.
Enter the user details and select the “Make this user administrator” option, then click the “Done” button.

Wait for the installation to complete. When prompted, click the “Reboot” button.

Click the “License Information” link. Check the “I accept the license agreement” checkbox and click the “Done” button. When you return to the previous screen, click the “Finish Configuration” button.

Decide if you want to use Kdump and click the “Forward” button.

Decide if you want to set up software updates and click the “Forward” button. If you chose not to register with ULN, you will need to confirm you decision also.

Click the “Forward” button.

On the sign-in screen, click on the user you want to log in as
Enter the password and click the “Sign In” button.
Accept the language by clicking the “Next” button.
Accept the input sources by clicking the “Next” button.
Click the “Start using Oracle Linux Server” button.
Install Vmware tools to do some internal works.

While installing Oracle 19c binaries on OEL 7.6. First, we need to download the software then unzip it on oracle home and start runInstaller from the software location.
Select a “Set Up Software Only” and click next.
Select on “Single instance database Installation” and click on next.
Select on “Enterprise Edition” and click on next .
Put the Oracle Base and click on next
Put the “Inventory Directory” and click on next
Select appropriate group and click on next

Provide the root password if you want to run the scripts automatically.
Check the prerequisite for installation
Review the summary page and click on install
After Installation progress completed.
To complete the installation on click on close.

Load bash profile then run dbca

Log in as the Oracle software owner.
Go to a command prompt.
Type dbca.
You see a splash screen and another screen with options

Select Create a Database option to create a new Db

Select the Create a Database option.

You are presented with the option of using a default configuration or an advanced one.
If you Select the Advanced option.
Click Next.

You’ll see output. Optional database templates are shown:

General Purpose
Data Warehouse
Custom Database

As i selected the Typical configuration provide Location of Datafile and FRA then provide password

Set the Oracle Home and connect to Sqlplus

we are successfully completed binary installation and Database installation of Oracle 19c

Catch Me On:- Hariprasath Rajaram 

Telegram:https://t.me/joinchat/I_f4DkeGfZuxgMIoJSpQZg 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/hariprasathdba

Step by Step Oracle TimesTen In-Memory Database Installation On Linux

In this article, we will see the step by step installation of Oracle TimesTen In-Memory Database 11.2.2 and TimesTen Applications Database Cache 11.2.2 on RHEL 6.8.

Download the Oracle TimesTen Database Software from here.

Create an operating system group for the TimesTen instance administrators
group.

Create ttadmin group:-

$ /usr/sbin/groupadd -g 54331 ttadmin

Create /etc/TimesTen directory:-

$ mkdir /etc/TimesTen

Assign ownship permission to group ttadmin to directory /etc/TimesTen:-

$ chgrp -R ttadmin /etc/TimesTen
$ chmod -R 775 /etc/TimesTen
$ ls -ltrhd /etc/TimesTen/ls -ltrhd /etc/TimesTen/
drwxrwxr-x. 2 root ttadmin 4.0K Dec 23 13:21 /etc/TimesTen/

Create user oratta with group ttadmin:-

$ /usr/sbin/useradd -u 54331 -g ttadmin oratta
$ id oratta
uid=54331(oratta) gid=54331(ttadmin) groups=54331(ttadmin)

Create and change ownership to the directories to oratta as owner and group ttadmin:-

$ mkdir -p /oradb/app/oratta/TimesTen
$ chown -R oratta:ttadmin /oradb/app/oratta

$ su – oratta
$ unzip the TimesTen software
$ tar -zxvf timesten112280.linux8664.tar.gz
$ cd linux8664
$ ./setup.sh

NOTE: Each TimesTen installation is identified by a unique instance name.
The instance name must be a non-null alphanumeric string, not longer
than 255 characters.

Please choose an instance name for this installation? [ tt1122 ]
Instance name will be ‘tt1122’.
Is this correct? [ yes ]

Of the three components:

[1] Client/Server and Data Manager
[2] Data Manager Only
[3] Client Only

Which would you like to install? [ 1 ]

Of the following options :

[1] /home/oratta
[2] /mnt/hgfs/shared/Softwares/oracle/Timesten
[3] Specify a location
[q] Quit the installation

Where would you like to install the tt1122 instance of TimesTen? [ 1 ] 3
Please specify a directory to install TimesTen? [ /home/oratta ] /oradb/app/oratta/TimesTen
Where would you like to create the daemon home directory? [ /oradb/app/oratta/TimesTen/tt1122/info ]

The daemon logs will be located in /oradb/app/oratta/TimesTen/tt1122/info
Would you like to specify a different location for the daemon logs? [ no ]
Installing into /oradb/app/oratta/TimesTen/tt1122 …
Uncompressing …

NOTE: If you are configuring TimesTen for use with Oracle Clusterware, the
daemon port number must be the same across all TimesTen installations
managed within the same Oracle Clusterware cluster.

NOTE: All installations that replicate to each other must use the same daemon
port number that is set at installation time. The daemon port number can
be verified by running ‘ttVersion’.

The default port number is 53396.

Do you want to use the default port number for the TimesTen daemon? [ yes ]
The daemon will run on the default port number (53396).

NOTE: For security, we recommend that you restrict access to the
TimesTen installation to members of a single OS group. Only members of
that OS group will be allowed to perform direct mode connections to
TimesTen, and only members of that OS group will be allowed to perform
operations that access TimesTen data stores, TimesTen files and shared
memory. The OS group defaults to the primary group of the instance
administrator. You can default to this group, choose another OS group
or you can make this instance world-accessible. If you choose to make
this instance world-accessible, all database files and shared memory
are readable and writable by all users.

Restrict access to the the TimesTen installation to the group ‘ttadmin’? [ yes ]

NOTE: Enabling PL/SQL will increase the size of some TimesTen libraries.

Would you like to enable PL/SQL for this instance? [ yes ]

In order to use the ‘Oracle TimesTen Application-Tier Database Cache’ feature in any databases
created within this installation, you must set a value for the TNS_ADMIN
environment variable. It can be left blank, and a value can be supplied later
using <install_dir>/bin/ttModInstall.

Please enter a value for TNS_ADMIN (s=skip)? [ ] /oradb/app/oracle/product/11.2.0.4/db_1/network/admin

TNS_ADMIN will be set to /oradb/app/oracle/product/11.2.0.4/db_1/network/admin
You can change TNS_ADMIN later by running <install_dir>/bin/ttmodinstall.

NOTE: It appears that you are running version 4 or higher of the g++
compiler. TimesTen ships with multiple sets of client libraries and server
binaries : one built for compatibility with g++ 3.4.6 and one with
g++ 4.1.0. The installer has created links to the 4.1.0 library in the
<install_dir>/lib directory and to the 4.1.0 server binary in the
<install_dir>/bin directory. If you want to use a different compiler,
please modify the links to point to the desired library and server binary.

Installing server components …
What is the TCP/IP port number that you want the TimesTen Server to listen on? [ 53397 ]
Do you want to install the Quick Start Sample Programs and the TimesTen Documentation? [ no ] yes
Where would you like to install the Quick Start and doc directories (s=skip)? [ /oradb/app/oratta/TimesTen/tt1122 ]
The TimesTen documentation has been installed in /oradb/app/oratta/TimesTen/tt1122.

The TimesTen Quick Start applications can take up to 64 Mbytes of disk space.
Depending on how your system is configured, you may not want to create the
Quick Start DemoDataStore directory in the default location,
/oradb/app/oratta/TimesTen/tt1122/info/DemoDataStore

Where would you like to create the DemoDataStore directory? [ /oradb/app/oratta/TimesTen/tt1122/info ]
Creating /oradb/app/oratta/TimesTen/tt1122/info/DemoDataStore …

Installing client components …

Would you like to use TimesTen Replication with Oracle Clusterware? [ no ]

NOTE: The TimesTen daemon startup/shutdown scripts have not been installed.

Run the ‘setuproot’ script :
$ cd /oradb/app/oratta/TimesTen/tt1122/bin
$ ./setuproot -install
This will move the TimesTen startup script into its appropriate location.

The startup script is currently located here :
‘/oradb/app/oratta/TimesTen/tt1122/startup/tt_tt1122’.

The Quickstart home page can be accessed here :
‘/oradb/app/oratta/TimesTen/tt1122/quickstart/index.html’

The 11.2.2.8 Release Notes are located here :
‘/oradb/app/oratta/TimesTen/tt1122/README.html’

Starting the daemon …
TimesTen Daemon startup OK.
End of TimesTen installation.

Set the Timeten Environment like below:-

$ cd /oradb/app/oratta/TimesTen/tt1122/bin
$ . ttenv.sh

LD_LIBRARY_PATH set to /oradb/app/oratta/TimesTen/tt1122/lib:/oradb/app/oratta/TimesTen/tt1122/ttoracle_home/instantclient_11_2

PATH set to /oradb/app/oratta/TimesTen/tt1122/bin:/oradb/app/oratta/TimesTen/tt1122/quickstart/sample_code/oci:/oradb/app/oratta/TimesTen/tt1122/quickstart/sample_code/odbc:/oradb/app/oratta/TimesTen/tt1122/quickstart/sample_code/odbc/xla:/oradb/app/oratta/TimesTen/tt1122/quickstart/sample_code/jdbc:/oradb/app/oratta/TimesTen/tt1122/quickstart/sample_code/odbc_drivermgr:/oradb/app/oratta/TimesTen/tt1122/quickstart/sample_code/proc:/oradb/app/oratta/TimesTen/tt1122/quickstart/sample_code/ttclasses:/oradb/app/oratta/TimesTen/tt1122/quickstart/sample_code/ttclasses/xla:/oradb/app/oratta/TimesTen/tt1122/ttoracle_home/instantclient_11_2:/oradb/app/oratta/TimesTen/tt1122/ttoracle_home/instantclient_11_2/sdk:/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/oratta/bin

CLASSPATH set to /oradb/app/oratta/TimesTen/tt1122/lib/ttjdbc6.jar:/oradb/app/oratta/TimesTen/tt1122/lib/orai18n.jar:/oradb/app/oratta/TimesTen/tt1122/lib/timestenjmsxla.jar:/oradb/app/oratta/TimesTen/tt1122/3rdparty/jms1.1/lib/jms.jar:.

TNS_ADMIN set to /oradb/app/oracle/product/11.2.0.4/db_1/network/admin

Verify the version:-

$ ttversion
TimesTen Release 11.2.2.8.0 (64 bit Linux/x86_64) (tt1122:53396) 2015-01-20T08:36:31Z
Instance admin: oratta
Instance home directory: /oradb/app/oratta/TimesTen/tt1122
Group owner: ttadmin
Daemon home directory: /oradb/app/oratta/TimesTen/tt1122/info
PL/SQL enabled.

$ ttstatus
TimesTen status report as of Sun Dec 23 14:10:09 2018

Daemon pid 16248 port 53396 instance tt1122
TimesTen server pid 16257 started on port 53397
————————————————————————
Accessible by group ttadmin
End of report

Catch Me On:- Hariprasath Rajaram

Telegram:https://t.me/joinchat/I_f4DhGF_Zifr9YZvvMkRg
LinkedIn:https://www.linkedin.com/in/hari-prasath-aa65bb19/
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/hariprasathdba

Oracle 19c Database Upgrade From 12.2.0.1 to 19.2.0.0 Using DBUA

Description:-

There are different ways of upgrading to the latest release of Oracle database and Oracle provides multiple methods to upgrade. Few are listed below:

Database Upgrade Assistant (DBUA)
Manual Upgrade
Transportable Tablespaces
Data Pump export/import
Oracle Streams
Oracle GoldenGate

Here I am going to choose DBUA to upgrade my database,

[oracle@standby dbs]$ export ORACLE_SID=upgr
[oracle@standby dbs]$ sqlplus / as sysdba

SQL*Plus: Release 12.2.0.1.0 Production on Thu Mar 21 20:02:00 2019

Copyright (c) 1982, 2016, Oracle. All rights reserved.

Connected to an idle instance.

SQL> startup
ORACLE instance started.

Total System Global Area 2449473536 bytes
Fixed Size 8623640 bytes
Variable Size 654313960 bytes
Database Buffers 1778384896 bytes
Redo Buffers 8151040 bytes
Database mounted.
Database opened.

Ensure backup is complete before upgrade.

Empty Recycle bin.

Run Gather statistics to finish upgrade soon.

SQL> SELECT * FROM v$backup WHERE status != 'NOT ACTIVE';

no rows selected


SQL> PURGE DBA_RECYCLEBIN ;

DBA_Recyclebin purged.


SQL> EXEC DBMS_STATS.GATHER_DICTIONARY_STATS;

PL/SQL procedure successfully completed.


SQL> !

Stop the running 12c listener

lsnrctl stop LISTENER

Run preupgrade tool and fixups

Oracle strongly recommends that you run the Pre-Upgrade Information Tool before starting the upgrade with DBUA. Although DBUA runs the Pre-Upgrade Information Tool as part of the pre-requisite checks, it is good practice to run the tool ahead of time in order to analyze the database and take actions that can decrease downtime for upgrading.

Connect to 12.2.0.1 database environment as SYS,

Pre-upgrade checks :

Run the preupgrade tool .

[oracle@standby dbs]$ java -jar /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/preupgrade.jar TEXT TERMINAL
Report generated by Oracle Database Pre-Upgrade Information Tool Version
19.0.0.0.0 Build: 1 on 2019-03-21T20:07:45

Upgrade-To version: 19.0.0.0.0

=======================================
Status of the database prior to upgrade
=======================================
Database Name:      UPGR
Container Name:     upgr
Container ID:       0
Version:            12.2.0.1.0
DB Patch Level:     No Patch Bundle applied
Compatible:         12.2.0
Blocksize:          8192
Platform:           Linux x86 64-bit
Timezone File:      26
Database log mode:  NOARCHIVELOG
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
Real Application Clusters        [to be upgraded]         OPTION OFF
Oracle Workspace Manager         [to be upgraded]         VALID
OLAP Analytic Workspace          [to be upgraded]         VALID
Oracle Label Security            [to be upgraded]         VALID
Oracle Database Vault            [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
Oracle OLAP API                  [to be upgraded]         VALID

==============
BEFORE UPGRADE
==============

REQUIRED ACTIONS
================
None

RECOMMENDED ACTIONS
===================
1. (AUTOFIXUP) Gather statistics on fixed objects prior the upgrade.

None of the fixed object tables have had stats collected.

Gathering statistics on fixed objects, if none have been gathered yet, is
recommended prior to upgrading.

For information on managing optimizer statistics, refer to the 12.2.0.1
Oracle Database SQL Tuning Guide.

INFORMATION ONLY
================
2. To help you keep track of your tablespace allocations, the following
AUTOEXTEND tablespaces are expected to successfully EXTEND during the
upgrade process.

Min Size
Tablespace      Size      For Upgrade
----------   ----------  -----------
SYSAUX         490 MB     509 MB
SYSTEM         800 MB     914 MB
TEMP           131 MB     150 MB
UNDOTBS1       70 MB      439 MB

Minimum tablespace sizes for upgrade are estimates.

3. Check the Oracle Backup and Recovery User's Guide for information on how
to manage an RMAN recovery catalog schema.

If you are using a version of the recovery catalog schema that is older
than that required by the RMAN client version, then you must upgrade the
catalog schema.

It is good practice to have the catalog schema the same or higher version
than the RMAN client version you are using.

ORACLE GENERATED FIXUP SCRIPT
=============================
All of the issues in database UPGR
which are identified above as BEFORE UPGRADE "(AUTOFIXUP)" can be resolved by
executing the following

SQL>@/u01/app/oracle/cfgtoollogs/upgr/preupgrade/preupgrade_fixups.sql

=============
AFTER UPGRADE
=============

REQUIRED ACTIONS
================
None

RECOMMENDED ACTIONS
===================
4. Upgrade the database time zone file using the DBMS_DST package.

The database is using time zone file version 26 and the target 19 release
ships with time zone file version 32.

Oracle recommends upgrading to the desired (latest) version of the time
zone file. For more information, refer to "Upgrading the Time Zone File
and Timestamp with Time Zone Data" in the 19 Oracle Database
Globalization Support Guide.

5. To identify directory objects with symbolic links in the path name, run
$ORACLE_HOME/rdbms/admin/utldirsymlink.sql AS SYSDBA after upgrade.
Recreate any directory objects listed, using path names that contain no
symbolic links.

Some directory object path names may currently contain symbolic links.

Starting in Release 18c, symbolic links are not allowed in directory
object path names used with BFILE data types, the UTL_FILE package, or
external tables.

6. (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.

7. Gather statistics on fixed objects after the upgrade and when there is a
representative workload on the system 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.

For information on managing optimizer statistics, refer to the 12.2.0.1
Oracle Database SQL Tuning Guide.

ORACLE GENERATED FIXUP SCRIPT
=============================
All of the issues in database UPGR
which are identified above as AFTER UPGRADE "(AUTOFIXUP)" can be resolved by
executing the following

SQL>@/u01/app/oracle/cfgtoollogs/upgr/preupgrade/postupgrade_fixups.sql


==================
PREUPGRADE SUMMARY
==================
/u01/app/oracle/cfgtoollogs/upgr/preupgrade/preupgrade.log
/u01/app/oracle/cfgtoollogs/upgr/preupgrade/preupgrade_fixups.sql
/u01/app/oracle/cfgtoollogs/upgr/preupgrade/postupgrade_fixups.sql

Execute fixup scripts as indicated below:

Before upgrade:

Log into the database and execute the preupgrade fixups
@/u01/app/oracle/cfgtoollogs/upgr/preupgrade/preupgrade_fixups.sql

After the upgrade:

Log into the database and execute the postupgrade fixups
@/u01/app/oracle/cfgtoollogs/upgr/preupgrade/postupgrade_fixups.sql

Preupgrade complete: 2019-03-21T20:07:46

Run the preupgrade_fixup.sql

[oracle@standby dbs]$ !sq
sqlplus / as sysdba

SQL*Plus: Release 12.2.0.1.0 Production on Thu Mar 21 20:13:03 2019

Copyright (c) 1982, 2016, Oracle. All rights reserved.


Connected to:
Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production

SQL> @/u01/app/oracle/cfgtoollogs/upgr/preupgrade/preupgrade_fixups.sql
Executing Oracle PRE-Upgrade Fixup Script

Auto-Generated by: Oracle Preupgrade Script
Version: 19.0.0.0.0 Build: 1
Generated on: 2019-03-21 20:07:39

For Source Database: UPGR
Source Database Version: 12.2.0.1.0
For Upgrade to Version: 19.0.0.0.0

Preup                            Preupgrade
Action                           Issue Is
Number   Preupgrade Check Name   Remedied      Further DBA Action
------ ------------------------  ----------   -------------------------
1.      pre_fixed_objects        YES            None.
2.      tablespaces_info         NO             Informational only.
                                            Further action is optional.
3.      rman_recovery_version    NO             Informational only.
                                            Further action is optional.

The fixup scripts have been run and resolved what they can. However,
there are still issues originally identified by the preupgrade that
have not been remedied and are still present in the database.
Depending on the severity of the specific issue, and the nature of
the issue itself, that could mean that your database is not ready
for upgrade. To resolve the outstanding issues, start by reviewing
the preupgrade_fixups.sql and searching it for the name of
the failed CHECK NAME or Preupgrade Action Number listed above.
There you will find the original corresponding diagnostic message
from the preupgrade which explains in more detail what still needs
to be done.

PL/SQL procedure successfully completed.

UPGRADE:

At this stage, we are still connected to 12c database which is up and running.

Now run the dbua utility from 12c oracle_home location.

[oracle@standby ~]$ export ORACLE_HOME=/u01/app/oracle/product/19.0.0/dbhome_1
[oracle@standby ~]$ export ORACLE_SID=upgr
[oracle@standby ~]$ export PATH=$ORACLE_HOME/bin:$PATH
[oracle@standby ~]$ dbua

DBUA performs some of the checks before actually starting the database upgrade. Some of the checks can be done manually to reduce downtime for the upgrade.

DBUA provides below options:

– Upgrade timezone.

– Gather dictionary statistics before upgrade.

– Make user tablespaces read only.

– Take RMAN backup before upgrade.

– Create Restore Point for Database Flashback

– Restore database backup to rollback upgrade

– Option to execute Custom scripts before and after upgrade

– show the location of DBUA logs and Alert log files.

– Option to upgrade existing listener to 18.x home or create a new listener in 18.x target home.

select the Upgrade Oracle Database option, then click the “Next” button.

If the prerequisite checks highlight any issues, take the appropriate action to fix the issues. If all the prerequisite checks are passed, click the “Next” button.

Amend the upgrade options if necessary, then click the “Next” button.

Select the recovery options for use in the event of an upgrade failure, then click the “Next” button.

Select the desired management options, then click the “Next” button

Post-upgrade checks:

Run “postupgrade_fixups.sql” to check post upgrade status.

SQL> @/u01/app/oracle/cfgtoollogs/upgr/preupgrade/postupgrade_fixups.sql

Session altered.


PL/SQL procedure successfully completed.


PL/SQL procedure successfully completed.


PL/SQL procedure successfully completed.


Package created.

No errors.

Package body created.


PL/SQL procedure successfully completed.

No errors.

Package created.

No errors.

Package body created.

No errors.
Executing Oracle POST-Upgrade Fixup Script

Auto-Generated by: Oracle Preupgrade Script
Version: 19.0.0.0.0 Build: 1
Generated on: 2019-03-21 20:07:45

For Source Database: UPGR
Source Database Version: 12.2.0.1.0
For Upgrade to Version: 19.0.0.0.0

Preup                            Preupgrade
Action                           Issue Is
Number Preupgrade Check Name     Remedied      Further DBA Action
------ ------------------------ ---------- ----------------------------
4.     old_time_zones_exist     YES                None.
5.     dir_symlinks             YES                None.
6.     post_dictionary          YES                None.
7.     post_fixed_objects       NO              Informational only.
                                            Further action is optional.

The fixup scripts have been run and resolved what they can. However,
there are still issues originally identified by the preupgrade that
have not been remedied and are still present in the database.
Depending on the severity of the specific issue, and the nature of
the issue itself, that could mean that your database upgrade is not
fully complete. To resolve the outstanding issues, start by reviewing
the postupgrade_fixups.sql and searching it for the name of
the failed CHECK NAME or Preupgrade Action Number listed above.
There you will find the original corresponding diagnostic message
from the preupgrade which explains in more detail what still needs
to be done.

PL/SQL procedure successfully completed.


Session altered.

Now the database upgrade is complete and the database is ready for normal use.

SQL> select VERSION,name,open_mode from v$instance,v$database;

VERSION            NAME        OPEN_MODE
----------------- --------- --------------------
19.0.0.0.0         UPGR        READ WRITE

SQL> SELECT * FROM v$timezone_file;

FILENAME              VERSION    CON_ID
-------------------- ---------- ----------
timezlrg_32.dat        32         0

SQL> select TZ_VERSION from registry$database;

TZ_VERSION
----------
   32

Catch Me On:- Hariprasath Rajaram 

Telegram:https://t.me/joinchat/I_f4DkeGfZuxgMIoJSpQZg 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/hariprasathdba

Support Freshers And Fellow Oracle DBAs Using Social Media

My primary goal for starting the below initiatives are to help my fellow DBAs in Oracle world and make www.oracledbwr.com a one stop solution for Oracle Technologies.

Telegram Group ( More than 2.5K DBA’s in the Group)

https://t.me/joinchat/I_f4DkeGfZvN1z5wyt_f4w

Whatsapp Group:-(Each Group 257 members)

Videos Library

I have uploaded the Performance Tuning,GoldenGate,RAC And Dataguard Videos for the below link to download.

https://mega.nz/#F!d00GTQQb!XKuAkQ6LQo7oi711-0ViiA

Documents Library

I have uploaded the Oracle DBA documents, interview questions and materials

Link to download

https://mega.nz/#F!7m5nlDaL

Encryption key

!gwbONpJRzF_b-H-DtnCxLQ

Social Media sites

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/hariprasathdba
Google+: https://plus.google.com/u/0/+HariPrasathdba

Oracle AIOUG Chennai Chapter -Are You Ready For Oracle Cloud Database Service Part-1

This session is about Are You Ready For Oracle Cloud Database Service Part-1. Below topics will be covered with Live Demo using oracle cloud account.

Introduction to cloud
Creating database Cloud Service
Administering Database Cloud Service
Backing Up and Restoring Databases on Database Cloud Service
Data Guard in Oracle Cloud
Using Oracle DBaaS Monitor
Patching Database Cloud Service
Migrating Oracle Databases to Database Cloud Service

Download the presentation Are You Ready For Living In The Oracle Cloud – 1

Special Thanks To Aioug Chennai Chapter Team

Hariharaputhran Vaithinathan
Harish Panduranga Rao
Justin Michael Raj
Veeratteshwaran Sridhar

Reference:-

All India Oracle Users Group – Chennai Chapter

Chennai, IN
1,835 Oracle Enthusiasts

What is AIOUG?AIOUG is a non profit organization started by like minded users who think such a community is required in India where the amount of Oracle user base is humongou…

Next Meetup

AIOUG Chennai Chapter – Feb 2019 Meetup

Saturday, Feb 23, 2019, 9:15 AM
8 Attending

Check out this Meetup Group →

Oracle AIOUG Chennai Chapter -Oracle 12c Multitenant Database Session

This session is about Oracle 12c Multitenant Database Session. Below topics will be covered with Live Demo using oracle vmbox

Oracle Multitenant Database Architecture
Overview of Multitenant : (CDB) & (PDB)
Multitenant : Create and Configure a (CDB) & (PDB)
Multitenant : Startup and Shutdown (CDB) & (PDB)
Multitenant : Manage Users and Privileges
Multitenant : Cloning pluggable database
Multitenant : Backup and Recovery (CDB) & (PDB)
Multitenant : Migrate a (Non-CDB) to a (PDB)

Download the presentation Oracle Database 12c Multitenant Architecture

Special Thanks To Aioug Chennai Chapter Team

Hariharaputhran Vaithinathan
Harish Panduranga Rao
Justin Michael Raj
Veeratteshwaran Sridhar

Reference:-

All India Oracle Users Group – Chennai Chapter

Chennai, IN
1,835 Oracle Enthusiasts

What is AIOUG?AIOUG is a non profit organization started by like minded users who think such a community is required in India where the amount of Oracle user base is humongou…

Next Meetup

AIOUG Chennai Chapter – Feb 2019 Meetup

Saturday, Feb 23, 2019, 9:15 AM
8 Attending

Check out this Meetup Group →

Oracle AIOUG Chennai Chapter -Database Security Assessment Tool

This session is about Database Security Assessment Tool. Below topics will be covered with Live Demo using oracle vmbox.

Database Security Assessment
DBSAT Overview and Flow
Advantages
How to download, configure and execute
Gather data and preparing reports
Interpreting the report
Summary

Download the presentation DBSAT – Oracle Database Security Assessment Tool

Special Thanks To Aioug Chennai Chapter Team

Hariharaputhran Vaithinathan
Harish Panduranga Rao
Justin Michael Raj
Veeratteshwaran Sridhar

Reference:-

All India Oracle Users Group – Chennai Chapter

Chennai, IN
1,835 Oracle Enthusiasts

What is AIOUG?AIOUG is a non profit organization started by like minded users who think such a community is required in India where the amount of Oracle user base is humongou…

Next Meetup

AIOUG Chennai Chapter – Feb 2019 Meetup

Saturday, Feb 23, 2019, 9:15 AM
8 Attending

Check out this Meetup Group →

Oracle AIOUG Chennai Chapter -Oracle Flashback Deep Dive

This session is about Oracle Flashback Deep Dive. Below topics will be covered with Live Demo using oracle vmbox.

History of Oracle Flashback Technologies
Flashback Architecture Overview
Flashback Technologies Transformation Since V9
Flashback Advanced use cases
Flashback Query
Flashback Table
Flashback Drop
Flashback Versions Query
Flashback Transaction Query
Flashback Query Functions
Flashback Database
Flashback Data Archive
Flashback Pluggable Database (PDB)
Temporal Validity

Download the presentation Oracle Database Flashback12R2

Special Thanks To Aioug Chennai Chapter Team

Hariharaputhran Vaithinathan
Harish Panduranga Rao
Justin Michael Raj
Veeratteshwaran Sridhar

Reference:-

All India Oracle Users Group – Chennai Chapter

Chennai, IN
1,835 Oracle Enthusiasts

What is AIOUG?AIOUG is a non profit organization started by like minded users who think such a community is required in India where the amount of Oracle user base is humongou…

Next Meetup

AIOUG Chennai Chapter – Feb 2019 Meetup

Saturday, Feb 23, 2019, 9:15 AM
8 Attending

Check out this Meetup Group →