4 After Upgrading to the New Release

Update Environment Variables (Linux and UNIX Systems Only)

If your operating system is Linux or UNIX, then make sure that the following environment variables point to the new Oracle Database 11g Release 1 (11.1) directories:

• 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 1 (11.1) home.

Upgrade the Recovery Catalog

For complete information about upgrading the recovery catalog and the UPGRADE CATALOG command, see the Oracle Database Backup and Recovery User's Guide.

Upgrade Statistics Tables Created by the DBMS_STATS Package

If you created statistics tables using the DBMS_STATS.CREATE_STAT_TABLE procedure, then upgrade these tables by executing the following procedure:

EXECUTE DBMS_STATS.UPGRADE_STAT_TABLE('scott', 'stat_table'); 

In the example, SCOTT is the owner of the statistics table and STAT_TABLE is the name of the statistics table. Execute this procedure for each statistics table.

Upgrade Externally Authenticated SSL Users

If you are upgrading from Oracle9i Release 2 (9.2) or Oracle Database 10g Release 1 (10.1), and you are using externally authenticated SSL users, then you must run the following command to upgrade those users:

ORACLE_HOME/rdbms/bin/extusrupgrade --dbconnectstring 
<hostname:port_no:sid> --dbuser <db admin> --dbuserpassword 
<password> -a

Install Oracle Text Supplied Knowledge Bases

The Oracle Text supplied knowledge bases are part of the companion Oracle Database 11g Release 1 (11.1) products and are not immediately available after an upgrade to Oracle Database 11g Release 1 (11.1). Any Oracle Text features dependent on the supplied knowledge bases which were available before the upgrade do not function after the upgrade. To reenable such features, you must install the Oracle Text supplied knowledge bases from the installation media.

After an upgrade, all user extensions to the Oracle Text supplied knowledge bases must be regenerated. These changes affect all databases installed in the given Oracle home.

Update Your Oracle Application Express Configuration

If your database originally included Application Express Version 3.0, there is no additional configuration necessary after upgrading to Oracle Database 11g Release 1 (11.1).

If your database was not an Oracle Express Edition (XE) database, but contained a prior version of Application Express (HTML DB), then version 3.0 is automatically installed during the upgrade. You must complete a series of post-installation steps to configure Application Express Version 3.0 for use with Oracle Database 11g. These steps are described in the section on post-installation tasks in the Oracle Database Application Express Installation Guide.

If your database was an Oracle Express Edition (XE) database, it contained a prior version of Application Express tailored for the XE environment. Refer to the OTN document describing the differences between Oracle Database XE Application Express and Application Express 3.0 at:

http://www.oracle.com/technology/products/database/application_express/html/upgrade_apex_for_xe.html

The database administration features available with the XE version of Application Express are not available in version 3.0, but Oracle Enterprise Manager DB Control can, optionally, be installed to provide a graphical interface for database administration.

Configure Fine-Grained Access to External Network Services

Oracle Database 11g Release 1 (11.1) includes fine-grained access control to the UTL_TCP, UTL_SMTP, UTL_MAIL, UTL_HTTP, or UTL_INADDR packages using Oracle XML DB. If you have applications that use one of these packages, you must install Oracle XML DB if it is not already installed. You must also configure network access control lists (ACLs) in the database before these packages can work as they did in prior releases.

The following example first looks for any ACL currently assigned to host_name. If one is found, then the example grants user_name the CONNECT privilege in the ACL only if that user does not already have it. If no ACL exists for host_name, then the example creates a new ACL called ACL_name, grants the CONNECT privilege to user_name, and assigns the ACL to host_name.

DECLARE
  acl_path  VARCHAR2(4000);
BEGIN
  SELECT acl INTO acl_path FROM dba_network_acls
   WHERE host = 'host_name' AND lower_port IS NULL AND upper_port IS NULL;
