Tables on Solution Manager
Hi all,
I would like to know the tables where test case id and test case status get stored in solution manager.
I was able to find the table TNODE02_AT which contains test case id which was created in configuration t-code SOLAR02
but i want to know the test case id assigned for test plan in test plan management t-code STWB_2.
hi ganashree,
did you ever find out the tables which relate test packages and test cases?
if yes then could you please share?
thanks,
emilia
Similar Messages
-
Table for solution manager key in ecc
Hi all
can any please tell me "solution manager key" is stored in which table in ecc
Thanks & regards
ChaitanyaHI,
I dont think it will be stored some where, it seems to be just installationpre-requisites.
What is the need of tracking solution manager key ..Its more interesting for me!
Regards -
Tables used for Devloping Customer Reports Of solution manager report
Dear All,
Kindkly Suggest Some Tables,which i can use in developing the solution manager report.
key fields i m using From results of Tcode CRM_DNO_MONITOR
ID
PERSON RESPONSIBLE
TEAM SUPPORT
POSTING DATE
PRIORITY
THANKS IN ADVANCE.Update my question my deadline is up to complete,
Regards,
Thiru. R -
Need to customized report in solution manager but duno which table to pull
Dear Gurus,
I need to create a customized report in solution manager to get the following fields:
1) Message number
2) Transport number link to the message number
3) Target client the transport go to
4) Date/Time of status change to "Consolidate"
5) Date/Time of transport imported
6) Date/Time of Email Sent through message when requesting for transport
Pls, help find the relation tables for the above objects, I'm a developer without any functional help and with no knowleadge of solution manager. Pls, help ASAP!
Desperate,
BelindaHi Belinda,
open the service message application in the Solman.
Open a service message, focus the needed fields and press F1 for technical details. Try finding the tables by using the where-used list.
Cheers,
André -
Java process table empty after upgrade solution manager 7.1 Sp10
Hi Experts,
I have installed solution manager 7.1 SP3 and completed the SP10 patch upgrade using SUM tool. The upgrade was completed successfully. After upgrade igswd was red. Then i copied the Igs files in kernel files. Now ABAP instance and Igs is working now but JAVA is not coming up. JAVA process table also empty. Can any one help me to solve this issue. Attached the error for reference.
trc file: "dev_disp", trc level: 1, release: "721"
sysno 00
sid VSM
systemid 562 (PC with Windows NT)
relno 7210
patchlevel 0
patchno 201
intno 20020600
make multithreaded, Unicode, 64 bit, optimized
profile \\VKCSOL\sapmnt\VSM\SYS\profile\VSM_DVEBMGS00_VKCSOL
pid 5448
kernel runs with dp version 138000(ext=120000) (@(#) DPLIB-INT-VERSION-138000-UC)
length of sys_adm_ext is 592 bytes
*** SWITCH TRC-HIDE on ***
***LOG Q00=> DpSapEnvInit, DPStart (00 5448) [dpxxdisp.c 1316]
shared lib "dw_xml.dll" version 201 successfully loaded
shared lib "dw_xtc.dll" version 201 successfully loaded
shared lib "dw_stl.dll" version 201 successfully loaded
shared lib "dw_gui.dll" version 201 successfully loaded
shared lib "dw_mdm.dll" version 201 successfully loaded
shared lib "dw_rndrt.dll" version 201 successfully loaded
shared lib "dw_abp.dll" version 201 successfully loaded
shared lib "dw_sym.dll" version 201 successfully loaded
shared lib "dw_aci.dll" version 201 successfully loaded
rdisp/softcancel_sequence : -> 0,5,-1
use internal message server connection to port 3900
rdisp/dynamic_wp_check : 1
rdisp/calculateLoadAverage : 1
Tue Apr 01 19:02:09 2014
*** WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 6 seconds
***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 6479]
MtxInit: 30000 0 0
DpSysAdmExtInit: ABAP is active
DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
display_tcp_ip: 0
DpIPCInit2: write dp-profile-values into sys_adm_ext
DpIPCInit2: start server >VKCSOL_VSM_00 <
DpShMCreate: sizeof(wp_adm) 42864 (2256)
DpShMCreate: sizeof(tm_adm) 5517056 (27448)
DpShMCreate: sizeof(wp_ca_adm) 64000 (64)
DpShMCreate: sizeof(appc_ca_adm) 64000 (64)
DpCommTableSize: max/headSize/ftSize/tableSize=500/16/1384064/1384080
DpShMCreate: sizeof(comm_adm) 1384080 (2744)
DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
DpShMCreate: sizeof(slock_adm) 0 (296)
DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
DpShMCreate: sizeof(file_adm) 0 (80)
DpShMCreate: sizeof(vmc_adm) 0 (2160)
DpShMCreate: sizeof(wall_adm) (41664/42896/64/192)
DpShMCreate: sizeof(gw_adm) 48
DpShMCreate: sizeof(j2ee_adm) 3952
DpShMCreate: SHM_DP_ADM_KEY (addr: 000000000DDE0050, size: 7174832)
DpShMCreate: allocated sys_adm at 000000000DDE0060
DpShMCreate: allocated wp_adm_list at 000000000DDE30B0
DpShMCreate: allocated wp_adm at 000000000DDE32A0
DpShMCreate: allocated tm_adm_list at 000000000DDEDA20
DpShMCreate: allocated tm_adm at 000000000DDEDA70
DpShMCreate: allocated wp_ca_adm at 000000000E330980
DpShMCreate: allocated appc_ca_adm at 000000000E340390
DpShMCreate: allocated comm_adm at 000000000E34FDA0
DpShMCreate: system runs without slock table
DpShMCreate: system runs without file table
DpShMCreate: allocated vmc_adm_list at 000000000E4A1C40
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated gw_adm at 000000000E4A1CF0
DpShMCreate: allocated j2ee_adm at 000000000E4A1D30
DpShMCreate: allocated ca_info at 000000000E4A2CB0
DpShMCreate: allocated wall_adm at 000000000E4A2D40
DpCommAttachTable: attached comm table (header=000000000E34FDA0/ft=000000000E34FDB0)
DpSysAdmIntInit: initialize sys_adm
rdisp/test_roll : roll strategy is DP_NORMAL_ROLL
dia token check not active (10 token)
MBUF state OFF
DpCommInitTable: init table for 500 entries
DpRqQInit: keep protect_queue / slots_per_queue 0 / 2001 in sys_adm
rdisp/queue_size_check_value : -> on,50,30,40,500,50,500,80
EmInit: MmSetImplementation( 2 ).
MM global diagnostic options set: 0
<ES> client 0 initializing ....
<ES> EsILock: use spinlock for locking
<ES> InitFreeList
<ES> block size is 4096 kByte.
<ES> Info: em/initial_size_MB( 16383MB) not multiple of em/blocksize_KB( 4096KB)
<ES> Info: em/initial_size_MB rounded up to 16384MB
Using implementation view
<EsNT> Using memory model view.
<EsNT> Memory Reset disabled as NT default
<ES> 4095 blocks reserved for free list.
ES initialized.
mm.dump: set maximum dump mem to 192 MB
mm.dump: set global maximum dump mem to 192 MB
EsRegisterEmCheck: Register EmGetEsHandles at 000000013FC48640
DpVmcSetActive: set vmc state DP_VMC_NOT_ACTIVE
MPI: dynamic quotas disabled.
MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
J2EE server info
start = TRUE
state = STARTED
pid = 5824
argv[0] = D:\usr\sap\VSM\DVEBMGS00\exe\jcontrol.EXE
argv[1] = D:\usr\sap\VSM\DVEBMGS00\exe\jcontrol.EXE
argv[2] = pf=\\VKCSOL\sapmnt\VSM\SYS\profile\VSM_DVEBMGS00_VKCSOL
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=65000
argv[5] = -DSAPSYSTEM=00
argv[6] = -DSAPSYSTEMNAME=VSM
argv[7] = -DSAPMYNAME=VKCSOL_VSM_00
argv[8] = -DSAPPROFILE=\\VKCSOL\sapmnt\VSM\SYS\profile\VSM_DVEBMGS00_VKCSOL
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 ( 4.0.1 4.0.1 5.1) [dpxxdisp.c 1702]
***LOG Q0K=> DpMsAttach, mscon ( VKCSOL) [dpxxdisp.c 12707]
MBUF state LOADING
DpStartStopMsg: send start message (myname is >VKCSOL_VSM_00 <)
DpStartStopMsg: start msg sent
CCMS: Initialized monitoring segment of size 60000000.
CCMS: Initialized CCMS Headers in the shared monitoring segment.
CCMS: Checking Downtime Configuration of Monitoring Segment.
CCMS: AlMsUpload called by wp 1024.
Tue Apr 01 19:02:10 2014
01.04.2014 13:32:10.628 PID=5448, TID=5744 SapTimer info. QPC/Windows time mismatch. System suspended, busy, missing ticks. Mismatch QpcTime-WindowsTime: -168 millisec (max +0). Slept 1000 millisec, Qpc elapsed: +1000 millisec, WindowsUtc elapsed +1168 millisec. SapTime-WindowsUtcTime=-1 seconds. TotalTimeCorrection=+0 millisec, QpcTime-WindowsUtcTime=-1028 millisec (*).
Tue Apr 01 19:02:11 2014
CCMS: AlMsUpload successful for D:\usr\sap\VSM\DVEBMGS00\log\ALMTTREE.DAT (2189 MTEs).
Tue Apr 01 19:02:13 2014
CCMS: start to initalize 3.X shared alert area (first segment).
DpJ2eeLogin: j2ee state = CONNECTED
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1296]
MBUF state ACTIVE
DpWpBlksLow: max wp blocks in queue is 800 (80 %)
MBUF component UP
DpMsgProcess: 1 server in MBUF
DpAppcBlksLow: max appc blocks in queue is 500 (50 %)
Tue Apr 01 19:02:21 2014
DpModState: change server state from STARTING to ACTIVE
Tue Apr 01 19:02:23 2014
***LOG Q0I=> NiIRead: P=127.0.0.1:61107; L=127.0.0.1:65000: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 5086]
*** ERROR => NiIRead: SiRecv failed for hdl 33/sock 1008
(SI_ECONN_BROKEN/10054; I4; ST; P=127.0.0.1:61107; L=127.0.0.1:65000) [nixxi.cpp 5086]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=5824)
*** ERROR => DpProcKill: kill failed [dpntdisp.c 397]
DpIJ2eeShutdown: j2ee state = SHUTDOWN
Regards
Jose H.Hi Ashutosh,
Thanks for your immediate reply. Please find the log below.
trc file: "dev_server0", trc level: 1, release: "721"
node name : ID3506750
pid : 8068
system name : VSM
system nr. : 00
started at : Sat Mar 29 13:41:08 2014
arguments :
arg[00] : D:\usr\sap\VSM\DVEBMGS00\exe\jlaunch.exe
arg[01] : pf=D:\usr\sap\VSM\SYS\profile\VSM_DVEBMGS00_VKCSOL
arg[02] : -DSAPINFO=VSM_00_server
arg[03] : pf=D:\usr\sap\VSM\SYS\profile\VSM_DVEBMGS00_VKCSOL
arg[04] : -DSAPSTART=1
Used property files
-> files [00] : D:\usr\sap\VSM\DVEBMGS00\j2ee\cluster\instance.properties
Bootstrap nodes
-> [00] bootstrap : D:\usr\sap\VSM\DVEBMGS00\j2ee\cluster\instance.properties
-> [01] bootstrap_ID3506700 : D:\usr\sap\VSM\DVEBMGS00\j2ee\cluster\instance.properties
-> [02] bootstrap_ID3506750 : D:\usr\sap\VSM\DVEBMGS00\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID3506700 : D:\usr\sap\VSM\DVEBMGS00\j2ee\cluster\instance.properties
-> [01] ID3506750 : D:\usr\sap\VSM\DVEBMGS00\j2ee\cluster\instance.properties
JStartupReadInstanceProperties: read instance properties [D:\usr\sap\VSM\DVEBMGS00\j2ee\cluster\instance.properties]
-> ms host : VKCSOL
-> ms port : 3901
-> OS libs : D:\usr\sap\VSM\DVEBMGS00\j2ee\os_libs
-> Admin URL :
-> run mode : safe
-> run action : UPGRADE
-> enabled : yes
[Thr 19300] Sat Mar 29 13:41:08 2014
[Thr 19300] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 19300] JLaunchRequestQueueInit: create pipe listener thread
[Thr 19300] JLaunchInitSignalHandling: signal handling is disabled
[Thr 4928] WaitSyncSemThread: Thread 4928 started as semaphore monitor thread.
[Thr 23444] JLaunchRequestFunc: Thread 23444 started as listener thread for np messages.
[Thr 19300] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)
[Thr 19300] MPI: dynamic quotas disabled.
[Thr 19300] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
[Thr 19300] CCMS: Detected Double Stack (parameter "rdisp/j2ee_start" is active)
[Thr 19300] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Doublestack.
[Thr 19300] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Doublestack.
[Thr 19300] CCMS: CCMS Monitoring Initialization finished, rc=0.
[Thr 19300] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) - using -Xmx2048m [jstartxx.c 2800]
[Thr 19300] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\VSM\DVEBMGS00\exe\jvmx.jar
JStartupIReadSection: read node properties [ID3506750]
-> node name : server0
-> node type : server
-> node execute : yes
-> jlaunch parameters :
-> java path : D:\usr\sap\VSM\DVEBMGS00\exe\sapjvm_4
-> java parameters : -XX:MaxNewSize=600M -XX:NewSize=600M -XX:MaxPermSize=512M -XX:PermSize=512M -XX:+UseConcMarkSweepGC -XX:+DisableExplicitGC -XX:TargetSurvivorRatio=90 -XX:SurvivorRatio=4 -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -verbose:gc -XX:SoftRefLRUPolicyMSPerMB=1 -XX:HeapDumpPath=OOM.hprof -XX:+HeapDumpOnOutOfMemoryError -Djco.jarm=1 -Djava.awt.headless=true -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dsun.io.useCanonCaches=false -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Dcom.sap.jvm.scenario=j2ee -XX:+JavaMonitorsInStackTrace -Xbootclasspath/p:D:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/connectors/AutoProbeConnector.jar;D:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/Agent.jar -Dcom.wily.introscope.agent.agentName=VSM_DVEBMGS00_server0 -Dcom.wily.introscope.agentProfile=D:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/IntroscopeAgent.profile -Dstartup.mode=SAFE -Dstartup.action=UPGRADE
-> java vm version : 4.1.024 1.6-b04
-> java vm vendor : SAP Java Server VM (SAP AG)
-> java vm type : server
-> java vm cpu : amd64
-> heap size : 2048M
-> init heap size : 2048M
-> stack size : 2M
-> root path : D:\usr\sap\VSM\DVEBMGS00\j2ee\cluster\server0
-> class path : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path : D:\usr\sap\VSM\DVEBMGS00\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 : D:\usr\sap\VSM\DVEBMGS00\exe\jstartup.jar;D:\usr\sap\VSM\DVEBMGS00\exe\jvmx.jar
-> shutdown class : com.sap.engine.boot.Start
-> parameters :
-> debuggable : no
-> debug mode : no
-> debug port : 50021
-> shutdown timeout : 120 sec.
[Thr 19300] JLaunchISetDebugMode: set debug mode [no]
[Thr 9092] JLaunchIStartFunc: Thread 9092 started as Java VM thread.
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack : 2097152 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -XX:MaxNewSize=600M
-> arg[ 4]: -XX:NewSize=600M
-> arg[ 5]: -XX:MaxPermSize=512M
-> arg[ 6]: -XX:PermSize=512M
-> arg[ 7]: -XX:+UseConcMarkSweepGC
-> arg[ 8]: -XX:+DisableExplicitGC
-> arg[ 9]: -XX:TargetSurvivorRatio=90
-> arg[ 10]: -XX:SurvivorRatio=4
-> arg[ 11]: -XX:+PrintGCDetails
-> arg[ 12]: -XX:+PrintGCTimeStamps
-> arg[ 13]: -verbose:gc
-> arg[ 14]: -XX:SoftRefLRUPolicyMSPerMB=1
-> arg[ 15]: -XX:HeapDumpPath=OOM.hprof
-> arg[ 16]: -XX:+HeapDumpOnOutOfMemoryError
-> arg[ 17]: -Djco.jarm=1
-> arg[ 18]: -Djava.awt.headless=true
-> arg[ 19]: -Djava.security.policy=./java.policy
-> arg[ 20]: -Djava.security.egd=file:/dev/urandom
-> arg[ 21]: -Dsun.io.useCanonCaches=false
-> arg[ 22]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[ 23]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[ 24]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
-> arg[ 25]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[ 26]: -Dcom.sap.jvm.scenario=j2ee
-> arg[ 27]: -XX:+JavaMonitorsInStackTrace
-> arg[ 28]: -Xbootclasspath/p:D:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/connectors/AutoProbeConnector.jar;D:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/Agent.jar
-> arg[ 29]: -Dcom.wily.introscope.agent.agentName=VSM_DVEBMGS00_server0
-> arg[ 30]: -Dcom.wily.introscope.agentProfile=D:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/IntroscopeAgent.profile
-> arg[ 31]: -Dstartup.mode=SAFE
-> arg[ 32]: -Dstartup.action=UPGRADE
-> arg[ 33]: -Dsys.global.dir=D:\usr\sap\VSM\SYS\global
-> arg[ 34]: -Dapplication.home=D:\usr\sap\VSM\DVEBMGS00\exe
-> arg[ 35]: -Djava.class.path=D:\usr\sap\VSM\DVEBMGS00\exe\jstartup.jar;D:\usr\sap\VSM\DVEBMGS00\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> arg[ 36]: -Djava.library.path=D:\usr\sap\VSM\DVEBMGS00\exe\sapjvm_4\jre\bin\server;D:\usr\sap\VSM\DVEBMGS00\exe\sapjvm_4\jre\bin;D:\usr\sap\VSM\DVEBMGS00\exe\sapjvm_4\bin;D:\usr\sap\VSM\DVEBMGS00\j2ee\os_libs;D:\usr\sap\VSM\DVEBMGS00\exe\sapjvm_4\jre\bin\server;D:\usr\sap\VSM\DVEBMGS00\exe\sapjvm_4\jre\bin;D:\usr\sap\VSM\DVEBMGS00\exe\sapjvm_4\bin;D:\usr\sap\VSM\DVEBMGS00\j2ee\os_libs;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;D:\usr\sap\VSM\DVEBMGS00\exe;D:\usr\sap\VSM\SYS\exe\uc\NTAMD64
-> arg[ 37]: -Dmemory.manager=2048M
-> arg[ 38]: -Xmx2048M
-> arg[ 39]: -Xms2048M
-> arg[ 40]: -Xss2M
-> arg[ 41]: -DLoadBalanceRestricted=no
-> arg[ 42]: -Djstartup.mode=JCONTROL
-> arg[ 43]: -Djstartup.ownProcessId=8068
-> arg[ 44]: -Djstartup.ownHardwareId=I0649086862
-> arg[ 45]: -Djstartup.whoami=server
-> arg[ 46]: -Djstartup.debuggable=no
-> arg[ 47]: -Xjvmx
-> arg[ 48]: -XsapSystem=00
-> arg[ 49]: -XmonGcCallback
-> arg[ 50]: -DSAPINFO=VSM_00_server
-> arg[ 51]: -DSAPSTART=1
-> arg[ 52]: -DSAPSTARTUP=1
-> arg[ 53]: -DSAPSYSTEM=00
-> arg[ 54]: -DSAPSYSTEMNAME=VSM
-> arg[ 55]: -DSAPMYNAME=VKCSOL_VSM_00
-> arg[ 56]: -DSAPDBHOST=VKCSOL
-> arg[ 57]: -Dj2ee.dbhost=VKCSOL
(CompilerOracle read from file D:\usr\sap\VSM\DVEBMGS00\exe\sapjvm_4\jre\.hotspot_compiler)
[Thr 9092] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [server0]
[Thr 20084] Sat Mar 29 13:41:10 2014
[Thr 20084] JHVM_RegisterNatives: com.sap.bc.krn.perf.PerfTimes
2.781: [GC 2.781: [ParNew: 409600K->2306K(512000K), 0.0126041 secs] 409600K->2306K(1994752K), 0.0127881 secs] [Times: user=0.05 sys=0.00, real=0.01 secs]
[Thr 20084] Sat Mar 29 13:41:11 2014
[Thr 20084] JHVM_RegisterNatives: com.sap.bc.proj.jstartup.JStartupFramework
[Thr 20084] JLaunchISetClusterId: set cluster id 3506750
[Thr 20084] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 20084] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
Sat Mar 29 13:41:23 2014
15.071: [GC 15.071: [ParNew: 411906K->16315K(512000K), 0.0306641 secs] 411906K->16315K(1994752K), 0.0309011 secs] [Times: user=0.13 sys=0.00, real=0.03 secs]
Sat Mar 29 13:41:32 2014
24.118: [GC 24.118: [ParNew: 425915K->29114K(512000K), 0.0363407 secs] 425915K->29114K(1994752K), 0.0365634 secs] [Times: user=0.11 sys=0.02, real=0.04 secs]
[Thr 18736] Sat Mar 29 13:41:38 2014
[Thr 18736] JHVM_RegisterNatives: com.sap.mona.api.JMonAPI
[Thr 18736] CCMS: openMonitoringSegment(): inside static JMON Lib: already connected.
[Thr 17644] JHVM_RegisterNatives: com.sap.mw.rfc.driver.CpicDriver
[Thr 19340] JHVM_RegisterNatives: com.sap.security.core.server.vsi.service.jni.VirusScanInterface
[Thr 7816] Sat Mar 29 13:41:39 2014
[Thr 7816] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 7816] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 25/sock 7884
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 17936] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 17936] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 7888
(SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp 3285]
31.816: [GC 31.816: [ParNew[Thr 21936] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 21936] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 1/sock 7856
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 2800] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 2800] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 9/sock 7860
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
: 438714K->67978K(512000K), 0.0626636 secs] 438714K->67978K(1994752K), 0.0628963 secs] [Times: user=0.11 sys=0.08, real=0.06 secs]
[Thr 7276] Sat Mar 29 13:41:40 2014
[Thr 7276] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 7276] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 7988
(SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp 3285]
[Thr 24572] Sat Mar 29 13:41:42 2014
[Thr 24572] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 24572] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 8132
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 5092] Sat Mar 29 13:41:43 2014
[Thr 5092] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 5092] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 8088
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 20084] JLaunchISetState: change state from [Starting (2)] to [Starting applications (10)]
[Thr 24276] Sat Mar 29 13:41:44 2014
[Thr 24276] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 24276] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 8480
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 1316] Sat Mar 29 13:41:45 2014
[Thr 1316] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 1316] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 9292
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 13068] Sat Mar 29 13:41:46 2014
[Thr 13068] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 13068] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 9736
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 19652] JLaunchISetState: change state from [Starting applications (10)] to [Running (3)]
[Thr 17680] Sat Mar 29 13:41:47 2014
[Thr 17680] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 39/sock 9736
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 23760] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 23760] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 10/sock 5976
(SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp 3285]
[Thr 17680] Sat Mar 29 13:41:48 2014
[Thr 17680] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 32/sock 9736
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 17680] Sat Mar 29 13:41:49 2014
[Thr 17680] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 9736
(SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp 3285]
[Thr 17680] Sat Mar 29 13:41:50 2014
[Thr 17680] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 6272
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 5348] Sat Mar 29 13:41:51 2014
[Thr 5348] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 5348] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 6336
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 17548] Sat Mar 29 13:41:52 2014
[Thr 17548] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 17548] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 6548
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 4216] Sat Mar 29 13:41:53 2014
[Thr 4216] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 4216] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 6424
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 23788] Sat Mar 29 13:41:54 2014
[Thr 23788] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 23788] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 6844
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 6100] Sat Mar 29 13:41:55 2014
[Thr 6100] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 6100] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 39/sock 7448
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 6828] Sat Mar 29 13:41:56 2014
[Thr 6828] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 6828] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 32/sock 6216
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 644] Sat Mar 29 13:41:57 2014
[Thr 644] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 644] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 5992
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 7376] Sat Mar 29 13:41:58 2014
[Thr 7376] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 7376] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 6136
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 24096] Sat Mar 29 13:41:59 2014
[Thr 24096] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 24096] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 6004
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 24460] Sat Mar 29 13:42:00 2014
[Thr 24460] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 24460] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 6276
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 13452] Sat Mar 29 13:42:01 2014
[Thr 13452] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 13452] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 7328
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 17884] Sat Mar 29 13:42:03 2014
[Thr 17884] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 17884] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 7372
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 6616] Sat Mar 29 13:42:04 2014
[Thr 6616] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 6616] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 39/sock 7200
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 3136] Sat Mar 29 13:42:05 2014
[Thr 3136] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 3136] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 32/sock 6344
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 8284] Sat Mar 29 13:42:06 2014
[Thr 8284] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 8284] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 7380
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 19240] Sat Mar 29 13:42:07 2014
[Thr 19240] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 19240] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 6940
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 21316] Sat Mar 29 13:42:08 2014
[Thr 21316] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 21316] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 5988
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 22436] Sat Mar 29 13:42:09 2014
[Thr 22436] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 22436] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 7368
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 20936] Sat Mar 29 13:42:10 2014
[Thr 20936] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 20936] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 7528
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 18784] Sat Mar 29 13:42:11 2014
[Thr 18784] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 18784] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 4460
(SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp 3285]
[Thr 21320] Sat Mar 29 13:42:12 2014
[Thr 21320] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 21320] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 39/sock 6148
(SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp 3285]
[Thr 19632] Sat Mar 29 13:42:13 2014
[Thr 19632] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 19632] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 32/sock 5948
(SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp 3285]
[Thr 8684] Sat Mar 29 13:42:14 2014
[Thr 8684] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 8684] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 6012
(SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp 3285]
[Thr 7468] Sat Mar 29 13:42:15 2014
[Thr 7468] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 7468] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 6032
(SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp 3285]
[Thr 5588] Sat Mar 29 13:42:16 2014
[Thr 5588] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 5588] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 1032
(SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp 3285]
[Thr 2036] Sat Mar 29 13:42:17 2014
[Thr 2036] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 2036] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 6052
(SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp 3285]
[Thr 6692] Sat Mar 29 13:42:18 2014
[Thr 6692] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 6692] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 6188
(SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp 3285]
[Thr 5184] Sat Mar 29 13:42:19 2014
[Thr 5184] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 5184] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 6192
(SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp 3285]
[Thr 5604] Sat Mar 29 13:42:20 2014
[Thr 5604] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 5604] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 39/sock 6220
(SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp 3285]
[Thr 15996] Sat Mar 29 13:42:21 2014
[Thr 15996] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 15996] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 32/sock 6236
(SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp 3285]
[Thr 17680] Sat Mar 29 13:42:22 2014
[Thr 17680] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 6236
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 17680] Sat Mar 29 13:42:23 2014
[Thr 17680] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 6236
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 17680] Sat Mar 29 13:42:24 2014
[Thr 17680] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 6236
(SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp 3285]
[Thr 17680] Sat Mar 29 13:42:26 2014
[Thr 17680] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 6064
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 19856] Sat Mar 29 13:42:27 2014
[Thr 19856] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 19856] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 6184
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 24128] Sat Mar 29 13:42:28 2014
[Thr 24128] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 24128] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 6248
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 13684] Sat Mar 29 13:42:29 2014
[Thr 13684] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 13684] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 39/sock 6260
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 7384] Sat Mar 29 13:42:30 2014
[Thr 7384] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 7384] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 32/sock 6264
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 7432] Sat Mar 29 13:42:31 2014
[Thr 7432] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 7432] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 6292
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 6700] Sat Mar 29 13:42:32 2014
[Thr 6700] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 6700] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 6304
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 7272] Sat Mar 29 13:42:33 2014
[Thr 7272] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 7272] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 6340
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 19864] Sat Mar 29 13:42:34 2014
[Thr 19864] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 19864] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 6392
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 5608] Sat Mar 29 13:42:35 2014
[Thr 5608] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 5608] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 6404
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 7160] Sat Mar 29 13:42:36 2014
[Thr 7160] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 7160] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 6416
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 14536] Sat Mar 29 13:42:37 2014
[Thr 14536] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 14536] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 39/sock 7340
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 24404] Sat Mar 29 13:42:38 2014
[Thr 24404] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 24404] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 32/sock 6232
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 22756] Sat Mar 29 13:42:39 2014
[Thr 22756] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 22756] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 6076
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 6284] Sat Mar 29 13:42:40 2014
[Thr 6284] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 6284] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 7472
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 12696] Sat Mar 29 13:42:41 2014
[Thr 12696] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 12696] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 6380
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 24180] Sat Mar 29 13:42:42 2014
[Thr 24180] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 24180] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 6420
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 23444] Sat Mar 29 13:42:43 2014
[Thr 23444] JLaunchRequestFunc: receive command:17, argument:0 from pid:20668
[Thr 23444] JLaunchIShutdownInvoke: set shutdown interval (stop:1396080763/end:1396080883/TO:120)
[Thr 23444] JLaunchProcessCommand: Invoke VM Shutdown
[Thr 23444] JHVM_FrameworkShutdownDirect: invoke direct shutdown
[Thr 8780] JLaunchISetState: change state from [Running (3)] to [Waiting for stop (4)]
[Thr 8780] JLaunchISetState: change state from [Waiting for stop (4)] to [Stopping (5)]
[Thr 5188] JHVM_RegisterNatives: com.sap.bc.proj.jstartup.sadm.ShmCache
[Thr 7240] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 7240] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 6376
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 6536] Sat Mar 29 13:42:44 2014
[Thr 6536] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 6536] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 6852
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 18244] Sat Mar 29 13:42:46 2014
[Thr 18244] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 18244] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 39/sock 6348
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 17680] Sat Mar 29 13:42:47 2014
[Thr 17680] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 32/sock 6348
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
[Thr 17680] Sat Mar 29 13:42:48 2014
[Thr 17680] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 6348
(SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp 3285]
[Thr 22796] CCMS: closeMonitoringSegment(): inside static JMON Lib: nothing to do.
[Thr 8780] JLaunchISetState: change state from [Stopping (5)] to [Stopped (6)]
[Thr 17680] Sat Mar 29 13:42:49 2014
[Thr 17680] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 6348
(SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp 3285]
Heap
par new generation reserved 614400K, committed 614400K, used 313963K [0x000000007fff0000, 0x00000000a57f0000, 0x00000000a57f0000)
eden space 409600K, 60% used [0x000000007fff0000, 0x000000008f028658, 0x0000000098ff0000)
from space 102400K, 66% used [0x0000000098ff0000, 0x000000009d2528e8, 0x000000009f3f0000)
to space 102400K, 0% used [0x000000009f3f0000, 0x000000009f3f0000, 0x00000000a57f0000)
concurrent mark-sweep generation reserved 1482752K, committed 1482752K, used 0K [0x00000000a57f0000, 0x00000000ffff0000, 0x00000000ffff0000)
concurrent-mark-sweep perm gen reserved 524288K, committed 524288K, used 70349K [0x00000000ffff0000, 0x000000011fff0000, 0x000000011fff0000)
[Thr 18896] JLaunchIExitJava: exit hook is called (rc = 0)
[Thr 18896] JLaunchCloseProgram: good bye (exitcode = 0)
Regards
Jose H. -
New Solution Manager 7.0 Problem R3LOAD import Fail: table ARCH_NUM
While performing the import of LABA Step 18 in installing Solution Manager 7. Mostro the following message:
u201C/usr/sap/SOL/SYS/exe/run/R3load: END OF LOG: 20080730190555
/usr/sap/SOL/SYS/exe/run/R3load: START OF LOG: 20080730190557
/usr/sap/SOL/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/
R3ldmain.c#14 $ SAP
/usr/sap/SOL/SYS/exe/run/R3load: version R7.00/V1.4
Compiled Jan 23 2008 17:39:05
/usr/sap/SOL/SYS/exe/run/R3load -i ATAB.cmd -dbcodepage 4103 -l ATAB.log -stop_on_error
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
(DB) INFO: ATAB created #20080730190558
failed to read short nametab of table ARCH_NUM (rc=2)
(CNVPOOL) conversion failed for row 0 of table VARKEY = ââÒâÒâÒâÒâÒâÒâÒâÒâÒâÒâÒ
âÒâÒâÒâÒâÒâÒâÒâÒâÒâÒâÒâÒ
(CNV) ERROR: data conversion failed. rc = 2
(DB) INFO: disconnected from DB
/usr/sap/SOL/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/SOL/SYS/exe/run/R3load: END OF LOG: 20080730190558
Maybe anyone knowshow to solve it?
Thank you.Hi Gabriel Morleg,
Seems that you had some problem during the creation of table SAPUSER.
In order to fix the table, you will need to perform some activities directly on the database. Use SQLPlus. For the next instructions I will assume your system is called ABC and the DBSchema is called SR3.
from the operating system, start sqlplus:
sqlplus / as sysdba
check step 1:
> select count(1) from dba_users where username='OPS$ABCADM';
If the above command returns nothing, then:
> create user "OPS$ABCADM" default tablespace PSAPSR3USR temporary tablespace psaptemp identified externally;
> grant connect, resource, sapdba to "OPS$ABCADM";
check step 2:
> select owner from dba_tables where table_name = 'SAPUSER';
if the above command returns nothing, then:
> create table "OPS$ABCADM".SAPUSER (USERID VARCHAR2(256), PASSWD VARCHAR2(256));
check step 3:
>select * from "OPS$ABCADM".SAPUSER ;
if the above command returns nothing, then:
> insert into "OPS$ABCADM".SAPUSER values ('SAPSR3', 'manager');
> alter user sapsr3 identified by manager;
if the command of step 3 returns content and you want to redefine, then:
> truncate table "OPS$ABCADM".SAPUSER;
> insert into "OPS$ABCADM".SAPUSER values ('SAPSR3', 'manager');
check step 4:
> select count(*) from dba_users where username = 'OPS$ORAABC';
if the command above returns nothing, then:
> create user "OPS$ORAABC" default tablespace PSAPSR3USR temporary tablespace psaptemp identified externally;
> grant connect, resource,sapdba to "OPS$ORAABC";
check step 5:
> select owner from dba_tables where table_name = 'SAPUSER';
If the command above returns nothing, then:
> create table "OPS$ORAABC".SAPUSER (USERID VARCHAR2(256), PASSWD VARCHAR2(256));
check step 6:
> select * from "OPS$ORAABC".SAPUSER ;
if the command above returns nothing, then:
> insert into "OPS$ORAABC".SAPUSER values ('SAPSR3','manager');
if the command os step 6 returns content and you want to redefine them:
> truncate table "OPS$ORAABC".SAPUSER;
> insert into "OPS$ORAABC".SAPUSER values ('SAPSR3', 'manager');
This should be enough to overcome the ORA 1403 error.
Regards
Valdecir -
Create a Support Message in Production system showing up in Solution Manage
Has anyone setup the link between creating a support message (under help) in a production system (like ECC) and SAP's Solution Manager.
I understand that it uses BADI SBCOS001 with the interface method PREPARE_FEEDBACK_BO, but when I try to run it, it tells me that Customizing for feedback functionality missing. What functionality is missing? And how to I correct this? And how do I ensure it shows in SAP Solution Manager under a solution or project?
Thanks
PaulHi Paul
The only way is to use the IMG. I have just completed this via the IMG info. BUT, it is not that simple.
Make sure your RFC's are trusted and that you have SAP ALL during config.
I hope this will help:
Setup Service Desk
Steps to follow while configuring support desk.
1) Implement the note 903587 .
2) Create all the relevant RFC objects in the satellite system and add the appropriate logical components using transaction SMSY.
3) Check all the objects in the table BCOS_CUST using transaction SM30.
Appl : OSS_MSG
+ :W
DEST :BACK RFC NAME (for solution manager system keep this field as 'NONE')
+ :CUST 620
+ :1.0.
*4) Check whether the BC sets are activated or not using the transaction SCPR20.If the BC sets are not activated then implement the note 898614.The steps to activate the BC sets are described below
4.1) Activate SOLMAN40_SDESK_BASICFUNC_000 BC Set.
4.2) Activate this in expert mode with option u201COverwrite everythingu201D.
4.3) Activation of the following components has to be done by replicating the previous steps
3.1) SOLMAN40_SDESK_TPI_ACT_AST_001
3.2) SOLMAN40_SDESK_ACTIONLOG_001
3.3) SOLMAN40_SDESK_ACT_ADVCLOSE_001
3.4) SOLMAN40_SDESK_TEXTTYPES_001
*Depends upon the number of inactive BC set objects that we have after the upgrade.
4.4) if the actions mentioned in 4.3 are not listed while executing the transaction SCPR20, then implement the note 898614.In the source client 000 of the solution manager system create a transport request using transaction SE09, unpack the file 'PIECELIST_SERVICE_DESK_INIT.ZIP' from the attachment of the note. Copy the contents of the file 'PIECELIST_SERVICE_DESK_INITIAL.TXT' to the transport request. And activate the actions. Use transaction SCC1 to import the transport request to the solution manager client. If any short dump occurs during the activation, implement the note 939116.
5) Check whether the number range is set correctly. If not set the number ranges of basic notification (ABA) and the support desk message (Service transaction SLFN).To be able to use the same number ranges for both message types, the internal number range for basic notification (ABA) must correspond to the external number range for the support desk message.
Number ranges for ABA notifications
5.1) create an internal and external number range using transaction DNO_NOTIF.
5.2) assign number range intervals to groups internal and external.
5.3) SLF1 is the internal number range group
5.4) SLF2 and SLF3 is the external number range interval
5.5) Use transaction DNO_CUST01 to assign message categories to the number range.
5.51) Go to transaction DNO_CUST01
5.52) From the GOTO menu select the menu item DETAILS
5.53) Now you can assign the number range of basis notification (ABA) into the notification type.
The number range for ABA notification is 12 characters in length and to make it compatible with the CRM service transaction insert 2 ZEROES at the beginning.
Number ranges for Support Desk notification
5.54) Use transaction CRMC_NR_RA_SERVICE, and define the internal and external number ranges. Intervals must correspond to the intervals of the basic notifications (ABA notification).
5.6) Then assign both the external and internal numbering
5.61) Go to SPRO and then to SAP Solution Manager
5.62) Then select General Settings and then select Transaction types
5.63) Select the transaction type SLFN and then select the menu item DETAILS from the GOTO menu.
5.64) In the Transaction Numbering block, assign the internal and external number range. The Number Range object should be CRM_SERVIC.
5.7) To view the priorities use transaction DNO_CUST01 and select the notification type as SLF1 and then select priorities from the left pane of the screen. The priorities of the first four cannot be deleted, but new priorities can be added.
6) Check the Action profiles for ABA Notifications (Action profiles are used for synchronization of ABA notification with the CRM Service transaction).
6.1) To check the action profiles use the transaction SPPFCADM and select the application type DNO_NOTIF then select u2018DEFINE ACTION PROFILE AND ACTIONSu2019.
6.2) Select the item u2018SLFN0001_STANDARD_DNOu2019 and then from the menu GOTO, select the menu item DETAILS.
7) The Action profile u2018SLFN0001_STANDARD_DNOu2019 has to be assigned to the message category SLF1 (ABA notifications) using the transaction DNO_CUST01.
8) The action profile for the support desk message can be set to u2018SLFN0001_ADVANCEDu2019.
8.1) From SPRO select SAP Solution Manager then Scenario Specific Settings.
8.2) Select the item Service Desk and then to general settings.
8.3) Execute the category u2018Define Transaction Typesu2019.
8.4) Select the transaction type as SLFN
8.5) From the GOTO menu select the menu item u2018DETAILSu2019 and assign the action profile as SLFN0001_ADVANCED .
9) Activate the partner/ Organization
9.1) Go to CRM->MASTER DATA->BUSINESS PARTNER->INTEGRATION BUSINESS PARTNER ORGANIZATION MANAGEMENT->SET UP INTEGRATION WITH ORGANIZATIONAL MANAGEMENT.
9.2)Find the entries starting with HRALX
HRALX-HRAC WITH VALUE 'X'.
HRALX-OBPON WITH VALUE 'ON'.
HRALX-PBPON u2018ONu2019.
HRALX-MSGRE u2013 u20180u2019.
9.3) If entries are not found create it.
10) Generate Business partner screens
10.1) Go to transaction BUSP.
10.2) Execute the report with the following parameters
CLIENT - Client in which business partners should be created (solution manager client)
APPLICATION OBJECT-
SCREEN - *
Generate all/ selected screens - All screens.
delete sub screen containers -
11) implement SAP note 450640.
11.1) Go to transaction SA38 and select the report CRM_MKTBP_ZCACL_UPDATE_30.
11.2) Execute it with test mode box unchecked.
If a new relationship is to be created then steps 12 and 13 has to be followed
12) To create a relationship category
12.1) Go to transaction BUBA
12.2) Select the entry CRMH00: Undefined relationship
12.3) click on copy
12.4) Rename CRMH00 to ZCRMH00.
12.5) CREATE A RELATIONSHIP CATEGORY.
IN GENERAL DATA FILL LIKE ' FROM BP1 : HAS THE ACTIVITY GROUP '.
' FROM BP2 : IS A PART OF ATTUNE
13) Add the relationship category to the support team partner function
13.1)Use SPRO
IMG GUIDE->SAP SOLUTION MANAGER->SCENARIO SPECIFIC SETTINGS->
-> SERVICE DESK->PARTNER DETERMINATION PROCEDURE->DEFINE PARTNER FUNCTION.
13.2) FIND THE PARTNER FUNCTION SLFN0003 (SUPPORT TEAM).
13.3) In the field relation ship category, Select the newly created relationship category and save.
14) Steps 12 and 13 should be repeated for various business partner types like sold-to-party, message processors if new relationship is to be created for the respective business partner types.
15) Create a new access sequence for the support team determination
15.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Configuration ->
-> Scenario Specific Settings ->Service Desk -> Partner Determination Procedure ->
->Define Access Sequence
15.2) Click on New Entries
15.3) Define a new access sequence with sequence name as u2018Z001u2019 and description u2018NEW BP RELATIONSHIP ACTIVITY GROUPu2019
15.4) Create an new Individual Access with the following value:
u2022 Batch Seq: 10
u2022 Dialog Seq : 10
u2022 Source : Business Partner Relationship.
u2022 Detail on the source:
u2022 Partner Function : Reported By (CRM)
u2022 Mapping/restrictions
u2022 Flag Mapping/definition for partner being Searched
u2022 Partner Function in Source: Support Team (CRM).
Save it.
This Access Sequence will give us the Partner which has the relationship assigned
to the Support Team in the Reported By partner data.
16) Adapt the partner determination schema/Function
16.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Scenario Specific Settings ->Service Desk ->
-> Partner Determination Procedure -> Define Partner Determination Procedure.
16.2) The two options to adapt partner determination schema are
16.21) Adapt the standard Procedure (SLFN0001) or to create a new one by copying the standard one.
16.22) select the line starting with SLFN0001 or the newly created procedure.
16.23) Double Click on Partner Function in Procedure.
16.24) Select the Partner Function "Support Team", and click Details.
16.25) in the detail view only change the Partner Determination/access Sequence to
the one we've just created. Save your entry.
17) Create a root organizational model.
17.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration-> Scenario Specific Settings ->Service Desk -> Organizational Model ->Create a Root Unit for Your Organizational Structure.
17.2) creating an organizational unit by entering the data in the BASIC DATA tab.
17.3) enter the organizational unit, the description and save it.
18) Create the support team organization
18.1) go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Scenario Specific Settings ->Service Desk -> Create Organizational Objects in the Organizational Structure. Or use transaction (PPOMA_CRM).
19) Create the business Partners.
19. 1) Key users- End user (Business Partner General) ,Address should be specified.
19.2) go to the transaction BP.
19.3) create a new Person, Select the role: Business Partner (Gen).
For Identification of the key user
19.31) click on the identification tab
19.32) enter a line in the identification number formatted as follows
IDTYPE : CRM001.
Identification number : <SID><INSTALL NUMBERS><CLIENT><USERNAME>
eg: USER NAME : USER1.
CLIENT : 100.
SID : ER1.
INSTALL NUMBER : 123456789.
IDENTIFICATION NUMBER : ER1 123456789 100 USER1.
20) Message Processors- Support Team members .
20.1) they should be created first as the users in the corresponding client of the solution manager.
20.2) As business partners they will have the role 'EMPLOYEE'.
20.3) Go to transaction BP .
20.4) Create New Person with the role employee.
20.5) In the Identification tab you should enter the user name in the employee data/User Name.
eg: username: proc1
enter proc1 in the field User name.
21) Organizational Business Partner- Organizational BPS have the same country in there main address tab. They should be created through the organizational model. Business partner corresponding to the root organization have the role 'SOLD TO PARTY'.
22) Assign the business partners (Message Processors) to the previously created support team.
22.1) Go to transaction PPOMA_CRM.
22.2) Select the support team 1.
22.3) Click on create
22.4) select position
22.5) call it 'MPROC_T1/Message Processors for team 1
22.6) Replicate it for the other support teams.
22.7) Select the position MPROC_T1/Message Processors for team1 and click assign,
choose owner/Business Partner find and select the business partner
22.8) Validate and Save it.
22.9) If the assignment of business partner is not possible then implement the note 1008656
Or 997009
23) Create the iBase component
23.1) IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings -> Standard Configuration of Basic Settings -> Solution Manager -> iBase -> Initially Create and Assign the Component Systems as iBase Components.
23.2) or use the transaction IB51 to create the installed base.
23.3) it is also possible to create the SOLUTION_MANAGER, select the solution and go to menu Edit -> Initial Data Transfer for iBase.
24)Assign Business Partners to iBase Components
IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings
-> SAP Solution Manager System ->ServiceDesk-> iBase -> Assign Business Partners to iBase Components.
*--optional--
If you want to be able to assign the System Administrator: Go to the IMG: SAP Solution Manager Implementation Guide -> Customer Relationship Management -> Basic Function -> Partner Processing -> Define Partner Determination Procedure.
Select the entry "00000032 Installed Base/IBase" and double click on Partner Functions in Procedure.
Then copy the Entry "Contact Person (CRM)" to a new entry with the partner Function "System Administrator (CRM)" , save it.
Go back to transaction IB52, select a component, and Goto -> Partner, you should be able
now to assign the partner Function "System Administrator".
25) Assign the SAP Standard Role to the user. Message Creator should have the role : SAP_SUPPDESK_PROCESS.
26)Define the transaction variant for the message processors
Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration -> Scenario Specific Settings ->Service Desk -> General Settings -> Specify User Selection Variant.
Here we will create variants for the central message processing transaction CRM_DNO_MONITOR.so that the user will have direct access to there dedicated message.
27) Go to transaction PFCG
27.1) Enter the role name as Z_MSG_PROCESSORS and choose single role.
27.2) Give a description Message Processor role and save it.
27.3) Go to the menu tab and choose add report
27.4) select the report type : ABAP Report
27.5) And in the report enter the report name as 'CRM_DNO_SERVICE_MONITOR'.
27.6) Enter the previously created variant.
27.7) flag the skip initial screen box.
27.8) flag the SAPGUI for windows.
27.9) Create a new transaction with tcode starting with Y or Z.
27.10)Display this transaction and check the values at the bottom of the screen
in the subscreen Default Values, you should have the following parameters:
u2022 D_SREPOVARI-REPORT = CRM_DNO_SERVICE_MONITOR
u2022 D_SREPOVARI-VARIANT = MY_TEAM_MSG
u2022 D_SREPOVARI-NOSELSCRN = X
And also all the user should have the correct role. -
Define Service Desk Destination in the Solution Manager System (Dump creen)
hi,
in SPRO when i click on Define Service Desk Destination in the Solution Manager System
i got dump screen with the error below
any help?
Runtime Errors SAPSQL_EMPTY_TABNAME
Except. CX_SY_DYNAMIC_OSQL_SYNTAX
Date and Time 13.07.2008 14:05:57
Short text
A dynamically specified FROM clause has an unexpected format.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSHI2" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_DYNAMIC_OSQL_SYNTAX', was not
caught in
procedure "STREE_READ_NODE_GENER" "(FUNCTION)", nor was it propagated by a
RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
The running ABAP program attempted to execute an Open SQL statement in
which a FROM clause was specified dynamically in the field "TABLE_NAME". In
this
FROM clause, either a table name after a join operator is missing, or an
alias name after the key name "AS". The field "TABLE_NAME" could be empty as
well.
regardsHi,
I am facing the same problem. What is SP15 ?
Is there any SAP Note that can be applied to correct this ?
Thanks. -
Unable to create tickt in service desk - Solution manage.
Hello,
I have implemented service desk ( Solution manager) and It is working fine for most of the system but i am getting error while creating a ticket in service desk for one system.
Due to some RFC connection problem i have regenerated the RFC ( trusted , Read and TMW) from Solman to Satellite system.
and now I am not bale to create ticket for that system.
Error message :
The URL http://cismp.cargotec.com:8014/sap/bc/bsp/sap/dswpnotifcreate/msg_new.do was not called due to an error.
Note
The following error text was processed in the system SMP : Error SYSTEM_CORE_DUMPED occured. P1=11
The error occurred on the application server cismp_SMP_14 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: MSG_SUBMIT of program CL_DSMOP_BSP_NOTI_MODEL=======CP
Method: DO_HANDLE_EVENT of program CL_DSMOP_BSP_NOTI_CTRL========CP
Method: DISPATCH_INPUT of program CL_BSP_CONTROLLER2============CP
Method: DO_REQUEST of program CL_DSMOP_BSP_NOTI_CTRL========CP
Method: DO_REQUEST of program CL_BSP_CTRL_ADAPTER===========CP
Method: ON_REQUEST of program CL_BSP_RUNTIME================CP
Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_HTTP_EXT_BSP===============CP
Method: EXECUTE_REQUEST_FROM_MEMORY of program CL_HTTP_SERVER================CP
Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME
Module: %_HTTP_START of program SAPMHTTP
Can any body guide me what should be done to resolve the issue.Hi Prakhar,
As i mentioned workcenter is working fine for all other systems. and user have all roles same as in other systems.
BP is created and we are trying to create ticket from Solman itself so there is no point to maintain bCOS_CUST table.
but still we are not able to create ticket only for one system.
Error Message :
Error when processing your request
What has happened?
The URL http://cismp.cargotec.com:8014/sap/bc/bsp/sap/dswpnotifcreate/msg_new.do was not called due to an error.
Note
The following error text was processed in the system SMP : Error SYSTEM_CORE_DUMPED occured. P1=11
The error occurred on the application server cismp_SMP_14 and in the work process 1 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: MSG_SUBMIT of program CL_DSMOP_BSP_NOTI_MODEL=======CP
Method: DO_HANDLE_EVENT of program CL_DSMOP_BSP_NOTI_CTRL========CP
Method: DISPATCH_INPUT of program CL_BSP_CONTROLLER2============CP
Method: DO_REQUEST of program CL_DSMOP_BSP_NOTI_CTRL========CP
Method: DO_REQUEST of program CL_BSP_CTRL_ADAPTER===========CP
Method: ON_REQUEST of program CL_BSP_RUNTIME================CP
Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_HTTP_EXT_BSP===============CP
Method: EXECUTE_REQUEST_FROM_MEMORY of program CL_HTTP_SERVER================CP
Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME
Module: %_HTTP_START of program SAPMHTTP
What can I do?
If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system SMP in transaction ST22.
If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server cismp_SMP_14 in transaction SM21.
If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 1 in transaction ST11 on the application server cismp_SMP_14 . In some situations, you may also need to analyze the trace files of other work processes.
If you do not yet have a user ID, contact your system administrator.
Error code: ICF-IE-http -c: 011 -u: XABHYABH -l: E -s: SMP -i: cismp_SMP_14 -w: 1 -d: 20091006 -t: 141511 -v: RABAX_STATE -e: SYSTEM_CORE_DUMPED
Regards,
Bhavesh -
Setting up EarlyWatch in Solution manager
Hi Guys
I am trying to configure Early Watch in solution manager(System Id u2013SOL , Installation No - 0020306432) for an satellite system (System Id -DEV u2013Installation No : 0020181089).
I have followed all the configuration steps listed below :
1. Configuration RFCs to market place SAPOSS and to satellite Systems and RFC Back to solution manager. All RFC like SAPOSS and Back has been tested from SDCCN (Solution manager and satellite system)
2. Configured SDCCN in solution manager and in satellite system except u201CGenerate Includes for Service data control centeru201D in SPRO of solution manager as this process is getting time out and not letting us to generate all the includes
3. Activated Service data Control center locally and assign solution manager as u2018Master system for allu2019.
4. Activated SDCCN in satellite system(DEV) ,Created Earlywatch Service in Solution manager for DEV system and also created/Started u2018Refresh Sessionu2019 in SDCCN of DEV(Satellite system)
5. This successfully shows me Early watch link in u2018Waitingu2019 Status in solution manager.
6. I click on u2018Start Service Processingu2019 to Schedule/Run u201CSM:EXEC SERVICESu201D background job .
Problem : Background job u201CSM:EXEC SERVICESu201D get cancelled after some time and throws a Dump which is pasted below.
Dump shows that an include u2018/1CAGTF/IF_LOGFUNC_000393u2019 is missing which should have been generated while activating the includes for SDCCN in SPRO of solution manager.
I found includes from u2018/1CAGTF/IF_LOGFUNC_000001u2019 to u2018/1CAGTF/IF_LOGFUNC_000353u2019 in the system as it seems that not all include have been generated .
*Could you please help me to provide some SAP note so that I would be able to generate all the includes . *
DUMP
Runtime Errors SYNTAX_ERROR
Date and Time 24.05.2008 00:01:02
Short text
Syntax error in program "RDSVASAEW_ROOT_____________073 ".
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "RDSVASAEW_ROOT_____________073
" in include "RDSVASAEW_ROOT_____________073 " in
line 96:
"INCLUDE report "/1CAGTF/IF_LOGFUNC_000393" not found."
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
What can you do?
Please eliminate the error by performing a syntax check
(or an extended program check) on the program "RDSVASAEW_ROOT_____________073
You can also perform the syntax check from the ABAP Editor.
If the problem persists, proceed as follows:
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
The following syntax error was found in the program
RDSVASAEW_ROOT_____________073 :
"INCLUDE report "/1CAGTF/IF_LOGFUNC_000393" not found."
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "mslsol"
Network address...... "192.168.193.154"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "2x Intel 801586"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 10
Shortdump setting.... "full"
Database server... "MSLSOL"
Database type..... "ORACLE"
Database name..... "SOL"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Aug 29 2006 00:18:21"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "OCI_10201_SHARE (10.2.0.2.0) "
Patch level. 75
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory consumption
Roll.... 8176
EM...... 29266272
Heap.... 0
Page.... 24576
MM Used. 24845128
MM Free. 236264
User and Transaction
Client.............. 600
User................ "BASISA"
Language key........ "E"
Transaction......... " "
Program............. "SAPLDSVAS_PROC"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "SAPLDSVAS_PROC" - in "EXECUTE".
The main program was "RDSMOPBACK_AUTOSESSIONS ".
In the source code you have the termination point in line 2146
of the (Include) program "LDSVAS_PROCCD0".
The program "SAPLDSVAS_PROC" was started as a background job.
Job Name....... "SM:EXEC SERVICES"
Job Initiator.. "BASISA"
Job Number..... 00384300
Source Code Extract
Line
SourceCde
2116
ls_stdparameter-versnr = po_ctnode->versnr.
2117
ls_stdparameter-grp = po_ctnode->grp.
2118
ls_stdparameter-id = po_ctnode->id.
2119
ls_stdparameter-reference_versnr = po_ctnode->reference_versnr.
2120
ls_stdparameter-reference_grp = po_ctnode->reference_grp.
2121
ls_stdparameter-reference_id = po_ctnode->reference_id.
2122
else.
2123
ls_stdparameter-grp = pf_grp.
2124
ls_stdparameter-versnr = pf_versnr.
2125
ls_stdparameter-reference_grp = pf_grp.
2126
ls_stdparameter-reference_versnr = pf_versnr.
2127
endif.
2128
2129
Formroutinen aufrufen
2130
loop at actseq
2131
into ls_actrel
2132
where exec_time = pf_exec_time.
2133
check ls_actrel-exec_time ne gf_exec_time_event
2134
or ( ls_actrel-exec_time = gf_exec_time_event and
2135
ls_actrel-event = pf_event ).
2136
call function 'DSVAS_CDMNT_FORM_NAME'
2137
exporting
2138
pf_container_type = 'A'
2139
pf_form_number = ls_actrel-action
2140
importing
2141
pf_form_name = lf_form_name.
2142
perform (lf_form_name)
2143
in program (program)
2144
using ls_stdparameter
2145
if found.
>>>>>
endloop.
2147
endmethod. "execute
2148
2149
Collect_Known_Events
2150
method collect_known_events.
2151
data: ls_actseq type line of ltype_action_sequence_table,
2152
lf_event type dsvasactseq-event.
2153
2154
loop at actseq into ls_actseq
2155
where ( exec_time = gf_exec_time_event and
2156
event ne space )
2157
or exec_time = gf_exec_time_1
2158
or exec_time = gf_exec_time_2
2159
or exec_time = gf_exec_time_3
2160
or exec_time = gf_exec_time_modus_close.
2161
if ls_actseq-exec_time = gf_exec_time_event.
2162
read table pt_events with table key table_line = ls_actseq-event
2163
transporting no fields.
2164
if sy-subrc ne 0.
2165
insert ls_actseq-event into table pt_events.
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
1
SY-TABIX
1
SY-DBCNT
0
SY-FDPOS
30
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
DSWP: Execute rule set
SY-MSGTY
E
SY-MSGID
FL
SY-MSGNO
046
SY-MSGV1
DSVAS_TOOLS_PACKAGE_GET
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080524
SY-UZEIT
000049
SY-XPROG
SAPCNVE
SY-XFORM
CONVERSION_EXIT
Active Calls/Events
No. Ty. Program Include Line
Name
11 FORM SAPLDSVAS_PROC LDSVAS_PROCCD0 2146
EXECUTE
10 METHOD SAPLDSVAS_PROC LDSVAS_PROCCD0 2142
LCL_ACTION_SEQUENCE=>EXECUTE
9 METHOD SAPLDSVAS_PROC LDSVAS_PROCCTI 1741
LCL_CHECK_TREENODE=>EXECUTE
8 METHOD SAPLDSVAS_PROC LDSVAS_PROCCTI 1792
LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE
7 METHOD SAPLDSVAS_PROC LDSVAS_PROCCTI 1806
LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE
6 METHOD SAPLDSVAS_PROC LDSVAS_PROCSEI 2025
LCL_SESSION=>EXECUTE
5 METHOD SAPLDSVAS_PROC LDSVAS_PROCSEI 1582
LCL_SESSION=>CONTEXT_INSTANCES_CREATE
4 METHOD SAPLDSVAS_PROC LDSVAS_PROCSEI 1995
LCL_SESSION=>EXECUTE
3 FUNCTION SAPLDSVAS_PROC LDSVAS_PROCU02 303
DSVAS_PROC_SESSION_OPEN
2 METHOD CL_DSMOP_SOLUTION=============CP CL_DSMOP_SOLUTION=============CM01P 184
CL_DSMOP_SOLUTION=>START_PERIODIC_SERVICES
1 EVENT RDSMOPBACK_AUTOSESSIONS RDSMOPBACK_AUTOSESSIONS 72
START-OF-SELECTION
Chosen variables
Name
Val.
No. 11 Ty. FORM
Name EXECUTE
PF_EXEC_TIME
I
4
9
0
0
PF_EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
PO_CTNODE
|
| 2000D000 |
| E0001C00 |
| PF_GRP |
| |
| 22222222222222222222 |
| 00000000000000000000 |
| 00000000000000000000 |
| 00000000000000000000 |
| PF_VERSNR |
| 00000 |
| 33333 |
| 00000 |
| 00000 |
| 00000 |
| <%_L02E>-EXEC_TIME |
| ??? |
| ?????? |
| ?????? |
| <%_L02F> |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| LS_ACTREL-EXEC_TIME |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| GF_EXEC_TIME_EVENT |
| E |
| 4 |
| 5 |
| 0 |
| 0 |
| SYST-REPID |
| SAPLDSVAS_PROC |
| 5454455455554422222222222222222222222222 |
| 310C43613F02F300000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| LS_ACTREL-EVENT |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| SY-SAPRL+0(4) |
| 70 |
| 33 |
| 70 |
| 00 |
| 00 |
| LS_ACTREL-ACTION |
| 108 |
| 333 |
| 108 |
| 000 |
| 000 |
| LF_FORM_NAME |
| ACTION_108 |
| 44544453332222222222222222222222 |
| 1349FEF1080000000000000000000000 |
| 00000000000000000000000000000000 |
| 00000000000000000000000000000000 |
| ME->PROGRAM |
| RDSVASAEW_ROOT_____________073 |
| 5455454455544555555555555553332222222222 |
| 243613157F2FF4FFFFFFFFFFFFF0730000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| %_DUMMY$$ |
| |
| 2222 |
| 0000 |
| 0000 |
| 0000 |
| LS_STDPARAMETER |
| EA6000000000255###ESESSION 00047EA_ROOT |
| 4433333333333330004545544422222222222222222222222222222222222222222223333344554452222222222222 |
| 516000000000255010535339FE00000000000000000000000000000000000000000000004751F2FF40000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| No. 10 Ty. METHOD |
| Name LCL_ACTION_SEQUENCE=>EXECUTE |
| PF_EXEC_TIME |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| PF_EVENT |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| PO_CTNODE |
|
2000D000
E0001C00
PF_GRP
22222222222222222222
00000000000000000000
00000000000000000000
00000000000000000000
PF_VERSNR
00000
33333
00000
00000
00000
<%_L02E>-EXEC_TIME
<%_L02F>
I
4
9
0
0
LS_ACTREL-EXEC_TIME
I
4
9
0
0
LS_ACTREL-EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LS_ACTREL-ACTION
108
333
108
000
000
LF_FORM_NAME
ACTION_108
44544453332222222222222222222222
1349FEF1080000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
ME->PROGRAM
RDSVASAEW_ROOT_____________073
5455454455544555555555555553332222222222
243613157F2FF4FFFFFFFFFFFFF0730000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LS_STDPARAMETER
EA6000000000255###ESESSION 00047EA_ROOT
4433333333333330004545544422222222222222222222222222222222222222222223333344554452222222222222
516000000000255010535339FE00000000000000000000000000000000000000000000004751F2FF40000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No. 9 Ty. METHOD
Name LCL_CHECK_TREENODE=>EXECUTE
PF_EXEC_TIME
I
4
9
0
0
PF_EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
GF_EXEC_TIME_ATTRIBUTES
a
6
1
0
0
RSJOBINFO
00000000000000 ##
2222222222222222222222222222222233333333333333222222222222222222222222222222222200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
ME
|
| 2000D000 |
| E0001C00 |
| GT_OPEN_SESSIONS |
| Table IT_3668[1x44] |
| FUNCTION-POOL=DSVAS_PROCDATA=GT_OPEN_SESSIONS |
| Table reference: 1911 |
| TABH+ 0(20) = 807E0D3E000000000000000077070000540E0000 |
| TABH+ 20(20) = 010000002C000000FFFFFFFF0417010010040000 |
| TABH+ 40( 8) = 10000000A4318001 |
| store = 0x807E0D3E |
| ext1 = 0x00000000 |
| shmId = 0 (0x00000000) |
| id = 1911 (0x77070000) |
| label = 3668 (0x540E0000) |
| fill = 1 (0x01000000) |
| leng = 44 (0x2C000000) |
| loop = -1 (0xFFFFFFFF) |
| xtyp = TYPE#000007 |
| occu = 16 (0x10000000) |
| access = 4 (ItAccessHashed) |
| idxKind = 0 (ItIndexNone) |
| uniKind = 1 (ItUnique) |
| keyKind = 3 (user defined) |
| cmpMode = 8 (cmpManyEq) |
| occu0 = 1 |
| groupCntl = 0 |
| rfc = 0 |
| unShareable = 0 |
| mightBeShared = 0 |
| sharedWithShmTab = 0 |
| isShmLockId = 0 |
| gcKind = 0 |
| isUsed = 1 |
| isCtfyAble = 1 |
| >>>>> Shareable Table Header Data <<<<< |
| tabi = 0xC0AB0D3E |
| pgHook = 0x00000000 |
| idxPtr = 0x78F10D3E |
| shmTabhSet = 0x00000000 |
| id = 2504 (0xC8090000) |
| refCount = 0 (0x00000000) |
| tstRefCount = 0 (0x00000000) |
| lineAdmin = 16 (0x10000000) |
| lineAlloc = 16 (0x10000000) |
| shmVersId = 0 (0x00000000) |
| shmRefCount = 1 (0x01000000) |
| >>>>> 1st level extension part <<<<< |
| regHook = Not allocated |
| collHook = Not allocated |
| ext2 = Not allocated |
| >>>>> 2nd level extension part <<<<< |
| tabhBack = Not allocated |
| delta_head = Not allocated |
| pb_func = Not allocated |
| pb_handle = Not allocated |
| GF_EXEC_TIME_BEFORE_REPORT_GEN |
| R |
| 5 |
| 2 |
| 0 |
| 0 |
| GF_EXEC_TIME_INIT |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| ME->INITIALIZED |
| |
| 2 |
| 0 |
| 0 |
| 0 |
| GF_EXEC_TIME_AFTER |
| A |
| 4 |
| 1 |
| 0 |
| 0 |
| ME->ACTSEQ |
|
2000D000
C0003C00
SCREEN
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ME->HAS_TABLES
X
5
8
0
0
SYST
##########################A###P##############################################T###ÿ##### u####
0000000000000000000000100040005000000050000000007000000000000000000000000000105000F00050270000
1000101000001000000000E010101000000000C0000000004000000000000000000000000000604000F00080050600
0000000000000000000000000000000000000000000000001000000000000000000000000000000000000040000000
00000000000000000000000000000000000000000000000070000000000000000000000000000000000000D000000C
SY-REPID
SAPLDSVAS_PROC
5454455455554422222222222222222222222222
310C43613F02F300000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->CHECK_TABLES
|
| 2000D000 |
| 3000CC00 |
| No. 8 Ty. METHOD |
| Name LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE |
| PF_EXEC_TIME |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| PF_EVENT |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| PF_CON |
| SESSION |
| 5455444222 |
| 35339FE000 |
| 0000000000 |
| 0000000000 |
| PF_INS |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| ME->DYNAMIC |
| X |
| 5 |
| 8 |
| 0 |
| 0 |
| ME |
|
2000D000
E0001C00
GF_SESSION_DEF_TYPE_MORE_DEV
L
4
C
0
0
ME->ACTIVE
X
5
8
0
0
GF_SESSION_DEF_TYPE_VERSION
V
5
6
0
0
ME->CON
SESSION
5455444222
35339FE000
0000000000
0000000000
ME->INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->CHILD_CONDSEQ
F0000000
F0000000
GF_CONTEXT_SESSION
SESSION
5455444222
35339FE000
0000000000
0000000000
ME->CHILDREN
Table[initial]
LO_TNODE
|
| F0000000 |
| F0000000 |
| %_ARCHIVE |
| |
| 2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| No. 7 Ty. METHOD |
| Name LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE |
| PF_EXEC_TIME |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| PF_EVENT |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| PF_CON |
| SESSION |
| 5455444222 |
| 35339FE000 |
| 0000000000 |
| 0000000000 |
| PF_INS |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| ME |
|
2000D000
F0000C00
ME->CHILD_CONDSEQ
|
| F0000000 |
| F0000000 |
| ME->CHILDREN |
| Table IT_3674[26x8] |
| DATA=CHILDREN
Table reference: 1919
TABH+ 0(20) = 68550D3E00000000000000007F0700005A0E0000
TABH+ 20(20) = 1A00000008000000800100000417010030080000
TABH+ 40( 8) = 10000000C1288001
store = 0x68550D3E
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 1919 (0x7F070000)
label = 3674 (0x5A0E0000)
fill = 26 (0x1A000000)
leng = 8 (0x08000000)
loop = 384 (0x80010000)
xtyp = TYPE#000029
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 4 (cmpSingleEq)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0xB0B10D3E
pgHook = 0xF0882E3E
idxPtr = 0x00000000
shmTabhSet = 0x00000000
id = 2508 (0xCC090000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 48 (0x30000000)
lineAlloc = 48 (0x30000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
LO_TNODE
|
| 2000D000 |
| E0001C00 |
| LO_CTNODE |
|
2000D000
E0001C00
%_SPACE
2
0
0
0
No. 6 Ty. METHOD
Name LCL_SESSION=>EXECUTE
PF_EXEC_TIME
I
4
9
0
0
PF_EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
PF_CON
SESSION
5455444222
35339FE000
0000000000
0000000000
PF_INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->ACTSEQ
|
| F0000000 |
| F0000000 |
| ME->GLOBAL_CHECK_GRP |
| EA_ROOT |
| 44554452222222222222 |
| 51F2FF40000000000000 |
| 00000000000000000000 |
| 00000000000000000000 |
| ME->GLOBAL_VERSNR |
| 00047 |
| 33333 |
| 00047 |
| 00000 |
| 00000 |
| ME->CHECK_TREE |
|
2000D000
F0000C00
GF_EXEC_TIME_MODUS_CLOSE
W
5
7
0
0
ME->RAISED_EVENTS
Table[initial]
GF_EXEC_TIME_LOGICAL_COMPLETE
L
4
C
0
0
No. 5 Ty. METHOD
Name LCL_SESSION=>CONTEXT_INSTANCES_CREATE
LT_ZOMBIES
Table[initial]
LS_CTREL-TREENODE
F0000000
F0000000
LO_ZOMBIE
|
| F0000000 |
| F0000000 |
| LT_NEW_CONINS |
| Table IT_3670[1x100] |
| FUNCTION-POOL=DSVAS_PROCCLASS=LCL_SESSIONMETHOD=CONTEXT_INSTANCES_CREATEDATA=LT_NEW_CONINS |
| Table reference: 1920 |
| TABH+ 0(20) = 90C50D3E30F3DE3D0000000080070000560E0000 |
| TABH+ 20(20) = 0100000064000000080100000417010060140000 |
| TABH+ 40( 8) = 01000000C1248401 |
| store = 0x90C50D3E |
| ext1 = 0x30F3DE3D |
| shmId = 0 (0x00000000) |
| id = 1920 (0x80070000) |
| label = 3670 (0x560E0000) |
| fill = 1 (0x01000000) |
| leng = 100 (0x64000000) |
| loop = 264 (0x08010000) |
| xtyp = TYPE#000094 |
| occu = 1 (0x01000000) |
| access = 1 (ItAccessStandard) |
| idxKind = 0 (ItIndexNone) |
| uniKind = 2 (ItUniqueNon) |
| keyKind = 1 (default) |
| cmpMode = 2 (cmpSingleMcmpR) |
| occu0 = 1 |
| groupCntl = 0 |
| rfc = 0 |
| unShareable = 0 |
| mightBeShared = 1 |
| sharedWithShmTab = 0 |
| isShmLockId = 0 |
| gcKind = 0 |
| isUsed = 1 |
| isCtfyAble = 1 |
| >>>>> Shareable Table Header Data <<<<< |
| tabi = 0x08AB0D3E |
| pgHook = 0x00000000 |
| idxPtr = 0x00000000 |
| shmTabhSet = 0x00000000 |
| id = 2505 (0xC9090000) |
| refCount = 0 (0x00000000) |
| tstRefCount = 0 (0x00000000) |
| lineAdmin = 1 (0x01000000) |
| lineAlloc = 1 (0x01000000) |
| shmVersId = 0 (0x00000000) |
| shmRefCount = 1 (0x01000000) |
| >>>>> 1st level extension part <<<<< |
| regHook = 0xB0F0BE3D |
| collHook = 0x00000000 |
| ext2 = 0x00000000 |
| >>>>> 2nd level extension part <<<<< |
| tabhBack = Not allocated |
| delta_head = Not allocated |
| pb_func = Not allocated |
| pb_handle = Not allocated |
| <LFS_CONINS> |
| SESSION |
| 54554442222222222222222222222222222222222222222222 |
| 35339FE0000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| ME |
|
90006000
4000B000
<LFS_CONINS>-CON
SESSION
5455444222
35339FE000
0000000000
0000000000
<LFS_CONINS>-INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SY
##########################A###P##############################################T###ÿ##### u####
0000000000000000000000100040005000000050000000007000000000000000000000000000105000F00050270000
1000101000001000000000E010101000000000C0000000004000000000000000000000000000604000F00080050600
0000000000000000000000000000000000000000000000001000000000000000000000000000000000000040000000
00000000000000000000000000000000000000000000000070000000000000000000000000000000000000D000000C
GF_EXEC_TIME_BEFORE
B
4
2
0
0
No. 4 Ty. METHOD
Name LCL_SESSION=>EXECUTE
PF_EXEC_TIME
I
4
9
0
0
PF_EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
PF_CON
2222222222
0000000000
0000000000
0000000000
PF_INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->ACTSEQ
|
| F0000000 |
| F0000000 |
| ME |
|
90006000
4000B000
ME->LOGICAL_COMPLETE
2
0
0
0
GF_EXEC_TIME_COMPLETE
C
4
3
0
0
ME->COMPLETE
2
0
0
0
SY-XFORM
CONVERSION_EXIT
444545544454545222222222222222
3FE65239FEF5894000000000000000
000000000000000000000000000000
000000000000000000000000000000
No. 3 Ty. FUNCTION
Name DSVAS_PROC_SESSION_OPEN
PF_HANDLE_TO_USE
0
0000
0000
PF_MAX_TREE
2
0
0
0
PF_MODE
C
4
3
0
0
PS_SESSION_NUMBER
EA6000000000255
443333333333333
516000000000255
000000000000000
000000000000000
PF_HANDLE
1
0000
1000
PF_HIDE_TREE
2
0
0
0
PF_MODE_USED
2
0
0
0
PF_NEXT_CHECK_GRP
22222222222222222222
00000000000000000000
00000000000000000000
00000000000000000000
PF_NEXT_CHECK_ID
00000
33333
00000
00000
00000
PF_NEXT_CON
2222222222
0000000000
0000000000
0000000000
PF_NEXT_INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
PT_ERRORS
Table[initial]
PT_FRONTEND_TREE[]
Table[initial]
PF_LANGUAGE
E
4
5
0
0
<%_TABLE_DSVASSESSADMIN>
LF_BUNDLE_VERSNR
00038
33333
00038
00000
00000
DSVASRESULTSGEN-CLUSTR
0
00
00
PS_SESSION_NUMBER-SESSNO
6000000000255
3333333333333
6000000000255
0000000000000
0000000000000
LS_OPEN_SESSIONS-SESSION
|
| 90006000 |
| 4000B000 |
| LO_SESSION |
|
90006000
4000B000
LS_OPEN_SESSIONS
EA6000000000255C####k#
4433333333333334009060
51600000000025531040B0
0000000000000000000000
0000000000000000000000
SY-XPROG
SAPCNVE
5454454222222222222222222222222222222222
3103E65000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LS_SESSDEFGEN-MULTI_USERPlease replace the Service Definitions in your SAP Solution Manager
system as described in SAP Note 727998.
As of SAP Solution Manager 7.0 (= 4.0) Support Package Stack 15 (which
includes ST-PI 700_2005_1 SP06) you can trigger the required steps
within transaction SDCCN:
Menu Utilities -> Maintain Service Definitions ->
Select 'Delete and Replace Service Definitions -> Confirm this
selection-> Confirm that you want to delete the definitions -> Confirm
that a new task 'Service Definition Refresh' was created
Take a note of the task id -> Review the log for this task id when it
is completed. You should not see any errors for either the update
of a Service Definitions table or the generation of any re-import
include.
Reschedule SM:EXEC SERVICES and the reported dump will no longer
occur. -
Error while installing solution manager 7.1
Hi All,
I am installing SAP Solution Manager 7.1 SR1 i am facing below issue ,any one please suggest me how to proceed further.I am new to sybase .
An error occurred while processing option SAP Solution Manager 7.1 Support Release 1 > SAP Systems > SAP ASE > Central System > Central System( Last error reported by the step: Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.). You can now:
Choose Retry to repeat the current step.
Choose Log Files to get more information about the error.
Stop the option and continue with it later.
Log files are written to C:\Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS.
import_monitor.java log:
java version "1.4.2_32"
Java(TM) 2 Runtime Environment, Standard Edition (build 4.1.016)
SAP Java Server VM (build 4.1.016 1.6-b03, Dec 31 2011 00:41:53 - 41_REL - optU - windows amd64 - 6 - bas2:164914 (mixed mode))
Import Monitor jobs: running 1, waiting 28, completed 0, failed 0, total 29.
Loading of 'SAPNTAB' import package: ERROR
Import Monitor jobs: running 0, waiting 28, completed 0, failed 1, total 29.
import_monitor Log:
INFO: 2014-07-01 10:49:48
Import Monitor is started.
CONFIG: 2014-07-01 10:49:48
Application options:
dbCodepage=4103
dbType=SYB
extFiles=no
importDirs=D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_1\DATA_UNITS\EXP1;D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_1\DATA_UNITS\EXP2;D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP3;D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4
installDir=C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS
jobNum=8
loadArgs=-c 99000000 -loadprocedure fast
monitorTimeout=30
orderBy=
r3loadExe=D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe
sapinst=
trace=all
tskFiles=yes
CONFIG: 2014-07-01 10:49:48
List of packages with table structure: 'SAP0000'.
CONFIG: 2014-07-01 10:49:48
List of packages with views: 'SAPVIEW'.
TRACE: 2014-07-01 10:49:48 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS\DDLSYB.TPL' template file is started.
INFO: 2014-07-01 10:49:48 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS\DDLSYB.TPL' template file is successfully completed.
Primary key creation: after load.
Index creation: after load.
INFO: 2014-07-01 10:49:48
Data codepage 1100 is determined using TOC file 'D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_1\DATA_UNITS\EXP1\DATA\SAPSSEXC.TOC' for package 'SAPSSEXC'.
INFO: 2014-07-01 10:49:48
Version table 'SVERS' is found in STR file 'D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DATA\SAPNTAB.STR' from package 'SAPNTAB'.
INFO: 2014-07-01 10:49:48
Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DATA\SAPNTAB.STR' from package 'SAPNTAB'.
INFO: 2014-07-01 10:49:48 com.sap.inst.migmon.LoadThreadDispatcher loadPackage_report
Monitor jobs: running 1, waiting 28, completed 0, failed 0, total 29 Package Group max threads: 1 current running threads : 0 processing package: SAPNTAB
TRACE: 2014-07-01 10:49:48 com.sap.inst.migmon.LoadTask run
Loading of 'SAPNTAB' import package is started.
TRACE: 2014-07-01 10:49:48 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPNTAB' import package into database:
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast
INFO: 2014-07-01 10:49:59 com.sap.inst.migmon.LoadTask run_report
Monitor jobs: running 0, waiting 28, completed 0, failed 1, total 29 error processing of package SAPNTAB
ERROR: 2014-07-01 10:49:59 com.sap.inst.migmon.LoadTask run
Loading of 'SAPNTAB' import package is interrupted with R3load error.
Process 'D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast' exited with return code 2.
For mode details see 'SAPNTAB.log' file.
Standard error output:
sapparam: sapargv(argc, argv) has not been called!
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
WARNING: 2014-07-01 10:50:18
Cannot continue import because not all import packages with data conversion tables are loaded successfully.
WARNING: 2014-07-01 10:50:18
1 error(s) during processing of packages.
INFO: 2014-07-01 10:50:18
Import Monitor is stopped.
INFO: 2014-07-01 11:09:16
Import Monitor is started.
CONFIG: 2014-07-01 11:09:16
Application options:
dbCodepage=4103
dbType=SYB
extFiles=no
importDirs=D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_1\DATA_UNITS\EXP1;D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_1\DATA_UNITS\EXP2;D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP3;D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4
installDir=C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS
jobNum=8
loadArgs=-c 99000000 -loadprocedure fast
monitorTimeout=30
orderBy=
r3loadExe=D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe
sapinst=
trace=all
tskFiles=yes
CONFIG: 2014-07-01 11:09:16
List of packages with table structure: 'SAP0000'.
CONFIG: 2014-07-01 11:09:16
List of packages with views: 'SAPVIEW'.
TRACE: 2014-07-01 11:09:16 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS\DDLSYB.TPL' template file is started.
INFO: 2014-07-01 11:09:16 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS\DDLSYB.TPL' template file is successfully completed.
Primary key creation: after load.
Index creation: after load.
INFO: 2014-07-01 11:09:16
Data codepage 1100 is determined using TOC file 'D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_1\DATA_UNITS\EXP1\DATA\SAPSSEXC.TOC' for package 'SAPSSEXC'.
INFO: 2014-07-01 11:09:16
Version table 'SVERS' is found in STR file 'D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DATA\SAPNTAB.STR' from package 'SAPNTAB'.
INFO: 2014-07-01 11:09:16
Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DATA\SAPNTAB.STR' from package 'SAPNTAB'.
INFO: 2014-07-01 11:09:16 com.sap.inst.migmon.LoadThreadDispatcher loadPackage_report
Monitor jobs: running 1, waiting 28, completed 0, failed 0, total 29 Package Group max threads: 1 current running threads : 0 processing package: SAPNTAB
TRACE: 2014-07-01 11:09:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPNTAB' import package is started.
TRACE: 2014-07-01 11:09:16 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPNTAB' import package into database:
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast
INFO: 2014-07-01 11:09:27 com.sap.inst.migmon.LoadTask run_report
Monitor jobs: running 0, waiting 28, completed 0, failed 1, total 29 error processing of package SAPNTAB
ERROR: 2014-07-01 11:09:27 com.sap.inst.migmon.LoadTask run
Loading of 'SAPNTAB' import package is interrupted with R3load error.
Process 'D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast' exited with return code 2.
For mode details see 'SAPNTAB.log' file.
Standard error output:
sapparam: sapargv(argc, argv) has not been called!
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
WARNING: 2014-07-01 11:09:46
Cannot continue import because not all import packages with data conversion tables are loaded successfully.
WARNING: 2014-07-01 11:09:46
1 error(s) during processing of packages.
INFO: 2014-07-01 11:09:46
Import Monitor is stopped.
NOTE:
The same issue has been solved in SCN Thread http://scn.sap.com/thread/3360385. As suggested in that note i am trying to look into the sap note
Note 1716201 - SYB:Update control.xml files for installation: Sybase ASE
in service market place but it is displaying as Document not released.
Kindly can any one help me in provind the above mentioned note or help me how to resolve this issue.
Regards,
SURYA.HI Divyanshu,
Below is the SAPNTAB.log:
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140630211543
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
Compiled Dec 2 2011 03:21:30
patchinfo (patches.h): (0.113) NewDB R3load better support (note 1564286)
process id 1680
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -ctf I D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DATA\SAPNTAB.STR C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS\DDLSYB.TPL SAPNTAB.TSK SYB -l SAPNTAB.log
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: job completed
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140630211543
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140630211543
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
Compiled Dec 2 2011 03:21:30
patchinfo (patches.h): (0.113) NewDB R3load better support (note 1564286)
process id 1904
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast
(DB) INFO: connected to DB
(SQL) INFO: Searching for SQL file SQLFiles.LST
(SQL) INFO: SQLFiles.LST not found
(SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST
(SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST not found
(SQL) INFO: Searching for SQL file SDIC.SQL
(SQL) INFO: SDIC.SQL not found
(SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL
(SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL not found
(DB) INFO: SVERS created
(IMP) INFO: import of SVERS completed (1 rows) #20140630211544
(DB) INFO: SVERS~0 created
(DB) INFO: DDNTF created
(SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "DDNTF"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: DDNTF~0 created
(DB) INFO: DDNTF_CONV_UC created
(SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "DDNTF_CONV_UC"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: DDNTF_CONV_UC~0 created
(DB) INFO: DDNTT created
(SYB_IMP) ERROR: DbSlEndModify failed
rc = 99, table "DDNTT"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: EndFastload: rc = 2
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "DDNTT~0" ON "DDNTT" ( "TABNAME" ) )
DbSlExecute: rc = 99
(SQL error 1505)
error message returned by DbSl:
[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key. Primary key is '""'
(DB) INFO: DDNTT_CONV_UC created
(SYB_IMP) ERROR: DbSlEndModify failed
rc = 99, table "DDNTT_CONV_UC"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: EndFastload: rc = 2
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "DDNTT_CONV_UC~0" ON "DDNTT_CONV_UC" ( "TABNAME" ) )
DbSlExecute: rc = 99
(SQL error 1505)
error message returned by DbSl:
[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key. Primary key is '""'
(DB) INFO: disconnected from DB
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 6 error(s)
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140630211555
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140701104948
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
Compiled Dec 2 2011 03:21:30
patchinfo (patches.h): (0.113) NewDB R3load better support (note 1564286)
process id 2304
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast
(DB) INFO: connected to DB
(DB) INFO: DDNTF deleted/truncated
(SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "DDNTF"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: DDNTF_CONV_UC deleted/truncated
(SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "DDNTF_CONV_UC"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: DDNTT deleted/truncated
(SYB_IMP) ERROR: DbSlEndModify failed
rc = 99, table "DDNTT"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: EndFastload: rc = 2
(SQL) INFO: Searching for SQL file SQLFiles.LST
(SQL) INFO: SQLFiles.LST not found
(SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST
(SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST not found
(SQL) INFO: Searching for SQL file SDIC.SQL
(SQL) INFO: SDIC.SQL not found
(SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL
(SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL not found
(DB) ERROR: DDL statement failed
(DROP INDEX "DDNTT"."DDNTT~0")
DbSlExecute: rc = 103
(SQL error 3701)
error message returned by DbSl:
[ASE Error SQL3701][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Cannot drop the index 'DDNTT.DDNTT~0', because it doesn't exist in the system catalogs.
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "DDNTT~0" ON "DDNTT" ( "TABNAME" ) )
DbSlExecute: rc = 99
(SQL error 1505)
error message returned by DbSl:
[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key. Primary key is '""'
(DB) INFO: DDNTT_CONV_UC deleted/truncated
(SYB_IMP) ERROR: DbSlEndModify failed
rc = 99, table "DDNTT_CONV_UC"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: EndFastload: rc = 2
(DB) ERROR: DDL statement failed
(DROP INDEX "DDNTT_CONV_UC"."DDNTT_CONV_UC~0")
DbSlExecute: rc = 103
(SQL error 3701)
error message returned by DbSl:
[ASE Error SQL3701][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Cannot drop the index 'DDNTT_CONV_UC.DDNTT_CONV_UC~0', because it doesn't exist in the system catalogs.
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "DDNTT_CONV_UC~0" ON "DDNTT_CONV_UC" ( "TABNAME" ) )
DbSlExecute: rc = 99
(SQL error 1505)
error message returned by DbSl:
[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key. Primary key is '""'
(DB) INFO: disconnected from DB
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 6 error(s)
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140701104959
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140701110916
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
Compiled Dec 2 2011 03:21:30
patchinfo (patches.h): (0.113) NewDB R3load better support (note 1564286)
process id 2056
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast
(DB) INFO: connected to DB
(DB) INFO: DDNTF deleted/truncated
(SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "DDNTF"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: DDNTF_CONV_UC deleted/truncated
(SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "DDNTF_CONV_UC"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: DDNTT deleted/truncated
(SYB_IMP) ERROR: DbSlEndModify failed
rc = 99, table "DDNTT"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: EndFastload: rc = 2
(SQL) INFO: Searching for SQL file SQLFiles.LST
(SQL) INFO: SQLFiles.LST not found
(SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST
(SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST not found
(SQL) INFO: Searching for SQL file SDIC.SQL
(SQL) INFO: SDIC.SQL not found
(SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL
(SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL not found
(DB) ERROR: DDL statement failed
(DROP INDEX "DDNTT"."DDNTT~0")
DbSlExecute: rc = 103
(SQL error 3701)
error message returned by DbSl:
[ASE Error SQL3701][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Cannot drop the index 'DDNTT.DDNTT~0', because it doesn't exist in the system catalogs.
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "DDNTT~0" ON "DDNTT" ( "TABNAME" ) )
DbSlExecute: rc = 99
(SQL error 1505)
error message returned by DbSl:
[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key. Primary key is '""'
(DB) INFO: DDNTT_CONV_UC deleted/truncated
(SYB_IMP) ERROR: DbSlEndModify failed
rc = 99, table "DDNTT_CONV_UC"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: EndFastload: rc = 2
(DB) ERROR: DDL statement failed
(DROP INDEX "DDNTT_CONV_UC"."DDNTT_CONV_UC~0")
DbSlExecute: rc = 103
(SQL error 3701)
error message returned by DbSl:
[ASE Error SQL3701][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Cannot drop the index 'DDNTT_CONV_UC.DDNTT_CONV_UC~0', because it doesn't exist in the system catalogs.
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "DDNTT_CONV_UC~0" ON "DDNTT_CONV_UC" ( "TABNAME" ) )
DbSlExecute: rc = 99
(SQL error 1505)
error message returned by DbSl:
[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key. Primary key is '""'
(DB) INFO: disconnected from DB
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 6 error(s)
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140701110927
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140701120231
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
Compiled Dec 2 2011 03:21:30
patchinfo (patches.h): (0.113) NewDB R3load better support (note 1564286)
process id 2288
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast
(DB) INFO: connected to DB
(DB) INFO: DDNTF deleted/truncated
(SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "DDNTF"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: DDNTF_CONV_UC deleted/truncated
(SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "DDNTF_CONV_UC"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: DDNTT deleted/truncated
(SYB_IMP) ERROR: DbSlEndModify failed
rc = 99, table "DDNTT"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: EndFastload: rc = 2
(SQL) INFO: Searching for SQL file SQLFiles.LST
(SQL) INFO: SQLFiles.LST not found
(SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST
(SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST not found
(SQL) INFO: Searching for SQL file SDIC.SQL
(SQL) INFO: SDIC.SQL not found
(SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL
(SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL not found
(DB) ERROR: DDL statement failed
(DROP INDEX "DDNTT"."DDNTT~0")
DbSlExecute: rc = 103
(SQL error 3701)
error message returned by DbSl:
[ASE Error SQL3701][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Cannot drop the index 'DDNTT.DDNTT~0', because it doesn't exist in the system catalogs.
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "DDNTT~0" ON "DDNTT" ( "TABNAME" ) )
DbSlExecute: rc = 99
(SQL error 1505)
error message returned by DbSl:
[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key. Primary key is '""'
(DB) INFO: DDNTT_CONV_UC deleted/truncated
(SYB_IMP) ERROR: DbSlEndModify failed
rc = 99, table "DDNTT_CONV_UC"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: EndFastload: rc = 2
(DB) ERROR: DDL statement failed
(DROP INDEX "DDNTT_CONV_UC"."DDNTT_CONV_UC~0")
DbSlExecute: rc = 103
(SQL error 3701)
error message returned by DbSl:
[ASE Error SQL3701][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Cannot drop the index 'DDNTT_CONV_UC.DDNTT_CONV_UC~0', because it doesn't exist in the system catalogs.
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "DDNTT_CONV_UC~0" ON "DDNTT_CONV_UC" ( "TABNAME" ) )
DbSlExecute: rc = 99
(SQL error 1505)
error message returned by DbSl:
[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key. Primary key is '""'
(DB) INFO: disconnected from DB
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 6 error(s)
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140701120242 -
SM:SELFDIAGNOSIS background job getting failed in Solution manager
Hi All,
SM:SELFDIAGNOSIS background job getting failed in Solution manger server :
Job Log:
2-22-2012 16:44:02 Job started 00 516 S
2-22-2012 16:44:02 Step 001 started (program RDSWP_SELF_DIAGNOSIS, variant &0000000000324, user ID BASISUSER) 00 550 S
2-22-2012 16:45:07 Internal session terminated with a runtime error (see ST22) 00 671 A
2-22-2012 16:45:07 Job cancelled 00 518 A
ST22: Dump:
Runtime Errors ITAB_DUPLICATE_KEY
Date and Time 02-22-2012 16:45:07
Short text
A row with the same key already exists.
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_DSWP_SD_DIAGNOSE_CONSISTENTCP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
An entry was to be entered into the table
"\CLASS=CL_DSWP_SD_DIAGNOSE_CONSISTENT\METHOD=CHECK_USERS_BP\DATA=LT_USCP"
(which should have
had a unique table key (UNIQUE KEY)).
However, there already existed a line with an identical key.
The insert-operation could have ocurred as a result of an INSERT- or
MOVE command, or in conjunction with a SELECT ... INTO.
The statement "INSERT INITIAL LINE ..." cannot be used to insert several
initial lines into a table with a unique key.
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"ITAB_DUPLICATE_KEY" " "
"CL_DSWP_SD_DIAGNOSE_CONSISTENTCP" or "CL_DSWP_SD_DIAGNOSE_CONSISTENTCM00M"
"CHECK_USERS_BP"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
KIndly Suggest to resolve the above issue
Thanks
NekkalapuHI,
Deatils:
SAP EHP 1 for SAP Solution Manager 7.0
SAP_ABA 701 0006 SAPKA70106
SAP_BASIS 701 0006 SAPKB70106
PI_BASIS 701 0006 SAPK-70106INPIBASI
ST-PI 2008_1_700 0002 SAPKITLRD2
CRMUIF 500 0004 SAPK-50004INCRMUIF
SAP_BW 701 0006 SAPKW70106
SAP_AP 700 0019 SAPKNA7019
BBPCRM 500 0016 SAPKU50016
BI_CONT 704 0007 SAPK-70407INBICONT
CPRXRPM 400 0016 SAPK-40016INCPRXRP
ST 400 0024 SAPKITL434
ST-A/PI 01M_CRM570 0000 -
ST-ICO 150_700 0009 SAPK-15079INSTPL
ST-SER 701_2010_1 0002 SAPKITLOS2
Thanks
Nekkalapu -
Creating a new user in solution manager?
Dear All,
How to create a new user in solution manager for creating an incident?prathish5,
I did this in our SolMan by following the instructions provided by a SAP document called: "Service Desk VAR Setup Master Data". I got it from the Support Portal, though I can't seem to find it now so I can't provide a link at this time.
Anyway, assuming that your SolMan is already able to download your master data (and/or your customers', if you are a VAR), these are the steps suggested by the guide:
1) The message creator (aka Key User) should have the following authorization roles:
SAP_SUPPDESK_CREATE
SAP_SUPPCF_CREATE
SAP_SMWORK_BASIC
SAP_SMWORK_INCIDENT_MAN
See also SAP note 834534.
A best practice is to create a Z copy of all of these roles (use transaction PFCG), so you can manage them and change them around if you need to. Just make sure to "activate" all the authorizations of your copy of the roles:
- Open the roles in tr. PFCG;
- Select Authorizations, and choose Change authorization data;
- If you get a yellow semaphore, be sure to review the authorizations and fill them according to your security policy. You can assign global permissions for all the authorization objects by double-clicking the yellow semaphore;
- Generate the profile, then go back and save the role;
2) Following the guide, with tr. SU01 I created a Template user and called it KEY_USER (make sure the user type is actually Template) and assigned to it the Z roles you created in the step above;
3) If your SolMan is working properly, you can now use report AI_SDK_SP_GENERATE_BP (tr. SA38) to create the Business Partners and SAP users automatically. The report will log in the Support Portal and read the users which are authorized to open a SAP tickets, and create a BP and user for each of them. Use the Template user KEY_USER created in step 2 as a "Reference user" and all the new users will automatically get the correct autorizations. Also if your SAP Connect (tr. SCOT) is correctly configured, you can choose to send an automatic mail to each user, with their login and generated password.
Otherwise, you can manually create a user with transactions SU01 and BP - be sure to fill the "Identities" table here - the report AI_SDK_SP_GENERATE_BP makes all these things automatically so it's definitely your best bet.
4) Your users should now be able to log in with the SAPgui and use transaction CREATE_NOTIF to create a new message in your SolMan. Also if you have done the preparation steps correctly they should also be able to log in your Incident Manager using their browser, and open a message there and also review their past messages.
Those are just a quick insight of the steps you need to do. This is NOT an easy thing to configure, at least it wasn't for me; if you don't have a reliable guide to follow you're going to struggle: I strongly suggest you browse through the SAP documentations (also the blogs) - http://service.sap.com/xsearch is your best friend!
I hope this helps a little bit. Good luck. -
How to maintain a common document in solution manager
Gurus ,
we are in the process of configuring service desk . One major type of support message we receive is user creation /modification .
currently we maintain these details in an common excel sheet . if a new requirement is made they take the latest modified excel sheet and mark the changes in them .
But now what we need in , we need to maintain this document is solution manager server .
and the users can access the document , make changes , save it and upload it back to the server .
any of you have any suggestions on implementing the sameHello Susin,
User Creation / Deletion / Modification is a Change in the system. It cannot be handled via a standard central document like a Excel on a datshare.
Solution Manager is not a content repository to be used for storing such documents. There is no way that you can acheive it as a standard process.
Probably what you can do is as follows :
- Create a table structure in Solution Manager and assign it colums as needed.
- Then write a ABAP Code to access and maintain this table Structure.
- Assign a transaction code to the ABAP Code so that it can be accessed by different users.
I hope that the reply helps.
Regards
Amit -
Background job failing - ECC 6.0, Solution Manager 7.0
Dear All,
Four days back, I have installed the Solution Manager 7.0 and ECC 6.0 on
HPUX IA64 hardware with database as Oracle 10.2.0.2.0 (Unicode).
In both server, latest kernel patch has been applied.
The Support package versions are (both server):
KERNEL (Release 700) 146
SAP_BASIS 0014
SAP_ABA 0014
PI_BASIS(2005_1_700) 0014
ST-PI 0005
SAP_BW 0016
While checking the the jobs from SM37, in both the server,
I am observing that following jobs are always failing with
same reason:
SAP_COLLECTOR_FOR_PERFMONITOR
=============================
Date Time Message text Message class Message no. Message type
========== ======== ====================================================================== ============= =========== ============
15.05.2008 06:25:12 Job started 00 516 S
15.05.2008 06:25:12 Step 001 started (program RSCOLL00, variant , user ID BGDUSER) 00 550 S
15.05.2008 06:25:18 Clean_Plan:Cleanup of DB13 Plannings DB6PM 000 S
15.05.2008 06:25:18 Clean_Plan:started by RSDBPREV on server gcbeccd DB6PM 000 S
15.05.2008 06:25:18 Clean_Plan:Cleaning up jobs of system RD3 DB6PM 000 S
15.05.2008 06:25:18 Clean_Plan:finished DB6PM 000 S
15.05.2008 06:25:18 Database system not supported S1 101 S
15.05.2008 06:25:36 ABAP/4 processor: DBIF_DSQL2_SQL_ERROR 00 671 A
15.05.2008 06:25:36 Job cancelled 00 518 A
SAP_REORG_UPDATERECORDS
=======================
Date Time Message text Message class Message no. Message type
========== ======== ===================================================================== ============= =========== ============
14.05.2008 00:31:01 Job started 00 516 S
14.05.2008 00:31:01 Step 001 started (program RSM13002, variant SAP&001, user ID BGDUSER) 00 550 S
14.05.2008 00:31:01 Reorganization of update date not allowed in batch 15 100 A
14.05.2008 00:31:02 Job cancelled 00 518 A
SAP_WP_CACHE_RELOAD_FULL
========================
Date Time Message text Message class Message no. Message type
========== ======== ============================================================================================ ============= =========== ============
15.05.2008 00:30:11 Job started 00 516 S
15.05.2008 00:30:11 Step 001 started (program RWP_RUNTIME_CACHE_RELOAD, variant SAP&RELOAD_ALL, user ID BGDUSER) 00 550 S
15.05.2008 00:30:11 No component system chosen URL_GEN_MSGS 031 E
15.05.2008 00:30:11 Job cancelled after system exception ERROR_MESSAGE 00 564 A
Please help to resolve this issue.
Thanks in advance.
Regards
Sudip GhoshHi Markus,
Thanks for the reply.
Below is the dump:
======
======
Runtime Errors DBIF_DSQL2_SQL_ERROR
Date and Time 15.05.2008 06:25:36
Short text
An SQL error occurred when executing Native SQL.
What happened?
The error 3113 occurred in the current database connection "DEFAULT".
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
How to correct the error
Database error text........: "ORA-03113: end-of-file on communication channel"
Database error code........: 3113
Triggering SQL statement...: "FETCH NEXT "
Internal call code.........: "[DBDS/NEW DSQL]"
Please check the entries in the system log (Transaction SM21).
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"DBIF_DSQL2_SQL_ERROR" " "
"RSORAVSH" or "RSORAVSH"
"FILL_DBVSE"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "gcbeccd"
Network address...... "10.10.4.158"
Operating system..... "HP-UX"
Release.............. "B.11.23"
Hardware type........ "ia64"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 15
Shortdump setting.... "full"
Database server... "gcbeccd"
Database type..... "ORACLE"
Database name..... "RD3"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Apr 5 2008 00:55:24"
create on........ "HP-UX B.11.23 U ia64"
Database version. "OCI_102 (10.2.0.1.0) "
Patch level. 146
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "HP-UX B.11"
Memory consumption
Roll.... 1117216
EM...... 0
Heap.... 0
Page.... 32768
MM Used. 695792
MM Free. 400816
User and Transaction
Client.............. 000
User................ "BGDUSER"
Language key........ "E"
Transaction......... " "
Transactions ID..... "482B8A4C89F0442BE10000000A0A049E"
Program............. "RSORAVSH"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "RSORAVSH" - in "FILL_DBVSE".
The main program was "RSORAVSH ".
In the source code you have the termination point in line 48
of the (Include) program "RSORAVSH".
The program "RSORAVSH" was started as a background job.
Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
Job Initiator.. "BGDUSER"
Job Number..... 05251100
Source Code Extract
Line
SourceCde
18
INCLUDE STRUCTURE v_system_event_struc.
19
DATA: END OF v_system_event_tab .
20
21
check sy-dbsys(3) = 'ORA' .
22
23
Get the new snapshots
24
25
PERFORM fill_dbvse TABLES v_system_event_tab.
26
27
28
Get the old snapshots from database table MONI
29
30
startday = sy-datum - days_to_keep .
31
32
33
Save new data now (otherwise these data will be selected twice)
34
35
CONCATENATE 'SYSEVENT' sy-datum sy-uzeit INTO monikey .
36
37
EXPORT sy-datum
38
sy-uzeit
39
v_system_event_tab
40
TO DATABASE moni(db) ID monikey .
41
42
*& Form FILL_DBVSE
43
44
FORM fill_dbvse TABLES v_system_event_tab.
45
date = sy-datum .
46
time = sy-uzeit .
47
EXEC sql performing append_v_system_event .
>>>>>
select event,
49
total_waits,
50
total_timeouts,
51
time_waited * 10,
52
average_wait * 10
53
into :v_system_event_struc
54
from v$system_event
55
ENDEXEC .
56
ENDFORM. " FILL_DBVSE
57
58
59
*& Form APPEND_V_SYSTEM_EVENT
60
61
FORM append_v_system_event.
62
v_system_event_tab-date = date .
63
v_system_event_tab-time = time .
64
65
MOVE-CORRESPONDING v_system_event_struc TO v_system_event_tab.
66
APPEND v_system_event_tab .
67
ENDFORM. " APPEND_V_SYSTEM_EVENT
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
16
SY-DBCNT
0
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
Report for Collecting Data from V$SYSTEM_EVENT Hourly
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080515
SY-UZEIT
062520
SY-XPROG
RSDBRUNT
SY-XFORM
%_INIT_PBO_FIRST
Active Calls/Events
No. Ty. Program Include Line
Name
2 FORM RSORAVSH RSORAVSH 48
FILL_DBVSE
1 EVENT RSORAVSH RSORAVSH 25
START-OF-SELECTION
Chosen variables
Name
Val.
No. 2 Ty. FORM
Name FILL_DBVSE
SY-REPID
RSORAVSH
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5545455422222222222222222222222222222222
23F2163800000000000000000000000000000000
V_SYSTEM_EVENT_STRUC
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222222222222222220000000000000000
0000000000000000000000000000000000000000000000000000000000000000000C000C000C000C
%_SPACE
0
0
2
0
SY
###############################################################################T######## ####
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000400
000001000000000000000000000000000000000F000000000000000000000000000000000000010500000005220000
000000000000000000000000010001000000000E00000000000000000000000000000000000006040000000800000C
No. 1 Ty. EVENT
Name START-OF-SELECTION
SY-LDBPG
SAPDB__S
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454455522222222222222222222222222222222
31042FF300000000000000000000000000000000
%_DUMMY$$
0000
0000
2222
0000
SY-DBSYS+0(6)
ORA
000
000
454
F21
SYST
###############################################################################T######## ####
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000400
000001000000000000000000000000000000000F000000000000000000000000000000000000010500000005220000
000000000000000000000000010001000000000E00000000000000000000000000000000000006040000000800000C
V_SYSTEM_EVENT_TAB[]
Table[initial]
V_SYSTEM_EVENT_TAB
00000000000000 ################
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
3333333333333322222222222222222222222222222222222222222222222222222222222222220000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000C000C000C000C
SY-DATUM
20080515
00000000
00000000
33333333
20080515
DAYS_TO_KEEP
30
0001
000E
STARTDAY
00000000
00000000
00000000
33333333
00000000
MONIKEY
0000000000000000000000
0000000000000000000000
2222222222222222222222
0000000000000000000000
SY-UZEIT
062520
000000
000000
333333
062520
SYST-REPID
RSORAVSH
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5545455422222222222222222222222222222222
23F2163800000000000000000000000000000000
MONI-CLUSTR
0
00
00
MONI
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222220022000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Internal notes
The termination was triggered in function "ExecuteCall"
of the SAP kernel, in line 1190 of the module
"//bas/700_REL/src/krn/runt/abexsql.c#2".
The internal operation just processed is "DSQL".
Internal mode was started at 20080515062520.
Internal call code.........: "[DBDS/NEW DSQL]"
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
(0) 0x4000000003b2b450 CTrcStack + 0x1b0 at dptstack.c:227 [dw.sapRD3_DVEBMGS00]
(1) 0x4000000004d2c470 Z16rabaxCStackSavev + 0x1d0 [dw.sapRD3_DVEBMGS00]
(2) 0x4000000004d32160 ab_rabax + 0x3570 [dw.sapRD3_DVEBMGS00]
(3) 0x40000000047b51e0 Z10abdbdserriPKtiS0_P9DS_HEADERS0_iPv + 0x470 [dw.sapRD3_DVEBMGS00]
(4) 0x4000000003d777f0 Z11ExecuteCallv + 0x11f0 [dw.sapRD3DVEBMGS00]
(5) 0x4000000003d7e7b0 Z8abjdsqlv + 0x1b0 [dw.sapRD3_DVEBMGS00]
(6) 0x400000000402f190 Z8abextriv + 0x440 [dw.sapRD3_DVEBMGS00]
(7) 0x4000000003f53bc0 Z9abxeventPKt + 0x3c0 at abrunt1.c:339 [dw.sapRD3_DVEBMGS00]
(8) 0x4000000003d9f210 Z8abtriggv + 0x110 at abrunt1.c:58 [dw.sapRD3_DVEBMGS00]
(9) 0x4000000003d9ebe0 ab_run + 0xc0 [dw.sapRD3_DVEBMGS00]
(10) 0x4000000001caa820 N_ab_run + 0x20 at dymainstp.c:4739 [dw.sapRD3_DVEBMGS00]
(11) 0x4000000001cb40f0 dynpmcal + 0x3f0 at dymainstp.c:2281 [dw.sapRD3_DVEBMGS00]
(12) 0x4000000001caf260 dynppai0 + 0xcb0 at dymainstp.c:1107 [dw.sapRD3_DVEBMGS00]
(13) 0x4000000001cb1ec0 dynprctl + 0x340 at dymainstp.c:358 [dw.sapRD3_DVEBMGS00]
(14) 0x4000000001c9dff0 dynpen00 + 0xac0 at dymain.c:1628 [dw.sapRD3_DVEBMGS00]
(15) 0x4000000001fea460 Thdynpen00 + 0x510 at thxxhead.c:4830 [dw.sapRD3_DVEBMGS00]
(16) 0x4000000001fb54e0 TskhLoop + 0x5520 at thxxhead.c:3945 [dw.sapRD3_DVEBMGS00]
(17) 0x4000000001faae40 ThStart + 0x460 at thxxhead.c:1164 [dw.sapRD3_DVEBMGS00]
(18) 0x4000000001569ec0 DpMain + 0x5f0 at dpxxdisp.c:1088 [dw.sapRD3_DVEBMGS00]
(19) 0x4000000002c10630 nlsui_main + 0x30 [dw.sapRD3_DVEBMGS00]
(20) 0x4000000002c105c0 main + 0x60 [dw.sapRD3_DVEBMGS00]
(21) 0xc00000000002be30 main_opd_entry + 0x50 [/usr/lib/hpux64/dld.so]
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
RSORAVSH
0
30.03.2005
10:21:59
19456
E
1
Prg
SAPMSSY0
1
17.12.2007
15:41:05
92160
E
2
Prg
SAPMSSYD
1
12.09.2006
11:33:31
21504
E
3
Prg
SAPFSYSCALLS
1
09.09.2004
14:18:32
8192
E
4
Prg
RSDBRUNT
0
17.12.2007
16:04:40
254976
E
5
Typ
RSSCR
0
30.03.2005
10:21:45
5120
6
Prg
RSDBSPBL
0
30.03.2005
10:21:58
72704
E
7
Prg
SAPDB__S
0
30.03.2005
10:22:01
19456
E
8
Prg
RSDBSPMC
0
12.09.2006
11:25:01
79872
E
9
Typ
DDSHDESCR
0
03.09.1997
03:05:16
4096
10
Typ
SPPARAMS
0
07.05.1997
13:10:38
2048
11
Prg
SAPLSABE
11
09.09.2004
14:18:36
13312
E
12
Prg
SAPLSECU
12
17.12.2007
15:31:45
87040
E
13
Typ
RSSUBINFO
0
14.10.1999
22:01:03
3072
14
Prg
SAPLSTUP
14
17.12.2007
15:29:58
74752
E
15
Prg
SAPLCNDP
15
11.09.2007
15:24:45
195584
E
16
Prg
SAPLSCNT
16
18.02.2005
14:16:06
30720
E
17
Prg
SAPSHDTV
16
05.01.2005
16:26:16
33792
E
18
Prg
SAPFGUICNTL
1
18.02.2005
14:15:08
24576
E
19
Prg
SAPLOLEA
19
11.09.2007
11:17:30
96256
E
20
Prg
SAPLSGUI
20
17.12.2007
15:41:05
84992
E
21
Prg
SAPLSTTM
21
05.07.2005
13:10:18
69632
E
22
Prg
SAPLSBDC
22
17.12.2007
15:30:54
44032
E
23
Prg
SAPLSFES
23
17.12.2007
16:04:40
260096
E
24
Prg
SAPLTHFB
24
17.12.2007
15:41:05
394240
E
25
Typ
WPINFO
0
26.02.1999
14:49:01
6144
26
Prg
SAPLURFC
26
17.12.2007
15:37:35
22528
E
27
Prg
SAPLSPLUGIN
27
09.09.2004
14:18:36
8192
E
28
Typ
SWCBCONT
0
15.11.2000
17:55:11
3072
29
Typ
OLE_VERBS
0
04.04.1995
16:02:20
2048
30
Typ
OLE_PA
0
04.04.1995
16:02:19
2048
31
Typ
SYST
0
09.09.2004
14:18:12
31744
32
Typ
MONI
0
31.03.2004
16:41:21
5120
Directory of Application Tables
Name Date Time Lngth
Val.
Program RSORAVSH
SYST 09.09.2004 14:18:12 00004612
\0\0\0\0\0\x0010\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0
MONI . . : : 00002944
\0\0 \0\0\0\0\0\0\0\0\0\0\0\0\0\0
ABAP Control Blocks (CONT)
Index
Name
Fl
PAR0
PAR1
PAR2
PAR3
PAR4
PAR5
PAR6
Source Code
Line
71
PAR2
03
0000
0014
002B
RSORAVSH
37
73
PAR2
03
0000
0015
002D
RSORAVSH
37
75
PAR2
03
0000
0016
0026
RSORAVSH
37
77
00
0000
RSORAVSH
37
78
PERP
00
0002
RSORAVSH
44
79
PERP
1C
0000
RSORAVSH
44
80
PERP
04
0000
RSORAVSH
44
81
mvqk
10
0005
0044
04EC
RSORAVSH
45
83
mvqk
0C
0005
0054
052E
RSORAVSH
46
85
DSQL
00
0017
RSORAVSH
48
86
DSQL
01
0018
RSORAVSH
48
87
DSQL
04
0025
RSORAVSH
48
>>>>>
DSQL
16
0025
RSORAVSH
48
89
BRAN
05
0004
RSORAVSH
48
90
perf
00
000A
RSORAVSH
48
91
PERP
80
0000
RSORAVSH
48
92
BRAX
00
FFFC
RSORAVSH
48
93
DSQL
23
0000
RSORAVSH
48
94
ENDF
00
0000
RSORAVSH
56
95
00
0000
RSORAVSH
56
===========
===========
Please check and advise.
Also, I am trying to search for the note 6083 in market place, but not getting the same.
Please advise.
Thanks & Regards
Sudip
Maybe you are looking for
-
How to install SAP BODS,which version is comaptiable to SAP R/3 system as source
I would like to know installation steps for BODS?How to make connection between SAP R/3 (Source )and BODS. What is the purpose of CTS to copy in the SAP R/3 application server?
-
Editing a Web Template in Dreamweaver
Is there a way I can edit a template permanantly in Dreamweaver? I use one of the provided templates and use the 'Contact' field as an external link. However I need two links not one, (apart from the header), so if there is a way to add an extra link
-
I've used Acrobat 9 for a few years with no problem. But recently, reading a standalone PDF file crashes Windows XP. If I try to create a PDF file, Windows XP crashes. If I try to uninstall Acrobat 9, XP crashes. But...I can view PDF files in Int
-
Yamaha KX61 USb MIDI keyboard doesn't work in Garage Band
I have installed latest Yamaha USB-MIDI driver V1.2.0 for Yamaha KX61. I have connected USB cable to Mac Mini and turned the keyboard on. In Other section of System Preferences I can see an icon for Yamaha USB-MIDI. In there I can see Device Name: Ya
-
Compressor speed depends on the codec you choose
Hi, add my cent to speed and quality issues. Compressor speed depends on the codec you choose, Animation it's incredibly sloooow...that's not happening in QT MPEG2 export. ah... tip: if software update blown away your QT MPEG2 export, reinstalling DV