BI7 dual stack upgrade using 'resource minimised' method

Hi
I am upgrading a Windows 2003/MS SQL 2005 sandpit NW04 BI 350 dual stack (ABAPJAVA) to BI7 (NW04S ABAPJAVA) as a test before working on our actual landscape, I have started the ABAP upgrade and chose the 'resource minimised' method as downtime isn't an issue on the sandpit, I then started the upgrade on the Java stack, but then noticed in the documentation it states you should use 'downtime minimised' for a dual stack upgrade? the ABAP prepare recognised I had a dual stack and said it would be synchronised but never complained about the resource minimised choice ? the phases have been waiting for synchronisation so far without a problem.
Is this a problem? I can reset the upgrade, but its quite far through, so would rather not !
Thanks,
Paul.

Hello Paul
As you said, SAP state that you must perform a dual stack upgrade using strategy downtime - minimised. I had a problem when I used resource minimised but if your upgrade is running then donu2019t terminate it. If it works, thatu2019s great.
What I normally do is run strategy downtime minimised with an import time of zero hours.
Thank You
Anwar

Similar Messages

How to reset java upgrade in dual stack upgrade

Hi,
We are working on dual stack upgrade.Now we are in downtime phase for both the stacks.I have situation to reset upgarde now.
I restored DB before downtime phase and jup for java and upg for abap.I am able to reset abap stack.Could anyone please let me know the process to reset java stack.
Thanks

Hi,
In order to reset Java Part, you need to restore file system of the same time-stamp which you have restored for database. Since you have restored DB, so shadow repository of Java Part is already gone, so only you need to restore file system.
Thanks
Sunny

PI 7.1 Dual stack to PI 7.4 Dual stack upgrade

Hi SAP friends,
We are planning to upgrade PI 7.1 (Dual Stack) to PI 7.4 (Dual Stack). Please suggest best way to do this:
In-place upgrade PI 7.1 to PI 7.4 (Dual Stack)
New Install PI 7.4 (Dual Stack) and migrate the contents from PI 7.1
Thanks
Vikas

Vikas
There is no hard and fast rule and it depends on a lot of factors within an organisation. Refer to the following official guide from SAP on the various factors to consider, then you would be able to come up with the best decision for your organisation.
Decision Making Factors when Moving to SAP NetWeaver Process Integration 7.3 - Upgrade or New Installation with Phase-ou…
Rgds
Eng Swee

SAP R/3 4.6 C to ECC 6.0 Upgrade using CU &UC method- Unicode conversion

Basis Gurus
   I am working on upgrade from R/3 4.6C to ECC 6.0.
ECC 6.0 upgrade completed( still in non Unicode). Now I am in the process of Unicode conversion.
I have used following methods for the upgrade.
1. Combined Upgrade & Unicode conversion(CU & UC)
2. Resource minimized( as I am doing it in Sandbox).
As I understand I need to perform the DB export and Import now for the unicode conversion.
According to the Upgrade document, First I need to run Export using R3load in ECC6.0(Non unicode)
and then install Unicode system and import the same data file.
My understanding was, when I choose, Resource minimized, I need to run Export and import
in the same system.
Can you please help me , whether I need another Unicode system for import ??
Graham

Hi,
Dont get confused with upg strategy and unicode conversion.
In general Upgrade strategy (either downtime-minimized/resource minimized)
In unicode conversion you have export/import(exp/imp) of data concept
In CU&UC approach you have to do in a streach to complete migrate from old release to new realease ECC 6.00.
Using database independent (sapinst only) or Using database dependent (migration monitor or Distribution monitor)
It can be done in 2 ways.
If you dont have addtional server for unicode conversion
       1)you can either do exp on same hardware and take bakup and do import using the exp dump.
       2)Do exp on one server and prepare your target empty database on another server and complete imp of data.
Hope this is clear.
Regards,
Vamshi.

PI system upgrade from 7.1 to 7.4 dual stack

