Instance no. for additonal dialog instances

Hi,
We currently have <b>'00'</b> as our Central Instance no.,  <b>'01'</b> is our SCS instance no.
We plan to install two more additonal dialog instances connecting to this central instance on separate servers.
Is there a best practice for instance nos. on the dialog instances.?
Should they be same 00 (as our central instance) or does this matter at all? Should they be unique across the portal landscape?
Any help will be appreciated.
Best Regards,

Hi,
the instance no does not matter in your scenario. It must only be unique per (physical) server as it defines the TCP ports that are used by the SAP instance. E.g. if you have two portal intallations on one server, its instance no.s must be different. If on separate servers, they can be identical. The latter also applies for additional dialog instances on separate servers.
The only thing that you need to keep unique across your (complete!) SAP landscape is the 3 letter SID.
Regards,
Dominik

Similar Messages

  • Setting the parameter DIR_ORAHOME for a Dialog Instance

    I have been advised by the SAP GoLiveCheck to set the parameter DIR_ORAHOME for my dialog instances. The Oracle home is currently on the central instance at G:\oracle\SID\102. What must the path for the parameter DIR_ORAHOME be set to on the dialog instance? (central_host\.....???))
    Help.
    Scott

    Hello Scott,
    >> What must the path for the parameter DIR_ORAHOME be set to on the dialog instance?
    The paraemeter must be the same as on the database server itself. Set the DIR_ORAHOME in the default profile.. that is the way we do it.
    For example: /oracle/<SID>/102_64
    Regards
    Stefan

  • Question about SSO (for Java Dialog instance) for Portal EP 6.0 SP 20

    Hi All
    I have following question.
    We are running Portal 6.0 SP 20. We have JAVA (Portal) CI+DB running on single host SAPQP1 and Two JAVA Dialog Instances (J2EE Application servers) running on separate host namely SAPAP35 and SAPAP36.
    I was able to configure SSO between SAPQP1 (CI+DB) and ECC R/3 system (QC1). SSO is working fine. Users can access all ESS/MSS data in portal when they use Portal URL running on SAPQP1 (http://sapqp1.xxxxx.com:50000/irj).
    But when users try to access ESS/MSS data via portal (URL) running on SAPQP35 (http://sapap35.xxxxx.com:50000/irj) and SAPAP36 ((http://sapap36.xxxxx.com:50000/irj) SSO does not work, i.e it system asks user id and password.
    So , how I can configure SSO between SAPAP35 and SAPAP36 JAVA Dialog instances and ECC R/3?

    Hi Sandip,
    obviously you already configured QC1 to accept Tickets issued by the Java Engine on SAPQP1. Did you imported the public (java) certificates from SAPAP35 and SAPAP36 into your ECC System? The certicficates need to be added in client 000 to your System PSE and in your production client to your ACL.
    Regards,
    Enno

  • Automatic shutdown of SAP Instance after installation of Dialog Instance

    Hi all,
    We've upgraded our system from SAP4.6C to ECC6.0 running on Win2003 64 bits Oracle 10g.
    After upgrade, we installed Dialog instance (this dialog instance is running outside MS cluster) and it is running on Microsoft cluster.  When we try to start up SAP dialog instance, the system is started but it automatically shuts down again.
    Below are the trace for DEV_DISP
    =============================
    trc file: "dev_disp", trc level: 1, release: "700"
    sysno      03
    sid        P02
    systemid   562 (PC with Windows NT)
    relno      7000
    patchlevel 0
    patchno    75
    intno      20050900
    make:      multithreaded, ASCII, 64 bit, optimized
    pid        3216
    Wed Nov 22 12:32:40 2006
    kernel runs with dp version 217(ext=109) (@(#) DPLIB-INT-VERSION-217)
    length of sys_adm_ext is 360 bytes
    SWITCH TRC-HIDE on ***
    ***LOG Q00=> DpSapEnvInit, DPStart (03 3216) [dpxxdisp.c   1237]
         shared lib "dw_xml.dll" version 75 successfully loaded
         shared lib "dw_xtc.dll" version 75 successfully loaded
         shared lib "dw_stl.dll" version 75 successfully loaded
         shared lib "dw_gui.dll" version 75 successfully loaded
         shared lib "dw_mdm.dll" version 75 successfully loaded
    rdisp/softcancel_sequence :  -> 0,5,-1
    use internal message server connection to port 3900
    Wed Nov 22 12:32:51 2006
    WARNING => DpNetCheck: NiHostToAddr(www.doesnotexist0091.qqq.nxst) took 11 seconds
    Wed Nov 22 12:33:08 2006
    WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 17 seconds
    ***LOG GZZ=> 2 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c  5273]
    MtxInit: 30000 0 0
    DpSysAdmExtInit: ABAP is active
    DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
    DpIPCInit2: start server >AP2_P02_03                              <
    DpShMCreate: sizeof(wp_adm)          5376     (896)
    DpShMCreate: sizeof(tm_adm)          4663200     (23200)
    DpShMCreate: sizeof(wp_ca_adm)          18000     (60)
    DpShMCreate: sizeof(appc_ca_adm)     6000     (60)
    DpCommTableSize: max/headSize/ftSize/tableSize=500/16/552048/552064
    DpShMCreate: sizeof(comm_adm)          552064     (1088)
    DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
    DpShMCreate: sizeof(file_adm)          0     (72)
    DpShMCreate: sizeof(vmc_adm)          0     (1496)
    DpShMCreate: sizeof(wall_adm)          (25648/36736/64/104)
    DpShMCreate: sizeof(gw_adm)     48
    DpShMCreate: SHM_DP_ADM_KEY          (addr: 0000000007DA0050, size: 5314128)
    DpShMCreate: allocated sys_adm at 0000000007DA0050
    DpShMCreate: allocated wp_adm at 0000000007DA1AB0
    DpShMCreate: allocated tm_adm_list at 0000000007DA2FB0
    DpShMCreate: allocated tm_adm at 0000000007DA3010
    DpShMCreate: allocated wp_ca_adm at 00000000082157B0
    DpShMCreate: allocated appc_ca_adm at 0000000008219E00
    DpShMCreate: allocated comm_adm at 000000000821B570
    DpShMCreate: system runs without file table
    DpShMCreate: allocated vmc_adm_list at 00000000082A21F0
    DpShMCreate: allocated gw_adm at 00000000082A2270
    DpShMCreate: system runs without vmc_adm
    DpShMCreate: allocated ca_info at 00000000082A22A0
    DpShMCreate: allocated wall_adm at 00000000082A22B0
    MBUF state OFF
    DpCommInitTable: init table for 500 entries
    EmInit: MmSetImplementation( 2 ).
    MM global diagnostic options set: 0
    <ES> client 0 initializing ....
    <ES> InitFreeList
    <ES> block size is 4096 kByte.
    Using implementation flat
    <EsNT> Memory Reset disabled as NT default
    <ES> 127 blocks reserved for free list.
    ES initialized.
    rdisp/http_min_wait_dia_wp : 1 -> 1
    Wed Nov 22 12:33:09 2006
    ***LOG Q0K=> DpMsAttach, mscon ( SAPGRPP02) [dpxxdisp.c   11586]
    DpStartStopMsg: send start message (myname is >AP2_P02_03                              <)
    DpStartStopMsg: start msg sent to message server o.k.
    CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
    CCMS: Initalizing shared memory of size 40000000 for monitoring segment.
    CCMS: start to initalize 3.X shared alert area (first segment).
    Release check o.K.
    MBUF state PREPARED
    MBUF component UP
    DpMBufHwIdSet: set Hardware-ID
    ***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1050]
    Wed Nov 22 12:33:49 2006
    ERROR => W0 (pid 1100) died [dpxxdisp.c   14241]
    ERROR => W1 (pid 1112) died [dpxxdisp.c   14241]
    ERROR => W2 (pid 1856) died [dpxxdisp.c   14241]
    ERROR => W3 (pid 576) died [dpxxdisp.c   14241]
    my types changed after wp death/restart 0x99 --> 0x98
    ERROR => W4 (pid 1368) died [dpxxdisp.c   14241]
    my types changed after wp death/restart 0x98 --> 0x90
    ERROR => W5 (pid 1108) died [dpxxdisp.c   14241]
    my types changed after wp death/restart 0x90 --> 0x80
    DP_FATAL_ERROR => DpWPCheck: no more work processes
    DISPATCHER EMERGENCY SHUTDOWN ***
    increase tracelevel of WPs
    NiWait: sleep (10000ms) ...
    NiISelect: timeout 10000ms
    NiISelect: maximum fd=569
    NiISelect: read-mask is NULL
    NiISelect: write-mask is NULL
    Wed Nov 22 12:33:59 2006
    NiISelect: TIMEOUT occured (10000ms)
    dump system status
    Workprocess Table (long)               Wed Nov 22 04:33:59 2006
    ========================
    No Ty. Pid      Status  Cause Start Err Sem CPU    Time  Program  Cl  User         Action                    Table
    0 DIA     1100 Ended         no      1   0             0                                                             
    1 DIA     1112 Ended         no      1   0             0                                                             
    2 DIA     1856 Ended         no      1   0             0                                                             
    3 DIA      576 Ended         no      1   0             0                                                             
    4 BTC     1368 Ended         no      1   0             0                                                             
    5 SPO     1108 Ended         no      1   0             0                                                             
    Dispatcher Queue Statistics               Wed Nov 22 04:33:59 2006
    ===========================
    --------++++--
    +
    Typ
    now
    high
    max
    writes
    reads
    --------++++--
    +
    NOWP
    0
    2
    2000
    6
    6
    --------++++--
    +
    DIA
    5
    5
    2000
    5
    0
    --------++++--
    +
    UPD
    0
    0
    2000
    0
    0
    --------++++--
    +
    ENQ
    0
    0
    2000
    0
    0
    --------++++--
    +
    BTC
    0
    0
    2000
    0
    0
    --------++++--
    +
    SPO
    0
    0
    2000
    0
    0
    --------++++--
    +
    UP2
    0
    0
    2000
    0
    0
    --------++++--
    +
    max_rq_id          11
    wake_evt_udp_now     0
    wake events           total     8,  udp     7 ( 87%),  shm     1 ( 12%)
    since last update     total     8,  udp     7 ( 87%),  shm     1 ( 12%)
    Dump of tm_adm structure:               Wed Nov 22 04:33:59 2006
    =========================
    Term    uid  man user    term   lastop  mod wp  ta   a/i (modes)
    Workprocess Comm. Area Blocks               Wed Nov 22 04:33:59 2006
    =============================
    Slots: 300, Used: 1, Max: 0
    --------++--
    +
    id
    owner
    pid
    eyecatcher
    --------++--
    +
    0
    DISPATCHER
    -1
    WPCAAD000
    NiWait: sleep (5000ms) ...
    NiISelect: timeout 5000ms
    NiISelect: maximum fd=569
    NiISelect: read-mask is NULL
    NiISelect: write-mask is NULL
    Wed Nov 22 12:34:04 2006
    NiISelect: TIMEOUT occured (5000ms)
    DpHalt: shutdown server >AP2_P02_03                              < (normal)
    DpJ2eeDisableRestart
    DpModState: buffer in state MBUF_PREPARED
    NiBufSend starting
    NiIWrite: hdl 2 sent data (wrt=110,pac=1,MESG_IO)
    MsINiWrite: sent 110 bytes
    MsIModState: change state to SHUTDOWN
    DpModState: change server state from STARTING to SHUTDOWN
    Switch off Shared memory profiling
    ShmProtect( 57, 3 )
    ShmProtect(SHM_PROFILE, SHM_PROT_RW
    ShmProtect( 57, 1 )
    ShmProtect(SHM_PROFILE, SHM_PROT_RD
    DpWakeUpWps: wake up all wp's
    Stop work processes
    Stop gateway
    killing process (1096) (SOFT_KILL)
    Stop icman
    killing process (748) (SOFT_KILL)
    Terminate gui connections
    wait for end of work processes
    wait for end of gateway
    [DpProcDied] Process lives  (PID:1096  HANDLE:536)
    waiting for termination of gateway ...
    NiWait: sleep (1000ms) ...
    NiISelect: timeout 1000ms
    NiISelect: maximum fd=569
    NiISelect: read-mask is NULL
    NiISelect: write-mask is NULL
    Wed Nov 22 12:34:05 2006
    NiISelect: TIMEOUT occured (1000ms)
    [DpProcDied] Process died  (PID:1096  HANDLE:536)
    wait for end of icman
    [DpProcDied] Process lives  (PID:748  HANDLE:544)
    waiting for termination of icman ...
    NiWait: sleep (1000ms) ...
    NiISelect: timeout 1000ms
    NiISelect: maximum fd=569
    NiISelect: read-mask is NULL
    NiISelect: write-mask is NULL
    Wed Nov 22 12:34:06 2006
    NiISelect: TIMEOUT occured (1000ms)
    [DpProcDied] Process lives  (PID:748  HANDLE:544)
    waiting for termination of icman ...
    NiWait: sleep (1000ms) ...
    NiISelect: timeout 1000ms
    NiISelect: maximum fd=569
    NiISelect: read-mask is NULL
    NiISelect: write-mask is NULL
    Wed Nov 22 12:34:07 2006
    NiISelect: TIMEOUT occured (1000ms)
    [DpProcDied] Process lives  (PID:748  HANDLE:544)
    waiting for termination of icman ...
    NiWait: sleep (1000ms) ...
    NiISelect: timeout 1000ms
    NiISelect: maximum fd=569
    NiISelect: read-mask is NULL
    NiISelect: write-mask is NULL
    Wed Nov 22 12:34:08 2006
    NiISelect: TIMEOUT occured (1000ms)
    [DpProcDied] Process lives  (PID:748  HANDLE:544)
    waiting for termination of icman ...
    NiWait: sleep (1000ms) ...
    NiISelect: timeout 1000ms
    NiISelect: maximum fd=569
    NiISelect: read-mask is NULL
    NiISelect: write-mask is NULL
    Wed Nov 22 12:34:09 2006
    NiISelect: TIMEOUT occured (1000ms)
    [DpProcDied] Process lives  (PID:748  HANDLE:544)
    waiting for termination of icman ...
    NiWait: sleep (1000ms) ...
    NiISelect: timeout 1000ms
    NiISelect: maximum fd=569
    NiISelect: read-mask is NULL
    NiISelect: write-mask is NULL
    Wed Nov 22 12:34:10 2006
    NiISelect: TIMEOUT occured (1000ms)
    [DpProcDied] Process lives  (PID:748  HANDLE:544)
    waiting for termination of icman ...
    NiWait: sleep (1000ms) ...
    NiISelect: timeout 1000ms
    NiISelect: maximum fd=569
    NiISelect: read-mask is NULL
    NiISelect: write-mask is NULL
    Wed Nov 22 12:34:11 2006
    NiISelect: TIMEOUT occured (1000ms)
    [DpProcDied] Process lives  (PID:748  HANDLE:544)
    waiting for termination of icman ...
    NiWait: sleep (1000ms) ...
    NiISelect: timeout 1000ms
    NiISelect: maximum fd=569
    NiISelect: read-mask is NULL
    NiISelect: write-mask is NULL
    Wed Nov 22 12:34:12 2006
    NiISelect: TIMEOUT occured (1000ms)
    [DpProcDied] Process lives  (PID:748  HANDLE:544)
    waiting for termination of icman ...
    NiWait: sleep (1000ms) ...
    NiISelect: timeout 1000ms
    NiISelect: maximum fd=569
    NiISelect: read-mask is NULL
    NiISelect: write-mask is NULL
    Wed Nov 22 12:34:13 2006
    NiISelect: TIMEOUT occured (1000ms)
    [DpProcDied] Process lives  (PID:748  HANDLE:544)
    waiting for termination of icman ...
    NiWait: sleep (1000ms) ...
    NiISelect: timeout 1000ms
    NiISelect: maximum fd=569
    NiISelect: read-mask is NULL
    NiISelect: write-mask is NULL
    Wed Nov 22 12:34:14 2006
    NiISelect: TIMEOUT occured (1000ms)
    [DpProcDied] Process lives  (PID:748  HANDLE:544)
    waiting for termination of icman ...
    NiWait: sleep (1000ms) ...
    NiISelect: timeout 1000ms
    NiISelect: maximum fd=569
    NiISelect: read-mask is NULL
    NiISelect: write-mask is NULL
    Wed Nov 22 12:34:15 2006
    NiISelect: TIMEOUT occured (1000ms)
    [DpProcDied] Process lives  (PID:748  HANDLE:544)
    waiting for termination of icman ...
    NiWait: sleep (1000ms) ...
    NiISelect: timeout 1000ms
    NiISelect: maximum fd=569
    NiISelect: read-mask is NULL
    NiISelect: write-mask is NULL
    Wed Nov 22 12:34:16 2006
    NiISelect: TIMEOUT occured (1000ms)
    [DpProcDied] Process died  (PID:748  HANDLE:544)
    DpStartStopMsg: send stop message (myname is >AP2_P02_03                              <)
    NiIMyHostName: hostname = 'AP2'
    AdGetSelfIdentRecord: >                                                                           <
    AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0
    AdCvtRecToExt: opcode 4 (AD_STARTSTOP), ser 0, ex 0, errno 0
    DpConvertRequest: net size = 189 bytes
    NiBufSend starting
    NiIWrite: hdl 2 sent data (wrt=562,pac=1,MESG_IO)
    MsINiWrite: sent 562 bytes
    send msg (len 110+452) to MSG_SERVER, type 1
    DpStartStopMsg: stop msg sent to message server o.k.
    NiIRead: hdl 2 received data (rcd=274,pac=1,MESG_IO)
    NiBufIIn: NIBUF len=274
    NiBufIIn: packet complete for hdl 2
    NiBufReceive starting
    MsINiRead: received 274 bytes
    MSG received, len 110+164, flag 1, from MSG_SERVER          , typ 0, key -
    DpHalt: received 164 bytes from message server
    NiIRead: hdl 2 received data (rcd=274,pac=1,MESG_IO)
    NiBufIIn: NIBUF len=274
    NiBufIIn: packet complete for hdl 2
    NiBufReceive starting
    MsINiRead: received 274 bytes
    MSG received, len 110+164, flag 1, from MSG_SERVER          , typ 0, key -
    DpHalt: received 164 bytes from message server
    NiIRead: hdl 2 received data (rcd=274,pac=1,MESG_IO)
    NiBufIIn: NIBUF len=274
    NiBufIIn: packet complete for hdl 2
    NiBufReceive starting
    MsINiRead: received 274 bytes
    MSG received, len 110+164, flag 1, from MSG_SERVER          , typ 0, key -
    DpHalt: received 164 bytes from message server
    NiIRead: hdl 2 received data (rcd=274,pac=1,MESG_IO)
    NiBufIIn: NIBUF len=274
    NiBufIIn: packet complete for hdl 2
    NiBufReceive starting
    MsINiRead: received 274 bytes
    MSG received, len 110+164, flag 1, from MSG_SERVER          , typ 0, key -
    DpHalt: received 164 bytes from message server
    NiIRead: hdl 2 recv would block (errno=EAGAIN)
    NiIRead: read for hdl 2 timed out (0ms)
    DpHalt: no more messages from the message server
    DpHalt: send keepalive to synchronize with the message server
    NiBufSend starting
    NiIWrite: hdl 2 sent data (wrt=114,pac=1,MESG_IO)
    MsINiWrite: sent 114 bytes
    send msg (len 110+4) to name           MSG_SERVER, type 0, key -
    MsSndName: MS_NOOP ok
    Send 4 bytes to MSG_SERVER
    NiIRead: hdl 2 recv would block (errno=EAGAIN)
    NiIPeek: peek successful for hdl 2 (r)
    NiIRead: hdl 2 received data (rcd=114,pac=1,MESG_IO)
    NiBufIIn: NIBUF len=114
    NiBufIIn: packet complete for hdl 2
    NiBufReceive starting
    MsINiRead: received 114 bytes
    MSG received, len 110+4, flag 3, from MSG_SERVER          , typ 0, key -
    Received 4 bytes from MSG_SERVER                             
    Received opcode MS_NOOP from msg_server, reply MSOP_OK
    MsOpReceive: ok
    MsSendKeepalive : keepalive sent to message server
    NiIRead: hdl 2 recv would block (errno=EAGAIN)
    Wed Nov 22 12:34:17 2006
    NiIPeek: peek for hdl 2 timed out (r; 1000ms)
    NiIRead: read for hdl 2 timed out (1000ms)
    DpHalt: no more messages from the message server
    DpHalt: sync with message server o.k.
    detach from message server
    ***LOG Q0M=> DpMsDetach, ms_detach () [dpxxdisp.c   11899]
    NiBufSend starting
    NiIWrite: hdl 2 sent data (wrt=110,pac=1,MESG_IO)
    MsINiWrite: sent 110 bytes
    MsIDetach: send logout to msg_server
    MsIDetach: call exit function
    DpMsShutdownHook called
    NiBufISelUpdate: new MODE -- (r-) for hdl 2 in set0
    SiSelNSet: set events of sock 548 to: ---
    NiBufISelRemove: remove hdl 2 from set0
    SiSelNRemove: removed sock 548 (pos=2)
    SiSelNRemove: removed sock 548
    NiSelIRemove: removed hdl 2
    MBUF state OFF
    AdGetSelfIdentRecord: >                                                                           <
    AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0
    AdCvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0
    AdCvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0
    blks_in_queue/wp_ca_blk_no/wp_max_no = 1/300/6
    LOCK WP ca_blk 1
    make DISP owner of wp_ca_blk 1
    DpRqPutIntoQueue: put request into queue (reqtype 1, prio LOW, rq_id 14)
    MBUF component DOWN
    NiICloseHandle: shutdown and close hdl 2 / sock 548
    NiBufIClose: clear extension for hdl 2
    MsIDetach: detach MS-system
    cleanup EM
    EsCleanup ....
    EmCleanup() -> 0
    Es2Cleanup: Cleanup ES2
    ***LOG Q05=> DpHalt, DPStop ( 3216) [dpxxdisp.c   10259]
    Good Bye .....
    Below is the trace for DEV_W0
    ==========================
    M patchno    75
    M intno      20050900
    M make:      multithreaded, ASCII, 64 bit, optimized
    M pid        1100
    M
    M  kernel runs with dp version 217(ext=109) (@(#) DPLIB-INT-VERSION-217)
    M  length of sys_adm_ext is 360 bytes
    M  ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 1100) [dpxxdisp.c   1299]
    I  MtxInit: 30000 0 0
    M  DpSysAdmExtCreate: ABAP is active
    M  DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
    M  DpShMCreate: sizeof(wp_adm)          5376     (896)
    M  DpShMCreate: sizeof(tm_adm)          4663200     (23200)
    M  DpShMCreate: sizeof(wp_ca_adm)          18000     (60)
    M  DpShMCreate: sizeof(appc_ca_adm)     6000     (60)
    M  DpCommTableSize: max/headSize/ftSize/tableSize=500/16/552048/552064
    M  DpShMCreate: sizeof(comm_adm)          552064     (1088)
    M  DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
    M  DpShMCreate: sizeof(file_adm)          0     (72)
    M  DpShMCreate: sizeof(vmc_adm)          0     (1496)
    M  DpShMCreate: sizeof(wall_adm)          (25648/36736/64/104)
    M  DpShMCreate: sizeof(gw_adm)     48
    M  DpShMCreate: SHM_DP_ADM_KEY          (addr: 000000000DDA0050, size: 5314128)
    M  DpShMCreate: allocated sys_adm at 000000000DDA0050
    M  DpShMCreate: allocated wp_adm at 000000000DDA1AB0
    M  DpShMCreate: allocated tm_adm_list at 000000000DDA2FB0
    M  DpShMCreate: allocated tm_adm at 000000000DDA3010
    M  DpShMCreate: allocated wp_ca_adm at 000000000E2157B0
    M  DpShMCreate: allocated appc_ca_adm at 000000000E219E00
    M  DpShMCreate: allocated comm_adm at 000000000E21B570
    M  DpShMCreate: system runs without file table
    M  DpShMCreate: allocated vmc_adm_list at 000000000E2A21F0
    M  DpShMCreate: allocated gw_adm at 000000000E2A2270
    M  DpShMCreate: system runs without vmc_adm
    M  DpShMCreate: allocated ca_info at 000000000E2A22A0
    M  DpShMCreate: allocated wall_adm at 000000000E2A22B0
    X  EmInit: MmSetImplementation( 2 ).
    X  MM global diagnostic options set: 0
    X  <ES> client 0 initializing ....
    X  Using implementation flat
    M  <EsNT> Memory Reset disabled as NT default
    X  ES initialized.
    M  ThInit: running on host AP2

    M Wed Nov 22 12:33:10 2006
    M  calling db_connect ...
    C  Prepending E:\usr\sap\P02\D03\exe to Path.
    M  call semaphore clean-up function ...
    M  ***LOG Q0E=> DpSigGenHandler, Exception (c06d007e) [dpnttool.c   432]
    M  -
    C-STACK -
    SAP (R) - R/3(TM) Callstack, Version 1.0
    Copyright (C) SAP AG. All rights reserved.
    Application exception occurred:
    Exception : c06d007e (Unknown exception)
    App       : disp+work.EXE (pid=1100)
    When      : 11/22/2006 12:33:14.515
    Threads   : 2
    Computer Name       : AP2
    User Name           : SAPServiceP02
    Number of Processors: 4
    Processor Type: EM64T Family 6 Model 15 Stepping 6
    Windows Version     : 5.2 Current Build: 3790
    State Dump for Thread Id 440
    --> (FAULT) Stack Back Trace <--
    FramePtr         ReturnAd         Param#1          Function Name
    000000000678f720 00000000078488ca 0000000000000003 kernel32!PulseEvent
    000000000678f7f0 0000000007847fe6 0000000007926000 dboraslib!__delayLoadHelper2 [delayhlp.cpp (271)]
    000000000678f860 00000000078136cd 000000000678f8b0 dboraslib!_tailMerge_OCI_dll
    000000000678f8c0 000000000782f3d8 0000003d00000000 dboraslib!get_oci_client_version [dboci.c (2766)]
    000000000678fa90 0000000001182107 000000000678fd80 dboraslib!DbSlConnect [dbsloci.c (1835)]
    000000000678fce0 000000000118251e 0000000000000000 disp+work!open_con [dbcon.c (3582)]
    000000000678fd50 00000000011856de 00000000ffffffff disp+work!supply_con [dbcon.c (3830)]
    000000000678fd90 000000000117826c 0000000000000001 disp+work!dbsl_connect [dbslxxx.c (232)]
    000000000678fdf0 00000000004ca16a 000000000755476c disp+work!db_connect [dblink.c (422)]
    000000000678fe80 00000000004cf609 0000000006d6bdfd disp+work!ThInit [thxxhead.c (1404)]
    000000000678feb0 000000000042c9e6 ffffffff00000002 disp+work!ThStart [thxxhead.c (1114)]
    000000000678fee0 0000000000401097 ffffffff00000003 disp+work!DpMain [dpxxdisp.c (1119)]
    000000000678ff10 00000000018919c1 0000000000000000 disp+work!nlsui_main [thxxanf.c (82)]
    000000000678ff70 0000000078d5965c 0000000000000000 disp+work!mainCRTStartup [crtexe.c (501)]
    000000000678ffa0 0000000000000000 0000000001891850 kernel32!BaseProcessStart
    State Dump for Thread Id c70
    --> Stack Back Trace <--
    FramePtr         ReturnAd         Param#1          Function Name
    000000000bd9fe40 0000000078d5f611 0000000006d31460 ntdll!NtFsControlFile
    000000000bd9feb0 000000000178a99f 0000000000000000 kernel32!ConnectNamedPipe
    000000000bd9ff40 000007ff7fc411c4 0000000000000000 disp+work!SigIMsgFunc [signt.c (595)]
    000000000bd9ff70 0000000078d6b66a 0000000078d6b630 msvcrt!endthreadex
    000000000bd9ffa0 0000000000000000 0000000000000000 kernel32!BaseThreadStart
    M  -

    M Wed Nov 22 12:33:15 2006
    M  call clean-up function ...
    M  in_ThErrHandle: 1
    M  ThSigHandler: signal (step 1, th_errno 11, action 4)

    M  Info for wp 0

    M    stat = 4
    M    reqtype = 1
    M    act_reqtype = -1
    M    rq_info = 0
    M    tid = -1
    M    mode = 255
    M    len = -1
    M    rq_id = 65535
    M    rq_source = 255
    M    last_tid = 0
    M    last_mode = 0
    M    semaphore = 0
    M    act_cs_count = 0
    M    control_flag = 0
    M    int_checked_resource(RFC) = 0
    M    ext_checked_resource(RFC) = 0
    M    int_checked_resource(HTTP) = 0
    M    ext_checked_resource(HTTP) = 0
    M    report = >                                        <
    M    action = 0
    M    tab_name = >                              <
    M    vm = V-1

    M  *****************************************************************************
    M  *
    M  *  LOCATION    SAP-Server AP2_P02_03 on host AP2 (wp 0)
    M  *  ERROR       ThSigHandler: signal
    M  *
    M  *  TIME        Wed Nov 22 12:33:15 2006
    M  *  RELEASE     700
    M  *  COMPONENT   Taskhandler
    M  *  VERSION     1
    M  *  RC          11
    M  *  MODULE      thxxhead.c
    M  *  LINE        10354
    M  *  COUNTER     1
    M  *
    M  *****************************************************************************

    M  PfStatDisconnect: disconnect statistics
    M  Entering TH_CALLHOOKS
    M  ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
    M  *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c   720]
    M  *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c  260]
    M  Entering ThSetStatError
    M  ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
    M  Entering ThReadDetachMode
    M  ***LOG Q02=> wp_halt, WPStop (Workproc 0 1100) [dpnttool.c   327]
    M  return from clean-up function ...
    Does anybody has a solution for this problem?
    Thank you.

    Hi all again,
    I had the same problem and found a solution for it.
    I made two steps to start the dialog instance successful. First I modified the NLS_LANG setting in the registry and enviroment (only if necessary). Second, I fetched the last Oracle Instant Client <b>OCL10264.sar</b> from SAP Net and extract the file to <b>E:\usr\sap\PDV\SYS\exe\nuc\NTAMD64</b> (This directory was created through the Installer. The Kernel lies under <b>E:\usr\sap\PDV\D20\exe</b>)
    Now I changed the variable <b>DIR_CLIENT_ORAHOME = $(DIR_EXECUTABLE)</b> to
    <b>DIR_CLIENT_ORAHOME = E:\usr\sap\PDV\SYS\exe\nuc\NTAMD64</b> in the Instance Profile of the new Dialog Instance. So the Kernel knows that he has to use the Oracle Instance Client and the profilevariable says where he found it.
    After these modifications the Dialog Instance starts with success.
    With kind regards
    Thomas Espenhain

  • WAS 6.40 Dialog Instance Installation

    Hi,
    I am installing a dialog instance for our WAS 6.40 JAVA on Win 2003 with ORacle DB. During the installation I get the following error.
    ERROR 2006-02-22 15:19:50
    CJS-20058  J2EE Engine J01 of SAP system EPD did not reach state "Starting Applications" after 1154 seconds: giving up.
    The is no special arguments for a dialog instance installation in documentation. So I did run SAPINST and selected dialog instance installation. Is something missing?
    Regards
    Following errors exist in log files.
    dev_jcmon
    [Thr 5348] *** ERROR => Can't attach to administration shared memory (rc=3) [jcmonxx.c    219]
    Error occurred during initialization of VM
    Could not reserve enough space for object heap
    in dev_jcontrol
    [Thr 1712] *** ERROR => Invalid property value [en.host/temepdev] [jstartxx.c   789]
    [Thr 1712] *** ERROR => Invalid property value [en.port/3201] [jstartxx.c   789]
    dev_icmon
    [Thr 1468] *** ERROR => Can't attach to administration shared memory (rc=3) [jcmonxx.c    219]
    Message was edited by: sez yigit

    Hi,
    This is content of instance.properties file.
    ID6181900.ClassPath=./bin/boot/boot.jar:./bin/system/bytecode.jar:.
    ID6181900.Debuggable=no
    ID6181900.JLaunchParameters=
    ID6181900.JavaParameters=-Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Djco.jarm=1 -XX:NewSize=28m -XX:MaxNewSize=28m -Xms170m -XX:+DisableExplicitGC -Drdbms.driverLocation=D:/usr/sap/EPD/J00/j2ee/classes12.jar
    ID6181900.JavaPath=C:/j2sdk1.4.2_08
    ID6181900.LogName=dispatcher
    ID6181900.MainClass=com.sap.engine.boot.Start
    ID6181900.MaxHeapSize=170
    ID6181900.Name=dispatcher
    ID6181900.Parameters=
    ID6181900.RootPath=D:/usr/sap/EPD/J00/j2ee/cluster/dispatcher
    ID6181900.Type=dispatcher
    ID6181950.ClassPath=./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.
    ID6181950.DebugMode=no
    ID6181950.DebugPort=50021
    ID6181950.Debuggable=no
    ID6181950.JLaunchParameters=
    ID6181950.JavaParameters=-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 -Dorg.xml.sax.driver=com.sap.engine.lib.xml.parser.SAXParser -Djco.jarm=1 -Dsun.io.useCanonCaches=false -XX:NewSize=85M -XX:MaxNewSize=85M -XX:MaxPermSize=192m -Djava.awt.headless=true -XX:PermSize=192m -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=1 -Xms512M -verbose:gc -XX:DisableExplicitGC -XX:PrintGCDetails -XX:PrintGCTimeStamps -XX:UseParNewGC -Djco.jarm=1 -Dsun.io.useCanonCaches=false -XX:NewSize=170m -XX:MaxNewSize=170m -XX:MaxPermSize=192m -Djava.awt.headless=true -XX:PermSize=192m -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=1 -Xms1024m -verbose:gc -XX:DisableExplicitGC -XX:PrintGCDetails -XX:PrintGCTimeStamps -XX:UseParNewGC -Djco.jarm=1 -Dsun.io.useCanonCaches=false -XX:NewSize=341m -XX:MaxNewSize=341m -XX:MaxPermSize=192m -Djava.awt.headless=true -XX:PermSize=192m -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=1 -Xms2048m -verbose:gc -XX:DisableExplicitGC -XX:PrintGCDetails -XX:PrintGCTimeStamps -XX:UseParNewGC -Djco.jarm=1 -Dsun.io.useCanonCaches=false -XX:NewSize=682m -XX:MaxNewSize=682m -XX:MaxPermSize=192m -Djava.awt.headless=true -XX:PermSize=192m -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=1 -Xms4096m -verbose:gc -XX:DisableExplicitGC -XX:PrintGCDetails -XX:PrintGCTimeStamps -XX:UseParNewGC -Djco.jarm=1 -Dsun.io.useCanonCaches=false -XX:NewSize=341m -XX:MaxNewSize=341m -XX:MaxPermSize=192m -Djava.awt.headless=true -XX:PermSize=192m -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=1 -Xms2048m -verbose:gc -XX:DisableExplicitGC -XX:PrintGCDetails -XX:PrintGCTimeStamps -XX:UseParNewGC -Djco.jarm=1 -Dsun.io.useCanonCaches=false -XX:NewSize=170m -XX:MaxNewSize=170m -XX:MaxPermSize=192m -Djava.awt.headless=true -XX:PermSize=192m -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=1 -Xms1024m -verbose:gc -XX:DisableExplicitGC -XX:PrintGCDetails -XX:PrintGCTimeStamps -XX:UseParNewGC -Drdbms.driverLocation=D:/usr/sap/EPD/J00/j2ee/classes12.jar
    ID6181950.JavaPath=C:/j2sdk1.4.2_08
    ID6181950.LogName=server0
    ID6181950.MainClass=com.sap.engine.boot.Start
    ID6181950.MaxHeapSize=2048
    ID6181950.Name=server0
    ID6181950.Parameters=
    ID6181950.RootPath=D:/usr/sap/EPD/J00/j2ee/cluster/server0
    ID6181950.Type=server
    bootstrap.ClassPath=./bootstrap/launcher.jar
    bootstrap.JavaParameters=-Djco.jarm=1 -Djco.jarm=1 -Djco.jarm=1 -Djco.jarm=1 -Djco.jarm=1 -Djco.jarm=1 -Djco.jarm=1 -Djco.jarm=1 -Djco.jarm=1 -Djco.jarm=1 -Djco.jarm=1 -Djco.jarm=1
    bootstrap.JavaPath=C:/j2sdk1.4.2_08
    bootstrap.MainClass=com.sap.engine.offline.OfflineToolStart
    bootstrap.MaxHeapSize=512
    bootstrap.Name=bootstrap
    bootstrap.Parameters=com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0061819
    bootstrap.RootPath=D:/usr/sap/EPD/J00/j2ee/cluster
    bootstrap.Type=bootstrap
    bootstrap_ID6181900.ClassPath=./bootstrap/launcher.jar
    bootstrap_ID6181900.JLaunchParameters=
    bootstrap_ID6181900.JavaParameters=-Djco.jarm=1 -Djco.jarm=1 -Djco.jarm=1 -Djco.jarm=1 -Djco.jarm=1 -Djco.jarm=1 -Djco.jarm=1 -Djco.jarm=1 -Djco.jarm=1 -Djco.jarm=1 -Djco.jarm=1 -Djco.jarm=1
    bootstrap_ID6181900.JavaPath=C:/j2sdk1.4.2_08
    bootstrap_ID6181900.MainClass=com.sap.engine.offline.OfflineToolStart
    bootstrap_ID6181900.MaxHeapSize=170
    bootstrap_ID6181900.Name=dispatcher bootstrap
    bootstrap_ID6181900.Parameters=com.sap.engine.bootstrap.Bootstrap ./bootstrap ID006181900
    bootstrap_ID6181900.RootPath=D:/usr/sap/EPD/J00/j2ee/cluster
    bootstrap_ID6181900.Type=bootstrap
    bootstrap_ID6181950.ClassPath=./bootstrap/launcher.jar
    bootstrap_ID6181950.JLaunchParameters=
    bootstrap_ID6181950.JavaParameters=-Djco.jarm=1 -Djco.jarm=1 -Djco.jarm=1 -Djco.jarm=1 -Djco.jarm=1 -Djco.jarm=1 -Djco.jarm=1 -Djco.jarm=1 -Djco.jarm=1 -Djco.jarm=1 -Djco.jarm=1 -Djco.jarm=1
    bootstrap_ID6181950.JavaPath=C:/j2sdk1.4.2_08
    bootstrap_ID6181950.MainClass=com.sap.engine.offline.OfflineToolStart
    bootstrap_ID6181950.MaxHeapSize=2048
    bootstrap_ID6181950.Name=server0 bootstrap
    bootstrap_ID6181950.Parameters=com.sap.engine.bootstrap.Bootstrap ./bootstrap ID006181950
    bootstrap_ID6181950.RootPath=D:/usr/sap/EPD/J00/j2ee/cluster
    bootstrap_ID6181950.Type=bootstrap
    instance.box.number=EPDJ00temitsprd
    instance.en.host=temepdev
    instance.en.port=3201
    instance.enabled=yes
    instance.install.dir=D:\usr\sap\EPD\J00\j2ee
    instance.ms.host=temepdev
    instance.ms.port=3601
    instance.osLibsPath=D:/usr/sap/EPD/J00/j2ee/os_libs
    instance.runAction=NONE
    instance.runMode=NORMAL
    instance.system.id=0
    dev_icmon
    trc file: "D:\usr\sap\EPD\J00\work\dev_jcmon", trc level: 1, release: "640"
    node name   : jcmon
    pid         : 2560
    system name : EPD
    system nr.  : 00
    started at  : Thu Feb 23 10:20:53 2006
    arguments   :
        arg[00] : D:\usr\sap/EPD/J00/j2ee/os_libs/jcmon.exe
        arg[01] : pf=
    temepdev\sapmnt\EPD\SYS\profile/EPD_J00_temitsprd
    [Thr 2084] Thu Feb 23 10:20:53 2006
    [Thr 2084] INFO: Unknown property [box.number=EPDJ00temitsprd]
    [Thr 2084] INFO: Unknown property [ms.host=temepdev]
    [Thr 2084] INFO: Unknown property [ms.port=3601]
    [Thr 2084] INFO: Unknown property [system.id=0]
    JStartupReadInstanceProperties: read instance properties [D:\usr\sap\EPD\J00\j2ee\cluster\instance.properties]
    -> ms host    : temepdev
    -> ms port    : 3601
    -> OS libs    : D:\usr\sap\EPD\J00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    [Thr 2084] *** ERROR => Can't attach to administration shared memory (rc=3) [jcmonxx.c    219]
    std_bootstrap_ID6181950.out
    stdout/stderr redirect
    node name   : server0 bootstrap
    pid         : 3304
    system name : EPD
    system nr.  : 00
    started at  : Thu Feb 23 10:14:16 2006
    Error occurred during initialization of VM
    Could not reserve enough space for object heap
    Failed to reserve 1610612736 (0x60000000) bytes before loading DLLs (error 8).

  • Installing 620 SAP_BASIS Dialog Instance with 6.40 Installation Master CD

    Greetings,
    At present we have a SAP R/3 Enterprise 47x200 which is dsitributed across two (windows 2003) clustered servers, one for the Central Instance and other for the Database (Oracle 9.2.0.5).
    Now and due to perfomance issues on the Central Instance we'd lke to add a Dialog Instance and here is where the doubts come up.
    Our SAP_BASIS version is 620 (System -> Status) whereas our SAP Kernel level is 640_REL (SM51).
    We have the original 6.20 Kernel CD but we don't have any valid SAP Installation Master CD (originally we made an upgrade from a 4.6B version) so I downloaded from service.sap.com/support the  51033746_13.ZIP (Installation_Master_6.20_6.40_06_08) file (I didn't found any other file better that this one).
    The first problem is that when I start sapinst.exe it ask (CD Browser Dialog) for a SAP 6.40 Kernel CD and not the 6.20 Kernel CD I already have. I have found a workaround editing LABEL.ASC file but I think it isn't a good practice.
    If I download the Kernel 6.40 from service.sap.com 51030763_1.ZIP (DVD_NW04_SR1_6.40_SAP_Kernel_Oracle) the Sapinst application works perfectly, but here comes up our doubts...
    -  Could be any problem using these 6.40 installation (Master Installation & Kernel) files for a Dialog Instance installatio in our environment? Are there other installation files which could fit better than these one? Where could I find them?
    -  When I install a Dialog Instance, does it make changes into the Database Server and Central Instance?
    - Initially we'd like to install the Dialog Instance in a test Server, try it, check that it works as we expect, and discard it in order to buy a big and powerful server where we'll definitely install the Dialog Instance. In this case, can we simply discard the test server or we have to follow a complex process for uninstall it?  (this question is somehow related to the previous one).
    Any help would be greatly appreciated. Thanks in advance.
    Javier

    Hi,
    it is OK that you have 640 kernel even if your BASIS is 620. 620 kernel is no longer supported by SAP.
    - Could be any problem using these 6.40 installation (Master Installation & Kernel) files for a Dialog Instance installatio in our environment? Are there other installation files which could fit better than these one? Where could I find them?
    You master DVD is correct
    - When I install a Dialog Instance, does it make changes into the Database Server and Central Instance?
    It does not make any changes to DB, you will see next Dialog instance in SM51 then
    - Initially we'd like to install the Dialog Instance in a test Server, try it, check that it works as we expect, and discard it in order to buy a big and powerful server where we'll definitely install the Dialog Instance. In this case, can we simply discard the test server or we have to follow a complex process for uninstall it? (this question is somehow related to the previous one).
    You can discard your dialog instance without following special procedures.

  • Dialog Instances Java are not up after System Copy NW2004s SR2 ABAP+JAVA

    Hello guys,
    I have just  performed a system copy of our BW system (douple stack NW2004s) wich consists from CI and 2 DIs. First I  made an export using SAPINST (Software from SAP_BUSINESS_SUITE_2005_SR2 for sparc solaris), where I choosed in SAP Installation Master->SAp Netweaver 2004s Support Release 2->Additional Software Life-cycle Tasks->System Copy->Oracle->Source System->Central System->Based on ABAP and Java->Database and Central Instance Export. I couldn't find any special task for export java from my dialog instances, so I thought it would be ok like that. Then I used the same software on my target system, choosed ...Additional Software Life-cycle Tasks->System Copy->Oracle->Target System->Central System->Based on ABAP and Java->Central System Installation. In the Dialog input phase of SAPINST I indicated that use db specific tools to copy your database. So I made the database restore+recovery with our DB tools and continued withthe SAPINST and Import.
    Afterwards the ABAP part and Java on the central Instance run perfect, but Java Stack is not up by both of Dialog Instances. I have checked the configtool on the server where the CI is running (the DIs are running on different linux servers) and couldn't see any entries for my dialog instances, only the CI was seable there. I tried to start configtool from the application server, but there I could find only the file config.properties in the directory /usr/sap/<SID>/.../j2ee/configtool/, others were simply not there, so it was impossible to start it. Have i forgotten something by EXPORT/IMPORT or I should just use other software for coping a System with douple stack on a CI and DIs? Or should I get configtools for Linux platform ( have searched but not found yet) and try to make the same changes wich i have done by the CI before i started Java on the CI? The most irritated point is that i can't see the dialog instanes in Configtool from the CI.
    Any other suggestions and good advices?
    Thanks a lot in advance.
    Regards, Polina

    Hi Manoj, </p>
    I have founded following information in the work directory of one of my dialog instances ( where the java stack doesn't want to start after the copy):  /usr/sap/SID/instance/work/ <br>
    1) std_server0.out  is in the condition before the system copy, no new data was written there. <br>
    2)dev_disp <br>
    DpJ2eeStart: j2ee state = STARTED<br>
    DpJ2eeLogin: j2ee state = CONNECTED<br>
    Fri Feb 26 12:58:04 2010<br>
    ERROR => DpJ2eeMsgProcess: NiRead failed (NIECONN_BROKEN) [dpxxj2ee.c   1212]<br>
    DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)<p>
    Fri Feb 26 12:58:20 2010<br>
    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN<br>
    Fri Feb 26 12:57:20 2010<br>
    ***LOG Q0I=> NiIBindSocket: could not delete file '/tmp/.sapstream64984' for hdl 2: unlink (1: Operation not permitted) [nixxi.cpp 3207]<br>
    ERROR => NiIBindSocket: could not delete file '/tmp/.sapstream64984' (hdl 2; errno=0) [nixxi.cpp    3214]<br>
    WARNING => NiIBind: Could not bind local domain socket, only listening on internet socket [nixxi.cpp    3491]<p>
    It seems that java is trying to start but something goes wrong and  it have to shut down<p>
    3)dev_bootstrap<br>
    [Thr 1086335296] JLaunchIExitJava: exit hook is called (rc = 66)<br>
    [Thr 1086335296] **********************************************************************<br>
    ERROR => The Java VM terminated with a non-zero exit code.<br>
    Please see SAP Note 943602 , section 'J2EE Engine exit codes'<br>
    for additional information and trouble shooting.<br>
    **********************************************************************<br>
    [Thr 1086335296] SigISetIgnoreAction : SIG_IGN for signal 17<br>
    [Thr 1086335296] JLaunchCloseProgram: good bye (exitcode = 66)<p>
    4) jvm_bootstrap.out<br>
    ...<br>
    Exception occurred:<br>
    com.sap.engine.frame.core.configuration.NameNotFoundException: A configuration with the path "cluster_data/dispatcher/ID264509300" does not exist.
    ..<br>
    Exception occurred:<br>
    com.sap.engine.bootstrap.SynchronizationException: Database initialization failed! Check database properties!<br>
            at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:476)<br>
            at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:146)<br>
    com.sap.engine.bootstrap.SynchronizationException: No such Dialog Instance (ID264509300) in the database! Check database consistency or local Bootstrap properties!<br>
    [Bootstrap module]> Problem occurred while performing synchronization.<p>
    j2ee/instance_id = ID2645093 <--- that is the ID of those DI where i took these traces from. So it seems that this ID is not in the database at all. Probably the infromation about the java stack of my DIs was not exported at all...<p>
    Thanks in advance. <br>
    Regards, <br>
    Polina

  • Installing Dialog Instances with ECC 6.0 and SQL Server 2005

    Hi, I have my ECC 6.0 SAP Server, it is Central Instance, Database instance, all in one. My users are working fine, however we will be adding some new users (15) and we want add a Dialog Instance. Can I add one Dialog instance to my landscape without any changes to my SAP Server ??? ..... My dialog instance will be in a new host.
    My hardware SAP Server is: 16 GB RAM, 500 GB RAID 5 for my database, four processors.
    What could be my Dialogue Instance hardware?
    I have read than I must install with sapinst and select Dialogue Instance and follow instructions. Are there any others considerations?? .....
    Do I must install SQL Server in the host Dialog instance ??.
    Please if you have some suggestions.
    Regards.

    Hello Jose,
    You can install your dialog instance without doing any change to the existing setup as you have mentioned its on a seprate new host.
    Two CPU's and 8GB memory would be fine for your dialog instance.It all depends on your requirement.
    Yes you need to install the dialog instance using SAPINST, its kool and sapinst would take care of all.
    You need not install any SQL server in the dialog instance host only you need to have a SQL client installed but that would be taken care by SAPINST.
    Hope this would clarify your query.
    Thanks and Regards,
    -Bijesh.

  • Installation of Dialog Instance (DI)

    Hello gurus,
    My main goal is install an ABAP Dialog Instance (DI) on a diferent host/server than the Central Instance (CI) is installed!
    We have an ECC 6.0 ABAP + JAVA (ABAP is non-unicode) on Windows Server 2003 x64 with SQL Server 2008 and we need a dialog instance (application server) to distribute SAP workload! I know that is possible to install a dialog instance on the same physical server with database server where is already installed the central instance... but what we want is simple, is install it not in the same server but on separate machine/server. We already have the other server that will be for the dialog instance, this is a Windows Server 2003 but this is a x32 bits!! (Is there any problem with this? It´s possible install a dialog instance in x32 bits server?!)
    Other question... before installation of dialog instance I have to install a database? or a client database which will comunicate with main database on central instance / server ? If so, I don´t know but it is possible to install a database client SQL Server 2008 on Windows Server 2003 that runs X32 bits ?? I guess not... only SQL versions 2000 / 2005 isn´t it?
    So, when I read the installation guide of SAP ERP 6.0 SR3 I only find there a short reference to Dialog Instance Installation and that is in fact a very little reference to this process! For instance, in this guide there is a reference to a dialog instance installation such a MSCS landscape...:
    You have to install at least one dialog instance for MSCS. You have the following options to install the dialog instance:
    ... but we don´t want install it in MSCS (cluester) because we don´t have a cluster configuration between this two windows servers and besides that we don´t want to have it!!
    We only want install a Dialog Instance in an existing Central Instance between two windows servers in same network!
    Can you help me to clarify this questions...?
    Thanks in advance,
    Best regards,
    João Dimas - Portugal

    Many thanks Matt Kangas,
    Now I can understand with more clarity some things...!!
    What I have to do is run the master installation DVD in future server that it will have the dialog instance... as I said that is a X32 server and so I have to run the master installation for X32 (ERP 6.0 SR3), isn´t it?
    Other thing Matt... when you warn me for the distribution kernel executables... what do you meant? I've never seen a system with both instances (CI and DI) installed, but this two will share the kernel files?
    Regarding database client... I only have install the SQL Server software on dialog instance server/machine!! But I think I will find a problem... this is a X32 machine so I think (correct me if I´m wrong) that is impossible to install SQL Server 2008 in X32 machines, it only supports X64 bits, if so it´s possible with other SQL version, like 2005 (SP3)? As I said, the database in CI machine/server is installed on version SQL Server 2008, so there is some problem in having a diferent client database version installed on DI server/machine (X32)?
    Best regards,
    João Dimas - Portugal

  • Installation of central or dialog instance?

    Hello,
    We are currently running an ABAP-System only. We want to install an AS JAVA in order to use Adobe Document Services. We only want to use Print Forms and no Interactive Forms.
    My question is, if the JAVA installation has to be as a central instance or as a dialog instance? I read through all the guides I could find, but I'm not quite sure in this point. Is the dialog instance only usable if you are already using a JAVA distributed system?
    What are your recommendations, is it enough to install a simple AS JAVA or would you recommend installing EP or EPC? As I said, the AS JAVA is only needed for Adobe Print Forms for now.
    Thanks in advance

    Hai,
    Check SAP Note: 925741, point no:1.
    For the scenario of print forms you can Install Adobe document services on a SAP Web AS 6.40 ABAP + J2EE system (J2EE Add-In).
    Regards,
    Yoganand.V

  • Install new Dialog Instance on 64-bit Server with 32-bit database

    I need to set up a new Application Server for our current ECC 5.0 32-bit Oracle 9.2.0.7 Non Unicode Database.  The new server is x64-bit and will have Windows 2003 64-bit OS.  I am reading SAP notes 785888 and 814834 and need help understanding how exactly to do this.  The database server is 32-bit Windows 2003 and so is all the other application servers.  Do I use the Oracle 9.2.0 client for 32-bit Oracle and do I use the SAP ECC X64 Install Master in setting up the dialog instance or do I use the 32-bit Install master?  Has anyone done this type of setup before?  Thanks.

    Hi,
    all basic information is provide in note 785888.
    you want to install dialog install on 64bit windows for 32 bit central instance for that you should consider following.
    -> file system is accessible from both host  vice a versa for that you can create one use sapinst on 64 bit host with administrator authorization. and create same user on central instance with administrator authorization and same password.
    -> perform dialog instance installation using this user  ( i.e sapinst)
    -> if you want to use  dialog instance on 64 bit host with 64 bit kernel, install oracle client 10.2 for 64 bit on 64 bit host of windows. for media information check note 949116.
    ->use  non unicode kernel because central instance use non unicode kernel.
    -> most important 64 bit dialog instance required 64 bit kernel, SAPinst installation screen ABAP System > Instance Directories, where you are asked for the "Location of SAP System Executable", you choose "Yes, locate executables on central instance host", before choosing "Next". The executables for the dialog instance are installed to
    <sapglobalhost>\sapmnt\<sapsid>\SYS\exe\<nuc\uc>\NT<AMD64|IA64|I386>*
    so when you want to apply kernel patch you have to uncar the kernel package to this location.
    -> maintain the kernel patch level same on both host.
    regards,
    kaushal

  • Portal dialog instance questions

    Dear SDN,
    2 questions on installing a dialog instance for the portal.
    1. Does the dialog instance need to have a a different instance number than the central instance if it is on a separate physical host
    2.  Can you log onto the portal from the dialog instance?
    dialog inst # = 3
    Ci inst #   =   1
    i.e.  http://dialoghost:50003/irj?
    Thanks

    Prakash Singh wrote:"No if the dialog instance is not on the same machine. 2. Yes you should be able to logon to portal from dialog instance. http://name of your dialog instance server: port/irj"
    The above statement is accurate, because any SAP instance is uniquely identified by its hostname and its instance number. So, on the same host you must have a different instance number for your SAP instance and on multiple hosts you could run an SAP instance with the same instance number as your central instance.
    Regards,
    Phani.

  • Location of Dialog Instance

    Hi all,
    We have several locations in the world and we want to install servers with dialog instance's for every location.
    What is the best place for a dialog instance?
    At the location itself or, like somebody told me, near the DBserver/Central Instance.
    Logically I would say, at the remote location itself...but I want some opinions on that.
    Regards,
    Bob Gulien

    Hi Bob,
    No, the recommendation is to install Dialog instance near DBServer/central Instance preferably connected by a high-speed (G-bit) LAN.
    The reason is that the data exchnage between SAP Servers are approx 10-times more than server to end-user. So, having Dialog Instance at the remote location will put enormous pressure on network and performance will not be adequate.
    Hope it solves your query ...
    Cheers !!
    Satya.
    PS: Pls reward points if the answer was helpful..thx,

  • How to delete Dialog instance on NW04

    Hi guys
    I have an installation NW04 on Cluster MSCS:
    Central Instance on node A
    SCS instance on Cluster Disk
    Dialog instance on node B
    We have performed upgrade to NW04s, and now in postprocessin we should deinstall Dialog Instance and install it again with software NW04s.
    Here documentation guide:
    ****************************************+
    After the upgrade of the central instance, you need to upgrade the dialog instance to the new release.
    Due to the fact that some special settings and binaries on a dialog instance cannot be upgraded
    remotely, you can only upgrade a dialog instance by uninstalling the old instance and then installing
    a new dialog instance with the tool SAPinst.
    Procedure
    1. Uninstall the old dialog instances as described in the document Installation Guide ‒ SAP Web Application
    Server 6.40 Java on <Operating System>: <Database>, Part II Installation and Post-Installation.
    2. Install the new dialog instances as described in the document Installation Guide ‒ <SAP NetWeaver /
    SAP application> <Technology> on <Operating System>: <Database>.
    Point 1, is :
    *************+
    1. Log on as a user with domain administration rights.
    2. Choose Start u2192 Settings u2192 Control Panel u2192 Add/Remove Programs.
    3. The Add/Remove Programs dialog box appears.
    4. Find the SAP entries.
    . Note
    Each SAP instance that is installed on the computer is listed with an entry like SAP Application Server
    for System <SAPSID> instance.
    5. Choose Remove.
    The SAP Uninstall Wizard starts.
    6. In the Welcome window, choose Next.
    The dialog box Uninstalling SAP System appears for you to select an uninstall method
    Depending on your selection, note the following when you use the check box to delete an SAP instance:
    -- If your check box is marked gray, you delete or uninstall the following:
    The SAP instance directory, for example:
    \usr\sap\<SAPSID>\D00
    Services, for example:
    SAP<SAPSID>_00
    The whole system directory, for example:
    \usr\sap\<SAPSID>\*
    -- If your check box is marked black, you delete or uninstall the following:
    The SAP instance directory, for example:
    \usr\sap\<SAPSID>\D00
    Services, for example, SAP <SAPSID>_00
    The whole system directory, for example:
    \usr\sap\<SAPSID>\*
    Local and domain user accounts
    If you have different SAP instances that use the same <SAPSID>, you can delete the instance
    directory only.
    The wizard informs you when the SAP system or selected instances have been deleted successfully
    But in my node B there is no SAP entry on Start u2192 Settings u2192 Control Panel u2192 Add/Remove Programs, however Dialog Instance exists, and windows service exists...and so on...
    So how can we deinstall this dialog instance???
    Thanks and regards
    Javier

    Hi
    In node A there is JC30 (Java central instance)
    In node B there is J32 (Java Dialog instance)
    SCS31 (Services Central Instance) is now in node A, but can be switched.
    Database Instance is OUTSIDE, is located on a Unix Server. (is not affected in this case)
    Looking node B, there is no entry on Adding/Removing Programs regarding to SAP instance.
    Of course, I can see windows services on node B, one for J32, other for SAPoscol, and one more for SCS31.
    Any idea?
    Thanks
    Javier

  • Differnce between central instance ,dialog instance and application instanc

    Hi all
    Please explain me what is central instance. what is it differnce betwenn the
    other instances like dilaog instance ,apllication instance.
    What is the exact use of having many instances ?
    regards
    Sanjeev.S

    Hi Sanjeev,
    First of all let me Clarify between Cental instance(CI)and Central Service instance(SCS). When you install NW04/NW04s systems on WIndows, when you open you windows console, you would first find the SID name that you have installed and when you expand this you'll find 2 instances. When you expand the first instance you'll find that there are message server and Enqueue server listed. This instance is called as Central Service instance or simply called SCS. You can look at the folder structure /usr/sap/<SID>/.
    Now the second instance is called as Central instance, when expanded you would see a SDM, a dispatcher and a server node. This is the instance which processes all your requests.
    Now answering your question about Dialog instance, When the CI is overloaded, i.e. your dispatcher is overloaded and your server is overloaded , you would install a dialog instance, which means that the database need not be installed for the Dialog instance and it can be on any system. While installing the Dialog instance it would ask you which Cental instance I have to refer, then you would be giving the necessary system to which you have created a dialog instance.
    Giving a graphical view,
    SID < J2E>
    < DATABASE>
    <hostname>00  message server
                            enqueue server
    <hostname>01  SDM
                            dispatcher
                            server0
    This is your one SAP system. Now you feel that this system is overloaded with lot of users, any there are many user who will be logging in again, so what you would do is install a dialog instance which would be referiing to J2E database but will have its own dispatcher and server0. SDM, message server and enqueue server are only one per systems.
    Now the dialog instance for J2E would look like this
    SID < K2E>
    <hostname2>01 dispatcher
                             server0
    Dialog instance is mainly for load balacing, now you can access the database of J2E by typing a different URL i.e. of K2E and hostname2 but still accees the data of the J2E. The communication between Dialog and Central instance is thru message server.
    In case you find it difficult to push thru, please let me know..

Maybe you are looking for