Skip to Content
avatar image
Former Member

Impact on Live ECC6 Production during data migration through TDMS


We are implementing TDMS 4. We are planning for test landscpes to be used for TDMS solution acceptance test. As per our company policy, we need to do a live test with production before declaring production system is ready for service (RFS). We want to migrate (Full client copy, Time based and Process based) test data from live proction through TDMS. Our production data size 2.62TB. I need to know following information:

Production Server spec: (Sender)

App Server1: CPU: 4 core, Memory: 44GB, HP-UX B.11.31, DB: Oracle 11g, ECC 6.0 EHP5

App Server2: CPU: 4 core, Memory: 44GB, HP-UX B.11.31, DB: Oracle 11g, ECC 6.0 EHP5

DBCI Server1: CPU: 4 core, Memory: 48GB, HP-UX B.11.31, DB: Oracle 11g, ECC 6.0 EHP5, Storage: 3.1TB

Standby DBCI Server1: CPU: 4 core, Memory: 48GB, HP-UX B.11.31, DB: Oracle 11g, ECC 6.0 EHP5

Qality Server spec: (Receiver)

CPU: 4 core, Memory: 24GB, HP-UX B.11.31, DB: Oracle 11g, ECC 6.0 EHP5, Storage: 2.4, Used: 2.2

Solution Manager 7.1 Server spec: (Controller)

CPU: 4 core, Memory: 36GB, HP-UX B.11.31, DB: Oracle 11g, ECC 6.0 EHP5, Storage: 1TB, Used: 0.5TB

Test cases:

1. Full client copy

2. Time based data transfer

3. Process based data transfer

4. Data scrambling

5. Data deletion - reduce current storage in non-production environment

1. How much time it may take to complete full client copy

2. What are the impact we may face during this data transfer - business impact

3. What are the precautions we need to take before executing data transfer

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    Oct 16, 2015 at 07:59 PM

    Hi Mohammad, i worked in a few TDMS proyects, mainly in Time based data transfer, and as per my experience i can tell you the following:

    1.-

    The total time that TDMS takes to do the copy is very variable, depends on the resources asigned to the TDMS process, because you can assign a number of workprocess (Dialog and batch) to do the copy, , the copy scenario (the total data to transfer is not the same for every scenario) and the hardware resources of the reciver and sender systems. I recomend you verify the SAP Notes with recomendations for the three systems: Sender, reciver, control and database (there are some oracle parameters to adjust for example), and do a test copy first to fix the process in next TDMS copies.

    2.-

    The impact is due to the fact that TDMS uses dialog and batch workprocess (in sender and reciver) to copy. You can control the number of WP assigned to the TDMS process (in some cases), but the recomendation is to run the copy process in time of low activity in the sender system (Productive).

    At database level, the TDMS create a cluster table of size aprox. 10% of the data transfer. You need to provissioning this space at tablespace level. So some performance issues may occur.

    3.-

    I thik you need to verify the DB space and resources (number of Workprocess available), and choose the best time frame to run your TDMS tests scenarios.

    I hope help in your doubts.

    Thanks and best regards.

    Hector.

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 19, 2015 at 06:51 PM

    Your PRD DB Size of 2,3 TB is relatively small, and you definitely have enough HW resources to start TDMS Roll-out project.

    Your primary goal should be STABLE run first, than you can gradually improve performance using different technique, described in "How-to Improve Performance for Data Transfer" Guide.Understand each Package phase in details, troubleshoot proactively, check all logs, ST22 dumps etc. In the actively running Production environment your worst 'enemy' could be annoying ORA-1555 (Snapshot too old) error - so fine tune DB indexes and collect fresh Optimizer statistics to avoid inefficient long-running SELECTs on the largest frequently changing ERP app.tables. Preferably run TDMS package when PRD system is at rest.

    TDMS workload is manageable, risk to impact PRD operations is minimal, start small with 8 default processes, then you always can add more TDMS job slots on-the-fly having enough free BATCH and DIA processes available.  

    When you start Data Deletion and Data Transfer into the Multi-Client environment with actively working users in other clients, they may face some terminated updates and other abnormalities because of mass array deletion/insertion technique used in TDMS, which may impact not just target client, where business users should be locked, but entire Receiver system for the short time.

    Good Luck,

    Andrei

    Add comment
    10|10000 characters needed characters exceeded