IF DBMS_NETWORK_ACL_ADMIN.CHECK_PRIVILEGE(acl_path, 
                                         'user_name','connect') IS NULL THEN
    DBMS_NETWORK_ACL_ADMIN.ADD_PRIVILEGE(acl_path,
                                         'user_name', TRUE, 'connect');
END IF;
EXCEPTION
  WHEN no_data_found THEN
    DBMS_NETWORK_ACL_ADMIN.CREATE_ACL('ACL_name.xml',
      'ACL description', 'user_name', TRUE, 'connect');
    DBMS_NETWORK_ACL_ADMIN.ASSIGN_ACL('ACL_name.xml','host_name');
END;
COMMIT;

Enable Oracle Database Vault

If you use Oracle Database Vault, then you were instructed to disable it before upgrading your database. You must now enable Database Vault again.

Deploy Database Vault Administrator (DVA)

You can manually deploy Database Vault Administrator (DVA) to the following Oracle Application Server Containers for J2EE (OC4J) home:

$ORACLE_HOME/oc4j/j2ee/home

Use the following steps to manually deploy the DVA application:

1. Edit the file, $ORACLE_HOME/oc4j/j2ee/home/config/server.xml. Enter the following line just before the last line that reads, </application-server>:

   <application name="dva" path="$ORACLE_HOME/dv/jlib/dva_webapp.ear" auto-start="true" />
   

   For example:

   <application name="dva" path="/u00/app/oracle/oracle/product/dv12/dv/jlib/dva_webapp.ear" auto-start="true" />
   

2. Edit the file, $ORACLE_HOME/oc4j/j2ee/home/config/http-web-site.xml. Enter the following line just above the last line that reads, </web-site>:

   <web-app application="dva" name="dva_webapp" root="/dva" />
   

3. Edit the file, $ORACLE_HOME/oc4j/j2ee/home/config/global-web-application.xml. Search for <servlet-class>oracle.jsp.runtimev2.JspServlet</servlet-class>. Uncomment the following lines after this:

   <init-param>
      <param-name>main_mode</param-name>
      <param-value>justrun</param-value>
   </init-param>
   

4. Create the following directory:

   mkdir -p $ORACLE_HOME/dv/jlib/sysman/config
   

5. Create the database connection configuration file, emoms.properties, in the configuration directory that you just created. Add the following lines to the file:

   oracle.sysman.emSDK.svlt.ConsoleMode=standalone
   oracle.sysman.eml.mntr.emdRepRAC=FALSE
   oracle.sysman.eml.mntr.emdRepDBName=ORACLE_SID
   oracle.system.eml.mntr.emdRepConnectDescriptor=TNS_connection_string
   

   Note:

   • oracle.sysman.eml.mntr.emdRepRAC should be set to TRUE for Oracle Real Application Clusters database.

   • For oracle.sysman.eml.mntr.emdRepConnectDescriptor, you can use an alias from $ORACLE_HOME/network/admin/tnsnames.ora. Alternatively, you can use the following syntax:

     oracle.sysman.eml.mntr.emdRepConnectDescriptor=(DESCRIPTION\=(ADDRESS_LIST\=(ADDRESS\=(PROTOCOL\=TCP) (HOST\=HOSTNAME)(PORT\=PORT))) (CONNECT_DATA\=(SERVICE_NAME\=ORACLE_SID)))
     

6. Start OC4J. Before starting OC4J, ensure that the correct environment variables are set. For example:

   ORACLE_SID=orcl
   export ORACLE_SID
   ORACLE_HOME=/u00/app/oracle/product/10.2/dv
   export ORACLE_HOME
   LD_LIBRARY_PATH=$ORACLE_HOME/bin:$ORACLE_HOME/lib:$ORACLE_HOME/jdbc/lib
   export LD_LIBRARY_PATH
   PATH=$ORACLE_HOME/bin:$ORACLE_HOME/jdk/bin:$PATH
   export PATH
   

   Note:

   LD_LIBRARY_PATH must be set to use the OCI-based JDBC libraries.

   Start OC4J using the following syntax:

   $ORACLE_HOME/jdk/bin/java -Djava.awt.headless=true -DEMDROOT=$ORACLE_HOME/dv/jlib -jar $ORACLE_HOME/oc4j/j2ee/home/oc4j.jar -userThreads -config $ORACLE_HOME/oc4j/j2ee/home/config/server.xml
   

