![]() ![]() Use utluiobj.sql after the upgrade to identify any new invalidĬheck Summary: Check for use of older timezone data fileįix Summary: Update the timezone using the DBMS_DST package after upgrade is complete.ĭatabase is using a time zone file older than version 18.Īfter the upgrade, it is recommended that DBMS_DST packageīe used to upgrade the 12.1.0.2.0 database time zone version Registry$nonsys_inv_objs unless there were over 5000. 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 SQL> Upgrade Fixup Script Generated on 01:42:41 Version: 12.1.0.2 Build: 008įix Summary: Invalid objects are displayed and must be reviewed. Make sure to select USE FLASHBACK OPTION: ( it will create a restore point automatically)ġ. Select parallelism to required degree and select upgrade timezone, which will upgrade the timezone, after end of db upgrade. Now run the dbua utility from 12c oracle_home location.Ĭd oracle/app/oracle/product/12.1.0.2/dbhome_1/bin UPGRADE:Īt this stage, we are still connected to 11g database which is up and running. If this query returns any row- Please make sure 20369415 is applied to the ORACLE 12C rdbms binary, before upgrade. Check the ACLS present: SQL> select aclid, start_date, end_date from xds_ace where start_date is not null Run below script to remove the EM component: sql> connect / as sysdbaĨ. Either we can use oracle 12c/13c cloud control or enterprise database express for monitoring database. Remove enterprise manager if installed:įrom 12c, enterprise manager has been decommissioned from 12c. Purge aud$ table ( take backup if required) SQL> truncate table sys.aud$ ħ. SQL> EXECUTE dbms_stats.gather_dictionary_stats Ħ. ![]() And take action manually, if those were not fixed by the script. To gather dictionary statistics execute the following commandĮXECUTE dbms_stats.gather_dictionary_stats Please gather dictionary statistics 24 hours prior to Note 2: See MOS Note 1088970.1 for information on APEX Upgraded outside of and prior to database upgrade. Note 1: To reduce database upgrade time, APEX can be manually Upgraded to APEX version 4.2.5 in the new release. Manually upgraded prior to database upgradeĪPEX is currently at version 3.2.1.00.12 and will need to be => ERRORS FOUND for B2BRBMT3 > PRE-UPGRADE RESULTS for B2BRBMT3 Oracle Application Express (APEX) can be Ĭp /oracle/app/oracle/product/12.1.0.2/dbhome_1/rdbms/admin/utluppkg.sql. Ĭp /oracle/app/oracle/product/12.1.0.2/dbhome_1/rdbms/admin/preupgrd.sql. Make sure no invalid objects under sys or system schema: select owner,object_type,count(*) from dba_objects where status='INVALID' group by owner,object_type order by owner,object_type Ĭopy the preupgrd.sql and utluppkg.sql script from Oracle 12c binary to any temporary location. Oracle Workspace Manager VALID 11.2.0.4.0Ĥ. Oracle Expression Filter VALID 11.2.0.4.0 Oracle Database Packages and Types VALID 11.2.0.4.0 Oracle Database Java Packages VALID 11.2.0.4.0 Oracle Database Catalog Views VALID 11.2.0.4.0 Oracle Application Express VALID 3.2.1.00.1 JServer JAVA Virtual Machine VALID 11.2.0.4.0 Select substr(comp_name,1,40) comp_name, status, substr(version,1,10) version from dba_registry order by comp_name Check whether all components are valid or not: SQL> alter system set db_recovery_file_dest='/dumparea/FRA/B2BRBMT3' scope=both ģ. SQL> alter system set db_recovery_file_dest_size=10G scope=both This is to ensure that, if upgrade fails, we can restore it using guarantee restore point. Install Oracle 12c RDMBS home – How to install oracle 12c binary DBUA in oracle 12c simplifies the upgrade process a lot. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |