client export fail with tp could not be started

[Former Member]

Hi exper,

i want to client export from PRD to QAS, but always fail with error message "Could not start transport control program tp, Transport program tp could not be started (RC=  9)" database total almost 300GB, the process run time 33hr with 33GB data export, than get this fail message, please tell me how to fix it?

[paul_power · Accepted solution]

Hello Edward,

First, check the tp version using

tp -v

command

I would strongly suggest to update to the latest tp (and R3trans while there) from the service marketplace. they are located alongside the kernel sections of the marketplace.

You mention that the DB is very large, the following notes may help reduce the size of the export and give further tips:

1537913 - Client Copy: Local & Remote copies, Client
Export/Import and Client deletion

Here are some usefull notes about client copies:

67205  - CC-INFO: Copying large and productive clients

You can use the report RSCCEXPT for putting the tables in exception
list. You can find out these from your dba, then you can transporting
them separately, ie, you can transport the entries manually by calling
transaction SE09 and including the transport object R3TR TABU <table
name> with the corresponding table keys in your transport request. And
then import the request in the target system using STMS.

Note #70290 CC-INFO: Excluding tables with 'RSCCEXPT'

Regards,

Paul

[Former Member · Accepted solution]

Hi Paul

i update tp, R3trans a few days ago, it still client export fail. regarding report RSCCEXPT, this using remote copy or client export? anyway for you solution i will try it.

Best regards,

Edward

[Former Member]

Hi Paul

i update tp, R3trans a few days ago, it still client export fail. regarding report RSCCEXPT, this using remote copy or client export? anyway for you solution i will try it.

Best regards,

Edward

[tomas_black]

Hi Edward,

adding to Paul's reply, please check the details of the failed CC logs. There might be a database related error (like ORA-01555). This ORA error usually caused by the commit clash during the export process.

Please make sure the client is protected (without any modification of the system) during the client export when you re-do the client export.

Please review the note 489690

1-a): To keep the runtime as short as possible, note the following points

        a)  Lock the source and target clients

I hope this helps.

Best regards,

Tomas Black

[Former Member]

Hi Tomas

i check CC logs no found ORA errors, refer note 489690, i can't lock the source client to export. and i found out these fail always stop at export the same table, now i try to exclude this table and export again, i hope will success this time.

thanks for your helps

Best regards,

Edward

[tomas_black]

Hello Edward,

ok thanks for getting back to us. Please update this thread after your new attempt.

Best regards,

Tomas Black

[tomas_black]

Hello Edward,

ok, please update the thread in case you still need assistance.        

Regards,

Tomas Black

[Former Member]

Hello Tomas

i extend the parameter:gw/keepalive to 1hr, client export success already.

Regards,

Edward