7. You can now access the DVA application. The HTTP port defaults to 8888 for this environment. Use the following URL:

   http://hostname:8888/dva
   

Recommended Tasks After All Database Upgrades

Performing the following tasks is recommended, but not required, after you have upgraded your database.

• Back Up the Database

• Reset Passwords to Enforce Case-Sensitivity

• Upgrade Automatic Storage Management (ASM)

• Add New Features as Appropriate

• Develop New Administrative Procedures as Needed

• Set Threshold Values for Tablespace Alerts

• Migrate From Rollback Segments to Automatic Undo Mode

• Configure Oracle Data Guard Broker

• Migrate Tables from the LONG Data Type to the LOB Data Type

sql> alter system set sec_case_sensitive_logon=false;

SQL> ALTER TABLE Long_tab MODIFY ( long_col CLOB );

Recommended Tasks After Upgrading an Oracle Database 10g Release 1 (10.1) Database

Performing the following tasks is recommended, but not required, after you have upgraded from Oracle Database 10g Release 1 (10.1) or Oracle Database 10g Release 2 (10.2).

• Upgrade Change Data Capture

• Configure Secure HTTP

• Provide Anonymous Access to XML DB Repository Data Through HTTP

Recommended Tasks After Upgrading an Oracle Express Edition Database

An Oracle Express Edition database contains only a subset of the components available in a Standard Edition or Enterprise Edition database. After upgrading to Oracle Database 11g Release 1 (11.1), you can use the Database Configuration Assistant to install additional components into your database. If you did not install Enterprise Manager DB Control during the DBUA upgrade, then you can install it, along with any other components you would like to have in the database.

Change Passwords for Oracle-Supplied Accounts

Depending on the release from which you upgraded, there might be new Oracle supplied accounts. Oracle recommends that you lock all Oracle supplied accounts except for SYS and SYSTEM, and expire their passwords, thus requiring new passwords to be specified when the accounts are unlocked.

You can view the status of all accounts by issuing the following SQL statement:

SQL> SELECT username, account_status
         FROM dba_users
         ORDER BY username;

To lock and expire passwords, issue the following SQL statement:

SQL> ALTER USER username PASSWORD EXPIRE ACCOUNT LOCK;

Migrate Your Initialization Parameter File to a Server Parameter File

If you are currently using a traditional initialization parameter file, then perform the following steps to migrate to a server parameter file:

1. If the initialization parameter file is located on a client computer, then transfer the file from the client computer to the server computer.

   Note:

   If you are using Oracle Real Application Clusters, then you must combine all of your instance-specific initialization parameter files into a single initialization parameter file. Instructions for doing this, and other actions unique to using a server parameter file for cluster databases, are discussed in:

   • Oracle Real Application Clusters Administration and Deployment Guide

   • The Real Application Cluster installation guide for your operating system

2. Create a server parameter file using the CREATE SPFILE statement. This statement reads the initialization parameter file to create a server parameter file. You are not required to start the database to issue a CREATE SPFILE statement.

3. Start up the instance using the newly-created server parameter file.

Upgrade Oracle Text

After an upgrade to Oracle Database 11g Release 1 (11.1), copy the following files from the previous Oracle home to the new Oracle home:

• Stemming user-dictionary files

• User-modified KOREAN_MORPH_LEXER dictionary files

• USER_FILTER executables

These files affect all databases installed in the given Oracle home.

You can obtain a list of the above files by:

1. Looking at $ORACLE_HOME/ctx/admin/ctxf102.txt

2. Executing $ORACLE_HOME/ctx/admin/ctxf102.sql as database user SYS, SYSTEM, or CTXSYS

