9i to 10g RAC Upgrade on Linux

7/27/2019 9i to 10g RAC Upgrade on Linux

1/31

Generic Linux Upgrade fromOracle9iReal Application Clustersto Oracle10gR1 Real ApplicationClusters Using Database Upgrade

Assistant (DBUA)An Oracle White PaperFebruary 2005

Version 1.1 18.04.2005


2/31

Introduction........................................................................................................3Oracle10gREAL APPLICATION ClusterS UPGRADE STEPS ............3

Prepare to Upgrade.......................................................................................3Test the Upgrade Process ............................................................................ 4Test the Upgraded Test Database .............................................................. 4Prepare and Preserve the Production Database .......................................4Upgrade the Production Database .............................................................4Enable New Features in the Production Database..................................5New SYSAUX Tablespace ..........................................................................5

Prepare and check your existing Oracle 9iReal Application ClustersInstallation ..........................................................................................................6Operating System Requirements for Oracle10gReal Application Clusters onLINUX................................................................................................................7

Operating System requirements..................................................................7User and Group requirements ....................................................................7

Installing Oracle10gReal Application Clusters .............................................7Oracle10gCRS Installation..........................................................................7Oracle10gDatabase Intallation .................................................................10

DBUA using an existing srvm configuration from oracle9i......................12Run the Oracle Net Configuration Assistant (NetCA) .........................12DBUA turns off ARCHIVE LOG mode during upgrade....................13Run DBUA ..................................................................................................14

DBUA without using an existing srvm configuration from oracle9i.......19POST- upgrade steps ......................................................................................24

Performance.................................................................................................24Verify your RAC Installation.....................................................................25Backup the Voting and OCR device........................................................26NTP Protocol ..............................................................................................26

REFERENcES ................................................................................................27Troubleshooting...............................................................................................28

Tracefiles and Debugging .......................................................................... 28Known Bugs ................................................................................................28

Appendix A ...................................................................................................... 29Appendix A ...................................................................................................... 29

Parameters....................................................................................................29New Processes.............................................................................................30

Generic Linux Upgrade from Oracle9iReal Application Clusters to Oracle10gR1 Real Application Clusters Using DBUA Page 2


3/31

Generic Linux* Upgrade from Oracle9iReal Application

Clusters to Oracle10gR1 Real Application Clusters Using DBUA

INTRODUCTION

The recommended method to upgrade from one Oracle release to the next is to

use the Database Upgrade Assistant (DBUA). This document focuses on the

upgrade part of DBUA from Oracle9iReal Application Clusters Release to the

Oracle10gReal Application Clusters Release on Linux x86.

* The DBUA steps are identical on any Linux platform such as IA64 / x86_64.

ORACLE10gREAL APPLICATION CLUSTERS UPGRADE STEPS

Prepare to upgrade

Test the upgrade process

Test the upgraded test database

Prepare and preserve the production database

Upgrade the production database Tune and adjust the new production database

Parameters

New Processes

SYSAUX tablespace

Prepare to Upgrade

Become familiar with the features of the new Oracle Database 10grelease and

determine your upgrade method.

There are two possibilities: manual upgrade or using the DBUA, which is the

recommended way toupgrade a Real Application Clusters database.

Define home directories for the new Oracle Database 10grelease. The Cluster

Ready Services (CRS)installation ($ORA_CRS_HOME), and if you intend to



4/31

use ASM, the ASM home directory ($ORA_ASM_HOME). Prepare a backup

strategy in the event that your upgrade fails and develop pre-production test

plans.

Test the Upgrade Process

Perform a test upgrade using a test database. The test upgrade should be

conducted in an environment created for testing and should not interfere withthe actual production database. Ideally, the test environment should resemble as

closely as possible, the structure and environment of the production database.

Datasets, runtime simulation, and workload should be the same as your

production environment.

Test the Upgraded Test Database

Perform the planned tests on the test database that was upgraded to the new

Oracle Database 10grelease.

Compare results, noting anomalies like errors, between the Oracle10gReal

Application Clusters test database and on the production database.

Investigate ways to correct any anomalies you find and then implement the

corrections. You may consider using the new tools available in Oracle10gReal

Application Clusters to identify and correct these runtime anomolies. These

tools include Automatic Workload Repository (AWR) and the SQL Tuning

Advisor (see the Oracle Database 10gdocumentation for futher details).

Do not upgrade production users to the new Oracle Database until all of the

applications have been tested and you have ensured that they operate properly

on the test database.

Prepare and Preserve the Production Database

Prepare the current production database as appropriate to ensure that the

upgrade to the new Oracle Database 10grelease will succeeds.

Check your production database log files for are any errors.

Take performance data (AWR reports) from all of the nodes and

identify any performance bottlenecks.

Perform a full backup of the current production database.

Schedule the downtime required for backing up and upgrading the production

database.

Upgrade the Production Database

Upgrade the production database to the new Oracle Database 10grelease.

After the upgrade, perform a full backup of the production database and

perform post-upgrade tasks.



5/31

Enable New Features in the Production Database

Determine which features of the Oracle Database 10grelease that you want to

use and modify your applications, if necessary, to use the new features. Note,

these features should have been defined and fully tested in the Oracle10gReal

Application Clusters test environment prior to the upgrade.

During the upgrade, multi-versioning can be a useful feature because you can

keep multiple copies of the same database on one computer. You can use theexisting release as your production environment while you test the new release.

See Oracle Database Upgrade Guide10g Release 1 (10.1)

Part No. B10763-02 pg. 1-6 for more information.

New SYSAUX Tablespace

This section describes the minimum size for the SYSAUX tablespace, which is

required in Oracle Database 10g. The SYSAUX tablespace must be created after

the new Oracle Database 10grelease is started and BEFORE the upgrade scripts

are invoked - this is done by DBUA automatically.

The SYSAUX tablespace, introduced in Oracle Database 10gRelease 10.1, servesas a compatibility and interoperability auxillary tablespace to the SYSTEM

tablespace. Because SYSAUX is the default tablespace for many Oracle10g

features and products that previously required their own tablespaces, it reduces

the number of tablespaces that you must maintain.

Almost all tools now place their objects in SYSAUX, for example, the Automatic

Workload Repository (AWR) has to be located there. The SYSAUX tablespace

can't be deleted or renamed and must be created with a minimal size or 240MB.

The recommended size is 500MB. Using DBUA the SYSAUX tablespace will be

created automatically.

To monitor which tools or procedures are using the SYSAUX tablespace selectfrom V$SYSAUX_OCCUPANTS . An example of the output is as follow:

OCCUPANT_NAME SCHEMA_N MOVE_PROCEDURE-------------- -------- --------------------------------LOGMNR SYSTEM SYS.DBMS_LOGMNR_D.SET_TABLESPACELOGSTDBY SYSTEM SYS.DBMS_LOGSTDBY.SET_TABLESPACEAO SYS DBMS_AW.MOVE_AWMETAXSOQHIST SYS DBMS_XSOQ.OlapiMoveProcODM DMSYS MOVE_ODMSDO MDSYS MDSYS.MOVE_SDOWM WMSYS DBMS_WM.move_procEM SYSMAN emd_maintenance.move_em_tblspcTEXT CTXSYS DRI_MOVE_CTXSYSULTRASEARCH WKSYS MOVE_WK



6/31

PREPARE AND CHECK YOUR EXISTING ORACLE 9iREAL APPLICATIONCLUSTERS INSTALLATION

Verify that the existing Oracle9iReal Application Clusters instances are running

without issues. To ensure optimal performance in an Oracle10gReal Appliction

Clusters database, all performance issues should be addressed prior to the

migration.

The Oracle9iOracle Cluster Manager called ORACM coexists with the new

Oracle10gCRS. No changes to the configuration files for the Oracle9iOracle

Cluster Manager are necessary.

During the upgrade, the DBUA determines if it is running in a cluster

environment. If not, the selected database is assumed to be "Single instance" by

default. If DBUA identifies a cluster environment, it then verifies that the

selected database exists in the Oracle10gOracle Cluster Repository (OCR).

If the Oracle Database 10gexists then the DBUA retrieves all of the information

relative to the selected database in from the OCR. During the CRS installation

the Oracle9iReal Application Clusters file specified in

/var/opt/oracle/srvConfig.loc is migrated to the OCR and it populates the

OCR with all relevant Oracle9idatabase configuration information.

If the OCR does not have the Oracle9idatabase configuration information, then

DBUA checks the /etc/oratab entries on remote nodes for the same database

with matching $ORACLE_HOME(s). If the DBUA identifies matching

