Spam/saint update and support package

Hi,
our solution manger server is crashed long back.Now i installed the solution manager in seperate server.
solution manager iam getting SPAM/SIANT version as 7.00/0.20 and in development/production SPAM/SAINT version in 7.00/0.23.
as per check in service market place under SPAM/SAINT update 700 iam getting SPAM/SAINT update version 700 iam got the message as to import Support Packages SAPKH60008 and SAPKGPAD08. Please advice.
*in solution manager support package is
SAPKB70008
SAPKA70008
SAPKIPYJ78
SAPKITLQI2
SAPKW70008
SAPKNA7005
SAPKU50005
SAPK-40005INCPRXRPM
SAPKITL416
SAPK-15074INSTPL
SAPKITLOG3*
*in dev/produ system support package is
SAPKB70011
SAPKA70011
SAPKIPYJ7B
SAPKITLQI3
SAPKW70012
SAPKNA7008
SAPKE60015
SAPKH60008
SAPKGPID08
SAPKGPGD08
SAPKGPRD08
SAPK-60008INFINBASIS
SAPKGPPD08
SAPKGPFD08
SAPKGPHD15
SAPKGPDD08*
please advice me in service.marketplace>downloads>support packages and from where i will get packages as in dev/production system.
Regards,
Asif

Hi Asif,
How to get particular support package from service market place .
EX:SAPKB70011
If you want to download the patch SAPKB70011:
Service Market Please --> Downloads --> SAP Support Packages --> Search for Support Package and Patches.
At the search field, enter SAPKB7001* it will give you all the support package from SAPKB70010 to SAPKB70019 if available.
You can add the required patch to your download manager.
Thanks & Regards,
Nagendra.

Similar Messages

Support Package Manager: SPAM/SAINT Update

Hi,
I downloaded the SPAM/SAINT Update and executed it with SAPCAR in the directory of the Application Server Folder. The original file KD74053.sar (6767 kb) is still in the folder, but a new file 'signature.smf' (5 kb) appeared.
What is that one for?
Next, I think that I should be able to take a next step with transaction SPAM (Support Package --> Load Packages --> From Application Server), but it's 'blanked out' and not accessible.
What are the next steps and how do I really get the SPAM/SAINT update working, so I can proceed to my actual goal, the Support Package Update.
Thanks!

Hi,
To reset DDIC password you could go with
SQL> select bname from usr02 where mandt='000' and bname='SAP*'
If the user SAP* exists then delete the user with below command
SQL> delete from usr02 where mandt='000' and bname='SAP*'
Run the below command to verify whether user deletion was successful.
SQL> select bname from usr02 where mandt='000' and bname='SAP*'
SQL> commit;
After that login to client 000 with SAP* and password as pass
reset the password for user DDIC with SAP* user.
Thanks,
Gaurav

Error in Spam / saint update TP_STEP_FAILURE and DDIC_ACTIVATION

Dear All,
While updating spam/ saint update I am facing this error
Details of Error:
The installation was stopped, since an error occurred during the phase
DDIC_ACTIVATION, which the Add-On Installation Tool is unable to resolve
without your input.
After you have corrected the cause of the error, continue with the
import by choosing Continue in the queue display.
The following details help you to analyze the problem:
    -   Error in phase: DDIC_ACTIVATION
    -   Reason for error: TP_STEP_FAILURE
    -   Return code: 0008
    -   Error message: tp step A, return code
        0008
Notes on phase DDIC_ACTIVATION
In this phase the system activates the imported Data Dictionary objects.
This phase may terminate for several reasons:
o   TP_INTERFACE_FAILURE: The system was unable to call the tp
     interface.
o   TP_FAILURE: The system was unable to execute the tp program. For
     more information, see the SLOG or ALOG log file.
o   TP_STEP_FAILURE: The system was unable to perform the tp step DDIC
    activation successfully. To see the cause of the problem in the
    activation log, choose Logs.
    If you import two or more OCS packages in one installation queue,
    and activate the Data Dictionary objects in the incorrect sequence,
    this can cause errors. In this case, the activation errors disappear
    if you repeat the activation run. To do this, choose Continue.
The Add-On Installation Tool requires that the Change and Transport
System (CTS) be configured correctly. For more detailed information,
read the online documentation available from Help -> SAP Library ->
mySAP Technology Components -> SAP Web Application Server -> BC Change
and Transport System .
A list of the most important SAP Notes for Online Correction Support
(OCS) is available in SAP Note 97620, which is updated regularly.
Please help me
Thanks
Senthil

