Today we have started an activity to migrate the database from 10gR2/11gr1 to 11gr2(11.2.0.3) and we will achieve this using RMAN backup of the database and restore it directly on 11gr2 thereafter upgrading to 11gr2.

Source Database with direct migration path’s: 8.1.7.4 OR 9.2.0.8 OR 10.2.0.4 OR 11.1.0.7

Prepare the Target Server :

  • Install Oracle Database Software 11.2.0.3

Prepare the Source Server :

  • Run the pre-upgrade tool on the source database. Copy the utlu112i.sql from the target 11.2.0.3 server and run it against the database that you wish to upgrade.Run the pre-upgrade script on the source database.
    SQL> @utlu112i.SQL
    Oracle DATABASE 11.2 Pre-Upgrade Information Tool 08-25-2013 12:37:31
    Script Version: 11.2.0.3.0 Build: 001
    .
    **********************************************************************
    DATABASE:
    **********************************************************************
    --> name: ERP
    --> version: 11.1.0.7.0
    --> compatible: 11.2.0.0.0
    --> blocksize: 8192
    --> platform: Microsoft Windows x86 64-bit
    --> timezone file: V14
    .
    **********************************************************************
    Tablespaces: [make adjustments IN the CURRENT environment]
    **********************************************************************
    --> SYSTEM tablespace is adequate for the upgrade.
    .... minimum required SIZE: 10535 MB
    --> APPS_UNDOTS1 tablespace is adequate for the upgrade.
    .... minimum required SIZE: 400 MB
    --> TEMP tablespace is adequate for the upgrade.
    .... minimum required SIZE: 60 MB
    --> APPS_TS_QUEUES tablespace is adequate for the upgrade.
    .... minimum required SIZE: 508 MB
    --> APPS_TS_TX_DATA tablespace is adequate for the upgrade.
    .... minimum required SIZE: 10071 MB
    --> CTXD tablespace is adequate for the upgrade.
    .... minimum required SIZE: 21 MB
    --> ODM tablespace is adequate for the upgrade.
    .... minimum required SIZE: 15 MB
    --> SYSAUX tablespace is adequate for the upgrade.
    .... minimum required SIZE: 1181 MB
    .
    **********************************************************************
    Flashback: OFF
    **********************************************************************
    **********************************************************************
    UPDATE Parameters: [UPDATE Oracle DATABASE 11.2 init.ora OR spfile]
    Note: Pre-upgrade tool was run ON a LOWER version 64-bit DATABASE.
    **********************************************************************
    --> If Target Oracle is 32-Bit, refer here for Update Parameters:
    -- No update parameter changes are required.
    --> If Target Oracle is 64-Bit, refer here for Update Parameters:
    -- No update parameter changes are required.
    .
    **********************************************************************
    Renamed Parameters: [UPDATE Oracle DATABASE 11.2 init.ora OR spfile]
    **********************************************************************
    -- No renamed parameters found. No changes are required.
    .
    **********************************************************************
    Obsolete/Deprecated Parameters: [UPDATE Oracle DATABASE 11.2 init.ora OR spfile

    **********************************************************************
    -- No obsolete parameters found. No changes are required
    .

    **********************************************************************
    Components: [The following DATABASE components will be upgraded OR installed]
    **********************************************************************
    --> Oracle Catalog Views [upgrade] VALID
    --> Oracle Packages and Types [upgrade] VALID
    --> JServer JAVA Virtual Machine [upgrade] VALID
    --> Oracle XDK for Java [upgrade] VALID
    --> Real Application Clusters [upgrade] INVALID
    --> OLAP Analytic Workspace [upgrade] VALID
    --> OLAP Catalog [upgrade] VALID
    --> Oracle Text [upgrade] VALID
    --> Oracle XML Database [upgrade] VALID
    --> Oracle Java Packages [upgrade] VALID
    --> Oracle interMedia [upgrade] VALID
    --> Spatial [upgrade] VALID
    --> Data Mining [upgrade] VALID
    --> Oracle OLAP API [upgrade] VALID
    .
    **********************************************************************
    Miscellaneous Warnings
    **********************************************************************
    WARNING: --> Database contains INVALID objects prior to upgrade.
    .... The list OF invalid SYS/SYSTEM objects was written TO
    .... registry$sys_inv_objs.
    .... The list OF non-SYS/SYSTEM objects was written TO
    .... registry$nonsys_inv_objs.
    .... USE utluiobj.SQL after the upgrade TO identify any NEW invalid
    .... objects due TO the upgrade.
    .... USER JUNK_PS has 4 INVALID objects.
    .... USER PUBLIC has 166 INVALID objects.
    .... USER CTXSYS has 1 INVALID objects.
    .... USER ORACLE_OCM has 3 INVALID objects.
    .... USER APPS has 160 INVALID objects.
    .... USER DBSNMP has 6 INVALID objects.
    .... USER SYS has 231 INVALID objects.
    WARNING: --> Your recycle bin contains 1076 object(s).
    .... It IS REQUIRED that the recycle bin IS empty prior TO upgrading
    .... your DATABASE. The command:
    PURGE DBA_RECYCLEBIN
    .... must be executed immediately prior TO executing your upgrade.
    WARNING: --> Database contains schemas with objects dependent on DBMS_LDAP pack
    ge.
    .... Refer TO the 11g Upgrade Guide FOR instructions TO configure Network ACLs.
    .... USER APPS has dependent objects.
    .
    **********************************************************************
    Recommendations
    **********************************************************************
    Oracle recommends gathering dictionary statistics prior TO
    upgrading the DATABASE.
    TO gather dictionary statistics EXECUTE the following command
    while connected AS SYSDBA:

    EXECUTE dbms_stats.gather_dictionary_stats;

    **********************************************************************
    Oracle recommends removing ALL hidden parameters prior TO upgrading.

    TO VIEW existing hidden parameters EXECUTE the following command
    while connected AS SYSDBA:

    SELECT name,description FROM SYS.V$PARAMETER WHERE name
    LIKE '\_%' ESCAPE '\'

    Changes will need to be made in the init.ora or spfile.

    **********************************************************************
    Oracle recommends reviewing any defined events prior to upgrading.

    To view existing non-default events execute the following commands
    while connected AS SYSDBA:
    Events:
    SELECT (translate(value,chr(13)||chr(10),'
    ')) FROM sys.v$parameter2
    WHERE UPPER(name) ='
    EVENT' AND isdefault='FALSE'

    Trace Events:
    SELECT (translate(value,chr(13)||chr(10),'
    ')) from sys.v$parameter2
    WHERE UPPER(name) = '
    _TRACE_EVENTS' AND isdefault='FALSE'

    Changes will need to be made in the init.ora or spfile.

    **********************************************************************
    SQL>

    Take backup of the source database be it 10gR1/2 OR 11gr1.

    rman target /
    backup DATABASE;
    backup archivelog ALL;

    Record the last sequence generated during completing of backup; In our case it is Seq 66513
    Either you take a backup of controlfile manually or configure it in RMAN to take a snap shot with AUTO option ON.

    RMAN> SHOW ALL;
    USING target DATABASE control file instead OF recovery catalog
    RMAN configuration parameters FOR DATABASE WITH db_unique_name ERP are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # DEFAULT
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # DEFAULT
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # DEFAULT
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # DEFAULT
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # DEFAULT
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # DEFAULT
    CONFIGURE MAXSETSIZE TO UNLIMITED; # DEFAULT
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # DEFAULT
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # DEFAULT
    CONFIGURE COMPRESSION ALGORITHM 'BZIP2'; # DEFAULT
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # DEFAULT
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'P:\R12\11.1.0\DATABASE\SNCFERP.ORA';
    # DEFAULT

    Transfer the backup to the target server.
    Our Path on Source : E:\rmanbkp\ERP_20130825_2068.BAK
    Path on Destination is same as the source. If you have a different path then it requires cataloging the files after restoring the controlfile from autobackup as show below.

    On the target server.

  • Create a pfile
  • erp.__db_cache_size=4177526784
    erp.__java_pool_size=16777216
    erp.__large_pool_size=16777216
    erp.__oracle_base='D:\app\oracle'#ORACLE_BASE set from environment
    erp.__pga_aggregate_target=1728053248
    erp.__sga_target=5150605312
    erp.__shared_io_pool_size=0
    erp.__shared_pool_size=905969664
    erp.__streams_pool_size=0
    *.audit_file_dest='D:\app\oracle\admin\erp\adump'
    *.audit_trail='db'
    *.compatible='11.2.0.0.0'
    *.control_files='D:\app\oracle\oradata\erp\control01.ctl','D:\app\oracle\fast_recovery_area\erp\control02.ctl'
    *.db_block_size=8192
    *.db_domain=''
    *.db_name='erp'
    *.db_recovery_file_dest='D:\app\oracle\fast_recovery_area'
    *.db_recovery_file_dest_size=4322230272
    *.diagnostic_dest='D:\app\oracle'
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=erpXDB)'
    *.nls_language='AMERTICAN'
    *.open_cursors=300
    *.pga_aggregate_target=1716518912
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=5149556736
    *.undo_tablespace='APPS_UNDOTS1'
    *.db_file_name_convert=("P:\ORACLE\ORADATA","D:\app\oracle\oradata\erp")
    *.log_file_name_convert=("P:\ORACLE\ORADATA","D:\app\oracle\oradata\erp","P:\R12\fra","D:\app\oracle\fast_recovery_area")
  • Start the database in nomount state
  •  SQL>startup nomount
  • Login to rman & restore controlfile
  • rman target /
    RMAN>restore controfile FROM 'E:\rmanbkp\SNCFERP.ORA';
    RMAN> catalog START WITH ''; --> If your backup files on the target system has a different path
  • Prepare the restore script
  • run
    {
    SET newname FOR datafile 35 TO 'D:\app\oracle\oradata\erp\APPS_TS_TOOLS.DBF';
    SET newname FOR datafile 1 TO 'D:\app\oracle\oradata\erp\SYSTEM01.DBF';
    SET newname FOR datafile 2 TO 'D:\app\oracle\oradata\erp\SYSTEM02.DBF';
    SET newname FOR datafile 3 TO 'D:\app\oracle\oradata\erp\SYSTEM03.DBF';
    SET newname FOR datafile 4 TO 'D:\app\oracle\oradata\erp\SYSTEM04.DBF';
    SET newname FOR datafile 5 TO 'D:\app\oracle\oradata\erp\SYSTEM05.DBF';
    SET newname FOR datafile 6 TO 'D:\app\oracle\oradata\erp\SYSTEM06.DBF';
    SET newname FOR datafile 7 TO 'D:\app\oracle\oradata\erp\SYSTEM07.DBF';
    SET newname FOR datafile 8 TO 'D:\app\oracle\oradata\erp\SYSTEM08.DBF';
    SET newname FOR datafile 9 TO 'D:\app\oracle\oradata\erp\SYSTEM09.DBF';
    SET newname FOR datafile 10 TO 'D:\app\oracle\oradata\erp\SYSTEM10.DBF';
    SET newname FOR datafile 11 TO 'D:\app\oracle\oradata\erp\SYSTEM11.DBF';
    SET newname FOR datafile 39 TO 'D:\app\oracle\oradata\erp\XXQIA.DBF';
    SET newname FOR datafile 12 TO 'D:\app\oracle\oradata\erp\UNDO01.DBF';
    SET newname FOR datafile 13 TO 'D:\app\oracle\oradata\erp\A_ARCHIVE01.DBF';
    SET newname FOR datafile 14 TO 'D:\app\oracle\oradata\erp\A_INT01.DBF';
    SET newname FOR datafile 15 TO 'D:\app\oracle\oradata\erp\A_MEDIA01.DBF';
    SET newname FOR datafile 16 TO 'D:\app\oracle\oradata\erp\A_NOLOG01.DBF';
    SET newname FOR datafile 17 TO 'D:\app\oracle\oradata\erp\A_QUEUE01.DBF';
    SET newname FOR datafile 18 TO 'D:\app\oracle\oradata\erp\A_QUEUE02.DBF';
    SET newname FOR datafile 19 TO 'D:\app\oracle\oradata\erp\A_REF01.DBF';
    SET newname FOR datafile 20 TO 'D:\app\oracle\oradata\erp\A_REF02.DBF';
    SET newname FOR datafile 21 TO 'D:\app\oracle\oradata\erp\A_SUMM01.DBF';
    SET newname FOR datafile 31 TO 'D:\app\oracle\oradata\erp\ODM.DBF';
    SET newname FOR datafile 32 TO 'D:\app\oracle\oradata\erp\OLAP.DBF';
    SET newname FOR datafile 33 TO 'D:\app\oracle\oradata\erp\OWAD01.DBF';
    SET newname FOR datafile 34 TO 'D:\app\oracle\oradata\erp\PORTAL01.DBF';
    SET newname FOR datafile 36 TO 'D:\app\oracle\oradata\erp\XXEULTS01.DBF';
    SET newname FOR datafile 38 TO 'D:\app\oracle\oradata\erp\INTERIM.DBF';
    SET newname FOR datafile 22 TO 'D:\app\oracle\oradata\erp\A_TXN_DATA01.DBF';
    SET newname FOR datafile 23 TO 'D:\app\oracle\oradata\erp\A_TXN_DATA02.DBF';
    SET newname FOR datafile 24 TO 'D:\app\oracle\oradata\erp\A_TXN_DATA03.DBF';
    SET newname FOR datafile 25 TO 'D:\app\oracle\oradata\erp\A_TXN_IND01.DBF';
    SET newname FOR datafile 26 TO 'D:\app\oracle\oradata\erp\A_TXN_IND02.DBF';
    SET newname FOR datafile 27 TO 'D:\app\oracle\oradata\erp\A_TXN_IND03.DBF';
    SET newname FOR datafile 28 TO 'D:\app\oracle\oradata\erp\A_TXN_IND04.DBF';
    SET newname FOR datafile 29 TO 'D:\app\oracle\oradata\erp\A_TXN_IND05.DBF';
    SET newname FOR datafile 30 TO 'D:\app\oracle\oradata\erp\CTXD01.DBF';
    SET newname FOR datafile 37 TO 'D:\app\oracle\oradata\erp\SYSAUX01.DBF';
    SET newname FOR datafile 40 TO 'D:\app\oracle\oradata\erp\RMXDATA01.DBF';
    SET newname FOR datafile 41 TO 'D:\app\oracle\oradata\erp\RMXIDX01.DBF';
    SET newname FOR datafile 42 TO 'D:\app\oracle\oradata\erp\RMXLOBS01.DBF';
    SET newname FOR datafile 43 TO 'D:\app\oracle\oradata\erp\A_TXN_DATA04.DBF';
    SET newname FOR datafile 44 TO 'D:\app\oracle\oradata\erp\A_TXN_DATA05.DBF';
    SET newname FOR datafile 45 TO 'D:\app\oracle\oradata\erp\A_REF03.DBF';
    SET newname FOR datafile 46 TO 'D:\app\oracle\oradata\erp\A_TXN_IND06.DBF';
    SET newname FOR datafile 47 TO 'D:\app\oracle\oradata\erp\A_TXN_IND07.DBF';
    SET newname FOR datafile 48 TO 'D:\app\oracle\oradata\erp\A_MEDIA02.DBF';
    SET newname FOR datafile 49 TO 'D:\app\oracle\oradata\erp\A_INT02.DBF';
    restore DATABASE;
    switch datafile ALL;
    recover DATABASE until logseq 66512;
    }
  • Once the database is recovered open the database in upgrade mode
  • SQL>ALTER DATABASE OPEN resetlogs upgrade;
  • Start the Cat upgrade script inorder to initiate the upgrade process
  • SQL>spool upgrade.log
    SQL>@?/catupgrd.SQL
    SQL> @catupgrd.SQL
    DOC>#######################################################################
    DOC>#######################################################################
    DOC>
    DOC> The FIRST TIME this script IS run, there should be no error messages
    DOC> generated; ALL normal upgrade error messages are suppressed.
    DOC>
    DOC> IF this script IS being re-run after correcting SOME problem, THEN
    DOC> expect the following error which IS NOT automatically suppressed:
    DOC>
    DOC> ORA-00001: UNIQUE CONSTRAINT (<constraint_name>) violated
    DOC> possibly IN conjunction WITH
    DOC> ORA-06512: at "<procedure/function name>", line NN
    DOC>
    DOC> These errors will automatically be suppressed BY the DATABASE Upgrade
    DOC> Assistant (DBUA) WHEN it re-runs an upgrade.
    DOC>
    DOC>#######################################################################
    DOC>#######################################################################
    DOC>#
    DOC>######################################################################
    DOC>######################################################################
    DOC> The following statement will cause an "ORA-01722: invalid number"
    DOC> error IF the USER running this script IS NOT SYS. Disconnect
    DOC> AND reconnect WITH AS SYSDBA.
    DOC>######################################################################
    DOC>######################################################################
    DOC>#
    no ROWS selected
    DOC>######################################################################
    DOC>######################################################################
    DOC> The following statement will cause an "ORA-01722: invalid number"
    DOC> error IF the DATABASE server version IS NOT correct FOR this script.
    DOC> Perform "ALTER SYSTEM CHECKPOINT" prior TO "SHUTDOWN ABORT", AND USE
    DOC> a different script OR a different server.
    DOC>######################################################################
    DOC>######################################################################
    DOC>#
    no ROWS selected
    DOC>#######################################################################
    DOC>#######################################################################
    DOC> The following statement will cause an "ORA-01722: invalid number"
    DOC> error IF the DATABASE has NOT been opened FOR UPGRADE.
    DOC>
    DOC> Perform "ALTER SYSTEM CHECKPOINT" prior TO "SHUTDOWN ABORT", AND
    DOC> restart USING UPGRADE.
    DOC>#######################################################################
    DOC>#######################################################################
    DOC>#
    no ROWS selected
    |
    |
    |
    SQL> SELECT COUNT(*) FROM bootstrap$mig;

    COUNT(*)
    ----------
    60

    1 ROW selected.

    SQL> SELECT COUNT(*) FROM bootstrap$mig;

    COUNT(*)
    ----------
    60

    1 ROW selected.

    SQL> SELECT COUNT(*) FROM bootstrap$mig;

    COUNT(*)
    ----------
    60

    1 ROW selected.

    SQL>
    SQL> WHENEVER SQLERROR CONTINUE
    SQL>
    SQL> DECLARE
    2 LS_Special_3 CONSTANT NUMBER := 11;
    3 LOCbldlogid VARCHAR2(22) := NULL;
    4 LOCLockDownScn NUMBER;
    5 rowcnt NUMBER;
    6 BEGIN
    7 SELECT COUNT(1) INTO rowcnt
    8 FROM SYS.V$DATABASE V
    9 WHERE V.LOG_MODE = 'ARCHIVELOG' AND
    10 V.SUPPLEMENTAL_LOG_DATA_MIN != 'NO';
    11 IF 0 != rowcnt THEN
    12 -- Logminer may be mining this redo stream, so we must do a special
    13 -- logminer dictionary build to capture the revised obj# etc.
    14 sys.dbms_logmnr_internal.DO_INT_BUILD(build_op=>LS_Special_3,
    15 dictionary_filename=>NULL,
    16 dictionary_location=>NULL,
    17 bldlogid_initxid=>LOCbldlogid,
    18 LockDownScn=>LOCLockDownScn,
    19 release_locks=>FALSE);
    20 END IF;
    21
    22 -- Now we can do the swap.
    23 dbms_ddl_internal.swap_bootstrap('BOOTSTRAP$MIG');
    24
    25 -- We've completed the swap.
    26 -- Remove the BOOTSTRAP_UPGRADE_ERROR entry in props$.
    27 DELETE FROM props$ WHERE name = 'BOOTSTRAP_UPGRADE_ERROR';
    28 DELETE FROM props$ WHERE name = 'LOGMNR_BOOTSTRAP_UPGRADE_ERROR';
    29 commit;
    30 END;
    31 /

    PL/SQL PROCEDURE successfully completed.

    SQL>
    SQL>
    SQL> /*****************************************************************************/
    SQL> /* Step 10 - SHUTDOWN THE DATABASE..!!!!!
    SQL> */

    SQL> /*****************************************************************************/
    SQL> shutdown immediate;
    DATABASE closed.
    DATABASE dismounted.
    ORACLE instance shut down.
    SQL>
    SQL>
    SQL>
    SQL> DOC
    DOC>#######################################################################
    DOC>#######################################################################
    DOC>
    DOC> The above SQL script IS the final step OF the upgrade. Please
    DOC> review any errors IN the spool log file. IF there are any errors IN
    DOC> the spool file, consult the Oracle DATABASE Upgrade Guide FOR
    DOC> troubleshooting recommendations.
    DOC>
    DOC> NEXT restart FOR normal operation, AND THEN run utlrp.SQL TO
    DOC> recompile any invalid application objects.
    DOC>
    DOC> IF the SOURCE DATABASE had an older TIME zone version prior TO
    DOC> upgrade, THEN please run the DBMS_DST package. DBMS_DST will upgrade
    DOC> TIMESTAMP WITH TIME ZONE DATA TO USE the latest TIME zone file shipped
    DOC> WITH Oracle.
    DOC>
    DOC>#######################################################################
    DOC>#######################################################################
    DOC>#
    SQL>
    SQL> Rem SET errorlogging off
    SQL> SET ERRORLOGGING OFF;
    SQL>
    SQL> REM END OF CATUPGRD.SQL
    SQL>
    SQL> REM bug 12337546 - Exit CURRENT sqlplus SESSION at END OF catupgrd.SQL.
    SQL> REM This forces USER TO START a NEW sqlplus SESSION IN ORDER
    SQL> REM TO CONNECT TO the upgraded db.
    SQL> exit
  • Start the database in normal mode and compile invalid objects
  • SQL> startup
    ORACLE instance started.
    Total System Global Area 5127602176 bytes
    Fixed SIZE 2264088 bytes
    Variable SIZE 939525096 bytes
    DATABASE Buffers 4177526784 bytes
    Redo Buffers 8286208 bytes
    DATABASE mounted.
    DATABASE opened.
    SQL> @%ORACLE_HOME%\rdbms\admin\utlrp.SQL
    TIMESTAMP
    --------------------------------------------------------------------------------
    COMP_TIMESTAMP UTLRP_BGN 2013-08-25 14:01:13

    Compiling invalid objects will take a longer time depending on the resources you have on the server i.e CPU+RAM.
    You can monitor the progress using the below query

    SQL>SELECT COUNT(*) FROM all_objects WHERE STATUS='INVALID';
  • Run catuppst.sql to migrate the baseline data
  • SQL> @catuppst.SQL
    TIMESTAMP
    --------------------------------------------------------------------------------

    COMP_TIMESTAMP POSTUP_BGN 2013-08-26 08:11:49

    PL/SQL PROCEDURE successfully completed.

    This script will migrate the Baseline DATA ON a pre-11g DATABASE
    TO the 11g DATABASE.

    ... ...
    ... Completed Moving the Baseline DATA ...
    ... ...
    ... IF there are no Move BL DATA messages ...
    ... above, THEN there are no renamed ...
    ... baseline TABLES IN the system. ...
    ... ...
    ... ...
    ... Completed the Dropping OF the ...
    ... Renamed Baseline TABLES ...
    ... ...
    ... IF there are no DROP TABLE messages ...
    ... above, THEN there are no renamed ...
    ... baseline TABLES IN the system. ...
    ... ...

    PL/SQL PROCEDURE successfully completed.

    0 ROWS created.

    Commit complete.

    TABLE created.

    2 ROWS created.

    1 ROW updated.

    2 ROWS updated.

    0 ROWS updated.

    TABLE dropped.

    Commit complete.

    0 ROWS updated.

    Commit complete.

    0 ROWS updated.

    Commit complete.

    0 ROWS updated.

    Commit complete.

    0 ROWS created.

    Commit complete.

    0 ROWS created.

    Commit complete.

    PL/SQL PROCEDURE successfully completed.

    TIMESTAMP
    --------------------------------------------------------------------------------
    COMP_TIMESTAMP POSTUP_END 2013-08-26 08:11:52

    PL/SQL PROCEDURE successfully completed.

    PL/SQL PROCEDURE successfully completed.

    PL/SQL PROCEDURE successfully completed.

    Generating apply AND ROLLBACK scripts...
    CHECK the following file FOR errors:
    D:\app\oracle\cfgtoollogs\catbundle\catbundle_PSU_PRODERP_GENERATE_2013Aug26_08_
    11_56.log
    Apply script: D:\app\oracle\product\11.2.0\db_1\rdbms\admin\catbundle_PSU_PRODER
    P_APPLY.SQL
    ROLLBACK script: D:\app\oracle\product\11.2.0\db_1\rdbms\admin\catbundle_PSU_PRO
    DERP_ROLLBACK.SQL

    PL/SQL PROCEDURE successfully completed.

    Executing script file...

    SQL> COLUMN spool_file NEW_VALUE spool_file NOPRINT
    SQL> SELECT 'D:\app\oracle\cfgtoollogs\catbundle\' || 'catbundle_PSU_' || name |
    | '
    _APPLY_' || TO_CHAR(SYSDATE, 'YYYYMonDD_hh24_mi_ss', 'NLS_DATE_LANGUAGE=''AME
    RICAN''') || '.log' AS spool_file FROM v$database;

    SQL> SPOOL &spool_file
    SQL> exec dbms_registry.set_session_namespace('
    SERVER')

    PL/SQL procedure successfully completed.

    SQL> ALTER SESSION SET current_schema = SYS;

    Session altered.

    SQL> PROMPT Updating registry...
    Updating registry...
    SQL> INSERT INTO registry$history
    2 (action_time, action,
    3 namespace, version, id,
    4 bundle_series, comments)
    5 VALUES
    6 (SYSTIMESTAMP, '
    APPLY',
    7 SYS_CONTEXT('
    REGISTRY$CTX','NAMESPACE'),
    8 '
    11.2.0.3',
    9 0,
    10 '
    PSU',
    11 '
    Patchset 11.2.0.2.0');

    1 row created.

    SQL> COMMIT;

    Commit complete.

    SQL> SPOOL off
    SQL> SET echo off
    Check the following log file for errors:
    D:\app\oracle\cfgtoollogs\catbundle\catbundle_PSU_ERP_APPLY_2013Aug26_08_11_58.log</li>
  • Run utlu112s.sql to confirm the successful upgrade
  • SQL&gt; @utlu112s.SQL
    .
    Oracle DATABASE 11.2 Post-Upgrade STATUS Tool 08-26-2013 09:02:13
    .
    Component CURRENT Version Elapsed TIME
    Name STATUS NUMBER HH:MM:SS
    .
    Oracle Server
    . VALID 11.2.0.3.0 00:19:20
    JServer JAVA Virtual Machine
    . VALID 11.2.0.3.0 00:03:35
    Oracle REAL Application Clusters
    . INVALID 11.2.0.3.0 00:00:00
    OLAP Analytic Workspace
    . VALID 11.2.0.3.0 00:00:24
    OLAP Catalog
    . VALID 11.2.0.3.0 00:00:56
    Oracle OLAP API
    . VALID 11.2.0.3.0 00:00:20
    Oracle XDK
    . VALID 11.2.0.3.0 00:00:41
    Oracle Text
    . VALID 11.2.0.3.0 00:01:03
    Oracle XML DATABASE
    . VALID 11.2.0.3.0 00:02:06
    Oracle DATABASE Java Packages
    . VALID 11.2.0.3.0 00:00:15
    Oracle Multimedia
    . VALID 11.2.0.3.0 00:06:15
    Spatial
    . VALID 11.2.0.3.0 00:07:03
    Gathering Statistics
    . 00:06:50
    Total Upgrade TIME: 00:48:55
    PL/SQL PROCEDURE successfully completed.
Tagged with →  
Share →
0 comments
Skip to toolbar