Tasks to Complete After Testing Your Oracle Database Upgrade
After you complete your upgrade testing, you may want to complete additional tasks, depending on your system.
Note:
If you completed your upgrade using the AutoUpgrade utility, then you only have to complete the following:
- "Identifying and Copying Oracle Text Files to a New Oracle Home"
- "Upgrading the Oracle Clusterware Configuration"
- Changing Passwords for Oracle Supplied Accounts
Oracle recommends that you carry out these tasks to protect new Oracle user accounts. - Migrating Your Initialization Parameter File to a Server Parameter File
If you are currently using a traditional initialization parameter file, then use this procedure to migrate to a server parameter file. - Identifying and Copying Oracle Text Files to a New Oracle Home
To upgrade Oracle Text, use this procedure to identify and copy required files from your existing Oracle home to the new release Oracle home. Complete this task after you upgrade Oracle Database. - Upgrading the Oracle Clusterware Configuration
If you are using Oracle Clusterware, then you must upgrade the Oracle Clusterware keys for the database. - Adjust the Initialization Parameter File for the New Release
Review these topics to help you to check your initialization parameters after upgrading. - Setting the COMPATIBLE Initialization Parameter After Upgrade
After testing, you can set theCOMPATIBLE
initialization parameter to the compatibility level you want for your new database.
Parent topic: Postupgrade Tasks for Oracle Database
Changing Passwords for Oracle Supplied Accounts
Oracle recommends that you carry out these tasks to protect new Oracle user accounts.
Depending on the release from which you upgraded, there may be new Oracle user accounts on your database. Oracle recommends that you lock all Oracle supplied accounts except for SYS
and SYSTEM
, and expire their passwords, so that new passwords are required when the accounts are unlocked.
Note:
If the default Oracle Database security settings are in place, then passwords must
be at least eight characters, and passwords such as
welcome
and
oracle
are not allowed.
See Also:
Oracle Database Security Guide about password requirements
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;
Migrating Your Initialization Parameter File to a Server Parameter File
If you are currently using a traditional initialization parameter file, then use this procedure to migrate to a server parameter file.
-
If the initialization parameter file is located on a client computer, then transfer the file from the client computer to the server computer.
-
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 aCREATE SPFILE
statement. -
Start up the instance using the newly-created server parameter file.
Note:
If you are using Oracle Real Application Clusters (Oracle RAC), then you must combine all of your instance-specific initialization parameter files into a single initialization parameter file. Complete the procedures necessary for using a server parameter file with cluster databases.
Related Topics
Identifying and Copying Oracle Text Files to a New Oracle Home
To upgrade Oracle Text, use this procedure to identify and copy required files from your existing Oracle home to the new release Oracle home. Complete this task after you upgrade Oracle Database.
Certain Oracle Text features rely on files under the Oracle home that you have configured. After manually upgrading to a new Oracle Database release, or after any process that changes the Oracle home, you must identify and move these files manually. These files include user filters, mail filter configuration files, and all knowledge base extension files. After you identify the files, copy the files from your existing Oracle home to the new Oracle home.
Upgrading the Oracle Clusterware Configuration
If you are using Oracle Clusterware, then you must upgrade the Oracle Clusterware keys for the database.
Run srvctl
to upgrade the database. For
example:
ORACLE_HOME/bin/srvctl upgrade database -db name -o ORACLE_HOME
Adjust the Initialization Parameter File for the New Release
Review these topics to help you to check your initialization parameters after upgrading.
Each release of Oracle Database introduces new initialization parameters, deprecates
some initialization parameters, and desupports some initialization parameters. You must
adjust the parameter file to account for these changes, and to take advantage of new
initialization parameters that can be beneficial to your system. With Oracle's automated
upgrade procedures, the tnsnames.ora
file is automatically populated
with new configuration information and settings. However, you may want to manually
update tnsnames.ora
and adjust local_listener
and
remote_listener
parameter references.
See Also:
-
Oracle Database Reference “Changes In this Release” section for a list of new initialization parameters, and for information about each parameter
Setting the COMPATIBLE Initialization Parameter After Upgrade
After testing, you can set the COMPATIBLE
initialization parameter to the compatibility
level you want for your new database.
The COMPATIBLE
initialization parameter controls the
compatibility level of your database. Set the
COMPATIBLE
initialization parameter to a higher value only
when you are certain that you no longer need the
ability to downgrade your database.
-
Perform a backup of your database before you raise the
COMPATIBLE
initialization parameter (optional).Raising the
COMPATIBLE
initialization parameter can cause your database to become incompatible with earlier releases of Oracle Database. A backup ensures that you can return to the earlier release if necessary. -
If you are using a server parameter file, then complete the following steps:
-
To set or change the value of the
COMPATIBLE
initialization parameter, update the server parameter file.For example, to set the
COMPATIBLE
initialization parameter to23.0.0
, enter the following statement:SQL> ALTER SYSTEM SET COMPATIBLE = '23.0.0' SCOPE=SPFILE;
-
Shut down and restart the instance.
-
-
If you are using an initialization parameter file, then complete the following steps:
-
If an instance is running, then shut it down.
For example:
SQL> SHUTDOWN IMMEDIATE
-
To set or change the value of the
COMPATIBLE
initialization parameter, you edit the initialization parameter file.For example, to set the
COMPATIBLE
initialization parameter tofor Oracle Database release 23.0.0.0.0
, enter the following in the initialization parameter file:COMPATIBLE = 23.0.0
-
Start the instance using
STARTUP
.
-
Note:
If you are using an ASM disk group, then the disk group compatibility attribute must be equal to or less than the value for the database compatibility parameter in init.ora
.