11g to 12c database upgrade steps

                                    Upgradation steps


Create directory to place the 12c software
    >Mkdir -p /u02/stage

Copy the 12c files into the stage

Unzip the files in the stage

Run >sh runInstaller

Go to sql and run preupgrade scripts

> @preupgrd.sql

ACTIONS REQUIRED:
1. Review results of the pre-upgrade checks:

 /u01/app/oracle/cfgtoollogs/test/preupgrade/preupgrade.log

2. Execute in the SOURCE environment BEFORE upgrade:

 /u01/app/oracle/cfgtoollogs/test/preupgrade/preupgrade_fixups.sql

3. Execute in the NEW environment AFTER upgrade:

 /u01/app/oracle/cfgtoollogs/test/preupgrade/postupgrade_fixups.sql

RUN PRE UPGRADE FIXUP SCRIPT

SQL> @/u01/app/oracle/cfgtoollogs/test/preupgrade/preupgrade_fixups.sql
Pre-Upgrade Fixup Script Generated on 2017-08-09 12:21:41  Version: 12.1.0.2 Build: 006
Beginning Pre-Upgrade Fixups...
Executing in container TEST

**********************************************************************
Check Tag:     DEFAULT_PROCESS_COUNT
Check Summary: Verify min process count is not too low
Fix Summary:   Review and increase if needed, your PROCESSES value.
**********************************************************************
Fixup Returned Information:
WARNING: --> Process Count may be too low

     Database has a maximum process count of 150 which is lower than the
     default value of 300 for this release.
     You should update your processes value prior to the upgrade
     to a value of at least 300.
     For example:
        ALTER SYSTEM SET PROCESSES=300 SCOPE=SPFILE
     or update your init.ora file.
**********************************************************************


**********************************************************************
Check Tag:     EM_PRESENT
Check Summary: Check if Enterprise Manager is present
Fix Summary:   Execute emremove.sql prior to upgrade.
**********************************************************************
Fixup Returned Information:
WARNING: --> Enterprise Manager Database Control repository found in the database

     In Oracle Database 12c, Database Control is removed during
     the upgrade. To save time during the Upgrade, this action
     can be done prior to upgrading using the following steps after
     copying rdbms/admin/emremove.sql from the new Oracle home
   - Stop EM Database Control:
    $> emctl stop dbconsole

   - 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.
**********************************************************************


**********************************************************************
Check Tag:     AMD_EXISTS
Check Summary: Check to see if AMD is present in the database
Fix Summary:   Manually execute ORACLE_HOME/oraolap/admin/catnoamd.sql script to remove OLAP.
**********************************************************************
Fixup Returned Information:
INFORMATION: --> OLAP Catalog(AMD) exists in database

     Starting with Oracle Database 12c, OLAP Catalog component is desupported.
     If you are not using the OLAP Catalog component and want
     to remove it, then execute the
     ORACLE_HOME/olap/admin/catnoamd.sql script before or
     after the upgrade.
**********************************************************************


**********************************************************************
Check Tag:     APEX_UPGRADE_MSG
Check Summary: Check that APEX will need to be upgraded.
Fix Summary:   Oracle Application Express can be manually upgraded prior to database upgrade.
**********************************************************************
Fixup Returned Information:
INFORMATION: --> Oracle Application Express (APEX) can be
     manually upgraded prior to database upgrade

     APEX is currently at version 3.2.1.00.12 and will need to be
     upgraded to APEX version 4.2.5 in the new release.
     Note 1: To reduce database upgrade time, APEX can be manually
             upgraded outside of and prior to database upgrade.
     Note 2: See MOS Note 1088970.1 for information on APEX
             installation upgrades.
**********************************************************************


**********************************************************************
                      [Pre-Upgrade Recommendations]
**********************************************************************

                        *****************************************
                        ********* Dictionary Statistics *********
                        *****************************************

Please gather dictionary statistics 24 hours prior to
upgrading the database.
To gather dictionary statistics execute the following command
while connected as SYSDBA:
    EXECUTE dbms_stats.gather_dictionary_stats;

^^^ MANUAL ACTION SUGGESTED ^^^


           **************************************************
                ************* Fixup Summary ************

  fixup routines generated INFORMATIONAL messages that should be reviewed.

**************** Pre-Upgrade Fixup Script Complete *********************



5. we have to remove 11g enterprise manager related schemas and tables so, because it won’t support in 12c

SQL> @emremove.sql
old  69:     IF (upper('&LOGGING') = 'VERBOSE')
new  69:     IF (upper('VERBOSE') = 'VERBOSE')
The Oracle Enterprise Manager related schemas and objects are dropped.
Do the manual steps to studown the DB Control if not done before running this script and then delete the DB Control configuration files

