Support Pack PI_BASIS 'on hold'
Hi All,
I am trying to apply PI_BASIS 2006_1_700 to my Solution Manager 4.0.
I applied the delta ackage thru SAINT.
I have Background WP 'RFC on Hold' state error ( SM 50 ) repeatedly.
Details of the Hold WPs shows the line " waiting for " RFC ..for the Report SAPLSTPA ..
SM66 says CPIC STOPPED.
And ST22 shows no dump, SM21 shows no Err Msg.
There are also 2 Table Locks in SM12 ( PAT01 , CWBNTHEAD )
The Conversation Id shown in SM50 Details of WP ( which is on Hold State ) has no err in smgw.
Since it is at DDIC ACTIVATION PHASE, I can't reset the queue through the SPAM/SAINT.
Now I'm stuck in the DDIC activation phase.
When I go to sm37 I see the job
OCS QUEUE IMPORT Active with Duration 100,725 secs.
I had restarted the import but still it is showing the same status.
It is not writing any logs (SLOG /ALOG)
This has been the status for the past 2 days now !
Any Ideas? Shud I reset the queue? If yes, then how?
Hi,
First step you need to take care is that if system is in production dont reset queue.Contact SAP because at this time your system is inconsistent and only SAP will help you.
But if you still want to reset queue then follow this link [CLICK HERE|http://*************************/2008/11/troubleshoot-with-spam-at-your-own-risk.html]
But do it at you own risk.SAP will never help you if you ask them after doing all these activities.
Hope it will help you...
Regards,
Gagan Deep Kaushal
Similar Messages
-
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.
Satishthanks 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 -
SB Audigy Series Support Pack 5.3 (02/24/2015)
This software/driver pack is unofficial, not supported by Creative Labs.
Use it at your own risk.
Supports any model of the following Sound Blaster cards (based on Emu10kx DSP):
- Audigy
- Audigy 2
- Audigy 2 ZS
- Audigy 4
- Audigy 5/RX
For Audigy SE/LS/Value and Live! 24-bit cards, click here for a compatible version.
Operating systems supported:
32-bit and 64-bit editions of Windows 10 / 8.1 / 8 / 7 SP1 / Vista SP2 / XP SP3
Included in the pack:
- Audigy series driver 3.01.0039 (Windows Vista or later) (**)
- Audigy series driver 2.09.0016 (Windows XP)
- ALchemy 1.45.03
- Audio Console 1.41.00
- DDL and DTS Connect License Activation 1.00.04 (*)
- Dolby Digital Live Pack 3.03.08 (*)
- EAX Console 3.00.60 (Windows Vista or later)
- EAX Console 3.00.59 (Windows XP only)
- Feature Mode Selection Utility 2.10.07
- Graphic Equalizer 2.10.01
- MediaSource DVD-Audio Player 2.00.78 (***)
- SoundFont Bank Manager 3.21.02
- Speaker Calibrator 1.60.14 (Windows XP only)
- Speaker Settings 2.10.05 (Windows Vista or later)
- Speaker Settings 2.10.04 (Windows XP only)
- Surround Mixer 4.00.76 (Windows XP only)
- THX Setup Console 2.20.08 (Windows XP only)
(*) Purchase and activation required, more info at http://buy.soundblaster.com.
(**) - For Audigy 5/RX (SB1550) and Audigy 4 Series II (SB0612) this driver also supports Windows XP.
(***) - Requires Audigy 2, Audigy 2 ZS ou Audigy 4
Does this driver improve sound quality or performance Are there any tweaks ?
No, this driver does not improve sound quality nor increase performance.
No, there are no tweaks.
If someone states that its driver improves sound quality and performance, you are being fooled, cheated.
It is even worse that the so called tweaks come from a person who is not EVEN technically acknowledged, does NOT know anything about Windows internals, software engineering and sound fidelity that all audiophiles always look for.
If you "feel" the sound better, that is the infamous placebo effect and there is no real proof that any tweaks work.
In fact, I have yet to see a driver that states in its release notes that it improves sound quality.
I've disassembled about every single .SYS driver, .DLL libraries and .EXE executables and found nothing.
There are some undocumented registry values, but nothing related to sound quality or performance.
Would the so called tweaks even exist, they would be in my Support Packs, you can bet that.
Fixes and improvements:
- Fixed Audigy 5/RX support.
- Readded "EndPoint Utility" to enable the use of other digital devices to output Dolby Digital Live encoded audio.
- Fixed driver installation issues on Windows 10.
- Fixed Audigy "1" or Audigy 2 mute issue.
- Audigy RX is now fully supported.
- EAX Console now works on Windows Vista or later.
- Karaoke effects now work properly on Windows Vista or later, just use EAX Console to enable them. Effects will only be applied to the Microphone input.
- Sound Blaster Audigy Control Panel now available for all cards, but it lacks many settings available on Audio Console, so use the later.
- Added instructions on how to install the Gameport.
- Fixed missing speaker settings strings on Windows XP when DDL is enabled.
- Improved driver installation, less confirmation prompts.
- Improved setup procedure and scripts.
- Removed Encode switcher for now, only DDL is available.
- Installation now customizable, select what you want to install.
- New integrated Post Driver Install Helper tweaks the driver without tampering certificate.
- CMSS2 is now available.
- OpenAL 64-bit support.
- Dolby Digital Live now works on Windows 8.1 (update 1). Creative Audio Service was not being installed on that OS.
- Special FX, Advanced EQ, Studio and Custom presets now available on Windows Vista or later.
- Audio Console does not crash anymore on non-English localized installs. Localized resources for Online Karaoke tab were missing; added mostly localized Korean and Chinese (Traditional) resources.
- Online Karaoke page is available for all Audigy cards on Windows Vista or later; this is NOT a new feature, but an easier way to configure the Microphone.
- EAX Settings for Windows Vista or later includes EAX Studio, a fancy version of EAX Control Panel, no changes in functionality, except the Test button now works.
- Added fully localized Korean and Chinese (Traditional) resources for EAX Studio, which were missing.
Undocumented fixes by Creative (not listed in the release notes):
- Headphone mode now sticks and does not revert automatically to Speakers mode on Windows Vista or later.
- Special FX, Advanced EQ and Studio presets were not working on Windows Vista or later.
Release Notes:
IMPORTANT: Driver uninstall on Windows Vista or later
The included driver for Windows Vista or later has a bug that causes a stop (blue screen) error when unloaded by disabling the Audigy or uninstalling the driver.
To workaround this issue, run the KillDrv.exe utility included and restart when asked to do so. Proceed normally and uninstall all the software or only the driver.
If you have previously installed the Audigy 5/RX driver, you MUST run this utility.
As the KillDrv verify the driver version installed, running it won't do any harm, even if the driver version is not affected.
HOW TO INSTALL THE GAMEPORT DRIVER
You can find a Gameport\ReadMe.htm file in the folder where you unpacked the Support Pack.
Just follow the steps shown in the screenshots.
WINDOWS 8.1 OR LATER DOES NOT SAVE SETTINGS
- Configure all settings and shutdown. Your settings will be saved.
- This does not work if you disable Fast startup permanently or temporarily (by holding the Shift key while shutting down).
- On Windows 10 you need to run the application with Administrator privileges (right-click and choose Run as Administrator). This is valid for all applications used to configure the card.
OpenAL 2D benchmark in RightMark 3DSound crashes your system
The included driver for Windows Vista or later has a bug that crashes your system if you run the OpenAL 2D benchmark using 63 buffers.
No problem With 62 or fewer buffers.
OpenAL 3D and OpenAL 3D + EAX benchmarks are not affected.
Details: DRIVER_IRQL_NOT_LESS_OR_EQUAL (0x000000D1) - ctoss2k.sys
There is no DirectSound hardware acceleration on Windows XP 64-bit (x64) with 4GB RAM or more
The Audigy driver does not support 64-bit addressing, disabling the DirectSound hardware acceleration and causing multichannel sound to be played only in the stereo channels (front left/right).
Workarounds:
- install the 32-bit (x86) version of Windows XP.
- limit to less than 4GB the amount of RAM available to Windows.
- enable the "Memory Hole" setting in the BIOS Setup, if your motherboard supports it.
- install and use Creative ALchemy to convert the DirectSound API calls into OpenAL, which is not affected by this issue.
Karaoke effects make the audio play in mono
You can avoid this issue by using EAX Console to enable Karaoke effects. Audio Console is affected by the issue.
Optionally, follow the steps below.
Open EAX Settings, select a Karaoke effect, then click the Edit button.
Click on the Source (Wave) tab and change the Original sound to 100% and Pitch Shift to 0%. Click the Save environment button.
Repeat the steps for all Karaoke effects.
These changes will be valid only for the current speaker configuration. If desired, repeat the same process for each speaker configuration.
MediaSource DVD-Audio Player system requirements
- 32-bit edition of Windows XP or later
- any Audigy 2, Audigy 2 ZS or Audigy 4 card
Built-in Decoder on Windows Vista or later
To use the built-in decoder, make sure it is enabled in Audio Console.
Select "SPDIF Out (Creative SB Audigy (WDM))" as the output device of your player and then configure the AC3/DTS filter to send the stream through SPDIF.
When you restart your computer, the Tone settings (Bass and Treble) are not applied.
Just readjust one of the controls one time per boot.
Equalizer and EAX effects are not available when using OpenAL or ALchemy
Only Tone (Bass and Treble) and CMSS 3D (CMSS, CMSS2 and Stereo Surround) features are available.
There is no sound in games with OpenAL support
Disable Advanced EQ and Special FX by selecting "No effect" before running the game or program.
Equalizer settings are not applied after using OpenAL or ALchemy
After you run a game with OpenAL support or using Creative ALchemy, the Equalizer settings are applied.
Just run Equalizer and the saved setting is loaded automatically.
Tone settings are lost when speaker configuration is changed
Bass and treble settings reset to their default values when speaker configuration is changed.
Download:
Filename: Audigy_SupportPack_5_3.exe
File size: 120 MB
CRC32 hash: 76110093
SHA- hash: 1001EB673EAF532EA10B2C986F1F4046D52F6771
Mirrors: Google Drive
All files are property of Creative Technology Ltd, unless otherwise noted.Originally Posted by Dave_
Please help me daniel_K. All I want to do is send 5.1 sound to my Sony amp (SRT-DH520). I have purchased a new SB Audigy 5/Rx [CFC0] and when I install from your pack everything looks great until I toggle the "Enable Dolby Digital Live". Then I get no sound output at all. And when I try to test the signal through the audio settigs it says "The device is being used by another application. Please close any devices that are playing audio to this device". I cant think of any other device running. When I untick the Enable Dolby Digital Live I can get stereo sound again. The DDL is authenticated. The cable is working. The amp is fine. I neeeeed help....
Unfortunately I don't have a sample card to test personally and don't know anyone with an Audigy 5/RX.
Anyway, I have a suggestion.
Run EndPtUtl.exe found in the Audio Console installation folder.
If the issue still persists, try to use the Digital Output (Coaxial/Optical) of another device, provided that you have any on your computer.
EndPtUtl.exe enables the use of any device for outputting encoded audio. -
Suggested Support Pack Level for ECC 6.0 Upgrade - Target
Hi ,
Can someone give us the suggested support pack level for the ECC 6.0 system after the upgrade.
Our current patch level is:
SAP_ABA 700 0012 SAPKA70012
SAP_BASIS 700 0012 SAPKB70012
PI_BASIS 2005_1_700 0012 SAPKIPYJ7C
ST-PI 2005_1_700 0003 SAPKITLQI3
SAP_BW 700 0014 SAPKW70014
SAP_AP 700 0009 SAPKNA7009
SAP_APPL 600 0010 SAPKH60010
SAP_HR 600 0013 SAPKE60013
EA-IPPE 400 0008 SAPKGPID08
EA-APPL 600 0008 SAPKGPAD08
EA-DFPS 600 0008 SAPKGPDD08
EA-FINSERV 600 0008 SAPKGPFD08
EA-GLTRADE 600 0008 SAPKGPGD08
EA-HR 600 0013 SAPKGPHD13
EA-PS 600 0008 SAPKGPPD08
EA-RETAIL 600 0008 SAPKGPRD08
FINBASIS 600 0008 SAPK-60008INFINBASIS
ECC-DIMP 600 0008 SAPK-60008INECCDIMP
ERECRUIT 600 0008 SAPK-60008INERECRUIT
FI-CA 600 0008 SAPK-60008INFICA
FI-CAX 600 0008 SAPK-60008INFICAX
INSURANCE 600 0008 SAPK-60008ININSURANC
IS-CWM 600 0008 SAPK-60008INISCWM
IS-H 600 0008 SAPK-60008INISH
IS-M 600 0008 SAPK-60008INISM
SEM-BW 600 0008 SAPKGS6008
IS-OIL 600 0008 SAPK-60008INISOIL
IS-PS-CA 600 0008 SAPK-60008INISPSCA
IS-UT 600 0008 SAPK-60008INISUT
LSOFE 600 0008 SAPK-60008INLSOFE
IRMIPM 30B 0005 SAPK-30BI7INIRM
IRMGLB 30B 0005 SAPK-30BG7INIRM
ST-A/PI 01K_ECC600 0000 -
GSCDMC 600 0001 SAPK-60001INGSCDMC
RCMGT 601 0001 SAPK-60101INRCMGT
Thanks
SenthilHi Senthil,
of course it is always recommended to use the newest Support Package Stack,
but if your system (your business processes) are working fine, I would recommend you to
import support package only then when you have an error or you want to have a special fiunctionality.
Some customers play support packages into the system only twice a year, because the business processes
should be tested after the sp import.
Kind regards
Imre Takácsi-Nagy
Senior Support Consultant II.
SAP Global Support Center Austria
Netweaver WEB Application Server ABAP / JAVA -
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 -
4.7 x 2.00 Support Pack Question
Hello,
I am attempting to apply upgrade from PI_BASIS 2004_1_620 to PI_BASIS 2005_1_620 on an R/3 Enterprise 4.7 x 2.00 System.
Using the SAINT tool, I am bringing in the SAPKINBB7A OCS package. I have tried the following queues:
SAPKINBB7A by itself
SAPKINBB7A with follow-up patches SAPKIPYJ51 to 3
SAPKINBB7A with follow-up patches SAPKIPYJ51 to 7
Each time, I get an IMPORT_PROPER failure:
Error in phase: IMPORT_PROPER
Reason for error: TP_STEP_FAILURE
Return code: 0012
Error message: OCS Package ALL, tp step "N", return code 0012
The error has the symptom of notes 794802 and 751864. However, the 751864 code is already present in the system before I begin.
If anyone has seen this particular set of circumstances, I would appreciate the input.
Regards,
JohnHello,
My SPAM/SAINT is updated to the latest level (patch 20). My Kernel is patched up to level 129.
I tried the Extras >> Ignore generation errors. However, this simply returned the message, "No generation errors found".
After further review of the logs, etc. I came across note 903242 which described the problem perfectly. After applying the suggested solution, the support packs proceeded to the next step.
Thank you for your help.
Regards,
John -
Hello Experts,
I am new to this fascinating world of SAP BASIS professionals and here I am again with my fourth issue. Please give your valuable advise.
The Scenario:
I have an ECC 6.0 ABAP+JAVA system installed. Recently I have upgraded 3 of it's software components, which are follows:
PI_BASIS 2005_1_700 Level 0009----to-----Level 0010.
SAP_BASIS 700 Level 0009----to-----Level 0010.
SAP_ ABA 700 Level 0009----to-----Level 0010.
My Question/Issue:
I have upgraded the above to Level 0010, but now I want to revert them back to Level 0009 (initial level), that is, I want to UNDO the SUPPORT PACK application. Is this possible? If this is possible, then how?
Please Note: I have not taken any database backup before applying this patches, furthermore, my database is in NO ARCHIVE LOG mode.
Help me....Hello,
Since you have no backup available, the only solution is re-installing the system.
"Fooling" the system by changing some of the PAT* tables is not a good proposition.
There remain a lot of open questions with this approach.
How are you going to revert your repository to the previous level ?
Support packages not only import source code corrections but also modifications to the repository (new fields in tables, extend data elements, ...) resulting in conversions of your repository.
By fooling the system you risk serious conflicts weeks or even months later, are you going to take that risk ?
I hope this can help you.
Wim -
hi all,
can any one give some info and the link where I can find information about BW support pack 13, 14 ,15hi ajay,
i think these oss notes should sufficient, they contain info what error corrected, possible new errors, new features added in the support packages. do you need other info ?
Symptom
Support Package 13 for BW Release 3.5.
Other terms
SAPBWNEWS, Support Packages for 3.5, BW 3.5, BW 3.50, BW Patches
Solution
This note contains the SAPBWNews for Support Package 13 for BW Release 3.5. This note lists all the notes that describe the corrections or enhancements contained in Support Package 13 (SAPKW35013). This note is updated as soon as other notes are added.
The information is divided into the following areas:
Manual actions that may be necessary:
Factors you must take into account when you import the Support Package
Errors that may occur after you import the Support Package
For general information:
This Support Package corrects the following errors
Enhancements contained in this Support Package
Support Package 13 for BW 3.5 corresponds to the technological status of Support Packages 28 for BW 3.0B (SAPBWNews 783170) and 22 BW 3.1 Content (SAPBWNews 783252).
Also see the following release and information notes
Support Package 13 SAP_UDI 350 Note 765119
Factors you must take into account when you import the Support Package:
Note that Support Package 4 is required as of NetWeaver Support Package Stack 14, that is, BW Server Support Package 14 PI_BASIS 2005. For information about upgrading to PI_BASIS 2005, refer to Note 821148.
Errors that may occur after you import the Support Package:
Querys on MultiCubes in read mode A. For information about this, read Note 896066.
Data is missing in individual aggregates.
The error is not corrected by reconstructing the aggregate. For information about this, read Note 898508.
When you display a note in the Note Assistant, the following error may occur: 'Output device A000 is not defined'. For more information, see Note 868905.
Under certain circumstances, the MultiProvider F4 help does not use aggregates that have also been used during the query execution. For more information, see Note 870557.
When you execute a MultiProvider query, a termination may occur. For more information, see Note 870505.
When you go from one query to another query or to a Web template, the system fills value variables for compound characteristics, which you can also change during query navigation, with the initial value ("#"). For more information, see Note 867616.
In certain situations when you execute a query, a termination (GETWA_NOT_ASSIGNED in SAPSRRK0 field symbol <L_S_SNID>) may occur or data may be missing from columns or structural elements. For more information, see Notes 851086 and 848340.
Some columns or structure items may remain empty in a query. For more information, see Note 863745.
When you check a query, the system may issue error message Brain A 039 (telling you that node &3 &4 does not exist in hierarchy &2 for the InfoObject &1), although the node exists and you can execute the query. For more information, see Note 855258.
A query with an exclude in the dynamic filter may not display any data under certain conditions. For more information, see Note 856495.
In some very exceptional cases, a query may terminate with error message X299(BRAIN) System error in program SAPLRRKH and form SELDER_INTERSECT_BUF-01. For more information, see Note 851754.
You can execute a query that does not use any key figures even if you do not have the necessary authorizations. For more information, see Note 856144.
List of notes:
868905
870557
870505
867616
851086
848340
855258
856495
851754
856144
This Support Package corrects the following errors:
Corrections in the end user technology area:
When you called the filter dialog in the BEx Broadcaster and the ad-hoc Query Designer, the system issued error message CX_SY_REF_IS_INITIAL. For more information, see Note 857393.
Corrections in the OLAP technology area:
In a query, some columns or structural elements remained empty. For more information, see Note 848340.
You were no longer able to create authorizations (profiles) in Transaction RSSM if the user name did not contain a period. The system ignored the authorization assignment using Transaction PFCG (roles) and the generation from ODS. For more information, see Note 849194.
When you executed a query, the ETWA_NOT_ASSIGNED runtime error occurred in the SAPSRRK0 program in the APPEND_KHANDLE_1 form; field symbol <L_S_SNID>. For more information, see Note 851086.
When you executed a query, it terminated with the X299(BRAIN) error message telling you that there was a system error in the SAPLRRKH program and the SELDER_INTERSECT_BUF-01- form. For more information, see Note 851754.
A query that contains both a fixed and dynamic restriction for a characteristic and that is evaluated on a remote cube may terminate (program SAPLRRK0; form CHECK_NAV_INIT_NEW-03- ). For more information, see Note 849969.
Corrections in the Warehouse Management area:
After you imported Support Package 12, it took a very long time to create and delete InfoPackages in a content creating BW system because Note 844739 delivered corrections for writing shadow InfoPackages, and these corrections may run for a relatively long time in several source systems that are connected to BW as well as several existing shadow InfoPackages. For more information, see Note 847030.
When you loaded data, data sometimes disappeared. Refer to Note 849857 for further information.
If you executed a where-used list for an InfoObject in the D version, a termination sometimes occurred. For more information, see Note 844007.
When you deleted master data, a termination sometimes occurred. For more information, see Note 856546.
Enhancements delivered with this Support Package:
Also refer to the Documentation Enhancements on the SAP Service Marketplace (http://service.sap.com/bi --> Documentation --> SAP BW 3.5 Documentation Enhancements), which describe the enhancements delivered with this Support Package.
Improvements in the OLAP technology area:
General performance improvements for OLAP. For more information, see Note 825396.
The performance of MultiCubes has been improved. For more information, see Notes 869487 and 903559.
Symptom
Support Package 14 for BW Release 3.5
Other terms
SAPBWNEWS, Support Packages for 3.5, BW 3.5, BW 3.50, BW Patches
Solution
This note contains the SAPBWNews for Support Package 14 for BW Release 3.5. It contains a list of all notes that describe the corrections or enhancements in Support Package 14 (SAPKW35014). The note will be updated as soon as other notes are added.
The information is divided into the following areas:
Manual activities that may be necessary:
Factors you must take into account when you import the Support Package
Errors that may occur after you import the Support Package
For general information:
This Support Package corrects the following errors
Enhancements delivered with this Support Package
Support Package 14 for BW 3.5 corresponds to the technological status of Support Packages 29 for BW 3.0B (SAPBWNews 783251) and 23 BW 3.1 Content (SAPBWNews 783253).
Also refer to the following release and information note:
SP14 SAP_UDI 350 Note 839096
Factors you must take into account when you import the Support Package:
Note that as of NetWeaver Support Package Stack 14, that is BW Server Support Package 14, you require PI_BASIS 2005 Support Package 4. For information about upgrading to PI_BASIS 2005, see Note 821148.
Note 855424 leads to syntax errors during the generation of update rules. Read the note for more information.
Errors that may occur after you import the Support Package:
A query displays additional rows or columns. For more information, see Note 901097.
Querys on MultiCubes in read mode A. For more information, see Note 896066.
The update from the PSA using the 'Update' indicator in the scheduler no longer works for normal master data that is not flexible and text DataSources that were updated using 'PSA only' - Reason: The problem is caused by the correction that is contained in Note 889160, Note 905105 corrects the problem.
A syntax error occurs in class CL_RSMD_CONVERSION, method DROP_TMPTABLES. For more information, see Note 905168.
F4 and authorization: SQL error in SAPLRSDM_F4. For more information, see Note 907337.
This Support Package corrects the following errors:
Corrections in the end user technology area:
When you go from a query to another query or to a Web template, value variables on compound characteristics, which can be changed simultaneously during the query navigation, are filled with the initial value ("#"). For more information, see Note 867616.
Corrections in the OLAP technology area:
In certain cases, when you execute a query, a termination (GETWA_NOT_ASSIGNED in the SAPSRRK0 <L_S_SNID> field symbol) occurs or data is missing in columns or structural components. For more information, see Notes 851086 and 848340.
In certain cases, when you execute a query, a termination occurs and the system issues message X299(BRAIN) 'System error: Program SAPLRRKH; form SELDER_INTERSECT_BUF-01-'. For more information, see Note 851754.
You can execute a query that does not use any key figures at all even if you do not have the necessary authorizations. For more information, see Note 856144.
When you check a query, the system may issue error message Brain A 039 (Node &3 &4 is not in hierarchy &2 for InfoObject &1) even though the node exists and you can execute the query. For more information, see Note 855258.
In certain cases, a query with an exclude in the dynamic filter may not display any data. For more information, see Note 856495.
In certain cases, the Multiprovider F4 help does not use aggregates that were also used during the query execution. For more information, see Note 870557.
A termination may occur when you execute a MultiProvider query. For more information, see Note 870505.
Corrections in the Warehouse Management area:
The UNCAUGHT_EXCEPTION runtime error occurs during the upload. For more information, see Note 855424.
Enhancements delivered with this Support Package:
Also refer to the Documentation Enhancements on the SAP Service Marketplace (http://service.sap.com/bi --> Documentation --> SAP BW 3.5 Documentation Enhancements), which describe the enhancements that are delivered with this Support Package.
Improvements in the OLAP technology area:
General performance improvements for OLAP. For more information, see Note 825396.
The runtime in the REMOVE_SELDR_0INFOPROV_NEW form is very long. For more information, see Note 887801.
Unnecessary reading of partprovider. For more information, see Note 885733.
The performance in form SAPLRRK0; loc_rechnen has been improved. For more information, see Note 884482.
Problems occur with hierarchy selections in MultiProviders. For more information, see Note 879290.
Query runtime if there are several nested formulas. For more information, see Note 872904.
Symptom
Support Package 15 for BW Release 3.5
Other terms
SAPBWNEWS, Support Packages for 3.5, BW 3.5, BW 3.50, BW patches
Solution
This note contains the SAPBWNews for Support Package 15 for BW Release 3.5. It contains a list of all notes that describe the corrections or enhancements in Support Package 15 (SAPKW35015). The note will be updated as soon as other notes are added.
The information is divided into the following areas:
Manual activities that may be necessary:
Factors you must take into account when you import the Support Package
Errors that may occur after you import the Support Package
For general information:
This Support Package corrects the following errors
Enhancements delivered with this Support Package
Support Package 15 for BW 3.5 corresponds to the technological status of Support Packages 30 for BW 3.0B (SAPBWNews 872271) and 24 BW 3.1 Content (SAPBWNews 872273).
Also refer to the following release and information note:
Support Package 15 SAP_UDI 350 Note 839097
Factors you must take into account when you import the Support Package:
Errors that may occur after you import the Support Package:
The query displays more rows. For more information about this, see Note 901097.
This Support Package corrects the following errors:
Enhancements delivered with this Support Package:
Also refer to the Documentation Enhancements on the SAP Service Marketplace (http://service.sap.com/bi > Documentation > SAP BW 3.5 Documentation Enhancements), which describe the enhancements that are delivered with this Support Package.
Improvements in the OLAP technology area:
General performance improvements for OLAP. For more information, see Note 825396.
Performance improvements when you are searching for filter values. For more information, see Note 900728.
Performance improvements when you start the query. For more information, see Note 905375.
Improvements in the Warehouse Management area:
The system also issues error messages during parallel reading. For more information, see Note 905083. -
MIDDLEWARE ( R/3 Plugin support pack details)
Hi Experts,
We have to integrate CRM5.0 with R/3 4.7. Can anybody tell me the version of the PI( plug-in) support package, which has to be installed at R/3.
Points will be rewarded.
Thanks in advance
Nadh.Hi Eric,
Thanks for your support.
I have gone through the SAP note 672651 - OCS: Known problems with Support Packages in Basis Rel.6.40 and did a analysis of steps to install BW 3.5 support packs
1.Logon to client 000 with superuser having full authorisaton (i.e SAP_ALL and SAP_NEW)
2.Update SPAM/SAINT Version
3.Install PI_Basis 2005_1_640 with SAINT tcode
4.Install SAP_BASIS support packs with SPAM
SAPKB64013---SAPKB64014
SAPKB64015---SAPKB64018
SAPKB64019---SAPKB64021
5.Install SAP_ABA support packs with SPAM
SAPKA64013---SAPKA64014
SAPKA64015---SAPKA64018
SAPKA64019---SAPKA64021
6.Install PI_Basis 2006_1_640 with SAINT
7.Install SAP_BW Support packs
SAPKW35013---SAPKW35014
SAPKW35015---SAPKW35018
SAPKW35019---SAPKW35021
Our BW 3.5 system is having SAP_Basis SAPKB64012 as current level and SAP_BW SAPKW35012
as current level.
Please let me know is the queue defined for Basis,ABAP and BW Supports packs is ok.
Regards,
Anil. -
Inits/Deltas during Uprgrades and support packs
How are people handling the deltas and initializations when upgrades and support packs are applied to the source system. We had to delete our delta queues and reload everything!!! I know that's not right. ( At least I hope that's not right!!!). Please advise...
Ye s- you should not have to reload targets a a result of an SP/Upgrade.
When there are changes to the PI_BASIS plugin (extraction from ERP), you need to clear your V3 and Delta queues.
When SAP Service API (internal and BI Data mart extraction) is changed, you need to clear the BW delta queues. This can require two complete extraction and laod processes.
As a matter of practice, we always clear all queues prior to an SP/upgrade.
See the How to... Checklist: Rapid SAP Netweaver 7.0 BI Technical Upgrade document which is where you can fins this info page 11or 12. -
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 :
<b>
Function MAP2I_BAPICMS_STR_MOV_INS_CRT (CMS_BUSISB104_MAPPI does not fit into the existing function group ((CMS_BUSISB10)</b>
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=7280We 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 ConsultantHi,
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,
AvinashHi 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 -
Issues with POWL action buttons and row selection after Support Packs
We recently applied ECC 603 Support Stack 16 to our environment and are having problems with some SAP standard POWL lists (example is KYKOP-OPS-MM-PO-W: Purchase Orders for Goods Receipt). In fact all of the POWL lists that we are using are behaving the same way. There are 2 changes that have happened after moving to this stack.
1. In order to select a row in the list, we now have to press ctrl + click, previously, just clicking the the row would select it and fire the OnLeadSelection
2. All of the Action Buttons in the POWL lists are disabled.
I have debugged the Feeder Class /KYK/CL_MM_FEEDER_PO and see in th GetActions method and see that the ls_actions-enabled is getting set to true, but for some reason the buttons are disabled when the list is rendered.
I've checked a side-effects report from OSS and have come up empty handed. Has anyone else run into this?
EricI have found an OSS note that addresses this problem. This problem will effect anyone who is using ALV for ABAP WebDynpro after applying BASIS Support Pack 20 for 7.0. The OSS note is 1363334. Question Answered.
Maybe you are looking for
-
Questions from an Entourage user on iCal - tasks, printing events, reminder
I'm shifting from Entourage to iCal (connecting to an Exchange 2007 server at work). I've got a few problems that I'm hoping someone can help me with: 1) how do I print a single event? In Entourage, I select the event, and right-clicking (or using th
-
Hi, I've got 3 problems with my web site, It's built using Dreamweaver 8, Illustrator and Photoshop CS2 on a mac. The first problem is with a roll-over image, several people have viewed the site using various browsers, Safari, Firefox and IE on both
-
Im deigning a new mac infrastructure, any tips on sites of guides?
I hope somebody can offer some advice, but im after some advise or pointers on where to start on the design of our new Mac infrastructure. I would love to get some help in with this, but unfortunately with the way the budgets have worked out, there i
-
LOADING DATA FROM SAP CO TRANSACTION DATA
Hello BW gurus, Suppose if BW Implementation team has decided to use the 0CO_OM_CCA_1 standard Data Source and Info Source to extract CO transaction data from SAP R/3 system into BW system . 1)For the above scenario, How to create a Data Source for
-
Error opening report as webservice when there's parameters!
I followed the instructions in the developer's guide: "Publishing and Consuming a Report as a Web Service" I am using VS2008 and Crystal Reports 2008. I have a web application with 1 report in it called CrystalReport1.rpt and this report is published