$ORACLE_HOME(s) in the /etc/oratab files (local and remote), it assumes

that it is a cluster database and asks the user for the local instance name. Once it

gets the local instance details DBUA connects to the Oracle9iinstance and

gathers database information from global views to populate the Oracle10gOCR.

From this point on, DBUA uses the Oracle10gOCR to process globalconfiguration information for the Oracle9iand Oracle10gdatabases.

Please check your /etc/oratab files on all of the nodes for equivalence.

Use the Oracle9i $ORACLE_HOME/bin/srvctl status database

d command to determine which databases are registered within

the srvm.dbf.



7/31

OPERATING SYSTEM REQUIREMENTS FOR ORACLE10gREALAPPLICATION CLUSTERS ON LINUX

Operating System requirements

Prior to the installation, check if the operating system version and patch

upgrades meet the Oracle10grequirements. Read the prerequisites documented

in the Oracle Real Application Clusters Installation and Configuration Guide

10g Release 1 (10.1) for AIX-Based Systems, Apple Mac OS X, HP-UX, HP

Tru64 UNIX, Linux, Solaris Operating System, and Windows Platforms

Part No. B10766-08

User and Group requirements

If the oracle user exists, but its primary group is not oinstall or it is not a

member of the appropriate OSDBA or OSOPER groups, then enter the

following command to modify it. Specify the primary group using the -g

option and any required secondary groups using the -G option:

# /usr/sbin/usermod -g oinstall -G dba[,oper] oracle

Please read chapter 5 Pre-Installation Tasks for RAC on Linux from the Real

Application Clusters Installation and Configuration Guide 10g Release.

INSTALLING ORACLE10gREAL APPLICATION CLUSTERS

The Oracle10gReal Application Clusters installation has two phases. First the

CRS / CSS installation in a separate HOME called $ORA_CRS_HOME and

second the RDBMS installation in the $ORACLE_HOME.

Oracle10gCRS Installation

During the CRS installation the user who is installing Oracle10gmust be able toread and write to the Oracle9ioraInventory. If a different user will perform the

installation then this user must be in the same group as the Oracle9iuser.

Confirm that the Oracle10ginstalling user is in the correct group by issuing the

command:

id as either user oracle9 or user oracle10

uid=502(oracle10) gid=54(oinstall) groups=54(oinstall),55(dba)uid=501(oracle9) gid=54(oinstall) groups=54(oinstall),55(dba)

If a Global Service Daemon (GSD) from Oracle9i, Release 9.2 or earlier, is

running, then stop it before installing Oracle Database 10g CRS by executing the

following command from the Oracle9iGSDs Oracle home:$ORACLE_HOME/bin/gsdctl stop



8/31

__________________________________________________________

Note:

If a shared srvm config file specified in /var/op/oracle/srvConfig.loc exists in

Oracle9i, then this file will be used as Oracle10gOCR file. During the CRS

installation a OCR file location and a voting file location is requested. Before

running the $ORA_CRS_HOME/root.sh on the first node change the

CRS_OCR_LOCATION variable defined $ORA_CRS_HOME/root.sh (line

number 212) to reflect the 9i srvm.dbf:

CRS_OCR_LOCATION=/ocfs_10g/9i_oracm/srvm.dbf

This step must be performed on all nodes.

The /etc/oracle/ocr.loc file will have the pointer to the in Oracle9i specified

/var/opt/srvConfig.loc, srvm.dbf file eg.

cat /etc/oracle/ocr.lococrconfig_loc=/ocfs_10g/9i_oracm/srvm.dbflocal_only=FALSE

$ORA_CRS_HOME/root root.sh will create this at the section

# 9.2 installed previouslyif [ -f "$OCRCONFIG" ]; then

# srvConfig.loc file exists, So take this location ocr.locSRV_OCRLOC=`$AWK -F= '/srvconfig_loc/ {print $2}' < $OCRCONFIG`

if [ "$SRV_OCRLOC" = "/dev/null" ]; then# Old OCR location is already invalidated. So ignore it# take the location entered by user to polulate ocr.locSRV_OCRLOC=$OCRCLOC

Fi

____________________________________________________

After running the $ORA_CRS_HOME/root.sh script, the /etc/oracle/ocr.loc

will define the location of the OCR file.

The Oracle9ipointer to the srvm file will be modified to point to /dev/null.