Hi,
i am having the same problem with SPAM
Error in phase: DDIC_ACTIVATION
Reason for error: TP_STEP_FAILURE
Return code: 0008
Error message: OCS Package SAPKA70012, tp step A, return code
0008
however i dont have the option to continue.. Please help
thanks

Spam/Saint update failed

Hello,
My current SPAM/SAINT version is 20.
I tried updating it to version 38.
But while updaing m facing a runtime error which is generating a short dump.
Short Text of dump is as follows:
Syntax error in program "CL_OCS_RT_ANALYSIS============CP
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLSPAM" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program
     "CL_OCS_RT_ANALYSIS============CP " in include
     "CL_OCS_RT_ANALYSIS============CM002 " in
    line 135:
    "Die Transformation "RTA_TRAFO" hat keine aktive Version."
    The include has been created and last changed by:
    *Created by: "SAP "    Last changed by: "SAP "*
Below is the status of Import phase
SPAM/SAINT update is being processed
SPAM status: (Red)
Import phase:     PROLOGUE
Please help.
Thanks Deepak

I have similar problem, i have the following runtime error:
The following syntax error occurred in program
"CL_OCS_RT_ANALYSIS============CP " in include
"CL_OCS_RT_ANALYSIS============CM002 " in
line 13:
"Type "OCSRT_TOOL" is unknown"
I have create OSS-message and SAP reply;s:
Regarding your issue, please transport the class CL_OCS_RT_ANALYSIS
from other system in the landscape which is on the same release and
support package level and with the SPAM\SAINT update version as the
PRD system to the PRD system to resolve the syntax error.
Once the syntax error is resolved in the PRD the SPAM\SAINT update can
be continued in the SPAM to import the SPAM\SAINT update in the system.
For more information please refer the link specified below for
including the objects manually in the transport request.
http://help.sap.com/saphelp_nw70/helpdata/en/57/38e2864eb711d182bf0000e829fbfe/content.htm
I looked to the url, but still not understanding how to add it...can someone explain me how to export it?
Thanks,
Cheung

Spam/saint update to 40

Hi,
Can we update spam/saint to level 40 without use of solution manager?
What are the requirements needed to download the spam/saint update?
Thanks in Advance

Hi,
Refer to help.sap.com for understanding the functionality of SPAM and SAINT.
http://help.sap.com/saphelp_46c/helpdata/en/d7/56e89a884b11d2b422006094b9ea64/frameset.htm
http://help.sap.com/saphelp_46c/helpdata/en/d7/56e89a884b11d2b422006094b9ea64/content.htm
Can we update spam/saint to level 40 without use of solution manager?
Specify the SAP release.
You must use solution manager to download SPAM / SAINT update.
Because you need to approve the download request from MOPZ.
What are the requirements needed to download the spam/saint update?
The basic requirement would be to import latest SPAM/SAINT package before you update your Support pack levels for ABAP system.
[Link|http://www.google.co.in/url?sa=t&rct=j&q=&esrc=s&source=web&cd=2&ved=0CDIQFjAB&url=http%3A%2F%2Fhelp.sap.com%2Fprintdocu%2Fcore%2Fprint46c%2Fen%2Fdata%2Fpdf%2FBCUPGOCSSPAM%2FBCUPGOCSSPAM.pdf&ei=4_BBT4DXI4jm2QWXwZynCA&usg=AFQjCNFWOUEaYbDCXw_1fR_gTBm-yeOXWw]
Br,
Venky

Delete SPAM/SAINT UPDATE

I was importing a Support Package update (SPAM/SAINT-Update Version 7.00/0026) by SPAM transaction but it displays me a message saying that there's a previous update at queue which has to be imported first, this update is SPAM/SAINT-Update Version 7.00/0022 but it has error status, I applied note 684564 and reset its status from 'Imported' to 'New', but I didn't backup the file ($DIR_EPS_ROOT/in ) in the server, I tried to dowload it again from the SAP marketplace but isn't available anymore, the name of the object is SAPKD70022.
Is there a different place to download this object or a way to delete it from SPAM queue?

In Se37,Use the function module OCS_RESET_QUEUE --- >execute --->IV_TOOL=SPAM, IV_FORCE=X
Deleted all the files from \usr\sap\trans\tmp..
Please make sure thatthere is no TP process
or R3trans process running in the system at Operating system level.
If any process exist, Please kill the process.
Upload the spam/saint package again
Scheduled the program RDDIMPDP using Report RDDNEWPP in se38.
Edited by: Venkatramani Hariharan on Jun 6, 2008 2:15 PM

OCS queue stuck on aborted spam/saint update

I have a spam saint update stuck in a queue. I have tried resetting the queue, and I have no option to delete the object in the queue.
Please advise.
Thanks

1) try the following.
Call SE37 -> Utilities pull down menu -> Repair Function group -> Function Group = SPAM
2) Please make sure you are using the latest version of tp and R3trans
If Point 1 doesnt help please unpack the package again by command
sapcar -xvf SAPKD00xxx
Please remove the entries related to the spam from the following tables: tepsin, pat01 & pat03, further disassemble the spam file,
upload again and try to apply.
Please do the following on console with <sid>adm user:
Run a 'tp delfrombuffer SAPKD00xxx <SID>
then add the patch to the buffer with
'tp addtobuffer SAPKD00xxx u1 pf=<PATH_PROFILE>'
and finally import the patch with >
'tp import SAPKD00xxx <SID> u26 pf=<PATH_PROFILE>'
Thanks
Prince Jose

Problem while updating the Support Package 17 on my SAP WAS SP9

Hi,
I'm facing problem while updating the Support Package 17 on my SAP WAS SP9
ERROR 2006-10-13 10:23:22
FSL-06002 Error 2 (The system cannot find the file specified.
) in execution of a 'CreateProcess' function, line (284), with parameter (java.exe ...).
Please help me in this regard.....
Thanks in advance...
Satya

Hello gentlemen, I am also having problem with the following running on 64 bit Windows and SQL2005/64 bit. I am erroring in Step 8 'Updating JDBC' driver. I am attempting to update from SP9 to SP18. The WEBAS Jave installed went flawless but I seem to be stuck here. Any help is appreciated...
ERROR 2006-11-22 10:13:57
FSL-06002 Error 2 (The system cannot find the file specified.
) in execution of a 'CreateProcess' function, line (284), with parameter (java.exe ...).

Update Java Support Package Stack in JSPM

Hi all,
When i update Java Support Package Stack in JSPM i can't start the dispatcher
[Thr 920] JLaunchIExitJava: exit hook is called (rc = -11113)
[Thr 920] **********************************************************************
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 920] JLaunchCloseProgram: good bye (exitcode = -11113)
When i goto the log-file of the dispatcher (server.0.log):
E:
usr
sap
P01
DVEBMGS01
j2ee
cluster
dispatcher
bin
services
log_configurator
log_configurator.jar
Loading model: {parent,local,references}
The error occurred while trying to load "com.sap.engine.services.log_configurator.LogInterfaceImpl".
     at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:401)
     at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
     at com.sap.engine.services.log_configurator.LogConfiguratorServiceFrameImpl.init(LogConfiguratorServiceFrameImpl.java:156)
     at com.sap.engine.services.log_configurator.LogConfiguratorServiceFrameImpl.start(LogConfiguratorServiceFrameImpl.java:127)
     at com.sap.engine.core.service630.container.ServiceRunner.startCommunicationServiceFrame(ServiceRunner.java:228)
     at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:158)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
     at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:82)
     at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:154)
#1.5 #0050569379EA000A00000004000010880004B40696AFED19#1323840297756#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:6]_32##0#0#Error#1#/System/Server#Plain###Core service log_configurator failed. J2EE Engine cannot be started.#
#1.5 #0050569379EA000A00000006000010880004B40696AFF1F0#1323840297756#/System/Server/Critical##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:6]_32##0#0#Fatal#1#com.sap.engine.core.Framework#Plain###Critical shutdown was invoked. Reason is: Core service log_configurator failed. J2EE Engine cannot be started.#
Somebody know how to solve this problem?
Thanks in advance,
Cheung