If your Oracle Text index uses KOREAN_LEXER which was deprecated in Oracle 9i and desupported in Oracle 10g Release 2, see Support Note 300172.1 for further information on manual migration from KOREAN_LEXER to KOREAN_MORPH_LEXER.

Upgrade the Oracle Cluster Registry (OCR) Configuration

If you are using Oracle Clusterware, then you must upgrade the Oracle Cluster Registry (OCR) keys for the database.

Use one of the following options to upgrade the OCR configuration to 11g:

• Use srvconfig from the Oracle Database 11g Release 1 (11.1) Oracle home. For example:

  % srvconfig -upgrade -dbname db_name -orahome pre-11g_Oracle_home
  

• Run srvctl. For example:

  pre-11g_Oracle_home/bin/srvctl remove database -d db_name
  11g_Oracle_home/bin/srvctl add database -d db_name -o 11g_Oracle_home
  11g_Oracle_home/bin/srvctl add instance -d db_name -i instance -n node
  

Adjust the Initialization Parameter File for the New Release

Each release of Oracle Database introduces new initialization parameters, deprecates some initialization parameters, and makes some initialization parameters obsolete. You should adjust the parameter file to account for these changes and to take advantage of new initialization parameters that might be beneficial to your system.

The COMPATIBLE initialization parameter controls the compatibility level of your database. When you are certain that you no longer need the ability to downgrade your database to its original version, set the COMPATIBLE initialization parameter based on the compatibility level you want for your new database.

Configure Enterprise Manager

If you are not yet using Oracle Enterprise Manager to manage your database, install and configure Enterprise Manager Database Control.

If your database is being managed by Oracle Enterprise Manager Database Control or Oracle Enterprise Manager Grid Control, then use the following command to update the configuration:

emca -upgrade (db | asm | db_asm) [-cluster] [-silent] [parameters]

You need to run this from the new Oracle Database 11g Oracle Home. When prompted, provide the Oracle home from which the configuration is being upgraded.

You can also configure Enterprise Manager using DBCA. Select the Configure Database Options option, and then select the Enterprise Manager Repository option.

Set CLUSTER_DATABASE Initialization Parameter

In "Prepare the New Oracle Home", you were instructed to set the CLUSTER_DATABASE initialization parameter to false before upgrading a cluster database. Now that the upgrade is finished, you must set this parameter to true.

Set Environment Variables

If your operating system is Linux or UNIX, then make sure that the following environment variables point to the new Oracle Database 11g Release 1 (11.1) directories:

• 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 1 (11.1) home.

Single-Instance ASM Upgrade

If ASM version 10.2 is installed in Oracle Home 1 (OH1) and the operating system user is orauser, execute the following steps:

1. As orauser, upgrade ASM to release 11.1 using OUI and DBUA. The new ASM release 11.1 should be running in a new Oracle Home 2 (OH2). ASM should still be running as orauser.

2. As orauser, bring down the ASM instance and the listener.

3. As root, run /etc/init.d/init.cssd stop to stop CSS.

4. As a new user (asmuser), install 11.1 in a third Oracle Home (OH3). This should be a software-only installation.

5. As root, run localconfig reset from OH3.

6. Update /etc/oratab so that OH3 is the Oracle home with the +ASM entry.

7. Copy listener.ora, sqlnet.ora, and tnsnames.ora from OH2.

8. Run EMCP to change the ASM instance path and connect-string role.

9. Make sure the disks are owned by asmuser and by OSDBA for ASM. They should also have the O660 permission set.

10. As asmuser, start the listener.

11. As asmuser, start ASM (connect as SYSASM).

12. Run the command, GRANT sysasm TO sys.

Cluster ASM Upgrade

For cluster ASM upgrade, execute the following steps:

1. As orauser, upgrade ASM to release 11.1 using OUI and DBUA. The new ASM release 11.1 should be running in a new Oracle Home 2 (OH2). ASM should still be running as orauser.

2. Bring down the ASM and Listener resources from CRS home.

