This page was exported from - SAP ADMIN
Export date: Mon Mar 17 2:09:53 2014 / +0000 GMT
Step By Step Manual Oracle Databa...
This page was exported from - SAP ADMIN
Export date: Mon Mar 17 2:09:53 2014 / +0000 GMT
If the dbupgdiag.sql script repor...
This page was exported from - SAP ADMIN
Export date: Mon Mar 17 2:09:53 2014 / +0000 GMT
{
ALLOCATE CHANNEL chan_name TYPE...
This page was exported from - SAP ADMIN
Export date: Mon Mar 17 2:09:53 2014 / +0000 GMT
At the operating system prompt, c...
This page was exported from - SAP ADMIN
Export date: Mon Mar 17 2:09:53 2014 / +0000 GMT
17 Crosscheck Environment Variabl...
This page was exported from - SAP ADMIN
Export date: Mon Mar 17 2:09:53 2014 / +0000 GMT
1. Install Oracle 11gR2 software ...
This page was exported from - SAP ADMIN
Export date: Mon Mar 17 2:09:53 2014 / +0000 GMT
SQL> SPOOL upgrade_info.log
SQL> ...
This page was exported from - SAP ADMIN
Export date: Mon Mar 17 2:09:53 2014 / +0000 GMT
Output as PDF file has been power...
This page was exported from - SAP ADMIN
Export date: Mon Mar 17 2:09:53 2014 / +0000 GMT
Output as PDF file has been power...
This page was exported from - SAP ADMIN
Export date: Mon Mar 17 2:09:53 2014 / +0000 GMT
14. set the compatible parameter....
Upcoming SlideShare
Loading in …5
×

oracle upgradation

256 views

Published on

Published in: Technology, News & Politics
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
256
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

oracle upgradation

  1. 1. This page was exported from - SAP ADMIN Export date: Mon Mar 17 2:09:53 2014 / +0000 GMT Step By Step Manual Oracle Database Upgrade to 11.2.0.2 Minimum Version of the database that can be directly upgraded to Oracle11g Release 2Source Database Target Database 9.2.0.8 or higher 11.2.x 10.1.0.5 or higher 11.2.x 10.2.0.2 or higher 11.2.x 11.1.0.6 or higher 11.2.x The following database version will require an indirect upgrade path. Source Database ---> Upgrade Path for Target Database--->Target Database 7.3.3 (or lower)-----> 7.3.4 ---> 9.2.0.8 ---->11.2.x 8.0.5 (or lower)----> 8.0.6 ---> 9.2.0.8 ---->11.2.x 8.1.7 (or lower)----> 8.1.7.4---> 10.2.0.4---->11.2.x 9.0.1.3 (or lower)----> 9.0.1.4-- ->10.2.0.4---->11.2.x 9.2.0.7(or lower)---->9.2.0.8---->11.2.x Here I am upgrading my Oracle 10.2.0.4 database to Oracle 11.2.0.2 1. Copy Pre upgrade Information gathering Script: - Log in to the system as the owner of the Oracle Database 11g Release 2 (11.2) Oracle home directory. Copy the Pre-Upgrade Information Tool (utlu112i.sql) and utltzuv2.sql from the Oracle Database 11g Release 2 (11.2) ORACLE_HOME/rdbms/admin directory to a directory outside of the Oracle home, such as the temporary directory on your system. $ORACLE_HOME/rdbms/admin/utlu112i.sql 2. Execute Pre Upgrade Script: - Should be change to the directory where utlu112i.sql had been copied in the previous step. Start SQL*Plus and connect to the database instance as a user with SYSDBA privileges. Then run and spool the utlu112i.sql file. Please note that the database should be started using the Source Oracle Home. $ sqlplus '/ as sysdba' SQL> spool upgrade_info.log SQL> @utlu112i.sql SQL> spool off SQL> Check the spool file and examine the output of the upgrade information tool.3. Check for the integrity of the source database: Check for the integrity of the source database prior to starting the upgrade by downloading and running dbupgdiag.sql script from below My Oracle Support article Note 556610.1 Script to Collect DB Upgrade/Migrate Diagnostic Information (dbupgdiag.sql) (Avoid this step if don?t have support access) Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.ProfProjects.com | Page 1/10 |
  2. 2. This page was exported from - SAP ADMIN Export date: Mon Mar 17 2:09:53 2014 / +0000 GMT If the dbupgdiag.sql script reports any invalid objects, run $ORACLE_HOME/rdbms/admin/utlrp.sql (multiple times) to validate the invalid objects in the database, until there is no change in the number of invalid objects. $ cd $ORACLE_HOME/rdbms/admin $ sqlplus "/ as sysdba" SQL> @utlrp.sql After validating the invalid objects, re-run dbupgdiag.sql in the database once again and make sure that everything is fine. 4. Check that National Characterset: Check that National Characterset (NLS_NCHAR_CHARACTERSET) is UTF8 and AL16UTF16.select value from NLS_DATABASE_PARAMETERS where parameter = 'NLS_NCHAR_CHARACTERSET'; If this is UTF8 or AL16UTF16 then no action is needed. If is not UTF8 or AL16UTF16 then refer the following article Note 276914.1 The National Character Set in Oracle 9i and 10g. 5. Optimizer Statistics: When upgrading to Oracle Database 11g Release 2 (11.2), optimizer statistics are collected for dictionary tables that lack statistics. This statistics collection can be time consuming for databases with a large number of dictionary tables, but statistics gathering only occurs for those tables that lack statistics or are significantly changed during the upgrade $ sqlplus "/as sysdba"SQL> EXEC DBMS_STATS.GATHER_DICTIONARY_STATS; 6.Ensure that no files need media recovery: Sql> SELECT * FROM v$recover_file; 7. Stop the listener for the database: Make pfile from spfile; $ lsnrctl stop 8. Suhtdown the Database: Shutdown the database. $ sqlplus "/as sysdba" SQL> shutdown immediate; 9. Back Up the Database:1- Perform Cold Backup (or) 2- Take a backup using RMAN Connect to RMAN:rman "target / nocatalog" RUN Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.ProfProjects.com | Page 2/10 |
  3. 3. This page was exported from - SAP ADMIN Export date: Mon Mar 17 2:09:53 2014 / +0000 GMT { ALLOCATE CHANNEL chan_name TYPE DISK; BACKUP DATABASE FORMAT '%U' TAG before_upgrade; BACKUP CURRENT CONTROLFILE TO ''; } 10 Backup and change pfile: Make a backup of the init.ora file. Comment out obsolete parameters * The DIAGNOSTIC_DEST initialization parameter replaces the USER_DUMP_DEST, BACKGROUND_DUMP_DEST. Note: Once the Parameter file is modified as per your requirement, copy the file to $ORACLE_HOME/dbs (11g Oracle Home ) 11 Set Environment Variables: If your operating system is UNIX then complete this step, else skip to next Step.1. Make sure the following environment variables point to the Oracle 11g Release directories: - ORACLE_BASE - ORACLE_HOME - PATH $ export ORACLE_HOME= $ export PATH=$ORACLE_HOME/bin:$PATH $ export ORACLE_BASE= Note : If ORACLE_BASE is not known, after setting Path towards 11g Oracle Home, execute 'orabase', which will point the location of base. $ orabase /uo1/app/oracle 2. Update the oratab entry, to set the new ORACLE_HOME pointing towards ORCL and disable automatic startup Sample /etc/oratab#orcl:/opt/oracle/product/10.2/db_1:N orcl:/opt/oracle/product/11.2/db_1:N Note : After /etc/oratab is updated to have sid and Oracle Home (11.2), you can execute oraenv (/usr/local/bin/oraenv) and set the environment. The input has to be the sid which is entered in /etc/oratab against 11g home. for Instance,[oracle@localhost ~]$ . oraenv ORACLE_SID = [orcl] ? orcl The Oracle base for ORACLE_HOME=/opt/oracle/product/11.2/db_1 is /u01/app/oracle [oracle@localhost ~]$ 12 Upgrade Database: Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.ProfProjects.com | Page 3/10 |
  4. 4. This page was exported from - SAP ADMIN Export date: Mon Mar 17 2:09:53 2014 / +0000 GMT At the operating system prompt, change to the $ORACLE_HOME/rdbms/admin directory of 11gR2 Oracle Home. $ cd $ORACLE_HOME/rdbms/admin $ sqlplus "/ as sysdba" SQL> startup UPGRADE Set the system to spool results to a log file for later verification after the upgrade is completed and start the upgrade script. SQL> set echo on SQL> SPOOL upgrade.log SQL> @catupgrd.sql SQL> spool off These measures are an important final step to ensure the integrity and consistency of the newly upgraded Oracle Database software. Also, if you encountered a message listing obsolete initialization parameters when you started the database for upgrade, then remove the obsolete initialization parameters from the parameter file before restarting. If necessary, convert the SPFILE to a PFILE so you can edit the file to delete parameters. Post Upgrade Steps 13 Post Upgrade: Start the database and run the Post-Upgrade Status Tool $ORACLE_HOME/rdbms/admin/utlu112s.sql which provides a summary of the upgrade at the end of the spool log. It displays the status of the database components in the upgraded database and the time required to complete each component upgrade. Any errors that occur during the upgrade are listed with each component and must be addressed $ sqlplus "/as sysdba" SQL> STARTUP SQL> @utlu112s.sql 14 Recompile Invalid Objects: This script can be run concurrently with utlrp.sql. Run utlrp.sql to recompile any remaining stored PL/SQL and Java code in another session. SQL> @utlrp.sql 15 Check for the integrity of the source database: Check for the integrity of the upgraded database by running dbupgdiag.sql script from below Metalink article Note 556610.1 Script to Collect DB Upgrade/Migrate Diagnostic Information (dbupgdiag.sql) If the dbupgdiag.sql script reports any invalid objects, run $ORACLE_HOME/rdbms/admin/utlrp.sql (multiple times) to validate the invalid objects in the database, until there is no change in the number of invalid objects.After validating the invalid objects, re-run dbupgdiag.sql in the upgraded database once again and make sure that everything is fine. 16 Configure & Start Listener.ora :Modify the listener.ora file: For the upgraded instance(s) modify the ORACLE_HOME parameter to point to the new ORACLE_HOME. Start the listener : lsnrctl start Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.ProfProjects.com | Page 4/10 |
  5. 5. This page was exported from - SAP ADMIN Export date: Mon Mar 17 2:09:53 2014 / +0000 GMT 17 Crosscheck Environment Variables: Set Environment Variables1. Make sure the following environment variables point to the Oracle 11g Release directories: - ORACLE_BASE - ORACLE_HOME - PATH Also check that your oratab file and any client scripts that set the value of ORACLE_HOME point to the Oracle Database 11g Release 2 (11.2) home. Note : If you are upgrading a cluster database, then perform these checks on all nodes in which this cluster database has instances configured. 2. Modify /etc/oratab entry to use automatic startup SID:ORACLE_HOME:YFor Instance, orcl:/opt/oracle/product/11.2/db_1:Y 18 Spfile from Pfile: Edit init.ora:- If you changed the CLUSTER_DATABASE parameter prior the upgrade set it back to TRUE - Migrate your initialization parameter file to a server parameter file. Create a server parameter file with a initialization parameter file SQL> create spfile from pfile; This will create a spfile as a copy of the init.ora file located in $ORACLE_HOME/dbs (UNIX) & %ORACLE_HOME%database (Windows). 19 Start the Database with spfile: Shutdown the database: Sql> shutdown immediate Now start the database it will user spfile Sql> startup Check the Alert log file for any Error. Database is ready to use now. ============================================================================================== ========================= Upgrading 10g to 11g R 2 with DBUA Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.ProfProjects.com | Page 5/10 |
  6. 6. This page was exported from - SAP ADMIN Export date: Mon Mar 17 2:09:53 2014 / +0000 GMT 1. Install Oracle 11gR2 software only (enterprise or standard to match the source db. This blog is on standard version. More on metalink note 870814.1). 2. In order to downgrade Oracle Enterprise Manager Database Control after upgrading to the new Oracle Database 11g release save Database Control files and data before upgrade. The emdwgrd utility resides in the ORACLE_HOME/bin directory in the new Oracle Database 11g release. 3. Follow these steps to save your Database Control files and data: 1. Install the new Oracle Database 11g release. This step is not required for an inplace patchset upgrade. 2. Set ORACLE_HOME to your old Oracle home. This step is not required for an inplace patchset upgrade. 3. Set ORACLE_SID to the SID of the database being upgraded. 4. Set PATH, LD_LIBRARY_PATH, and SHLIB_PATH to point to the Oracle home from which the database is being upgraded. 5. Go to the Oracle home of the new Oracle Database 11g release. 6. Execute one of the following: if Single DB emdwgrd -save -sid old_SID -path save_directory for RAC setenv EM_REMCP /usr/bin/scp emdwgrd -save -cluster -sid old_SID -path save_directory If the release 10g Oracle home is on a shared device, add -shared to the previous command line. create a TNS name entry in the 10g Oracle Home (network/admin) with the same name as the SID before running the above command [oracle@server110 std]$ emdwgrd -save -sid std1 -path /home/oracle/emdu Enter sys password for database std1? Mon Sep 14 19:14:24 2009 - Verify EM DB Control files ... pass Mon Sep 14 19:14:24 2009 - Validating DB Connection to std1 ... pass ENV var EM_REMCP not defined, check if rcp or scp is configured. RCP = /usr/bin/rcp -rp, REMSH = /usr/bin/rsh shared = 0 Mon Sep 14 19:14:28 2009 - Creating directory ... created Mon Sep 14 19:14:29 2009 - Stopping DB Control ... stopped Mon Sep 14 19:14:34 2009 - Saving DB Control files ... saved Mon Sep 14 19:14:50 2009 - Recompiling invalid objects ... recompiled Mon Sep 14 19:14:57 2009 - Exporting sysman schema for std1 ... exported Mon Sep 14 19:15:56 2009 - DB Control was saved successfully. Mon Sep 14 19:15:56 2009 - Starting DB Control ... started Mon Sep 14 19:17:33 2009 - Dump directory was dropped successfully. 7. Copy the Pre-Upgrade Information Tool (utlu112i.sql) from the Oracle Database 11g Release 2 (11.2) ORACLE_HOME/rdbms/admin directory to a directory outside of the Oracle home. 8. run above script and examin the output Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.ProfProjects.com | Page 6/10 |
  7. 7. This page was exported from - SAP ADMIN Export date: Mon Mar 17 2:09:53 2014 / +0000 GMT SQL> SPOOL upgrade_info.log SQL> @utlu112i.sql SQL> SPOOL OFF 9. Gather statistics on schemas instructed by utlu111i.sql EXEC DBMS_STATS.GATHER_DICTIONARY_STATS; EXEC DBMS_STATS.GATHER_SCHEMA_STATS(?user_name?); 10. Grant privileges revoked from public to resolve invalid objects 11. If the timezone warning is Database is using a timezone file older than version 11. then check the timezone with select * from v$timezone_file; if it is not 11 then to fix the problem use the DBMS_DST PL/SQL package and follow the instructions in "Steps to Upgrade Time Zone File and Timestamp with Time Zone Data" in Oracle Database Globalization Support Guide. if the timezone warning is Database is using a timezone file greater than version 11. then before upgrading the database, patch the 11gR2 $ORACLE_HOME/oracore/zoneinfo/ with a timezone data file of the same version as the one used in the source release database. 12. Create a listener for the new 11g R2 Oracle home 13. Run DBUA from new 11g Home Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.ProfProjects.com | Page 7/10 |
  8. 8. This page was exported from - SAP ADMIN Export date: Mon Mar 17 2:09:53 2014 / +0000 GMT Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.ProfProjects.com | Page 8/10 |
  9. 9. This page was exported from - SAP ADMIN Export date: Mon Mar 17 2:09:53 2014 / +0000 GMT Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.ProfProjects.com | Page 9/10 |
  10. 10. This page was exported from - SAP ADMIN Export date: Mon Mar 17 2:09:53 2014 / +0000 GMT 14. set the compatible parameter. alter system set compatible='11.2.0.0.0' scope=spfile ; 15. To upgrade the timezone shutdown the database and start in upgrade mode startup upgrade; exec DBMS_DST.BEGIN_UPGRADE(11); After PL/SQL executes start the database in normal mode and truncate timezone trigger tables truncate table sys.dst$error_table; truncate table sys.dst$trigger_table; VAR numfail number BEGIN DBMS_DST.UPGRADE_DATABASE(:numfail, parallel => TRUE, log_errors => TRUE, log_errors_table => 'SYS.DST$ERROR_TABLE', log_triggers_table => 'SYS.DST$TRIGGER_TABLE', error_on_overlap_time => TRUE, error_on_nonexisting_time => TRUE); DBMS_OUTPUT.PUT_LINE('Failures:'|| :numfail); END; / after finishes BEGIN DBMS_DST.END_UPGRADE(:numfail); END; / Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.ProfProjects.com | Page 10/10 |

×