Copy configuration files (init file, tnsnames, listener, pwfile) from old Oracle Home to new.Ģ. This time make sure you dont have the critical warnings like the one with TIMEZONE version.ġ. ■ Sync Standby Database with the Primary Database ■ Resolve Outstanding Distributed Transactions ■ Save Oracle Enterprise Manager Database Control Data ■ Access Control to Network Utility Packages Oracle recommends gathering stats before the upgrade: EXEC DBMS_STATS.GATHER_DICTIONARY_STATS If you have any db links with passwords, you may want to back up the sys.link$ table to save the information. The following points must be addressed correctly otherwise there maybe problems.Įxample: CONNECT role now only has create session privilege. must be executed immediately prior to executing your upgrade.Ĭheck the warning messages and rectify them as needed. that the recycle bin is empty prior to upgradingġ. Your recycle bin is turned on and it contains format string will still prevent the upgraded database from starting up. Archive Logging is currently OFF, but failure to add the %r to the As of 10.1, log_archive_format requires a %r format qualifier WARNING: -> log_archive_format must be updated. Resolve outstanding distributed transactions prior to upgrade. WARNING:-> There are outstanding unresolved distributed transactions. Ensure no files are in backup mode prior to upgrade. WARNING: -> There are files in backup mode. Ensure no files need media recovery prior to upgrade. WARNING: -> There are files which need media recovery. Ensure all materialized view refreshes are complete prior to upgrade. WARNING: -> There are materialized view refreshes in progress. 11g Upgrade Guide for instructions to save the EM data prior to upgrade. Direct downgrade of EM Database Control is not supported. WARNING: -> EM Database Control Repository exists in the database. Refer to the 11g Upgrade Guide for instructions to configure Network ACLs. WARNING: -> Database contains schemas with objects dependent on network packages. Use utluiobj.sql after the upgrade to identify any new invalid The list of non-SYS/SYSTEM objects was written to The list of invalid SYS/SYSTEM objects was written to WARNING: -> Database contains INVALID objects prior to upgrade. statistics prior to upgrading the database. Refer to the 11g Upgrade Guide for instructions to update WARNING: -> Database contains stale optimizer statistics. to the latest version which comes with the new release. be used to upgrade the 10.2.0.2.0 database timezone version After the release migration, it is recommended that DBMS_DST package WARNING: -> Database is using a timezone file older than version 11. > "user_dump_dest" replaced by "diagnostic_dest"Ĭomponents: ![]() > "background_dump_dest" replaced by "diagnostic_dest" New name is "plsql_code_type" new value is "INTERPRETED" WARNING: -> "plsql_compiler_flags" old value was "INTERPRETED" WARNING: -> "sga_target" needs to be increased to at least 388 MB ![]() ![]() > EXAMPLE tablespace is adequate for the upgrade. AUTOEXTEND additional space required: 41 MB ![]() > TEMP tablespace is adequate for the upgrade. AUTOEXTEND additional space required: 287 MB > SYSAUX tablespace is adequate for the upgrade. AUTOEXTEND additional space required: 352 MB > UNDOTBS1 tablespace is adequate for the upgrade. WARNING: -> SYSTEM tablespace is not large enough for the upgrade. The following is an example of the output generated by the Pre-Upgrade Information Tool: Start SQL*Plus and login as ‘/ as sysdba’Ĭheck the output of the Pre-Upgrade Information Tool in upgrade_info.log. Change directory to /tmp that you copied utlu112i.sql to in Step 1.Ĥ. Set your environment to the one that is being upgraded. Copy the Pre-Upgrade Information Tool (utlul12i.sql) from the Oracle Database 11gR2 directory: $ORACLE_HOME/rdbms/admin to a temporary directory /tmp.Ģ. Run the Pre-Upgrade Information Tool (You Must Run This tool)ġ. THE RECOMMENDED IS 11.2.0 FOR 11gR2 PARAMETER FILE. COMPATIBLE PARAMETER MUST BE SET TO MINIMUM 10.0.0.0.
0 Comments
Leave a Reply. |