INCLUDE=DBLINK
parameter to export all database links into a dump file suitable for import into the downgraded database. This dump file can then be used to replace the database links after the downgrade.11.2.0
or higher, then you cannot downgrade.COMPATIBLE
initialization parameter must be set to 11.0.0
or lower.COMPATIBLE
initialization parameter must be set to 10.2.0
or lower.COMPATIBLE
initialization parameter must be set to 10.1.0
.SET
clause of the ALTER SYSTEM
statement as described in Oracle Real Application Clusters Administration and Deployment Guide.DV_PATCH_ADMIN
role for the SYS
account.DBMS_DST
PL/SQL package to update the database time zone version, then you must apply the patch for the same time zone file version into the earlier release's Oracle home before downgrading.DBMS_DST
was then run to update this database to DSTv14. Then, before downgrading from release 11.2.0.3 to 10.2.0.4, you need to apply on the release 10.2.0.4 side the DSTv14 patch for 10.2.0.4 for Linux x64. This ensures that your TIMESTAMP
WITH
TIME
ZONE
data is not logically corrupted during retrieval.ORA_TZFILE
environment variable to the full path name of the timezone.dat
file when you upgraded to Oracle Database 11g Release 2 (11.2), then you must unset it if you subsequently downgrade your database.ORA_TZFILE
variable, then connecting to the database using the smaller time zone file might produce the following errors:apxrelod.sql
file from the Oracle Database 11g Release 2 (11.2) ORACLE_HOME/apex/
directory to a directory outside of the Oracle home, such as the temporary directory on your system.ORA-00600
errors. You can re-create these objects after the downgrade.ORACLE_UNQNAME
environment variable to the database unique name.path
is the voting disk path listed in the File
Name
column displayed in the previous step:/rdbms/admin
directory.CLUSTER_DATABASE
initialization parameter to FALSE
. After the downgrade, you must set this parameter back to TRUE
.SYSDBA
privileges.DOWNGRADE
mode:PFILE
option to specify the location of your initialization parameter file.catdwgrd.sql
:ORA-39709
error is displayed and the SQL*Plus session terminates without downgrading the Oracle Database data dictionary. All components must be successfully downgraded before the Oracle Database data dictionary is downgraded. You must identify and fix the problem before rerunning the catdwgrd.sql
script.downgrade.log
. Correct any problems you find in this file and rerun the downgrade script if necessary.downgrade.log
to something else.ORACLE_HOME
PATH
oratab
file and any client scripts that set the value of ORACLE_HOME
point to the downgraded Oracle home.OracleService
SID
Oracle service of the Oracle Database 11g Release 2 (11.2) database, where SID
is the instance name.ORADIM
command. For example, if your SID is ORCL, then enter the following command:ORADIM
command.Variable | Description |
---|---|
SID | Same SID name as the SID of the database being downgraded. |
PASSWORD | Password for the database instance. This is the password for the user connected with SYSDBA privileges. The -INTPWD option is not required. If you do not specify it, then operating system authentication is used, and no password is required. |
USERS | Maximum number of users who can be granted SYSDBA and SYSOPER privileges. |
ORACLE_HOME | Oracle home directory of the database to which you are downgrading. Ensure that you specify the full path name with the -PFILE option, including drive letter of the Oracle home directory. |
ORCL
, your PASSWORD is TWxy5791
, the maximum number of USERS is 10, and the ORACLE_HOME directory is C:ORANT, then enter the following command:ORADIM
utility makes all necessary changes automatically.CLUSTER_DATABASE
initialization parameter to FALSE
. After the downgrade, you must set this initialization parameter back to TRUE
.ORACLE_HOME
/rdbms/admin
directory of the previous release.SYSDBA
privileges.catrelod.sql
:catrelod.sql
script reloads the appropriate version of all of the database components in the downgraded database.xsrelod.sql
script:xsrelod.sql
script avoids the following error:dbmsxdbt.sql
script:dbmsxdbt.sql
script avoids the following errors when reloading XDB.DBMS_XDBT
package:apxrelod.sql
script (in step 4). Manually reload Oracle Application Express by running the apxrelod.sql
script:apxrelod.sql
script avoids package APEX_030200.WWV_FLOW_HELP
being INVALID
due to the following error:reload.log
. Correct any problems you find in this file and rerun the appropriate script if necessary.PFILE
option to specify the location of your initialization parameter file.olstrig.sql
script from the Oracle Database 11g Release 2 (11.2) Oracle home to the Oracle home of the version to which the database is to be downgraded.olstrig.sql
to re-create DML triggers on tables with Oracle Label Security policies.utlrp.sql
script:utlrp.sql
script recompiles all existing PL/SQL modules that were previously in an INVALID
state, such as packages, procedures, types, and so on.db-unique-name
is the database name (not the instance name), old_ORACLE_HOME
is the location of the old Oracle home in which the downgraded database will be running. In this example, to_relnum
is the database release number to which the database is being downgraded. (For example: 11.2.0.1.0.)]srvctl
before running the emca -restore
command. This needs to be executed from the ORACLE_HOME
/bin of the version to which the database is being downgraded.srvctl
emca
-restore
command with the appropriate options to restore Oracle Enterprise Manager Database Control or Grid Control to the old Oracle home. The options that you specify depend on whether the database being downgraded is an Oracle RAC database or an Oracle ASM database, as follows:emca
for this procedure. See Oracle Database Administrator's Guide for complete information about emca
.emca
varies according to the options that you specify and the values that you enter at the prompts.emca
-restore
command is not required for an inplace patchset upgrade.emca
-restore
procedure you are ready to restore the Oracle Enterprise Manager Database files and data with the emdwgrd
utility. You must run the emdwgrd utility from the Oracle Database 11g Release 2 (11.2) home. But ORACLE_HOME
and other environment variables must be set to point to the Oracle home from which the upgrade originally took place.emdwgrd.bat
for emdwgrd
.ORACLE_HOME
to the Oracle home from which the database upgrade originally took place.ORACLE_HOME
to the current Oracle home.ORACLE_SID
to the SID of the database that was upgraded and then downgraded.PATH
, LD_LIBRARY_PATH
and SHLIB_PATH
to point to the Oracle home from which the database upgrade originally took place.SID
is the SID of the database that was upgraded and then downgraded and save_directory
is the path to the storage location you chose when saving your database control files and data:restore
command:-shared
to the previous command line.emdwgrd
.emdwgrd
utility produces output similar to the following:emdwgrd
finishes, Oracle Enterprise Manager Database Control has been downgraded to the old Oracle home.emdwgrd
utility produces output similar to the following:DV_OWNER
role.INCLUDE=DBLINK
parameter to export all database links into a dump file suitable for import into the downgraded database. This dump file can then be used to replace the database links after the downgrade.https://support.oracle.com
. Oracle recommends that you read the entire note before taking action.xsrelod.sql
script, which is included with release 11.2.0.1. This problem only occurs after downgrading to release 11.2.0.1 and then attempting to enable XML DB indexes. The error 'ORA-01418: specified index does not exist' may be raised and can safely be ignored.imrelod.sql
script which is included with release 11.2.0.2. The error 'ORA-20000: Oracle ORDIM component in registry is status: DOWNGRADED. Oracle ORDIM must be installed and valid prior to Oracle Multimedia upgrade, downgrade, or patch.' can safely be ignored.catdwgrd.sql
script and before running the catrelod.sql
script, issue the following two commands: