on 07-10-2007 1:37 PM
hi
i was installed ECC 6.0 version in my system. after installation i check the TPPARAM file. TPPARAM is missed.
how it will come
Thanks
siva kumar
siva.erp@gmail.com
Hi,
Did you run STMS to set up your transport management system? It will create all necessary files on operating system level. The file TPPARAM usually does not exist any more, the profile is called TP_DOMAIN_<SID>.PFL.
Best regards,
Elmar.
Message was edited by:
Elmar Billen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As I said, there is no TPPARAM any more.
<i>> transports are working fine</i>
So what is your problem?
<i>> OS level TP is not working.</i>
Why do you want to use tp at the operating system level? You can use STMS.
If you really need to call tp at the operating system level, try "tp ... pf=/usr/sap/trans/bin/TP_DOMAIN_<SID>.PFL"
Best regards,
Elmar.
hi elmar
C:\Documents and Settings\sapadmin>tp connect SAPVMP pf=e:\usr\sap\trans\bin\TP_
DOMAIN_VMP.PFL
This is tp version 370.01.01 (release 700, unicode enabled)
ERROR: : parameter (null) has wrong length
Usage of command CONNECT:
tp CONNECT <SAPSID> [options ...]
Checks the possibility of connecting to the database of system <SAPSID>.
Additionlly calls R3trans to connect to the database of system <SAPSID>.
In case of a call via RFC tp's and R3trans' source time stamp is returned.
Options:
pf=<TPPARAM> specify a transport 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 transport parameter file
<entry> a parameter description as in a tp parameter file
<SAPSID> R/3 system's name, (target or source whatever is appropriate)
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0206
tp finished with return code: 206
meaning:
parameter %s has wrong length
C:\Documents and Settings\sapadmin>tp connect SAPVMP pf=e:/usr/sap/trans/bin/TP_
DOMAIN_VMP.PFL
This is tp version 370.01.01 (release 700, unicode enabled)
ERROR: : parameter (null) has wrong length
Usage of command CONNECT:
tp CONNECT <SAPSID> [options ...]
Checks the possibility of connecting to the database of system <SAPSID>.
Additionlly calls R3trans to connect to the database of system <SAPSID>.
In case of a call via RFC tp's and R3trans' source time stamp is returned.
Options:
pf=<TPPARAM> specify a transport 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 transport parameter file
<entry> a parameter description as in a tp parameter file
<SAPSID> R/3 system's name, (target or source whatever is appropriate)
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0206
tp finished with return code: 206
meaning:
parameter %s has wrong length
-
I got the above errors
Thanks for your reply
<i>C:\Documents and Settings\sapadmin>tp connect <b>SAPVMP</b> pf=e:\usr\sap\trans\bin\TP_
DOMAIN_VMP.PFL</i>
Is this a typo? The command should be "tp connect <b>VMP</b> pf=....".
If this still does not work, try "tp connect VMP pf=e:\usr\sap\trans\bin\TP_DOMAIN_VMP.PFL -t2 tf=dev_tp" and post dev_tp here.
Best regards,
Elmar.
hi i got the following errors
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
C:\Documents and Settings\vmdadm>tp connect VMP pf=e:\usr\sap\trans\bin\tp_domai
n_vmp.pfl
This is tp version 370.01.01 (release 700, unicode enabled)
Warning: Parameter DBHOST is no longer used.
Warning: Parameter DBNAME is no longer used.
Access denied on
blrsap001\sapmnt\trans\tmp\SLOG0728.VMP.LOC (1)
blrsap001\sapmnt\trans\tmp\SLOG0728.VMP.LOC is already in use (1), I'm waiting
1 sec (20070710202929). My name: pid 5284 on blrsap002 (vmdadm)
Access denied on
blrsap001\sapmnt\trans\tmp\SLOG0728.VMP.LOC (2)
blrsap001\sapmnt\trans\tmp\SLOG0728.VMP.LOC is already in use (2), I'm waiting
3 sec (20070710202930). My name: pid 5284 on blrsap002 (vmdadm)
Access denied on
blrsap001\sapmnt\trans\tmp\SLOG0728.VMP.LOC (3)
blrsap001\sapmnt\trans\tmp\SLOG0728.VMP.LOC is already in use (3), I'm waiting
1 sec (20070710202933). My name: pid 5284 on blrsap002 (vmdadm)
Access denied on
blrsap001\sapmnt\trans\tmp\SLOG0728.VMP.LOC (4)
blrsap001\sapmnt\trans\tmp\SLOG0728.VMP.LOC is already in use (4), I'm waiting
5 sec (20070710202934). My name: pid 5284 on blrsap002 (vmdadm)
Access denied on
blrsap001\sapmnt\trans\tmp\SLOG0728.VMP.LOC (5)
blrsap001\sapmnt\trans\tmp\SLOG0728.VMP.LOC is already in use (5), I'm waiting
3 sec (20070710202939). My name: pid 5284 on blrsap002 (vmdadm)
Access denied on
blrsap001\sapmnt\trans\tmp\SLOG0728.VMP.LOC (6)
blrsap001\sapmnt\trans\tmp\SLOG0728.VMP.LOC is already in use (6), I'm waiting
3 sec (20070710202942). My name: pid 5284 on blrsap002 (vmdadm)
Access denied on
blrsap001\sapmnt\trans\tmp\SLOG0728.VMP.LOC (7)
blrsap001\sapmnt\trans\tmp\SLOG0728.VMP.LOC is already in use (7), I'm waiting
2 sec (20070710202945). My name: pid 5284 on blrsap002 (vmdadm)
Access denied on
blrsap001\sapmnt\trans\tmp\SLOG0728.VMP.LOC (8)
blrsap001\sapmnt\trans\tmp\SLOG0728.VMP.LOC is already in use (8), I'm waiting
5 sec (20070710202947). My name: pid 5284 on blrsap002 (vmdadm)
Access denied on
blrsap001\sapmnt\trans\tmp\SLOG0728.VMP.LOC (9)
blrsap001\sapmnt\trans\tmp\SLOG0728.VMP.LOC is already in use (9), I'm waiting
5 sec (20070710202952). My name: pid 5284 on blrsap002 (vmdadm)
Access denied on
blrsap001\sapmnt\trans\tmp\SLOG0728.VMP.LOC (10)
blrsap001\sapmnt\trans\tmp\SLOG0728.VMP.LOC is already in use (10), I'm waitin
g 4 sec (20070710202957). My name: pid 5284 on blrsap002 (vmdadm)
blrsap001\sapmnt\trans\tmp\SLOG0728.VMP.LOC: Permission denied
PANIC --> exiting
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0233
tp finished with return code: 233
meaning:
SAP-System not installed properly (HEAD SYST)
.LO files in \usr\sap\trans\tmp are used to synchronize access to various files in the SAP Transport environment.
tp.exe will create a lot of them and needs also to be able to delete them.
Before renaming the file you should have a look to it's contents. It will contain the process id and the hostname of the locking process.
You only should delete a lockfile if the lockholder is no longer existing and you find out why the lockfile is left.
regards
Peter
hi
before i gave wrong path
now i give new path. i got follwing errors. can you help me please.
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
C:\Documents and Settings\vmdadm>tp connect vmp pf=f:\usr\sap\trans\tp_domain_vm
p.pfl
This is tp version 370.01.01 (release 700, unicode enabled)
E-f:\usr\sap\trans\tp_domain_vmp.pfl could not be opened.
EXIT
ERROR: System : Parameter SAPEVTPATH not set. Batch jobs cannot be started.
Error in f:\usr\sap\trans\tp_domain_vmp.pfl: 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,...)
thanks
siva
Hi,
can you please post the full error here, as well as the contents of F:\usr\sap\trans\bin\TP_DOMAIN_VMP.PFL?
As I said above, there is usually no need to call tp directly - you can use STMS to manage you transports. Did you set up and distribute a proper STMS configuration? TP_DOMAIN_VMP.PFL is written during the setup of TMS. You can check your settings e.g. with STMS -> Import Overview -> Import Queue -> Check -> Transport Tool. Are there any errors displayed? If yes, can you post them here?
Thanks,
Elmar.
Message was edited by:
Elmar Billen
Hi,
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
C:\Documents and Settings\vmdadm>tp connect VMP pf=F:\usr\sap\trans\TP_DOMAIN_VM
P.PFL
This is tp version 370.01.01 (release 700, unicode enabled)
E-F:\usr\sap\trans\TP_DOMAIN_VMP.PFL could not be opened.
EXIT
ERROR: System : Parameter SAPEVTPATH not set. Batch jobs cannot be started.
Error in F:\usr\sap\trans\TP_DOMAIN_VMP.PFL: 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,...)
C:\Documents and Settings\vmdadm>
-
this is my transport profile
#TMS:0006:DOMAIN_VMP
#U
#
#----
#Caution !
#This file was generated by the Transport Management System.
#Do not change this file using a text editor.
#For further information please see the online documentation of
#transaction STMS.
#If this file was destroyed, it can be regenerated in the TMS.
#To do this, log on to the domain controller (system VMP) and call
#Transaction STMS. In the System Overview, you can distribute the TMS
#configuration. This regenerates the file.
#STMS -> Overview -> Systems -> Extras -> Distribute TMS Configuration
#----
#
#
TRANSDIR =
blrsap001\sapmnt\trans
#
VMD/CTC = 1
VMD/DBHOST = blrsap002
VMD/DBNAME = VMD
VMD/DBTYPE = ora
VMD/NBUFFORM = 1
VMD/TP_VERSION = 266
#
VMP/CTC = 1
VMP/DBHOST = blrsap001
VMP/DBNAME = VMP
VMP/DBTYPE = ora
VMP/NBUFFORM = 1
VMP/TP_VERSION = 266
Obviously, your transport directory is not stored on F:\usr\sap\trans (as you're logged on as vmdadm, I assume that you are on blrsap002) but on
blrsap001\sapmnt\trans.
So, first make sure that vmdadm and vmpadm (as well as SAPServiceVMD and SAPServiceVMP) have r/w access to
blrsap001\sapmnt\trans (there were read/write errors in one of your erlier postings).
Next, if you want to connect to VMP:
- log on as vmpadm on host blrsap001
- execute the command "tp connect VMP pf=
blrsap001\sapmnt\trans\bin\TP_DOMAIN_VMP.PFL"
If you want to connect to VMD:
- log on as vmdadm on host blrsap002
- execute the command "tp connect VMD pf=
blrsap001\sapmnt\trans\bin\TP_DOMAIN_VMP.PFL"
If there are errors, please post them here.
What is the result of the STMS check I recommended to you in my last posting?
- Elmar.
GUI TRANSPORTS FINE
TRANSPORT TOOL FINE
IN VMD ERRORS
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
C:\Documents and Settings\vmdadm>tp connect VMP pf=f:\usr\sap\trans\bin\TP_DOAMI
N_VMP.PFL
This is tp version 370.01.01 (release 700, unicode enabled)
E-f:\usr\sap\trans\bin\TP_DOAMIN_VMP.PFL could not be opened.
EXIT
ERROR: System : Parameter SAPEVTPATH not set. Batch jobs cannot be started.
Error in f:\usr\sap\trans\bin\TP_DOAMIN_VMP.PFL: 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,...)
C:\Documents and Settings\vmdadm>
-
IN VMP ERRORS
C:\Documents and Settings\vmpadm>tp connect VMD pf=F:\usr\sap\trans\bin\tp_domai
n_vmp.pfl
This is tp version 370.01.01 (release 700, unicode enabled)
Warning: Parameter DBHOST is no longer used.
Warning: Parameter DBNAME is no longer used.
HALT 20070711124232
ERROR: SAP-System not installed properly. Systems name (VMD) is different from n
ame in TADIR (VMP)
ERROR: EXIT(16) -> process ID is: 7540
tp returncode summary:
TOOLS: Highest return code of single steps was: 16
ERRORS: Highest tp internal error was: 0233
tp finished with return code: 233
meaning:
SAP-System not installed properly (HEAD SYST)
C:\Documents and Settings\vmpadm>
Once again, please do the following steps:
If you want to connect to <b>VMP:</b>
- log on as <b>vmpadm</b> on host <b>blrsap001</b>
- execute the command "tp connect <b>VMP</b> pf=
blrsap001\sapmnt\trans\bin\TP_DOMAIN_VMP.PFL"
If you want to connect to <b>VMD:</b>
- log on as <b>vmdadm</b> on host <b>blrsap002</b>
- execute the command "tp connect <b>VMD</b> pf=
blrsap001\sapmnt\trans\bin\TP_DOMAIN_VMP.PFL"
Also, is VMD a copy of VMP? If yes, did you execute the post copy steps? See e.g. OSS note 21152 for the error "ERROR: SAP-System not installed properly [...]".
- Elmar.
Message was edited by:
Elmar Billen
i am getting following errors
C:\Documents and Settings\vmpadm>tp connect VMP pf=F:\usr\sap\trans\bin\tp_domai
n_vmp.pfl
This is tp version 370.01.01 (release 700, unicode enabled)
Warning: Parameter DBHOST is no longer used.
Warning: Parameter DBNAME is no longer used.
Connection to Database of VMP was successful.
This is R3trans.exe version 6.14 (release 700 - 28.11.06 - 18:05:00).
unicode enabled version
R3trans.exe finished (0000).
tp finished with return code: 0
meaning:
Everything OK
User | Count |
---|---|
83 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.