Hi,
We want to upgrade PI system to 7.4 .currently we are using PI 7.1 system (dual stack)and want to go for 7.4 dual stack.
which one single stack or dual stack is the best approach and what are the impacts normally see when upgrading to newer version.
We are planning to install 7.4 freshly recomonded by SAP .
We need to migrate objects from older system to newer system?
I want to know the process from basis perspective also .
Import/export or migrate is the best way to move objects from older sytem to newer system.
Please suggest me any links about the process including basis point of view also suggestions for the approach.
thanks,
aman

>>>> which one single stack or dual stack is the best approach and what are the impacts normally see when upgrading to newer version.
I would prefer single stack considering the SAP's future road map but of course it depends on how much effort your company is ready to spend. Incase you have lot of CCBPM's then you'll have to redesign them using Netweaver BPM if you go with single stack.
As are going with fresh installation(migration) of dual stack then you don't need to invest much.
>>> We are planning to install 7.4 freshly recomonded by SAP .
We need to migrate objects from older system to newer system?
I want to know the process from basis perspective also .
There is wizard using which you can move the directory objects ( classical scenario's to Integrated configurations). Please use it for ID objects
Refer to the below blog for more details. (ignore blog's title. it's applicable for dual stack-> dual stack too)
Moving Integration Directory Artifacts from dual stack to single stack
For ESR you can simply export and import the tpz file.
>>> I want to know the process from basis perspective also .
They can simply follow the installation guide and execute the post installation steps properly.

PI 7.31 Dual Stack Using BPM/BRM and ccBPM

Hello,
My client has decided to use SAP PI 7.31, because we have many ccBPM solutions, being used a long time, the idea is install the Dual Stack solution and keep using the ccBPM, at least for while.
But for the new integration solutions, we would like to use the AEX(Local AEX-Based) and connect to BPM and BRM, and maybe migrate the old solutions when possible.
Is it possible, use the both solutions( AEX/BPM/BRM and ccBPM) ? In this case, we will have all the benefits and great perfomance
when using the AEX/BPM/BRM(Local AEX-Based) solution, that we have in the single stack ?
Best regards,
Dylon.

Hi, vishal jain.
Thank you! Checking your link, we will probably choose the third case:
If PI is installed as dual-stack, then PO, PI and BPM/BRM, will have to be installed with different SIDs. PI on one SID and BPM/BRM on a different SID.
But the question remains... in this case is possible to use ccBPM and BPM/BRM, ok ?
And when using the BPM/BRPM, how is the performance and benefits ?
Are the same when using single stack solution ?
Best regards!

OSDB Migration using the migration monitor with dual stack

Hi
How can i use the migration monitor for dual Stack system. i knew that migration monitor use the R3LOAD. i never find using the JLOAD. how migration monitor export the Java.
Please advice me
Thank you
Vish

> We are using the NFS filsystem. its mounted the two systems.
Good!
> Can i know which ExchangeDir we need to use.
>
> i saw two of them
>
> 1. NetExchangeDir
> 2. FtpExchangeDir
So assuming that you have not read the documentation (which you really should):
- You need to create a separate directory on the NFS where both systems have access
- you need to configure the export machine as "server" (read the docs!)
- you need to configure the exchange directory on both export and import migmon
Markus

Upgrade WSS content DB WSS 3.0 using database attached method‏

i m trying to upgrade WSS content DB WSS 3.0 using database attached method. when i use stsadm command to addcontentdb getting following error. i have also run db repair command but still getting error.
[SPUtility] [DEBUG] [3/23/2015 11:41:39 PM]: File C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\sql\storeup.sql, Time out = 24595 sec
[SPManager] [ERROR] [3/23/2015 11:54:36 PM]: Upgrade [SPContentDatabase Name=WSS_Content_DB Parent=SPDatabaseServiceInstance] failed.
[SPManager] [ERROR] [3/23/2015 11:54:36 PM]: The transaction log for database 'WSS_Content_DB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
The transaction log for database 'WSS_Content_DB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
The statement has been terminated.
pls guide how to fix.
iffi

sounds like the database ran out of log space. did you fill the drive? does the database's log file have a hard limit?
Scott Brickey
MCTS, MCPD, MCITP
www.sbrickey.com
Strategic Data Systems - for all your SharePoint needs

Single stack vs. Dual Stack - Why does SAP recommend single stack?

Hello SAP,
I am a business partner who specializes in infrastructure consulting for SAP solutions. The SAP Consultants I am working with recently have been recommending that customers install single stack systems. I would like to know why? Are there problems with dual stack systems? Is SAP changing things in a later release and they want customers to be prepared for the change?
From an infrastucture point of view this recommendation combined with SAP NetWeaver architecture will result in an explosion of SID names which leads to an explosion of application server instances and DBMS instances and an explosion of installed servers. I know it is possible to combine SIDs into a single DBMS using MCOD and to have multiple application servers in a single physical server, but there are issues with mulitple application server instances and MCOD use which make normal maintenance operations difficult.
I think it would be much better for customers to install dual stack systems and simply adjust the SAP profile parameters to disable one stack or the other. This way, you could still have 1 stack per application server instance and you would not be have to be creative with SAP SID names!!! Creating a DBMS instance or installing an additional server is not a simple nor economical proposition.
Regards,
Zaz

I am a business partner who specializes in infrastructure consulting for SAP solutions. The SAP Consultants I am working with recently have been recommending that customers install single stack systems. I would like to know why? Are there problems with dual stack systems?
The problems are:
- difficult to size and maintain - Java + ABAP will fight for resources (memory,CPU) and there´s not much one can do to tune if either ABAP or Java as dual stack instance on a single box is running nuts (for whatever reason).
- System copies via R3load - if you want to copy a huge system (let´s say ERP 6.0 + Java stack) you need to use sapinst + R3load to do the copy. Imagine if the system is 1 TB or bigger, this is very time consuming
- Upgrades are complicated - if you upgrade a dual stack system you need to run two PREPARES and two upgrades at the same time - there are sync points each upgrade wait for the other to finish --> difficult to plan in sense of runtimes and even more notes/preparation to do (a dual stack SolMan upgrade from 3.2 to 4.0 had almost 100 notes (technical!) and two upgrade preparation guides...)
- interdependencies - example: you run ERP + EP + BI-Java on one system. You upgrade your BI (which is on a different box) to a new support package. Since the BI-Java need to be in sync with the BI ABAP support package you need to upgrade the EP too - and since there´s a direct dependency (doublestack system) you will need to install support packages on your ERP. So you finally end up in having dependency chains that a total different system (BI) will force you to upgrade/patch your ERP. And if you have e. g. a CRM connected to the same EP you will need to patch that too...
Is SAP changing things in a later release and they want customers to be prepared for the change?
No - the possibility of having a dual stack installation will be still there.
From an infrastucture point of view this recommendation combined with SAP NetWeaver architecture will result in an explosion of SID names which leads to an explosion of application server instances and DBMS instances and an explosion of installed servers. I know it is possible to combine SIDs into a single DBMS using MCOD and to have multiple application servers in a single physical server, but there are issues with mulitple application server instances and MCOD use which make normal maintenance operations difficult.
I agree - MCOD is not a good solution for this problem.
I think it would be much better for customers to install dual stack systems and simply adjust the SAP profile parameters to disable one stack or the other. This way, you could still have 1 stack per application server instance and you would not be have to be creative with SAP SID names!!! Creating a DBMS instance or installing an additional server is not a simple nor economical proposition.
There are 36 * 36 * 36 (minus a few reserved) names for SIDs- this should be enough - also for the biggest customers
Of course one could install both and disable the one you don´t need - but this won´t help in dependency thing. If you e. g. install a dual stack instance for CRM and disable the Java part, you can nicely run it. In case of an upgrade, you will need to upgrade the Java part too (see above) although you don´t use it. The upgrade will detect the doublestack and wait for the java instance to be upgraded too. Same is true vice versa. And believe me: you don´t want that
In fact it is better to separate - that´s at least our experience. The main no-go for such a configuration on our side was the dependency thing. Since they are there and you can´t do much about them we decided to have a 1:1 relationship for ABAP backend and Java "frontend". You will get more instances (and names and databases) but you can patch applications independently from each other. So an implementation of a BI patch won´t imply that you finally also patch your ERP production and other systems that connect to that portal.
There are virtualization techniques available to not need more boxes, you can consolidate them on one machine as if you were installing a dual stack so that is not really an issue. This depends, of course, on the platform and database you use (e. g. Oracle does not support production installations in VMWare). We use for our Java instances Solaris on Opteron (or Intel 64bit) and zones/containers and for the ABAP part we use Linux + Xen. Both virtualization methods come with the OS (so no additional $$$) and both are supported by SAP.
The propagated advantage of having a dual stack installation (shared memory access etc.) is so small that it doesn´t outban the additional complexity - which is definitely there.
I hope those arguments will help to understand SAPs (and the consultants) position - get back if you want more
Markus

Issue in portal after abap stack upgrade

Hi,
Except travel and expenditure, everything is working fine after abap stack upgrade. we have restarted abap and portal 3-4 times, we use abap ume. we are getting error:
Portal runtime error.
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID: 18:57_27/02/12_0004_16184750
defaulttrace:
\#39;<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>/;sap-ext-sid=<ESID[url_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[url_ENCODE]>&sap-wd-tstamp=<$TimeStamp>&<FPNInfo[IF_false PROCESS_RECURSIVE]>&sap-explanation=<User.Explanation[SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PARAMETER_MAPPING PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>&\#39;; the problem occured at position 310. Cannot process expression <System.client> because Invalid System Attribute:
System:    &\#39;SAP_LocalSystem&\#39;,
Attribute: &\#39;client&\#39;.
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:125)
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     ... 29 more
#1.5 #00144FF922BF006B00000028000021AF0004B9F256577D3A#1330350388639#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#J2EE_ADM_EDJ#73##ERPDEV_EDJ_16184750#J2EE_ADM_EDJ#d2df5090614511e1cbb100144ff922bf#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Java###07:16_27/02/12_0004_16184750
[EXCEPTION]
#1#com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template &\#39;<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>/;sap-ext-sid=<ESID[url_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[url_ENCODE]>&sap-wd-tstamp=<$TimeStamp>&<FPNInfo[IF_false PROCESS_RECURSIVE]>&sap-explanation=<User.Explanation[SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PARAMETER_MAPPING PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>&\#39;; the problem occured at position 310. Cannot process expression <System.client> because Invalid System Attribute:
System:    &\#39;SAP_LocalSystem&\#39;,
Attribute: &\#39;client&\#39;.
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:125)
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
     at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:235)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:541)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:430)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
