NW04s Upgrade

Hi.
I might be posing an irrelevant question here but I just wanted to be sure. Do we require any ALPHA conversion activity in case of an Upgrade from NW04(3.5) to NW04s? Or is it history from 3.1 onward?
Cheers
Anand

Thanks Prakash.
Cheers
Anand

Similar Messages

Nw04s upgrade queries regarding compatibility

Hi,
We are currently on EP6.0 SP10 and also are using standalone ITS
620. We are in the process of upgrading to NW04s ie EP 7.0 .Could
someone pls clarify the following
1) Will (our existing) ITS 620 be compatible with EP7 ?
2) Will our R/3 version ie 4.7 and OS WIN 2003 be compatible?
3) Are there any specific hardware requirements for EP7.0?
Help on this would be very much appreciated
Regards
Vineeth

Hi,
unfortunatly, the guy that configured the its/erp at that time does not work for us anymore, I don't have much info for that.
Min hardware EP7 :
Suitable backup system
Minimum disk space:
Database Software:
1 GB (x86, AMD64)
2 GB (IA64)
SAP system files (not including paging file):
5 GB (x86, AMD64)
8 GB (IA64)
SAP database files (not including paging file):
2 GB
4.3 GB of temporary disk space for every required installation DVD that
you have to copy to a local hard disk
To check disk space:
1. Choose Start® Programs® Administrative Tools ® Computer Management® Disk
Management.
2. Select the local drive.
3. Choose Properties.
Minimum RAM:
1.5 GB
To check RAM, in the Windows Explorer choose Help® About Windows.
Caution
During the installation with SAPinst, make sure not to enter a value larger
than the maximum Java heap size of your platform. For more information,
see the corresponding documentation of your Java Development Kit - JDK.
Paging File Size:
1 times RAM plus 8 GB
For 64-bit systems, also see SAP Note 153641. If you want to install only a small
system, contact your hardware partner for appropriate swap space values.
To check paging file size:
1. Right-click My Computer and choose Properties.
2. Choose Advanced® Performance Settings.
3. If required, in section Virtual Memory, choose Change.
From my experience, you can add easily 10 gb to your EP6 portal for the upgrade to EP7.
At least 2.5 gb ram, and dual processor. I once used a dual 2.4 xeon, it was ok.
JDK 1.4.2_11 for usa and jdk 1.4.2_13 for canada because of the new timezone change.
Brad

NW04 - Upgrade J2EE to SP14

Hi,
I have a strange problem when I try upgrade my Linux TestDrive from SP12 to SP14.
Hostname: NW
The installation is working on SP12. Im able to deploy both from NWDS and SDM.
The sapinst is executed with the remotehost parameter: sapinst SAPINST_USE_HOSTNAME=nw4host
The upgrade goes smooth until Deploy via SDM/JEE where I get a Error: Unable to compare host[nw4host] and host[tetasoft-002] Throwable: java.net.UnknownHostException Throwable message: tetasoft-002: tetasoft-002
The strange thing is that my laptop is called tetasoft-002.
Any idea how to solve this? Is there a parameter I should use?
callSdmViaSapinst.log:
Nov 1, 2005 1:09:39 PM   Info: The deployment prerequisites finished without any errors. All items are correct.
Nov 1, 2005 1:10:00 PM   Error: Unable to compare host[nw4host] and host[tetasoft-002] Throwable: java.net.UnknownHostException Throwable message: tetasoft-002: tetasoft-002
Nov 1, 2005 1:10:00 PM   Info: Saved current Engine state.
Nov 1, 2005 1:10:00 PM   Info: Error handling strategy: OnErrorStop
Nov 1, 2005 1:10:00 PM   Info: Update strategy: UpdateLowerVersions
Nov 1, 2005 1:10:00 PM   Info: Starting: Update: Selected development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4014.00.0000.20050818152214.0000' updates currently deployed development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4012.00.0000.20050331133103.0000'.
Nov 1, 2005 1:10:00 PM   Info: SDA to be deployed: /usr/sap/NW4/DVEBMGS00/SDM/root/origin/sap.com/SQLTrace/SAP AG/6.4014.00.0000.20050818152214.0000/SQLTrace.ear
Nov 1, 2005 1:10:00 PM   Info: Software type of SDA: J2EE
Nov 1, 2005 1:10:00 PM   Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Nov 1, 2005 1:10:00 PM   Error: Unable to compare host[nw4host] and host[tetasoft-002] Throwable: java.net.UnknownHostException Throwable message: tetasoft-002
Nov 1, 2005 1:10:01 PM   Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Nov 1, 2005 1:10:01 PM   Error: Aborted: development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4014.00.0000.20050818152214.0000':
CPO data could not be get.
com.sap.sdm.apiint.serverext.servertype.deployment.DeploymentActionException: Error: Caught the following error or exception: "com.sap.sdm.apiint.serverext.servertype.deployment.DeploymentActionException"
Additional error message is:
Caught exception from deploy service of SAP J2EE Engine. Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.
com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [nw4host] with user name: [J2EE_ADMIN]
                                                  Check your login information.
                                                  Exception is:
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot create new RemoteLoginContext instance.]
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.checkLoginCredentials.DMEXC)
Additional error message is:
com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [nw4host] with user name: [J2EE_ADMIN]
                                                  Check your login information.
                                                  Exception is:
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot create new RemoteLoginContext instance.]
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).NO_CPO)
Nov 1, 2005 1:10:02 PM   Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Nov 1, 2005 1:10:02 PM   Info: -
Deployment was successful -
Nov 1, 2005 1:10:02 PM   Info: Summarizing the deployment results:
Nov 1, 2005 1:10:02 PM   Error: Admitted: /home/hda/SAP Download (Linux)/test/J2EE-RUNT-CD/J2EE-ENG/ONLINE/SAPJTECHS14_0.SCA
Nov 1, 2005 1:10:02 PM   Error: Processing error. Return code: 4
Best regards
Henrik