defaulttrc.0.trc"
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[./log/defaultTrace.trc]/>
<!PATTERN[defaultTrace.trc]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[UTF8]/>
<!FILESET[0, 2, 10485760]/>
<!PREVIOUSFILE[defaultTrace.1.trc]/>
<!NEXTFILE[defaultTrace.1.trc]/>
<!LOGHEADER[END]/>
#1.5 #0050569379EA001500000D53000016300004B40029F81C09#1323812703907#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###com.sapportals.portal.prt.runtime.PortalRuntimeException: [ApplicationItem.release]: SAPJ2EE::sap.com/tcwd4vccorestdinfoactors#
#1.5 #0050569379EA001500000D54000016300004B40029F8209A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:506)#
#1.5 #0050569379EA001500000D55000016300004B40029F82100#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.PortalAppBroker.releaseAllItems(PortalAppBroker.java:590)#
#1.5 #0050569379EA001500000D56000016300004B40029F82147#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.PortalAppBroker.shutdown(PortalAppBroker.java:672)#
#1.5 #0050569379EA001500000D57000016300004B40029F8218D#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.runtime.Portal.shutdown(Portal.java:725)#
#1.5 #0050569379EA001500000D58000016300004B40029F821D1#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalCoreInitializer.shutdown(PortalCoreInitializer.java:111)#
#1.5 #0050569379EA001500000D59000016300004B40029F82215#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.PortalInitializer.shutdown(PortalInitializer.java:164)#
#1.5 #0050569379EA001500000D5A000016300004B40029F8225A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.Dispatcher.destroy(Dispatcher.java:651)#
#1.5 #0050569379EA001500000D5B000016300004B40029F8229E#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.destroyServlets(WebComponents.java:722)#
#1.5 #0050569379EA001500000D5C000016300004B40029F822E4#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadDestroyer.run(ApplicationThreadDestroyer.java:62)#
#1.5 #0050569379EA001500000D5D000016300004B40029F82329#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
#1.5 #0050569379EA001500000D5E000016300004B40029F8236C#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
#1.5 #0050569379EA001500000D5F000016300004B40029F823AF#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)#
#1.5 #0050569379EA001500000D60000016300004B40029F823F3#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)#
#1.5 #0050569379EA001500000D61000016300004B40029F826A8#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception during stop of application: SAPJ2EE::sap.com/tcwd4vccorestdinfoactors#
#1.5 #0050569379EA001500000D62000016300004B40029F82700#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.releaseResources(SAPJ2EEApplicationItem.java:162)#
#1.5 #0050569379EA001500000D63000016300004B40029F82747#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:479)#
#1.5 #0050569379EA001500000D64000016300004B40029F8278A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     ... 12 more#
#1.5 #0050569379EA001500000D65000016300004B40029F82AA4#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Caused by: java.lang.NullPointerException#
#1.5 #0050569379EA001500000D66000016300004B40029F82AF6#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.portal.prt.sapj2ee.SAPJ2EEPortalRuntime.getSAPJ2EEApplicationState(SAPJ2EEPortalRuntime.java:630)#
#1.5 #0050569379EA001500000D67000016300004B40029F82B41#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.service.sapj2ee.Mediator.getSAPJ2EEApplicationState(Mediator.java:216)#
#1.5 #0050569379EA001500000D68000016300004B40029F82B87#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.releaseResources(SAPJ2EEApplicationItem.java:121)#
#1.5 #0050569379EA001500000D69000016300004B40029F82BCB#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     ... 13 more#
#1.5 #0050569379EA001500000D6A000016300004B40029F82D15#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###com.sapportals.portal.prt.runtime.PortalRuntimeException: [ApplicationItem.release]: SAPJ2EE::sap.com/com.sapportals.connectors.sap#
#1.5 #0050569379EA001500000D6B000016300004B40029F82FE9#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:506)#
#1.5 #0050569379EA001500000D6C000016300004B40029F8303F#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.PortalAppBroker.releaseAllItems(PortalAppBroker.java:590)#
#1.5 #0050569379EA001500000D6D000016300004B40029F83085#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.PortalAppBroker.shutdown(PortalAppBroker.java:672)#
#1.5 #0050569379EA001500000D6E000016300004B40029F830E5#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.runtime.Portal.shutdown(Portal.java:725)#
#1.5 #0050569379EA001500000D6F000016300004B40029F8312A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalCoreInitializer.shutdown(PortalCoreInitializer.java:111)#
#1.5 #0050569379EA001500000D70000016300004B40029F8316F#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.PortalInitializer.shutdown(PortalInitializer.java:164)#
#1.5 #0050569379EA001500000D71000016300004B40029F831B4#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.Dispatcher.destroy(Dispatcher.java:651)#
#1.5 #0050569379EA001500000D72000016300004B40029F831F8#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.destroyServlets(WebComponents.java:722)#
#1.5 #0050569379EA001500000D73000016300004B40029F8323E#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadDestroyer.run(ApplicationThreadDestroyer.java:62)#
#1.5 #0050569379EA001500000D74000016300004B40029F83283#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
#1.5 #0050569379EA001500000D75000016300004B40029F832C9#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
#1.5 #0050569379EA001500000D76000016300004B40029F8330C#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)#
#1.5 #0050569379EA001500000D77000016300004B40029F83350#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)#
#1.5 #0050569379EA001500000D78000016300004B40029F835C4#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception during stop of application: SAPJ2EE::sap.com/com.sapportals.connectors.sap#
#1.5 #0050569379EA001500000D79000016300004B40029F8361A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.releaseResources(SAPJ2EEApplicationItem.java:162)#
#1.5 #0050569379EA001500000D7A000016300004B40029F83662#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:479)#
#1.5 #0050569379EA001500000D7B000016300004B40029F836AA#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     ... 12 more#
#1.5 #0050569379EA001500000D7C000016300004B40029F83A09#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Caused by: java.lang.NullPointerException#
#1.5 #0050569379EA001500000D7D000016300004B40029F83A67#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.portal.prt.sapj2ee.SAPJ2EEPortalRuntime.getSAPJ2EEApplicationState(SAPJ2EEPortalRuntime.java:630)#
#1.5 #0050569379EA001500000D7E000016300004B40029F83AAF#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.service.sapj2ee.Mediator.getSAPJ2EEApplicationState(Mediator.java:216)#
#1.5 #0050569379EA001500000D7F000016300004B40029F83AF5#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.releaseResources(SAPJ2EEApplicationItem.java:121)#
#1.5 #0050569379EA001500000D80000016300004B40029F83B3A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     ... 13 more#

