CRM support pack queries

Hello Support,
I have CRM 2005 in my landscape.It has the following patch level.
for ABAP stack it is at Stack 8
for JAVA stak it is at Stack 4.
And we are going for both (ABAP and JAVA) to STACK 15 which is latest.
I have the following query
1.) Can i directlly upgrade the JAVA stack from 4 to 15. Since i guess the present stack is too low.
Will we face any issue in doing so. What is the general practise?.
2.) For the ABAP stack , can i put the whole stack from 9 to 15 in the queue at a time or do one stack at a time.
Example
first upgrade it to 9 then 10 and so on
or directly in one queue to 15, so that we can have only one SPDD and SPAU.
3.) what is the main SNOTE for the CRM support pack.
4.) What all pre-requisite are ther perticulary for the CRM support packs.
Regards
Anthony

Hi mohit ,
Thanks for the reply ..
Yes , i will try convicing the client for going to latest -1 patches.
Now you have suggest that we must go for the ABAP to first SP12 and then to the latest -1.
I have the following query regarding this.
1.) How should i go to SP12 stack.
a.) by directly adding all the stacks till 12 in one go. (that is starting the queue from stack 8 to 12 ).
b.) going one stack at a time (i.e first will bring it to stack 9 then 10 then 11 and then 12)
c.) going component wise ( eg , first the BASIS till 12 , then the ABAP , then BW and so on.)
Regards
Anthony

Similar Messages

Urgent help CRM Support Pack Upg error sapevt.exe SAP_TRIGGER_RDDIMPDP

Hi All,
SP for CTS add-on in CRM qa 7.02 stuck. Please help as soon as possible. Aborted and tried to run in CI instance still stuck.
INFO: event SAP_IMPORT_START triggered successfully
START DISTRIBUTION OF DD-O CRQ S      20150424123453              DDIC         SAPCRMQAS 20150424123452988
START tp_getprots          CRQ S      20150424123453              DDIC         SAPCRMQAS 20150424123452988
STOP tp_getprots          CRQ S      20150424123456              DDIC         SAPCRMQAS 20150424123452988
STOP DISTRIBUTION OF DD-O CRQ S      20150424123456              DDIC         SAPCRMQAS 20150424123452988
INFO TBATG CONVERSION OF CRQ N      not needed                  DDIC         SAPCRMQAS 20150424123452988
INFO: apg locked (anticipatory program generation)
START MOVE NAMETABS        CRQ 6      20150424123456              DDIC         SAPCRMQAS 20150424123452988
START tp_getprots          CRQ P      20150424123456              DDIC         SAPCRMQAS 20150424123452988
STOP tp_getprots          CRQ P      20150424123457              DDIC         SAPCRMQAS 20150424123452988
STOP MOVE NAMETABS        CRQ 6      20150424123457              DDIC         SAPCRMQAS 20150424123452988
START MAIN IMPORT          CRQ I      20150424123457              DDIC         SAPCRMQAS 20150424123452988
INFO: apg unlocked (anticipatory program generation)
STOP MAIN IMPORT          CRQ I      20150424123518              DDIC         SAPCRMQAS 20150424123452988
INFO TBATG CREATION OF EN CRQ n      not needed                  DDIC         SAPCRMQAS 20150424123452988
INFO EXECUTION OF STANDAR CRQ 9      not needed: sxpra execution is switched off              DDIC         SAPCRMQAS 20150424123452988
INFO: event SAP_IMPORT_STOP triggered successfully
STOP imp all              CRQ   0000 20150424123519              DDIC         SAPCRMQAS 20150424123452988
START EXECUTION OF REPORTS CRQ R      20150424123525              DDIC         SAPCRMQAS
START tp_getprots          CRQ R      20150424123525              DDIC         SAPCRMQAS
START imp subset           CRQ        20150424123543              APServiceCRQ SAPCRQAPP
START DD IMPORT            CRQ H      20150424123543              APServiceCRQ SAPCRQAPP
STOP DD IMPORT            CRQ H      20150424123618              APServiceCRQ SAPCRQAPP
START DD ACTIVATION        CRQ A      20150424123618              APServiceCRQ SAPCRQAPP
WARNING: System CRQ. Warning.        20150424123635 :
ERROR:       The following call returned with exit code 7:
ERROR:         sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=CRQ
ERROR:       Background jobs cannot be started.
ERROR:       Please check trace file dev_evt.
WARNING:       (This warning is harmless if no further warnings follow.)
WARNING: System CRQ. Warning.        20150424123918 :
ERROR:       The following call returned with exit code 7:
ERROR:         sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=CRQ
ERROR:       Background jobs cannot be started.
ERROR:       Please check trace file dev_evt.
WARNING:       (This warning is harmless if no further warnings follow.)
START tp_getprots          CRQ J      20150424123918              APServiceCRQ SAPCRQAPP
START tp_getprots          CRQ R      20150424125606              DDIC         SAPCRMQAS
START tp_getprots          CRQ R      20150424130559              DDIC         SAPCRMQAS
START tp_getprots          CRQ R      20150424131530              DDIC         SAPCRMQAS
START tp_getprots          CRQ R      20150424132551              DDIC         SAPCRQAPP
Services file entries
sapmsCRQ 3600/tcp # SAP System Messaging Service Port
saphostctrl 1128/tcp # SAPHostControl over SOAP/HTTP
saphostctrl 1128/udp # SAPHostControl over SOAP/HTTP
saphostctrls 1129/tcp # SAPHostControl over SOAP/HTTPS
saphostctrls 1129/udp # SAPHostControl over SOAP/HTTPS
sapmsCRQ 3603/tcp # SAP System Message Server Port
sapmsSHDCRQ             3606/tcp #Upgrade shadow instance
sapdp06             3206/tcp #Upgrade shadow instance
sapgw06             3306/tcp #Upgrade shadow instance
Thanks,
Kavitha Rajan

Hi Kavitha,
Please refer to the KBAs specified below which can assist you in resolving the issue.
2074984 - RDDIMPDP job cannot be started due to duplicated services
1702079 - Background jobs cannot be started, exit code 7 in SLOG during Support Package/transport                  import
1913676 - Troubleshooting guide for Support Package / Add-Ons Installations errors during the main import 'IMPORT_PROPER' phase in SPAM or SAINT
Thank You.
Regards,
Deepika

What is the best way to apply Support Pack Stacks among satellite systems

Hi,
We have differenst systems liek R3, SCM,CRM,XI, BW and EP. We would like to apply teh support pack stack 12.
Which land sacpe need to be applied with the stack first?
R3 or other satellite systems? Is there any recommendation available from SAP on this?
Thanks in advance
Jnaneswar.P

Thanks for your reply Nick101. I see my example was oversimplified. When I say "multiple groups of contacts over multiple users" I'm really referring to N groups of contacts over N users.
So I need to add Fred, who can access and sync Bob's contacts, Sally's contacts, and Common contacts, as well as Fred's contacts. Can I do it with OS X server?
You mention you keep your and your partner's contacts administered locally. What keeps you from administering them through OS X server as well?
I am guessing this can all somehow be accomplished with multiple contact accounts, but I can't find any information on the web explicitly describing this.

