MOS-01011 'E:/USR/SAP/PND/D02/exe/sapstartsrv.exe' returned with '-1'

Hi,
We are installing Dialog instance of CRM 5.0 on windows 2003 server. Central instance is located on AIX 5.3 server. Database we are using is DB2. During the installation first 8 steps out of 10 have been successfully. We are facing error in "Install Instance Basics" step. Service not started is the message.
Errors are as under:
ERROR 2007-10-12 13:03:57
MOS-01011  'E:/usr/sap/PND/D02/exe/sapstartsrv.exe' returned with '-1'.
ERROR 2007-10-12 13:03:57
MOS-01011  'E:/usr/sap/PND/D02/exe/sapstartsrv.exe' returned with '-1'.
ERROR 2007-10-12 13:03:57
FCO-00011  The step createService with step key |NW_DI|ind|ind|ind|ind|0|0|NW_DI_Instance|ind|ind|ind|ind|10|0|NW_Instance|ind|ind|ind|ind|1|0|createService was executed with status ERROR .
Please help.
Rgds,
- gaurav

Hi,
we were having the very same problem, and after a while we figured it out.
Check if user SAPServiceJ2E and user j2eadm are part of the group Administrators in your windows (in windows2000 look for computer manager/local users and groups)
In our case they weren't, we add them to Administrators group and bypassed this error.
I hope this helps you out.
Regards,
Laura

