dbupgdiag.sql
script. The script can be run in SQL*Plus both before the upgrade on the source database and after the upgrade on the upgraded database as SYS user.http://support.oracle.com
lsinventory
command from the new Oracle home in order to list an accurate and complete inventory of what is currently installed on the system.ORACLE_HOME
PATH
oratab
file and any client scripts that set the value of ORACLE_HOME
point to the new Oracle home that is created for the new Oracle Database 11g release. Although DBUA automatically points oratab
to the new Oracle home, client scripts must be checked no matter which method you use to upgrade.UPGRADE CATALOG
command, see Oracle Database Backup and Recovery User's Guide for the topic that describes the procedures.DBMS_DST
PL/SQL package to upgrade the time zone file.timezlrg_
version_number
.dat
, while the small versions are designated as timezone_
version_number
.dat
. The files are located in the oracore/zoneinfo
subdirectory under the Oracle Database home directory.DBMS_DST
' on My Oracle Support at https://support.oracle.com
DBMS_STATS.CREATE_STAT_TABLE
procedure, then upgrade these tables by running the following procedure:SCOTT
is the owner of the statistics table and STAT_TABLE
is the name of the statistics table. Perform this procedure for each statistics table.extusrupgrade
) script to upgrade those users. The script has the following syntax:extusrupgrade
scriptUTL_TCP
, UTL_SMTP
, UTL_MAIL
, UTL_HTTP
, or UTL_INADDR
packages using Oracle XML DB. If you have applications that use these packages, then you must install Oracle XML DB if it is not installed. You must also configure network access control lists (ACLs) in the database before these packages can work as they did in earlier releases.host_name
. If one is found, then the example grants user_name
the CONNECT
privilege in the ACL, only if that user does not have this privilege. 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
.DV_PATCH_ADMIN
role for the SYS
account.hPP5620qr
fails if it is entered as hpp5620QR
or hPp5620Qr
. In previous releases, passwords were not case sensitive.ALTER
USER
statement.sec_case_sensitive_logon
to false
:sysdba
and sysoper
users, you can generate a new orapw
file using the new command line switch ignorecase
.welcome
and oracle
are not allowed. See Oracle Database Security Guide for more information.UNDO_MANAGEMENT
initialization parameter specifies which undo space management mode the system should use, as follows:UNDO_MANAGEMENT
=AUTO
(or if UNDO_MANAGEMENT
is not set), then the database instance starts in automatic undo management mode.UNDO_MANAGEMENT
initialization parameter defaults to automatic undo management mode in Oracle Database 11g Release 1 (11.1), but it defaults to manual undo management mode in earlier releases. You must therefore use caution when upgrading a previous release to Oracle Database 11g.UNDO_MANAGEMENT
=MANUAL
, then undo space is allocated externally as rollback segments.UNDO_MANAGEMENT=MANUAL
.UNDO_MANAGEMENT=AUTO
or by removing the parameter.LocalListenerAddress
has been deprecated as of release 11.2.0.1 due to changes with broker communication and the redo transport setting.InitialConnectIdentifier
has been changed to DGConnectIdentifier
. The value of DGConnectIdentifier
is used for all Data Guard network traffic, all of the time. If you are upgrading an Oracle Database release 10g configuration, which requires you to first upgrade to Oracle Database 11g Release 1 (11.1), the value that exists for InitialConnectIdentifier
is retained as the new value for DGConnectIdentifier
for the database. When upgrading an Oracle RAC database, the database administrator must ensure that the value for the InitialConnectIdentifier
property reaches all instances.LOB
data types (BFILE
, BLOB
, CLOB
, and NCLOB
) can provide many advantages over LONG
data types. See Oracle Database Concepts for information about the differences between LONG
and LOB
data types.ALTER TABLE
statement to change the data type of a LONG
column to CLOB
and that of a LONG RAW
column to BLOB
.LONG
column named long_col
in table long_tab
is changed to data type CLOB
:LONG
columns to LOBs, all the existing constraints and triggers on the table are still usable. However, all the indexes, including Domain indexes and Functional indexes, on all columns of the table become unusable and must be rebuilt using an ALTER INDEX..REBUILD
statement. Also, the Domain indexes on the LONG
column must be dropped before changing the LONG
column to a LOB./xdbconfig.xml
in the repository) can have two additional elements, http2-port
and http2-protocol
. These elements are not added to the Oracle XML DB configuration file by default during an upgrade. If you need support for HTTPS, then you must edit the configuration file to add these two new elements (see the XML schema for their exact locations), and to set the value of http2-protocol
to tcps
. The value of http2-port
should be different from the value of http-port
.http2-port
and http2-protocol
in the Oracle XML DB configuration file, you must configure the database and the listener to enable Oracle XML DB to use HTTPS. Additionally, if the steps in the following procedure were not performed before the upgrade, then you must perform them after the upgrade./xdbconfig.xml
in the repository) is automatically upgraded so that it can have an additional element, allow-repository-anonymous-access
. This element is of Boolean type which means it can have a value of true
or false
. You can use this element to disallow unauthenticated access to your Oracle XML DB Repository data through HTTP even if you unlock the ANONYMOUS
user account. The allow-repository-anonymous-access
element is not added to the Oracle XML DB configuration file by default during an upgrade, but when this element is missing, it is interpreted as false
.true
, in addition to unlocking the ANONYMOUS
user account.allow-repository-anonymous-access
element and configuring Oracle XML DBREMOTE_LISTENERS
parameter. However, you cannot remove the listeners themselves, because only node listeners can create dedicated servers for the database.SYS
and SYSTEM
, and expire their passwords, thus requiring new passwords to be specified when the accounts are unlocked.welcome
and oracle
are not allowed. See Oracle Database Security Guide for more information.REMOTE_LOGIN_PASSWORDFILE
initialization parameter is set to either exclusive
or shared
, create a password file with ORAPWD
.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.CREATE SPFILE
statementKOREAN_MORPH_LEXER
dictionary filesUSER_FILTER
executables$ORACLE_HOME/ctx/admin/ctxf102.txt
$ORACLE_HOME/ctx/admin/ctxf102.sql
as database user SYS
, SYSTEM
, or CTXSYS
KOREAN_LEXER
which was deprecated in Oracle 9i and desupported in Oracle Database 10g Release 2 (10.2), see Note 300172.1 on My Oracle Support for further information on manual migration from KOREAN_LEXER
to KOREAN_MORPH_LEXER
.https://support.oracle.com
srvctl
for release 11.2.0.3 to upgrade the database. For example:tnsnames.ora
file is not automatically populated with new configuration information and settings. Therefore, you may need to manually update tnsnames.ora
and adjust local_listener
and remote_listener
parameter references if these need to be resolved.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 release, set the COMPATIBLE
initialization parameter based on the compatibility level you want for your new database.COMPATIBLE
initialization parameter to a higher value:COMPATIBLE
initialization parameter (optional).COMPATIBLE
initialization parameter might cause your database to become incompatible with earlier releases of Oracle Database, and a backup ensures that you can return to the earlier release if necessary.COMPATIBLE
initialization parameter.COMPATIBLE
initialization parameter to 11.0.0
, enter the following statement:COMPATIBLE
parameter is set to a release number earlier than 11.0.0, then you cannot locate the server parameter file (SPFILE
) on HARD storage.COMPATIBLE
parameter is set to 11.0.0, then you can optionally locate the server parameter file on HARD storage.SPFILE
location (ORACLE_HOME/dbs) might not be on a HARD-compliant storage system, it is likely you must provide a parameter file that specifies the location of the SPFILE
.COMPATIBLE
initialization parameter.COMPATIBLE
initialization parameter to 11.0.0
, enter the following in the initialization parameter file:STARTUP
.init.ora
.local_listener
and remote_listener
parameter references if they need to be resolved in tnsnames.ora
. DBUA handles changes to network naming and listeners during automatic upgrades, but during a manual upgrade, tnsnames.ora
is not changed, nor are the listeners.CLUSTER_DATABASE
initialization parameter to false
before upgrading a cluster database. Now that the upgrade is finished, you must set this parameter to true
.ORACLE_HOME
either to an Oracle Database home, or to the grid home, depending on whether you are administering an Oracle Database instance as part of database administration, or administering an Oracle ASM instance as part of storage administration.ORACLE_HOME
PATH
oratab
file and any client scripts for Oracle ASM that set the value of ORACLE_HOME
point to the Oracle ASM home in the grid infrastructure home.asmca
).asmca
command to complete the upgrade separately. However, you must run asmca
soon after you upgrade Oracle Clusterware, as Oracle ASM management tools such as srvctl
do not work until Oracle ASM is upgraded.grid
, then the home of an existing Oracle ASM must be owned by the user grid
before you upgrade it.crsctl
and adding users to the CRS Administrators listdbms_diskgroup
)ASMCA_ROLLING_UPGRADE
as true
. For example:ORACLE_HOME
PATH
oratab
file and any client scripts that set the value of ORACLE_HOME
point to the Oracle home of the new Oracle Database 11g release.ORACLE_HOME
, PATH
, and oratab
checks are required only if you upgrade manually. DBUA automatically points oratab
OH1
) and the operating system user is orauser
.orauser
, upgrade Oracle ASM to release 11.2 using OUI and ASMCA. The new Oracle ASM release 11.2 runs in the grid infrastructure home. Oracle ASM should still be running as orauser
.orauser
, bring down the Oracle ASM instance and the listener.root
, run /etc/init.d/init.cssd stop
to stop CSS.asmuser
), install 11.2 in a third Oracle home (OH3
). This should be a software-only installation.root
, run localconfig reset
from OH3
./etc/oratab
so that OH3
is the Oracle home with the +ASM
entry.listener.ora
, sqlnet.ora
, and tnsnames.ora
from OH2
.connect-string
role.asmuser
and by OSASM for Oracle ASM. They should also have the O660
permission set.asmuser
, start the listener.asmuser
, start Oracle ASM (connect as SYSASM
).GRANT sysasm TO sys
.orauser
, upgrade Oracle ASM to release 11.2 using OUI and ASMCA. The new Oracle ASM release 11.2 should be running in a new Oracle home 2 (OH2
). Oracle ASM should still be running as orauser
.crs
for example), install 11.2 into a third Oracle home (OH3
) to match that of the Grid Infrastructure home. This must be a software-only installation./etc/oratab
so that OH3
is the Oracle home with the +ASM
entry.listener.ora
, sqlnet.ora
, and tnsnames.ora
from OH2
.connect-string
role.asmuser
and by OSASM for Oracle ASM. They should also have the O660
permission set.GRANT sysasm TO sys
.oracle
) to multiple role-allocated software owner user accounts (such as grid
, oracle1
, oracle2
), then change the owner of the existing Oracle ASM installation owner to the installation owner that you plan to use for the Oracle Grid Infrastructure installation.OH4
) and currently running oracle
as the operating system user, and you want to change the Oracle ASM operating system user to grid
. This is useful if you have two databases using Oracle ASM, and you had installed Oracle ASM with an installation owner that is the same as that for the existing databases, and you want to change the operating system installation owner of Oracle ASM to enable separate databases to run as separate operating system users, where neither Oracle Database installation owner has Oracle Grid Infrastructure binary ownership.OH4
) and currently running oracle
as the operating system user, then you should consider changing the Oracle ASM operating system user to grid
. Changing the operating system user of Oracle ASM enables separate databases to run as separate operating system users, where no Oracle Database installation owner has grid infrastructure binary ownership.hPP5620qr
fails if it is entered as hpp5620QR
or hPp5620Qr
. In previous releases, passwords were not case sensitive. Download wondershare dvd creator 5 1 2 2.ALTER
USER
statement.welcome
and oracle
are not allowed. See Oracle Database Security Guide for more information.COMPATIBLE.RDBMS
attribute, then you cannot revert to the previous setting. Therefore, before advancing the COMPATIBLE.RDBMS
attribute, ensure that the values for the COMPATIBLE
COMPATIBLE.RDBMS
before you advance the attribute value.compatible.rdbms
and compatible.asm
attributes to specify the minimum software release required by the database instance and the Oracle ASM instance, respectively, to access the disk group. For example, the following ALTER DISKGROUP
statement advances the Oracle ASM compatibility of the disk group asmdg2
:ALTER DISKGROUP
and CREATE DISKGROUP
statementsASM_PREFERRED_READ_FAILURE_GROUPS
initialization parameter to list failure group names that contain the preferred read disks for each node in a clusterASM_PREFERRED_READ_FAILURE_GROUPS
initialization parameter