Support Pack level for R/3 4.7 and BW 3.5 with SAP CRM2007

What should be the Support Pack level for R/3 4.7 and BW 3.5 with SAP CRM2007?
Regards,
Rajesh Banka

>
Rajesh Banka wrote:
> What should be the Support Pack level for R/3 4.7 and BW 3.5 with SAP CRM2007?
>
> Regards,
> Rajesh Banka
Hi Rajesh,
Please see the note '833438', it explains which pack is required in this scenario.
"You cannont connect ERP (R/3) releases lower than 4.6C to CRM 5.0.
All subsequent CRM releases (5.0 or higher) cannot be connected to ERP lower
than (R/3) 4.6C.
These types of system landscapes are not supported by SAP.
If you are using CRM 5.0, you must have implemented Plug-in PI 2004.1
Support Package 10 and, provided you have Basis Release 620 or higher, you
must import PI_BASIS 2005.1 in R/3. --> After you have imported these
plug-ins"
Thanks,
Nitin Sharma

Steps to configure solman to approve support packs

I have installed a Solution Manager System.
What are teh steps to be done to connect the SOLMAN system to SAP, so that i can login to SOLMAN to approve Support packs.

Hi Balaji,
             First you have to add the solution in the solution manager you can do
              that by transaction 'DSWP' .Then go to transaction smsy and add the
               R/3 systems which you have installed. In this transaction smsy,you
               have to add the server and the database by giving the necessary details
              then it will automatically creates the necessary rfc's.
              After doing this you have to go to Transaction 'SOLUTION_MANAGER'
              then click on the change management. Then go to maintainance
              optimizer. Here it will ask u which solution and then for which system u
               want to update.
              Revert back if you any queries.
Reward points if helpfull.
Regards,
Vamshi.

SPAM/SAINT support packs.

Hello,
I am updating SPAM?SAINT from 700/0023 to 700/0030. I have found the Support Pack version in Service Market place and when I did click Download it does not show up in my Download manager.
Is it because all these can only be downloaded from Solution Manager?
How do I go find the Spam/Saint Update in Solution Manager? I could not find it. Like we have the additional components in service market place, do we also have some kind of a tab in SOlman ?
Thanks
Druva

Druva,
>When I open the .sim file for Maintenance Optimizer in step 5 it says" enter the Maintenance ERP >system Date and then press enter". What does it actually mean.
Sorry but when I have approved SP downloads with SOLMAN, I had no .sim file to deal with.
So, I don't have an answer....
I just put my SPs in my download basket, then I go in SOLMAN in solution_manager transaction where I choose whatever solution we have (there is no control, I can approve CRM SPs with an BI solution...). Then When I use Download manager, I see all the approved SPs.
Regards,
Olivier

Will Kodo EJB3 support SQL queries standard?

Hello,
Will Kodo EJB3 support SQL queries (via
EntityManager.createNativeQuery(...))
in the Standard Edition since native queries are part of the API? Or will
that functionality require Enterprise Edition or Performance Pack?
thanks and good luck in the new year,
dave

Currently, SQL queries require the enterprise edition. Whether this
will change for Kodo 4 final has not been decided. The safest route
would be to assume that it will not change.

How to remove newly applied support pack.

Hi all,
i applied support pack in my R/3 4.7 server.
if any procedure for remove already applied support pack.
Regards.
Satish

thanks for the accolade
well... it´s true - and I highly appreciate it.
As you surely know, this IS a topic for SAP now for a
long time. Our hosting services face very similar
problems than customer landscapes.
This "landscape management" was - afaik - at least
one of the good intentions behind new products like
solution manager.
Anyhow - and this is my very personal view only and
of course in no way the view of SAP - these solutions
seem sometimes like "breaking a butterfly on a
wheel"...
Not only that, it doesn´t help in those 1000 basic tasks like those mentioned, it even makes it worse, much worser, than any sqlplus statement can do harm to your system. Without wanting to step on someones toes and with all appropriate respect: It´s a typical prove for an example of highly educated academical but theoretical people trying to solve practical problems - It´s getting better, no doubt, but there´s still a pretty long way to go before it will really help.
I´m of the opinion: If SAP has the strategy "everything is in the database", then please give us tools to maintain that data, if you don´t want people to do that manually using database tools. A "maintenance optimizer" guided procedure is certainly nothing, that really helps
The CCC-situation is also something I'm aware of.
Saving maintenance fee on this way does come with a
different kind of costs, that's for sure.
Full ack.
I also agree that for the overall solution at a
customers site it's not easy to get hold of a
comprehensive, current and well accessible
documentation. All I can say about that is, that
people working on this topic to make the
documentation more available to everybody.
The documentation is there, it´s just the vast amount of it killing brains.
If I as administrator need to keep all those things together, like dependencies between SPs, connections to other systems, codepage issues, printers and all that stuff you deal with every day, why can´t someone from SAP do the same? I mean, SAP expects administrators to do that, why don´t they do it on their own? There are of course tools to assist (System Landscape Manager, Self Diagnose etc.) - but they are all different, all have their own glitches and additional notes, patches etc. you have to deal with ON TOP of all to make them usable for you and they all have a pretty isolated view on an isolated problem.
As said before, all data is in the database, so use it
A big
obstacle with that is surely that customer landscapes
differ widely and nearly all aspects.
...driven by customers? certainly not. You as SAP say "We don´t extend SD functionality any more, use CRM" and "we don´t extend purchase in ERP any more, use SRM" - but they totally forget to keep the customers able to manage those systems, interdependencies, spoken plain technically without even digging into the applications themselves. Example:
- SRM needs a new SP
--> dependency to a specific the PI_BASIS in R/3
--> upgrading PI_BASIS needs a SPAM update
--> SPAM update needs a new tp/R3trans
--> tp/R3trans needs a new SQLDBC/Oracle/DB2/libdb 1,000,000 notes - and finding them is impossible, you will probably do the "try-and-error" approach here because there´s simply no chance to get that information at once - because of "isolated problems", isolated groups and abstraction over abstraction.
I'm used to think of SAP solutions as a kind of
factories. Although you can actually buy factories
today for many standard production processes it's
likely that the one you get will differ from every
other factory. Documenting such a factory will always
require individual changes.
I don´t think so.
If you have an ERP, CRM and SRM system, they have some sort of connections between them, this is common on all scenarios and is nothing, that is customer specific. On one side you "force" customers to use new products, on the other side you have no tools on side to REALLY´maintain those systems in a landscape aside from a Solution Manager software, that itself needs more maintenance, more mandays of configuration and more nerves to configure than all our systems together when done manually.
And there´s stil no "support package rollback" function
Markus

Difference Between Patches And Support Packs

Hi Experts,
I have one doubt,
1.... I want to Know Difference Between the Patches And the Support Packs
2...What is the Use of these Two??????????Is it Necessary to Apply these Two??
I asked This Question in Number of Queries...................
Please Let me Know All the Above Mentioned Queries
Regards
Khanna