Importing a SPAM/SAINT Update

Hello,
I am trying to update SPAM/SAINT.
In Transaction SPAM, when I import SPAM/SAINT Update the package SAPKD70139 is proposed for the queue.
I need to import this one SAPKD70042, that already decompressed in EPS/in.
(Both are displaying in OCS overview)
Could anybody help me to find the way deleting a Not imported Package (SAPKD70139) in OCS Packages / SPAM ?
Many Thanks in advance
Latif

Issue is solved.
Regards

SPAM/ SAINT update still running

Dear All,
I have installed SAP Web Neweaver 04s as ABAP on MSSQL database windows OS and upgraded kernel.
But now when i go to import SPAM /SAINT from level 17 to 23 ie. SAPKD64023 then its running in IMPORT_PROPER Phase since last 5-6 hrs.
PLEASE SUGGEST how to speed up my process??
Log is as below:
Log Overview for SAPKD64023
      SAPKD64023              SPAM/SAINT Update - Version 640/0023
        BPW        System BPW
                   Generate Transport Information File      02.01.2008 13:41:45    (0) Successfully Completed
                   Test Import                              02.01.2008 13:41:46    (0) Successfully Completed
                   Import Request Piece List                02.01.2008 13:41:47    (4) Ended with Warning
                   Import ABAP Dictionary Objects           02.01.2008 13:41:52    (4) Ended with Warning
                   02.01.2008 10:54:46    (4) Ended with Warning
                   02.01.2008 13:41:52    (4) Ended with Warning
                   ABAP Dictionary Activation               02.01.2008 14:13:28    (4) Ended with Warning
            Import steps not specific to transport request
                   ABAP Dictionary Distribution             02.01.2008 14:23:31    (4) Ended with Warning
Regards & Thanks,
Ankita.

Dear Marqus,
Happy New Year!!
And Thanks for ur reply n when i check SLOG* it says:
Please check the system. Use transactions SM21, SM37, SM50.
WARNING:       (This warning is harmless if no further warnings follow.)
WARNING: System BPW. Warning.        20080102161830 :
WARNING:       Background job RDDIMPDP could not be started or terminated abnormally.
      Please check that the R/3 system is running.
      Please check the system. Use transactions SM21, SM37, SM50.
WARNING:       (This warning is harmless if no further warnings follow.)
Now wat shd i do to resolve it??
Regards,
Ankita.

SPAM/SAINT Update stuck on Import phase Epilogue

