1. OATM Conversion This section covers required steps to convert Oracle E-Business tablespaces to OATM format. 1.1. Reset FPA user password using FNDCPASS command FNDCPASS apps/$apps_password 0 Y system/$system_password ORACLE FPA fpa_pwd 1.2. Fix FPA Index sqlplus fpa/fpa<<EOF spool deleting.log set serveroutput on exec dbms_aw.execute('aw delete FPAPJP'); commit; spool off EOF 1.3. Enabe CTXSYS Schema in Oracle Apps Logon to Oracle Applications with the System Administrator Responsibility. Navigate to Security -> ORACLE -> Register Query for CTXSYS schema and Set Privilege to “Enabled”.
Transcript
1. OATM ConversionThis section covers required steps to convert Oracle E-Business tablespaces to OATM format. 1.1. Reset FPA user password using FNDCPASS command
FNDCPASS apps/$apps_password 0 Y system/$system_password ORACLE FPA fpa_pwd
1.2. Fix FPA Index
sqlplus fpa/fpa<<EOFspool deleting.log
set serveroutput onexec dbms_aw.execute('aw delete FPAPJP');commit;
spool offEOF
1.3. Enabe CTXSYS Schema in Oracle Apps
Logon to Oracle Applications with the System AdministratorResponsibility. Navigate to Security -> ORACLE -> RegisterQuery for CTXSYS schema and Set Privilege to “Enabled”.
1.4. Disable Custom Schemas
Logon to Oracle Applications with the System AdministratorResponsibility. Navigate to Security -> ORACLE -> RegisterQuery for XX% schema and Set Privilege to “External”.
1.5. Run OATM Migration Utility1.5.1. Login to application tier as applmgr and run perl
$FND_TOP/bin/fndtsmig.pl1.5.2.
1.6. Migration Sizing Reports
Select Option 1. Migration Sizing Reports
Select Option 2. Calculate total space required by each new tablespace to migrate all Oracle Application products.
Please do not skip this step.
Oracle Applications Tablespace Migration Utility Main Menu
1. Migration Sizing Reports2. Create New Tablespaces3. Generate Migration Commands4. Execute Migration Commands5. Run Migration Status Reports6. Run Post Migration Steps7. Run Customization Steps8. Run Migration in Batch Mode
[Q]uit [N]ext
Please enter your option - 1
Migration Sizing Reports
These reports are provided to help you gauge the space requirementsfor the new Tablespaces. Additionally, they will also help youdetermine the type of migration approach that best suits your needs
1. Generate a Report with the list of all the Oracle Application product schemas that can be migrated2. Calculate total space required by each new tablespace to migrate all Oracle Application product schemas (relevant for a complete migration)3. Calculate total space required by each new tablespace to migrate each Oracle Application product schema (relevant for a schema-by-schema migration)4. Calculate total space required by each Oracle Applications schema, with details for each object5. Display Sizing Exception report
[Q]uit [B]ack [N]ext
Please enter your option - 2
This step will provide the complete migration space needed:Enter the Extent Allocation type A(Autoallocate) or U(niform Exten Size)
[U]:
Enter Uniform Extent Size for the Tablesapces in Kbytes[1024]:
Enter the Extent Allocation type A(utoallocate) or U(niform Extent Size)[U]: U
Enter Uniform Extent Size for the Tablespaces in KBytes[1024]:
Enter the absolute path for the datafiles directory: /d01/oracle/uatdb/uatdata
The directory /d01/oracle/uatdb/uatdata does not exist on this node.
Please ensure that this directory is accessible from the database server.
Do you still want to use this directory [N]: Y
Enter the Number of Datafiles for APPS_TS_TX_DATA tablespace[1]: 6
Enter the Datafile Size for APPS_TS_TX_DATA tablespace (MB): 8000
Enter the Number of Datafiles for APPS_TS_TX_IDX tablespace[1]: 7
Enter the Datafile Size for APPS_TS_TX_IDX tablespace (MB): 7000
Enter the Number of Datafiles for APPS_TS_SEED tablespace[1]: 2
Enter the Datafile Size for APPS_TS_SEED tablespace (MB): 4000
Enter the Number of Datafiles for APPS_TS_INTERFACE tablespace[1]: 2
Enter the Datafile Size for APPS_TS_INTERFACE tablespace (MB): 3000
Enter the Number of Datafiles for APPS_TS_SUMMARY tablespace[1]: 10
Enter the Datafile Size for APPS_TS_SUMMARY tablespace (MB): 8000
Enter the Number of Datafiles for APPS_TS_NOLOGGING tablespace[1]: 3
Enter the Datafile Size for APPS_TS_NOLOGGING tablespace (MB): 5000
Enter the Number of Datafiles for APPS_TS_ARCHIVE tablespace[1]: 2
Enter the Datafile Size for APPS_TS_ARCHIVE tablespace (MB): 4000
Enter the Number of Datafiles for APPS_TS_QUEUES tablespace[1]: 2
Enter the Datafile Size for APPS_TS_QUEUES tablespace (MB): 3000
Enter the Number of Datafiles for APPS_TS_MEDIA tablespace[1]: 1
Enter the Datafile Size for APPS_TS_MEDIA tablespace (MB): 2000
Enter the Number of Datafiles for APPS_TS_TOOLS tablespace[1]: 2
Enter the Datafile Size for APPS_TS_TOOLS tablespace (MB): 3000
Tablespace creation script /d02/oracle/uatappl/admin/uat/log/crtts.sql created
Execute the above script by connecting database server;
1.7. Display Sizing Exception Report
Selection Option 5 Display Sizing Exception reportCheck for the errors to know if any objects in error exist for all schemas
1.8. Invalid Index Report
Choose option 3 to Generate Migration Commands
Perform Option 1 in order to find and correct any invalid indexes
The error related to Index CTXSYS can be ignored as this index “DEFAULT_POLICY_ORACONTAINS” does not exist
[oracle@testplan ~]$ cd $ORACLE_HOME/ctx/sample/script[oracle@testplan script]$ lsdrkorean.sql[oracle@testplan script]$ sqlplus
SQL*Plus: Release 11.2.0.4.0 Production on Tue Oct 7 06:34:53 2014
Copyright (c) 1982, 2013, Oracle. All rights reserved.
Enter user-name: /as sysdba
Connected to:Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit ProductionWith the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> @drkorean.sqlList of indexes that use KOREAN_LEXER as top level lexer:List of indexes that use KOREAN_LEXER as a sub lexer:"CS"."CS_FORUM_MESSAGES_TL_N3"Migrate KOREAN_LEXER to KOREAN_MORPH_LEXERRebuild all indexes that use korean lexer as top level lexer:Reindex all documents that use KOREAN_LEXER as sub lexerreindexing : "CS"."CS_FORUM_MESSAGES_TL" finished.SQL> alter index cs.CS_FORUM_MESSAGES_TL_N3 rebuild;
1.9. Generate Migration Commands
Choose option 3 to Generate Migration Commands.
Enter Option 2, which will generate the commands for schemas.
After the Migration commands are generated, please check the logfile and make sure there are no errors in the logfile before proceeding
1.9.1. Execute option to generate execution commands for all schemas
1.10. Build Migration commands for custom objects1.11. Execute OATM from the application
1.12.
1.12.1. Use max workers possible for first run
1.12.2. After sequential and parallel jobs complete, check for log file of long objects to verify if treads are still running. In case they die, kill LONG object migration job and restart migration again this time reducing parallel workers
1.12.3.
1.13. Verify Objects are migrated correctly1.14.
1.15. Run Post Migration Steps
a) Fix any unsusable indexes generating a script b) Check for any valid Domain indexes c) Verify any LOBs that didn’t get migrated You may see the following index. It is a known bug and use the following fix and rerun the script and make sure there are no exceptions. If there exceptions, use the generated command and manually migrate the LOB segments.
AQ$_WF_CONTROL_D lob index didn’t get migrateFollowed note 418238.1
1.18.1.18.1. Compile Invalid Objects using ADADMIN1.18.2. Generate JAR Files with Force Option=Yes using ADADMIN1.18.3. Generate all forms and reports using ADADMIN