Thank you for ur Quick Reply Satish.
And one more thing i want to clarify with you ...
Here i am going to Install XI 3.0 with WAS 6.20.
1......I installed j2sdk1.4.2_12
2......Installed Oracle 9i
Question1:- Do i need to Patch it to Oracle 9.2.0.7.0?????????
Or I can do it Later Also???????(At Present I dont Have it)
I Installed Up to Here.
3.....After this I wil Install WAS 6.20 with ABAP + JAVA Stack
( I have Doc for this).......
4....After this I wil Install XI 3.0
I think this is the XI Installtion.....
Question2:- Is this way of Installation is Correct?????
Question3:-After Completion of All these We should do the XI Post Installtion...Right?????
Question4:- When can we Apply the Support Packs And Patches??????? In the Post Installation Or After the Post Installation?????
Please Give me the Right Direction To Install the XI Successfully.......
Helpful ANS Wil be REWARD Points
Regards
Khanna

Difference between Support Stacks & Support Packs

Hi All,
Just the general question.
Difference between Support stacks & Support Packs? Please explain.
Thanks you all.

You can find all the products existing into CRM in the PeopleSoft Enterprise CRM 9 Product-to-PeopleBook Index, with the name of each linked Peoplebook to refer on the main CRM Peoplesoft documentation page.
And especially the PeopleSoft Enterprise CRM 9 Call Center Applications PeopleBook about Support and HelpDesk features.
Nicolas.

Support Pack Testing

Hi all ,
Can any one share or give their inputs on How the testing should be handled for BW support packs ? Basicaaly the test cases for both BW backend and BW frond end ?
Any input will be greatly appreciated.

I generally perform a triage process when looking thru the Notes. If you haven;t already implemented Hot Fix and High Priority notes, I would review them first. Then you make a pass through the other Notes:
- there may be components of BW that you don't use, e.g. SEM, MDX, or maybe notes for certain extractors you don't use. Those Notes can pretty much be set aside - you shouln't have to do anything else with them.
- identify any notes that require you to do something as a prerequisite, e.g. perhapss there is an RSADMIN entry you need to make, or some other option that must be set somewhere.
- identify any notes that require you to do something to take advantage of a new feature - this is different than the previous group of Notes that were required changes. These would be broken up into two groups, Notes that sound like they deleiver somehting you really need/want right away, and those Notes that provide features that are less critical.
- identify the Notes that sound likethey make change that are important to your installation.
- there are Notes that fix really obscure problems that you have not encounted, and thos go into a low priority group.
- you'll probably have some Notes that require some reseacrh to gauge their impact.
I think once you have grouped the Notes, you should start to be able to get a feel for what needs a thorough test and review, and what might only warrant a quick check to make sure it still seems to work.
You'll need to perform basic config testing - can I create/change InfoProviders, InfoObjects, queries etc.
Test a representative sample of qureies, wkbks - BEx and web.
Test daily data load preocess which should include all the regular functions such as compression, rollup, change run, etc.
Test important BW Admin functions that you might not run every day, e.g PSA deletion, RSRV, etc.
Also review any more recent Notes that have been published for a future SP to make sure there is nothing in them that is of concern.

Support Pack error in SPAM

Hi
I am importing a group of Support Packs into our DEV environment to bring the landscape uptodate, we are running NW04 on Windows 2003 64 bit & SQL Server 2000, I've updated to the latest SPAM and Kernel before the Support Packs.
When importing in SPAM I have used the calculate queue method, all looks ok, when I perform the import, in the phase TEST IMPORT i get the following error for Support Pack SP 12 for EA-FINSERV 5.00 :