cat /var/opt/oracle/srvConfig.locLocal_only=FALSEsrvconfig_loc=/dev/null

After successfully running $ORA_CRS_HOME/root.sh on all of the nodes, the

Oracle 10g CRS and the Oracle9ioracm stack will both be up and running.

To confirm successful execution of the $ORA_CRS_HOME/root.sh script onall of the nodes, run $ORA_CRS_HOME/bin/ocrcheck as root, the version

should be version2:



9/31

Status of Oracle Cluster Registry is as follows :Version : 2Total space (kbytes) : 262144Used space (kbytes) : 404Available space (kbytes) : 261740

Cluster registry integrity check succeeded___________________________________________________________

Note:

After the language selection screen appears during the CRS installation the

following error message might appear if the srvm.dbf is on an OCFS mounted

drive. Then try the following workaround:

Before installing CRS, move /var/opt/oracle/srvConfig.loc to a

backup location. Afterwards while doing the CRS Install on the "Cluster

Node Selection" screen move /var/opt/oracle/srvConfig.loc back and

continue with the installation.

___________________________________________________________

Figure 1 - Seeing this error message please apply workaround from Bug: 3940214 noted

above.



10/31

Oracle10gDatabase Intallation

The installation performs the same steps like any other Oracle10ginstallation.

But during the installer session it will discover that there is an existing Oracle9i

database installed and the Oracle Universal Installer (OUI) will run the two

additional stepsas described in this section.

Figure 2 - OUI discovers that a database from a previous version is installed.



11/31

Figure 3 - All installed Oracle9i databases are listed and can be choosen for upgrade.

The installation is complete when the $ORACLE_HOME/root.sh script

completes. The Virtual IP Configuration Assistant (VIPCA) is invoked from

within the $ORACLE_HOME/root.sh script. Confirm that the VIP is

configured and running by issuing the following command:

ifconfig

eth0 Link encap:Ethernet HWaddr 00:B0:D0:21:D8:84inet addr:140.86.194.88 Bcast:140.86.199.255

Mask:255.255.248.0inet6 addr: fe80::2b0:d0ff:fe21:d884/64 Scope:LinkUP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1RX packets:5752434 errors:0 dropped:0 overruns:1 frame:0TX packets:126279 errors:0 dropped:0 overruns:0 carrier:0collisions:774 txqueuelen:100RX bytes:715754138 (682.5 Mb) TX bytes:69324548 (66.1 Mb)Interrupt:9 Base address:0xdc80

eth0:1 Link encap:Ethernet HWaddr 00:B0:D0:21:D8:84inet addr:140.86.194.104 Bcast:140.86.194.255

Mask:255.255.255.0UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1Interrupt:9 Base address:0xdc80

In this example the VIP interface eth0:1 is running on NICeth0.



12/31

The Global Service Daemon (GSD) of Oracle9ishould not be running. This can

be verified with gsdctl stat on all of the nodes. Only the GSD from

Oracle10gshould be running.

To verify all of the Oracle10gnode applications resource statuses, including

GSD and VIP, run the following command

$ORA_CRS_HOME/bin/crs_stat t

An example of the output is as follows:

Name Type Target State Host------------------------------------------------------------ora.mars.gsd application ONLINE ONLINE marsora.mars.ons application ONLINE ONLINE marsora.mars.vip application ONLINE ONLINE marsora.venus.gsd application ONLINE ONLINE venusora.venus.ons application ONLINE ONLINE venusora.venus.vip application ONLINE ONLINE venus

The Oracle10gGSD is running for compatibilty to support Oracle9iclients like

SRVM, and the EM AGENT. Oracle10gclients are not using the Oracle9i GSD

anymore. The above output reflects node applications status for all resources on

the nodes MARS and VENUS. Node application descriptions can be found in

the Oracle10gdocumention, Oracle Real Application Clusters Administrators

Guide. Once the installation is complete, the DBUA runs to upgrade your

Oracle9idatabase.

DBUA USING AN EXISTING SRVM CONFIGURATION FROM ORACLE9i

DBUA may be used with an existing SRVM configuration file or without this

file. The steps to follow for both scenarios are outlined below.

After installing the new Oracle Database 10grelease and specifying an instance

to upgrade, the DBUA is started automatically. Otherwise, the DBUA can be

started in the stand alone mode after the installation is complete by running:

$ORACLE_HOME/bin/dbua

Run the Oracle Net Configuration Assistant (NetCA)

If you are upgrading from Oracle9iand a listener was not configured in the

Oracle9irepository, then run Oracle10gNetCA to configure the listener

protocol address and service information for the new Oracle Database 10g,

including a listener.ora file. An Oracle Database 10glistener is required for an

Oracle Database 10gdatabase. Previous versions of the listener are notrecommended for use with an Oracle10gdatabase. However, it is possible to use

an Oracle Database 10glistener with previous versions of the Oracle database

for Oracle 9i/ Oracle10gco-existence and backwards compatibility.



13/31

___________________________________________________________

Note:

It is important to run NetCA before running the DBUA. Although DBUA does

not create or modify the listener.ora file, DBUA registers the database in

the listener.ora file in the new Oracle Home as it upgrades the database.

___________________________________________________________

To check whether resources are online or offline use the following command:

$ORA_CRS_HOME/bin/crs_stat t

Name Type Target State Host------------------------------------------------------------ora....RS.lsnr application ONLINE ONLINE marsora.mars.gsd application ONLINE ONLINE marsora.mars.ons application ONLINE ONLINE marsora.mars.vip application ONLINE ONLINE marsora....US.lsnr application ONLINE ONLINE venusora.venus.gsd application ONLINE ONLINE venusora.venus.ons application ONLINE ONLINE venus

ora.venus.vip application ONLINE ONLINE venus

DBUA turns off ARCHIVE LOG mode during upgrade

The Oracle 10.1.0.x DBUA disables archiving during the upgrade (the original

archiving mode is restored after the upgrade is done). This improves upgrade

performance. Disabling archiving may cause problems in conjunction with Data

Guard or Standby Databases. The DBUA gets the information to turn OFF

archiving during the upgrade from an XML file which is generated by a PL/SQL

package.

___________________________________________________________

Note:

You can make the following one-word change in this PL/SQL file to enable

ARCHIVE LOG mode during the upgrade:

a) Open the file $10gOH/rdbms/admin/utlu101x.sql

b) Go to line no.1234 or search for a line with textArchiveLog

Modify the line1234 '');

to

1234 '');

c) Save the file and run DBUA

RESULT: This will cause the database to be upgraded in theArchive log mode.

___________________________________________________________



14/31

Modify $ORACLE_HOME/bin/dbua $LD_LIBRARY path variable

Due to a bug the DBUA can fail with a PRKH-1001 HASCONTEXT

