Quantcast
Channel: SCN : Discussion List - SAP on Oracle
Viewing all articles
Browse latest Browse all 1892

Disp+work is no coming up

$
0
0

Hi experts,

 

I performed the database refresh on quality with production backup.

 

Did all the necessary steps. But when starting the quality system ABAP part is up but there is no j2ee processes in MMC.

 

and disp+work is not up fully as in screenshot.

 

system detail is as:

ECC6.0 ehp3.

Oracle 10g

windows 20xx.

 

 

the log details are as

 

dev_disp

 

Mon Dec 23 16:33:11 2013

*** WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 4 seconds

***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c  5418]

MtxInit: 30000 0 0

DpSysAdmExtInit: ABAP is active

DpSysAdmExtInit: VMC (JAVA VM in WP) is not active

DpIPCInit2: start server >DEVQA_QAS_00                            <

DpShMCreate: sizeof(wp_adm)        29792    (1752)

DpShMCreate: sizeof(tm_adm)        5912704    (29416)

DpShMCreate: sizeof(wp_ca_adm)        24064    (80)

DpShMCreate: sizeof(appc_ca_adm)    8000    (80)

DpCommTableSize: max/headSize/ftSize/tableSize=500/16/552064/552080

DpShMCreate: sizeof(comm_adm)        552080    (1088)

DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0

DpShMCreate: sizeof(slock_adm)        0    (104)

DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0

DpShMCreate: sizeof(file_adm)        0    (72)

DpShMCreate: sizeof(vmc_adm)        0    (1864)

DpShMCreate: sizeof(wall_adm)        (41664/36752/64/192)

DpShMCreate: sizeof(gw_adm)    48

DpShMCreate: SHM_DP_ADM_KEY        (addr: 000000000EBC0050, size: 6614016)

DpShMCreate: allocated sys_adm at 000000000EBC0050

DpShMCreate: allocated wp_adm at 000000000EBC21F0

DpShMCreate: allocated tm_adm_list at 000000000EBC9650

DpShMCreate: allocated tm_adm at 000000000EBC96B0

DpShMCreate: allocated wp_ca_adm at 000000000F16CF30

DpShMCreate: allocated appc_ca_adm at 000000000F172D30

DpShMCreate: allocated comm_adm at 000000000F174C70

DpShMCreate: system runs without slock table

DpShMCreate: system runs without file table

DpShMCreate: allocated vmc_adm_list at 000000000F1FB900

DpShMCreate: allocated gw_adm at 000000000F1FB980

DpShMCreate: system runs without vmc_adm

DpShMCreate: allocated ca_info at 000000000F1FB9B0

DpShMCreate: allocated wall_adm at 000000000F1FB9C0

MBUF state OFF

DpCommInitTable: init table for 500 entries

rdisp/queue_size_check_value :  -> off

ThTaskStatus: rdisp/reset_online_during_debug 0

EmInit: MmSetImplementation( 2 ).

MM global diagnostic options set: 0

<ES> client 0 initializing ....

<ES> InitFreeList

<ES> block size is 4096 kByte.

<ES> Info: em/initial_size_MB( 16378MB) not multiple of em/blocksize_KB( 4096KB)

<ES> Info: em/initial_size_MB rounded up to 16380MB

Using implementation view

<EsNT> Using memory model view.

<EsNT> Memory Reset disabled as NT default

 

Mon Dec 23 16:33:12 2013

<ES> 4094 blocks reserved for free list.

ES initialized.

mm.dump: set maximum dump mem to 96 MB

J2EE server info

  start = TRUE

  state = STARTED

  pid = 3620

  argv[0] = D:\usr\sap\QAS\DVEBMGS00\exe\jcontrol.EXE

  argv[1] = D:\usr\sap\QAS\DVEBMGS00\exe\jcontrol.EXE

  argv[2] = pf=D:\usr\sap\QAS\SYS\profile\QAS_DVEBMGS00_DEVQA

  argv[3] = -DSAPSTART=1

  argv[4] = -DCONNECT_PORT=65000

  argv[5] = -DSAPSYSTEM=00

  argv[6] = -DSAPSYSTEMNAME=QAS

  argv[7] = -DSAPMYNAME=DEVQA_QAS_00

  argv[8] = -DSAPPROFILE=D:\usr\sap\QAS\SYS\profile\QAS_DVEBMGS00_DEVQA

  argv[9] = -DFRFC_FALLBACK=ON

  argv[10] = -DFRFC_FALLBACK_HOST=localhost

  start_lazy = 0

  start_control = SAP J2EE startup framework

 

DpJ2eeStart: j2ee state = STARTED

rdisp/http_min_wait_dia_wp : 1 -> 1

***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c   1692]

***LOG Q0K=> DpMsAttach, mscon ( DEVQA) [dpxxdisp.c   12429]

DpStartStopMsg: send start message (myname is >DEVQA_QAS_00                            <)

DpStartStopMsg: start msg sent

CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

CCMS: Initalizing shared memory of size 60000000 for monitoring segment.

CCMS: Checking Downtime Configuration of Monitoring Segment.

CCMS: start to initalize 3.X shared alert area (first segment).

DpMsgAdmin: Set release to 7000, patchlevel 0

MBUF state PREPARED

MBUF component UP

DpMBufHwIdSet: set Hardware-ID

***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1050]

DpMsgAdmin: Set patchno for this platform to 184

Release check o.K.

DpJ2eeLogin: j2ee state = CONNECTED

 

Regards,

 

Gesh Raj


Viewing all articles
Browse latest Browse all 1892

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>