If you upgrade a database from 10 g to 11.2, all Data Mining metadata objects are migrated from DMSYS to SYS. SQL> SELECT 'Drop public synonym ' ||'"'||SYNONYM_NAME||'" ' FROM DBA_SYNONYMS WHERE TABLE_OWNER = 'DMSYS' SQL> SPOOL dir_path/DROP_DMSYS_SYNONYMS.SQL If the above SQL returns non-zero rows, create and run a SQL script as shown in the following example:
SQL> SELECT COUNT(*) FROM DBA_SYNONYMS WHERE TABLE_OWNER = 'DMSYS' SQL> DELETE FROM SYS.EXPPKGACT$ WHERE SCHEMA = 'DMSYS' If it does, you should drop the DMSYS schema and its associated objects from the database as follows: If you upgrade a database with the Data Mining option from 11.2.0.1 to 11.2.0.2, make sure that the DMSYS schema does not exist in your 11.2.0.1 database. If the size is inadequate, then an ORA-19815 error will be written to the alert log, and the upgrade will stop until additional space is made available.Ĥ.2.8 Upgrading a Database With Oracle Data Mining (ODM) If you are using a Fast Recovery Area, then check that the size available is sufficient for the redo generated during the upgrade. If you are using file systems for data file storage, then be sure there is adequate space in the file systems for tablespace growth during the upgrade.
However, to avoid potential space problems during either a manual upgrade or an upgrade using the Database Upgrade Assistant (DBUA), you can set one data file for each tablespace to AUTOEXTEND ON MAXSIZE UNLIMITED for the duration of the upgrade. The tablespace size estimates may be too small, especially if Oracle XML DB is installed in your database. For a manual upgrade, be sure to run this utility on your existing database prior to upgrading. The Oracle Database 11 g Pre-Upgrade Information Utility ( utlu112i.sql) estimates the additional space that is required in the SYSTEM tablespace and in any tablespaces associated with the components that are in the database (for example, SYSAUX, DRSYS) (reference Bug 13067061). For example, whether your application uses any TIMESTAMP WITH TIME ZONE type, you do not need to run the DBMS_DST package to upgrade your time zone version to the latest one available.įast Recovery was previously known as Flash Recovery. Note that, in release 11.2.0.2, you have the option to retain your current time zone version after migrating to 11.2. The other two database properties will be used when you upgrade your time zone version using DBMS_DST package. DST_PRIMARY_TT_VERSION property records the actual time zone version in use. The Pre-Upgrade Information Tool also populates three new database properties ( DST_PRIMARY_TT_VERSION, DST_SECONDARY_TT_VERSION, and DST_UPGRADE_STATE) in sys.database_properties that are pertinent to the time zone version and its upgrade.
The warning recommends running the DBMS_DST package to upgrade the database time zone version to the latest and to update TIMESTAMP WITH TIME ZONE data as well.
The Pre-Upgrade Information Tool ( utlu112i.sql and its counterpart used by the Database Upgrade Assistant) provides a warning if the time zone file version is not version 11. You can use SELECT VERSION FROM V$TIMEZONE_FILE to identify the time zone file version when upgrading your Oracle Database 10 g or 11 g databases.
If your older database is using a time zone file version greater than 14, then you must obtain the corresponding time zone file patch for 11.2 prior to upgrading your database. Oracle Database 11 g Release 2 (11.2) ships with time zone file versions 1 through 14. Section 4.19, "Oracle Grid Infrastructure for a Cluster" Section 4.18, "Oracle Real Application Clusters"
Section 4.15, "Oracle Internet Directory" Section 4.13, "Oracle Configuration Manager" Section 4.12, "Oracle Client Applications" Section 4.11, "Oracle Application Express" Section 4.10, "Media Management Software" Section 4.6, "Oracle Enterprise Manager Database Control" Section 4.5, "Oracle Automatic Storage Management (Oracle ASM)" Section 4.3, "Features Not Available or Restricted in 11.2.0.2" Section 4.2, "Compatibility, Upgrading, Downgrading, and Installation" This section of the Readme contains the following sub-sections: Note: If you are on Oracle Database 11 g Release 2 (11.2.0.2), this is the Readme section that you need to read.