Released request in DEV system not showing up in the QA system

[Former Member]

TR Released in the ECC DEV but its not showing up in the ECC QA system.

Due to this we are unable to import two Transports requests.

But other Transports are reflecting in QA.

When I am trying to manually add it following is the error I am getting

This is tp version 372.04.40 (release 701, unicode enabled)

Warning: Parameter IMPDP_BY_EVENT is no longer used.

Warning: Parameter STARTDB is no longer used.

Warning: Parameter IMPDP_BY_EVENT is no longer used.

Warning: Parameter STARTDB is no longer used.

Warning: Parameter DBLIBPATH is no longer used.

Addtobuffer failed for RDNK920074.

Neither datafile nor cofile exist (cofile may also be corrupted).

standard output from tp and from tools called by tp:

tp returncode summary:

TOOLS: Highest return code of single steps was: 0

ERRORS: Highest tp internal error was: 0247

Please Suggest to resolve this issue.

Thanks,

Shiva

[anindya_bose · Accepted solution]

Hi Shiva

>Neither datafile nor cofile exist (cofile may also be corrupted).

Did you check if cofile ( starts with K) and datafile( Starts with R) are there in usr/sap/trans/cofile and usr/sap/trans/data respectively? If those are not there then the TR might have been released as "Local Change Request" instead of with some target system.

If you find , those datafiles and cofiles are there, then your cofile might get corrupted as the error message is indicating.

You can create a new transport of copies ( from SE01) with a target system and include objects from the old request. Then release the request. Check if that is coming to your QAS import queue.

[former_member66264]

First:

are you sure the request is released and the data cofile exist?

ownerships of the files are ok?

can you post the export log of this transport ( on dev via SE01 for example?)

Rgds

Nico

[former_member66264]

First:

are you sure the request is released and the data cofile exist?

ownerships of the files are ok?

can you post the export log of this transport ( on dev via SE01 for example?)

[Former Member]

Try adding it through OS level, login as <sidadm> and run command tp addtobuffer <TRnumber> <SID> pf=< Transport profile>

Provided, the data and cofiles in the respective folders

Regards

Jose

Edited by: J. James on Nov 11, 2009 11:26 PM