Gregor,
I have exactly the same symptom in SP9 --> SP13 on clustered Solaris WebAS/EP installation. I am curious as to why you think it's to do with DISPLAY variable - though I wouldnt be at all surprised by some of the imaginings that sapinst has.
In my case, I get the RemoteLoginContext problem, but no 'comapre host' message. Simply that the J2EE administrator credential check failed. At this time, thye J2EE is up and running, all services and apps are in the started/running state; the SDM is stopped (but gets started by the deploy task of sapinst). There is no corruption of the secure store password so far as I can gather.
My installation sounds somewhat similar to Henrik's:
Physical Host : spvcs53prod
Virtual SCS IP (on same host): spscs50prod
Virtuaal CI IP (on same host): spci50prod
..\sapinst SAPINST_USE_HOSTNAME=spci50prod SAPINST_START_GUI=false
The CI is on a virtual host too, for system admin and monitoring reasons, though it is not in a switchable cluster group. I have had some problems for example with the delivered startsap and stopsap scripts. These cannot locate the required hostnames accurately on network adapters as the output of the ping command varies depending on the physical/virtual setup. (start.sopsap parse the ping result to verify hostnames). Maybe sapinst is doing something similar in these installation situations?
Any help appreciated, as we are now stuck delivering a production cluster !
Thanks.

What is the quickest to upgrade disaster recovery system to NW04s in MSCS?

Hi,
I have an issue which I need assistance from SAP/Windows 2003 experts.
Hope you can share your opinion on an SAP upgrade issue we're grappling with.
Objective : Upgrade our SAP Bank Analyzer disaster recovery environment from NW04 to NW04s SR2, to be same as production. Both production and disaster recovery (DR) run under two node WIN2003 Enterprise MSCS. The SAP CI usually runs on node A and Oracle 10g runs on node B.
The Oracle software, parameters, database files and the SAP folder \usr\sap are already matching. These files and folders are on EMC mirrored disks, so this will be automatically synchronized from production status.
Therefore I believe it is only the SAP software components on the local hard disks - binaries, DLLs, registry, DCOM, environment variable etc, that need to be upgraded on the two DR machines.
For your information, the current SAP 6.40 instance, Oracle 10g instance, MSCS failover capability are all working in the DR environment as we just did an exercise a month ago to prove this.
 Disaster Recovery Environment :
On shared drives that are synchronized between prod and DR : SAP folder \usr\sap including the kernel binaries, Oracle parameter files, database datafiles, redologs, sapbackup etc.
Issue : What is the quickest and reliable method to achieve the objective? Other than the SAP kernel binaries and profiles, I'm not certain what other related components are updated/replaced that are stored locally on each of the clustered machine.
There are three different approaches we can think of :
1) Repeat the whole NW04s upgrade process in the DR environment. This takes several days. The exposure of not having a disaster recovery environment for several days is a minus.
 or
2) Un-install the SAP CI and MSCS definitions. Synchronise the DR shared disks from production to have the upgraded production NW04s database contents and SAP folder \usr\sap.
Use SAPINST to re-install either traditional CI or ASCS option 'System Copy". And then re-create the MSCS definitions for SAP CI using SAPINST again.
The disadvantage is I can't trial this in any other of our environments. Also, we want to run with the traditional CI instead of ASCS until early next year for other reasons. So we would have to reverse the ASCS back to traditional CI with this method, by reversing the steps in OSS NOTE 101190 "Splitting CI after upgrade to 700".
 or
3) Somehow identify all the SAP components that are stored locally on each machine (eg. environment variables, registry settings, DCOM definitions, DLL in various folders). Then just copy them from Production to DR machines or recreate them. I'm not confident of identifying the local SAP components. And I have not been able to find any good OSS NOTEs or forum threads on this topic. The most helpful OSS NOTE I can find is 112266 point 13 and 19.
Thanks for any input.
Benny Kwan

See:
* https://support.mozilla.com/kb/Form+autocomplete
* Firefox > Preferences > Privacy > History: "Remember search and form history"
* Autofill Forms: https://addons.mozilla.org/firefox/addon/autofill-forms/

SAP XI 2.0 to 3.0 Upgradation

Hi All
Please let me know whether it is possible to upgrade SAP XI 2.0 to 3.0.
If Yes, what all componenents from XI 2.0 can be leveraged to 3.0.
If No, is it going to be fresh SAP XI 3.0 implementation.
Pls let me know if your comments
Regards
Madhan Doraikannan

Hi Madhan,
Take a look at these threads...
upgrade from xi 2.0 to xi 3.0
Xi 2.0 to 3.0 migration
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.highlightedcontent?documenturi=/library/ep/nw04/upgrade/componentUpgradeGuide-SAPExchangeInfrastructure+3.0.pdf
Hope these help!
regards,
Prashanth

Is it really necessary to re-install the dialog instances?

Hi,
We are upgrading from NW04 (WAS 6.40) to NW04s (WAS 7.00) ABAP SR2 only on Windows 2003 with Oracle 9i. There is no JAVA stack in our environment and we don't need it.
In production system we have five separate dialog instances on five different physcial machines. All these application servers runnon Windows 2003 as well.
Reading through the NW04s upgrade guide "SAP NetWeaver 2004s
Application Server ABAP" dated 28th November 2006,
section 6.26 states we have to "install the new dialog instance on top of the old dialog instance".
In the past upgrades eg. upgrade to NW04, we did not have to use SAPINST to re-install the dialog instance. Instead, the official NW04 (WAS6.40) upgrade guide just instructs us to amend instance profile parameters and copy the new version of kernel binaries either manually or using sapcpe.
I want to avoid doing this re-installation work for the five dialog insatnces. Because I want to reduce the production outage period.
Question all the upgrade experts
1) Does any one have experience that indicates I should follow the SAP documentation to un-install 6.40 instance and then re-install at 7.00 level again?
2) Also, what is the technical reason to uninstall and re-install?
The full section 6.26 section paragraph is pasted here.
6.26 Upgrading or Installing Dialog Instances
After the upgrade of the central instance, you need to upgrade the dialog instance to the new release.
To do this, you install the new dialog instance on top of the old dialog instance using the tool SAPinst.
You can now also install additional dialog instances, if necessary.
Procedure
Proceed as described in the document Installation Guide ‒ <SAP NetWeaver / SAP solution> <Technology> on
<Operating System>: <Database>.
Caution
If you upgrade a dialog instance, make sure to use the same instance number as on the source release.

