OATM migration R12 Tutorial part 4



Last updated on September 17th, 2017 at 12:24 pm

The next space after tablespace creation would be generating migration commands

[applmgr] cd $APPL_TOP/admin
[applmgr] perl $FND_TOP/bin/fndtsmig.pl
Enter OATM configuration file or press enter to continue: <ENTER>
Enter APPL_TOP[/xyz/oracle/xyzappl]: <ENTER>
Enter FND_TOP[/xyz/oracle/xyzappl/fnd/11.5.0]: <ENTER>
Enter the Database Connect String[TEST]: <ENTER>
Enter the password for your ‘SYSTEM’ ORACLE schema: <SYSTEM-Password>
Please create log directory /xyz/oracle/xyzappl/admin/test/log to continue: Create the path
Enter the ORACLE APPS Schema name[APPS]: <ENTER>
Enter the password for APPS: <APPS-Password>

Enter the ORACLE Application Object Library [APPLSYS]: <ENTER>

================================================================
CONNECT_STRING=TEST
FND_TOP=/xyz/oracle/xyzappl/fnd/11.5.0
APPLSYS_SCHEMA=APPLSYS
APPS_SCHEMA=APPS

APPL_TOP=/xyz/oracle/xyzappl

Please review: press ‘Y’ to accept or ‘N’ to re-enter[Y]: <ENTER>
Oracle Applications Tablespace Migration Utility

Main Menu
1. Migration Sizing Reports
2. Create New Tablespaces
3. Generate Migration Commands
4. Execute Migration Commands
5. Run Migration Status Reports
6. Run Post Migration Steps
7. Run Customization Steps
8. Run Migration in Batch Mode

[Q]uit [N]ext

Please enter your option – 3
Generate Migration:

Generate Migration Commands

Generation of Migration commands including disable/enable
commands for triggers, constraints, policies, stop/start for queues.

  1. Invalid Indexes Report. Please correct/drop these before
    generating migration commands

  2. Generate migration commands for all schemas

  3. Generate migration commands for a list of schemas

[Q]uit [B]ack [N]ext

 

Please enter your option –

Option 1: It should be run to find out the invalid index report.Then these index either should be dropped or recreated
Option 2: Generate migration commands for all schemas.Run Option 1 to generate the commands for migrating the objects in all the schemas into the correct tablespace.
The migration commands are stored in the table FND_TS_MIG_CMDS.
You can check the generated log file fndgmcmd<timestamp>.log for errors during the generation process. A threshold object size is asked determine whether an object will be moved sequentially or in parallel.Migration commands for all objects with total blocks greater than or equal to threshold blocks are generated with the PARALLEL clause and execution mode as sequential. Migration commands for objects with total blocks less than threshold are generated with NOPARALLEL clause and execution mode as parallel.
Partitioned objects will always get executed sequentially irrespective of their size.

Option 3 is to generate the commands for migrating the objects in list of schema into the correct tablespace. The migration commands are stored in the table FND_TS_MIG_CMDS.
You can check the generated log file fndgmcmd<timestamp>.log for errors during the generation process. A threshold object size is asked determine whether an object will be moved sequentially or in parallel.Migration commands for all objects with total blocks greater than or equal to threshold blocks are generated with the PARALLEL clause and
will get executed sequentially. Migration commands for objects with total blocks less than threshold are generated with NOPARALLEL clause and will get executed in parallel using multiple processes. Partitioned objects will always get executed sequentially irrespective of their size.

Please enter your option – 2

Enter the threshold blocks for Sequential processing[10000]: <Enter>

Command generation successful. Please check the log
$APPL_TOP/admin/$TWO_TASK/log/fndgmcmd*.log

All the related OATM material are

OATM lesson 1

Migration sizing report

Migration Status Reports

Execute Migration command


Leave a Reply