Function MAP2I_BAPICMS_STR_MOV_INS_CRT (CMS_BUSISB104_MAPPI does not fit into the existing function group ((CMS_BUSISB10)
The only option I am given is to repeat the phase, I've repeated this a few times and get the same error on TEST IMPORT. I'm new to NW04 640 BASIS, but I know from running 4.6X system that you can re-run phases and quite often they work correctly 2nd time round, is it worth changing SPAM to not stop on test import errors ? as I know objects required can be in earlier support packs (i'm applying supports pack EA-FINSERV 5.00 08 to 11 as part of the queue before 12 which is giving me the error.
I've checked on OSS and cannot find any notes on this error/support pack.
Thanks.

nope, not tried with ignore test errors yet, wanted to check opinions here to see if thats the next step to try, or if there's anything else I could try ?

Error in JSPM Support Pack update

Hi,
i am in the process of doing java support packs form level 9 to 14.
I am doing 3 at a time
After the sap-jee support pack got deployed the server0 for j2ee is not starting.
Pls hlep
The following is the log of disp_server0
trc file: "F:\usr\sap\BWD\DVEBMGS01\work\dev_server0", trc level: 1, release: "700"
node name   : ID13786450
pid         : 7296
system name : BWD
system nr. : 01
started at : Tue Jun 17 16:30:40 2008
arguments       :
*       arg[00] : F:\usr\sap\BWD\DVEBMGS01\exe\jlaunch.exe*
*       arg[01] : pf=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
*       arg[02] : -DSAPINFO=BWD_01_server*
*       arg[03] : pf=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
*       arg[04] : -DSAPSTART=1*
*       arg[05] : -DCONNECT_PORT=3227*
*       arg[06] : -DSAPSYSTEM=01*
*       arg[07] : -DSAPSYSTEMNAME=BWD*
*       arg[08] : -DSAPMYNAME=WDBSSAPBWD01_BWD_01*
*       arg[09] : -DSAPPROFILE=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
*       arg[10] : -DFRFC_FALLBACK=ON*
*       arg[11] : -DFRFC_FALLBACK_HOST=localhost*
[Thr 4660] Tue Jun 17 16:30:40 2008
*[Thr 4660] *** WARNING => INFO: Unknown property [instance.box.number=BWDDVEBMGS01wdbssapbwd01] [jstartxx.c   841]*
*[Thr 4660] *** WARNING => INFO: Unknown property [instance.en.host=WDBSSAPBWD01] [jstartxx.c   841]*
*[Thr 4660] *** WARNING => INFO: Unknown property [instance.en.port=3200] [jstartxx.c   841]*
*[Thr 4660] *** WARNING => INFO: Unknown property [instance.system.id=1] [jstartxx.c   841]*
JStartupReadInstanceProperties: read instance properties [F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties]
-> ms host    : WDBSSAPBWD01
-> ms port    : 3900
-> OS libs    : F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs
-> Admin URL :
-> run mode   : safe
-> run action : UPGRADE
-> enabled    : yes
Used property files
-> files [00] : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
Instance properties
-> ms host    : WDBSSAPBWD01
-> ms port    : 3900
-> os libs    : F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs
-> admin URL :
-> run mode   : safe
-> run action : UPGRADE
-> enabled    : yes
Bootstrap nodes
-> [00] bootstrap            : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
-> [01] bootstrap_ID13786400 : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
-> [02] bootstrap_ID13786450 : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID13786400           : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
-> [01] ID13786450           : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
[Thr 4660] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 4660] JLaunchRequestQueueInit: create pipe listener thread
[Thr 6916] JLaunchRequestFunc: Thread 6916 started as listener thread for np messages.
[Thr 4836] WaitSyncSemThread: Thread 4836 started as semaphore monitor thread.
[Thr 4660] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
[Thr 4660] CPIC (version=700.2006.09.13)
[Thr 4660] [Node: server0] java home is set by profile parameter
*     Java Home: F:\java*
[Thr 4660] JStartupICheckFrameworkPackage: can't find framework package F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar
JStartupIReadSection: read node properties [ID13786450]
-> node name          : server0
-> node type          : server
-> node execute       : yes
-> jlaunch parameters :
-> java path          : F:\java
-> java parameters    : -Djco.jarm=1 -XX:MaxPermSize=256M -XX:PermSize=256M -XX:NewSize=171M -XX:MaxNewSize=171M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Dstartup.mode=SAFE -Dstartup.action=UPGRADE
-> java vm version    : 1.4.2_16-b05
-> java vm vendor     : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
-> java vm type       : server
-> java vm cpu        : amd64
-> heap size          : 1024M
-> init heap size     : 1024M
-> root path          : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\server0
-> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path       : F:\usr\sap\BWD\DVEBMGS01\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     : F:\usr\sap\BWD\DVEBMGS01\exe\jstartup.jar;F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar
-> shutdown class     : com.sap.engine.boot.Start
-> parameters         :
-> debuggable         : no
-> debug mode         : no
-> debug port         : 50121
-> shutdown timeout   : 120000
[Thr 4660] JLaunchISetDebugMode: set debug mode [no]
[Thr 6772] JLaunchIStartFunc: Thread 6772 started as Java VM thread.
[Thr 6772] [JHVM_PrepareVMOptions] use java parameters set by profile parameter
*     Java Parameters: -Xss2m*
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack   : 1048576 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -Djco.jarm=1
-> arg[ 4]: -XX:MaxPermSize=256M
-> arg[ 5]: -XX:PermSize=256M
-> arg[ 6]: -XX:NewSize=171M
-> arg[ 7]: -XX:MaxNewSize=171M
-> arg[ 8]: -XX:+DisableExplicitGC
-> arg[ 9]: -verbose:gc
-> arg[ 10]: -Xloggc:GC.log
-> arg[ 11]: -XX:+PrintGCDetails
-> arg[ 12]: -XX:+PrintGCTimeStamps
-> arg[ 13]: -Djava.awt.headless=true
-> arg[ 14]: -Dsun.io.useCanonCaches=false
-> arg[ 15]: -XX:SoftRefLRUPolicyMSPerMB=1
-> arg[ 16]: -XX:SurvivorRatio=2
-> arg[ 17]: -XX:TargetSurvivorRatio=90
-> arg[ 18]: -Djava.security.policy=./java.policy
-> arg[ 19]: -Djava.security.egd=file:/dev/urandom
-> arg[ 20]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[ 21]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[ 22]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[ 23]: -Dstartup.mode=SAFE
-> arg[ 24]: -Dstartup.action=UPGRADE
-> arg[ 25]: -Dsys.global.dir=F:\usr\sap\BWD\SYS\global
-> arg[ 26]: -Dapplication.home=F:\usr\sap\BWD\DVEBMGS01\exe
-> arg[ 27]: -Djava.class.path=F:\usr\sap\BWD\DVEBMGS01\exe\jstartup.jar;F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> arg[ 28]: -Djava.library.path=F:\java\jre\bin\server;F:\java\jre\bin;F:\java\bin;F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs;C:\Perl\site\bin;C:\Perl\bin;C:\Program Files\HP\NCU;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;F:\java\bin;F:\usr\sap\BWD\SYS\exe\uc\NTAMD64
-> arg[ 29]: -Dmemory.manager=1024M
-> arg[ 30]: -Xmx1024M
-> arg[ 31]: -Xms1024M
-> arg[ 32]: -DLoadBalanceRestricted=no
-> arg[ 33]: -Djstartup.mode=JCONTROL
-> arg[ 34]: -Djstartup.ownProcessId=7296
-> arg[ 35]: -Djstartup.ownHardwareId=T1648851106
-> arg[ 36]: -Djstartup.whoami=server
-> arg[ 37]: -Djstartup.debuggable=no
-> arg[ 38]: -Xss2m
-> arg[ 39]: -DSAPINFO=BWD_01_server
-> arg[ 40]: -DSAPSTART=1
-> arg[ 41]: -DCONNECT_PORT=3227
-> arg[ 42]: -DSAPSYSTEM=01
-> arg[ 43]: -DSAPSYSTEMNAME=BWD
-> arg[ 44]: -DSAPMYNAME=WDBSSAPBWD01_BWD_01
-> arg[ 45]: -DSAPPROFILE=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01
-> arg[ 46]: -DFRFC_FALLBACK=ON
-> arg[ 47]: -DFRFC_FALLBACK_HOST=localhost
-> arg[ 48]: -DSAPSTARTUP=1
-> arg[ 49]: -DSAPSYSTEM=01
-> arg[ 50]: -DSAPSYSTEMNAME=BWD
-> arg[ 51]: -DSAPMYNAME=WDBSSAPBWD01_BWD_01
-> arg[ 52]: -DSAPDBHOST=WDBSSDBBWD01
-> arg[ 53]: -Dj2ee.dbhost=WDBSSDBBWD01
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
[Thr 6772] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [server0]
[Thr 4752] Tue Jun 17 16:30:41 2008
[Thr 4752] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
[Thr 4752] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 4752] JLaunchISetClusterId: set cluster id 13786450
[Thr 4752] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 4752] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 7688] Tue Jun 17 16:30:52 2008
[Thr 7688] JLaunchIExitJava: exit hook is called (rc = -11113)
*[Thr 7688] ***********************************************************************
ERROR => The Java VM terminated with a non-zero exit code.*
Please see SAP Note 943602 , section 'J2EE Engine exit codes'*
for additional information and trouble shooting.*
[Thr 7688] JLaunchCloseProgram: good bye (exitcode = -11113)
trc file: "F:\usr\sap\BWD\DVEBMGS01\work\dev_server0", trc level: 1, release: "700"
node name   : ID13786450
pid         : 4560
system name : BWD
system nr. : 01
started at : Tue Jun 17 16:30:55 2008
arguments       :
*       arg[00] : F:\usr\sap\BWD\DVEBMGS01\exe\jlaunch.exe*
*       arg[01] : pf=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
*       arg[02] : -DSAPINFO=BWD_01_server*
*       arg[03] : pf=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
*       arg[04] : -DSAPSTART=1*
*       arg[05] : -DCONNECT_PORT=3227*
*       arg[06] : -DSAPSYSTEM=01*
*       arg[07] : -DSAPSYSTEMNAME=BWD*
*       arg[08] : -DSAPMYNAME=WDBSSAPBWD01_BWD_01*
*       arg[09] : -DSAPPROFILE=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
*       arg[10] : -DFRFC_FALLBACK=ON*
*       arg[11] : -DFRFC_FALLBACK_HOST=localhost*
[Thr 5300] Tue Jun 17 16:30:55 2008
*[Thr 5300] *** WARNING => INFO: Unknown property [instance.box.number=BWDDVEBMGS01wdbssapbwd01] [jstartxx.c   841]*
*[Thr 5300] *** WARNING => INFO: Unknown property [instance.en.host=WDBSSAPBWD01] [jstartxx.c   841]*
*[Thr 5300] *** WARNING => INFO: Unknown property [instance.en.port=3200] [jstartxx.c   841]*
*[Thr 5300] *** WARNING => INFO: Unknown property [instance.system.id=1] [jstartxx.c   841]*
JStartupReadInstanceProperties: read instance properties [F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties]
-> ms host    : WDBSSAPBWD01
-> ms port    : 3900
-> OS libs    : F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs
-> Admin URL :
-> run mode   : safe
-> run action : UPGRADE
-> enabled    : yes
Used property files
-> files [00] : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
Instance properties
-> ms host    : WDBSSAPBWD01
-> ms port    : 3900
-> os libs    : F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs
-> admin URL :
-> run mode   : safe
-> run action : UPGRADE
-> enabled    : yes
Bootstrap nodes
-> [00] bootstrap            : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
-> [01] bootstrap_ID13786400 : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
-> [02] bootstrap_ID13786450 : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID13786400           : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
-> [01] ID13786450           : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
[Thr 5300] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 5300] JLaunchRequestQueueInit: create pipe listener thread
[Thr 7140] JLaunchRequestFunc: Thread 7140 started as listener thread for np messages.
[Thr 6892] WaitSyncSemThread: Thread 6892 started as semaphore monitor thread.
[Thr 5300] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
[Thr 5300] CPIC (version=700.2006.09.13)
[Thr 5300] [Node: server0] java home is set by profile parameter
*     Java Home: F:\java*
[Thr 5300] JStartupICheckFrameworkPackage: can't find framework package F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar
JStartupIReadSection: read node properties [ID13786450]
-> node name          : server0
-> node type          : server
-> node execute       : yes
-> jlaunch parameters :
-> java path          : F:\java
-> java parameters    : -Djco.jarm=1 -XX:MaxPermSize=256M -XX:PermSize=256M -XX:NewSize=171M -XX:MaxNewSize=171M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Dstartup.mode=SAFE -Dstartup.action=UPGRADE
-> java vm version    : 1.4.2_16-b05
-> java vm vendor     : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
-> java vm type       : server
-> java vm cpu        : amd64
-> heap size          : 1024M
-> init heap size     : 1024M
-> root path          : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\server0
-> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path       : F:\usr\sap\BWD\DVEBMGS01\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     : F:\usr\sap\BWD\DVEBMGS01\exe\jstartup.jar;F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar
-> shutdown class     : com.sap.engine.boot.Start
-> parameters         :
-> debuggable         : no
-> debug mode         : no
-> debug port         : 50121
-> shutdown timeout   : 120000
[Thr 5300] JLaunchISetDebugMode: set debug mode [no]
[Thr 6352] JLaunchIStartFunc: Thread 6352 started as Java VM thread.
[Thr 6352] [JHVM_PrepareVMOptions] use java parameters set by profile parameter
*     Java Parameters: -Xss2m*
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack   : 1048576 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -Djco.jarm=1
-> arg[ 4]: -XX:MaxPermSize=256M
-> arg[ 5]: -XX:PermSize=256M
-> arg[ 6]: -XX:NewSize=171M
-> arg[ 7]: -XX:MaxNewSize=171M
-> arg[ 8]: -XX:+DisableExplicitGC
-> arg[ 9]: -verbose:gc
-> arg[ 10]: -Xloggc:GC.log
-> arg[ 11]: -XX:+PrintGCDetails
-> arg[ 12]: -XX:+PrintGCTimeStamps
-> arg[ 13]: -Djava.awt.headless=true
-> arg[ 14]: -Dsun.io.useCanonCaches=false
-> arg[ 15]: -XX:SoftRefLRUPolicyMSPerMB=1
-> arg[ 16]: -XX:SurvivorRatio=2
-> arg[ 17]: -XX:TargetSurvivorRatio=90
-> arg[ 18]: -Djava.security.policy=./java.policy
-> arg[ 19]: -Djava.security.egd=file:/dev/urandom
-> arg[ 20]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[ 21]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[ 22]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[ 23]: -Dstartup.mode=SAFE
-> arg[ 24]: -Dstartup.action=UPGRADE
-> arg[ 25]: -Dsys.global.dir=F:\usr\sap\BWD\SYS\global
-> arg[ 26]: -Dapplication.home=F:\usr\sap\BWD\DVEBMGS01\exe
-> arg[ 27]: -Djava.class.path=F:\usr\sap\BWD\DVEBMGS01\exe\jstartup.jar;F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> arg[ 28]: -Djava.library.path=F:\java\jre\bin\server;F:\java\jre\bin;F:\java\bin;F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs;C:\Perl\site\bin;C:\Perl\bin;C:\Program Files\HP\NCU;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;F:\java\bin;F:\usr\sap\BWD\SYS\exe\uc\NTAMD64
-> arg[ 29]: -Dmemory.manager=1024M
-> arg[ 30]: -Xmx1024M
-> arg[ 31]: -Xms1024M
-> arg[ 32]: -DLoadBalanceRestricted=no
-> arg[ 33]: -Djstartup.mode=JCONTROL
-> arg[ 34]: -Djstartup.ownProcessId=4560
-> arg[ 35]: -Djstartup.ownHardwareId=T1648851106
-> arg[ 36]: -Djstartup.whoami=server
-> arg[ 37]: -Djstartup.debuggable=no
-> arg[ 38]: -Xss2m
-> arg[ 39]: -DSAPINFO=BWD_01_server
-> arg[ 40]: -DSAPSTART=1
-> arg[ 41]: -DCONNECT_PORT=3227
-> arg[ 42]: -DSAPSYSTEM=01
-> arg[ 43]: -DSAPSYSTEMNAME=BWD
-> arg[ 44]: -DSAPMYNAME=WDBSSAPBWD01_BWD_01
-> arg[ 45]: -DSAPPROFILE=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01
-> arg[ 46]: -DFRFC_FALLBACK=ON
-> arg[ 47]: -DFRFC_FALLBACK_HOST=localhost
-> arg[ 48]: -DSAPSTARTUP=1
-> arg[ 49]: -DSAPSYSTEM=01
-> arg[ 50]: -DSAPSYSTEMNAME=BWD
-> arg[ 51]: -DSAPMYNAME=WDBSSAPBWD01_BWD_01
-> arg[ 52]: -DSAPDBHOST=WDBSSDBBWD01
-> arg[ 53]: -Dj2ee.dbhost=WDBSSDBBWD01
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
[Thr 6352] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [server0]
[Thr 5836] Tue Jun 17 16:30:56 2008
[Thr 5836] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
[Thr 5836] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 5836] JLaunchISetClusterId: set cluster id 13786450
[Thr 5836] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 5836] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 6128] Tue Jun 17 16:31:06 2008
[Thr 6128] JLaunchIExitJava: exit hook is called (rc = -11113)
*[Thr 6128] ***********************************************************************
ERROR => The Java VM terminated with a non-zero exit code.*
Please see SAP Note 943602 , section 'J2EE Engine exit codes'*
for additional information and trouble shooting.*
[Thr 6128] JLaunchCloseProgram: good bye (exitcode = -11113)
trc file: "F:\usr\sap\BWD\DVEBMGS01\work\dev_server0", trc level: 1, release: "700"
node name   : ID13786450
pid         : 8152
system name : BWD
system nr. : 01
started at : Tue Jun 17 16:31:10 2008
arguments       :
*       arg[00] : F:\usr\sap\BWD\DVEBMGS01\exe\jlaunch.exe*
*       arg[01] : pf=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
*       arg[02] : -DSAPINFO=BWD_01_server*
*       arg[03] : pf=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
*       arg[04] : -DSAPSTART=1*
*       arg[05] : -DCONNECT_PORT=3227*
*       arg[06] : -DSAPSYSTEM=01*
*       arg[07] : -DSAPSYSTEMNAME=BWD*
*       arg[08] : -DSAPMYNAME=WDBSSAPBWD01_BWD_01*
*       arg[09] : -DSAPPROFILE=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
*       arg[10] : -DFRFC_FALLBACK=ON*
*       arg[11] : -DFRFC_FALLBACK_HOST=localhost*
[Thr 6468] Tue Jun 17 16:31:10 2008
*[Thr 6468] *** WARNING => INFO: Unknown property [instance.box.number=BWDDVEBMGS01wdbssapbwd01] [jstartxx.c   841]*
*[Thr 6468] *** WARNING => INFO: Unknown property [instance.en.host=WDBSSAPBWD01] [jstartxx.c   841]*
*[Thr 6468] *** WARNING => INFO: Unknown property [instance.en.port=3200] [jstartxx.c   841]*
*[Thr 6468] *** WARNING => INFO: Unknown property [instance.system.id=1] [jstartxx.c   841]*
JStartupReadInstanceProperties: read instance properties [F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties]
-> ms host    : WDBSSAPBWD01
-> ms port    : 3900
-> OS libs    : F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs
-> Admin URL :
-> run mode   : safe
-> run action : UPGRADE
-> enabled    : yes
Used property files
-> files [00] : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
Instance properties
-> ms host    : WDBSSAPBWD01
-> ms port    : 3900
-> os libs    : F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs
-> admin URL :
-> run mode   : safe
-> run action : UPGRADE
-> enabled    : yes
Bootstrap nodes
-> [00] bootstrap            : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
-> [01] bootstrap_ID13786400 : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
-> [02] bootstrap_ID13786450 : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID13786400           : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
-> [01] ID13786450           : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
[Thr 6468] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 6468] JLaunchRequestQueueInit: create pipe listener thread
[Thr 7576] JLaunchRequestFunc: Thread 7576 started as listener thread for np messages.
[Thr 7312] WaitSyncSemThread: Thread 7312 started as semaphore monitor thread.
[Thr 6468] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
[Thr 6468] CPIC (version=700.2006.09.13)
[Thr 6468] [Node: server0] java home is set by profile parameter
*     Java Home: F:\java*
[Thr 6468] JStartupICheckFrameworkPackage: can't find framework package F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar
JStartupIReadSection: read node properties [ID13786450]
-> node name          : server0
-> node type          : server
-> node execute       : yes
-> jlaunch parameters :
-> java path          : F:\java
-> java parameters    : -Djco.jarm=1 -XX:MaxPermSize=256M -XX:PermSize=256M -XX:NewSize=171M -XX:MaxNewSize=171M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Dstartup.mode=SAFE -Dstartup.action=UPGRADE
-> java vm version    : 1.4.2_16-b05
-> java vm vendor     : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
-> java vm type       : server
-> java vm cpu        : amd64
-> heap size          : 1024M
-> init heap size     : 1024M
-> root path          : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\server0
-> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path       : F:\usr\sap\BWD\DVEBMGS01\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     : F:\usr\sap\BWD\DVEBMGS01\exe\jstartup.jar;F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar
-> shutdown class     : com.sap.engine.boot.Start
-> parameters         :
-> debuggable         : no
-> debug mode         : no
-> debug port         : 50121
-> shutdown timeout   : 120000
[Thr 6468] JLaunchISetDebugMode: set debug mode [no]
[Thr 7456] JLaunchIStartFunc: Thread 7456 started as Java VM thread.
[Thr 7456] [JHVM_PrepareVMOptions] use java parameters set by profile parameter
*     Java Parameters: -Xss2m*
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack   : 1048576 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -Djco.jarm=1
-> arg[ 4]: -XX:MaxPermSize=256M
-> arg[ 5]: -XX:PermSize=256M
-> arg[ 6]: -XX:NewSize=171M
-> arg[ 7]: -XX:MaxNewSize=171M
-> arg[ 8]: -XX:+DisableExplicitGC
-> arg[ 9]: -verbose:gc
-> arg[ 10]: -Xloggc:GC.log
-> arg[ 11]: -XX:+PrintGCDetails
-> arg[ 12]: -XX:+PrintGCTimeStamps
-> arg[ 13]: -Djava.awt.headless=true
-> arg[ 14]: -Dsun.io.useCanonCaches=false
-> arg[ 15]: -XX:SoftRefLRUPolicyMSPerMB=1
-> arg[ 16]: -XX:SurvivorRatio=2
-> arg[ 17]: -XX:TargetSurvivorRatio=90
-> arg[ 18]: -Djava.security.policy=./java.policy
-> arg[ 19]: -Djava.security.egd=file:/dev/urandom
-> arg[ 20]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[ 21]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[ 22]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[ 23]: -Dstartup.mode=SAFE
-> arg[ 24]: -Dstartup.action=UPGRADE
-> arg[ 25]: -Dsys.global.dir=F:\usr\sap\BWD\SYS\global
-> arg[ 26]: -Dapplication.home=F:\usr\sap\BWD\DVEBMGS01\exe
-> arg[ 27]: -Djava.class.path=F:\usr\sap\BWD\DVEBMGS01\exe\jstartup.jar;F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> arg[ 28]: -Djava.library.path=F:\java\jre\bin\server;F:\java\jre\bin;F:\java\bin;F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs;C:\Perl\site\bin;C:\Perl\bin;C:\Program Files\HP\NCU;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;F:\java\bin;F:\usr\sap\BWD\SYS\exe\uc\NTAMD64
-> arg[ 29]: -Dmemory.manager=1024M
-> arg[ 30]: -Xmx1024M
-> arg[ 31]: -Xms1024M
-> arg[ 32]: -DLoadBalanceRestricted=no
-> arg[ 33]: -Djstartup.mode=JCONTROL
-> arg[ 34]: -Djstartup.ownProcessId=8152
-> arg[ 35]: -Djstartup.ownHardwareId=T1648851106
-> arg[ 36]: -Djstartup.whoami=server
-> arg[ 37]: -Djstartup.debuggable=no
-> arg[ 38]: -Xss2m
-> arg[ 39]: -DSAPINFO=BWD_01_server
-> arg[ 40]: -DSAPSTART=1
-> arg[ 41]: -DCONNECT_PORT=3227
-> arg[ 42]: -DSAPSYSTEM=01
-> arg[ 43]: -DSAPSYSTEMNAME=BWD
-> arg[ 44]: -DSAPMYNAME=WDBSSAPBWD01_BWD_01
-> arg[ 45]: -DSAPPROFILE=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01
-> arg[ 46]: -DFRFC_FALLBACK=ON
-> arg[ 47]: -DFRFC_FALLBACK_HOST=localhost
-> arg[ 48]: -DSAPSTARTUP=1
-> arg[ 49]: -DSAPSYSTEM=01
-> arg[ 50]: -DSAPSYSTEMNAME=BWD
-> arg[ 51]: -DSAPMYNAME=WDBSSAPBWD01_BWD_01
-> arg[ 52]: -DSAPDBHOST=WDBSSDBBWD01
-> arg[ 53]: -Dj2ee.dbhost=WDBSSDBBWD01
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
[Thr 7456] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [server0]
[Thr 7648] Tue Jun 17 16:31:11 2008
[Thr 7648] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
[Thr 7648] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 7648] JLaunchISetClusterId: set cluster id 13786450
[Thr 7648] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 7648] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 7432] Tue Jun 17 16:31:21 2008
[Thr 7432] JLaunchIExitJava: exit hook is called (rc = -11113)
*[Thr 7432] ***********************************************************************
ERROR => The Java VM terminated with a non-zero exit code.*
Please see SAP Note 943602 , section 'J2EE Engine exit codes'*
for additional information and trouble shooting.*
[Thr 7432] JLaunchCloseProgram: good bye (exitcode = -11113)
trc file: "F:\usr\sap\BWD\DVEBMGS01\work\dev_server0", trc level: 1, release: "700"
node name   : ID13786450
pid         : 7280
system name : BWD
system nr. : 01
started at : Tue Jun 17 16:31:25 2008
arguments       :
*       arg[00] : F:\usr\sap\BWD\DVEBMGS01\exe\jlaunch.exe*
*       arg[01] : pf=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
*       arg[02] : -DSAPINFO=BWD_01_server*
*       arg[03] : pf=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
*       arg[04] : -DSAPSTART=1*
*       arg[05] : -DCONNECT_PORT=3227*
*       arg[06] : -DSAPSYSTEM=01*
*       arg[07] : -DSAPSYSTEMNAME=BWD*
*       arg[08] : -DSAPMYNAME=WDBSSAPBWD01_BWD_01*
*       arg[09] : -DSAPPROFILE=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
*       arg[10] : -DFRFC_FALLBACK=ON*
*       arg[11] : -DFRFC_FALLBACK_HOST=localhost*
[Thr 5400] Tue Jun 17 16:31:25 2008
*[Thr 5400] *** WARNING => INFO: Unknown property [instance.box.number=BWDDVEBMGS01wdbssapbwd01] [jstartxx.c   841]*
*[Thr 5400] *** WARNING => INFO: Unknown property [instance.en.host=WDBSSAPBWD01] [jstartxx.c   841]*
*[Thr 5400] *** WARNING => INFO: Unknown property [instance.en.port=3200] [jstartxx.c   841]*
*[Thr 5400] *** WARNING => INFO: Unknown property [instance.system.id=1] [jstartxx.c   841]*
JStartupReadInstanceProperties: read instance properties [F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties]
-> ms host    : WDBSSAPBWD01
-> ms port    : 3900
-> OS libs    : F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs
-> Admin URL :
-> run mode   : safe
-> run action : UPGRADE
-> enabled    : yes
Used property files
-> files [00] : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
Instance properties
-> ms host    : WDBSSAPBWD01
-> ms port    : 3900
-> os libs    : F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs
-> admin URL :
-> run mode   : safe
-> run action : UPGRADE
-> enabled    : yes
Bootstrap nodes
-> [00] bootstrap            : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
-> [01] bootstrap_ID13786400 : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
-> [02] bootstrap_ID13786450 : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID13786400           : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
-> [01] ID13786450           : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
[Thr 5400] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 5400] JLaunchRequestQueueInit: create pipe listener thread
[Thr 4264] WaitSyncSemThread: Thread 4264 started as semaphore monitor thread.
[Thr 4488] JLaunchRequestFunc: Thread 4488 started as listener thread for np messages.
[Thr 5400] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
[Thr 5400] CPIC (version=700.2006.09.13)
[Thr 5400] [Node: server0] java home is set by profile parameter
*     Java Home: F:\java*
[Thr 5400] JStartupICheckFrameworkPackage: can't find framework package F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar
JStartupIReadSection: read node properties [ID13786450]
-> node name          : server0
-> node type          : server
-> node execute       : yes
-> jlaunch parameters :
-> java path          : F:\java
-> java parameters    : -Djco.jarm=1 -XX:MaxPermSize=256M -XX:PermSize=256M -XX:NewSize=171M -XX:MaxNewSize=171M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Dstartup.mode=SAFE -Dstartup.action=UPGRADE
-> java vm version    : 1.4.2_16-b05
-> java vm vendor     : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
-> java vm type       : server
-> java vm cpu        : amd64
-> heap size          : 1024M
-> init heap size     : 1024M
-> root path          : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\server0
-> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path       : F:\usr\sap\BWD\DVEBMGS01\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     : F:\usr\sap\BWD\DVEBMGS01\exe\jstartup.jar;F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar
-> shutdown class     : com.sap.engine.boot.Start
-> parameters         :
-> debuggable         : no
-> debug mode         : no
-> debug port         : 50121
-> shutdown timeout   : 120000
[Thr 5400] JLaunchISetDebugMode: set debug mode [no]
[Thr 4872] JLaunchIStartFunc: Thread 4872 started as Java VM thread.
[Thr 4872] [JHVM_PrepareVMOptions] use java parameters set by profile parameter
*     Java Parameters: -Xss2m*
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack   : 1048576 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -Djco.jarm=1
-> arg[ 4]: -XX:MaxPermSize=256M
-> arg[ 5]: -XX:PermSize=256M
-> arg[ 6]: -XX:NewSize=171M
-> arg[ 7]: -XX:MaxNewSize=171M
-> arg[ 8]: -XX:+DisableExplicitGC
-> arg[ 9]: -verbose:gc
-> arg[ 10]: -Xloggc:GC.log
-> arg[ 11]: -XX:+PrintGCDetails
-> arg[ 12]: -XX:+PrintGCTimeStamps
-> arg[ 13]: -Djava.awt.headless=true
-> arg[ 14]: -Dsun.io.useCanonCaches=false
-> arg[ 15]: -XX:SoftRefLRUPolicyMSPerMB=1
-> arg[ 16]: -XX:SurvivorRatio=2
-> arg[ 17]: -XX:TargetSurvivorRatio=90
-> arg[ 18]: -Djava.security.policy=./java.policy
-> arg[ 19]: -Djava.security.egd=file:/dev/urandom
-> arg[ 20]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[ 21]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[ 22]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[ 23]: -Dstartup.mode=SAFE
-> arg[ 24]: -Dstartup.action=UPGRADE
-> arg[ 25]: -Dsys.global.dir=F:\usr\sap\BWD\SYS\global
-> arg[ 26]: -Dapplication.home=F:\usr\sap\BWD\DVEBMGS01\exe
-> arg[ 27]: -Djava.class.path=F:\usr\sap\BWD\DVEBMGS01\exe\jstartup.jar;F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> arg[ 28]: -Djava.library.path=F:\java\jre\bin\server;F:\java\jre\bin;F:\java\bin;F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs;C:\Perl\site\bin;C:\Perl\bin;C:\Program Files\HP\NCU;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;F:\java\bin;F:\usr\sap\BWD\SYS\exe\uc\NTAMD64
-> arg[ 29]: -Dmemory.manager=1024M
-> arg[ 30]: -Xmx1024M
-> arg[ 31]: -Xms1024M
-> arg[ 32]: -DLoadBalanceRestricted=no
-> arg[ 33]: -Djstartup.mode=JCONTROL
-> arg[ 34]: -Djstartup.ownProcessId=7280