6. copy spfile and password file to 12c home/dbs from 11g home/dbs

7.update oratab file with new home location.
 Vi /etc/oratab

8. [oracle@localhost dbs]$ echo $ORACLE_HOME
/u01/app/oracle/product/11.2.0/dbhome_1
[oracle@localhost dbs]$ export ORACLE_HOME=/u01/app/oracle/product/12.1.0/dbhome_1
[oracle@localhost dbs]$ export path=$ORACLE_HOME/bin:$PATH
[oracle@localhost dbs]$ echo $ORACLE_HOME
/u01/app/oracle/product/12.1.0/dbhome_1
[oracle@localhost dbs]$





Note: Down the listener for 11g and shut down the database.


9. start upgrade (start the database in upgrade mode).

$ cd $ORACLE_HOME/rdbms/admin
$ $ORACLE_HOME/perl/bin/perl catctl.pl -n 8 catupgrd.sql



10. sql>@utlu121s.sql
To check the upgrade status 

11. If we had no errors, the "catuppst.sql" script would have been run as part of the upgrade. Since we did have errors, we need to run it manually.

SQL> @catuppst.sql

12.query to check the invalid objects

Sql>Select count(*) from dba_objects where status=’INVALID’;

13.To validate the invalid objects we run utlrp script

Sql>@utlrp.sql


Upgradation is completed. So shut down the database and startup.



Comments

Post a Comment

Popular posts from this blog

Oracle Database Client(12.1.0.2.0) Installation for Microsoft Windows(x64)

Image
Step1) Download Oracle Client 12C from below link http://www.oracle.com/technetwork/database/enterprise-edition/downloads/database12c-win64-download-2297732.html Oracle Database Client (12.1.0.2.0) for Microsoft Windows (x64) winx64_12102_client.zip  (64-bit) (925,039,944 bytes) Oracle Database Client (12.1.0.2.0) for Microsoft Windows (32-bit) winnt_12102_client32.zip  (32-bit) (902,922,170 bytes)  chose the one based on your laptop Step2) Extract the downloaded file Oracle 12c 64 bit client has now been extracted. Double click ‘setup.exe’. This may test your patience, let it work! (Sometimes a minute or less can seem like an eternity). Don’t touch anything! Administrator: Enables applications to connect to an Oracle database on the local system or on a remote system. It provides tools that let you administer
Read more

configuring goldengate

configuring goldengate Pre req:  Install Goldengate software on both the servers golden gate home: /u02/app/goldengate Update bash_profile on both Source and Target side [oracle@localhost ~]$ vi .bash_profile if [ -f ~/.bashrc ]; then         . ~/.bashrc fi # User specific environment and startup programs export ORACLE_SID=test export ORACLE_HOME=/u01/app/oracle/product/12.1.0/dbhome_1 export GRID_HOME=/u01/app/oracle/product/12.1.0/grid export LD_LIBRARY_PATH=$ORACLE_HOME/lib export PATH=$ORACLE_HOME/bin:$PATH: export PATH=$GRID_HOME/bin:$PATH: export PATH=$ORACLE_HOME/OPatch:$PATH: PATH=$PATH:$HOME/bin export PATH export GGS_HOME=/u02/app/goldengate alias ggn='cd ${GGS_HOME}' alias ggsci='cd ${GGS_HOME}/ggsci' export LD_LIBRARY_PATH=$GGS_HOME:$ORACLE_HOME/lib:/lib:/usr/lib ".bash_profile" 25L, 684C                                     24,1          75% Source db_name: TEST target db_name: CLONE 1. check for
Read more

sample extract,pump and replicate(goldengate)

NAMING CONVENTION should be followed in any environment we are Implementing GoldenGate# E starts with Extract  P starts with Pump R starts with Replicat  Here we are taking extract: EWORK pump: PWORK replicat:RWORK ###we are replicating schema pavan(including all tables)### goldengate home:'/u02/app/goldengate' source side:  test GGSCI (localhost.localdomain) 2> start mgr Manager started. GGSCI (localhost.localdomain) 1> dblogin userid ogg_user@test password oracle; Successfully logged into database. GGSCI (localhost.localdomain as ogg_user@test) 2> add schematrandata pavan allcols 2017-10-09 14:22:20  INFO    OGG-01788  SCHEMATRANDATA has been added on schema pavan. 2017-10-09 14:22:20  INFO    OGG-01976  SCHEMATRANDATA for scheduling columns has been added on schema pavan. 2017-10-09 14:22:21  INFO    OGG-01977  SCHEMATRANDATA for all columns has been added on schema pavan. Configuring Extract: GGSCI (local
Read more