Hi Matt,
Thanks for your detailed response. Our system is very much heavy batch processing oriented. Therefore our management does not want to hand over the production system until all dialog instances are ready at the new version.
It would be great if the upgrade process is quick as you pointed out.
Can you show me where this "upgrade dialog instance" option in V7 SAPINST? FYI. I should be able to start sapinst over the next few days to look for this upgrade option.
However, I just got a response from ASIA-PACIFIC OSS that says I have to un-install and re-install the existing dialog instance. Their response is as follows :
The dialog instance does not need to be upgraded since in the dialog
instance, no database exists but only the kernel files and some
profiles exist. After the upgrade, you should re-install the dialog
instance since in the central instance, the kernel release has been
changed to 700 due to the upgrade. But in the old dialog instance,
it should still have the old release kernel files and profiles.
Thus, by using reinstallation, the new release kernel files will be
installed in the dialog instance.
As to the procedure, you should uninstall the old instance firstly since during the installation, the files will be put to the same path of the
old instance.We recommend you to backup the old dialog instance files
before the installation.Sorry there is no related note but you can refer to the upgrade and installation guides.
Thanks for your input and assistance.
Benny Kwan
National Australia Bank

Error in hierarchy presentation

Hi.
In my PRD system, whenever I run a query that has a hierarchy or try do display some data based on a hierarchy (GL), I get the foll error message:
System error in program SAPLRSDRH and form BUILD_VIEW-3-
In addition to that we also get the foll error when we try to choose the filter button in the navigation bar:
CL_RSR_WWW_RENDERER and form GET_FILTER_VALUES_CH
Any ideas?
We recently upgraded our Oracle to 10g from 9 in preparation for an NW04s upgrade.
Cheers
Anand

Thanks Paulo.
But we are on 3.5 already and this note seems relevant for 3.1c and below.
Have you seen this error:
System error in program SAPLRSDRH and form BUILD_VIEW-3-
Cheers
Anand

Error while upgrading NW04s to sp5

I installed NW04s in my machine. I am trying to upgrade it to sp5. I could upgrade the ABAP stack to sp5 without any problem. When i am doing java stack, i could update all other support packages except the one 'CAF05_0-10003464.SCA'. When this package is on progress, the process gets almost completed and gives the status also 'deployed'. But after that it throws the following error and the status also changed to 'not deployed'.
ERROR: Not updated. Deploy Service returned ERROR:
 java.rmi.RemoteException: Exception in operation update with application sap.com/caf~tc..
 Reason: com/sap/caf/metamodel/ApplicationInterface; nested exception is:
 java.lang.NoClassDefFoundError: com/sap/caf/metamodel/ApplicationInterface
 at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:682)
 at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1278)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
 at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
 at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
 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:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
 Caused by: java.lang.NoClassDefFoundError: com/sap/caf/metamodel/ApplicationInterface
 at java.lang.Class.getDeclaredMethods0(Native Method)
 at java.lang.Class.privateGetDeclaredMethods(Class.java:1655)
 at java.lang.Class.privateGetPublicMethods(Class.java:1778)
 at java.lang.Class.privateGetPublicMethods(Class.java:1788)
 at java.lang.Class.getMethods(Class.java:832)
 at com.sap.engine.services.ejb.deploy.xml.MethodsExtractor.getWithNotSpecifiedMethodInterface(MethodsExtractor.java:156)
 at com.sap.engine.services.ejb.deploy.xml.MethodsExtractor.getAllMethodsInBean(MethodsExtractor.java:103)
 at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.getMethodXml(EJBJarParser.java:1168)
 at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.processContainerTransaction(EJBJarParser.java:1023)
 at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.processAssemblyDescriptor(EJBJarParser.java:924)
 at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.parseXml(EJBJarParser.java:156)
 at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.parseXml(EJBJarParser.java:97)
 at com.sap.engine.services.ejb.deploy.DeployAdmin.parseSingleJar(DeployAdmin.java:298)
 at com.sap.engine.services.ejb.EJBAdmin.buildAppDescriptorBeforeUpdate(EJBAdmin.java:408)
 at com.sap.engine.services.ejb.EJBAdmin.needUpdate(EJBAdmin.java:341)
 at com.sap.engine.services.deploy.server.application.UpdateTransaction.getContainersWhichNeedUpdate(UpdateTransaction.java:537)
 at com.sap.engine.services.deploy.server.application.UpdateTransaction.getConcernedContainers(UpdateTransaction.java:493)
 at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:263)
 at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:164)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:670)
 ... 10 more
 For detailed information see the log file of the Deploy Service.