We installed teh objects through SDM .
this solved the issue

Support Pack upgrade error in Import Phase

Hello,
Currently I am upgrading SCM system with Support pack level 12 to 20 . When i am applying Basis 12 to 20. I got an error in Import_Proper phase.
Could you please help me on this? I tried and still searching solution for this..But no luck...
Os is : AIX and
Log File: /usr/sap/trans/log/SAPIB70013.xxx
Main import
Transport request : SAPKB70013
System : xxxx
tp path : tp
Version and release: 372.04.71 700
child process 934006 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function: db_report_interface
fcode: CLOSE_LINE_MODE
tabname: SOURCE
len (char): 40
key: CL_OBJECT_COLLECTION==========CT
retcode: 1
SQL error -913 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
child process 1212554 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function: db_report_interface
fcode: CLOSE_LINE_MODE
tabname: SOURCE
len (char): 40
key: CL_WDR_APPLICATION_WINDOW=====CT
retcode: 1
SQL error -913 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
child process 1171520 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function: db_report_interface
fcode: CLOSE_LINE_MODE
tabname: SOURCE
len (char): 40
key: CL_WDY_MD_EVENT_SOURCE========CI
retcode: 1
SQL error -913 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
child process 1331412 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function: db_xrtab
fcode: RT_MI_LOAD
tabname: ECSCR_DATA
len (char): 106
key: EC_TEST_DATA 00000000P10 IECATTDEFAULT
retcode: 1
SQL error -904 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
insert / update sequence failed due to an error in DBI.
maybe there's a concurrent process which inserted this table entry at the same time.
insert / update sequence failed due to an error in DBI.
maybe there's a concurrent process which inserted this table entry at the same time.
child process 1310922 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function: db_xrtab
fcode: RT_MI_END
tabname: WDY_APP_PROPERTY
len (char): 64
key: DEMO_UIEL_DROPDOWN_BY_IDX DEMO_VIEW
retcode: 1
SQL error -904 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
import portion 018446 - 999999 not imported because the child processes died for unknown reason
child process 1310924 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function: db_report_interface
fcode: CLOSE_LINE_MODE
tabname: SOURCE
len (char): 40
key: CL_WDY_MD_OUTGOING_EVENT======CT
retcode: 1
SQL error -913 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
child process 1286192 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function: db_xrtab
fcode: RT_MI_LOAD
tabname: ECSCR_DATA
len (char): 106
key: EC_TEST_DATA 00000000P10 IECATTDEFAULT
retcode: 1
SQL error -904 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
import portion 009158 - 018411 not imported because the child processes died for unknown reason
import portion 018412 - 018527 not imported because the child processes died for unknown reason
import portion 018528 - 999999 not imported because the child processes died for unknown reason
sap_dext called with msgnr 1:
db call info -
function: db_xrtab
fcode: RT_MI_LOAD
tabname: ECSCR_DATA
len (char): 106
key: EC_TEST_DATA 00000000P10 IECATTDEFAULT
retcode: 1
SQL error -904 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
Main import
End date and time : 20100909034914
Ended with return code: ===> 12 <===
 | ######################################