#1.5 #00144FF922BF006A0000001E000021AF0004B9F25959F274#1330350439133#com.sap.mw.jco#sap.com/tcwddispwda#com.sap.mw.jco#ESSEMP2#288##ERPDEV_EDJ_16184750#ESSEMP2#907dd803614911e1968500144ff922bf#SAPEngine_Application_Thread[impl:3]_6##0#0#Info##Plain###[WD JCO API] WebDynproExtension.addClientPool(SAP_R3_SelfServiceGenerics_ESSEMP2_EN_useSSO_(J2EE16184700)ID1578814350DB10044082816827940554End_9513223) with lang 'EN' and languages vector {EN,EN}#
#1.5 #00144FF922BF0062000016D7000021AF0004B9F26C7D264E#1330350760207#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eed5c7ef614411e1996800144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 207,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736980#Plain###Error! The following problem(s) occurred during request processing:#
#1.5 #00144FF922BF0062000016D9000021AF0004B9F26C7D286A#1330350760208#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eed5c7ef614411e1996800144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 207,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736980#Java###Error! Request failed due to failure of child requests#1#Request failed due to failure of child requests#
#1.5 #00144FF922BF0062000016DB000021AF0004B9F26C7D2DAC#1330350760209#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eed5c7ef614411e1996800144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 207,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Java###Request failed due to failure of child requests
[EXCEPTION]
#1#Request failed due to failure of child requests
     at com.sap.tc.cbs.server.dao.impl.Request.checkForFailedChildRequests(Request.java:494)
     at com.sap.tc.cbs.server.dao.impl.Request.capture(Request.java:398)
     at com.sap.tc.cbs.server.proc.RequestHandler.process(RequestHandler.java:138)
     at com.sap.tc.cbs.server.proc.RequestHandler.run(RequestHandler.java:121)
     at com.sap.tc.cbs.server.rt.threads.PerpetualRunnable.run(PerpetualRunnable.java:109)
#1.5 #00144FF922BF006200001777000021AF0004B9F26FD235FC#1330350816114#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eed5c7ef614411e1996800144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 207,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736988#Plain###            Error! The following problem(s) occurred during request processing:#
#1.5 #00144FF922BF006200001779000021AF0004B9F26FD23863#1330350816114#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eed5c7ef614411e1996800144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 207,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736988#Plain###            Error! The following error occurred during request processing:The build failed due to wrong or incomplete arguments, passed to the build tool.
Please check CBS service parameters against manual.#
#1.5 #00144FF922BF006600001720000021AF0004B9F26FFE4EC5#1330350819004#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##f556c50a614411e19dc200144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 208,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736987#Plain###            Error! The following problem(s) occurred during request processing:#
#1.5 #00144FF922BF006600001722000021AF0004B9F26FFE50DC#1330350819004#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##f556c50a614411e19dc200144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 208,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736987#Plain###            Error! The following error occurred during request processing:The build failed due to wrong or incomplete arguments, passed to the build tool.
Please check CBS service parameters against manual.#
#1.5 #00144FF922BF005F0000179B000021AF0004B9F2714FA0E9#1330350841110#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eeb712eb614411e1926f00144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 206,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736989#Plain###Error! The following problem(s) occurred during request processing:#
#1.5 #00144FF922BF005F0000179D000021AF0004B9F2714FA2FC#1330350841111#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eeb712eb614411e1926f00144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 206,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736989#Java###Error! Request failed due to failure of child requests#1#Request failed due to failure of child requests#
#1.5 #00144FF922BF005F0000179F000021AF0004B9F2714FA854#1330350841111#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eeb712eb614411e1926f00144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 206,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Java###Request failed due to failure of child requests
[EXCEPTION]
#1#Request failed due to failure of child requests
     at com.sap.tc.cbs.server.dao.impl.Request.checkForFailedChildRequests(Request.java:494)
     at com.sap.tc.cbs.server.dao.impl.Request.capture(Request.java:398)
     at com.sap.tc.cbs.server.proc.RequestHandler.process(RequestHandler.java:138)
     at com.sap.tc.cbs.server.proc.RequestHandler.run(RequestHandler.java:121)
     at com.sap.tc.cbs.server.rt.threads.PerpetualRunnable.run(PerpetualRunnable.java:109)