06/11/29 12:14:54 - ***********************************************************
Nov 29, 2006 12:14:54... Info: End of log messages of the target system.
Nov 29, 2006 12:14:54... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Nov 29, 2006 12:14:54... Error: Aborted: development component 'caf/tc'/'sap.com'/'MAIN_APL70VAL_C'/'644873':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Exception in operation update with application sap.com/caf~tc..
Reason: com/sap/caf/metamodel/ApplicationInterface; nested exception is:
 java.lang.NoClassDefFoundError: com/sap/caf/metamodel/ApplicationInterface
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Nov 29, 2006 12:14:55... Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Can anyone help me to sort out this problem?

Symptom
JSPM hangs by upgrade from SP4 to SP5 with the following message into the log file:
ERROR: Not updated. Deploy Service returned ERROR: java.rmi.RemoteException: Exception in operation
update with application sap.com/caf~tc..
Reason: com/sap/caf/rt/exception/CAFDeleteException; nested exception is: ,,java.lang.NoClassDefFoundError:
JUP fails by NW04 SP14 -> NW04s SP5 upgrade with the message into log file:
ERROR: Not updated. Deploy Service returned ERROR: java.rmi.RemoteException: Exception in operation
update with application sap.com/caf~tc..
Reason: com/sap/caf/rt/exception/CAFDeleteException; nested exception is: ,,java.lang.NoClassDefFoundError:
Reason and Prerequisites
Deployment of CAF component sap.com/caf~tc failed by deployment scenario of type:
1. The application is deployed with a reference to Lib1, where Class A
is included.
2. Then class A is moved from Lib1 to Lib2 (removed from Lib1);
3. Then the new version of the application which has references to both
libraries Lib1 and Lib2 is deployed via SDM;
4. The deployment fails with NoClassDefFoundError: class A.
For patricular case we have the situation:
The class com/sap/caf/rt/exception/CAFDeleteException was moved from
caf/runtime/ear to caf/runtime/api/lib between the SPs.
Solution
Please follow the steps:
1. Close JSPM application
2. Start <device>:\usr\sap\<sid>\JC<instance number>\SDM\program\RemoteGui.bat
3. From the menu invoke "SDM Gui" -> "Login" and enter your SDM password
4. Navigate to tab "Undeployment" and select CAF component caf~tc, press button "Select" and "Start Undeployment" and complete undeployment confirming it.
5. Navigate to tab "Deployment" and select CAF component using plus button and select option "Update deployed SDA/SCAs that have any version" into Deployment configuration options below and complete deployment confirming it.
6. Close "SDM Gui" application.
7. Restart JSPM and on the step "Select package type" select option "Single support packages" in order to update all other components, which left not deployed.
8. On step "Specify Queue" select all not deployed components and complete their deployment.
An alternative way is:
1. If there is a problem with CAF deployment do not stop the upgrade application.
2. Open command prompt and go to SDM\program directory
3. Execute: sdm jstartup "mode=integrated"
4. Execute: startserver
5. After that start the SDM remote GUI application
6. From the menu invoke "SDM Gui" -> "Login" and enter your SDM password
7. Navigate to tab "Undeployment" and select CAF component caf~tc, press button "Select" and "Start Undeployment" and complete undeployment confirming it.
8. Logout and close "SDM Gui" application.
9. In the command prompt execute: stopserver
10. In the command prompt execute: sdm jstartup "mode=standalone"
11. Go to the Upgrade application and restart the process from the point of failure
Best Regards,
Barry.

Error while upgrading NW04s ABAP from sp7 to sp8