3. As a new user (asmuser), install 11.1 in a third Oracle Home (OH3). This should be a software-only installation.

4. From CRS home, run:

   srvctl remove listener -n node_name
   srvctl add listener -n node_name -o OH3
   srvctl modify asm -n node_name -i ASM_instance_name -o ORACLE_HOME_path
   

5. Update /etc/oratab so that OH3 is the Oracle home with the +ASM entry.

6. Copy listener.ora, sqlnet.ora, and tnsnames.ora from OH2.

7. Run EMCP to change the ASM instance path and connect-string role.

8. Make sure the disks are owned by asmuser and by OSDBA for ASM. They should also have the O660 permission set.

9. Start ASM and Listener resources from the new ASM 11g ORACLE_HOME or the new Oracle Database 11g ORACLE_HOME.

10. Run the command, GRANT sysasm TO sys.

If you have clustered ASM instances, then you also have the option of performing a rolling ASM upgrade. A rolling upgrade enables you to independently upgrade or patch ASM nodes without affecting database availability, thus providing greater uptime.

Reset ASM Passwords to Enforce Case-Sensitivity

Starting with Oracle Database 11g Release 1 (11.1), you can enforce case sensitivity for passwords. For example, the password hPP5620qr fails if it is entered as hpp5620QR or hPp5620Qr. In previous releases, passwords were not case sensitive.

To take advantage of enforced case-sensitive passwords, you must reset the passwords of existing users during the database upgrade procedure. For new ASM instances, there are no additional tasks or management requirements. For upgraded ASM instances, each user password must be reset with an ALTER USER statement.

Advance the ASM and Oracle Database Disk Group Compatibility

Starting with Oracle Database 11g Release 1 (11.1), you can advance the Oracle Database and the ASM disk group compatibility settings across software versions.

Advancing compatibility enables new features only available in the new version. However, it makes the disk group incompatible with older versions of the software. Note that advancing on-disk compatibility is an irreversible operation.

You use the compatible.rdbms and compatible.asm attributes to specify the minimum software version required by the database instance and the ASM instance, respectively, to access the disk group. For example, the following ALTER DISKGROUP statement advances the ASM compatibility of the disk group asmdg2:

ALTER DISKGROUP asmdg2 SET ATTRIBUTE 'compatible.asm' = '11.1'

In this case, the disk group can be managed only by ASM software of version 11.1 or higher, while any database client of version 10.1 or higher can use the disk group.

Set Up ASM Preferred Read Failure Groups

ASM administrators can specify some disks to be preferred over others for read I/O operations. When ASM preferred read failure groups are defined, ASM can read from the extent that is closest to it, rather than always reading the primary copy.

Both the ASM clients and ASM require Oracle Database 11g Release 1 (11.1) or higher to use the preferred read feature. The compatible.asm and compatible.rdbms attributes are the disk group attributes that must be advanced to release 11.1 to use this new feature.

Database Upgrade After ASM Upgrade

If you are migrating to an environment with separate operating system users, you must upgrade the database after upgrading ASM. The database user must be a member of OSDBA for ASM.

There are three scenarios to consider:

• Keeping orauser as the Operating System User

• Changing the Operating System User For a Single-Instance Database

• Changing the Operating System User for an Oracle RAC Database

Upgrade the Oracle Cluster Registry (OCR) Configuration for ASM

If you are using Oracle Clusterware, then you must upgrade the Oracle Cluster Registry (OCR) keys for ASM by running the following command:

srvctl modify asm -n node [-p spfile] -o asm_home -i instance

The -p option is necessary only if you are using an SPFILE and it was moved.

Adjust the ASM Initialization Parameter File for the New Release

Each release of Oracle Database introduces new initialization parameters, deprecates some initialization parameters, and makes some initialization parameters obsolete. You should adjust the parameter file to account for these changes and to take advantage of new initialization parameters that might be beneficial to your system.

Install and Configure Enterprise Manager Database Control for ASM

If you want to use Enterprise Manager Database Control with ASM, then you must install and configure it.