cbs.5:
#1.5 #00144FF922BF006E00009D0900000EEE0004B9E196C2E0E9#1330278454976#/Applications/CBS/Service##com.sap.tc.cbs.server.rt.sync.AccessOrc####n/a##446ca3fd5c7b11e195a000144ff922bf#Thread[CBS AccessQueue Orchestrator,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Plain###Access orchestrator failure#
#1.5 #00144FF922BF006E00009D1100000EEE0004B9E196C49580#1330278455088#/Applications/CBS/Service##com.sap.tc.cbs.server.rt.sync.AccessOrc####n/a##446ca3fd5c7b11e195a000144ff922bf#Thread[CBS AccessQueue Orchestrator,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Plain###Access orchestrator failure#
#1.5 #00144FF922BF006E00009D1900000EEE0004B9E196C664FD#1330278455207#/Applications/CBS/Service##com.sap.tc.cbs.server.rt.sync.AccessOrc####n/a##446ca3fd5c7b11e195a000144ff922bf#Thread[CBS AccessQueue Orchestrator,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Plain###Access orchestrator failure#
#1.5 #00144FF922BF006E00009D2100000EEE0004B9E196C81B65#1330278455319#/Applications/CBS/Service##com.sap.tc.cbs.server.rt.sync.AccessOrc####n/a##446ca3fd5c7b11e195a000144ff922bf#Thread[CBS AccessQueue Orchestrator,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Plain###Access orchestrator failure#
#1.5 #00144FF922BF00310000000000000DA90004B9F0155B9416#1330340708455#/Applications/CBS/Administration##com.sap.tc.cbs.service.CBSFrame#######SAPEngine_System_Thread[impl:5]_82##0#0#Info#1#com.sap.tc.cbs.service.CBSFrame#Java###Starting CBS service on node ...#1#16184750#
Pls suggest