Hi,
I installed NW04s in my system and its ABAP stack is upgraded to sp7. When i was upgrading its SAP_BASIS support package to sp8, i got the following error.
Error in phase: IMPORT_PROPER
Reason for error: TP_BUFFER_INCONSISTENCY
Return code: 0008
Error message: Pkgs. in queue don"t exist in the tp buffer (e.g. SAPKB70008)
This phase imports all Repository objects and table entries. It may terminate for the following reasons:
○ TP_INTERFACE_FAILURE: The tp interface could not be called.
○ TP_FAILURE: The tp program could not be executed. For more information, read the SLOG or ALOG log files.
○ TP_STEP_FAILURE: A tp step could not be performed successfully. You can find the source of error in the relevant log, for example, in the import log.
If a tp step 6, N or S is in the termination message, it is a step independent of the transport request. The corresponding logs are contained in the log overview under the node Import steps not specific to the transport request.
You can also find these logs in the following files in the log subdirectory of your transport directory (usually /usr/sap/trans/log):
tp step 6: P<YY><MM><DD>.<SID>
tp step N: N<YY><MM><DD>.<SID>
tp step S: DS<YY><MM><DD>.<SID>
To display these files, run report RSPUTPRT or call transaction AL11.
Can anyone help me to resolve this problem?
Thanks in advance.

I have the similar problem to yours with tp_buffer_consistency at the xpra_phase when I was runing SAINT on a SAP R/3 Service Tool (RTCTOOL) with SAPKITAR19.
Shall you confirm what you have solved your problem are:
1) You have removed registers from the file /usr/sap/trans/buffer/SID which contains the troubled register, an example SAPKNNNNNN. First make a backup of that file before removing registers.
2) You have removed registers from the two tables: PAT01 (PATCH=SAPKNNNNNN), and PAT03 (PATCH=SAPKNNNNNN)
3) Invoke the trx SAINT
4) Installation package-->load package --> from application server
5) Select the uploaded SP and click the button Continue.
6) Anything else.
Appreciate in hearing from your input.
Rodolfo

Universal Worklist UWL not working in NW04s SPS9 after upgrade from NW04

Hello all,
this is just a hint in case anyone has the same problem with the UWL.
It happened to me in 2 cases, that in a Portal 7 SPS9 the UWL only showed a blank page after upgrade from NW04. In NW04 the UWL worked.
The reason for it was something like a corrupt deployment (but there were no according error messages in any log files). The SAP Support told me to redeploy the UWLJWF*.sca according to note 895523, that worked.
You can check whether the deployment is the reason of a non-working UWL setting the property "Launch Web Dynpro UI" to 'no'. Then the old HTMLB sources (that should work) are used (But it is not recommended to use the old sources anymore)
Kind regards
Andreas

.. just a hint ..

Portal Upgrade from Nw04 6.0 to Nw04s 7.0

Hi all,
Im trying to perform the portal upgrade from version 6.0 Nw04 SP 19 to version 7.0 Nw04s.
During the preparation I obtain the following error:
#Java###The software component com.wilytech.jmxservice/wilytech.com could not be read from the BC_COMPVERS table; the table schema may be outdated. Fix it and then repeat the phase from the beginning.##
I have implemented note n 873624 in order to align the keyname and the keyvendor in sap manifest.mf but with no luck, the detect start release component fails with the same error.
Any suggestion?
Thanks and regards
alessio

Hi,
you can find a good startup in the guide <a href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5e1226c7-0601-0010-7d82-a8134e833150">Enterprise Portal Migration Update</a>
hope this helps.
alessio

Upgrade Ep6 to NW04s portal - deploy error

