on 09-30-2011 3:35 AM
I had perform a system copy with different system ID from the source system successfully. I encounter some problem during the STMS configuration. I already set all the configuration for the target system but when I tried to transport one configuration from one client to another, it prompts out error as below:
Transport control program tp ended with error code 0247
Errors: addtobuffer has problems with data- and/or cofile
However, when I check back the source system, there are no such problem even without the 2 files above.
Hi,
Have you reconfigured STMS after system copy again ? Does these data and cofiles present at OS level ?
Thanks
Sunny
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
After system copy, you need to delete old STMS configuration then add again to domain controller. If you have already done this then it is fine.
OS means operating system, on your operating system, go to /usr/sap/trans and there check in data and cofile folder that whether data and cofiles of that transport exists or not.
Thanks
Sunny
If I did not use the same name as the source system database, the transport number will begin with the new system ID. Is there way where I can import the transport number from the source system to the target system?
In normal practice, SID of development, quality and production system's SID's are different, and we do the transport between these systems. So, answer of your question is you can do the transport if SID is different.
My question to you are :
Have you reconfigured STMS after system refresh ? What is role of the system that is created after system copy ? What is transport route of your systems in which are doing transport ?
Thanks
Sunny
I already configure the STMS and I was able to transport between client in the current development server. However, if I need to have the transport number of the old development server import to the current development server, I'm not able to do so. My route is transport from the current development server transport to production server.
Hi Swiber,
It sounds like you are simply using a different /usr/sap/trans directory compared to the one of your original development system.
logon to your new development server and check the /usr/sap/trans/cofiles directory for the transport you are looking to import, compare this directory to the one on your original development system.
If you do not wish to share the old dev systems /usr/sap/trans directory with the new one copy the cofiles and data files across manually to enable you to catchup any transports you wish to import into the new dev system.
If I have misunderstood your request I apologise.
Regards,
Chris
Edited by: Chris O'Haire on Oct 4, 2011 3:23 AM
I encounter error when i tried to add the request in the production server. I suspect this might be because the request does not exist in cofile and data folder. So, I would like to know why the it does not create by itself in the production server?
Transport control program tp ended with error code 0247
Message no. XT200
An error occurred when executing a tp command.
Command: ADDTOBUFFER DEVK900010 PRD pf=\\swisapfs01\sapmnt\
Return code: 0247
Error text: addtobuffer has problems with data- and/or cofile
Request: DEVK900010
The function terminates.
Correct the error and execute the command again if necessary.
Hi,
As said by Chris, You should first check the transport directory of both the systems. Do they share the common trans dir or different? Co-files and data files are generated when the transport is released not every time you add it to the add to buffer or import to a new system.
Regards,
Vamshi.
User | Count |
---|---|
93 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.