Hi everyone,
I work a little time with sap basis and some friends tell me that a good way to learn it´s mount a sap lab at home and make each installation process since the begin.
I work with energy company(Utilities), I would like to know how I can do it??? it´s so much complicated??? where can I find support or help in this case??.
please, send me any information that could help me.
Thanks
Hi experts ,
Im facing issue in Solman 7.1 which its creating dump as
Eror analysis
Category ABAP Programming Error
Runtime Errors CREATE_DATA_UNKNOWN_TYPE
Except. CX_SY_CREATE_DATA_ERROR
ABAP Program SAPLSMD_FUNC
Application Component SV-SMG-DIA
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_CREATE_DATA_ERROR', was not
caught in
procedure "SMD_DATA_LOADER255" "(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 dynamically specified type "/BI0/V0SYB_C01H2" at CREATE DATA is no valid
data type.
The type is either unknown or an object type.
OS:Windows 2008 ,DB:Sybase 15.7.0.110,Solman is SP04 ie (710/04) ,BI-Cont 706/02
Abap/basis stack -702/09
I have gone through some notes and manually activate the info -objects but it same continues with same dump
Im not sure if the Sap Note 1342231 could work for me .
Appreciate your help asap.
Rgd
Asim
Hello,
i'm installing Introscope in a client with Windows Server 2003, SLQ 2005 and 32 bits system...
every time í try to startup the service of introscope manager it gives me the following error
"The Introscope Enterprise Manager service terminated with service-specific error 1 (0x1)."
I already installed with sysdam, administrator, and so on, but it always give me the some error.
the path of installation it's \usr\sap\ccms\introscope...
can you help?
Thanks
In the Connect Managed System step of Managed System Configuration, I created the RFCs and users for the RFC without any problem. But when I click the Test RFC button, I'm getting the following:
BACK RFC:Password logon no longer possible - too many failed attempts
BACK RFC:Name or password is incorrect (repeat logon)
LOGIN-Destination SM_QA1CLNT300_LOGIN created
Destination SM_QA1_TRUSTED_BACK created
TRUSTED-Destination SM_SM1CLNT100_TRUSTED created
Destination SM_SM1_TRUSTED_BACK created
TRUSTED-Destination SM_QA1CLNT300_TRUSTED created
BACK-Destination SM_SM1CLNT100_BACK with User SMB_QA1 created successfully
Roles already existed and were assigned to user SMB_QA1
User SM_SM1 has changed
Role SAP_SOLMAN_READ has been uploaded to the managed system QA1~300
Customer role ZSAP_SOLMAN_READ has been created as a copy of SAP role SAP_SOLMAN_READ
Changes already exist completely
Roles already existed and were assigned to user SM_SM1
Operation successfully executed
User SMTMSM1 has changed
Role SAP_SOLMAN_READ has been uploaded to the managed system QA1~300
Customer role ZSAP_SOLMAN_READ has been created as a copy of SAP role SAP_SOLMAN_READ
Changes already exist completely
Role SAP_SOLMAN_TMW has been uploaded to the managed system QA1~300
Customer role ZSAP_SOLMAN_TMW has been created as a copy of SAP role SAP_SOLMAN_TMW
Changes already exist completely
Roles already existed and were assigned to user SMTMSM1
Operation successfully executed
User SMB_QA1 has changed
Customer role ZSAP_SOLMAN_BACK has been created as a copy of SAP role SAP_SOLMAN_BACK
The user SMB_QA1 in SM is locked so I unlocked it. But it will be locked again after I click Test a few times. I tried the following without success:
Any help would be appreciated. Thanks.
Henry
Hello,
Checking the technical monitoring status, it shows grey
Checked the error & it shows the extractor not executed.
When checking the extractor status, its executed for host & not for the ABAP instance. Please assist.
Other systems have the extractor info as below
Thanks,
Hi All,
We need host agent for SAP kernel 640 and patch level 247 for manage system for monitoring purpose .
Is it possible to install host agent ? if it so please tell the complete procedure to install the manage system ?
or is there any other way to monitor the OS and DB details through solman system 7.1 without using host agent ? if it so please tell the complete procedure.
Hi All
We are planning to do PI message monitoring for PI Interfaces using CCMS monitor in solution manager since our PI is on version 7.0 .
We have already did PI message monitor (CCMS Monitor) 6 months ago and by that time it was working fine and I was able to do the configuration .
Now I have tried to do few more interfaces but I could not able to find anything in the CCMS context , where I suppose to select SAP XI Central Monitoring .
I have verfied the System Topology for PI system in Solman and it is fine .
And I have verified the RZ21 of PI system it is fine and all the interfaces are listing .
Kindly help to fix the issue .
Regards
Bala
Hi gurus,
We are getting this error when we are trying connect the manage system through the solman 7.20
System details : R3 system is in Windows server 2003, MSSQL 2000 kernal version 640 and patch level 247.
The solman system is in windows 2012 , MSSQL 2012 and kernal 720 patch level 600.
the questions
1) is it possible to downgrade to solman version and which will support MSSQL 2000 ?
2) is there any other alternative way for this error without downgrade?
Thanks
Rammohan
HI Experts,
Can anyone help me to restrict attachments deletion in solman service desk and let me how to find the history for the same
THanks in advance
Regards
Kapil
Hello,
I want to trigger an OS script when File system alert gets triggered. I performed the configuration as per document 'How-to guide: OS Command Adapter', but the script does not get triggered on Alert.
The script can be executed directly from SM49.
BAdi is assigned in template for Third-party tab and activated. There are no logs written in SLG1 for OS_CMD as mentioned in document, while I can see log for Notification sent.
How can we verify that BAdI gets triggered correctly? Please help troubleshoot this to find out where it goes wrong. Thanks.
Hello
I get the followingwarning messagefor allconnected systemsin ourSolution Manager.
In theAgentAdministrationitlooks like this
I already have changedthe value ofsmd.file.root_directories to \\<HOST>\sapmnt. But the warning persist.
How can I fix the issue? Which value is correct?
Thank you for your assistance.
Veysel I.
Hello
we just made a releaseupgrade to SM 7.1sp10
Unfortunately the Functionality to open a ticket from connected systems
with the Function under "Help/ Create Support Message" looses the Description-Text.
in the Development-system this works fine, but in Production the text-types SU99 and SUSD
are not saved.
I debugged so far in SUP_STSUP_NOTIFICATION_CREATE and the texts are transferred, but
the crm-Object does not save them.
Using transaction notif_create the description is saved.
Any ideas?
Kind Regards
Rolf Keplinger
Dear All,
Please help in charm 7.1 configuration. We have configured client specific routes and rfcs configured.
As the client specific routes activated, we are updating the target client for all the transport requests in buffer of all systems. Only after assigning the target client for old requests in buffer we are getting the option to import a request, we are still doing this.
Now i have created project and activated charm, when i check for errors i find that solman not able to get the tms parameters in all systems. Please help urgently.
Below is the error details showing for each system:
Check System XXX:
1. Error getting TMS configuration parameters of system xxx
2.Invalid TMS configuration for domain DOMAIN_xxx
3. Transport control program not configured
I have checked the tp tool and transport directory of all systems in STMS, everything is fine.
Thank you.
HI
while working on managed system configuration in the step landscape parameter at one place we have to give path to the folder of logs of database.
as i am working on distributed environment i.e sap on one server and database on another server i gave path to the database log directory it is giving error that directory not found.
is there any work around for it?
Dear Gurus,
I need your help as I have problems with my Solman 7.1 SP11 (OS: SUSE Linux 11).
I have just upgraded my Solman 7.1 SP11 and I already applied sap notes 1933506 latest version 9.
To fix some issue which I already posted here "http://scn.sap.com/thread/3562637", I decided to upgrade these two components (based by
recommendation from sap note 856909 - Error after JDK upgrade on system with Wily Introscope) :
-LMSERVICE11P_1-20006622.SCA
-SAPJVM4_43-10009718.SAR
I upgraded it by using SUM10SP10_7-20006543.SAR. During upgrade, I am stuck at the step of starting JAVA. Now my Solman cannot start the J2EE
already. The server0 cannot be started. Here are the logs:
-dev_server0
-dev_bootstrap
-std_bootstrap.out
-dev_bootstrap_ID3152050
-jvm_bootstrap.out
-log_bootstrap_ID0031520.0.log
=============================================================================================================
-dev_server0
**********************************************************************
JStartupIReadSection: read node properties [ID3152050]
-> node name : server0
-> node type : server
-> node execute : yes
-> jlaunch parameters :
-> java path : /usr/sap/S01/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 -
Dcom.wily.introscope.agent.agentName=S01_DVEBMGS00_server0 -
Dcom.wily.introscope.agentProfile=/usr/sap/DA1/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.
4.0-2012-06-26/wily/IntroscopeAgent.profile -XX:+JavaMonitorsInStackTrace -
Xbootclasspath/p:/usr/sap/DA1/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.4.0-2012-06-
26/wily/connectors/AutoProbeConnector.jar:/usr/sap/DA1/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAG
ENT.8.2.4.0-2012-06-26/wily/Agent.jar
-> java vm version : 4.1.028 23.5-b02
-> 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 : /usr/sap/S01/DVEBMGS00/j2ee/cluster/server0
-> class path : ./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.
-> OS libs path : /usr/sap/S01/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 : /usr/sap/S01/DVEBMGS00/exe/jstartup.jar:/usr/sap/S01/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 140546455713632] JLaunchISetDebugMode: set debug mode [no]
[Thr 140546043488000] JLaunchIStartFunc: Thread 140546043488000 started as Java VM thread.
**********************************************************************
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack : 1048576 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -
Denv.class.path=:/db2/db2s01/sqllib/java/db2java.zip:/db2/db2s01/sqllib/java/runtime.zip:.:/db2/db2s01/sqllib/java/db2java.zip:/db2/db2s01/sqlli
b/java/runtime.zip:.
-> arg[ 4]: -XX:MaxNewSize=600M
-> arg[ 5]: -XX:NewSize=600M
-> arg[ 6]: -XX:MaxPermSize=512M
-> arg[ 7]: -XX:PermSize=512M
-> arg[ 8]: -XX:+UseConcMarkSweepGC
-> arg[ 9]: -XX:+DisableExplicitGC
-> arg[ 10]: -XX:TargetSurvivorRatio=90
-> arg[ 11]: -XX:SurvivorRatio=4
-> arg[ 12]: -XX:+PrintGCDetails
-> arg[ 13]: -XX:+PrintGCTimeStamps
-> arg[ 14]: -verbose:gc
-> arg[ 15]: -XX:SoftRefLRUPolicyMSPerMB=1
-> arg[ 16]: -XX:HeapDumpPath=OOM.hprof
-> arg[ 17]: -XX:+HeapDumpOnOutOfMemoryError
-> arg[ 18]: -Djco.jarm=1
-> arg[ 19]: -Djava.awt.headless=true
-> arg[ 20]: -Djava.security.policy=./java.policy
-> arg[ 21]: -Djava.security.egd=file:/dev/urandom
-> arg[ 22]: -Dsun.io.useCanonCaches=false
-> arg[ 23]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[ 24]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[ 25]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
-> arg[ 26]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[ 27]: -Dcom.sap.jvm.scenario=j2ee
-> arg[ 28]: -Dcom.wily.introscope.agent.agentName=S01_DVEBMGS00_server0
-> arg[ 29]: -
Dcom.wily.introscope.agentProfile=/usr/sap/DA1/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.
4.0-2012-06-26/wily/IntroscopeAgent.profile
-> arg[ 30]: -XX:+JavaMonitorsInStackTrace
-> arg[ 31]: -
Xbootclasspath/p:/usr/sap/DA1/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.4.0-2012-06-
26/wily/connectors/AutoProbeConnector.jar:/usr/sap/DA1/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAG
ENT.8.2.4.0-2012-06-26/wily/Agent.jar
-> arg[ 32]: -Dsys.global.dir=/usr/sap/S01/SYS/global
-> arg[ 33]: -Dapplication.home=/usr/sap/S01/DVEBMGS00/exe
-> arg[ 34]: -
Djava.class.path=/usr/sap/S01/DVEBMGS00/exe/jstartup.jar:/usr/sap/S01/DVEBMGS00/exe/jvmx.jar:./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/syste
m/bytecode.jar:.
-> arg[ 35]: -
Djava.library.path=/usr/sap/S01/DVEBMGS00/exe/sapjvm_4/jre/lib/amd64/server:/usr/sap/S01/DVEBMGS00/exe/sapjvm_4/jre/lib/amd64:/usr/sap/S01/DVEBM
GS00/exe/sapjvm_4/jre/../lib/amd64:/usr/sap/S01/DVEBMGS00/exe:/usr/sap/S01/DVEBMGS00/exe:/usr/sap/S01/DVEBMGS00/exe:/usr/sap/S01/SYS/exe/run:/us
r/sap/S01/SYS/exe/uc/linuxx86_64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib:/usr/sap/S01/DVEBMGS00/j2ee/os_libs:/usr/sap/S01/D
VEBMGS00/exe:/usr/sap/S01/DVEBMGS00/exe:/usr/sap/S01/DVEBMGS00/exe:/usr/sap/S01/SYS/exe/run:/usr/sap/S01/SYS/exe/uc/linuxx86_64
-> arg[ 36]: -Dmemory.manager=2048M
-> arg[ 37]: -Xmx2048M
-> arg[ 38]: -Xms2048M
-> arg[ 39]: -Xss2M
-> arg[ 40]: -DLoadBalanceRestricted=no
-> arg[ 41]: -Djstartup.mode=JCONTROL
-> arg[ 42]: -Djstartup.ownProcessId=19811
-> arg[ 43]: -Djstartup.ownHardwareId=Z0506874237
-> arg[ 44]: -Djstartup.whoami=server
-> arg[ 45]: -Djstartup.debuggable=no
-> arg[ 46]: -Xjvmx
-> arg[ 47]: -XsapSystem=00
-> arg[ 48]: -XmonGcCallback
-> arg[ 49]: -DSAPINFO=S01_00_server
-> arg[ 50]: -DSAPSTART=1
-> arg[ 51]: -DCONNECT_PORT=23735
-> arg[ 52]: -DSAPSYSTEM=00
-> arg[ 53]: -DSAPSYSTEMNAME=S01
-> arg[ 54]: -DSAPMYNAME=jjsapmon_S01_00
-> arg[ 55]: -DSAPPROFILE=/usr/sap/S01/SYS/profile/S01_DVEBMGS00_jjsapmon
-> arg[ 56]: -DFRFC_FALLBACK=ON
-> arg[ 57]: -DFRFC_FALLBACK_HOST=localhost
-> arg[ 58]: -DSAPSTARTUP=1
-> arg[ 59]: -DSAPSYSTEM=00
-> arg[ 60]: -DSAPSYSTEMNAME=S01
-> arg[ 61]: -DSAPMYNAME=jjsapmon_S01_00
-> arg[ 62]: -DSAPDBHOST=jjsapmon
-> arg[ 63]: -Dj2ee.dbhost=jjsapmon
**********************************************************************
(CompilerOracle read from file /usr/sap/S01/DVEBMGS00/exe/sapjvm_4/jre/.hotspot_compiler)
[Thr 140546043488000] JHVM_LoadJavaVM: Java VM created OK.
Heap
par new generation reserved 614400K, committed 614400K, used 98347K [0x00000000014a0000, 0x0000000026ca0000, 0x0000000026ca0000)
eden space 409600K, 24% used [0x00000000014a0000, 0x00000000074aaf48, 0x000000001a4a0000)
from space 102400K, 0% used [0x000000001a4a0000, 0x000000001a4a0000, 0x00000000208a0000)
to space 102400K, 0% used [0x00000000208a0000, 0x00000000208a0000, 0x0000000026ca0000)
concurrent mark-sweep generation reserved 1482752K, committed 1482752K, used 0K [0x0000000026ca0000, 0x00000000814a0000, 0x00000000814a0000)
concurrent-mark-sweep perm gen reserved 524288K, committed 524288K, used 2521K [0x00000000814a0000, 0x00000000a14a0000, 0x00000000a14a0000)
[Thr 140545581360896] JLaunchIExitJava: exit hook is called (rc = 1)
[Thr 140545581360896] **********************************************************************
[Thr 140545581360896] *** ERROR => The Java VM terminated with a non-zero exit code.
[Thr 140545581360896] *** Please see SAP Note 943602 , section 'J2EE Engine exit codes'
[Thr 140545581360896] *** for additional information and trouble shooting.
[Thr 140545581360896] **********************************************************************
[Thr 140545581360896] SigISetIgnoreAction : SIG_IGN for signal SIGCHLD
[Thr 140545581360896] JLaunchCloseProgram: good bye (exitcode = 1)
904,1 Bot
=============================================================================================================
-dev_bootstrap
[Thr 140282983114592] Fri Jun 6 16:09:21 2014
[Thr 140282983114592] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 140282983114592] JLaunchRequestQueueInit: create pipe listener thread
[Thr 140282982233856] JLaunchRequestFunc: Thread 140282982233856 started as listener thread for np messages.
[Thr 140282983114592] JLaunchInitSignalHandling: signal handling is disabled
[Thr 140282920482560] WaitSyncSemThread: Thread 140282920482560 started as semaphore monitor thread.
[Thr 140282983114592] NiInit3: NI already initialized; param 'maxHandles' ignored (init=1;par=32768;cur=2048)
[Thr 140282983114592] CCMS: Detected Double Stack (parameter "rdisp/j2ee_start" is active)
[Thr 140282983114592] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Doublestack.
[Thr 140282983114592] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Doublestack.
[Thr 140282983114592] CCMS: CCMS Monitoring Initialization finished, rc=0.
[Thr 140282983114592] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/S01/DVEBMGS00/exe/jvmx.jar
JStartupIReadSection: read node properties [bootstrap]
-> node name : bootstrap
-> node type : bootstrap
-> node execute : yes
-> java path : /usr/sap/S01/DVEBMGS00/exe/sapjvm_4
-> java parameters : -Djco.jarm=1
-> java vm version : 4.1.028 23.5-b02
-> java vm vendor : SAP Java Server VM (SAP AG)
-> java vm type : server
-> java vm cpu : amd64
-> heap size : 256M
-> root path : /usr/sap/S01/DVEBMGS00/j2ee/cluster
-> class path : ./bootstrap/launcher.jar
-> OS libs path : /usr/sap/S01/DVEBMGS00/j2ee/os_libs
-> main class : com.sap.engine.offline.OfflineToolStart
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : /usr/sap/S01/DVEBMGS00/exe/jstartup.jar:/usr/sap/S01/DVEBMGS00/exe/jvmx.jar
-> parameters : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0031520
-> debuggable : yes
-> debug mode : no
-> debug port : 60000
-> shutdown timeout : 120 sec.
**********************************************************************
[Thr 140282845656832] JLaunchIStartFunc: Thread 140282845656832 started as Java VM thread.
**********************************************************************
JHVM_LoadJavaVM: VM Arguments of node [bootstrap]
-> stack : 1048576 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -
Denv.class.path=:/db2/db2s01/sqllib/java/db2java.zip:/db2/db2s01/sqllib/java/runtime.zip:.:/db2/db2s01/sqllib/java/db2java.zip:/db2/db2s01/sqlli
b/java/runtime.zip:.
-> arg[ 4]: -Djco.jarm=1
-> arg[ 5]: -Dsys.global.dir=/usr/sap/S01/SYS/global
-> arg[ 6]: -Dapplication.home=/usr/sap/S01/DVEBMGS00/exe
-> arg[ 7]: -Djava.class.path=/usr/sap/S01/DVEBMGS00/exe/jstartup.jar:/usr/sap/S01/DVEBMGS00/exe/jvmx.jar:./bootstrap/launcher.jar
-> arg[ 8]: -
Djava.library.path=/usr/sap/S01/DVEBMGS00/exe/sapjvm_4/jre/lib/amd64/server:/usr/sap/S01/DVEBMGS00/exe/sapjvm_4/jre/lib/amd64:/usr/sap/S01/DVEBM
GS00/exe/sapjvm_4/jre/../lib/amd64:/usr/sap/S01/DVEBMGS00/exe:/usr/sap/S01/DVEBMGS00/exe:/usr/sap/S01/DVEBMGS00/exe:/usr/sap/S01/SYS/exe/run:/us
r/sap/S01/SYS/exe/uc/linuxx86_64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib:/usr/sap/S01/DVEBMGS00/j2ee/os_libs:/usr/sap/S01/D
VEBMGS00/exe:/usr/sap/S01/DVEBMGS00/exe:/usr/sap/S01/DVEBMGS00/exe:/usr/sap/S01/SYS/exe/run:/usr/sap/S01/SYS/exe/uc/linuxx86_64
-> arg[ 9]: -Dmemory.manager=256M
-> arg[ 10]: -Xmx256M
-> arg[ 11]: -DLoadBalanceRestricted=no
-> arg[ 12]: -Djstartup.mode=BOOTSTRAP
-> arg[ 13]: -Djstartup.ownProcessId=18525
-> arg[ 14]: -Djstartup.ownHardwareId=Z0506874237
-> arg[ 15]: -Djstartup.whoami=bootstrap
-> arg[ 16]: -Djstartup.debuggable=yes
-> arg[ 17]: -Xjvmx
-> arg[ 18]: -XsapSystem=00
-> arg[ 19]: -XmonGcCallback
-> arg[ 20]: -XdebugPortRange:60000-60000
-> arg[ 21]: -XdebugStateChangeCallback
-> arg[ 22]: -DSAPINFO=S01_00_bootstrap
-> arg[ 23]: -DSAPSTART=1
-> arg[ 24]: -DCONNECT_PORT=23735
-> arg[ 25]: -DSAPSYSTEM=00
-> arg[ 26]: -DSAPSYSTEMNAME=S01
-> arg[ 27]: -DSAPMYNAME=jjsapmon_S01_00
-> arg[ 28]: -DSAPPROFILE=/usr/sap/S01/SYS/profile/S01_DVEBMGS00_jjsapmon
-> arg[ 29]: -DFRFC_FALLBACK=ON
-> arg[ 30]: -DFRFC_FALLBACK_HOST=localhost
-> arg[ 31]: -DSAPSTARTUP=1
-> arg[ 32]: -DSAPSYSTEM=00
-> arg[ 26]: -DSAPSYSTEMNAME=S01
-> arg[ 27]: -DSAPMYNAME=jjsapmon_S01_00
-> arg[ 28]: -DSAPPROFILE=/usr/sap/S01/SYS/profile/S01_DVEBMGS00_jjsapmon
-> arg[ 29]: -DFRFC_FALLBACK=ON
-> arg[ 30]: -DFRFC_FALLBACK_HOST=localhost
-> arg[ 31]: -DSAPSTARTUP=1
-> arg[ 32]: -DSAPSYSTEM=00
-> arg[ 33]: -DSAPSYSTEMNAME=S01
-> arg[ 34]: -DSAPMYNAME=jjsapmon_S01_00
-> arg[ 35]: -DSAPDBHOST=jjsapmon
-> arg[ 36]: -Dj2ee.dbhost=jjsapmon
**********************************************************************
Fri Jun 6 16:09:22 2014
(CompilerOracle read from file /usr/sap/S01/DVEBMGS00/exe/sapjvm_4/jre/.hotspot_compiler)
[Thr 140282845656832] JHVM_LoadJavaVM: Java VM created OK.
**********************************************************************
JHVM_BuildArgumentList: main method arguments of node [bootstrap]
-> arg[ 0]: com.sap.engine.bootstrap.Bootstrap
-> arg[ 1]: ./bootstrap
-> arg[ 2]: ID0031520
**********************************************************************
[Thr 140282845656832] JHVM_RegisterNatives: com.sap.bc.krn.perf.PerfTimes
: [140282845656832] 16:09:32 ***ERROR (:0): OutOfMemoryError: Could not allocate 14065825 bytes
[Thr 140282514757376] Fri Jun 6 16:09:38 2014
[Thr 140282514757376] JLaunchIExitJava: exit hook is called (rc = 66)
[Thr 140282514757376] **********************************************************************
[Thr 140282514757376] *** ERROR => The Java VM terminated with a non-zero exit code.
[Thr 140282514757376] *** Please see SAP Note 943602 , section 'J2EE Engine exit codes'
[Thr 140282514757376] *** for additional information and trouble shooting.
[Thr 140282514757376] **********************************************************************
[Thr 140282514757376] SigISetIgnoreAction : SIG_IGN for signal SIGCHLD
[Thr 140282514757376] JLaunchCloseProgram: good bye (exitcode = 66)
192,1 Bot
**********************************************************************
=============================================================================================================
-std_bootstrap.out
--------------------------------------------------------------------------------
stdout/stderr redirect
--------------------------------------------------------------------------------
node name : bootstrap
pid : 18399
system name : S01
system nr. : 00
started at : Fri Jun 6 16:09:20 2014
(CompilerOracle read from file /usr/sap/S01/DVEBMGS00/exe/sapjvm_4/jre/.hotspot_compiler)
[Thr 140282514757376] Fri Jun 6 16:09:23 2014
[Thr 140282514757376] *** ERROR => JsfGetShmVmci: check failed: sRefs.statAccess > SFI_SMA_NOTINIT [jsfxxsproc.c 439]
[Thr 140282514757376] Fri Jun 6 16:09:25 2014
[Thr 140282514757376] *** ERROR => JsfGetShmVmci: check failed: sRefs.statAccess > SFI_SMA_NOTINIT [jsfxxsproc.c 439]
[Thr 140282514757376] *** ERROR => JsfGetShmVmci: check failed: sRefs.statAccess > SFI_SMA_NOTINIT [jsfxxsproc.c 439]
[Thr 140282514757376] *** ERROR => JsfGetShmVmci: check failed: sRefs.statAccess > SFI_SMA_NOTINIT [jsfxxsproc.c 439]
[Thr 140282514757376] *** ERROR => JsfGetShmVmci: check failed: sRefs.statAccess > SFI_SMA_NOTINIT [jsfxxsproc.c 439]
[Thr 140282514757376] *** ERROR => JsfGetShmVmci: check failed: sRefs.statAccess > SFI_SMA_NOTINIT [jsfxxsproc.c 439]
[Thr 140282514757376] Fri Jun 6 16:09:28 2014
[Thr 140282514757376] *** ERROR => JsfGetShmVmci: check failed: sRefs.statAccess > SFI_SMA_NOTINIT [jsfxxsproc.c 439]
[Thr 140282514757376] *** ERROR => JsfGetShmVmci: check failed: sRefs.statAccess > SFI_SMA_NOTINIT [jsfxxsproc.c 439]
[Thr 140282514757376] Fri Jun 6 16:09:30 2014
[Thr 140282514757376] *** ERROR => JsfGetShmVmci: check failed: sRefs.statAccess > SFI_SMA_NOTINIT [jsfxxsproc.c 439]
[Thr 140282514757376] *** ERROR => JsfGetShmVmci: check failed: sRefs.statAccess > SFI_SMA_NOTINIT [jsfxxsproc.c 439]
[Thr 140282514757376] Fri Jun 6 16:09:32 2014
[Thr 140282514757376] *** ERROR => JsfGetShmVmci: check failed: sRefs.statAccess > SFI_SMA_NOTINIT [jsfxxsproc.c 439]
[Thr 140282514757376] *** ERROR => JsfGetShmVmci: check failed: sRefs.statAccess > SFI_SMA_NOTINIT [jsfxxsproc.c 439]
: [140282845656832] 16:09:32 ***ERROR (:0): OutOfMemoryError: Could not allocate 14065825 bytes
33,1 Bot
=============================================================================================================
-dev_bootstrap_ID3152050
**********************************************************************
JHVM_LoadJavaVM: VM Arguments of node [server0 bootstrap]
-> stack : 1048576 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -
Denv.class.path=:/db2/db2s01/sqllib/java/db2java.zip:/db2/db2s01/sqllib/java/runtime.zip:.:/db2/db2s01/sqllib/java/db2java.zip:/db2/db2s01/sqlli
b/java/runtime.zip:.
-> arg[ 4]: -Djco.jarm=1
-> arg[ 5]: -Dsys.global.dir=/usr/sap/S01/SYS/global
-> arg[ 6]: -Dapplication.home=/usr/sap/S01/DVEBMGS00/exe
-> arg[ 7]: -Djava.class.path=/usr/sap/S01/DVEBMGS00/exe/jstartup.jar:/usr/sap/S01/DVEBMGS00/exe/jvmx.jar:./bootstrap/launcher.jar
-> arg[ 8]: -
Djava.library.path=/usr/sap/S01/DVEBMGS00/exe/sapjvm_4/jre/lib/amd64/server:/usr/sap/S01/DVEBMGS00/exe/sapjvm_4/jre/lib/amd64:/usr/sap/S01/DVEBM
GS00/exe/sapjvm_4/jre/../lib/amd64:/usr/sap/S01/DVEBMGS00/exe:/usr/sap/S01/DVEBMGS00/exe:/usr/sap/S01/DVEBMGS00/exe:/usr/sap/S01/SYS/exe/run:/us
r/sap/S01/SYS/exe/uc/linuxx86_64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib:/usr/sap/S01/DVEBMGS00/j2ee/os_libs:/usr/sap/S01/D
VEBMGS00/exe:/usr/sap/S01/DVEBMGS00/exe:/usr/sap/S01/DVEBMGS00/exe:/usr/sap/S01/SYS/exe/run:/usr/sap/S01/SYS/exe/uc/linuxx86_64
-> arg[ 9]: -Dmemory.manager=256M
-> arg[ 10]: -Xmx256M
-> arg[ 11]: -DLoadBalanceRestricted=no
-> arg[ 12]: -Djstartup.mode=BOOTSTRAP
-> arg[ 13]: -Djstartup.ownProcessId=18837
-> arg[ 14]: -Djstartup.ownHardwareId=Z0506874237
-> arg[ 15]: -Djstartup.whoami=bootstrap
-> arg[ 16]: -Djstartup.debuggable=yes
-> arg[ 17]: -Xjvmx
-> arg[ 18]: -XsapSystem=00
-> arg[ 19]: -XmonGcCallback
-> arg[ 20]: -XdebugPortRange:60000-60000
-> arg[ 21]: -XdebugStateChangeCallback
-> arg[ 22]: -DSAPINFO=S01_00_bootstrap
-> arg[ 23]: -DSAPSTART=1
-> arg[ 24]: -DCONNECT_PORT=23735
-> arg[ 25]: -DSAPSYSTEM=00
-> arg[ 26]: -DSAPSYSTEMNAME=S01
-> arg[ 27]: -DSAPMYNAME=jjsapmon_S01_00
-> arg[ 28]: -DSAPPROFILE=/usr/sap/S01/SYS/profile/S01_DVEBMGS00_jjsapmon
-> arg[ 29]: -DFRFC_FALLBACK=ON
-> arg[ 30]: -DFRFC_FALLBACK_HOST=localhost
-> arg[ 31]: -DSAPSTARTUP=1
-> arg[ 32]: -DSAPSYSTEM=00
-> arg[ 33]: -DSAPSYSTEMNAME=S01
-> arg[ 34]: -DSAPMYNAME=jjsapmon_S01_00
-> arg[ 35]: -DSAPDBHOST=jjsapmon
-> arg[ 36]: -Dj2ee.dbhost=jjsapmon
**********************************************************************
(CompilerOracle read from file /usr/sap/S01/DVEBMGS00/exe/sapjvm_4/jre/.hotspot_compiler)
[Thr 140094896854784] Fri Jun 6 16:09:45 2014
[Thr 140094896854784] JHVM_LoadJavaVM: Java VM created OK.
**********************************************************************
JHVM_BuildArgumentList: main method arguments of node [server0 bootstrap]
-> arg[ 0]: com.sap.engine.bootstrap.Bootstrap
-> arg[ 1]: ./bootstrap
-> arg[ 2]: ID003152050
**********************************************************************
[Thr 140094896854784] JHVM_RegisterNatives: com.sap.bc.krn.perf.PerfTimes
[Thr 140094564890368] Fri Jun 6 16:09:49 2014
[Thr 140094564890368] JLaunchIExitJava: exit hook is called (rc = 0)
[Thr 140094564890368] SigISetIgnoreAction : SIG_IGN for signal SIGCHLD
[Thr 140094564890368] JLaunchCloseProgram: good bye (exitcode = 0)
188,1 Bot
=============================================================================================================
-jvm_bootstrap.out
--------------------------------------------------
Bootstrap MODE:
<INSTANCE GLOBALS>
determined by parameter [ID0031520].
--------------------------------------------------
Instance [ID31520] will run in [normal] mode, performing action [NONE]
Discovered property [instance.en.port] with value [3201] !
Discovered property [instance.en.host] with value [jjsapmon] !
Synchronizing file [./.hotspot_compiler].
...Synched ok!
Synchronizing file [../../SDM/program/.hotspot_compiler].
...Synched ok!
* Synchronizing native files...
Synchronizing file [./../os_libs/ServicesNatives2_native.zip].
...Synched ok!
Synchronizing file [./../os_libs/PDFManipulation_native.zip].
...Synched ok!
Synchronizing file [./../os_libs/FontManagerService_native.zip].
Error synchronizing file [./../os_libs/FontManagerService_native.zip].
com.sap.engine.frame.core.configuration.InvalidPersistentDataStreamException: Could not get file from DB.
at com.sap.engine.core.configuration.impl.PersistentDataInputStream.getStream(PersistentDataInputStream.java:84)
at com.sap.engine.core.configuration.impl.PersistentDataInputStream.read(PersistentDataInputStream.java:135)
at com.sap.engine.bootstrap.Synchronizer.getFile(Synchronizer.java:245)
at com.sap.engine.bootstrap.Synchronizer.getFile(Synchronizer.java:216)
at com.sap.engine.bootstrap.Synchronizer.synchronizeFile(Synchronizer.java:151)
at com.sap.engine.bootstrap.Bootstrap.getOSDependentFiles(Bootstrap.java:683)
at com.sap.engine.bootstrap.Bootstrap.synchInstanceGlobals(Bootstrap.java:201)
at com.sap.engine.bootstrap.Bootstrap.makeUpdate(Bootstrap.java:968)
at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:947)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by:
com.ibm.db2.jcc.am.DisconnectRecoverableException: [jcc][t4][10379][11961][3.65.77] Client disconnect exception encountered: [jcc][t4][2091]
[11332][3.65.77] Attempt to fully materialize lob data that is too large for the JVM.
Disable data source property "fullyMaterializeLobData" for locator-based lob implementation. ERRORCODE=-4499, SQLSTATE=null ERRORCODE=-4499,
SQLSTATE=null
at com.ibm.db2.jcc.am.cd.a(cd.java:319)
at com.ibm.db2.jcc.am.cd.a(cd.java:369)
at com.ibm.db2.jcc.t4.c.a(c.java:890)
at com.ibm.db2.jcc.t4.c.a(c.java:985)
at com.ibm.db2.jcc.t4.c.b(c.java:956)
at com.ibm.db2.jcc.t4.c.b(c.java:710)
at com.ibm.db2.jcc.am.gc.a(gc.java:214)
at com.ibm.db2.jcc.t4.c.a(c.java:127)
at com.ibm.db2.jcc.am.ResultSet.nextX(ResultSet.java:381)
at com.ibm.db2.jcc.am.ResultSet.next(ResultSet.java:308)
at com.sap.sql.jdbc.basic.BasicResultSet.next(BasicResultSet.java:61)
at com.sap.sql.jdbc.direct.DirectResultSet.next(DirectResultSet.java:132)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBAccessDefault.getFileEntry(DBAccessDefault.java:1007)
at com.sap.engine.core.configuration.impl.persistence.rdbms.FileLoader.getInputStream(FileLoader.java:33)
at com.sap.engine.core.configuration.impl.PersistentDataInputStream.getStream(PersistentDataInputStream.java:81)
at com.sap.engine.core.configuration.impl.PersistentDataInputStream.read(PersistentDataInputStream.java:135)
at com.sap.engine.bootstrap.Synchronizer.getFile(Synchronizer.java:245)
at com.sap.engine.bootstrap.Synchronizer.getFile(Synchronizer.java:216)
at com.sap.engine.bootstrap.Synchronizer.synchronizeFile(Synchronizer.java:151)
at com.sap.engine.bootstrap.Bootstrap.getOSDependentFiles(Bootstrap.java:683)
at com.sap.engine.bootstrap.Bootstrap.synchInstanceGlobals(Bootstrap.java:201)
at com.sap.engine.bootstrap.Bootstrap.makeUpdate(Bootstrap.java:968)
at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:947)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by: com.ibm.db2.jcc.am.DisconnectRecoverableException: [jcc][t4][2091][11332][3.65.77] Attempt to fully materialize lob data that is too
large for the JVM.
Disable data source property "fullyMaterializeLobData" for locator-based lob implementation. ERRORCODE=-4499, SQLSTATE=null
at com.ibm.db2.jcc.am.cd.a(cd.java:319)
at com.ibm.db2.jcc.am.cd.a(cd.java:404)
at com.ibm.db2.jcc.t4.ab.Dc(ab.java:2170)
at com.ibm.db2.jcc.t4.ab.d(ab.java:2155)
at com.ibm.db2.jcc.t4.bb.a(bb.java:185)
at com.ibm.db2.jcc.t4.bb.c(bb.java:31)
at com.ibm.db2.jcc.t4.q.a(q.java:32)
at com.ibm.db2.jcc.t4.i.readFetch_(i.java:263)
at com.ibm.db2.jcc.am.ResultSet.flowFetch(ResultSet.java:3796)
at com.ibm.db2.jcc.t4.c.a(c.java:887)
... 25 more
Synchronizing file [./../os_libs/librscp4j.so].
...Synched ok!
Synchronizing file [./../os_libs/XMLFormService_native.zip].
...Synched ok!
All CHMOD commands finished successfully...
Exception occurred:
com.sap.engine.bootstrap.SynchronizationException: Unable to synchronize native files for instance [ID31520]!
at com.sap.engine.bootstrap.Bootstrap.synchInstanceGlobals(Bootstrap.java:211)
at com.sap.engine.bootstrap.Bootstrap.makeUpdate(Bootstrap.java:968)
at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:947)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
----------==[ Caused by: ]==----------
com.sap.engine.frame.core.configuration.InvalidPersistentDataStreamException: Could not get file from DB.
at com.sap.engine.core.configuration.impl.PersistentDataInputStream.getStream(PersistentDataInputStream.java:84)
at com.sap.engine.core.configuration.impl.PersistentDataInputStream.read(PersistentDataInputStream.java:135)
at com.sap.engine.bootstrap.Synchronizer.getFile(Synchronizer.java:245)
at com.sap.engine.bootstrap.Synchronizer.getFile(Synchronizer.java:216)
at com.sap.engine.bootstrap.Synchronizer.synchronizeFile(Synchronizer.java:151)
at com.sap.engine.bootstrap.Bootstrap.getOSDependentFiles(Bootstrap.java:683)
at com.sap.engine.bootstrap.Bootstrap.synchInstanceGlobals(Bootstrap.java:201)
at com.sap.engine.bootstrap.Bootstrap.makeUpdate(Bootstrap.java:968)
at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:947)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by:
com.ibm.db2.jcc.am.DisconnectRecoverableException: [jcc][t4][10379][11961][3.65.77] Client disconnect exception encountered: [jcc][t4][2091]
[11332][3.65.77] Attempt to fully materialize lob data that is too large for the JVM.
Disable data source property "fullyMaterializeLobData" for locator-based lob implementation. ERRORCODE=-4499, SQLSTATE=null ERRORCODE=-4499,
SQLSTATE=null
at com.ibm.db2.jcc.am.cd.a(cd.java:319)
at com.ibm.db2.jcc.am.cd.a(cd.java:369)
at com.ibm.db2.jcc.t4.c.a(c.java:890)
at com.ibm.db2.jcc.t4.c.a(c.java:985)
at com.ibm.db2.jcc.t4.c.b(c.java:956)
at com.ibm.db2.jcc.t4.c.b(c.java:710)
at com.ibm.db2.jcc.am.gc.a(gc.java:214)
at com.ibm.db2.jcc.t4.c.a(c.java:127)
at com.ibm.db2.jcc.am.ResultSet.nextX(ResultSet.java:381)
at com.ibm.db2.jcc.am.ResultSet.next(ResultSet.java:308)
at com.sap.sql.jdbc.basic.BasicResultSet.next(BasicResultSet.java:61)
at com.sap.sql.jdbc.direct.DirectResultSet.next(DirectResultSet.java:132)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBAccessDefault.getFileEntry(DBAccessDefault.java:1007)
at com.sap.engine.core.configuration.impl.persistence.rdbms.FileLoader.getInputStream(FileLoader.java:33)
at com.sap.engine.core.configuration.impl.PersistentDataInputStream.getStream(PersistentDataInputStream.java:81)
at com.sap.engine.core.configuration.impl.PersistentDataInputStream.read(PersistentDataInputStream.java:135)
at com.sap.engine.bootstrap.Synchronizer.getFile(Synchronizer.java:245)
at com.sap.engine.bootstrap.Synchronizer.getFile(Synchronizer.java:216)
at com.sap.engine.bootstrap.Synchronizer.synchronizeFile(Synchronizer.java:151)
at com.sap.engine.bootstrap.Bootstrap.getOSDependentFiles(Bootstrap.java:683)
at com.sap.engine.bootstrap.Bootstrap.synchInstanceGlobals(Bootstrap.java:201)
at com.sap.engine.bootstrap.Bootstrap.makeUpdate(Bootstrap.java:968)
at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:947)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by: com.ibm.db2.jcc.am.DisconnectRecoverableException: [jcc][t4][2091][11332][3.65.77] Attempt to fully materialize lob data that is too
large for the JVM.
Disable data source property "fullyMaterializeLobData" for locator-based lob implementation. ERRORCODE=-4499, SQLSTATE=null
at com.ibm.db2.jcc.am.cd.a(cd.java:319)
at com.ibm.db2.jcc.am.cd.a(cd.java:404)
at com.ibm.db2.jcc.t4.ab.Dc(ab.java:2170)
at com.ibm.db2.jcc.t4.ab.d(ab.java:2155)
at com.ibm.db2.jcc.t4.bb.a(bb.java:185)
at com.ibm.db2.jcc.t4.bb.c(bb.java:31)
at com.ibm.db2.jcc.t4.q.a(q.java:32)
at com.ibm.db2.jcc.t4.i.readFetch_(i.java:263)
at com.ibm.db2.jcc.am.ResultSet.flowFetch(ResultSet.java:3796)
at com.ibm.db2.jcc.t4.c.a(c.java:887)
... 25 more
[Bootstrap module]> Problem occurred while performing synchronization.
~
157,1 Bot
=============================================================================================================
-log_bootstrap_ID0031520.0.log
Caused by:
com.ibm.db2.jcc.am.DisconnectRecoverableException: [jcc][t4][10379][11961][3.65.77] Client disconnect exception encountered: [jcc][t4][2091]
[11332][3.65.77] Attempt to fully materialize lob data that is too large for the JVM.
Disable data source property "fullyMaterializeLobData" for locator-based lob implementation. ERRORCODE=-4499, SQLSTATE=null ERRORCODE=-4499,
SQLSTATE=null
at com.ibm.db2.jcc.am.cd.a(cd.java:319)
at com.ibm.db2.jcc.am.cd.a(cd.java:369)
at com.ibm.db2.jcc.t4.c.a(c.java:890)
at com.ibm.db2.jcc.t4.c.a(c.java:985)
at com.ibm.db2.jcc.t4.c.b(c.java:956)
at com.ibm.db2.jcc.t4.c.b(c.java:710)
at com.ibm.db2.jcc.am.gc.a(gc.java:214)
at com.ibm.db2.jcc.t4.c.a(c.java:127)
at com.ibm.db2.jcc.am.ResultSet.nextX(ResultSet.java:381)
at com.ibm.db2.jcc.am.ResultSet.next(ResultSet.java:308)
at com.sap.sql.jdbc.basic.BasicResultSet.next(BasicResultSet.java:61)
at com.sap.sql.jdbc.direct.DirectResultSet.next(DirectResultSet.java:132)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBAccessDefault.getFileEntry(DBAccessDefault.java:1007)
at com.sap.engine.core.configuration.impl.persistence.rdbms.FileLoader.getInputStream(FileLoader.java:33)
at com.sap.engine.core.configuration.impl.PersistentDataInputStream.getStream(PersistentDataInputStream.java:81)
at com.sap.engine.core.configuration.impl.PersistentDataInputStream.read(PersistentDataInputStream.java:135)
at com.sap.engine.bootstrap.Synchronizer.getFile(Synchronizer.java:245)
at com.sap.engine.bootstrap.Synchronizer.getFile(Synchronizer.java:216)
at com.sap.engine.bootstrap.Synchronizer.synchronizeFile(Synchronizer.java:151)
at com.sap.engine.bootstrap.Bootstrap.getOSDependentFiles(Bootstrap.java:683)
at com.sap.engine.bootstrap.Bootstrap.synchInstanceGlobals(Bootstrap.java:201)
at com.sap.engine.bootstrap.Bootstrap.makeUpdate(Bootstrap.java:968)
at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:947)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by: com.ibm.db2.jcc.am.DisconnectRecoverableException: [jcc][t4][2091][11332][3.65.77] Attempt to fully materialize lob data that is too
large for the JVM.
Disable data source property "fullyMaterializeLobData" for locator-based lob implementation. ERRORCODE=-4499, SQLSTATE=null
at com.ibm.db2.jcc.am.cd.a(cd.java:319)
at com.ibm.db2.jcc.am.cd.a(cd.java:404)
at com.ibm.db2.jcc.t4.ab.Dc(ab.java:2170)
at com.ibm.db2.jcc.t4.ab.d(ab.java:2155)
at com.ibm.db2.jcc.t4.bb.a(bb.java:185)
at com.ibm.db2.jcc.t4.bb.c(bb.java:31)
at com.ibm.db2.jcc.t4.q.a(q.java:32)
at com.ibm.db2.jcc.t4.i.readFetch_(i.java:263)
at com.ibm.db2.jcc.am.ResultSet.flowFetch(ResultSet.java:3796)
at com.ibm.db2.jcc.t4.c.a(c.java:887)
... 25 more
[Jun 6, 2014 4:09:32 PM ] Synchronizing file [./../os_libs/librscp4j.so].
[Jun 6, 2014 4:09:33 PM ] ...Synched ok!
[Jun 6, 2014 4:09:33 PM ] Synchronizing file [./../os_libs/XMLFormService_native.zip].
[Jun 6, 2014 4:09:38 PM ] ...Synched ok!
[Jun 6, 2014 4:09:38 PM ] All CHMOD commands finished successfully...
[Jun 6, 2014 4:09:38 PM ] Exception occurred:
com.sap.engine.bootstrap.SynchronizationException: Unable to synchronize native files for instance [ID31520]!
at com.sap.engine.bootstrap.Bootstrap.synchInstanceGlobals(Bootstrap.java:211)
at com.sap.engine.bootstrap.Bootstrap.makeUpdate(Bootstrap.java:968)
at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:947)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
----------==[ Caused by: ]==----------
com.sap.engine.frame.core.configuration.InvalidPersistentDataStreamException: Could not get file from DB.
at com.sap.engine.core.configuration.impl.PersistentDataInputStream.getStream(PersistentDataInputStream.java:84)
at com.sap.engine.core.configuration.impl.PersistentDataInputStream.read(PersistentDataInputStream.java:135)
at com.sap.engine.bootstrap.Synchronizer.getFile(Synchronizer.java:245)
at com.sap.engine.bootstrap.Synchronizer.getFile(Synchronizer.java:216)
at com.sap.engine.bootstrap.Synchronizer.synchronizeFile(Synchronizer.java:151)
at com.sap.engine.bootstrap.Bootstrap.getOSDependentFiles(Bootstrap.java:683)
at com.sap.engine.bootstrap.Bootstrap.synchInstanceGlobals(Bootstrap.java:201)
at com.sap.engine.bootstrap.Bootstrap.makeUpdate(Bootstrap.java:968)
at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:947)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by:
com.ibm.db2.jcc.am.DisconnectRecoverableException: [jcc][t4][10379][11961][3.65.77] Client disconnect exception encountered: [jcc][t4][2091]
[11332][3.65.77] Attempt to fully materialize lob data that is too large for the JVM.
Disable data source property "fullyMaterializeLobData" for locator-based lob implementation. ERRORCODE=-4499, SQLSTATE=null ERRORCODE=-4499,
SQLSTATE=null
at com.ibm.db2.jcc.am.cd.a(cd.java:319)
at com.ibm.db2.jcc.am.cd.a(cd.java:369)
at com.ibm.db2.jcc.t4.c.a(c.java:890)
at com.ibm.db2.jcc.t4.c.a(c.java:985)
at com.ibm.db2.jcc.t4.c.b(c.java:956)
at com.ibm.db2.jcc.t4.c.b(c.java:710)
at com.ibm.db2.jcc.am.gc.a(gc.java:214)
at com.ibm.db2.jcc.t4.c.a(c.java:127)
at com.ibm.db2.jcc.am.ResultSet.nextX(ResultSet.java:381)
at com.ibm.db2.jcc.am.ResultSet.next(ResultSet.java:308)
at com.sap.sql.jdbc.basic.BasicResultSet.next(BasicResultSet.java:61)
at com.sap.sql.jdbc.direct.DirectResultSet.next(DirectResultSet.java:132)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBAccessDefault.getFileEntry(DBAccessDefault.java:1007)
at com.sap.engine.core.configuration.impl.persistence.rdbms.FileLoader.getInputStream(FileLoader.java:33)
at com.sap.engine.core.configuration.impl.PersistentDataInputStream.getStream(PersistentDataInputStream.java:81)
at com.sap.engine.core.configuration.impl.PersistentDataInputStream.read(PersistentDataInputStream.java:135)
at com.sap.engine.bootstrap.Synchronizer.getFile(Synchronizer.java:245)
at com.sap.engine.bootstrap.Synchronizer.getFile(Synchronizer.java:216)
at com.sap.engine.bootstrap.Synchronizer.synchronizeFile(Synchronizer.java:151)
at com.sap.engine.bootstrap.Bootstrap.getOSDependentFiles(Bootstrap.java:683)
at com.sap.engine.bootstrap.Bootstrap.synchInstanceGlobals(Bootstrap.java:201)
at com.sap.engine.bootstrap.Bootstrap.makeUpdate(Bootstrap.java:968)
at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:947)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by: com.ibm.db2.jcc.am.DisconnectRecoverableException: [jcc][t4][2091][11332][3.65.77] Attempt to fully materialize lob data that is too
large for the JVM.
Disable data source property "fullyMaterializeLobData" for locator-based lob implementation. ERRORCODE=-4499, SQLSTATE=null
at com.ibm.db2.jcc.am.cd.a(cd.java:319)
at com.ibm.db2.jcc.am.cd.a(cd.java:404)
at com.ibm.db2.jcc.t4.ab.Dc(ab.java:2170)
at com.ibm.db2.jcc.t4.ab.d(ab.java:2155)
at com.ibm.db2.jcc.t4.bb.a(bb.java:185)
at com.ibm.db2.jcc.t4.bb.c(bb.java:31)
at com.ibm.db2.jcc.t4.q.a(q.java:32)
at com.ibm.db2.jcc.t4.i.readFetch_(i.java:263)
at com.ibm.db2.jcc.am.ResultSet.flowFetch(ResultSet.java:3796)
at com.ibm.db2.jcc.t4.c.a(c.java:887)
... 25 more
[Jun 6, 2014 4:09:38 PM ] [Bootstrap module]> Problem occurred while performing synchronization.
10444,1 Bot
Hi Guru's,
I am in situation where I have to configure Change request Management with Single Domain Controller in Solution Manager 7.1 SP11.
I have configured transport routes in ECC development system (000) to Integration , quality and production and now I want to add this configuration to Solution manager without domain link.
please help me on this greatly appreciated
thanks
HI All,
I am facing the below issue while executing the managed system wizard @ Bytecode adapter installation.
Error @ Managed system
Failed to create Introscope Agent Connector at: /usr/sap/SMD/SMDA98/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/connectors: - java.io.IOException: Cannot run program "null/bin/java" (in directory "/usr/sap/SMD/SMDA98/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/connectors"): java.io.IOException: error=2, No such file or directory.
Error @ Diagnostic agent level
| Jun 6, 2014 10:52:31 AM [Thread[Thread-19,5,main] | ] Error | Operation Failed : |
[EXCEPTION]
com.sap.smdagent.vmmanager.VMManagerException: Failed to get Instance properties - 48161
| at com.sap.smdagent.vmmanager.impl700.VMManager._getSettings(VMManager.java:170) | |
| at com.sap.smdagent.vmmanager.impl700.VMManager.getSettings(VMManager.java:156) | |
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | |
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | |
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | |
| at java.lang.reflect.Method.invoke(Method.java:597) | |
| at com.sap.smd.server.exec.asio.AsioInvocationHandler$1.call(AsioInvocationHandler.java:94) | |
| at com.sap.smd.server.util.concurrent.FutureResult$1.run(FutureResult.java:90) | |
| at com.sap.smd.server.exec.asio.AsioInvocationHandler$AsioRunner.run(AsioInvocationHandler.java:285) | |
| at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:46) | |
| at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:785) | |
| at java.lang.Thread.run(Thread.java:679) |
Caused by: java.lang.SecurityException: User is not authorized to access Configuration Manager.
| at com.sap.engine.services.configuration.ConfigurationRuntimeInterfaceImpl.checkAuthorization(ConfigurationRuntimeInterfaceImpl.java:62) | |
| at com.sap.engine.services.configuration.ConfigurationRuntimeInterfaceImpl.getConfigurationContext(ConfigurationRuntimeInterfaceImpl.java:48) | |
| at sun.reflect.GeneratedMethodAccessor392.invoke(Unknown Source) | |
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | |
| at java.lang.reflect.Method.invoke(Method.java:331) | |
| at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:159) | |
| at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336) | |
| at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201) |
1. As per standard note , patch levels are on sap recommended level only.
2. Created connector manually as per wily documentation , but still no use.
3. Given the permissions for temp,<SID>cluster etc.. as per sap notes and restarted all the services including sapstartsrv
4. Assigend SPML roles as suggested by note.
5. checked java environment and umask for diagnostic users , everything looks ok.
Checked couple of notes related to the above issue ,
1616058 - XSRF possible in SPML Services in AS Java
1820230 - Byte Code Adapter Installation error in Solution Manager 7.1 Managed System Configuration step Configure Automatically
1752441 - Introscope Agent Connector generation is done using JDK at: null
Hi Charm experts,
I work in Vendor company and one of our customer plans to start using Retrofit during ERP Ehp upgrade project.
We both like to know does someone have experience how Retrofit works in real world. If you are using Retrofit could you share your experience:
- does it help when you do dual development maintenance
- does it save time?
- Have you got problems with it?
- Do you recommend it to us?
- Who will use Retrofit, developer?
Thanks very much if you have time to write you experiences.
Best Regards,
Leena Nissilä
Hi Friends,
I am having question whether SOLMAN 7.1 SP4 is supporting SAP NetWeaver BW 7.4 for any configuration like EWA .
I do not find the option for SAP NW BW 7.4 while creating Logical Component in SOLMAN.
Thanks
Mukesh Khamparia
HI all,
One of my client is using SAP ECC 4.7 sytem which is quite older version. He wants to carry out Business Process Monitoring through Solution Manager. So is it possible to carry out Business process monitoring for such older ECC system?
Thanks,
Rutvik Upadhyay.