Hi James Bond
From the exception above, it can be seen that the AppIntegrator iView is trying to run on the "SAP_LocalSystem" where it should be running on a "real" backend system.
Please check what is the System alias in this iView and make sure it points on a backend system which has the same alias in the Portal System landscape.
Hope that helps,
Robin Hood.

EHP4 Dual stack

hi guys,
we plan to upgrade Enterprise Dual stack(ABAP+JAVA) System to EHP4 system.
In EHP4 upgrade document it says, No dual stack supported for EHP4 installation..was that mean
only for Installation or upgrade too.
Seperate SID is required for EHP4 system after upgrade? Please confirm.
thanks

hi jaichan,
yes, you are right ..For new installation of SAP ERP to EHP4 level, you cannot install dual stack system..i have read in sap note 855534..please find below the extract from this note:
As of SAP Business Suite 7, you can no longer install Dual Stack Application Systems (ABAP+Java).
If you want to use both SAP Business Suite ABAP and Java Components in your system landscape, you have to proceed as follows:
1. Install a separate ABAP-based SAP Business Suite system.
2. Install the required Java components in a separate Java-based SAP system.
3. Configure the connection of the Java-based SAP system to the ABAP-based SAP Business Suite back-end system.
The SAP Business Suite 7 comprises: EHP4 for SAP ERP 6.0, SAP CRM 7.0, SAP SCM 7.0, SAP PLM 7.0, SAP SRM 7.0
As of now you will find the latest recommendations at a central place in SDN:
https://www.sdn.sap.com/irj/sdn/landscapedesign -> Distribution Models
You will also find information about the deployment of SAP NetWeaver usage types and the SAP Business Suite there.
but you can upgrade your previously installed SAP ERP dual stack system without having seperate SID's thing...
We have upgraded around 50 of our systems without any problem
thanks sunny

Mapping error in PI 7.4 dual stack

Dear Experts,
Recently we upgraded our system from PI 7.1 to PI 7.4 dual stack.
Scenerio is ECC->PI->SOAP(Webservice) synchronous
Issue in detail:
We are creating a invoice in ECC system through PI its updating in third party site using SOAP webservice and will get a reference number from that site and then updating in ECC as in synchronous way.
Invoice data's are reached PI sucessfully from ECC but it not updating in the site and getting below mapping error after upgarded to PI 7.4.
Your points will be highly appreciable.
Kindly help to sort out this issue.
Best Regards,
Monikandan

