Target TDMS Client too big.

[Former Member]

Hi.

We are coping our production system using TDTIM scenario (1 month). The

TDMS system estimates (Display Data Transfer Volume task) the target

client size in 330 GB approx. But in the running phase of the "Start

data Transfer" the target client grows to 750 GB consuming the

available space of the server. Then we have canceled the transfer.

For example, some tables were completely copied to the target client,

even with the TDTIM scenario: CE4PA00_ACCT for example.

For the transfer we used the approach documented in the on line help as:

"If you want to keep the downtime for your receiver system as short as possible, you can use the following alternative approach"

Do you have any idea about this behavior?

Thanks.

Best Regards.

Hector Ganga Castro.

[former_member765639]

Hello,

The estimated volume is quite less then the data which is actually transferred.

The approximate estimate can be determined via transaction DTLMON under the tab runtime information.

Give mass transfer id and access plan id as input ( mass transfer id can obtained from the logs of the activty "Define mass transfer id " and accessplan id can be obtained from table CNVMBTPACK)

Under the tab "Runtime information" , you can calculate the sum of the data calculated for all objects to get total data to be transferred. Also this also not exact but most approximate.

Regarding the tables which are fully transferred by TDMS, you can also skip if you dont require them in the receiver.

Thanks and Regards

Isha

[Former Member]

Thanks. But actaully, the stimation size obtined throught activity "Display Data transfer Volume" is about 300 GB, but in transaction DTLMON, in the runtime tab the transfer size is 700 GB, with 2 tables of 200 GB each one.

Do you know why the inconsistence between the two stimations?

Thanks and best regards.

[former_member765639]

The volume calculated in system analysis phase is just a rough estimation which is calculated by the extrapolation of the

statistical values.

Also sender system might have grown during the time lag between the volume calculated in "System Analysis" phase and actual data selected in "Data Transfer" phase.

Note also that the transfer volume is not the same as the volume increase of the receiver system. This growth value is determined rather by other factors, such as indexes (primary index, secondary index) and data compression etc.

Edited by: Isha Sukhija on Mar 29, 2011 7:40 AM

[Former Member]

Some tables are required to be transferred in full, so do not worry about some table getting transferred in full

As you said that you have stopped the data transfer, you may try and do a database re-org to free up some space and then restart the data transfer.

Hope this helps.

[Former Member]

Thanks for your answer, but what about the stimation size in the pahse "Display Data Transfer Volume"?. The system stimates aprox. 330 GB of data transfer, but with the 30 % of the transfer completed, the size of the target client was about 700 GB, and the table CE4PA00_ACCT is about 200 GB in the source client, and consecuent, in the target client.

Best regards.

[Sandeep_Kumar]

For table CE4PA00_ACCT , you may check whether this table is required in full or can it be reduced based on some selection group.