INTERNAL ERROR (UNEXPECTED CLSS ERROR:[12] error message

during the database information discovery. The workaround is as follows:

Before starting the $ORALE_HOME/bin/dbua , add

/etc/ORCLcluster/oracm/lib to the LD_LIBRARY_PATH in the

$ORALE_HOME/bin/dbua script line 135.

# Set the LD_LIBRARY_PATH to set the path for shared objects# Do not set it on AIXif [ $PLATFORM != IBM_AIX ]; thenLD_LIBRARY_PATH=/etc/ORCLcluster/oracm/lib:$LIB32_DIR:$ORACLE_HOME/network/lib32:$LIB_DIR:$ORACLE_HOME/network/lib:$LD_LIBRARY_PATHexport LD_LIBRARY_PATH;fi

Run DBUA

Below are the steps invoked to perform a successful upgrade.

Figure 4 - All instances running on the server from previous Oracle9ireleases are listed.



15/31

Figure 5 - Choose an instance, type the sys password and select next. Now the database

information will be gatherd. If in Oracle9i the shared configuration file srvm was used the

information is already migrated to the Oracle10g OCR.

Figure 6 - Specify the SYSAUX tablespace, minimum size required is 240MB.



16/31

Figure 7 - Select to recompile all invalid objects after the upgrade. In multiple CPU

environments another checkbox offeres to choose the number of parallel threads for

recompilation.

Figure 8 - Select I would like this tool to backup the database if DBUA should perform

a backup.



17/31

Figure 9 - Specify the Enterprise Manager control.

Figure 10 At the Database Services screen additional Services can be added if needed.



18/31

Figure 11 - The Summary screen will display all modifications done during the upgrade.

Figure 12 - The progress bar indicates which component will be upgraded and the

progress. After a successful upgrade the summary screen will display the changes and

modifacations.



19/31

DBUA WITHOUT USING AN EXISTING SRVM CONFIGURATION FROMORACLE9i

___________________________________________________________________

Note:

Please read the section DBUA turns off ARCHIVE LOG mode during

upgrade page 13.

If the DBUA cannot obtain information from an Oracle9isrvm configuration

file, then use the /etc/oratab information, from all of the nodes to discover if an

Oracle9iReal Application Clusters database is installed and then select from

global views to retrieve from an active instance to upgrade to a cluster database.

Therefor, all instances in a cluster must be running prior to running DBUA.

The /etc/oratab entry for the $ORACLE_HOME must be identical on all

nodes for the DBUA to identify a clustered environment.

____________________________________________________________

If DBUA indentifes a clustered environment using the /etc/oratab, then the

DBUA prompts for a local instance name for the identified clustered database.

Figure 13 - At the popup window enter the instance name from the instance where the

DBUA was launched.



20/31

Figure 14 - DBUA will automatically create the SYSAUX tablespace. Minimum

recommended size is 400 MB.

Figure 15 - Select Recompile invalid objects if all invalid ojbects should be

recompiled.



21/31

Figure 16 - Make sure a backup exists before you start the upgrade process.

Figure 17 - Choose yes or no, to configure the Database with Enterprise Manager.



22/31

Figure 18 - During the upgrade process additional services can be created.

Figure 19 - Choose the TAF policy if additional services are added.



23/31

Figure 20 - The Summary screen will display all modifications done during the upgrade.

Figure 21 Now the individual upgrade steps will be performed and after the successful

upgrade to Oracle Database 10g, the detailed Upgrade Results will be displayed. During

the upgrade DBUA will shutdown all instances, start one in exclusive mode and perform

the necessary steps.



24/31

Figure 21 The Upgrade Results screen at the end of the upgrade.

POST- UPGRADE STEPS

Performance

Rule-Based Optimizer Desupported

Starting with Oracle Database 10grelease 10.1, the cost-based optimizer (CBO)

is enabled by default. The rule-based optimizer is no longer supported in release

10.1. As a result, rule and choose are no longer supported as

OPTIMIZER_MODE initialization parameter values and a warning is displayed

in the alert log ifOPTIMIZER_MODE is set to either of these values.

Optimizer Statistics

Collection of optimizer statistics is now automatically performed by default for

all schemas (including SYS), for pre-existing databases upgraded to Oracle

Database 10g, and for newly created Oracle Database 10gdatabases. Gathering



25/31

optimizer statistics on stale objects is scheduled by default to occur daily during

maintenance.

Optimizer statistics are automatically gathered with the job

GATHER_STATS_JOB . This job gathers statistics about all of the objects in the

database that have:

Missing statistics

Stale statistics

This job is created automatically at database creation time and is managed by the

Scheduler. This Scheduler runs this job when the maintenance window is

opened. By default, the maintenance window opens every night from 10p.m. to

6a.m. and all day on weekends. The GATHER_STATS_JOB continues until it

finishes, even if it exceeds the allocated time for maintenance. The duration of

maintenance can be changed.

See Also: Oracle Database Administrator's Guidefor information about the

Scheduler and maintenance tasks

COMPUTE STATISTICS Clause of CREATE INDEX

In earlier releases, the COMPUTE STATISTICS clause ofCREATE INDEX

could be used to start or stop the collection of statistics on an index. This clause

has been deprecated. Oracle Database 10gnow automatically collects statistics

during index creation and rebuild. This clause is supported for backward

compatibility and will not cause errors.

AWR and Statspack

Database performance statistics are now automatically collected by the

AutomaticWorkload Repository (AWR) database component for databases

upgraded to Oracle Database 10g. This data is stored in the SYSAUX tablespace,and is used by the database for automatic generation of performance

recommendations.

If Statspack is used for performance data gathering, then refer to the Statspack

README (ORACLE_HOME/rdbms/admin/spdoc.txt) for directions about

using Statspack in Oracle Database 10gto avoid conflict with the AWR. For

more information regarding performance tuning see the Oracle Database 10g

Performance Tuning Guide.

Verify your RAC Installation

Check if your Private Interconnect is used correctly

Confirm that RAC is using the desired IPC protocol by checking the alert.log to

identify the protocol used.



26/31

cluster interconnect IPC version:Oracle UDP/IP

IPC Vendor 1 proto 2 Version 1.0

PMON started with pid=2

RAC will use the same virtual interconnect selected during CRS install. To

confirm which interconnect is used and where it is defined, use the following

select statement.

select * from x$ksxpia;

ADDR INDX NST_ID P PICK NAME_KSXPIA IP_KSXPIA---------------- ---- ------ - ---- ----------- ---------00000003936B8580 0 1 OCR eth1 10.0.0.1

Pick: OCR Oracle ClusterwareOSD Operating System dependentCI indicates that the init.ora parameter

cluster_interconnects is specified

The ksxpia.pick field indicates where the IPC layer obtains the interconnect

definitions which interface and IP.

Backup the Voting and OCR device

After installing Oracle RAC 10gand after ensuring that the system is functioning

properly, make a backup of the OCR and Voting disk. In addition, make a

backup of the OCR and Voting disk contents after you complete any node

additions or node deletions and after running any de-installation procedures. Use

dd or copy depending on whether your OCR and Voting disk are on raw devices

or Oracle Cluster Filsystem files.

Please see Note.279793.1 for additional information

NTP Protocol

We recommend setting up the Network Time Protocol (NTP) on all cluster

nodes. This synchronizes the clocks among all of the nodes, and facilitates

analysis of tracing information based on timestamps.

Note that adjusting clocks by more than 15 minutes can cause instance evictions.

It is strongly advised to shutdown all instances before date/time adjustments.



27/31

REFERENCES

Oracle Database Upgrade Guide 10g Release 1 (10.1)Part Number B10763-02

Oracle Real Application Clusters Installation and Configuration Guide 10g

Release 1 (10.1) for AIX-Based Systems, Apple Mac OS X, hp HP-UX, hp

Tru64 UNIX, Linux, Solaris Operating System, and Windows Platforms PartNo. B10766-08

Note: 265831 Automatic Checkpoint Tuning in 10g

Note: 276301.1 DBUA Took Primary to NOARCHIVELOG Mode

Note: 222627.1 Migrating to the Cost-Based Optimizer

Migrating Databases To and From ASM with Recovery Manager see

Oracle Database Backup and Recovery Advanced User's Guide

10g Release 1 (10.1)Part Number B10734-01



28/31

TROUBLESHOOTING

Tracefiles and Debugging

To turn on DBUA tracing modify $ORACLE_HOME/bin/dbua at the end of

the script and add -DTRACING.ENABLED=true -DTRACING.LEVEL=2 in

front of the classpath, as follows:

$JRE_DIR/bin/java -Dsun.java2d.font.DisableAlgorithmicStyles=true -DORACLE_HOME=$OH -mx64m -DTRACING.ENABLED=true -DTRACING.LEVEL=2 -classpath $CLASSPATHoracle.sysman.assistants.dbma.Dbma $*

During the migration DBUA writes trace files to

$ORACLE_HOME/assistants/dbma/logs and in

$ORACLE_BASE/admin/upgrade//*

Known Bugs

Bug:3724769 DBUA does not cover the non-existance from a listener in 9iBug:4040264 DBUA fails with error PRKR-100: cluster database does not exist

Bug:4147045 DBUA fails with PRKH-1001 HAScontext internal error

(unexpected CLSS error:[12])

Bug: 3690107 DBUA takes the db to noarchivelogmode creating a gap in the

standby database

Bug: 3940214 10.1.0.2 and 10.1.0.3 CRS installations fail on existing 9.2 RAC

environment



29/31

APPENDIX A

Parameters

Check the existing Oracle9iReal Application Clusters database parameter file for

deprecated parameters and the Oracle10gReal Application Clusters database for

obsolete parameters.

Deprecated Parameters

SQL> select name from v$parameter where isdeprecated='TRUE';

NAME-----------------------------buffer_pool_keep (DB_KEEP_CACHE_SIZE in 10g)buffer_pool_recycle (DB_RECYCLE_CACHE_SIZE in 10g)drs_start (DG_BROKER_START in 9.2)fast_start_io_target (FAST_START_MTTR_TARGET in 9.0)global_context_pool_sizelock_name_spacelog_archive_startmax_enabled_rolesparallel_automatic_tuning

parallel_server (CLUSTER_DATABASE in 9.0)parallel_server_instances (CLUSTER_DATABASE_INSTANCES in 10g)plsql_compiler_flags (PLSQL_CODE_TYPE and PLSQL_DEBUG)serial_reuse

Obsolete Parameters

SQL> select name from v$obsolete_parameter;

DBLINK_ENCRYPT_LOGIN ORACLE_TRACE_COLLECTION_NAMEHASH_JOIN_ENABLED ORACLE_TRACE_COLLECTION_PATHLOG_PARALLELISM ORACLE_TRACE_COLLECTION_SIZEMAX_ROLLBACK_SEGMENTS ORACLE_TRACE_ENABLEMTS_CIRCUITS ORACLE_TRACE_FACILITY_NAMEMTS_DISPATCHERS ORACLE_TRACE_FACILITY_PATHMTS_LISTENER_ADDRESS PARTITION_VIEW_ENABLEDMTS_MAX_DISPATCHERS PLSQL_NATIVE_C_COMPILERMTS_MAX_SERVERS PLSQL_NATIVE_LINKER

MTS_MULTIPLE_LISTENERS PLSQL_NATIVE_MAKE_FILE_NAMEMTS_SERVERS PLSQL_NATIVE_MAKE_UTILITYMTS_SERVICE ROW_LOCKINGMTS_SESSIONS SERIALIZABLEOPTIMIZER_MAX_PERMUTATIONS TRANSACTION_AUDITINGUNDO_SUPPRESS_ERRORS

New init.ora parameters

asm_diskgroups log_archive_configasm_diskstring log_archive_local_firstasm_power_limit plsql_code_typedb_flashback_retention_target plsql_debugdb_recovery_file_dest plsql_optimize_leveldb_recovery_file_dest_size plsql_warningsdb_unique_name resumable_timeoutddl_wait_for_locks sga_target

fileio_network_adapters skip_unusable_indexesgcs_server_processes smtp_out_serverinstance_type sp_nameldap_directory_access sqltune_categorystreams_pool_size



30/31

New important defaults

LOG_ARCHIVE_FORMAT: should include %s, %t, and %r

PGA_AGGREGATE_TARGET:not set: enabled with 20% of the SGA0: disabledValue set: PGA=Value

STATISTICS_LEVEL = TYPICAL [Default]collects data and saves it to the AWR (see also: v$statistics_level)

FAST_START_MTTR_TARGET = 0not set: enables automatic checkpointing0: disables automatic checkpointingValue set: enables automatic checkpointing

New Processes

There are a few new background processes who are important for Oracle

Database 10g.

For Monitoring purposesMMAN == Memory Manager (? SGA)MMON == Manageability Monitor (? AWR)MMNL == Manageability Monitor Light (? AWR)For Backup&Recovery and Flashback

CTWR == Change Tracking Writer (? CTF/RMAN)RVWR == Recovery Writer (? Flashback Logs)For Automatic Storage ManagerASMB == ASM BackgroundRBAL == ASM Rebalance masterARBn == ASM Rebalance 0..nFor DataGuardNSV == Data Guard Net SlaveINSV == Data Guard Instance-Slave

There are several new operating system processes for CRS and the Cluster

Synchronization Services (CSS) such as:

ocssd.bincrsd.binevmd.bin



31/31

White Paper Title: Generic Linux Upgrade from Oracle9iReal Application Clusters to Oracle10gR1 Real Application Clusters Using DBUA .

Author: Knapp Roland

Contributing Authors: Mike Dietrich, John McHugh

Oracle Corporation

World Headquarters

500 Oracle Parkway

Redwood Shores, CA 94065

U.S.A.

Worldwide Inquiries:

Phone: +1.650.506.7000

Fax: +1.650.506.7200

www.oracle.com

Copyright 2003, Oracle. All rights reserved.

This document is provided for information purposes only

and the contents hereof are subject to change w ithout notice.

This document is not warranted to be error-free, nor subject toany other warranties or conditions, whether expressed orally

or implied in law, including implied warranties and conditions of

merchantability or fitness for a particular purpose. We specifically

disclaim any liability with respect to this document and no

contractual obligations are formed either directly or indirectly

by this document. This document may not be reproduced or

transmitted in any form or by any means, electronic or mechanical,

for any purpose, without our prior written permission.

Oracle is a registered trademark of Oracle Corporation and/or its

affiliates. Other names may be trademarks of their respective owners.

Documents

9i to 10g RAC Upgrade on Linux