I am upgrading our EP 6 system to NW04s w/Portal. Java AS only. No ABAP. In the DEPLOY_ONLINE phase it is stopping after about 2 hours.
When I restart it, from the logs it appears to be restarting from the beginning instead of where it stopped. But I can't find the true cause of why it's stopping in the first place.
My arch logs are not full and my tablespaces are ok, so the DB didn't fill up with anything more than it should.
The logs show that most items were deployed, even though with warnings. 2 errored out, although I can't find why in the detailed logs:
Aug 4, 2006 12:10:42 PM Info: Summarizing the deployment results:
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/ADSSAP08_0-10003001.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BIIBC06_0.SCA
Aug 4, 2006 12:10:42 PM Info: OK: /usr/sap/put/PD1upg/data/archives/BIWEBAPP06_1.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BIMMR08_0-10002782.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BIUDI08_0-10002781.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5***03_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5BUA03_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5BUY02_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5COM02_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5DCO02_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5ESS03_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5HRA03_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5INV02_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5MSS03_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5MTC02_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5PLA02_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5PRS02_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5PSS03_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5QIN02_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5SAL02_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5SUP02_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/CAF08_0-10003464.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/CAFKM08_0-10003478.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/CAFUM08_0-10003472.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/EPPSERV08_0-10003474.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/EPWDC08_0-10003557.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/EPBC208_0-10003489.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/FSCMBD03_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/ISHERCSS03_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/KMKWJIKS08_0-10003021.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/KMCBC08_0-10003491.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/KMCCM08_0-10003492.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/KMCCOLL08_0-10003493.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/LMPORTAL08_0-10003487.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/LMTOOLS08_0-10003486.SCA
Aug 4, 2006 12:10:42 PM Info: OK: /usr/sap/put/PD1upg/data/archives/NETPDK08_0-10003351.SCA
Aug 4, 2006 12:10:42 PM Info: OK: /usr/sap/put/PD1upg/data/archives/RTC08_0-10003494.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/RTCSTREAM08_0-10003488.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/SAPCRMDIC03_0.sca
Aug 4, 2006 12:10:42 PM Error: Aborted: /usr/sap/put/PD1upg/data/archives/SAPEU08_0-10003026.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/SAPPCUIGP03_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/SAPASR03_0.sca
Aug 4, 2006 12:10:42 PM Error: Aborted: /usr/sap/put/PD1upg/data/archives/SAPESS03_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/SAPMSS03_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/SAPPSS03_0.sca
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/UMEADMIN08_0-10003471.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/UWLJWF08_0-10003490.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/VCBASE08_0-10003602.SCA
Aug 4, 2006 12:10:42 PM Info: OK: /usr/sap/put/PD1upg/data/archives/VCFLEX08_0-10003616.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/VCFRAMEWORK08_0-10003624.SCA
Aug 4, 2006 12:10:42 PM Info: OK: /usr/sap/put/PD1upg/data/archives/VCKITGP08_0-10003617.SCA
Aug 4, 2006 12:10:42 PM Info: OK: /usr/sap/put/PD1upg/data/archives/VCKITXX08_0-10003615.SCA
Aug 4, 2006 12:10:42 PM Warning: Warning: /usr/sap/put/PD1upg/data/archives/WDEXTENSIONS08_0-10003618.SCA
Aug 4, 2006 12:10:42 PM Error: Processing error. Return code: 4

Hello,
We are having the exact same issue when DEPLOY_ONLINE encounters WDEXTENSIONS08_0-10003618.SCA as part of the NW2004s upgrade process.
We just submitted an OSS message to SAP about it --- but I am wondering if you have received a solution already?
Is this a bad support package that SAP released?

Webdynpro error after upgrade NW04 to NW04s sp9

Hi,
I created some WD in NW04 using JDI. After upgrade to NW04s i got error messages in the program. The messages look like:
Error com.sap.tc.webdynpro.progmodel.api.IWDApplicationStateChangeInfo cannot be resolved (or is not a valid type) for the argument stateChangeInfo of the method wdDoApplicationStateChange LeaveReqComp.java OJL_TEST_Dpoczelfbedwebdynreqbelastingdienst.nl/gen_wdp/packages/nl/belastingdienst/zelfbed line 203
Hope somebody can help me solve my problem.
Kind regards,
Maarten.

Hi Maarten
I am also facing similar sort of problem when i am trying to import the local web dynpro DC into 2004s that was build n exported from 2004 and when i try to build it in 2004s i get error
com.sap.tc.webdynpro.progmodel.api.IWDApplicationStateChangeInfo cannot be resolved for the argument stateChangeInfo of the method wdDoApplicationStateChange
com.sap.tc.webdynpro.progmodel.api.IWDApplicationStateChangeReturn cannot be resolved for the argument stateChangeReturn of the method wdDoApplicationStateChange
were u able to solve the problem if yes please help me in that case
thanks !
Asif

NW04S SP04- SP07 upgrade, 300 seconds between each DC deployed

