Knowledge Management

Question:
We have a transport that is classed as released but on trying to "addtobuffer" the message "Neither datafile nor cofile exist <cofile may be corrupted>". Therefore, we cannot proceed. Neither can we review the contents of the transport.
Is there anything we can do to fix this ?
Thanks
Jim
Answer:
First at all you should verify that you really have lost data and cofile.
Check if the file exist at operating system level. May be it is a permisisons problem.
I don't understand why you can not see the obecjt list from the system ( se01). I think this information is stored in the database, not in the operating system.
If you see the object list in the transport request you can include it in a new request and transport this new request, but you have to do it carefully. Keep in mind that tha obecjects may have changed between the first request relesase and today.
Answer:
Maybe the cofiles and data are owned by root
you should see
they are like the number of the order transport
not in the same order
like K00312358.C11
and R00312358.C11
If it s released and you cant see it you can try by
STMS
see the SID you are looking for
for example C11
and then right clic and choose system
you will be abble to add it again to the buffer
Adel
Answer:
I don't understand why you can not see the obecjt list from the system ( se01). I think this information is stored in the database, not in the operating system.
Info is stored on the OS level and only in the database after the transport (import phase) was done.
Regards,
Answer:
The information is also stored in the databse of the source system, isn't it?
If the request has not been exported in a system of his landscape i agree with you but that information has not been provided by Jim.
Answer:
Hi Adela,
We have a transport that is classed as released but on trying to "addtobuffer" the message "Neither datafile nor cofile exist <cofile may be corrupted>". Therefore, we cannot proceed. Neither can we review the contents of the transport.
As said by Jim, he's doing a tp addtobuffer meaning he's doing the initial phase of transport ... this also means that he's doing it on a different system since he wouldn't get an error if he did it on the same system ... in other words the information was provided by Jim ...
Regards,
Answer:
Thanks Bubu but just to clarify setup...
We have a 2 system landscape at Rel 4.0B - Development and Production. The transport was released on the Dev box and the problem does arise at the Prod side.
FYI, we have done other transports OK since this one was created which adds to the confusion.
Jim
Answer:
Hello,
Just verify that the transport is not a LOCAL transport (Transaction SE01)!!! Because if the transport is a local transport SAP do not create a Cofile and neither a data file...
Regards.
Pascal.
Answer:
Pascal,
The Transport is NOT a local transport.
Regards
Jim
Answer:
Jim,
Do you see the object list from SE01.
If not, how do you know the request has really existed on your system?
Answer:
The list of objects included in SE01 are...
_______________________________________________________
4 Object list of request
5 View maintenance: Data
V_T459A
V_T459K
V_T461P
V_T461S
____________________________________________________________
Jim
Answer:
If you still want to transport that data you can create a new request and include the obects from the old request.
Then you release it and you will have that obecjts in the new request.
The only problem you can have is that the data in the view has changed between the release of the first request and today.
In that case you would transport diferent information.
Do you undertand me?
My advice is ask to the consultant to repeat the request ( they should know what the order contaans).
Answer:
Could it be that in the system where the error occurred, the transport directory /usr/sap/trans being read by the system is the local directory because the NFS /usr/sap/trans is not mounted? If this is the case, just mount the directory and try the transport again.