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. For more information about Oracle (NYSE:ORCL), visit .2. Oracle offers a comprehensive and fully integrated stack of cloud applications and platform services. My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts. To view full details, sign in with your My Oracle Support account.ĭon't have a My Oracle Support account? Click to get started! Note the LINE numbers for the ORA-00942 errors, line numbers 78 WMSYS LTUTIL PACKAGE BODY PL/SQL: SQL Statement ignored 7838 7 WMSYS LTUTIL PACKAGE BODY PL/SQL: ORA-00942: table or view does not exist 7838 18 WMSYS LTUTIL PACKAGE BODY PL/SQL: SQL Statement ignored 7828 7 WMSYS LTUTIL PACKAGE BODY PL/SQL: ORA-00942: table or view does not exist 7828 22 SQL>select owner, name, type, text, line, position from dba_errors where owner = 'WMSYS' WMSYS.LTUTIL is invalid with these errors Workspace Manager is invalid and there is one invalid object, WMSYS.LTUTIL Information in this document applies to any platform. Workspace Manager INVALID with invalid object WMSYS.LTUTIL after upgrade to 12.2
0 Comments
Leave a Reply. |