It may be helpful and could speed up the upgrade if these unsupported and unwanted (by the application DB is used for) components are removed before the upgrade. This post list steps for removing some of these components. It's best to take a full database backup before running these components removal scripts.
The database used is a 188.8.131.52 SE database created with the OLTP template. Currently all the components have the status valid.
--> Oracle Catalog Views [upgrade] VALID --> Oracle Packages and Types [upgrade] VALID --> JServer JAVA Virtual Machine [upgrade] VALID --> Oracle XDK for Java [upgrade] VALID --> Oracle Workspace Manager [upgrade] VALID --> OLAP Analytic Workspace [upgrade] VALID --> OLAP Catalog [upgrade] VALID --> EM Repository [upgrade] VALID --> Oracle Text [upgrade] VALID --> Oracle XML Database [upgrade] VALID --> Oracle Java Packages [upgrade] VALID --> Oracle interMedia [upgrade] VALID --> Spatial [upgrade] VALID --> Expression Filter [upgrade] VALID --> Rule Manager [upgrade] VALID --> Oracle OLAP API [upgrade] VALIDBut if ultrp was run some of the unsupported components will become invalid.
1. Removing Application Express
@?/apex/apxremov.sql2. Removing Multimeida (interMedia)
@?/ord/im/admin/imremov.sql3. Removing Spatial
sqlplus "/as sysdba" set pagesize 0 set feed off spool dropsyn.sql select 'drop public synonym "' || synonym_name || '";' from dba_synonyms where table_owner='MDSYS'; spool off; @dropsyn.sql set feedback on drop user mddata cascade; drop user spatial_csw_admin_usr cascade; drop user spatial_wfs_admin_usr cascade; drop user MDSYS cascade;4.Removing Expression Filter
5. Removing OLAP components (also refer 1362752.1, 565773.1)
drop user olapsys cascade; @?/rdbms/admin/utlrp spool olapdrop.sql select 'drop public synonym ' || synonym_name || ';' from dba_synonyms where owner='PUBLIC' and table_owner='OLAPSYS'; spool off @olapdrop.sql select * from sys.exppkgact$ where package = 'DBMS_AW_EXP' and schema= 'SYS'; delete from sys.exppkgact$ where package = 'DBMS_AW_EXP' and schema= 'SYS'; commit; select * FROM SYS.EXPPKGACT$ WHERE PACKAGE = 'DBMS_CUBE_EXP' AND SCHEMA= 'SYS'; create table exppkgact$_bck as select * from exppkgact$; delete from exppkgact$ where package = 'DBMS_CUBE_EXP' and schema = 'SYS'; commit; drop package CWM2_OLAP_INSTALLER; @?/rdbms/admin/utlrpAt this stage Oracle database packages and types may be invalid. To fix this start the DB in restrict mode and run
@?/rdbms/admin/catalog.sql @?/rdbms/admin/catproc.sql @?/rdbms/admin/utlrp.sql6. Removing XDK for Java
drop public synonym xslprocessor; @?/xdk/admin/rmxml.sql7. Removing JServer
@?/javavm/install/rmjvm.sql8. Removing Java packages
@?/rdbms/admin/catnojav.sql9. Removing Oracle Warehouse Builder (OWB)
@?/owb/UnifiedRepos/clean_owbsys.sqlThese are the only components removed as the application still uses wm_concat workspace manager could not be removed. But if required following script could be used to remove workspace manager
@$ORACLE_HOME/rdbms/admin/owmuinst.plbRemoving Oracle text may have consequences for expdp/impdp (not tested) so it was left. But if required this too could be removed with
@?/ctx/admin/catnoctx.sql drop procedure sys.validate_context;At this stage the OLAP components (only two will left in the dba_registry listing) may have status invalid. Other components will have status valid or removed. This doesn't affect the upgrade from 184.108.40.206 to 220.127.116.11. Once upgraded the OLAP components will have the status option_off.
COMP_NAME STATUS ---------------------------------------- ------------- Oracle Enterprise Manager VALID Oracle XML Database VALID Oracle Text VALID Oracle Workspace Manager VALID Oracle Database Catalog Views VALID Oracle Database Packages and Types VALID JServer JAVA Virtual Machine REMOVED Oracle XDK REMOVED Oracle Database Java Packages REMOVED OLAP Analytic Workspace OPTION OFF Oracle OLAP API OPTION OFFUseful metalink note
Information On Installed Database Components and Schemas [ID 472937.1]