on 05-14-2008 5:40 PM
Hi Friends,
When i run the TPCheck all , i getting the following error, please help me friends what to do.
ebswidp2:bpmadm 134> tp check all pf=TP_DOMAIN_BPM.PFL
This is tp version 305.13.23 (release 46D) for ANY database
/usr/sap/trans/tmp/SLOG0820.ALL.LOC: No such file or director
PANIC --> exiting
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0212
tp finished with return code: 212
Please help me friends what to do.
thanks.
Hi,
in addition for Mr. Markus suggestion
check permission of /usr/sap/trans/tmp
regards,
kaushal
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
> ebswidp2:bpmadm 134> tp check all pf=TP_DOMAIN_BPM.PFL
> This is tp version 305.13.23 (release 46D) for ANY database
> /usr/sap/trans/tmp/SLOG0820.ALL.LOC: No such file or director
> PANIC --> exiting
Is that directory (/usr/sap/trans/tmp) existing? Is the /usr/sap/trans mounted?
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HEre is the information i got when i have run the directory
ebswidp2:bpmadm 34> /usr/sbin/mount
/ on /dev/vg00/lvol3 ioerror=mwdisable,delaylog,dev=40000003 on Sun Apr 13 10:11:12 2008
/stand on /dev/vg00/lvol1 ioerror=mwdisable,log,tranflush,dev=40000001 on Sun Apr 13 10:11:14 2008
/var on /dev/vg00/lvol8 ioerror=mwdisable,delaylog,dev=40000008 on Sun Apr 13 10:11:27 2008
/var/opt on /dev/vg00/lvol11 ioerror=mwdisable,delaylog,dev=4000000b on Sun Apr 13 10:11:27 2008
/var/adm/sw on /dev/vg00/lvol9 ioerror=mwdisable,delaylog,dev=40000009 on Sun Apr 13 10:11:27 2008
/var/adm/crash on /dev/vg00/lvol10 ioerror=mwdisable,delaylog,dev=4000000a on Sun Apr 13 10:11:28 2008
/usr on /dev/vg00/lvol7 ioerror=mwdisable,delaylog,dev=40000007 on Sun Apr 13 10:11:28 2008
/usr/sap/bpm on /dev/vg00/lvol23 ioerror=mwdisable,delaylog,nodatainlog,dev=40000012 on Sun Apr 13 10:11:29 2008
/tmp on /dev/vg00/lvol6 ioerror=mwdisable,delaylog,dev=40000006 on Sun Apr 13 10:11:29 2008
/oracle on /dev/vg00/lvol20 ioerror=mwdisable,delaylog,nodatainlog,dev=4000000f on Sun Apr 13 10:11:29 2008
/oracle/stage on /dev/vg00/lvol21 ioerror=mwdisable,delaylog,nodatainlog,dev=40000010 on Sun Apr 13 10:11:30 2008
/oracle/GAM on /dev/vg00/lvol28 ioerror=mwdisable,delaylog,nodatainlog,dev=4000001a on Sun Apr 13 10:11:30 2008
/opt on /dev/vg00/lvol5 ioerror=mwdisable,delaylog,dev=40000005 on Sun Apr 13 10:11:30 2008
/home on /dev/vg00/lvol4 ioerror=mwdisable,delaylog,dev=40000004 on Sun Apr 13 10:11:30 2008
/net on -hosts ignore,indirect,nosuid,soft,nobrowse,dev=4c000000 on Sun Apr 13 10:12:28 2008
/usr/sap/trans/bpm on /etc/auto.direct ignore,direct,dev=4c000003 on Sun Apr 13 10:12:28 2008
/sapmnt/bpm on /etc/auto.direct ignore,direct,dev=4c000004 on Sun Apr 13 10:12:28 2008
/export/sapmnt/bpm on /dev/vgdbcibpm00_01/lvol2 ioerror=mwdisable,delaylog,nodatainlog,dev=400e0002 on Sun Apr 13 10:42:30 2008
/export/usr/sap/trans/bpm on /dev/vgdbcibpm00_01/lvol3 ioerror=mwdisable,delaylog,nodatainlog,dev=400e0003 on Sun Apr 13 10:42:30 2008
/oracle/bpm on /dev/vgdbcibpm00_01/lvol4 ioerror=mwdisable,delaylog,nodatainlog,dev=400e0004 on Sun Apr 13 10:42:31 2008
/oracle/bpm/sapreorg on /dev/vgdbcibpm00_01/lvol5 ioerror=mwdisable,delaylog,nodatainlog,dev=400e0005 on Sun Apr 13 10:42:31 2008
/usr/sap/bpm/DVEBMGS00 on /dev/vgdbcibpm00_01/lvol6 ioerror=mwdisable,delaylog,nodatainlog,dev=400e0006 on Sun Apr 13 10:42:31 2008
/oracle/bpm/saparch on /dev/vgdbcibpm00_02/lvol1 ioerror=mwdisable,delaylog,nodatainlog,convosync=direct,dev=400f0001 on Sun Apr 13 10:42:31 2008
/oracle/bpm/origlogA on /dev/vgdbcibpm00_03/lvol1 ioerror=mwdisable,delaylog,nodatainlog,convosync=direct,dev=40100001 on Sun Apr 13 10:42:31 2008
/oracle/bpm/origlogB on /dev/vgdbcibpm00_03/lvol2 ioerror=mwdisable,delaylog,nodatainlog,convosync=direct,dev=40100002 on Sun Apr 13 10:42:31 2008
/oracle/bpm/sapdata1 on /dev/vgdbcibpm00_04/lvol1 ioerror=mwdisable,mincache=direct,delaylog,nodatainlog,convosync=direct,dev=40110001 on Sun Apr 13 1
0:42:32 2008
/oracle/bpm/sapdata2 on /dev/vgdbcibpm00_04/lvol2 ioerror=mwdisable,mincache=direct,delaylog,nodatainlog,convosync=direct,dev=40110002 on Sun Apr 13 1
0:42:32 2008
/oracle/bpm/sapdata3 on /dev/vgdbcibpm00_04/lvol3 ioerror=mwdisable,mincache=direct,delaylog,nodatainlog,convosync=direct,dev=40110003 on Sun Apr 13 1
0:42:32 2008
/oracle/bpm/sapdata4 on /dev/vgdbcibpm00_04/lvol4 ioerror=mwdisable,mincache=direct,delaylog,nodatainlog,convosync=direct,dev=40110004 on Sun Apr 13 1
0:42:32 2008
/oracle/bpm/sapdata5 on /dev/vgdbcibpm00_04/lvol5 ioerror=mwdisable,mincache=direct,delaylog,nodatainlog,convosync=direct,dev=40110005 on Sun Apr 13 1
0:42:32 2008
/oracle/bpm/sapdata6 on /dev/vgdbcibpm00_04/lvol6 ioerror=mwdisable,mincache=direct,delaylog,nodatainlog,convosync=direct,dev=40110006 on Sun Apr 13 1
0:42:32 2008
/sapmnt/bpm on dbcibpm:/export/sapmnt/bpm nodevs,rsize=32768,wsize=32768,NFSv3,dev=4c000012 on Sun Apr 13 10:42:34 2008
/upgrade on /dev/vg01/lvol1 ioerror=mwdisable,delaylog,nodatainlog,dev=40190001 on Tue Apr 15 06:16:53 2008
ebswidp2:bpmadm 35>
> /usr/sap/bpm on /dev/vg00/lvol23
> /usr/sap/trans/bpm on /etc/auto.direct
> /sapmnt/bpm on /etc/auto.direct
> /export/usr/sap/trans/bpm on /dev/vgdbcibpm00_01/lvol3
I must admit, you have a strange filesystem setup. It's not clear to me, where you actual transport directory resides (on /usr/sap/trans/bpm or /export/usr/sap/trans/bpm or if this maybe the same directory just somehow "linked").
To me it seems, that you profile TP_DOMAIN_BPM.PFL points to the "normal" /usr/sap/trans dirctory (you can open it and check it) but the correct directory is a different one.
Did you set that up? If not, the I would contact the responsible admin to either adapt the profile paths in STMS correctly (or give you an information what is the correct trans directory...)
Markus
No i didn't set this up. Any how they are going for an upgrade.
But my main issue was i wanted to delete the below files which are existing from 2003,
Data files
Cofiles
Log files
For transport files i was trying to run command tp check all in order to find out the files which are not required.
This was my main problem.
Before deleting the file i want to be sure.
Please help.
Rama,
I could tell you to delete /usr/sap/bpm/trans/cofile* and /export/usr/sap/trans/cofile* etc. but since I have no clue how your system is set up (in transaction STMS) and what the person who set it up thought by doing so it would most probably bring more harm than any success.
What we can try to find out, what the correct profile is we can do the following:
- logon in client 000 with a different user than DDIC
- start transaction SPAM
- execute "Utilities - Check transport tool"
If that test works, drill up the "tp interface" and the "transport profile" and post the results here so we can see what directory is the correct one and then suggest how to proceed.
Markus
Hi,
I have done as you said, here is the message
tp interface
Host name ebswidp2
Version 1.70
Transport directory /usr/sap/trans/BPM
Logging On (TPLOG contains 42913 entries)
Transport profile
Path /usr/sap/trans/BPM/bin/TP_DOMAIN_BDM.PFL
Profile TP_DOMAIN_BDM.PFL is readable
Version Version 0053 (domain DOMAIN_BDM)
Thanks,
rama
This what i got after running
ebswidp2:BPMadm 26> tp check all pf=/usr/sap/trans/BPM/bin/TP_DOMAIN_BDM.PFL
This is tp version 305.13.23 (release 46D) for ANY database
check>Log file is written to /usr/sap/trans/BPM/tmp/CHECK.LOG
check>
check>Collected 15 filenames from [/usr/sap/trans/BPM/buffer/.]
check>Collected 5 Systemnames from [/usr/sap/trans/BPM/buffer/.]
check>Collected 00006 out of 00006 entries from buffer BPM.
check>Collected 00006 entries from buffers
check>.
check>Collected 7081 filenames from [/usr/sap/trans/BPM/cofiles/.]
check>Found 0 invalid filenames on Cofile-directory
check>HALT 20080516140645
ERROR: A target system group (/MSTR_CFG/) is used with a name longer than 3.
This is only possible with NBUFFORM=TRUE!
ERROR: EXIT(16) -> process ID is: 21143
tp returncode summary:
TOOLS: Highest return code of single steps was: 16
ERRORS: Highest tp internal error was: 0204
tp finished with return code: 204
meaning:
parameter is missing
Now what do u suggest me to do?
> ebswidp2:BPMadm 26> tp check all pf=/usr/sap/trans/BPM/bin/TP_DOMAIN_BDM.PFL
> This is tp version 305.13.23 (release 46D) for ANY database
>
> check>Log file is written to /usr/sap/trans/BPM/tmp/CHECK.LOG
>
> check>
> check>Collected 15 filenames from [/usr/sap/trans/BPM/buffer/.]
> check>Collected 5 Systemnames from [/usr/sap/trans/BPM/buffer/.]
> check>Collected 00006 out of 00006 entries from buffer BPM.
> check>Collected 00006 entries from buffers
> check>.
> check>Collected 7081 filenames from [/usr/sap/trans/BPM/cofiles/.]
> check>Found 0 invalid filenames on Cofile-directory
> check>HALT 20080516140645
> ERROR: A target system group (/MSTR_CFG/) is used with a name longer than 3.
> This is only possible with NBUFFORM=TRUE!
> ERROR: EXIT(16) -> process ID is: 21143
You have really interesting problems
You need to add NBUFFORM=TRUE to your tp options:
- logon in client 000 on the domain controller for that transport domain (most likely that is system BDM)
- start STMS
- Overview - Systems
- open each system and add in the tab "transport tool" NBUFFORM with the value TRUE (or 1)
- save all changes
- distribute the changes to the profile
Then try again your check all.
Markus
Sorry for asking, As this is our PRD system , can i make changes, will that have any effects. Do i need to restart the system for the changes to take into effect.
I can raise a request for making changes for again the changes have to go from development and then test then PRODUCtion.
IS it is okay if i make changes directly on PRD system.
Thanks,
rama
> Sorry for asking, As this is our PRD system , can i make changes, will that have any effects. Do i need to restart the system for the changes to take into effect.
>
> I can raise a request for making changes for again the changes have to go from development and then test then PRODUCtion.
>
> IS it is okay if i make changes directly on PRD system.
I really wonder how this transport group can work without this option, means, how you're able to transport through that group...
What we can try without making those changes directly in the TMS is giving that option manually:
tp check all pf=/usr/sap/trans/BPM/bin/TP_DOMAIN_BDM.PFL -DNBUFFORM=TRUE
Markus
This is the error i am getting now
This is tp version 305.13.23 (release 46D) for ANY database
FATAL ERROR: Command line options '-D' not correctly maintained for
client transport control or new buffer format.
Check the online documentation of parameters CTC and NBUFFORM respectively.
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 TPPARAM (param missing, unknown,...)
Now it gives the follwoing error
ERROR: : parameter NBUFFORM=TRUE is unknown
Usage of command CHECK:
tp CHECK ALL
Generates a list of old files in the transport system.
Options:
data|log|cofiles|sap consider specified directory only
verbose print more information to stdout
pf=<TPPARAM> specify a parameter file
silent redirect stdout to dev_tp in current directory
-D"<entry>" specify a parameter for tp
-t<k> specify a trace level for tp
tf=<filename> specify the name of a trace file for tp
shdwtadir=<tabname> specify the name of a shadow TADIR
Description of arguments:
<TPPARAM> (complete) path of a tp parameter file
<entry> a parameter description as in a tp parameter file
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0205
Rama,
this parameter has to be added in the configuration to enable your check. Since I don't know your system landscape, your transport routes and how this is set up I can just recommend to open a call @ SAP and let someone look on the system.
You could enter that parameter as described for the affected systems using STMS in client 000 on the domain controller but as said, since I don't know how many other systems are connected and how they are set up I can't say if that will have an influence. I would need to have a look on the system to judge that.
I recommend: Open an OSS call, give them the result of the latest tp check all that was running and giving that "NBUFFORM=TRUE!" error and ask for assistance.
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.