Under status it shows that SPAM/SAINT update is being processed and SPAM status shows red light.
Import phase is EPILOGUE.
I got out of the SPAM and restarted it, it shows the updated SPAM version but status is still red light.
I am updating to version 6.20/30 from 29
Any idea or suggestion

Hello Bill
Do you see any processes running in SM50?
Try to come out from SPAM and go again in SPAM and check.
regards,
Payal

Install Kernel Patch and Support Package

Hi Gurus.
How can I update the kernel patch and support package in solution manager?
What patchs i have to download In the service.sap.com ?
best Regards
luis

Hi Luis,
Yopu must already have checked this info at Inst Guides..
else...The Post installation steps in the installation guide contain the procedure for application of latest support packs procedure.
https://websmp204.sap-ag.de/instguides
The following SAP notes can also be referred : 212876
Information of how to download a kernel can be obtained from 19466.
Details of Patches and their release schedules can be obtained as always at
https://websmp104.sap-ag.de/ocs-schedules
Hopefully it Helps in your quest.
Br,
Sri

OSS and Support Packages

Hi all,
Is ther any difference between the OSS and support packages?
Plz explain for this one.
regatrds
vijay

Hi,
IMPORTANT DIFFERENCE
Support packages provide a bundle of fixes in electronic form that are imported into the SAP system. These Support packages must be imported in order (starting with the very first one) and they cannot be skipped. All fixes within a Support package must be imported together, there is no ability to pick and choose the fixes.
The second form of fixes that SAP provides is via OSS notes that pertain to specific problems. These notes must be manually applied to the system, as these fixes are generally not available in electronic form at the time the note is published. Care must be taken to ensure that the note is entered correctly otherwise new problems may occur, or the existing problem is not corrected.
A Support package may contain fixes that also exist as individual notes, but many times they contain fixes that are only provided in Support packages. SAPs strategy for providing intra-release fixes is through Support packages and the use of individual notes is decreasing.
I hope this information could help you.
Note: Points always encourage me to reply !!

SPAM/SAINT update issue before and after EHP4

We tried to update the SPAM/SAINT package after the installation of ECC 6.0 EHP4 Ready system.
Here are few steps which we have performed on the system even before EHP4 installation.
1. we tried to update the SPAM before moving with EHP4 installation however it did not completed and when logs seems to be proper. We reset the queue with Function Module OCS_RESET_QUEUE using Tx se37 .
2. The spam status went to green with updated version
3.We moved ahead with the EHP4 installation assuming that installation will fix the SPAM issue. After the installation completed the SPAM status was green with the new version , however when we exectuted the import spam/saint it again went to the PROLOGUE state.
Please let us know if we can use the system productively as we have performed these steps without the SAP support , also there are no errors at the ST22 other than originated by the spam tx.
Please find the attached trans log
http://s000.tinyupload.com/index.php?file_id=66042159519595351356
http://s000.tinyupload.com/index.php?file_id=20880680182063159483
Please advice....
Also , the show buffer command shows following output..
D:\usr\sap\GCQ\SYS\exe\uc\NTAMD64>tp showbuffer GCQ pf=
hostname\sapmnt\t
rans\bin\TP_DOMAIN_GCQ.PFL tag=SPAM
This is tp version 375.94.95 (release 701, unicode enabled)
GCQ buffer:
SAPKD70139 | | |has already been imported completely
that makes 0 transports to be imported.
tp finished with return code: 0
meaning:
Everything OK
Edited by: indian tiger on Jul 14, 2010 3:03 PM

Hi,
> 1. we tried to update the SPAM before moving with EHP4 installation however it did not completed and when logs seems to >be proper. We reset the queue with Function Module OCS_RESET_QUEUE using Tx se37 .
This is not supported by SAP.
As I understand you are installing new EHP4 system, then what do you mean by before moving to EHP4 installation ?
> 2. The spam status went to green with updated version
> 3.We moved ahead with the EHP4 installation assuming that installation will fix the SPAM issue. After the installation >completed the SPAM status was green with the new version , however when we exectuted the import spam/saint it again >went to the PROLOGUE state.
>
As I can see your buffer status which is showing that transport is already imported then why are you importing same SPAM status again.
What is your current SPAM level and which SPAM level you are trying to update ?
What is the system status now ? Is upgrade completed successfully. Please provide all information.
Thanks
Sunny

Spam/saint update and support package

Similar Messages

Maybe you are looking for