Similar Messages

  • Severe error(s) occurred in phase PREP_INSTALL/SHDINST_OS Last error code set: Process H:\SUM\abap\exe/sapstartsrv.exe exited with -1

    Hi Experts ,
    Currently performing EHP7 upgrade I have faced error during the configuration phase , below attached was the error screenshot .
    error logs shows the below :
    Executing module 'PREP_INSTALL'.
    Execution of PREPARE module "Installation" begins at 20140302202456
    # Starting phase execution with maxpar = 6, scheduled: 14x'-'
    CURRENTPHASE PREP_INSTALL/SHDINST_OS
    ...started at 20140302202456
    # Using phase log file 'SHDINST_OS.LOG'.
    ..finished at 20140302202457 with status ABORTED.
    # Error message set: 'Process H:\SUM\abap\exe/sapstartsrv.exe exited with -1, see 'H:\SUM\abap\log\SAPup.ECO' for details'
    .begin dialog at 20140302202459
    SHDINST_OS log :
    1 ETQ399 Possibly the password for user ISNET\SAPServiceDEC entered in phase
    1 ETQ399 INITPUT was wrong. You can reset it by calling 'SAPup set stdpar'.
    1 ETQ399 Try to execute SAPSTARTSRV.EXE manually using the following syntax:
    1 ETQ399 H:\SUM\abap\exe\sapstartsrv.exe -r
    1 ETQ399 -p H:\SUM\abap\DEC\SYS\profile\START_DVEBMGS01_SAPECCDV -s DEC -n 01
    1 ETQ399 -U ISNET\SAPServiceDEC -P <PASSWORD> -e ISNET\decadm
    1 ETQ399 and check if the service SAPDEC_01 can be stopped and restarted.
    1EETQ399 Last error code set is: Process H:\SUM\abap\exe/sapstartsrv.exe exited with -1, see 'H:\SUM\abap\log\SAPup.ECO' for details
    1EETQ204 Upgrade phase "SHDINST_OS" aborted with severe errors ("20140302202457")
    Kindly advice to fix

    Hi Mohan,
    Solution of your issue is already present in SHDINST_OS.LOG
    Possibly the password for user ISNET\SAPServiceDEC entered in phase
    1 ETQ399 INITPUT was wrong. You can reset it by calling 'SAPup set stdpar'.
    1 ETQ399 Try to execute SAPSTARTSRV.EXE manually using the following syntax:
    1 ETQ399 H:\SUM\abap\exe\sapstartsrv.exe -r
    1 ETQ399 -p H:\SUM\abap\DEC\SYS\profile\START_DVEBMGS01_SAPECCDV -s DEC -n 01
    1 ETQ399 -U ISNET\SAPServiceDEC -P <PASSWORD> -e ISNET\decadm
    1 ETQ399 and check if the service SAPDEC_01 can be stopped and restarted.
    Read the log carefully.Have you performed the above mentioned steps from SHDINST_OS.LOG file at your end.
    Also just give a full restart your server,up all the required services & confirm the execution of the phase.
    Thanks,
    Gaurav

  • WAS 6.40 ABAP stack install - error with sapstartsrv.exe - Help needed!

    Hi all,
    Can anyone assist me with a new installation issue? I am trying to perform an initial install of WAS 6.40 SP3 ABAP stack (non unicode) using the NW Master CD and CD51030103 for the SAP Kernel on a vanilla W2K AS server.
    I also have a previously installed working version of EP6.0 SP9 on WAS 6.40 (SP9) on the same physical server.
    The problem is occuring at the Create and reregister services part of the new 6.40 kernel install, I am getting the message:
    WARNING 2004-12-08 18:45:26
    Execution of the command "F:\usr\sap\IDS\SYS\exe\run/sapstartsrv.exe '-r' '-q' '-p' 'F:\usr\sap\IDS\SYS\profile\START_DVEBMGS00_devbox01' '-s' 'IDS' '-n' '00' '-U' 'devbox01\SAPServiceIDS' '-P' 'XXXXXX' '-e' 'devbox01\idsadm'" finished with return code -1. Output: Test call to Service failed.Profile parameter SAPSYSTEMNAME or SAPSYSTEM doesn't match installation parameters.Service not correctly installed.
    ERROR 2004-12-08 18:45:26
    MOS-01011 'F:\usr\sap\IDS\SYS\exe\run/sapstartsrv.exe' returned with '-1'.
    I have had no problems in the past in installing a 6.20 kernel on the same host as a portal server, but this time with 6.40 I have had no luck.
    I have tried replacing the version of sapstartsrv.exe from the
    ..usr\sap\SID\SYS\exe\run directory with a more recent version to see if the exe version was the problem but this has not resolved.
    I have also tried to run the installation again without deleting the previous files, and this has also made no difference.
    I have read through most of the forum's regarding problems with sapstartsrv.exe failing, but couldn't find anything that can help fix my problem.
    If anybody thinks they can help, it would be most appreciated
    Cheers,
    Paul

    Hi Sergio, hi Paul,
    I'm getting the same error while trying to install with RI 2.5. Interesting enough, I also have a 6.20 installed on the same machine.
    Sergio, do you mean by your last post one should change the system nr when configuring the installation?
    Paul, did you find a workaround/solution?
    Thanks in advance
    Detlev

  • WAS 6.40 ABAP stack install - error with sapstartsrv.exe

    Hi,
    Can anyone assist? I am trying to perform an initial install of WAS 6.40 SP3 ABAP stack (non unicode) using the NW Master CD and CD51030103 for the SAP Kernel on a vanilla W2K AS install, which also has a working EP6.0 SP9 runnning on it.
    At the Create and reregister services part of the kernel install, I am getting the message:
    WARNING 2004-12-08 18:45:26
    Execution of the command "F:\usr\sap\IDS\SYS\exe\run/sapstartsrv.exe '-r' '-q' '-p' 'F:\usr\sap\IDS\SYS\profile\START_DVEBMGS00_devbox01' '-s' 'IDS' '-n' '00' '-U' 'devbox01\SAPServiceIDS' '-P' 'XXXXXX' '-e' 'devbox01\idsadm'" finished with return code -1. Output: Test call to Service failed.Profile parameter SAPSYSTEMNAME or SAPSYSTEM doesn't match installation parameters.Service not correctly installed.
    ERROR 2004-12-08 18:45:26
    MOS-01011  'F:\usr\sap\IDS\SYS\exe\run/sapstartsrv.exe' returned with '-1'.
    I have had no problems in the past in installing a 6.20 kernel on the same host as a portal server, but this time no luck.
    I have also tried replacing the version of sapstartsrv.exe from the
    ..usr\sap\SID\SYS\exe\run directory with a more recent version to see if the exe version was the problem but this has not resolved.
    I have also tried to run the installation again without deleting the previous files, and this has also made no difference.
    I have read through most of the forum's regarding problems with sapstartsrv.exe failing, but nothing of use to fix my problem.
    If anybody thinks they can help, it would be most appreciated
    Cheers,
    Paul
    Message was edited by: Paul Brine

    Hi Sergio, hi Paul,
    I'm getting the same error while trying to install with RI 2.5. Interesting enough, I also have a 6.20 installed on the same machine.
    Sergio, do you mean by your last post one should change the system nr when configuring the installation?
    Paul, did you find a workaround/solution?
    Thanks in advance
    Detlev

  • Problem during installation with sapstartsrv.exe

    Hi Community,
    i have a problem with step 26 of the installation process. The service sapstartsrv.exe is not started within 40 seconds and the installation failed. I added the user j2eadm and SAPServiceJ2E with admin rights without success.
    log file says:
    WARNING    2008-09-09 15:35:19.013
               CJSlibModule::writeWarning_impl()
    Execution of the command "C:\usr\sap\CE1\SYS\exe\uc\NTI386\sapstartsrv.exe -stdin" finished with return code -1. Output:
    Service not started within 40 seconds.
    ERROR      2008-09-09 15:35:19.200
               CJSlibModule::writeError_impl()
    MOS-01011  'C:/usr/sap/CE1/SYS/exe/uc/NTI386/sapstartsrv.exe' returned with '-1'.
    ERROR      2008-09-09 15:35:19.200
               CJSlibModule::writeError_impl()
    MOS-01011  'C:/usr/sap/CE1/SYS/exe/uc/NTI386/sapstartsrv.exe' returned with '-1'.
    Any suggestions?

    Hello experts!
    I have similar issue with installing CE 7.1 EHP1 at phase 23 (Install instance basics).
    I've got error MOS-01011 in sapinst_dev.log.
    TRACE      2008-10-23 16:42:47.810 [synxcpipe.cpp:195]
               CSyStdIOPipe::waitForOverlappedIO(int timeout)
               lib=syslib module=syslib
    Syslib info about system call. OS message 109 (The pipe has been ended.
    ) after execution of system call 'GetOverlappedResult' with parameter ((pipe to child process)), line (140) in file (synxcpipe.cpp).
    WARNING    2008-10-23 16:42:47.810
               CJSlibModule::writeWarning_impl()
    Execution of the command "C:\usr\sap\CE1\SYS\exe\uc\NTI386\sapstartsrv.exe -stdin" finished with return code -1. Output:
    Test call to Service failed.
    Profile parameter SAPSYSTEMNAME or SAPSYSTEM doesn't match installation parameters.
    Service not correctly installed.
    Event Viewer (Application log) has the following record:
    Event Type:     Error
    Event Source:     Application Error
    Event Category:     (100)
    Event ID:     1000
    Date:          2008/10/23
    Time:          16:43:07
    User:          N/A
    Computer:     C239020
    Description:
    Faulting application sapstartsrv.exe, version 7110.4.15.19843, faulting module sapstartsrv.exe, version 7110.4.15.19843, fault address 0x0009e200.
    Event Viewer (System log) has the following record:
    Event Type:     Error
    Event Source:     Service Control Manager
    Event Category:     None
    Event ID:     7034
    Date:          2008/10/23
    Time:          16:43:52
    User:          N/A
    Computer:     C239020
    Description:
    The SAPCE1_01 service terminated unexpectedly.  It has done this 1 time(s).
    Any suggestions?
    Edited by: Sergey Vlasov on Oct 23, 2008 11:58 PM

  • Usr/sap/trans on rootvg (QA server)

    Dear all,
    we are using AIX os
    Client export has been done on PROD .
    now we have issue with increasing file on QA server usr/sap/trans for import process , this file system is configured on rootvg and vendor also not advisable to increase usr/sap/trans file system bcoz of rootvg. Kindly advise how can i resolve the file system issues..
    let me know any alternate option instead of increasing  rootvg file system (usr/sap/trans)
    Kindly advise
    Edited by: satheesh0812 on Feb 4, 2011 8:35 AM

    Hi,
    There are 2 was of doing it :
    1. unmount existing usr/sap/trans and mount a new one with increased space and all files copied from earlier 1.
    Then take a restart of SAP system
    2. Point DIR_TRANS to another directory which as more space and copy all files from existing /usr/sap/trans and then take a restart.
    Regards,
    Nirmal.K

  • ERROR: The new SAP tools in /usr/sap/DEV/EHPI/abap/exe cannot connect

    Hi All.
    I am attempting to upgrade my ECC 6.0 EPH3 system to EPH4.(System 'i' V6R1M1) I am hitting an error  on phase PREP_INIT/CHECKPROF_INI which states 'ERROR: The new SAP tools in /usr/sap/DEV/EHPI/abap/exe cannot connect to your database.' The log file /usr/sap/DEV/EHPI/abap/log/DBCONNCHK.LOG contains more details about the failure.
    At this point I see the processes has created to additional kernel libraries: SAPDEV70UP and SAPDEV70U2
    I am logged on as DEVOFR per the documentation. DEVOFR is the owner of all objects in /usr/sap/DEV/EPHI.
    Here is the error from DBCONNCHK.LOG :
    4 ETW000  [dev trc     ,00000]  R3INLPGM: RmtExeLib is SAPDEV70UP                                      32507  1.917692
    4 ETW000  [dbsldb4d    ,00000]  *** ERROR => CPFB755 occured: Program DBSLENCWT in library SAPDEV70UP not found.
    4 ETW000                                                                                52633  1.970325
    4 ETW000  [dev trc     ,00000]  DBSLENCWT: rc=9998, msg=                                                  33  1.970358
    4 ETW000  [dev trc     ,00000]  Wed Sep 29 09:55:53 2010                                              154488  2.124846
    4 ETW000  [dbsldb4d    ,00000]  *** ERROR => CPF0006 occured: Errors occurred in command.                 47  2.124893
    4 ETW000  [dbsldb4.    ,00000]  *** ERROR => Command: CALL PGM(SAPDEV70UP/CHGR3SYSLE) PARM('*ADD') :Failed
    When I display library SAPDEV70UP,  DBSLENCWT is there and R3OWNER is the owner.
    My DBSL is at the latest version for my environment.
    Has anyone seen this?
    Thanks in adnvance.
    Diana

    FYI,
    I got past this issue by upgrading the kernel first.
    Thanks,
    Diana

  • Unable to access application /usr/sap/ SID /DVEBMGS42/exe/jlaunch

    I have a SAP System which has AS-ABAP installed.
    I am in the process of isntalling java add in . I am getting the following error .Pls help
    Unable to access application /usr/sap/<SID>/DVEBMGS42/exe/jlaunch
    I logged in as root user and also as <SID>adm , but did not work
    Please help

    if u r on a unix platform go  to the directory /usr/sap/<SID>/DVEBMGS42/exe/ and see for the permisions using ls-l
    if there are permisiions missing try giving them
    u can use # chmod 777 *
    but this will access to all files to every user in the system.
    Edited by: jet l.....i on Feb 8, 2008 3:24 PM

  • /usr/sap/QAS/SYS/exe/run/startdb: Terminating with error code 12

    Hi Experts,
    We have made a system copy from Production to Quality and it has been done successfully. Now we are able to open the database manually.  But when we are trying to start SAP it is not connecting the database base and it is giving error which is given below :
    /home/qasadm/startdb.log
    Copyright (c) 1982, 2005, Oracle.  All Rights Reserved.
    Connected to an idle instance.
    ORACLE instance started.
    Total System Global Area 4764729344 bytes
    Fixed Size                  2035312 bytes
    Variable Size            2432700816 bytes
    Database Buffers         2315255808 bytes
    Redo Buffers               14737408 bytes
    Database mounted.
    Database opened.
    Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production
    With the Partitioning and Data Mining options
    Mon Apr 12 10:45:40 IST 2010
    Connect to the database to verify, that the database is now open
    R3trans check finished with return code: 12
    ERROR: Startup of database failed
        Notify Database Administrator.
    /usr/sap/QAS/SYS/exe/run/startdb: Terminating with error code 12
    ^C
    root@bsltest # tail -f /home/qasadm/startdb.log
    Connect to the database to check the database state:
    R3trans: connect check finished with return code: 12
    Database not available
    Mon Apr 12 10:55:53 IST 2010
    Shutdown database
    First trying to shutdown the database - May be,
    the database is in the nomount or mount state
    Mon Apr 12 10:56:22 IST 2010
    starting database
    SQL*Plus: Release 10.2.0.2.0 - Production on Mon Apr 12 10:56:22 2010
    Copyright (c) 1982, 2005, Oracle.  All Rights Reserved.
    Connected to an idle instance.
    ORACLE instance started.
    Total System Global Area 4764729344 bytes
    Fixed Size                  2035312 bytes
    Variable Size            2432700816 bytes
    Database Buffers         2315255808 bytes
    Redo Buffers               14737408 bytes
    Database mounted.
    Database opened.
    Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production
    With the Partitioning and Data Mining options
    Mon Apr 12 10:56:42 IST 2010
    Connect to the database to verify, that the database is now open
    R3trans check finished with return code: 12
    ERROR: Startup of database failed
        Notify Database Administrator.
    /usr/sap/QAS/SYS/exe/run/startdb: Terminating with error code 12
    Kindly see the logs and request you to kindly help us how it will resolve this issue.
    Regards,
    Jitendra

    We have made a system copy from Production to Quality
    After client copy sap schema had been changed thats why its not connecting.
    fyi: Client copy and system copy both are different
    schema had been changed thats why its not connecting
    This is one of the post installation step after doing a system copy(reffer the ssytem copy guide)
    Problem has resolved
    Great, suggest you to close this thread
    Regards,
    Nick Loy

  • SDA hdbsdautil does not exist in /usr/sap/ SID /home

    I am looking to test ODBC connections for SDA per this document:
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/706d9725-7087-3110-6d9e-91be8ad377d6?QuickLink=index&overridelayout=true&59064390315971
    But hdbsdautil does not exist in my home folder.
    I am able to see that program under exe:
    /sapmnt/<SID>/exe/linuxx86_64/HDB_1.00.70.00.386119_1342680
    But when I execute there I see the following error:
    error while loading shared libraries: libhdbrskernel.so: cannot open shared object file: No such file or directory
    Any thoughts?

    Hi Sebastian,
    Of course the program hdbsdautil is not in the home directory, as it resides in the exe directory of the SAP HANA software.
    server:/usr/sap/HBW/HDB10> which hdbsdautil
    /usr/sap/HBW/HDB10/exe/hdbsdautil
    server:/usr/sap/HBW/HDB10>
    It seems it was not included in the initial SP07 release of HANA 1.0 and an update to the latest version on SP07, which is Rev. 73 is anyway recommended.
    Best Regards Roland

  • Error when running:    startup.bat -fixdirectory= T:\usr\sap\ABC\upg

    I am trying to start a SAP PI 7/0 to 7.1 installation.
    I have performed all of the prerequisite steps and am now trying to run the startup.bat file from the Installation Master CD.
    I am entering:
    STARTUP.bat -fixdirectory= T:\usr\sap\ABC\upg
    and it runs:
    H:\SAPup\SAPNWAS_ABAP71_UpgMstr>STARTUP.bat -fixdirectory= T:\usr\sap\ABC\upg
    SAP directory - T:\usr\sap
    ABC directory - T:\usr\sap\ABC
    UPG directory - T:\usr\sap\ABC\upg\
    Using SAPCAR from  H:\SAPup\SAPNWAS_ABAP71_UpgMstr\DATA_UNITS\UM_SAPCAR_WINDOWS_
    X86_64
    Using SAP JVM from H:\SAPup\SAPNWAS_ABAP71_UpgMstr\DATA_UNITS\UM_SAPJVM5_WINDOWS
    X8664
    Creating upgrade directory structure...
    Found runtime H:\SAPup\SAPNWAS_ABAP71_UpgMstr\DATA_UNITS\UM_SAPCAR_WINDOWS_X86_6
    4\vcredist_x64.msi
    Installing runtime (msiexec /qn /i H:\SAPup\SAPNWAS_ABAP71_UpgMstr\DATA_UNITS\UM
    SAPCARWINDOWS_X86_64\vcredist_x64.msi)...
    Coping SAPCAR.EXE to T:\usr\sap\ABC\upg\sdt\exe\SAPCAR.EXE...
    Coping STARTUP.BAT to T:\usr\sap\ABC\upg\STARTUP.BAT...
    Coping STARTUP.JS to T:\usr\sap\ABC\upg\STARTUP.JS...
    Unpacking H:\SAPup\SAPNWAS_ABAP71_UpgMstr\DATA_UNITS\UM_SAPJVM5_WINDOWS_X86_64\S
    APJVM5.SAR ...
    Found H:\SAPup\SAPNWAS_ABAP71_UpgMstr\DATA_UNITS\UM_SLCNTRL\DSU_SLCTRL.SAR
    Unpacking H:\SAPup\SAPNWAS_ABAP71_UpgMstr\DATA_UNITS\UM_SLCNTRL\DSU_SLCTRL.SAR .
    Unpacking H:\SAPup\SAPNWAS_ABAP71_UpgMstr\DATA_UNITS\UM_SLCFG\DSU_SLCFG.SAR ...
    Unpacking H:\SAPup\SAPNWAS_ABAP71_UpgMstr\DATA_UNITS\UM_SLCFG_NW07\DSU_SLCFG_NW0
    7.SAR ...
    Starting DSUService (T:\usr\sap\ABC\upg\sdt\exe\DSUService.bat -srvarg=/DSUServi
    ce/cdpath=H:\SAPup\SAPNWAS_ABAP71_UpgMstr\ -fixdirectory= T:\usr\sap\ABC\upg )..
    And then stops. During this time, a second command window quickly appears and disappears and tries to start.
    No log files are created in:
    H:\SAPup\SAPNWAS_ABAP71_UpgMstr
    or:
    T:\usr\sap\ABC\upg
    Any ideas?
    Thanks.

    Hi Srinivas and Paul,
    How did you solve this issue? I'm facing the same issue
    Thanks andkind regards,
    Angel

  • JStartupICheckFrameworkPackage:can't find frameworkpackage E:\usr\sap\ SID

    Hi Friends, I have install NW AS JAVA only on windows 2008 sp2 server. Installation completed successfully, but now when i am trying to start sap it gives some error. I have pasted the logs below. Some valuable suggession will be appriciated.....Thanks...
    Below are the logs from dev_bootstrap
    trc file: "E:\usr\sap\JPD\JC00\work\dev_bootstrap", trc level: 1, release: "700"
    node name   : bootstrap
    pid         : 2828
    system name : JPD
    system nr.  : 00
    started at  : Tue Jun 21 15:36:37 2011
    arguments       :
           arg[00] : E:\usr\sap\JPD\JC00\exe\jlaunch.exe
           arg[01] : pf=E:\usr\sap\JPD\SYS\profile\JPD_JC00_julee
           arg[02] : -DSAPINFO=JPD_00_bootstrap
           arg[03] : pf=E:\usr\sap\JPD\SYS\profile\JPD_JC00_julee
    [Thr 2348] Tue Jun 21 15:36:38 2011
    [Thr 2348] *** WARNING => INFO: Unknown property [instance.box.number=JPDJC00julee] [jstartxx.c   841]
    [Thr 2348] *** WARNING => INFO: Unknown property [instance.en.host=julee] [jstartxx.c   841]
    [Thr 2348] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c   841]
    [Thr 2348] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c   841]
    JStartupReadInstanceProperties: read instance properties [E:\usr\sap\JPD\JC00\j2ee\cluster\instance.properties]
    -> ms host    : julee
    -> ms port    : 3901
    -> OS libs    : E:\usr\sap\JPD\JC00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : E:\usr\sap\JPD\JC00\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : julee
    -> ms port    : 3901
    -> os libs    : E:\usr\sap\JPD\JC00\j2ee\os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : E:\usr\sap\JPD\JC00\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID9765400  : E:\usr\sap\JPD\JC00\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID9765450  : E:\usr\sap\JPD\JC00\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID9765400            : E:\usr\sap\JPD\JC00\j2ee\cluster\instance.properties
    -> [01] ID9765450            : E:\usr\sap\JPD\JC00\j2ee\cluster\instance.properties
    [Thr 2348] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 2348] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 2124] JLaunchRequestFunc: Thread 2124 started as listener thread for np messages.
    [Thr 1936] WaitSyncSemThread: Thread 1936 started as semaphore monitor thread.
    [Thr 2348] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 2348] CPIC (version=700.2009.02.11)
    [Thr 2348] Tue Jun 21 15:36:39 2011
    [Thr 2348] [Node: bootstrap] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_13-x64
    [Thr 2348] JStartupICheckFrameworkPackage: can't find framework package E:\usr\sap\JPD\JC00\exe\jvmx.jar
    JStartupIReadSection: read node properties [bootstrap]
    -> node name          : bootstrap
    -> node type          : bootstrap
    -> node execute       : yes
    -> java path          : C:\j2sdk1.4.2_13-x64
    -> java parameters    : -Djco.jarm=1
    -> java vm version    : 1.4.2_13-b06
    -> java vm vendor     : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
    -> java vm type       : server
    -> java vm cpu        : amd64
    -> heap size          : 512M
    -> root path          : E:\usr\sap\JPD\JC00\j2ee\cluster
    -> class path         : .\bootstrap\launcher.jar
    -> OS libs path       : E:\usr\sap\JPD\JC00\j2ee\os_libs
    -> main class         : com.sap.engine.offline.OfflineToolStart
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : E:\usr\sap\JPD\JC00\exe\jstartup.jar;E:\usr\sap\JPD\JC00\exe\jvmx.jar
    -> parameters         : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0097654
    -> debuggable         : yes
    -> debug mode         : no
    -> debug port         : 60000
    -> shutdown timeout   : 120000
    [Thr 2188] JLaunchIStartFunc: Thread 2188 started as Java VM thread.
    [Thr 2188] [JHVM_PrepareVMOptions] use java parameters set by profile parameter
         Java Parameters: -Xss2m
    JHVM_LoadJavaVM: VM Arguments of node [bootstrap]
    -> stack   : 1048576 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Djco.jarm=1
    -> arg[  4]: -Dsys.global.dir=E:\usr\sap\JPD\SYS\global
    -> arg[  5]: -Dapplication.home=E:\usr\sap\JPD\JC00\exe
    -> arg[  6]: -Djava.class.path=E:\usr\sap\JPD\JC00\exe\jstartup.jar;E:\usr\sap\JPD\JC00\exe\jvmx.jar;.\bootstrap\launcher.jar
    -> arg[  7]: -Djava.library.path=C:\j2sdk1.4.2_13-x64\jre\bin\server;C:\j2sdk1.4.2_13-x64\jre\bin;C:\j2sdk1.4.2_13-x64\bin;E:\usr\sap\JPD\JC00\j2ee\os_libs;D:\oracle\JPD\102\bin;C:\j2sdk1.4.2_13-x64\bin;E:\usr\sap\JPD\SYS\exe\uc\NTAMD64
    -> arg[  8]: -Dmemory.manager=512M
    -> arg[  9]: -Xmx512M
    -> arg[ 10]: -DLoadBalanceRestricted=no
    -> arg[ 11]: -Djstartup.mode=BOOTSTRAP
    -> arg[ 12]: -Djstartup.ownProcessId=2828
    -> arg[ 13]: -Djstartup.ownHardwareId=R0075126991
    -> arg[ 14]: -Djstartup.whoami=bootstrap
    -> arg[ 15]: -Djstartup.debuggable=yes
    -> arg[ 16]: -Xss2m
    -> arg[ 17]: -DSAPINFO=JPD_00_bootstrap
    -> arg[ 18]: -DSAPSTARTUP=1
    -> arg[ 19]: -DSAPSYSTEM=00
    -> arg[ 20]: -DSAPSYSTEMNAME=JPD
    -> arg[ 21]: -DSAPMYNAME=julee_JPD_00
    -> arg[ 22]: -DSAPDBHOST=julee
    -> arg[ 23]: -Dj2ee.dbhost=julee
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    [Thr 2188] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [bootstrap]
    -> arg[  0]: com.sap.engine.bootstrap.Bootstrap
    -> arg[  1]: ./bootstrap
    -> arg[  2]: ID0097654
    [Thr 2188] Tue Jun 21 15:36:41 2011
    [Thr 2188] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 2120] Tue Jun 21 15:36:45 2011
    [Thr 2120] JLaunchIExitJava: exit hook is called (rc = 0)
    [Thr 2120] JLaunchCloseProgram: good bye (exitcode = 0)
    Edited by: Basis Admin on Jun 21, 2011 4:03 PM

    Pl find the logs below
    trc file: "E:\usr\sap\JPD\JC00\work\dev_server0", trc level: 1, release: "700"
    node name   : ID9765450
    pid         : 2244
    system name : JPD
    system nr.  : 00
    started at  : Tue Jun 21 15:36:56 2011
    arguments       :
           arg[00] : E:\usr\sap\JPD\JC00\exe\jlaunch.exe
           arg[01] : pf=E:\usr\sap\JPD\SYS\profile\JPD_JC00_julee
           arg[02] : -DSAPINFO=JPD_00_server
           arg[03] : pf=E:\usr\sap\JPD\SYS\profile\JPD_JC00_julee
    [Thr 2932] Tue Jun 21 15:36:56 2011
    [Thr 2932] *** WARNING => INFO: Unknown property [instance.box.number=JPDJC00julee] [jstartxx.c   841]
    [Thr 2932] *** WARNING => INFO: Unknown property [instance.en.host=julee] [jstartxx.c   841]
    [Thr 2932] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c   841]
    [Thr 2932] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c   841]
    JStartupReadInstanceProperties: read instance properties [E:\usr\sap\JPD\JC00\j2ee\cluster\instance.properties]
    -> ms host    : julee
    -> ms port    : 3901
    -> OS libs    : E:\usr\sap\JPD\JC00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : E:\usr\sap\JPD\JC00\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : julee
    -> ms port    : 3901
    -> os libs    : E:\usr\sap\JPD\JC00\j2ee\os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : E:\usr\sap\JPD\JC00\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID9765400  : E:\usr\sap\JPD\JC00\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID9765450  : E:\usr\sap\JPD\JC00\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID9765400            : E:\usr\sap\JPD\JC00\j2ee\cluster\instance.properties
    -> [01] ID9765450            : E:\usr\sap\JPD\JC00\j2ee\cluster\instance.properties
    [Thr 2932] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 2932] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 496] JLaunchRequestFunc: Thread 496 started as listener thread for np messages.
    [Thr 324] WaitSyncSemThread: Thread 324 started as semaphore monitor thread.
    [Thr 2932] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 2932] CPIC (version=700.2009.02.11)
    [Thr 2932] [Node: server0] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_13-x64
    [Thr 2932] JStartupICheckFrameworkPackage: can't find framework package E:\usr\sap\JPD\JC00\exe\jvmx.jar
    JStartupIReadSection: read node properties [ID9765450]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : C:\j2sdk1.4.2_13-x64
    -> java parameters    : -Djco.jarm=1 -XX:MaxPermSize=256M -XX:PermSize=256M -XX:NewSize=171M -XX:MaxNewSize=171M -XX:DisableExplicitGC -verbose:gc -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> java vm version    : 1.4.2_13-b06
    -> java vm vendor     : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
    -> java vm type       : server
    -> java vm cpu        : amd64
    -> heap size          : 1024M
    -> init heap size     : 1024M
    -> root path          : E:\usr\sap\JPD\JC00\j2ee\cluster\server0
    -> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : E:\usr\sap\JPD\JC00\j2ee\os_libs
    -> main class         : com.sap.engine.boot.Start
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : E:\usr\sap\JPD\JC00\exe\jstartup.jar;E:\usr\sap\JPD\JC00\exe\jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 50021
    -> shutdown timeout   : 120000
    [Thr 2932] JLaunchISetDebugMode: set debug mode [no]
    [Thr 784] JLaunchIStartFunc: Thread 784 started as Java VM thread.
    [Thr 784] [JHVM_PrepareVMOptions] use java parameters set by profile parameter
         Java Parameters: -Xss2m
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 1048576 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Djco.jarm=1
    -> arg[  4]: -XX:MaxPermSize=256M
    -> arg[  5]: -XX:PermSize=256M
    -> arg[  6]: -XX:NewSize=171M
    -> arg[  7]: -XX:MaxNewSize=171M
    -> arg[  8]: -XX:+DisableExplicitGC
    -> arg[  9]: -verbose:gc
    -> arg[ 10]: -XX:+PrintGCDetails
    -> arg[ 11]: -XX:+PrintGCTimeStamps
    -> arg[ 12]: -Djava.awt.headless=true
    -> arg[ 13]: -Dsun.io.useCanonCaches=false
    -> arg[ 14]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 15]: -XX:SurvivorRatio=2
    -> arg[ 16]: -XX:TargetSurvivorRatio=90
    -> arg[ 17]: -Djava.security.policy=./java.policy
    -> arg[ 18]: -Djava.security.egd=file:/dev/urandom
    -> arg[ 19]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[ 20]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[ 21]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[ 22]: -Dsys.global.dir=E:\usr\sap\JPD\SYS\global
    -> arg[ 23]: -Dapplication.home=E:\usr\sap\JPD\JC00\exe
    -> arg[ 24]: -Djava.class.path=E:\usr\sap\JPD\JC00\exe\jstartup.jar;E:\usr\sap\JPD\JC00\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 25]: -Djava.library.path=C:\j2sdk1.4.2_13-x64\jre\bin\server;C:\j2sdk1.4.2_13-x64\jre\bin;C:\j2sdk1.4.2_13-x64\bin;E:\usr\sap\JPD\JC00\j2ee\os_libs;D:\oracle\JPD\102\bin;C:\j2sdk1.4.2_13-x64\bin;E:\usr\sap\JPD\SYS\exe\uc\NTAMD64
    -> arg[ 26]: -Dmemory.manager=1024M
    -> arg[ 27]: -Xmx1024M
    -> arg[ 28]: -Xms1024M
    -> arg[ 29]: -DLoadBalanceRestricted=no
    -> arg[ 30]: -Djstartup.mode=JCONTROL
    -> arg[ 31]: -Djstartup.ownProcessId=2244
    -> arg[ 32]: -Djstartup.ownHardwareId=R0075126991
    -> arg[ 33]: -Djstartup.whoami=server
    -> arg[ 34]: -Djstartup.debuggable=no
    -> arg[ 35]: -Xss2m
    -> arg[ 36]: -DSAPINFO=JPD_00_server
    -> arg[ 37]: -DSAPSTARTUP=1
    -> arg[ 38]: -DSAPSYSTEM=00
    -> arg[ 39]: -DSAPSYSTEMNAME=JPD
    -> arg[ 40]: -DSAPMYNAME=julee_JPD_00
    -> arg[ 41]: -DSAPDBHOST=julee
    -> arg[ 42]: -Dj2ee.dbhost=julee
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    [Thr 784] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 2632] Tue Jun 21 15:37:13 2011
    [Thr 2632] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 2632] Tue Jun 21 15:37:14 2011
    [Thr 2632] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    Exception in thread "Thread-1" [Thr 2632] *** ERROR => JHVM_RegisterNatives: registration for method nativeTrace (ILjava/lang/String;I)V failed. [jhvmxx.c     387]
    Exception in thread "Thread-1" [Thr 2632] *** ERROR => JHVM_RegisterNatives: registration for class com.sap.bc.proj.jstartup.JStartupFramework failed. [jhvmxx.c     402]
    [Thr 2632] Tue Jun 21 15:37:16 2011
    [Thr 2632] JLaunchISetClusterId: set cluster id 9765450
    [Thr 2632] Tue Jun 21 15:37:17 2011
    [Thr 2632] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 2632] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    Tue Jun 21 15:37:29 2011
    32.693: [GC 32.693: [DefNew: 87552K->5616K(131328K), 0.0379367 secs] 87552K->5616K(1004800K), 0.0380208 secs]
    Tue Jun 21 15:37:35 2011
    39.239: [GC 39.239: [DefNew: 93168K->10731K(131328K), 0.0522776 secs] 93168K->10731K(1004800K), 0.0523620 secs]
    Tue Jun 21 15:37:42 2011
    46.142: [GC 46.142: [DefNew: 98283K->11872K(131328K), 0.0369234 secs] 98283K->11872K(1004800K), 0.0369857 secs]
    Tue Jun 21 15:37:44 2011
    48.101: [GC 48.101: [DefNew: 99424K->15175K(131328K), 0.0416394 secs] 99424K->15175K(1004800K), 0.0416992 secs]
    Tue Jun 21 15:37:47 2011
    50.864: [GC 50.864: [DefNew: 102727K->17598K(131328K), 0.0535968 secs] 102727K->17598K(1004800K), 0.0536599 secs]
    Tue Jun 21 15:37:56 2011
    59.912: [GC 59.912: [DefNew: 105150K->20359K(131328K), 0.0552269 secs] 105150K->20359K(1004800K), 0.0553026 secs]
    Tue Jun 21 15:38:05 2011
    68.822: [GC 68.822: [DefNew: 107911K->27950K(131328K), 0.0925732 secs] 107911K->27950K(1004800K), 0.0927059 secs]
    Tue Jun 21 15:38:22 2011
    86.155: [GC 86.155: [DefNew: 115502K->32318K(131328K), 0.0952289 secs] 115502K->32318K(1004800K), 0.0953143 secs]
    [Thr 3836] Tue Jun 21 15:38:24 2011
    [Thr 3836] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
    [Thr 3920] JHVM_RegisterNatives: registering methods in com.sap.security.core.server.vsi.service.jni.VirusScanInterface
    Tue Jun 21 15:38:25 2011
    89.549: [GC 89.550: [DefNew
    Tue Jun 21 15:38:26 2011
    : 119870K->37903K(131328K), 0.0946425 secs] 119870K->37903K(1004800K), 0.0947168 secs]
    [Thr 2632] Tue Jun 21 15:38:30 2011
    [Thr 2632] JLaunchISetState: change state from [Starting (2)] to [Starting applications (10)]
    93.769: [GC 93.769: [DefNew: 125455K->39983K(131328K), 0.0848278 secs] 125455K->39983K(1004800K), 0.0848963 secs]
    Tue Jun 21 15:38:42 2011
    106.101: [GC 106.101: [DefNew: 127535K->40711K(131328K), 0.1103185 secs] 127535K->44523K(1004800K), 0.1104881 secs]
    Tue Jun 21 15:38:48 2011
    111.757: [GC 111.758: [DefNew: 128263K->37882K(131328K), 0.0922447 secs] 132075K->46051K(1004800K), 0.0923087 secs]
    Tue Jun 21 15:38:53 2011
    116.821: [GC 116.821: [DefNew: 125434K->41012K(131328K), 0.0868214 secs] 133603K->49181K(1004800K), 0.0868870 secs]
    Tue Jun 21 15:38:58 2011
    121.834: [GC 121.834: [DefNew: 128564K->40328K(131328K), 0.0883693 secs] 136733K->50264K(1004800K), 0.0884344 secs]
    Tue Jun 21 15:39:02 2011
    125.894: [GC 125.894: [DefNew: 127880K->38270K(131328K), 0.1261970 secs] 137816K->50849K(1004800K), 0.1262624 secs]
    Tue Jun 21 15:39:03 2011
    Excluding compile:  com.sap.engine.services.webservices.jaxrpc.encoding.TypeMappingImpl::initializeRelations
    Tue Jun 21 15:39:06 2011
    129.644: [GC 129.644: [DefNew: 125822K->39879K(131328K), 0.0743170 secs] 138401K->52458K(1004800K), 0.0743815 secs]
    Tue Jun 21 15:39:09 2011
    133.455: [GC 133.455: [DefNew: 127431K->41403K(131328K), 0.0858201 secs] 140010K->55026K(1004800K), 0.0858849 secs]
    Tue Jun 21 15:39:11 2011
    Excluding compile:  com.sap.engine.services.webservices.jaxrpc.encoding.InstanceBuilder::readElement
    Excluding compile:  com.sap.engine.services.webservices.jaxrpc.encoding.GeneratedComplexType::_loadInto
    Tue Jun 21 15:39:12 2011
    136.149: [GC 136.149: [DefNew: 128955K->38683K(131328K), 0.0844984 secs] 142578K->56636K(1004800K), 0.0845627 secs]
    Tue Jun 21 15:39:17 2011
    140.904: [GC 140.904: [DefNew: 126235K->42612K(131328K), 0.0888091 secs] 144188K->60566K(1004800K), 0.0888767 secs]
    Tue Jun 21 15:39:20 2011
    144.177: [GC 144.177: [DefNew: 130164K->39791K(131328K), 0.0883459 secs] 148118K->62169K(1004800K), 0.0884110 secs]
    Tue Jun 21 15:39:23 2011
    Excluding compile:  com.sap.engine.services.webservices.jaxrpc.encoding.InstanceBuilder::readSequence
    147.268: [GC 147.268: [DefNew: 127343K->33797K(131328K), 0.0799426 secs] 149721K->62721K(1004800K), 0.0800037 secs]

  • /usr/sap/trans/actlog - Increase log detail

    Hi everyone,
    I'm after away of logging when objects are added to deleted from a modifiable change request (eg I want to see the object details, who, and date/time.  I'm aware that when you create a new transport request/task that a log is created in /usr/sap/trans/actlog, however I was wondering if there was away to increase the detail level of what is written to the log file, or if someone knows of another way of tracking this information.
    Cheers
    Shaun

    Operating system level files in the transport process:
    The SAP C program TP, requires a special file structure for the transport process. The file system is operating system dependent. TP uses a transport directory or file system, which is called /usr/sap/trans.
    The /usr/sap/trans file system is generally NFS mounted form the development system to other systems unless a system is defined as a single system in the CTS pipeline. All the sub directories should have <SID>adm as the owner and sapsys as the group; and proper read, write and execute access should be given to owner and the group. The TP imports are always performed by <SID>adm.
    The following are the subdirectories in /usr/sap/trans:
    /data
    /cofiles
    /bin
    /log
    /actlog
    /buffer
    /sapnames
    /tmp
    /usr/sap/trans/data: holds the data of transport objects after they are released . This subdirectory contains files named R9<5 digits >. containing the exported objects. The example of a data file is R904073.DEV. The extension DEV means the data file was released from the DEV or development system.
    /usr/sap/trans/cofiles: The cofiles directory holds the command files for all change requests. This subdirectory contains command files named K9<5 digits>.. They contain, for example, import steps to be performed. files are like a command or control files used to import the data files. The common directory for CTS system is /usr/sap/trans. After a change request is released from the source system , the data is exported immediately to the file system of the operating system. The SAP transport utility TP uses the cofile to transport a data file. The example of a file in cofiles directory is K904073.DEV.
    /usr/sap/trans/bin: holds the most important file TPPARAM in the CTS system. TPPARAM file has all the information about the CTS systems in the CTS pipeline. TPPARAM file is the parameter file for the transport program TP and it is the common file for all the systems in the CTS pipeline. As you know already that /usr/sap/trans should be NFS mounted to all the systems in a CTS pipeline, TP program has access to the TPPARAM file from all the systems. The following is an example of typical TPPARAM file for five SAP systems in the CTS pipeline:
    #@(#) TPPARAM.sap 20.6 SAP 95/03/28
    # Template of TPPARAM for UNIX #
    # First we specify global values for some parameters, #
    # later the system specific incarnation of special parameters #
    # global Parameters #
    transdir = /usr/sap/trans/
    dbname = $(system)
    alllog = ALOG$(syear)$(yweek)
    syslog = SLOG$(syear)$(yweek).$(system)
    # System spezific Parameters #
    # Beispiel T11 #
    DEV/dbname = DEV
    DEV/dbhost = sap9f
    DEV/r3transpath = /usr/sap/DEV/SYS/exe/run/R3trans
    QAS/dbname = QAS
    QAS/dbhost = sap8f
    QAS/r3transpath = /usr/sap/QAS/SYS/exe/run/R3trans
    TRN/dbname = TRN
    TRN/dbhost = sap17
    TRN/r3transpath = /usr/sap/TRN/SYS/exe/run/R3trans
    PRE/dbname = PRE
    PRE/dbhost = sap19f
    PRE/r3transpath = /usr/sap/PRE/SYS/exe/run/R3trans
    PRD/dbname = PRD
    PRD/dbhost = sap18f
    PRD/r3transpath = /usr/sap/PRD/SYS/exe/run/R3trans
    /usr/sap/trans/log: holds the entire log files, trace files and statistics for the CTS system. This subdirectory contains all log files, such as ULOGs, ALOGs, SLOGs, log files named 9<5 digits>. for each executed step, and log files named . for steps that are collectively executed, for example, step N (structure conversion) and step P (move nametabs). When the user goes to SE09 (workbench organizer) or SE10 (customizing organizer) transaction and opens the log for a transport, the log file for that transport will be read from /usr/sap/trans/log directory. Each change request should have a log file. Examples of log files are DEVG904073.QAS, DEVI904073.QAS and DEVV904073.QAS. The name of a log file consists of the names of the change request, the executed step, and the system in which the step was executed:
    <source system><action><6 digits>.<target system>
    Now we can analyze the above example DEVG904073. QAS. The <source system> = DEV, <action> = G or report and screen generation, <6 digits> = 904073 (these six digits numbers are exactly the same number as the six digits of the transport) and the <target system> = QAS
    Possible values for <action> are:
    A: Dictionary activation
    D: Import of application-defined objects
    E: R3trans export
    G: Report and screen generation
    H: R3trans dictionary import
    I: R3trans main import
    L: R3trans import of the command files
    M: Activation of the enqueue modules
    P: Test import
    R: Execution of reports after put (XPRA)
    T: R3trans import of table entries
    V: Set version flag
    X: Export of application-defined objects.
    /usr/sap/trans/actlog: This subdirectory contains files named Z<6 digits> recording each action on a request or task, for example, creation, release, or change of ownership. The example of an action file is DEVZ902690.DEV. The following are the contents of the file:
    1 ETK220 “==================================================” “=================
    =============================
    1 ETK191 “04/30/1998″ Action log for request/task: “DEVK902690″
    1 ETK220 “==================================================” “=================
    =============================
    1 ETK185 “04/30/1998 18:02:32″ “MOHASX01″ has reincluded the request/task
    4 EPU120 Time… “18:02:32″ Run time… “00:00:00″
    1 ETK193 “04/30/1998 18:02:33″ “MOHASX01″ owner, linked by “MOHASX01″ to “DEVK902691″
    4 EPU120 Time… “18:02:33″ Run time… “00:00:00″
    1 ETK190 “05/04/1998 11:02:40″ “MOHASX01″ has locked and released the request/task
    1 ETK194 “05/04/1998 11:02:40″ **************** End of log *******************
    4 EPU120 Time… “11:02:40″ Run time… “00:00:09″
    ~
    ~”DEVZ902690.DEV” 10 lines, 783 characters
    /usr/sap/trans/buffer: This subdirectory contains an import buffer for each SAP System named after the SID. When a change request is released, the import buffer of the target systems is updated. Contains control information on which requests are to be imported into which systems and in what order the imports must occur. The /usr/sap/trans/buffer will have a directory for each system in the CTS pipeline. For example the buffer file for DEV system is /usr/sap/trans/buffer/DEV.
    /usr/sap/trans/sapnames: holds information pertaining to transport requests for each system user. This subdirectory contains files named after the user's logon name. A file is created for each SAP System user, who performs transport actions, and updated when the user releases a request. There are files for each user who released change requests from the system.
    /usr/sap/trans/tmp: holds information about temporary data and log files. While the transport is occurring the Basis administrator can find a file that is related to the transport in the tmp directory; that file shows the exact status if the transport (What objects are being imported at that time).
    Important SAP delivery class and table types and tables in the CTS process:
    Delivery class
    The delivery class defines who (i.e. the SAP system itself or the customer) is responsible for maintaining the table contents. In addition the delivery class controls how the table behaves in a client copy and an upgrade. For example when you select a SAP defined profiles to perform a client copy, certain tables are selected according to their delivery class. DD02L table can show what delevery class a table belongs to.
    The following delivery classes exist:
    A: Application table.
    C: Customizing table, maintenance by customer only.
    L: Table for storing temporary data.
    G: Customizing table, entries protected against overwriting.
    E: Control table.
    S: System table, maintenance only by SAP.
    W: System table, contents can be transported via own TR objects.
    Table type
    The table type defines whether a physical table exists for the logical table description defined in the ABAP/4 Dictionary and how the table is stored on the database.
    The following are different table types in SAP:
    Transparent Tables
    There is a physical table on the database for each transparent table. The names of the physical table and the logical table definition in the ABAP/4 Dictionary are same. For every transparent table in SAP, there is a table in database. The business and application data are stored in transparent tables.
    Structure
    No data records exist on the database for a structure. Structures are used for the interface definition between programs or between screens and programs.
    Append Structure
    An Append structure defines a subset of fields which belong to another table or structure but which are treated as a separate object in the correction management. Append structures are used to support modifications.
    The following table types are used for internal purposes, for example to store control data or for continuous texts:
    Pooled table
    Pooled tables can be used to store control data (e.g. screen sequences, program parameters or temporary data). Several pooled tables can be combined to form a table pool. The table pool corresponds to a physical table on the database in which all the records of the allocated-pooled tables are stored.
    Cluster table
    Cluster tables contain continuous text, for example documentation. Several cluster tables can be combined to form a table cluster. Several logical lines of different tables are combined to form a physical record in this table type. This permits object-by-object storage or object-by-object access. In order to combine tables in clusters, at least part of the keys must agree. Several cluster tables are stored in one corresponding table on the database.
    Tables in CTS process:
    TRBAT and TRJOB:
    TRJOB and TRBAT are the major tables in the CTS process. After TP program has sent the event to the r3 system, RDDIMPDP checks table TRBAT in the target system to find out if there is an action to be performed. Mass activation, distribution, or table conversions are the examples of actions. If there is action to be performed, RDDIMPDP starts the appropriate program in the background task. RDDIMPDP then reschedules itself.
    By checking table TRJOB, RDDIMPDP automatically recognizes if a previous step was aborted, and restarts this step. For each transport request , TP program inserts an entry into table TRBAT. If the return code 9999 in this table then the step is waiting to be performed. Return code 8888 indicates that the step is active and currently being processed. A return code of 12 or less indicates that the step is finished. In addition, TP inserts a header entry to let the RDDIMPDP program know to start processing. The column return code will therefore contain a B for begin. When RDDIMPDP is started, it sets the header entry to R(un), and starts the required program. When all the necessary actions are performed for all the transport requests, the column return code contains all the return codes received, and the column TIMESTAMP contains the finishing time. The header entry is set to F(inished). TP monitors the entries in TRBAT and TRJOB tables. When the header entry in TRBAT is set to finished. The entry in TRJOB is deleted.
    Transport Tables SE06
    TDEVC – Development classes
    TASYS – Details of the delivery. Systems in the group that should automatically receive requests, have to be specified in table TASYS.
    TSYST – The transport layers will be assigned to the integration systems. ( Define all systems)
    TWSYS – Consolidation routes ( define consolidation path)
    DEVL – Transport layers are defined here
    In “Configuring the CTS system” section, We will learn more about the transport tables in SE06 transaction
    Programs in the CTS process:
    In the CTS table section we learned about the RDDIMPDP program. RDDIMPDP program needs to be scheduled in all the clients in an instance. It is recommended to schedule the RDDIMPDP as event driven.
    RDDPUTPP and RDDNEWPP programs can be used to schedule RDDIMPDP program in the background.
    The ABAP/4 programs that RDDIMPDP starts are determined by the transport step to be executed that is entered in the function field of table TRBAT.
    Function Job Name Description of transport Steps
    J RDDMASGL Activation of ABAP/4 dictionary objects
    M RDDMASGL Activation of match codes and lock objects
    S RDDDISOL Analysis of database objects to be converted
    N RDDGENOL Conversion of database objects
    Y RDDGENOL Conversion of matchcode tables
    X RDDDICOL Export of AD0 objects
    D RDDDIC1L Import of AD0 objects
    E RDDVERSE Version management update during export
    V RDDVERSL Version management update during import
    R RDDEXECL Execution of programs for post – import processing
    G RDDDIC3L Generation of ABAP/4 programs and screens
    Version Management:
    One of the important features of Workbench Organizer is Version Management. This feature works for all the development objects. Using the version management feature the users can compare and retrieve previous versions of objects.
    Version management provides for comparisons, restore of previous versions, documentation of changes and assistance in the adjustment of data after upgrading to a new release. With the release of a change request, version maintenance is automatically recorded for each object. If an object in the system has been changed N times, it will have N delta versions and one active version. To display version management, for ABAPs use transaction SE38 and for tables, domains and data elements use SE11. The path to follow is Utilities -> Display version. Using version management the users can view existing version for previously created ABAP code, make changes to the code, compare code versions and restore original version of the code. Now the users will be restore previous versions without cut and paste steps of the past.
    TP and R3trans program:
    The basis administrator uses TP program to transport SAP objects from one system to another. TP is a C program delivered by SAP that runs independently of the R/3 system. TP program uses the appropriate files located in a common transport directory /usr/sap/trans. TP starts C programs, ABAP/4 programs and special operating system commands to its job. R3trans is one of the most important utility program called by TP. Before using the TP program, the basis administrator needs to make sure that the CTS system is setup properly and the right version of TP is running in the system. The TP program is located in the run time directory /usr/sap/<SID>/SYS/exe/run directory. It is automatically copied in the install process. A global parameter file TPPARAM that contains the databases of the different target systems and other information for the transport process controls TP. The global parameter file determines which R3trans is used for each system. If the parameter r3transpath is not defined properly then no export and import can be done. The basis administrator should make sure that the default value “r3transpath” is properly defined. Later in this chapter we will learn more about TP and R3trans; also we are going to see how they are used.
    Configuring the TPPARAM file:
    Each time TP is started, it must know the location of the global parameter file. As we have seen before TPPARAM file should be in directory /usr/sap/trans/bin. The parameters in TPPARAM can either global (valid for each and every system in the cts pipeline) or local to one system. Th parameters are either operating system dependant (these parameters preceded by a keyword corresponding to the specific operating system) or database dependant (contain a keyword corresponding to a specific database system).
    The global parameter file provides variables that can be used for defining parameters. The variables can be defined in format: $(xyz). The brackets can be substituted with the “\”-character if required.
    The following pre-defined variables are available for the global parameter file:
    $(cpu1): The CPU name can be sun or as4 for example. In heterogeneous networks this variable is very important.
    $(cpu2): Acronym for the name of the operating system. The example for this variable can be
    hp-ux, or sunos . This is an operating system specific variable.
    $(dname): Used for the day of the week (SUN,MON,….).
    $(mday): Used for the day of the current month (01-31).
    $(mname): Used for the name of the month (JAN…DEC).
    $(mon): Used for the Month (01-12).
    $(system): R/3 System name.
    $(wday): Day of the week (00-06, Sunday=00, Monday=01, Tuesday=02 and so on).
    $(yday): Day of the current year (001-366). Using the number any day of the year can be chosen.
    $(year): Year (Example:1998 or 1999).
    $(syear): Short form of the year (two positions).
    $(yweek): Calendar week (00-53). The first week begins with the first Sunday of the year.
    For the database connection:
    The transport environment also needs parameters to connect to the R/3 System database. As we know already the every instance in the R/3 CTS pipeline has its own database, therefore specific parameters should be defined for each database system. From dbtype parameter of RSPARAM file, TP program identifies the database system.
    The two parameters “dbname” and “dbhost” are required for ORACLE databases.
    DBHOST: is the name of the computer on which the database processes execute. TCP/IP name of the host if NT is being used.
    DBNAME: is the name of the database instance.
    As of Release 3.0E, two new parameters have been introduced.
    DBLOGICALNAME: The default value is $(system). The logical name that was used to install the database.
    DBCONFPATH: The default value is $(transdir).
    The parameters “dbname” and “dbhost” are also used for INFORMIX databases in an installation:
    DBHOST: Same as Oracle.
    DBNAME: Name of the database instance, uppercase and lowercase are distinguished here.
    INFORMIXDIR : “/informix/<SAPSID>” is the default value. Defines the directory namewhere the database software can be found.
    INFORMIXSQLHOSTS: “$(informixdir)/etc/sqlhosts[.tli|.soc]“is default value under Unix. The name of the SQLhosts file with its complete path is defined with this parameter.
    INFORMIX_SERVER: “$(dbhost)$(dbname)shm” is the default value. The name of the database server may be specified for a local connect.
    INFORMIX_SERVERALIAS: “$(dbhost)$(dbname)tcp”is the default vlue. The name of the database server can be specified for a remote connect.
    For Microsoft SQL Server database the two parameters “dbname” and “dbhost” are also required. DBHOST: The TCP/IP name of the host on which the database is running.
    DBNAME: The database instance name.
    For DB2 in AS/400 only “dbhost” is required.
    DBHOST: System name of the host on which the database is running.
    If the”OptiConnect” is used, the following line should be specified:
    OPTICONNECT 1
    For DB2/ AIX
    The two parameters “dbname” and “dbhost” are required
    DBHOST: The host on which the database processes are running. It is the TCP/IP name of the host for Windows NT (As we have seen in the earlier examples).
    DBNAME: Database instance name.
    The DB2 for AIX Client Application Enabler Software must also be installed on the host on which tp is running.
    ALLLOG: “ALOG” $(syear) $(yweek)”is the default value. This variable can be used in TPPARAM file to specify the name of a file in which tp stores information about every transport step carried out for a change request anywhere in the transport process. The file always resides in the log directory.
    SYSLOG: “SLOG $(syear) $(yweek).$(system)” is the default value. This variable can be used to name a file in which tp stores information about the progress of import actions in a certain R/3 System. The file does not store information for any particular change request. The file always resides in the log directory.
    tp_VERSION: Zero is the default value. If this parameter is set to not equal to zero, a lower version of tp may not work with this TPPARAM file. If the default value (zero) is set, the parameter has no affect.
    STOPONERROR: (Numeric value) The default value is 9. When STOPONERROR is set to zero, tp is never stopped in the middle of an “import” or “put” call. When STOPONERROR is set to a value greater than zero, tp stops as soon as a change request generates a return code that is equal to or greater than this value (The numeric value of the STOPONERROR parameter is stored in the variable BADRC). Change requests, which still have to be processed for the current step, are first completed. A “SYNCMARK” in the buffer of the R/3 System involved, sets a limit here. tp divides the value of this parameter between two internal variables. STOPONERROR itself is treated as a boolean variable that determines whether tp should be stopped, if the return code is too high.
    REPEATONERROR (Numeric value too): The default value is 9. The REPEATONERROR parameter is similar to STOPONERROR. The difference is, REPEATONERROR specifies the return code up to which a change request is considered to be successfully processed. Return codes less than REPEATONERROR are accepted as “in Order”. Change requests that were not processed successfully stay in the buffer.
    NEW_SAPNAMES: Default value is “FALSE”. A file is created for each user of the R/3 System group in the “sapnames” subdirectory of the transport directory. Except some of the operating system,the name of the user is the name of the file. It is very important to remember hat the special characters or length of the file name could cause problems. If all the R/3 Systems in the transport group have at least Release level 3.0.; TP program is efficient to handle this problem. The user names are modified to create file names that are valid in all operating systems and the real user names are stored in a corresponding file.
    Though we have seen so many parameters, for the minimum configuration the following two parameters are very important.
    TRANSDIR: specifies the name of the common transport directory. The following is a typical example from TPPARAM of Unix as we have seen before.
    transdir = /usr/sap/trans/
    DBHOST: contains the name of the database host. In Windows NT environment, this is the TCP/IP host name. The following is an example in Unix:
    DEV/dbname = DEV
    DEV/dbhost = sap9f
    DEV/r3transpath = /usr/sap/DEV/SYS/exe/run/R3trans
    For TP, to control ‘Start and Stop’ command files and database in R/3 the following important parameters are specified in TPPARAM:
    Parameters for the tp Function “PUT”: LOCK_EU (boolean) default value is “TRUE”. Though from version 3.1 onward the tp put command is used seldom in cts process still it is important to know how this parameter works. When “tp put” is used, it changes the system change option . If the parameter is set to “FALSE” nothing gets changed. If the parameter is set to “TRUE”, the system change option is set to “Objects cannot be changed” at the beginning of the call, and gets changed back to its previous value at the end of the call. The “tp put” command will give the exact status of the locking mechanism.
    LOCKUSER (used as boolean value): Default value is “TRUE”. This parameter is about the user login while tp put call is executed. If this parameter is set to “FALSE”, no locking mechanism for the users takes affect. If this parameter is defined as “TRUE” then a character is set in the database level; so only DDIC and SAP* can log on to the system. Users that have already logged on are not affected (this is a reason for activating the parameters STARTSAP and STOPSAP). The charactertor is removed at the end of the call, and all the users can log on to the SAP R/3 System again.
    STARTSAP: Default value is ” “.or “PROMPT” for Windows NT . This parameter is used by TP to start an R/3 System. It is not necessary for the clients to make tp start and stop R/3 system..
    STOPSAP: Default value is ” “or “PROMPT” for Windows NT. TP uses this parameter to stop an R/3 System.
    STARTDB: Default value is ” “. TP uses the value of this parameter to start the database of an R/3 System.
    The parameter is not active under Windows NT.
    STOPDB: Default value is ” “. TP uses the value of this parameter to stop the database of an R/3 System.
    This parameter is not active under Windows NT.
    The above parameters in UNIX can be used as following:
    STARTSAP = startsap R3
    STOPSAP = stopsap R3
    STARTDB = startsap db
    STOPDB = stopsap db
    In Windows NT:
    STARTSAP = \\$(SAPGLOBALHOST)\sapmnt\$(system)\sys\exe\run\startsap.exe
    R3 <SID> <HOST NAME> <START PROFILE>
    STOPSAP = \\$(SAPGLOBALHOST)\sapmnt\$(system)\sys\exe\run\stopsap.exe
    R3 <SID> <HOST NAME> <INSTANCE> <PROFILE PATH + Instance profile>
    The parameters STARTDB and STOPDB are not active under Windows NT.
    Parameters for the tp function “CLEAROLD”
    DATALIFETIME (Numeric): Default value is “200″. When the data file has reached a minimum age, it is moved to the subdirectory old data with tp check. tp clearold all. The life span of the data files in the data sub directory can be set in days with this all, parameter.
    OLDDATALIFETIME (Numeric): Default value is “365″. When a file located in the olddata subdirectory is no longer needed for further actions of the transport system and has reached a minimum age, it is removed with tp check.all, tp clearold all. The minimum age in days can be set with this parameter.
    COFILELIFETIME (Numeric): Default value is “365″. This parameter is used just like DATALIFETIME parameter.
    LOGLIFETIME (Numeric): Default value is “200″. This parameter applies to the life span of the log files. When the log files in log subdirectory is no longer needed for the transport system and has reached a minimum age, it is deleted with the calls tp check.all, tp clearold all. The minimum age in days can be defined with this parameter.
    The Three Key Utilities of the CTS system (TP, R3trans and R3chop):
    TP: Earlier in this chapter we have seen the objectives of TP. The TP transport control program is a utility program that helps the user to transport objects from one system to another. TP program is the front-end for the utility R3trans. TP stands for “Transports and Puts”. To make the TP work successfully the CTS system needs to be correctly configured. The following steps are very important for TP to run properly.
    The transport directory /usr/sap/trans must be installed and NFS mounted to all the systems in the CTS pipe line.
    RDDIMPDP program must be running (event driven is recommended) in each client. RDDIMPDP can be scheduled in the background by executing RDDNEWPP or RDDPUTPP. Use the tp checkimpdp <sap sid> command in /usr/sap/trans/bin directory as <sid>adm user to check RDDIMPDP program.
    Use the tp connect <sap sid> command in /usr/sap/trans/bin directory to see whether the tp program is connecting to the database successfully or not. To run TP command the user has to logon as <sid>adm in source or target system.
    The R/3 Systems in the CTS pipeline must have different names.
    The Global CTS Parameter File TPPARAM must be correctly configured.
    The source system (for the export) and target system ( for the import) must have at least two background work processes. TP always schedules the C class job, so if all the background jobs are defined as A class job then there will be problems in transport steps.
    Important Tips :.It is always better to have the up to date TP version installed in your system. A user can ftp a current version of TP from SAPSERV4 of SAP. Though R3trans and other utility programs can be used to do the transport, it is recommended to use TP whenever possible for the following reasons..
    The exports and imports are done separately using TP program. For example: when a transport is released from the system, the objects are exported from the source database to the operating system and then the import phase starts to transport those objects to the target system.
    TP takes care of the order of the objects. The order, that was followed to export the objects; the same order will be followed to import them to the target database.
    The TP command processes all change requests or transports in the SAP system buffer that have not yet been imported successfully. All the import steps are executed automatically after TP calls R3trans program to execute the following necessary steps:
    Dictionary Import: ABAP/4 dictionary objects will be imported in this step.
    Dictionary Activation: Name tabs or runtime descriptions will be written inactively. The R/3 system keeps running until the activation phase is complete. The enqueue modules are the exceptions in the running phase. After the activation of new dictionary structure the new actions are decided to get the runtime objects to the target system.
    Structure conversion: If necessary the table structure is changed in this phase.
    Move Nametabs: The new ABAP/4 Dictionary runtime objects which were inactive up to now are moved into the active runtime environment in this process. The database structures are adjusted accordingly. From the first step to the Main import step inconsistencies can occur to the R/3 system. After the main import phase all the inconsistency ca be solved.
    Main import with R3trans: All the data are imported completely and the system comes to a consistent state.
    Activation of enqueue-objects: The enqueue-objects cannot be activated in the same way as the objects of the ABAP/4 Dictionary, so they have to be activated after the main import in this step. They are then used directly in the running system.
    Structure Conversion of match codes, Import application defined objects, versioning and execution of user defined activities are some of the steps after activation of enqueue-objects. The next step is generation of ABAP/4 programs and screens, where all the programs and screens associated with the change request are generated. When all the import steps are completed successfully, the transport request is removed from the import buffer.
    It is recommended by SAP to schedule regular periods for imports into the target system (e.g. daily, weekly or monthly). Shorter periods between imports are not advisable. The transport to production should not be done in the off hours when the users are not working
    TP can be started with different parameters. The “tp help” command can help user to generate a short description about the use of the command.
    The following are the some important commands of TP:
    For export:
    tp export <change request>: The complete objects in the request from the source system will be transported. This command also used by SAP System when it releases a request.
    tp r3e <change request>: R3trans export of one transport request.
    tp sde <change request>: Application defined objects in one transport request can be exported.
    tp tst <change request> <SAP system >: The test import for transport request can be done using this command.
    tp createinfo <change request>: This command creates a information file that is automatically done during the export.
    tp verse <request>: This command creates version creates versions of the objects in the specified request.
    To Check the transport buffer, global parameter file and change requests:
    tp showbuffer <sid>: Shows all the change requests ready to be imported to the target system.
    tp count <sid>: Using this command users can find out the number of requests in the buffer waiting for import.
    tp go <sid>: This command shows the environment variables needed for the connection to the database of the <sid> or target system.
    tp showparams <sid>: All the values of modifiable tp parameters in the global parameter file. The default value is shown for parameters that have not been set explicitly.
    To import the change requests or transports:
    tp addtobuffer <request>.<sid>: If a change request is not in the buffer then this command is used to add it to the buffer, before the import step starts.
    tp import all <sid>: This command imports all the change requests from the buffer to the target system.
    tp put <sid>: The objective of this command is same as “tp import all <sid>”, but this command locks the system. This command also starts and stops the SAP system, if the parameters startsap and stopsap parameters are not set to ” “.
    tp import <change request> <sid>: To import a single request from the source system to target system.
    tp r3h <change request>| all <sid>: Using this command user can import the dictionary structures of one transport or all the transport from the buffer.
    tp act <change request>|all <sid>: This command activates all the dictionary objects in the change request.
    tp r3i <change request> | all <sid>: This command imports everything but dictionary structures of one.
    tp sdi <change request>|all <sid>: Import application-defined objects.
    tp gen <change request>|all <sid>: Screen and reports are generated using this command.
    tp mvntabs <sid>: All inactive nametabs will be activated with this command.
    tp mea <change request>|all <sid>: This command will activate the enqueue modules in the change request.
    When you call this command, note the resulting changes to the import sequence.
    Additional tp utility options:
    tp check <sid>|all (data|cofiles|log|sapnames|verbose): User uses this command to find all the files in the transport directory that are not waiting for imports and they have exceeded the minimum time specified using the COFILELIFETIME, LOGFILELIFETIME, OLDDATALIFETIME and DATALIFETIME parameters of TPPARAM file.
    tp delfrombuffer <request>.<sid>: This command removes a single change request from the buffer. In case of TMS, the request will be deleted from the import queue.
    tp setstopmark <sid>: A flag is set to the list of requests ready for import into the target system. When the user uses the command tp import all <sapsid> and tp put <sapsid>, the requests in front of this mark are only processed. After all the requests in front of the mark have been imported successfully, the mark is deleted.
    tp delstopmark <sid>: This command deletes the stop mark from the buffer if it exists.
    tp cleanbuffer <sapsid>: Removes all the change requests from the buffer that are ready for the import into the target system.
    tp locksys <sid>: This command locks the system for all the users except SAP* and DDIC. The users that have already logged on are not affected by the call.
    tp unlocksys <sid>: This command unlocks the system for all the users.
    tp lock_eu <sid>: This command sets the system change option to “system can not be changed” tmporarily.
    tp unlock_eu <sid>: This command unlocks the system for all the changes.
    tp backupall <sid>: This command starts a complete backup using R3trans command. It uses /usr/sap/trans/backup directory for the backup.
    tp backup delta <sid>: Uses R3trans for a delta backup into /usr/sap/trans/backup directory.
    tp sapstart <sid>: To start the R/3 system.
    tp stopsap <sid>: To stop the R/3 system.
    tp dbstart <sid>: To start the database.
    tp dbstop <sid>: To stop the database.
    Unconditional modes for TP: Unconditional modes are used with the TP program and these modes are intended for the special actions needed in the transport steps. Using unconditional mode user can manipulate the rules defined by the workbench organizer. The unconditional mode should be used when needed, otherwise it might create problems for the R/3 system database. Unconditional mode is used after the letter “U” in the TP command. Unconditional mode can be a digit between 0 to 9 and each has a meaning to it. The following is a example of a import having unconditional mode.
    tp import devk903456 qas client100 U12468
    0: Called a overtaker; change request can be imported from buffer without deleting it and then uncoditional mode 1 is used to allow another import in the correct location.
    1: If U1 is used with the export then it ignores the correct status of the command file; and if it is used with import then it lets the user import the same change request again.
    2: When used with tp export, it dictates the program to not to expand the selection with TRDIR brackets. If used in tp import phase, it overwrites the originals.
    3: When used with tp import, it overwrites the system-dependant objects.
    5: During the import to the consolidation system it permits the source systems other than the integration system.
    6: When used in import phase, it helps to overwrite objects in unconfirmed repairs.
    8: During import phase it ignores the limitations caused by the table classification.
    9: During import it ignores that the system is locked for this kind of transport.
    R3trans: TP uses R3trans program to transport data from one system to another in the CTS pipeline. efficient basis administrator can use R3trans directly to export and import data from and into any SAP systems. Using this utility transport between different database and operating system can e done without any problems. Different versions of R3trans are fully compatible with each other and can be used for export and import. The basis administrator has to be careful using R3trans for different release levels of R/3 software; logical inconsistency might occur if the up to date R3trans is not used for the current version of R/3 system.
    The syntax for using the control file is following:
    R3trans [<options>] <control file> (several options used at the same time; at least one option must be there)
    For example: R3trans –u 1 –w test.log test
    In the above example a unconditional mode is used, a log file “test.log” file is used to get the log result and a control file “test”, where the instructions are given for the R3trans to follow. The user needs to logon as <sid>adm to execute R3trans.
    The following options are available for the R3trans program:
    R3trans -d : This command is used to check the database connection .
    R3trans -u <int>: Unconditional mode can be used as we have seen in the above example.
    R3trans -v : This is used for verbose mode. It writes additional details to the log file
    R3trans -i <file>: This command directly imports data from data file without a control file.
    R3trans -l <file>: This provides output of a table of contents to the log file.
    R3trans -n : This option provides a brief information about new features of R3trans.
    R3trans –t: This option is used for the test mode. All modifications in the database are rolled back.
    R3trans -c <f1> [<f2>]: This command is used for conversion. The <f1> file will be copied to <f2> file after executing a character set conversion to the local character set.
    Important tips: Do not confuse the backup taken using R3trans with database backup. The backups taken using R3trans are logical backups of objects. In case something happens to the SAP system these backups can not be used for recovery. R3trans backups can be only used to restore a copy of a particular object that has been damaged or lost by the user.
    R3trans -w <file>: As we have seen in the above example this option can be used to write to a log file. If no file is mentioned then trans.log is default directory for the log.
    R3trans also can be used for the database backup.
    R3trans –ba: This command is used for a complete backup. we will see in the next paragraph how to use
    the control file for the backup.
    R3trans –bd: This command is used for a delta backup if the user does not want a complete backup.
    R3trans –bi: This option

  • Difference between /usr/sap/ and /usr/sapmnt/  Directories

    Hi all,
       I want to know the difference between /usr/sap/ and /usr/sapmnt/ directiories. We are having exe,profile and global in both directories.
    Thx
    Ral

    /usr/sap is symlink to the /usr/sapmnt. You can study this link ( point 2 in procedure) to understand better
    http://help.sap.com/saphelp_nw04/helpdata/en/4f/37782a21fc11d288cd0000e83539c3/content.htm
    Reward points if useful

  • Executable does not exist: F:\usr\sap\PD1\JC01\j2ee\os_libs\adssap\XMLFormS

    Hi All,
    I am currently trying to setup a standard PCR and have gone through the steps for configuration, and I am going to run my Personnel Change Request, but it throws and exeptions and bombs. One of the key lines I could piece together from the Stack Trace is the follow:
    <b>Caused by: java.io.IOException: Executable does not exist: F:\usr\sap\PD1\JC01\j2ee\os_libs\adssap\XMLFormService\bin\XMLForm.exe
         at com.adobe.service.ProcessResource.startProcess(ProcessResource.java:252)
         ... 42 more
         at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:374)
         ... 51 more</b>
    This would lead me to believe that ADS or XMLForms was not installed, or installed correctly.
    Could anyone provide any clarity to this situation?

    Hello,
    fist make sure you use a supported plattform for ADS:
    http://service.sap.com/PAM
    If it it supported try the following:
    If these files are not exist, it might be caused by deployment or
    synchronizing binaries (bootstrap). In order to force synchronize
    os native module, please try follows:
        Stop J2EE engine
        rename version.bin to version.bin.old
         this file can be found under /usr/sap/<SID>/JCxx/j2ee/cluster
        Start J2EE engine
    If deployment is correctly done, native files will be downloaded.
    Best regards,
    Dezso

Maybe you are looking for