Upgrade from Oracle 9i to 11g Database

Upgrade from 9i to 11g

The following is a real scenario for upgrading a 9.2.0.8 DB to 11.2.0.1.0 version on Redhat 4.7 in 28 Step

Before continue please check Metalink [ID 730365.1]
It Includes all patchset downloads + How to upgrade from any Oracle DB version to another one.

Required packges for installing 11g software: This for RHCL 4.7
---------------------------------------------------------
libaio-devel-0.3.105
elfutils-libeif-devel-0.97
unixODBC-devel-2.2.11

Install 11g software on new ORACLE Home...

Apply the latest CPU patch (Optional)... Yes you can Apply the cpu patch on the 11g ORACLE_HOME -as a pre-Upgrade step- before having a database. Check Metalink Note [ID 461082.1]

Note ID: 429825.1
####### ########
Database upgrade steps from 9i to 11g:
#####################################

HHHHHHHHHHHH
On the 9i Server
HHHHHHHHHHHH

Step 1:
----------
Log into 11g server and copy the following scripts from 11g ORACLE_HOME/rdbms/admin directory on 11g server to 9i server:

$scp /u01/oracle/ora11g/11.2.0.1/rdbms/admin/utlu112i.sql oracle@9i_server:/home/oracle
$scp /u01/oracle/ora11g/11.2.0.1/rdbms/admin/utltzuv2.sql oracle@9i_server:/home/oracle


Step 2:
----------
=Run utlrp script to fix any invalid object before the upgrade:
--------------------------------------------------------------
SQL> @?/rdbms/admin/utlrp.sql

Note down invalid objects to compare after the upgrade to 11g:
--------------------------------------------------------------
SQL> set pages 0
SQL> set linesize 170
SQL> select 'alter '||object_type||' '||owner||'.'||object_name||' compile;' from dba_objects where status <> 'VALID';

Step 3: Save a script for Deprecated CONNECT Role:
----------
In 11g version CONNECT role has only the "CREATE SESSION" privilege, the other privileges are NOT exist in CONNECT role in 11g version like:

CREATE VIEW
CREATE TABLE
ALTER SESSION
CREATE CLUSTER
CREATE SYNONYM
CREATE SEQUENCE
CREATE DATABASE LINK

So you need to re-grant these privileges to users who have connect role after upgrade to 11g.
This SQL will help you just save the result in somewhere to run it after the upgrade:

SQL> set linesize 170
SQL> set pages 100
SQL> spool /home/oracle/connect_role.sql
SQL> SELECT 'grant CREATE VIEW,CREATE TABLE,ALTER SESSION,CREATE CLUSTER,CREATE SYNONYM,CREATE SEQUENCE to '||grantee||';'
FROM dba_role_privs WHERE granted_role = 'CONNECT' AND grantee
NOT IN ('SYS', 'OUTLN', 'SYSTEM', 'CTXSYS', 'DBSNMP','LOGSTDBY_ADMINISTRATOR',
'ORDSYS','ORDPLUGINS', 'OEM_MONITOR', 'WKSYS', 'WKPROXY','WK_TEST',
'WKUSER', 'MDSYS', 'LBACSYS', 'DMSYS','WMSYS', 'OLAPDBA', 'OLAPSVR',
'OLAP_USER','OLAPSYS', 'EXFSYS', 'SYSMAN', 'MDDATA','SI_INFORMTN_SCHEMA',
'XDB', 'ODM');
SQL> spool off