Thanks and Regards,
Sankar
SAP BASIS Consultant

Hi,
Thanks for you reply. I restarted import but no luck still. I activated some object also not working. when i call SPAM it is not going to the SPAM pager. Showing dump...
Runtime Errors CALL_FUNCTION_NOT_FOUND
Except. CX_SY_DYN_CALL_ILLEGAL_FUNC
Date and Time 10.09.2010 09:41:37
Short text
 Function module "POSS_UIREQ_OPT_SUBMIT" not found.
What happened?
 The function module "POSS_UIREQ_OPT_SUBMIT" is called,
 but cannot be found in the library.
 Error in the ABAP Application Program
 The current ABAP program "SAPLSTXC" 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_DYN_CALL_ILLEGAL_FUNC', was
 not caught in
 procedure "OPEN_FORM" "(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 program "SAPLSTXC" contains the CALL FUNCTION statement.
 The name of the function module to be called is "POSS_UIREQ_OPT_SUBMIT".
 No function module exists with the name "POSS_UIREQ_OPT_SUBMIT".
 All function modules are listed in the Function Library (SE37).
Possible reasons:
a) Wrong name specified. Pay particular attenti
 upper/lower case and underscores ("_").
 or
b) Transport error
c) In the case of an enqueue/dequeue module,
 the lock object may not have been activated
 (ABAP/4 Dictionary).
When i tried to check function module it is not there..
Could you please help on this?
Regards,
Sankar Basis Consultant

BSI Tax Factory Upgrade:HR Support packs

Hi All,
We are starting with upgrade of BSI tax Factory from 8.0 to 9.0. And as per SAP main note '1469858' for upgrade, the support
pack required is 'HRSP61' but we currently have 'HRSP59'. Also, CLC 61 was applied for 2010 year end activities.
So, with CLC 61 present, would it be possible to upgrade to 9.0 without upgrading to HRSP 61 ?
In other words I want to confirm if CLC 61 includes the Tax Factory 9.0 updates.
Thanks,
Avinash

Hi Avinash,
I just updated relevant information for your query in the following thread:
[*BSI 8.0 becomes obsolete August 31st 2011, 9.0 troubleshooting guide here*;
Kind regards,
Felipe

CRM support pack queries

Similar Messages

Maybe you are looking for