Oracle applications tablespace Migration Tutorial part 5



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

Oracle applications tablespace Migration

The next space after generation of migration command would be executing the commands.Here is  the final Oracle applications tablespace Migration happens

We need to follow below things before moving on this steps
1) Take a full backup of the database
2) The migration is very I/O intensive,So we need to make sure everything is good from OS and network perspective
3) Check all the database parameter and set as per the guidelines for optimal performance
4) There should be enough TEMP tablespace for this to succeed

[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 – 4
Execute Migration Commands

Execution of Migration commands including disable
commands for triggers constraints, stop/start for queues.

PLEASE TAKE COMPLETE BACKUP OF THE DATABASE BEFORE MIGRATION

  1. Migrate all Schemas
  2. Migrate a list of Schemas
  3. Migrate CTXSYS Schema
    Note: Migrate CTXSYS schema when no other migration process is in progress.

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

Please enter your option – 1

Please enter your option – 1
Are you sure you want to migrate all schemas[N]: Y
Enter the maximum number of parallel processes for TEST[15]: 15

Starting the Migration process for all schemas. Please wait…

Migration processes for tables with LONG and LONG RAW columns started in the background. Please monitor the log file //xyz/oracle/xyzappl/admin/TEST/log/fndmlongzdfff.log for errors and completion of this migration process.

Sequential migration process started in the background for TEST. Please monitor the log file /xyz/oracle/xyzappl/admin/TEST/log/fndemseqDDDdd.log for erro
rs and completion of this migration process.

Parallel migration processes started in the background for TEST. Please monitor the log file //xyz/oracle/xyzappl/admin/TEST/log/fndemcmdufyrufuf.log for errors and completion of this migration process.

OATM Utility processes are running in the background. sql*plus sessions and one JRE session are spawned in the background. You can monitor those sessions from the OS. Please donot kill any of those sessions as it will adversely affect migration process and result in errors. Monitor migration by running migration progress report.

Press Return key to return to the menu…
The session overview

OATM V$SESSIONS SQL-Activity

sqlplus /nolog
CONNECT / as SYSDBA

SELECT status, module, sid, serial#
FROM v$session
WHERE module in
(‘TS_MIGRATE_SEQUENTIAL_OBJECTS’,
‘TS_MIGRATE_PARALLEL_OBJECTS’, ‘TS_MIGRATE_LONGS’,
‘TS_SIZING’, ‘TS_GEN_SCRIPT’, ‘TS_SET_DEFAULTS’,
‘TS_CREATE_TABLESPACE’, ‘TS_DISABLE_CMDS’,
‘TS_GENERATE_STATEMENTS’, ‘TS_POSTMIGRATION_STEPS’)
AND status <> ‘KILLED’;

Migration processes for tables with LONG and LONG RAW columns runs in a single session.
Sequential migration process started in the background . It is run with parallel option.So it used parallel_max_servers as the parameter to maximise the throughput
alter table AP.AP_CHECKS_ALL move APPS_TS_TX_DATA parallel;
Parallel migration processes started in the background. It is run with number of parallel threads given with no parallel option

alter table APPLSYS.FND_USERS move APPS_TS_SEED noparallel;

All the related OATM material are

OATM lesson 1

Migration sizing report

Generate Migration commands

Migration status report

 


Leave a Reply