Hi Monikandan,
It seems you are trying the sign the payload in your java mapping. So, looking at the attached error, there could be 2 possibilities:
1) Either there is no certificate with alias: *_PRD
2) This certificate is stored in some "System" type keystore view which is not accessible from you mapping code. Try to move your certificate to some "User" keystore view.
Thanks & regards,
Piyush

PI 7.4 dual stack

Dear experts,
I understood PI 7.4 SP06 can be installed on dual stack ABAP+Java. If this is the case, what about ccBPM/BPM scenarios ? can support both ? only nwBPM/ccBPM ?
what about NWDS present version ?
Deva

Hi Deva,
In case there you are making use of Dual stack PI you CCBPM scenarios will work same as earlier dual stack PI versions. In case of Dual stack it will still be PI and not PO as PO comprises of Lone Java PI+ N/W BPM+ BRM on one system.
Also if you want to make use of N/W BPM it has to be installed seperately. Ideally you should go for lone Java if you want to make use of N/W BPM to minimise your hardware requirements.
Also NWDS version has to be less than or equal to the PI version being used.
Regards,
Sriram

Error in Dual Stack Splitting:SAPControl:GetAccessPointList not implemented

Hi,
Am doing dual stack split with Keep Database option. Environment is
OS- Sun Solaris SPARC 64 bit
Database – Oracle 11.2.0.3
System – ECC 6.0 (Netweaver 7.0) NUC
We stuck in 1sr step while taking export of JAVA. Error is – GetAccessPointList fail:SAPControl:GetAccessPointList not implemented : method name or namespace not recognized
I have upgraded kernel from 700 Sp 333 to 720 sp 700. also set parameter alternatively
service/protectedwebmethods = SDEFAULT
service/protectedwebmethods = DEFAULT
service/protectedwebmethods = NONE in all profiles, but still no luck.
Please find below logs.
Also output of command
Please find below log files, as I have executed command -
sapcontrol '-prot' 'NI_HTTP' '-nr' '20' '-function' 'GetAccessPointList' which gets completed successfully(20- Instance No of ABAP). Log file
-sapcontrol.log
but when I execute command
sapcontrol '-prot' 'NI_HTTP' '-nr' '00' '-function' 'GetAccessPointList'-- which shows error (00-instance no of SCS)
log file - sapcontrol1.log
Please find log files.
Regards
Vivek

Hi Vivek ,
Check for the permission of sapuxuserchk in all the exe directories including the local exe directory of SCS00
1563660 - sapcontrol, user authorization issues (SUM)
Thanks ,
Manu

Homogeneous system copy ECC 6.0 EHP4 dual stack system

Hello ,
I have a requirement of homogeneous system for the below Source system
Source system :
ECC6.0 EHP1 ABAP+java dual stack system with DB2 AIX
Required Target system:
ECC 6.0 EHP1 (same as target system except single stack java not required)
1 .I was trying to use db specific homogeneous system copy method wiht redirected restore script
2. Not possible to get downtime on source system hense it's a production system , then i used target system installaion with homogeneous system copy database specific mehthod
Problem is - it's asking migration export while creating the target system , but i don't have any migration export since i have not exported from source system .
please help us to proceed further.
Thanks in Advance.

2. Not possible to get downtime on source system hense it's a production system , then i used target system installaion with homogeneous system copy database specific mehthod
What did you choose to do in database specific method - DB2 backup/restore ?
//Backup Restore
Homegeneous system copy(database specific method)
Target -
As I understand, you have started IMPORT using SAPinst for target system installation. During IMPORT, what target system installation (only ABAP or what ?) you chose ?
//I took ABAP+JAVA
'Problem is - it's asking migration export while creating the target system , but i don't have any migration export since i have not exported from source system .'
This is because the source system is ABAP+Java, and now during target system installation, then IMPORT procedure is asking for Java Export dump.
Thanks

BI7 dual stack upgrade using 'resource minimised' method

Similar Messages

Maybe you are looking for