Post Processing Steps after Support Package Stack Application
I'm curious if anyone has any guidelines for post processing steps (or pre-processing) when applying Support Package Stacks to their Development Infrastructure (Developmend Workplace and the Central NWDI Server). We have just upgraded a couple of developers local engines and developer studio to SP stack 19 from SP stack 14 and are experiencing some problems. We also applied the J2EE stack and appropriate SCA files to the NWDI server.
After the support packs it looks like our DTR files are gone (when reimporting configuration via Developer Studio the SC's are there but there are no DC's inside of them). Additionally, it looks like we have to manually reimport the newest versions of SAP_BUILDT, SAP_JTECHS, and SAP-JEE. Another thing is that old Local Web Dynpro DC's are now complaining about class path problems and different versions of files. We followed the documentation for applying SP19 exactly as the documentation says for a Java Development Usage type. Is there a checklist or something that anyone has for steps to perform after the application of the support packs?
I think I'm missing something. Now I see the code and DC's inside the DTR. However, when I try to import into NWDS no DC's come in (the software components exist, but no DC's in them). Additionally, the CBS web ui reports that my software components do not contain any DC's even though I see them in the DTR. What things can I look at to determine what I'm missing here?
Thought I'd add some more info..after applying the support packs, we imported the new SAPBUILD, SAP_JTECH, and SAP_jee SCA'S into our track as we required some functionality from the newer build SCA. We also reimported our old archives back into the system by manually checking them in assuming this would fix the problem with us not seeing the source in the NWDS or the DTR. After the import, the CBS no longer sees our custom DC's, but the DTR does (both in active and inactive ws). When importing the dev configuration into the NWDS our custom DC's no longer appear, but SAP's standard SCA's do.
Message was edited by:
Eric Vota
Similar Messages
-
Post processing steps after system copy
Hi experts,
Please clarify the doubts, reg my situation,
We don have our development server in synchronous with production server, so we destroyed the existing development client and copied the production client, now the new system logical name in sm30 in table T000 is MABCLNT900 and also our production server is same,as we copied it from production server, previously our development server was with MAACLNT495 which was mapped with MAQCLNT500 , R3 test sytem,
in this scenario we want run BDLS tool to change client name in both R3 and BW , Please explain step by step procedure in achieving this,
Thanks in advanceHi,
As I understood your system landscape should look like this:
BW DEV (MAACLNT495) <-> R3 DEV (MAQCLNT500)
BW PRD (MABCLNT900) <-> R3 PRD (???)
After BW system copy you should change connections in SM59 and then use BDLS to change logical system name.
You can also use Restore function for source systems (RSA1).
Although if you copy both R/3 and BW systems at the same time it's possbile just to keep the same logical system names as they are in productive (it's easier to maintain).
Please read notes: 886102, 543715, 325470, 325525, 184322, 886102, 184971, 184447, ...
regards
Krzys -
Syntax Error while applying support package stack 8
I get the following short dump while I was applying support package stack 8. I'm at the latest saint version 34
Runtime Errors SYNTAX_ERROR
Date and Time 23.07.2009 14:09:27
Short text
Syntax error in program "CL_DYNPRO_PROPERTY_BAG========CP ".
What happened?
Error in the ABAP application program.
The current ABAP program "SAPLSCR2" had to be interrupted because it con
a statement that cannot be executed.
In the include "CL_DYNPRO_PROPERTY_BAG========CM009 " in the line 176 of
program "CL_DYNPRO_PROPERTY_BAG========CP " the following syntax
errors occur:
"The field "SPROP_C_TAG_CUSTOMPROPERTY" is unknown, but there is a fiel"
"d with the similar name "SPROP_C_TAG_TOOLTIPTEXT". "SPROP_C_TAG_TOOLTI"
"PTEXT"."
Author and last person to change the include are:
Author "SAP "
Last changer "SAP "
Error analysis
The following syntax error was found in the program
CL_DYNPRO_PROPERTY_BAG========CP :
"The field "SPROP_C_TAG_CUSTOMPROPERTY" is unknown, but there is a fiel"
"d with the similar name "SPROP_C_TAG_TOOLTIPTEXT". "SPROP_C_TAG_TOOLTI"
"PTEXT"."
Trigger Location of Runtime Error
Program SAPLSCR2
Include LSCR2U47
Row 31
Module type (FUNCTION)
Module Name RS_SCRP_PROP_ADD_TO_PROP_LIST
1 FUNCTION RS_SCRP_PROP_ADD_TO_PROP_LIST.
2 *"----
3 ""Lokale Schnittstelle:
4 *" IMPORTING
5 *" REFERENCE(P_TEXTFIELD) TYPE D021S-FNAM OPTIONAL
6 *" REFERENCE(P_TOOLTIPTEXT_TEXTELEM) TYPE CHAR3 OPTIONAL
7 *" REFERENCE(P_TOOLTIPTEXT_VARIABLE) TYPE D021S-FNAM OPTIONAL
8 *" REFERENCE(P_KEEPTAB) TYPE SEU_BOOL OPTIONAL
9 *" REFERENCE(P_DISABLEIMPLICITLABELS) TYPE SEU_BOOL OPTIONAL
10 *" REFERENCE(P_BARCODEINPUT) TYPE SEU_BOOL OPTIONAL
11 *" CHANGING
12 *" REFERENCE(P_PROP_LIST) TYPE PROP_LIST
13 *"----
14
15 data: l_prop type prop_line,
16 l_prop_list type prop_list,
17 l_string type prop_str.
18
19 * Property TextField
20 * -
21
22 if p_textfield is supplied.
23 clear l_prop_list.
24 clear l_prop.
25 l_prop-name = sprop_c_tag_textfield_name.
26 l_prop-syntax = sprop_c_syntax_content .
27 l_prop-value = p_textfield.
28 append l_prop to l_prop_list.
29 * Zusammensetzen eines Strings der Form
30 * <Name>value_1</Name> ... <Name>value_n</Name>
>> call method cl_dynpro_property_bag=>fill_prop_list_into_properties
32 exporting
33 prop_list = l_prop_list
34 importing
35 properties = l_string.
36 * Property-Eintrag zusammensetzen
37 clear l_prop.
38 l_prop-name = sprop_c_tag_textfield.
39 l_prop-type = sprop_c_type_string.
40 l_prop-syntax = sprop_c_syntax_content .
41 l_prop-value = l_string.
42 * Property-Eintrag in PROP_LIST aufnehmen/ersetzen
43 read table p_prop_list transporting no fields
44 with key name = l_prop-name.
45 if sy-subrc = 0.
46 modify p_prop_list index sy-tabix
47 from l_prop.
48 else.
49 append l_prop to p_prop_list.
50 endif.
Can anyone help me? I now get the same error with executing other transactions as well.Hi,
Please let us know the component which you are trying to apply. Is it BASIS or ABAP or BW and also let us know the version?
I hope you are applying the BW patch 8, as per SAP's recommendation we need to apply both 8 an 9 patch of BW at the same time. If not we need to apply some notes which you could find in the service market place. Once you apply the notes, you can proceed with the SP application.
Regards,
Varadhu -
Support Package Stack NetWeaver vs. ERP
When I use Maintenance Optimizer to get the latest Support Package Stack (13) from my ERP system (ECC 6.0), it does not get the latest kernel and Basis support packages. After applying, the Early Watch report still shows the kernel is out of date. However, if I go through Service Marketplace and get the latest NetWeaver Stack (16), it gets the latest kernel and Basis package. After applying, Early Watch states that the Kernel is up to date. How should the support package stacks for an ECC 6.0 system be applied - both ERP and NetWeaver stacks or ERP stack only which is not the latest?
Hi,
Its Your requirement, So its better you should opt it for.
Mostly the ecc6 would contain all the components even like sap_hr and others,
but your nw stack doesn't have this.
Also you have to select the kernal like you have to make the appropriate settings in the selection page
which will get you the kernal files in the stack.
Regards,
Vamshi. -
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,
Cheungdefaulttrc.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# -
Hi
I want to use interactive forms in my web dynpro application and I see that one of the prerequisites is that I have support package stack 11.
How do I check what stack I have?
If I don't have the right level, how do I get the SP stack?
thanks
AntonHi,
Login to http://pc024788:50000/index.html -> System Information using Administrator account. Check under Software Components the patch level marked like SP17.
If u want to upgrade, go to http://service.sap.com/sp-stacks
Choose Netweaver 04 if u want to upgrade the NW04 server. Then give the target support pack and source pach. Check the appropriate check boxes. Then Download to ur basket.Then using download manager, u can download the folders to ur hard disk.
Regards,
Vijai -
Hi all,
I want to request SAP the latest DVDs of Support Package Stack for NW7.0, ERP 6.0, and Sol Man. 4.0, is it possible & how to do it?
Thanks,
Toan DoHi Toan,
It's possible to order them or download them from SAP Marketplace
http://service.sap.com/swdc
Regards
Juan -
Support package stack 11 (Java and ABAP)
Does anybody have any experience with the latest support package stack 11 already? Are there some problems solved, and more important: are there new errors introduced?
Thanks for your help.Hi Deepu,
Thanks for your reaction. I'm familiar with this OSS note. I'm mainly curious to customer experiences who have already implemented it. This SPS will solve some of our problems, but we're a little scared for the new errors that will be introduced with it.
Guus -
Support package stacks: Do we need to import all SP in the stack?
Hi all.
We are about to import Support Package Stack 13 into our ERP 6.0 system. The SPS includes a lot of support packages for software components such as IS-OIL, IS-UT and other IS-* components.
These components are inactive in our system, and are not used. However, I know that the recommendation is to import the complete stack.
I am therefore having some doubts if it is wise to import the IS-* related support packages.
Please advise.
Regards,
ThomasThank you for your feedback.
However, I would like to ask if the only argument is to follow SAP recommendation? What risks are we running if we do not implement the IS component support packages?
As the IS-* components are not active, I don't see how not importing these support packages will cause "inconsistence" in the system. Also, it would reduce the total number of support packages that needs to be included.
I am generally positive to following SAP's recommendations, but in this case we are are in a situation where we need to lift the SAP system from SPS 8 to SPS 13 in one operation. That includes a massive amount of support packages, and possibly a lot more time than the timeframe we have available.
Regards,
Thomas -
Post installation steps after SAP BW system copy
Hi!
I am about to do post processsing steps after system copy of SAP BW system.
1) One of the steps is to delete all entries from tables DBSTATHORA, DBSTAIHORA, DBSTATIORA,
DBSTATTORA.
Question: what is the way to do this?
2) During the installation I received the error within import ABAP step.
(IMP) INFO: import of D010TAB completed (4477754 rows) #20090505133631
DbSl Trace: Error 12801 in exec_immediate() from oci_execute_stmt(), orpc=0
DbSl Trace: ORA-12801 occurred when executing SQL stmt (parse error offset=0)
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "D010TAB~0" ON "D010TAB" ( "MASTER", "TABNAME" ) TABLESPACE PSAPSR3700 STORAGE (INITIAL 423090176 NEXT 0000000640K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) NOLOGGING COMPUTE STATISTICS PARALLEL )
DbSlExecute: rc = 99
(SQL error 12801)
error message returned by DbSl:
ORA-12801: error signaled in parallel query server P000
ORA-01659: unable to allocate MINEXTENTS beyond 34 in tablespace PSAPSR3700
(DB) INFO: disconnected from DB
As solution I changed the the following lines within D010TAB.TSK:
from D010TAB~ 0 C err to D010TAB~0 C ign and
from D010TAB1 C err to D010TAB1 C ign
Question:
how to create index manually after system copy?
Thnak you very much!Jgen Pfeiffer wrote:>
> Hi!
>
> I am about to do post processsing steps after system copy of SAP BW system.
>
> 1) One of the steps is to delete all entries from tables DBSTATHORA, DBSTAIHORA, DBSTATIORA,
> DBSTATTORA.
> Question: what is the way to do this?
Simply run
TRUNCATE TABLE <table_name>;
for each of those tables.
Make sure to either logon as SAP<SID> or provide the owner of the tables with the statement.
> 2) During the installation I received the error within import ABAP step.
> (IMP) INFO: import of D010TAB completed (4477754 rows) #20090505133631
> DbSl Trace: Error 12801 in exec_immediate() from oci_execute_stmt(), orpc=0
> DbSl Trace: ORA-12801 occurred when executing SQL stmt (parse error offset=0)
> (DB) ERROR: DDL statement failed
> (CREATE UNIQUE INDEX "D010TAB~0" ON "D010TAB" ( "MASTER", "TABNAME" ) TABLESPACE PSAPSR3700 STORAGE (INITIAL 423090176 NEXT 0000000640K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) NOLOGGING COMPUTE STATISTICS PARALLEL )
> DbSlExecute: rc = 99
> (SQL error 12801)
> error message returned by DbSl:
> ORA-12801: error signaled in parallel query server P000
> ORA-01659: unable to allocate MINEXTENTS beyond 34 in tablespace PSAPSR3700
> (DB) INFO: disconnected from DB
>
> As solution I changed the the following lines within D010TAB.TSK:
> from D010TAB~ 0 C err to D010TAB~0 C ign and
> from D010TAB1 C err to D010TAB1 C ign
>
> Question:
> how to create index manually after system copy?
The problem here was the large INITIAL size clause.
If there is enough freespace at all in the tablespace this should work:
CREATE UNIQUE INDEX "D010TAB~0" ON "D010TAB" ( "MASTER", "TABNAME" ) TABLESPACE PSAPSR3700 NOLOGGING COMPUTE STATISTICS PARALLEL;
If I'm not wrong, the second index is just vice versa:
CREATE UNIQUE INDEX "D010TAB~1" ON "D010TAB" ( "TABNAME", "MASTER" ) TABLESPACE PSAPSR3700 NOLOGGING COMPUTE STATISTICS PARALLEL;
In general it is really not a good idea to skip the creation of unique indexes...
regards,
Lars -
Need info about Support Package Stack
Hi,
Can anyone tel me what are the Support package stack released in XI 3.0 and what are the modification in each SPS.
Please send the related Docs if anyone has.
Thanks&Regards
Sreediviahi,
check the below link
http://help.sap.com/saphelp_nw04/helpdata/en/46/e45ab9db8166bfe10000000a1553f7/frameset.htm
regards
kummari
Edited by: kummari on Jul 28, 2008 11:40 AM -
Support Package Stacks Best Practice
Good morning all,
We're at the start of a mySAP ERP implementation and we'd like to set a strategy as regards how we implement SP Stacks.
We are only using the base mySAP ERP functionality; we're not using the HR, Retail, Public Services extensions. Because of this, I'd like to know what is the best practice for applying SP Stacks in our environment.
Do we need to install the SPs for the HR, Retail, etc.. extensions to keep the SP Stack consistent, or do we simply install only the base SPs that we require?
Any help is greatly accepted.
Thx,
Arwel.Hi Kobby,
Thanks for your information.
The Support Package Stacks for 7.0 version is 15
I would like to know the Stacks for SAP Solution Manager - 4.0
Version.
Thanks and Regards,
Sateesh.Kandula -
AccAD 2.2: Support Package Stack 02 available
Hello,
Support-Package-Stack 02 for AccAD 2.2 seems to be released now. At least I can see it in the Download area on SMP :o)
But there are no notes about it yet.
Will there be Release notes for SPS02, which bugfixes and new features are in it?
Best regards,
Stephan RoßmanithHi Stephan,
The official release is expected for November 15th in which the exepcted updates user manual and release notes should also be available within a weeks timeframe.
All the Best,
Smadar -
Support Packages stack ERP HR level
Hi,
I am requesting information about what the ERP HR stack level is for the common SAP ERP 6.0 Support Package Stack level 17 which is comming out week 13, 2010?
Regards,
Jesper
SAP Project Manager from DenmarkDear customer,
I am sorry but this is not a Service Marketplace issue. Would you please be so kind to place this question in the Area of the BASIC Team or to open a ticket under component BC-UPG
Thanks and best wishes
Dragana Manojlovic
SAP Senior Support Consultant II -
Maintenace optimiser, support package Manager, Support package stack
HI all,
Could you please enlighten me the differences among
Maintenance Optimizer,support package Manager, Support package stack
And the purpose and most importantly the documentation to be able to use them
in case of implementation phase (In case of a fresh ECC 60 Production version)
Thank youMaintenace optimiser is used in solution Manager to Approve the Patch that you need to download fron Service market place
Support package stack is the collection of patch for a release.
Support package Manager is SPAM/SAINT used to apply support pack.
If you want some thing else please revert back
thanksd Rishi Abrol
Maybe you are looking for
-
Yoga 2 Pro display/screen wobble in laptop or stand mode
Been looking around but can't find anyone mentioning the screen/display wobble when using the yoga 2 pro in laptop or stand mode. That baffles me. I tried normal touching on the screen on the Yoga 2 Pro at Best Buy in laptop and stand modes and the
-
I have owned Adobe Creative Suites since version 2 or 3. I owned 5 or 6 when I decided to try the cloud. Now I no longer want the expense of the cloud, but unfortunately I cannot find my non-cloud Creative Suites.
-
How to completely delete photos?
Hi, I am using iphoto 5 on my G5 iMac running leopard. I am taking a digital photo class and we are taking a lot of 'test' pictures to learn the manual controls. So I am deleting 75% of them after downloading, in order to determine which meet the cla
-
Elements 9 Edit or Organize will not come up after re-loading program onto new computer.
I got a new computer and re-loaded Photoshop Elements 9 onto it. I got no error messages during install. I can open the initial "Welcome to Photoshop Elements 9" screen, but when I attmept to open Organize or Edit by clicking on the button they will
-
Statistical forecast - automatic model
Dear Experts, I have specific question regarding statistical forecast in DP i am using automatic model selection -2 outlier correction - expost method mape upper limit set to -20 % in diagnosis group forecast profile - uni variant now i have Invoice