Step 4:
----------
Create script to save DBLINKS creation script:
SELECT 'CREATE '||DECODE(U.NAME,'PUBLIC','public ')||'DATABASE LINK '||CHR(10)
||DECODE(U.NAME,'PUBLIC',Null, 'SYS','',U.NAME||'.')|| L.NAME||chr(10)
||'CONNECT TO ' || L.USERID || ' IDENTIFIED BY "'||L.PASSWORD||'" USING '''||L.HOST||''''
||chr(10)||';' TEXT
FROM SYS.LINK$ L, SYS.USER$ U
WHERE L.OWNER# = U.USER#;

Step 5: Upgrade the TIMEZONE version
----------
Convert the 9i database TIMEZONE from version 1 to version 4:

Download this interm patch 5632264 .. Extract it .. run "opatch apply" command .. As the following:

First shutdown the database:
---------------------------
SQL> shu immediate;

Apply the patch:
---------------
$cd /u01/oracle/ora9i/
$unzip p5632264_92080_timezoneV4.zip
$cd /u01/oracle/ora9i/5632264
$opatch apply

Startup the database again:
---------------------------
SQL> startup

The following query must return version 4:

SELECT CASE COUNT(DISTINCT(tzname))
WHEN 183 then 1
WHEN 355 then 1
WHEN 347 then 1
WHEN 377 then 2
WHEN 186 then CASE COUNT(tzname) WHEN 636 then 2 WHEN 626 then 3 ELSE 0 END
WHEN 185 then 3
WHEN 386 then 3
WHEN 387 then case COUNT(tzname) WHEN 1438 then 3 ELSE 0 end
WHEN 391 then case COUNT(tzname) WHEN 1457 then 4 ELSE 0 end
WHEN 392 then case COUNT(tzname) WHEN 1458 then 4 ELSE 0 end
WHEN 188 then case COUNT(tzname) WHEN 637 then 4 ELSE 0 end
WHEN 189 then case COUNT(tzname) WHEN 638 then 4 ELSE 0 end
ELSE 0 end VERSION
FROM v$timezone_names;

VERSION
----------
4

Step 6:
----------
Run the script you extracted before from 11gr2 binaries

$cd /home/oracle/

$sqlplus "/ as sysdba"

SQL> spool utlu112i.log
SQL> @utlu112i.sql
SQL> spool off


This script will give you infomation about tablespaces if they need to adjusted according to 11g requirements ,also gives information about parameters need to be modified and also Obsolete/Deprecated ones and also deprecated roles like connect.
Keep the log it will be helpful.


Step 7: Gather SYS schema statistics
----------
Gather statistics for SYS schema:
SQL> EXEC DBMS_STATS.GATHER_DICTIONARY_STATS('SYS',OPTIONS=>'GATHER', ESTIMATE_PERCENT => DBMS_STATS.AUTO_SAMPLE_SIZE, METHOD_OPT => 'FOR ALL COLUMNS SIZE AUTO', CASCADE => TRUE);


Step 8: Check the Dictionary
----------
Check for any corruption in the dictionary -will create a script then will run it-:

Script Creation:
Following code creates a script called analyze.sql


Set verify off
Set space 0
Set line 120
Set heading off
Set feedback off
Set pages 1000
Spool analyze.sql
SELECT 'Analyze cluster "'||cluster_name||'" validate structure cascade;'
FROM dba_clusters
WHERE owner='SYS'
UNION
SELECT 'Analyze table "'||table_name||'" validate structure cascade;'
FROM dba_tables
WHERE owner='SYS'
AND partitioned='NO'
AND (iot_type='IOT' OR iot_type is NULL)
UNION
SELECT 'Analyze table "'||table_name||'" validate structure cascade into invalid_rows;'
FROM dba_tables
WHERE owner='SYS'
AND partitioned='YES';

spool off

Run the following scripts for Dictionary checking:

SQL> @?/rdbms/admin/utlvalid.sql
SQL> @analyze.sql

Step 9:
----------

Ensure there is no files need media recovery or in backup mode:

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

Step 10:
----------

Resolve any outstanding unresolved distributed transaction:

SQL> select * from dba_2pc_pending;

If that query returned rows you should do the following:
--
SQL> SELECT local_tran_id
FROM dba_2pc_pending;
SQL> EXECUTE dbms_transaction.purge_lost_db_entry('');
SQL> COMMIT;


Step 11:
----------
Ensure the users sys and system have 'system' as their default tablespace.

SQL> SELECT username, default_tablespace
FROM dba_users
WHERE username in ('SYS','SYSTEM');

Step 12:
-----------
Ensure that the aud$ is in the system tablespace when auditing is enabled.

SQL> SELECT tablespace_name
FROM dba_tables
WHERE table_name='AUD$';

Step 13: Saving database files location
----------
Note down the location of datafiles, redo logs, control files.

SQL> col name for a70
SQL> col file_name for a70
SQL> col member for a70
SQL> set feedback off
SQL> spool db_files.txt
SQL> SELECT name FROM v$controlfile;
SQL> SELECT file_name FROM dba_data_files;
SQL> SELECT group#, member FROM v$logfile;
SQL> spool off

Step 14:
-----------
Check whether database has any externally authenticated SSL users.

SELECT name FROM sys.user$
WHERE ext_username IS NOT NULL
AND password = 'GLOBAL';

If any SSL users are found then Step 31 has to be followed after the upgrade

Step 15: Set DB in NoArchivelog mode.
----------
Put the database in noarchivelog mode to minimize the upgrade time.

$ sqlplus "/as sysdba"
SQL> shutdown immediate;
SQL> alter database noarchivelog;
SQL> archive log stop;
SQL> shutdown immediate;

Step 16: Take a cold backup.
----------

Step 17:
----------
Copy the Datafiles + PFile from the 9i server to the new 11g server -in case you are upgrading in a new server-


HHHHHHHHHHHHH
On The 11g Server:
HHHHHHHHHHHHH

Step 18: Modify the copied 9i Pfile.
----------
=Comment out obsoleted parameters like:

transaction_auditing
hash_join_enabled
DDL_WAIT_FOR_LOCKS
LOGMNR_MAX_PERSISTENT_SESSIONS
PLSQL_COMPILER_FLAGS

=Replace all deprecated parameters like:

BACKGROUND_DUMP_DEST (replaced by DIAGNOSTIC_DEST)
CORE_DUMP_DEST (replaced by DIAGNOSTIC_DEST)
USER_DUMP_DEST (replaced by DIAGNOSTIC_DEST)
STANDBY_ARCHIVE_DEST
log_archive_start
max_enabled_roles
COMMIT_WRITE
INSTANCE_GROUPS
LOG_ARCHIVE_LOCAL_FIRST
PLSQL_DEBUG (replaced by PLSQL_OPTIMIZE_LEVEL)
PLSQL_V2_COMPATIBILITY
REMOTE_OS_AUTHENT
TRANSACTION_LAG attribute (of the CQ_NOTIFICATION$_REG_INFO object)

=set the COMPATIBLE parameter to 10.1.0
compatible=10.1.0

=set the parameter CLUSTER_DATABASE=FALSE

=Add the parameter DIAGNOSTIC_DEST to hold database logs:
diagnostic_dest=/u01/oracle/ora11g/11.2.0.1/diagnostics/ORCL

When done copy the pfile to 11g ORACLE_HOME/dbs

Step 19: Create the Diagnostic directory for the DB
----------
mkdir -p $ORACLE_HOME/diagnostics/ORCL

Step 20:
----------
Make sure that ".bash_profile" holds the new 11g installation environment variables like:
ORACLE_BASE
ORACLE_HOME
ORACLE_SID
LD_LIBRARY_PATH
TNS_ADMIN
CLASSPATH
PATH

These variables are supposed to be exist since the 11gr2 installation on that server, If you are doing the upgrade on the same server you must create a new profile something like ".11g_bash_profile" holding all variables for 11g installation.

Step 21: Update oratab & oraInventory
----------
Update the oratab file:

$vi /etc/oratab

#ORCL:/u01/oracle/ora9i:Y
ORCL:/u01/oracle/ora11g/11.2.0.1:Y

-Hash the entry for 9i ORACLE_HOME in case you upgrading on the same server then add the an entry for 11g ORACLE_HOME

Update oraInventory location:
-----------------------------
$vi /etc/oraInst.loc

inventory_loc=/u01/oracle/oraInventory
inst_group=oinstall


Step 22:
----------
Upgrading the Database to 11gR2...

Note: If you are upgrading on the same server run the profile holds the 11g environment variables -you prepared before- for the 11g installation.

Startup the DB in upgrade mode:
------------------------------
startup UPGRADE

Create the SYSAUX tablespace:
----------------------------
SQL>CREATE TABLESPACE SYSAUX
DATAFILE '/fiber_ocfs_pefms_data_1/oracle/pefms/sysaux01.dbf' SIZE 2000M reuse
autoextend on next 100m maxsize unlimited
EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO ONLINE;

start the upgrade script:
------------------------
$cd $ORACLE_HOME/rdbms/admin

SQL> set echo on
SQL> SPOOL upgrade.log
SQL> @?/rdbms/admin/catupgrd.sql
SQL> spool off

Database will be shutdown by catupgrd.sql script. Restart the Instance to reinitialize the system parameters for normal operation.

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.

Run the Post-Upgrade Status Tool:
--------------------------------
SQL> @?/rdbms/admin/utlu112s.sql

Recompile any remaining stored PL/SQL:
-------------------------------------
SQL> @?/rdbms/admin/catuppst.sql
SQL> @?/rdbms/admin/utlrp.sql

Check for the integrity of the upgraded database by running dbupgdiag.sql script:
--------------------------------------------------------------------------------
Download that script from Metalink Note [ID 556610.1] and run it.

During the test I found duplicate objects between SYS and SYSTEM so I followed the Metalink Note and dropped duplicate objects owned by SYSTEM user:

Warning:
Don't run the following commands unless you make sure that following objects are duplicate ones in your DB.

SQL> drop TABLE system.AQ$_SCHEDULES;
SQL> drop INDEX system.AQ$_SCHEDULES_PRIMARy;
SQL> drop PACKAGE system.DBMS_REPCAT_AUTH;
SQL> drop PACKAGE system.BODYDBMS_REPCAT_AUTH;
SQL> drop PACKAGE system.DBMS_SHARED_POOL;
SQL> drop PACKAGE system.BODYDBMS_SHARED_POOL;
SQL> drop TABLE system.UTL_RECOMP_INVALID ;
SQL> drop TABLE system.UTL_RECOMP_SORTED;
SQL> drop TABLE system.UTL_RECOMP_COMPILED;
SQL> drop TABLE system.UTL_RECOMP_BACKUP_JOBS;
SQL> drop TABLE system.UTL_RECOMP_LOG;
SQL> drop PACKAGE system.UTL_RECOMP;
SQL> drop PACKAGE system.BODYUTL_RECOMP;
SQL> drop TABLE system.CHAINED_ROWS;

Step 23:
----------
Grant the missing privileges related to "connect" which been deprecated in 11g:
------------------------------------------------------------------------------
-Using Script been created in Step3-
SQL> @/home/oracle/connect_role.sql


##################
Post Upgrade Steps:
##################

Step 24:
-----------
Check listener.ora for any modifications needed to listen on the upgraded DB.

LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = pc-ora-test)(PORT = 1521))
)
)

SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(ORACLE_HOME = /u01/oracle/ora11g/11.2.0.1)
(SID_NAME = ORCL)
)
)


Startup the listener:

lsnrctl start

Step 25: Create the SPFILE & Password file
-----------
Create the SPFILE:
-----------------
SQL> create spfile from pfile;

Create the Password File:
------------------------
$cd /u01/oracle/ora11g/11.2.0.1/dbs

$orapwd file=orapwORCL password=

Step 26:
----------
Change the compatability version to use the new 11g features:

alter system set compatible='11.1.0.6' scope=spfile;

shu immediate;
startup;

Step 27: Load Product user profile information
----------
This step is needed to tackle the error "Error accessing PRODUCT_USER_PROFILE" when you login to SQLPLUS.

Running script pupbld.sql as SYSTEM user:

SQL> conn system/xxx
SQL> @/u01/oracle/ora11g/11.2.0.1/sqlplus/admin/pupbld.sql

Step 28: Rebuild unusable indexes
----------
Using this script:
SQL> select 'alter index '||OWNER||'.'||INDEX_NAME||' rebuild online parallel 4;'from dba_indexes where status ='UNUSABLE';

Step 29: Gather Statistics on the database
----------
This step is very important for performance on the database.

Gather FIXED OBJECTS stats:
--------------------------
SQL> Execute DBMS_STATS.GATHER_FIXED_OBJECTS_STATS (no_invalidate => FALSE );

Note:"gather fixed objects" is not included in gather_dictionary_stats it is also not included in the the daily gather statistics job. The database does not gather these statistics automatically.

Gather DICTIONARY stats:
-----------------------
SQL> Execute DBMS_STATS.GATHER_DICTIONARY_STATS ();

Gather database statistics:
--------------------------
SQL> EXEC DBMS_STATS.GATHER_DATABASE_STATS(ESTIMATE_PERCENT=>100,METHOD_OPT=>'FOR ALL COLUMNS SIZE SKEWONLY',cascade => TRUE,degree => 4);

Step 30: Fix Invalid objects:
-----------
SQL> @?/rdbms/admin/utlrp

Step 31: lock default accounts
-----------
-Oracle recommends that you lock all Oracle supplied accounts except SYS and SYSTEM.
-Never lock these two accounts or the Enterprise Manager will not work: DBSNMP & SYSMAN

List of Default accounts and their description:

User Description
---- -----------
SYS All of the base tables and views for the database's data dictionary are stored in the schema SYS.
SYSTEM contains additional tables and views that display administrative information and used by Oracle tools.
DBSNMP Supports Oracle SNMP (Simple Network Management Protocol).
OUTLN centrally manage metadata associated with stored outlines.
MDSYS Supports Oracle Spatial.
ORDSYS Supports Oracle interMedia.
ORDPLUGINS Supports Oracle interMedia.
CTXSYS Supports Oracle ConText for advanced linguistic processing of English-language text.
DSSYS Dynamic Services Secured Web Service.
WKSYS support Oracle's Ultrasearch option.
WMSYS store all the metadata information for Oracle Workspace Manager.
XDB support SQL XML management: XML DB
ODM support Oracle Data Mining.
OLAPSYS used to create OLAP metadata structures.
REPADMIN Replication user.
ANONYMOUS support SQL XML management.

Please check this link for full descrition:
http://www.idevelopment.info/data/Oracle/DBA_tips/Database_Administration/DBA_26.shtml

Step 32: Check for Oracle recommended patches
-----------
Metalink Note ID 756671.1 includes the recommended patches starting from release 10.2.0.3 and above.

Also: Note ID 742060.1 includes the most accurate information Oracle can provide for coming releases.

Steps to recover from Logical Corruption Without Backup

Creating a Repair Table

The following example creates a repair table for the users  tablespace.

BEGIN

DBMS_REPAIR.ADMIN_TABLES (

     TABLE_NAME => 'REPAIR_TABLE',

     TABLE_TYPE => dbms_repair.repair_table,

     ACTION     => dbms_repair.create_action,

     TABLESPACE => 'USERS');

END;

/

For each repair or orphan key table, a view is also created that eliminates any rows that pertain to objects that no longer exist. The name of the view corresponds to the name of the repair or orphan key table and is prefixed by DBA_ (for example, DBA_REPAIR_TABLE or DBA_ORPHAN_KEY_TABLE).

The following query describes the repair table that was created for the users  tablespace.

DESC REPAIR_TABLE

 Name                         Null?    Type

 ---------------------------- -------- --------------

 OBJECT_ID                    NOT NULL NUMBER

 TABLESPACE_ID                NOT NULL NUMBER

 RELATIVE_FILE_ID             NOT NULL NUMBER

 BLOCK_ID                     NOT NULL NUMBER

 CORRUPT_TYPE                 NOT NULL NUMBER

 SCHEMA_NAME                  NOT NULL VARCHAR2(30)

 OBJECT_NAME                  NOT NULL VARCHAR2(30)

 BASEOBJECT_NAME                       VARCHAR2(30)

 PARTITION_NAME                        VARCHAR2(30)

 CORRUPT_DESCRIPTION                   VARCHAR2(2000)

 REPAIR_DESCRIPTION                    VARCHAR2(200)

 MARKED_CORRUPT               NOT NULL VARCHAR2(10)

 CHECK_TIMESTAMP              NOT NULL DATE

 FIX_TIMESTAMP                         DATE

 REFORMAT_TIMESTAMP                    DATE

Example: Creating an Orphan Key Table

This example illustrates the creation of an orphan key table for the users tablespace.

BEGIN

DBMS_REPAIR.ADMIN_TABLES (

     TABLE_NAME => 'ORPHAN_KEY_TABLE',

     TABLE_TYPE => dbms_repair.orphan_table,

     ACTION     => dbms_repair.create_action,

     TABLESPACE => 'USERS');

END;

/

The orphan key table is described in the following query:

DESC ORPHAN_KEY_TABLE

 Name                         Null?    Type

 ---------------------------- -------- -----------------

 SCHEMA_NAME                  NOT NULL VARCHAR2(30)

 INDEX_NAME                   NOT NULL VARCHAR2(30)

 IPART_NAME                            VARCHAR2(30)

 INDEX_ID                     NOT NULL NUMBER

 TABLE_NAME                   NOT NULL VARCHAR2(30)

 PART_NAME                             VARCHAR2(30)

 TABLE_ID                     NOT NULL NUMBER

 KEYROWID                     NOT NULL ROWID

 KEY                          NOT NULL ROWID

 DUMP_TIMESTAMP               NOT NULL DATE

Example: Detecting Corruption

The CHECK_OBJECT procedure checks the specified object, and populates the repair table with information about corruptions and repair directives. You can optionally specify a range, partition name, or subpartition name when you want to check a portion of an object.

Validation consists of checking all blocks in the object that have not previously been marked corrupt. For each block, the transaction and data layer portions are checked for self consistency. During CHECK_OBJECT, if a block is encountered that has a corrupt buffer cache header, then that block is skipped.

The following is an example of executing the CHECK_OBJECT procedure for the scott.dept table.

SET SERVEROUTPUT ON

DECLARE num_corrupt INT;

BEGIN

num_corrupt := 0;

DBMS_REPAIR.CHECK_OBJECT (

     SCHEMA_NAME => 'SCOTT',

     OBJECT_NAME => 'DEPT',

     REPAIR_TABLE_NAME => 'REPAIR_TABLE',

     CORRUPT_COUNT =>  num_corrupt);

DBMS_OUTPUT.PUT_LINE('number corrupt: ' || TO_CHAR (num_corrupt));

END;

/

SQL*Plus outputs the following line, indicating one corruption:

number corrupt: 1

Querying the repair table produces information describing the corruption and suggesting a repair action.

SELECT OBJECT_NAME, BLOCK_ID, CORRUPT_TYPE, MARKED_CORRUPT,

       CORRUPT_DESCRIPTION, REPAIR_DESCRIPTION

     FROM REPAIR_TABLE;

OBJECT_NAME                      BLOCK_ID CORRUPT_TYPE MARKED_COR

------------------------------ ---------- ------------ ----------

CORRUPT_DESCRIPTION

------------------------------------------------------------------------------

REPAIR_DESCRIPTION

------------------------------------------------------------------------------

DEPT                                    3            1 FALSE

kdbchk: row locked by non-existent transaction

        table=0   slot=0

        lockid=32   ktbbhitc=1

mark block software corrupt

The corrupted block has not yet been marked corrupt, so this is the time to extract any meaningful data. After the block is marked corrupt, the entire block must be skipped.

Example: Fixing Corrupt Blocks

Use the FIX_CORRUPT_BLOCKS procedure to fix the corrupt blocks in specified objects based on information in the repair table that was generated by the CHECK_OBJECTprocedure. Before changing a block, the block is checked to ensure that the block is still corrupt. Corrupt blocks are repaired by marking the block software corrupt. When a repair is performed, the associated row in the repair table is updated with a timestamp.

This example fixes the corrupt block in table scott.dept that was reported by the CHECK_OBJECT procedure.

SET SERVEROUTPUT ON

DECLARE num_fix INT;

BEGIN

num_fix := 0;

DBMS_REPAIR.FIX_CORRUPT_BLOCKS (

     SCHEMA_NAME => 'SCOTT',

     OBJECT_NAME=> 'DEPT',

     OBJECT_TYPE => dbms_repair.table_object,

     REPAIR_TABLE_NAME => 'REPAIR_TABLE',

     FIX_COUNT=> num_fix);

DBMS_OUTPUT.PUT_LINE('num fix: ' || TO_CHAR(num_fix));

END;

/

SQL*Plus outputs the following line:

num fix: 1

The following query confirms that the repair was done.

SELECT OBJECT_NAME, BLOCK_ID, MARKED_CORRUPT

     FROM REPAIR_TABLE;

OBJECT_NAME                      BLOCK_ID MARKED_COR

------------------------------ ---------- ----------

DEPT                                    3 TRUE

Example: Finding Index Entries Pointing to Corrupt Data Blocks

The DUMP_ORPHAN_KEYS procedure reports on index entries that point to rows in corrupt data blocks. For each index entry, a row is inserted into the specified orphan key table. The orphan key table must have been previously created.

This information can be useful for rebuilding lost rows in the table and for diagnostic purposes.

Note:

This should be run for every index associated with a table identified in the repair table.

In this example, pk_dept is an index on the scott.dept table. It is scanned to determine if there are any index entries pointing to rows in the corrupt data block.

SET SERVEROUTPUT ON

DECLARE num_orphans INT;

BEGIN

num_orphans := 0;

DBMS_REPAIR.DUMP_ORPHAN_KEYS (

     SCHEMA_NAME => 'SCOTT',

     OBJECT_NAME => 'PK_DEPT',

     OBJECT_TYPE => dbms_repair.index_object,

     REPAIR_TABLE_NAME => 'REPAIR_TABLE',

     ORPHAN_TABLE_NAME=> 'ORPHAN_KEY_TABLE',

     KEY_COUNT => num_orphans);

DBMS_OUTPUT.PUT_LINE('orphan key count: ' || TO_CHAR(num_orphans));

END;

/

The following output indicates that there are three orphan keys:

orphan key count: 3

Index entries in the orphan key table implies that the index should be rebuilt. This guarantees that a table probe and an index probe return the same result set.

Example: Skipping Corrupt Blocks

The SKIP_CORRUPT_BLOCKS procedure enables or disables the skipping of corrupt blocks during index and table scans of the specified object. When the object is a table, skipping applies to the table and its indexes. When the object is a cluster, it applies to all of the tables in the cluster, and their respective indexes.

The following example enables the skipping of software corrupt blocks for the scott.dept table:

BEGIN

DBMS_REPAIR.SKIP_CORRUPT_BLOCKS (

     SCHEMA_NAME => 'SCOTT',

     OBJECT_NAME => 'DEPT',

     OBJECT_TYPE => dbms_repair.table_object,

     FLAGS => dbms_repair.skip_flag);

END;

/

Querying scott's tables using the DBA_TABLES view shows that SKIP_CORRUPT is enabled for table scott.dept.

SELECT OWNER, TABLE_NAME, SKIP_CORRUPT FROM DBA_TABLES

    WHERE OWNER = 'SCOTT';

OWNER                          TABLE_NAME                     SKIP_COR

------------------------------ ------------------------------ --------

SCOTT                          ACCOUNT                        DISABLED

SCOTT                          BONUS                          DISABLED

SCOTT                          DEPT                           ENABLED

SCOTT                          DOCINDEX                       DISABLED

SCOTT                          EMP                            DISABLED

SCOTT                          RECEIPT                        DISABLED

SCOTT                          SALGRADE                       DISABLED

SCOTT                          SCOTT_EMP                      DISABLED

SCOTT                          SYS_IOT_OVER_12255             DISABLED

SCOTT                          WORK_AREA                      DISABLED

10 rows selected.

Manual upgrade from 9i to 10g Release 2

Manual upgrade from 9i to 10g Release 2

This procedure describes the steps necessary to manually upgrade a database from 9.2.x to 10.2.x. It assumes that you have already installed 10g onto the server. Of course, it is essential that you take a backup of your database before attempting any upgrade.

1. Compile any invalid objects
@?/rdbms/admin/utlrp.sql

2. Create a sysaux tablespace
Having a sysaux tablespace is a requirement in 10g. So, if you haven't already got one, create one now.
create tablespace sysaux
datafile '<file_name>' size 512M
extent management local
segment space management auto
/

3. Run utlu102i.sql
This utility script checks that the database is ready to be upgraded to 10g. It also identifies any actions that need to be taken. The script is located in the 10g oracle home, so you will need to specify the full path to it.
@/u01/app/oracle/product/10.2.0/db_1/rdbms/admin/utlu102i.sql

Review the output and make any necessary alterations. Make a note of how many invalid objects there are.

4. Shut the database down with either normal or immediate
shutdown immediate

5. Copy the spfile (or pfile) and the password file from the existing home to the 10g one.
cp ${ORACLE_HOME}/dbs/*${ORACLE_SID}* <new_home>/dbs/

6. Edit oratab
Alter /etc/oratab (or /var/opt/oracle/oratab) to point to the10g home. Once done, rerun oraenv to bring the alteration into effect.

7. Upgrade the database
sqlplus "/ as sysdba"

startup upgrade
This next bit is the upgrade itself. It takes roughly half an hour to complete. Spool the output to a file so that you can review it afterward.
@?/rdbms/admin/catupgrd.sql

8. Recompile any invalid objects
@?/rdbms/admin/utlrp.sql
Compare the number of invalid objects with the number noted in step 3. It should hopefully be the same or less.

9. Then check the status of the upgrade
@?/rdbms/admin/utlu102s.sql

10. Alter or remove initialisation parameters
Temporarily creating a pfile is the easiest way.
create pfile from spfile;

shutdown immediate

vi ${ORACLE_HOME}/dbs/init${ORACLE_SID}.ora
Alter/remove parameters identified in step 9. Set compatible to 10.2.0.0.0
startup

create spfile from pfile;

shutdown immediate

startup

That's it!

Pre-Requiste for R12 Installation

How to Install Oracle EBS R12 on Redhat Enterprise Linux 5.5

Before we begin the wild ride, there a few modifications that needs to be done to the system, a few packages need to be installed. I’ll assume that you have searched for quite a while and maybe you even tried to install the damn thing and ran into errors, so I’ll get right into the process. Here what we’re going to do:

1.    Install Development Tools

2.    Install required packages

3.    Modify the System Configuration and Kernel (don’t panic)

4.    Create Required Users

5.    Install Oracle Apps

Install Development Tools

1	yum groupinstall "Development Tools"

Install required packages

You can either install the following packages using yum or download this file which include all the files.

1.    openmotif21-2.1.30-11.EL5.i386.rpm

2.    xorg-x11-libs-compat-6.8.2-1.EL.33.0.1.i386.rpm

3.    elfutils-libelf-devel-0.125

4.    elfutils-libelf-devel-static-0.125

5.    libaio-devel-0.3.106

6.    unixODBC-2.2.11

7.    unixODBC-devel-2.2.11

Note: You need to make the following modifications after installing openmotif

1 2	$ unlink /usr/lib/libXtst.so.6 $ ln -s /usr/X11R6/lib/libXtst.so.6.1 /usr/lib/libXtst.so.6

Modify the System Configuration and Kernel

Open /etc/sysctl.conf as root

1 2	$ su - root $ vi  /etc/sysctl.conf

then add the following lines at the end of the file

1 2 3 4 5 6 7 8 9 10 11

#Oracle EBS R12.1.1 Kernel Settings kernel.shmall = 2097152 kernel.shmmax = 4294967295 kernel.shmmni = 4096 kernel.sem = 256 32000 100 142 fs.file-max = 327679 net.ipv4.ip_local_port_range = 10000 65000 net.core.rmem_default=262144 net.core.rmem_max=262144 net.core.wmem_default=262144 net.core.wmem_max=4194304

Now lets apply the new settings

1	$ /sbin/sysctl –p

Add the following lines to the /etc/security/limits.conf file:

1 2 3 4 5 6 7

* hard nofile 65535 * soft nofile 4096 * hard nproc 16384 * soft nproc 2047

Add the following lines to the /etc/resolv.conf file:

1 2	options attempts:5 options timeout:15

Now we need to restart the system so the above modifications gets applied.

Create Required Users

We’ll need to create one group dba and two users, oracle and applmgr. The oracle users will be the owner of the database tier folders and services, while the applmgr user will be the owner of the applications tier.

You can either create the group and the users using GUI or use the following commands:

1 2 3 4

$ su - root $ groupadd dba $ useradd –g dba  –d  /home/oracle oracle $ useradd –g dba  –d  /home/applmgr applmgr

Install Oracle Apps

Before we start the installation we need first to create the installation directory. We will name the directory ebs and create at root /.

1 2 3 4 5

$ su - root $ cd / $ mkdir ebs $ chown oracle:dba ebs $ chmod 777 ebs

Now we can start the rapid install wizard. I’ll not be using a staging area but the following applies to both installing from a staging area or from Oracle’s EBS media pack DVDs.
I’ll assume that the DVD-Rom is mounted at /media/cdrom.

1 2 3

// run the following as the oracle user, not root $ cd /media/cdrom/Disk/rapidwiz $ ./rapidwiz