on 07-19-2010 10:32 PM
Hi Everybody,
We are having a problem in our STMS QAS queue
Always when we create a request in DEV and release, 2 requests
appear in the STMS QAS queue.
We already deleted the data and cofiles for these 2 requests.
Besides we already deleted the request by STMS -menu Request-Delete and the problem persists.
We are using UNIX as S.O
Any suggestion?
Maybe one place that we forgot the requests should be deleted too?
Best Regards,
Fábio Karnik Tchobnian
Hi,
For clarification, if you release one request from development are there two entries written to the QAS queue? If so, what are the transport numbers for the two entries?
Do you not want these entries to be moved to the QAS queue?
WL
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Juan ,
Hi i entered as sidadm and have done the command below:
Please see the error.
dec:decadm 49> tp delfrombuffer PECKX00009 DEC
This is tp version 372.04.71 (release 700, unicode enabled)
E-TPSETTINGS could not be opened.
EXIT
Error in TPSETTINGS: transdir not set.
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0208
tp finished with return code: 208
meaning:
error in transportprofil (param missing, unknown,...)
What does it mean?
Regards,
Fábio Tchobnian
Hi Wayne,
For clarification, if you release one request from development are there two entries written to the QAS queue? If so, what are the transport numbers for the two entries?
If i create a request A in DEV the request appear in QAS as number 1 plus after some time 2 requests that i can call X and Y
with number 2 and 3.
The X and y are old requests created in the past (2007)
Do you not want these entries to be moved to the QAS queue?
Yes i want to remove that from the QAS queue forever.
I already deleted the data and cofiles for the 2 requests that
for my surprise was in the QAS system.
Best Regards,
Fábio Karnik Tchobnian
Juan ,
Hi i entered as sidadm and have done the command below:
Please see the error.
dec:decadm 49> tp delfrombuffer PECKX00009 DEC
This is tp version 372.04.71 (release 700, unicode enabled)
E-TPSETTINGS could not be opened.
EXIT
Error in TPSETTINGS: transdir not set.
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0208
tp finished with return code: 208
meaning:
error in transportprofil (param missing, unknown,...)
What does it mean?
Regards,
Fábio Tchobnian
HI Wayne,
Make sure you are in directory /usr/sap/trans/bin when you execute this command.
Also, in transaction STMS you can go in to the QAS buffer, highlight the request and do a Request --> Delete and get the same result.
Ok , i have done it by STMS, lets discard the command .
So the issue is the X and Y requests that keep showing up in the QAS buffer? Otherwise STMS is working OK?
Yes for the issue. STMS is working fine. .
IAnother information is that X and Y requests was created directly in QAS.
Best Regards,
Fábio T
Hi Fio,
Error in TPSETTINGS: transdir not set.
You'll need to setup your TRANSDIR parameters for your systems if you want to call the tp program at the OS level.
- I removed the file QAS in /usr/sap/trans/buffer/ in DEV and
/usr/sap/trans/buffer in QAS system with devadm and qasadm.
Do you have 2 different /usr/sap/trans/buffer directories? The transport directory <TRANSDIR> (default value for Unix: /usr/sap/trans) should be shared among the domain controller and the systems involved. Maybe that's why your requests are duplicated. When the tp program is called from SAP system, this value is overwritten by the DIR_TRANS parameter of the instance profile (domain controller).
Hope it helps.
Regards,
Dao
Try using command tp delfrombuffer <request> <sapsid> , that shgould remove the request from the import buffer.
Regards
Juan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.