Hi,
I am currently running an SP upgrade on NW04S from SP04 to SP07 on an EP system running on HP-UX IA64.
However, there is a problem with SDM/JSPM (JSPM been updated to SP07 without problems) which is apparant by the fact that there is a five minute wait (300 s) between each development component which is deployed. So far the deployment has taken two hours, but it will take days to complete with the current tempo.
The SDM logs indicate the problem fairly clear:
May 29, 2006 10:34:01... Info: Starting: Update: Selected development component
'tc/epbc/pcm/adminapi/java'/'sap.com'/'SAP AG'/'7.0007.20050929163406.0000'
updates currently deployed development component 'tc/epbc/pcm/adminapi/java'/'sap.com'/'SAP AG'/'7.00.20050713145732.0000'.
May 29, 2006 10:34:01... Info: SDA to be deployed: /usr/sap/ED3/JC16/SDM/root/origin/sap.com/tc/epbc/pcm/adminapi/
java/SAP AG/7.0007.20050929163406.0000/tc~epbc~pcm~adminapi~java.sda
May 29, 2006 10:34:01... Info: Software type of SDA: primary-library
May 29, 2006 10:34:01... Info: ***** Begin of SAP J2EE Engine Offline Deployment (Library component of SAP J2EE Engine) *****
May 29, 2006 10:39:02... Error: An error occured in JStartup Framework:
The instance with instance name 'JC_sapED3_ED3_16 ' did not respond within 300 s.
Throwable: com.sap.bc.proj.jstartup.impl.JStartupClusterControlExceptionImpl Throwable message:
The instance with instance name 'JC_sapED3_ED3_16 ' did not respond within 300 s.
May 29, 2006 10:39:02... Info: No information about the
J2EE engine cluster is available. 
The offline deployment process is continuing.
May 29, 2006 10:39:02... Info: ***** End of SAP J2EE Engine Offline Deployment
(Library component of SAP J2EE Engine) *****
May 29, 2006 10:39:02... Info: Finished successfully: development component
'tc/epbc/pcm/adminapi/java'/'sap.com'/'SAP AG'/'7.0007.20050929163406.0000', grouped by
What I don't understand is how the spaces appended after the profile name have appeared (in line
The instance with instance name 'JC_sapED3_ED3_16 ' did not respond within 300 s.
). I tried to search some configuration files, but nothing yet.
Note 942411 is the closest I have found from SAP regarding this problem, but I can find nothing in the dev_jcontrol logs.
Is there any way to resolve this issue, or reduce the wait time to something significantly less than 300 s?

Hi Vyara,
Actually, I had no problems login in with visual admin and accessing SAP EP while the update was running.
(haven't checked the logs or jcmon though)
I realized I forgot to set the systemcomponentstate of SDM to mode=activate:
 StopServer.sh
 sdm.sh jstartup mode=standalone
 sdm.sh systemcomponentstate mode=activate
 sdm.sh jstartup mode=integrated
 StartServer.sh
And after doing that and restart the system, things look better.
Thanks for your help

Upgrading Portal from NW04 Sp14 to NW04S SP 9

Hi,
We are preparing to upgrade our EP 6 , NW04 SP 14 highly available installation to NW04S SP 9. It seems JSPM is the tool that comes with NW04s SP 9 which runs the upgrade for existing NW04s systems. However NW04 SP14 does not have this tool it only has SDM. Would be grateful if someone could tell me how to start off the upgrade? Do we need to deploy the JSPM from NW04s SP9 via SDM first on existing system? or is there another tool to start this upgrade?
Tarek

Hi,
1.Is this SP25 upgrade from SP24 will support the IE8 and Firefox 3.5
without any issues for webdynpro application running as of now?
For this you can refer SAP note 1098009, 1296463 and 960549.
2.is it required to upgrade ESS and MSS and anything on ERP side along
with Portal upgrade to SP25
Yes, you should upgrade ESS/MSS to keep it in sync with NW SP level. You can check below link for SP level of ESS/MSS with NW patch level and backend system patch level:
[Link|https://wiki.sdn.sap.com/wiki/display/ERPHCM/HOW%20TO%20GET%20RID%20OF%20SP%20STACK%20MISMATCH%20ISSUES]
3.After upgrade NWDI to SP25, all the present tracks with custom
components will work as it is?
It should work as such there is no well known issue with existing track after upgrade.
Thanks
Vijay Kalluri

NW04s Upgrade

Similar Messages

Maybe you are looking for