Alternatives- Homogenous / Heteregenous system copy
Considerations- Archive log mode, Rollback Segments & Temporary Tablespace, Parallel Proccessing
ARCHIVELOG MODE SWITCH
Disable the archive log mode either through the sapdba or svrmgrl:
svrmgrl> startup mount
svrmgrl> alter database noarchivelog;
svrmgrl> shutdown immediate
svrmgrl> startup
Check the archive log mode:
svrmgrl> archive log list
ROLLBACK SEGMENTS
Rollback Segments; create a big rollback segment and take the other RBS's offline:
svrmgrl> create rollback segment RB_BIG tablespace PSAPROLL storage (initial 800m next 400m optimal 800 minextents2 maxextents 500 )
svrmgrl> alter rollback segment "RB_BIG" online;
svrmgrl> alter rollback segment "RB_01" offline;
Monitor the rollback segment growth:
V$ROLLNAME V$ROLLSTAT(optimal value is in this view) DBA_ROLLBACK_SEGS
svrmgrl> select n.name, s.extents, s.size, s.optsize from v$rollname n, v$rollstat s;
Drop the rollback segment:
svrmgrl>drop rollback segmnet RB_BIG;
TEMPORARY TABLESPACE
Monitoring the usage:
DBA_SEGMENTS, V$SORT_USAGE, V$SORT_SEGMENT
PARALLEL PROCCESSING
At SCCL set the parallel proccessing prior to the client copy. Rule of thumb "Two proccesses per CPU" You can check how many CPU's you have at ST06--> Detailed analysis.
OSS notes:
67205- Large client copy
70290- Table exclusion
69444- Client copy error messages
22514- Client copy error analysis
24853- Client copy functionality
70547- Client transport functionality
102034-Commit intervals
118823 - Client size