BI 7.0 upgrade from SP14 to SP18
Hi Friends,
We are upgrading SAP BI 7.0 from SP14 to SP18 and one of the source systems which is CRM 5.0 is not upgrading. So i want to know is there any impacts to data sources that we are using for CRM data and what are the steps we have to consider in this scenario.
Thanks,
Mani.
As per my knowledge there is no impact on the datasources.
As your CRM is not upgrading,there will no change in the datasource and their structures.and mappings in the transfer rules. if u have upgraded the CRM system then you might observe some new datasources along with new upgrade version.
Similar Messages
-
Tranport portal content from SP14 to SP18
Hello,
Is it possible and advisable to transport portal content (iviews, roles, etc) from a portal on EP6 SP14 to EP6 SP18? Do I need to manually move configuration from one portal to the other? What are my options?
Thank you for feedback.
KevinHi Kevin,
There should be absolutely no problem in transporting EPAs from SP14 to SP18 (as far as the transport mechanism in concerned; as far as SP14 based PAR implementations are concerned, they maybe should be checked if they use some undocumented APIs which are always subject to change without notice, but from your question I don't think that this was your problem/question).
> Do I need to manually move configuration from one portal to the other
What conf are you thinking of? As far as PCD objects and their conf is concerned, as said, for that you should use the normal transport packages.
As far as the KM config is concerned, this can be transported, too, but that is (totally independent from SP-level questions) something where one has to be careful (the best choice is only to bundle a configArchive with special own settings one is aware of, and not to transport the complete KM config).
Hope it helps
Detlev -
Downtime for upgrade from SP14 to SP23 - PI 7.0
Hello All,
What is the estimated downtime for upgrading PI7.0 from SP14 to SP23. We only have one application server in the environment and the decision to upgrade will happen based on the downtime information . Appreciate any response . Thanks Rahul.Hi Rahul,
We have recently upgraded our PI 7.0 system from SP 21 to SP 21.
Basis team has requested for 19 hrs downtime. But the actual downtime that was required was less than 10 hours.
During upgrade, you have a downtime minimisation approach which would enable you to perform few actvities online without bringing down the system.
To follow this approach, Goto the transaction code "SAINT" --> Extras --> Settings --> Import Queue --> Import Mode.
There would be an option called "Downtime-minimized". Check that option so that you would be able to reduce the downtime during the upgrade.
Regards,
Subbu -
Exception in rpdata after upgrade from SP11 to SP18
Hi All,
after updating Web AS and ADS from NW04 SP11 to SP18 I get the following error when testing the ADS webservice via http://:/AdobeDocumentServices/Config.
com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception in method rpData.
at com.adobe.AdobeDocumentServicesLocalLocalObjectImpl0.rpData(AdobeDocumentServicesLocalLocalObjectImpl0.java:148)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)
at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)
at SoapServlet.doPost(SoapServlet.java:51)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
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.NullPointerException
at java.lang.String.<init>(String.java:390)
at com.adobe.AdobeDocumentServicesWorker.execute(Unknown Source)
at com.adobe.AdobeDocumentServicesEJB.processRequest(Unknown Source)
at com.adobe.AdobeDocumentServicesEJB.rpData(Unknown Source)
at com.adobe.AdobeDocumentServicesLocalLocalObjectImpl0.rpData(AdobeDocumentServicesLocalLocalObjectImpl0.java:120)
... 25 more
java.lang.NullPointerException
at java.lang.String.<init>(String.java:390)
at com.adobe.AdobeDocumentServicesWorker.execute(Unknown Source)
at com.adobe.AdobeDocumentServicesEJB.processRequest(Unknown Source)
at com.adobe.AdobeDocumentServicesEJB.rpData(Unknown Source)
at com.adobe.AdobeDocumentServicesLocalLocalObjectImpl0.rpData(AdobeDocumentServicesLocalLocalObjectImpl0.java:120)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)
at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)
at SoapServlet.doPost(SoapServlet.java:51)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
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)
I´ve updated the ADS regarding to this thread: https://forums.sdn.sap.com/click.jspa?searchID=1034429&messageID=1964510 and SAP Note 727168.
But I couldn´t remove and register the "ReaderRights" because I´m getting the error:
Error while loading service Document Services Configuration
com.sap.engine.services.adminadapter.exception.AdminException: com/adobe/service/sap/configuration/ConfigurationException
when choosing the "Document Services Configuration" service in Visual Admin
We don´t want to use interactive forms at the moment (just PrintForms) so we don´t need the ReaderRights, correct?
Does anyone have an idea what´s wrong?
Thanks in advance
HelmutAre you using Windows platform?
If you are using windows platform you can use Visual Administrator for viewing your logs.
regards,
Sujesh -
Upgrade from SP14 to SP24 for EP 7.0
Hi All,
We need to upgrade EP 7.0 SP 14 to SP 24 and back-end database from Oracle to MaxDB. Could you please let me know what are the steps I need to follow while upgrading.
I want to move the KM content once migration is done, could you please tell me the list of issues that one should take care at the time of migrating, transporting the content, and from upgrading Oracle database to MaxDB?.
Regards
SureshHi,
For patching the EP system from 14 to 24, you need to download the Support Paackages using SolMan - MOPZ feature. Once this is done, using JSPM tool, the system can be patched. Details can be got at http://service.sap.com/instguides -> SAP Netweaver-> SAP Netweaver 2004s -> Maintainence -> SP guides
Rgds,
Soujanya -
MAXDB issue when upgrading from SP14 to SP15
Hello,
I am trying to upgrade my local WAS to SP15. I am getting the following DB error during the installation (excerpt from callSdmViaSapinst.log file):
Feb 15, 2006 10:32:01... Info: Creating connections to database "J2E".
Feb 15, 2006 10:32:01... Info: Creating vendor connection to database.
Feb 15, 2006 10:32:01... Info: Vendor connection created successfully.
Feb 15, 2006 10:32:01... Info: Creating openSQL connection to database.
Feb 15, 2006 10:32:03... Info: OpenSQL connection created successfully.
Feb 15, 2006 10:32:05... Info: <!LOGHEADER[START]/>
Feb 15, 2006 10:32:05... Info: <!HELP[Manual modification of the header may cause parsing problem!]/>
Feb 15, 2006 10:32:05... Info: <!LOGGINGVERSION[1.5.3.7186 - 630]/>
Feb 15, 2006 10:32:05... Info: <!NAME[C:\usr\sap\J2E\JC00\SDM\program\log\jddilog20060215103203.log]/>
Feb 15, 2006 10:32:05... Info: <!PATTERN[jddilog20060215103203.log]/>
Feb 15, 2006 10:32:05... Info: <!FORMATTER[com.sap.dictionary.database.dbs.DbTraceFormatter(%s %m %-30l %24d)]/>
Feb 15, 2006 10:32:05... Info: <!ENCODING[Cp1252]/>
Feb 15, 2006 10:32:05... Info: <!LOGHEADER[END]/>
Feb 15, 2006 10:32:05... Info:
Feb 15, 2006 10:32:05... Info: E R R O R ******* (DbObjectSqlStatements)
Feb 15, 2006 10:32:05... Info: 10:32:04 2006-02-15 dbs-Error: Exception caught during SQL execution [-6000] (at 15): Duplicate table name:BC_CMSRTS CREATE TABLE "BC_CMSRTS"("VENDOR" VARCHAR(256) UNICODE DEFAULT ' ' , "NAME" VARCHAR(256) UNICODE DEFAULT ' ' , "PROVIDER" VARCHAR(40) UNICODE DEFAULT ' ' , "CMSNAME" VARCHAR(10) UNICODE DEFAULT ' ' , "CMSURL" VARCHAR(256) UNICODE DEFAULT ' ' , "TRACKNAME" VARCHAR(8) UNICODE DEFAULT ' ' , "SYSTYPE" VARCHAR(10) UNICODE DEFAULT ' ' , "LOCATION" VARCHAR(40) UNICODE DEFAULT ' ' , "CONFIGTYPE" VARCHAR(5) UNICODE DEFAULT ' ' , "RELEASE" VARCHAR(10) UNICODE DEFAULT ' ' , "SERVICELEVEL" VARCHAR(10) UNICODE DEFAULT ' ' , "PATCHLEVEL" VARCHAR(10) UNICODE DEFAULT ' ' , "APPLYTIME" VARCHAR(20) UNICODE DEFAULT ' ' )
Feb 15, 2006 10:32:05... Info:
Feb 15, 2006 10:32:05... Info: E R R O R ******* (DbModificationManager)
Feb 15, 2006 10:32:05... Info: 10:32:04 2006-02-15 dbs-Error: Statements could not be executed successfully
Feb 15, 2006 10:32:05... Error: Aborted: development component 'tc/SL/UTIL_JDD'/'sap.com'/'SAP AG'/'6.4015.00.0000.20051027101403.0000':
No further description found.
Feb 15, 2006 10:32:05... Info: -
Deployment was successful -
Feb 15, 2006 10:32:05... Info: Summarizing the deployment results:
Feb 15, 2006 10:32:05... Error: Admitted: C:\Documents and Settings\DKEISERlocal\My Documents\Portal\installs\WAS15\J2EE-RUNT-CD\J2EE-ENG\OFFLINE\SAPJEECOR15_0.SCA
Feb 15, 2006 10:32:05... Error: Admitted: C:\Documents and Settings\DKEISERlocal\My Documents\Portal\installs\WAS15\J2EE-RUNT-CD\J2EE-ENG\OFFLINE\JRFC.SDA
Feb 15, 2006 10:32:06... Error: Processing error. Return code: 4
Have tried everything I know of (restarting, etc.). Also tried to drop the duplicate table and it won't let me. Anyone have any ideas??
Thanks in advance...Hi,
you could try (re)loading the MaxDB system tables. You can do that using either the Database Manager GUI, or from the commandline:
dbmcli -d <SID> -u <dbm-user>,<pwd> load_systab -u <dba-user>,<pwd> -ud DOMAIN
The standard dbm-user is called 'control', the standard dba-user 'superdba'.
Kind regards,
Roland -
Upgrade from PI 7.0 SP18 to PI 7.1 EHP1
Hi all,
I'm performing an Upgrade from Netweaver PI 7.0 SP18 to PI 7.1 EHP1.
I've checked all the notes ragarding any known issuses about the process BUT....
Here's the problem: in Phase TR_CMDIMPORT_PREPARE ( during the Support Package Import ) the upgrade stops with this error:
ERROR: 339 errors detected during TR_CMDIMPORT_PREPARE.
Errors are accumulated in file PCMDIMP.ELG.
PCMDIMP.ELG shows problems related to R3trans version, but, as you can see, my version is newer:
"2EETW000 import of new package definition (note 1089083 needs at least R3trans version 6.18, this is 6.19."
What could possibly be wrong?
Notice that in my download directory I've put:
the latest Upgrade Correction ( NW711_19-10007578.SAR ).
the latest Kernel ( 711 46 )
the latest EHP1 Support Package ( 03 )
the latest SAPup: 7.10/5 29.003 ( as suggested by note 1156185. I know it's 7.10, not 7.11 but the note it's clear on that. Anyway i tried, unsuccessfully, without the SUPup, so.... )
I use the following media:
NW PI 7.1 EHP1 Upgrade Master 51036470
NW 7.11 IM/Kernel/TREX WIN x64, IA64 51036476
NW AS ABAP 7.1 EHP1 Language 51036707
I even tried to use the original Kernel from the DVD...
Any suggestion?
Thanks and Regards,
Andrea
P.S. Partial PCMDIMP.ELG file :
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CMDFILE IMPORT ERRORS and RETURN CODE in SAPL-71101INPIBASIS.JIM
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CMDFILE IMPORT ERRORS and RETURN CODE in SAPL-71102INPIBASIS.JIM
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CMDFILE IMPORT ERRORS and RETURN CODE in SAPL-71103INPIBASIS.JIM
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EETW000 import of new package definition (note 1089083 needs at least R3trans version 6.18, this is 6.19.
2EETW000 import of new package definition (note 1089083 needs at least R3trans version 6.18, this is 6.19.
2EETW000 import of new package definition (note 1089083 needs at least R3trans version 6.18, this is 6.19.
2EETW000 import of new package definition (note 1089083 needs at least R3trans version 6.18, this is 6.19.
1 ETP111 exit code : "8"
Edited by: Andrea Campo on Sep 23, 2009 2:37 PM
Edited by: Andrea Campo on Sep 23, 2009 2:38 PMThis is part of SAPL-71103INPIBASIS.JIM:-------
4 EPU201XBEGIN OF SECTION BEING ANALYZED
1 ETP199X######################################
1 ETP179 CREATE COFILE FROM DATAFILE
1 ETP101 transport order : "SAPK-71103INPIBASIS"
1 ETP102 system : "JIM"
1 ETP108 tp path : "E:\usr\sap\JIM\upg\abap\exe\tp.EXE"
1 ETP109 version and release : "375.32.47" "711"
1 ETP198
4 ETW000 E:\usr\sap\JIM\upg\abap\exe\R3trans.exe version 6.19 (release 711 -
22.01.09 - 11:27:00).
4 ETW000 unicode enabled version
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time : 23.09.2009 - 12:47:46
4 ETW000 control file: E:\usr\sap\JIM\upg\abap\tmp\SAPKK-71103INPIBASIS.JIM
4 ETW000 > #pid 4904 on srvsvi-w037v (APServiceJIM)
4 ETW000 > createcofile
4 ETW000 > file='E:\usr\sap\JIM\upg\abap\data\R-71103INPIBASIS.SAP'
4 ETW000 >
4 ETW000 R3trans was called as follows: E:\usr\sap\JIM\upg\abap\exe\R3trans.exe -w
E:\usr\sap\JIM\upg\abap\tmp\SAPL-71103INPIBASIS.JIM
E:\usr\sap\JIM\upg\abap\tmp\SAPKK-71103INPIBASIS.JIM
4 ETW000 trace at level 1 opened for a given file pointer
4 ETW000
4 ETW000 ================== STEP 1 =====================
4 ETW000 date&time : 23.09.2009 - 12:47:46
4 ETW000 function : CREATECOFILE
4 ETW000 data file : E:\usr\sap\JIM\upg\abap\data\R-71103INPIBASIS.SAP
4 ETW000 buffersync : NO
4 ETW000 clients : default
4 ETW000 commit : -1
4 ETW000 table cache : dynamic
4 ETW000
4 ETW000 Character set on this machine : 2 byte unicode little endian.
4 ETW000 Character set on the data file: 2 byte unicode big endian.
4 ETW000 Data file is compressed with algorithm 'L'.
4 ETW000 Export was executed on 01.07.2009 at 14:30:19 by k7dadm
3 ETW709 "711 "
4 ETW000 with R3trans version: 22.01.09 - 11:27:00
4 ETW000 Source System = Solaris on SPARCV9 CPU on DBMS = DB6 --- DB2DBDFT = 'K7D'
--- SYSTEM = 'K7D'.
4 ETW000
4 ETW000 language vector during export: 1234568ABCDEFGHIJKLMNOPQRSTUVWcd
4 ETW000 language vector during export: 1234568ABCDEFGHIJKLMNOPQRSTUVWcd (ISO-
ZHTHKOROSLHRUKARHECSDEENFRELHUITJADAPLZFNLNOPTSKRUESTRFISVBGCASH)
4 ETW000 lsm during export: ALL
4 ETW000 datafile was created with 'langdeletions=no'.
4 ETW000 trfunction = D (patch transport)
3 ETW692 "SAPK-71103INPIBASIS "
3 ETW708 "000"
3 ETW695 "D"
3 ETW694 "SAP "
3 ETW693 "SAP "
3 ETW696 "20090609"
3 ETW713 "PI_BASIS Support Package 03 for 7.11 "
3 ETW691 "CORRMERGMERGEINFO PI_BASIS K7D 20090609 133924
3 ETW707 "CORRMERGMERGEINFO PI_BASIS K7D 20090609 133924
3 ETW691 "LIMUCLSD/SCMB/CA_DF_ATTR_QTY
3 ETW707 "R3TRCLAS/SCMB/CA_DF_ATTR_QTY"
4 ETW000 809204 bytes read.
4 ETW000 Transport overhead 17.1 %.
4 ETW000 Data compressed to 7.0 %.
4 ETW000 Duration: 0 sec (809204 bytes/sec).
3 ETW710 "0" "0"
4 ETW000 End of Transport (0000).
4 ETW000 date&time: 23.09.2009 - 12:47:46
1 ETP179 CREATE COFILE FROM DATAFILE
1 ETP110 end date and time : "20090923124746"
1 ETP111 exit code : "0"
1 ETP199 ######################################
1 ETP199X######################################
1 ETP176 IMPORT OF COMMANDFILE ONLY
1 ETP101 transport order : "SAPK-71103INPIBASIS"
1 ETP102 system : "JIM"
1 ETP108 tp path : "E:\usr\sap\JIM\upg\abap\exe\tp.exe"
1 ETP109 version and release : "375.32.47" "711"
1 ETP198
4 ETW000 E:\usr\sap\JIM\upg\abap\exe\R3trans.exe version 6.19 (release 711 -
22.01.09 - 11:27:00).
4 ETW000 unicode enabled version
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time : 23.09.2009 - 12:49:20
4 ETW000 control file: E:\usr\sap\JIM\upg\abap\tmp\SAPKK-71103INPIBASIS.JIM
4 ETW000 > #pid 7740 on srvsvi-w037v (jimadm)
4 ETW000 > import
4 ETW000 > buffersync=no
4 ETW000 > file='E:\usr\sap\JIM\upg\abap\data\R-71103INPIBASIS.SAP'
4 ETW000 > continuation='E:\usr\sap\JIM\upg\abap\data\R-71103INPIBASIS_#.SAP'
4 ETW000 > client cascade yes
4 ETW000 > repeatimport=yes
4 ETW000 > importtruncated = yes
4 ETW000 > including 'NOTHING'
4 ETW000 R3trans was called as follows: E:\usr\sap\JIM\upg\abap\exe\R3trans.exe -u
26 -w E:\usr\sap\JIM\upg\abap\tmp\SAPL-71103INPIBASIS.JIM
E:\usr\sap\JIM\upg\abap\tmp\SAPKK-71103INPIBASIS.JIM
4 ETW000 active unconditional modes: 26
4 ETW000 Connected to DBMS = MSSQL --- SERVER = 'SRVSVI-W037V' DBNAME = 'JIM' ---
SYSTEM = 'JIM'.
4 ETW690 COMMIT "0" "0"
4 ETW000 trace at level 1 opened for a given file pointer
4 ETW000
4 ETW000 ================== STEP 1 =====================
4 ETW000 date&time : 23.09.2009 - 12:49:20
4 ETW000 function : IMPORT
4 ETW000 data file : E:\usr\sap\JIM\upg\abap\data\R-71103INPIBASIS.SAP
4 ETW000 Continuation : E:\usr\sap\JIM\upg\abap\data\R-71103INPIBASIS_#.SAP
4 ETW000 buffersync : NO
4 ETW000 clients : cascade
4 ETW000 repeatimport : YES (corresponds to unconditional mode 1)
4 ETW000 repeatclimport : NO
4 ETW000 c.s.i. : NO
4 ETW000 importtruncated : YES (imported data may be destroyed!)
4 ETW000 charsetadapt : YES
4 ETW000 def. charset : WEUROPEAN
4 ETW000 commit : 100000
4 ETW000 table cache : dynamic
4 ETW000 INCLUDING : 'NOTHING'
4 ETW000
4 ETW000 rejected clients : 066
4 ETW000
4 ETW000 client cascade to: 000, 001
4 ETW000 Character set on this machine : 2 byte unicode little endian.
4 ETW000 Character set on the data file: 2 byte unicode big endian.
4 ETW000 Data file is compressed with algorithm 'L'.
4 ETW000 Export was executed on 01.07.2009 at 14:30:19 by k7dadm
3 ETW709 "711 "
4 ETW000 with R3trans version: 22.01.09 - 11:27:00
4 ETW000 Source System = Solaris on SPARCV9 CPU on DBMS = DB6 --- DB2DBDFT = 'K7D'
--- SYSTEM = 'K7D'.
4 ETW000
4 ETW000 language vector during export: 1234568ABCDEFGHIJKLMNOPQRSTUVWcd
4 ETW000 language vector during export: 1234568ABCDEFGHIJKLMNOPQRSTUVWcd (ISO-
ZHTHKOROSLHRUKARHECSDEENFRELHUITJADAPLZFNLNOPTSKRUESTRFISVBGCASH)
4 ETW000 lsm during export: ALL
4 ETW000 datafile was created with 'langdeletions=no'.
4 ETW000 trfunction = D (patch transport)
4 ETW000 switching to selective language import
4 ETW000 the following languages will be imported: DEI
4 ETW000 Used Commandfile SAPK-71103INPIBASIS (SAPUSER/140)
4 ETW000 This is a patch transport.
4 ETW000 1 entry for E070 updated (SAPK-71103INPIBASIS).
4 ETW000 140 entries for E071 inserted (SAPK-71103INPIBASIS *).
4 ETW000 1 entry for E071K inserted (SAPK-71103INPIBASIS *).
4 ETW000 1 entry for E071KF inserted (SAPK-71103INPIBASIS *).
4 ETW000 1 entry for E070C inserted (SAPK-71103INPIBASIS).
4 ETW000 1 entry for E07T updated (SAPK-71103INPIBASIS *).
4 ETW690 COMMIT "103098" "103098"
3WETW000 different nametabs for table ENHOBJ (field ENHOBJTYPE).
3WETW000 key field truncated
3WETW000 Key field is not in NTAB.
4 ETW000 table ENHOBJ: entry in DB is 2 bytes smaller than in file.
4 ETW000 ... ignoring such differences.
3WETW000 different nametabs for table TRDIR (field TROBJECT_TYPE).
4 ETW000 Field is not in NTAB.
3WETW000 different nametabs for table TRDIR (field TROBJECT_NAME).
3WETW000 different nametabs for table SPROXREG (field IFR_IDEMPOTENT).
[u2026]
4 ETW000 Field is not in NTAB.
4 ETW000 table SPROXREG: entry in DB is 2 bytes smaller than in file.
4 ETW000 ... ignoring such differences.
3 ETW677 "R3TRCLAS/SCMB/CL_DF_ARCH_ADD_TABLE" not imported in this step.
2EETW000 import of new package definition (note 1089083 needs at least R3trans
version 6.18, this is 6.19.
[u2026]
4 ETW000 no entries for PAK_RUNTIME_ENV will be imported in this step.
3 ETW677 "R3TRDEVC/SCMB/FLOW" not imported in this step.
2EETW000 import of new package definition (note 1089083 needs at least R3trans
version 6.18, this is 6.19.
3 ETW677 "R3TRDEVC/SCMB/FLOW_NET" not imported in this step.
3 ETW677 "R3TRDSYSSIMGASC0TSAI" not imported in this step.
3WETW000 different nametabs for table ENHLOG (field ENHTOOLTYPE).
4 ETW000 Field is not in NTAB.
4 ETW000 table ENHLOG: entry in DB is 20 bytes smaller than in file.
4 ETW000 ... ignoring such differences.
3 ETW677 "R3TRENHO/SCMB/ARC_DOCFLOW_ADD_TABLE" not imported in this step.
3 ETW677 "R3TRFUGR/SCMB/DF_ARCHIVE" not imported in this step.
3 ETW677 "R3TRFUGRRSC2" not imported in this step.
2EETW000 import of new package definition (note 1089083 needs at least R3trans
version 6.18, this is 6.19.
4 ETW109 table "PAK_INTF_CONTENT" does not exist in nametab.
4 ETW000 no entries for PAK_INTF_CONTENT will be imported in this step.
3 ETW677 "R3TRPINF/SCMB/FLOW_API_DOCUMENT" not imported in this step.
2EETW000 import of new package definition (note 1089083 needs at least R3trans
version 6.18, this is 6.19.
3 ETW677 "R3TRPINF/SCMB/FLOW_API_NET" not imported in this step.
4 ETW000 SAPK-71103INPIBASIS touched.
4 ETW690 COMMIT "128" "103226"
4 ETW000 809204 bytes read.
4 ETW000 Transport overhead 17.1 %.
4 ETW000 Data compressed to 7.0 %.
4 ETW000 Duration: 0 sec (809204 bytes/sec).
3 ETW710 "0" "0"
4 ETW000
4 ETW000 Summary:
4 ETW000
4 ETW000 1 COMML imported.
4 ETW000 1 COMMT imported.
4 ETW000 Totally 2 Objects imported.
4 ETW000
4 ETW000 103226 bytes modified in database.
4 ETW000 [dev trc ,00000] Disconnecting from ALL connections:
264239 0.264239
4 ETW000 [dev trc ,00000] Disconnected from connection 0
4041 0.268280
4 ETW000 [dev trc ,00000] statistics db_con_commit (com_total=3, com_tx=3)
4 ETW000
31 0.268311
4 ETW000 [dev trc ,00000] statistics db_con_rollback (roll_total=0,
roll_tx=0)
4 ETW000
23 0.268334
4 ETW000 Disconnected from database.
4 ETW000 End of Transport (0008).
4 ETW000 date&time: 23.09.2009 - 12:49:20
4 ETW000 34 warnings occured.
4 ETW000 4 errors occured.
1 ETP176 IMPORT OF COMMANDFILE ONLY
1 ETP110 end date and time : "20090923124920"
1 ETP111 exit code : "8"
1 ETP199 ######################################
1 ETP199X######################################
1 ETP176 IMPORT OF COMMANDFILE ONLY
1 ETP101 transport order : "SAPK-71103INPIBASIS"
1 ETP102 system : "JIM"
1 ETP108 tp path : "E:\usr\sap\JIM\upg\abap\exe\tp.exe"
1 ETP109 version and release : "375.32.47" "711"
1 ETP198
4 ETW000 E:\usr\sap\JIM\upg\abap\exe\R3trans.exe version 6.19 (release 711 -
22.01.09 - 11:27:00).
4 ETW000 unicode enabled version
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time : 23.09.2009 - 13:57:11
4 ETW000 control file: E:\usr\sap\JIM\upg\abap\tmp\SAPKK-71103INPIBASIS.JIM
4 ETW000 > #pid 5540 on srvsvi-w037v (jimadm)
4 ETW000 > import
4 ETW000 > buffersync=no
4 ETW000 > file='E:\usr\sap\JIM\upg\abap\data\R-71103INPIBASIS.SAP'
4 ETW000 > continuation='E:\usr\sap\JIM\upg\abap\data\R-71103INPIBASIS_#.SAP'
4 ETW000 > client cascade yes
4 ETW000 > repeatimport=yes
4 ETW000 > importtruncated = yes
4 ETW000 > including 'NOTHING'
4 ETW000 R3trans was called as follows: E:\usr\sap\JIM\upg\abap\exe\R3trans.exe -u
26 -w E:\usr\sap\JIM\upg\abap\tmp\SAPL-71103INPIBASIS.JIM
E:\usr\sap\JIM\upg\abap\tmp\SAPKK-71103INPIBASIS.JIM
4 ETW000 active unconditional modes: 26
4 ETW000 Connected to DBMS = MSSQL --- SERVER = 'SRVSVI-W037V' DBNAME = 'JIM' ---
SYSTEM = 'JIM'.
4 ETW690 COMMIT "0" "0"
4 ETW000 trace at level 1 opened for a given file pointer
4 ETW000
4 ETW000 ================== STEP 1 =====================
4 ETW000 date&time : 23.09.2009 - 13:57:11
4 ETW000 function : IMPORT
4 ETW000 data file : E:\usr\sap\JIM\upg\abap\data\R-71103INPIBASIS.SAP
4 ETW000 Continuation : E:\usr\sap\JIM\upg\abap\data\R-71103INPIBASIS_#.SAP
4 ETW000 buffersync : NO
4 ETW000 clients : cascade
4 ETW000 repeatimport : YES (corresponds to unconditional mode 1)
4 ETW000 repeatclimport : NO
4 ETW000 c.s.i. : NO
4 ETW000 importtruncated : YES (imported data may be destroyed!)
4 ETW000 charsetadapt : YES
4 ETW000 def. charset : WEUROPEAN
4 ETW000 commit : 100000
4 ETW000 table cache : dynamic
4 ETW000 INCLUDING : 'NOTHING'
4 ETW000
4 ETW000 rejected clients : 066
4 ETW000
4 ETW000 client cascade to: 000, 001
4 ETW000 Character set on this machine : 2 byte unicode little endian.
4 ETW000 Character set on the data file: 2 byte unicode big endian.
4 ETW000 Data file is compressed with algorithm 'L'.
4 ETW000 Export was executed on 01.07.2009 at 14:30:19 by k7dadm
3 ETW709 "711 "
4 ETW000 with R3trans version: 22.01.09 - 11:27:00
4 ETW000 Source System = Solaris on SPARCV9 CPU on DBMS = DB6 --- DB2DBDFT = 'K7D'
--- SYSTEM = 'K7D'.
4 ETW000
4 ETW000 language vector during export: 1234568ABCDEFGHIJKLMNOPQRSTUVWcd
4 ETW000 language vector during export: 1234568ABCDEFGHIJKLMNOPQRSTUVWcd (ISO-
ZHTHKOROSLHRUKARHECSDEENFRELHUITJADAPLZFNLNOPTSKRUESTRFISVBGCASH)
4 ETW000 lsm during export: ALL
4 ETW000 datafile was created with 'langdeletions=no'.
4 ETW000 trfunction = D (patch transport)
[u2026]
roll_tx=0)
4 ETW000
23 0.228932
4 ETW000 Disconnected from database.
4 ETW000 End of Transport (0008).
4 ETW000 date&time: 23.09.2009 - 13:57:11
4 ETW000 34 warnings occured.
4 ETW000 4 errors occured.
1 ETP176 IMPORT OF COMMANDFILE ONLY
1 ETP110 end date and time : "20090923135712"
1 ETP111 exit code : "8"
1 ETP199 ######################################
4 EPU202XEND OF SECTION BEING ANALYZED -
Hi All,
I'm currently trying to upgrade from SP11 to SP14. I started with upgrading the J2EE Engine.
Whe doing so the Installation stops at step 17 with the
following error message in log-file callSdmViaSapinst.log:
ERROR: Not deployed. Deploy Service returned ERROR:
java.rmi.RemoteException: Cannot deploy application sap.com/tc~uddi..
Reason: Application alias [uddi] for application [sap.com/tc~uddi] already exists in the HTTP Provider Service. The application that holds this alias is [sap.com/com.sap.uddi].
Has anybody encountered a similar problem and can help me?
Thanks,
StephanHi Vasu,
here is the complete StackTrace as found in callSdmViaSapinst.log. I hope this is what you meant by installation path. BTW, restarting the installation didn't help.
Regards,
Stephan
05/12/12 14:24:31 - ***********************************************************
05/12/12 14:24:36 - Start updating EAR file...
05/12/12 14:24:36 - start-up mode is lazy
05/12/12 14:24:39 - EAR file updated successfully for 2766ms.
05/12/12 14:24:39 - Start deploying ...
05/12/12 14:24:42 - EAR file uploaded to server for 2547ms.
05/12/12 14:24:56 - ERROR: Not deployed. Deploy Service returned ERROR:
java.rmi.RemoteException: Cannot deploy application sap.com/tc~uddi..
Reason: Application alias [uddi] for application [sap.com/tc~uddi] already exists in the HTTP Provider Service. The application that holds this alias is [sap.com/com.sap.uddi].; nested exception is:
com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Application alias [uddi] for application [sap.com/tc~uddi] already exists in the HTTP Provider Service. The application that holds this alias is [sap.com/com.sap.uddi].
at com.sap.engine.services.servlets_jsp.server.container.DeployAction.deploy(DeployAction.java:144)
at com.sap.engine.services.servlets_jsp.server.container.WebContainer.deploy(WebContainer.java:104)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:387)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:290)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3027)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:467)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:294)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
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:95)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Application alias [uddi] for application [sap.com/tc~uddi] already exists in the HTTP Provider Service. The application that holds this alias is [sap.com/com.sap.uddi].
at com.sap.engine.services.servlets_jsp.server.container.DeployAction.deploy(DeployAction.java:144)
at com.sap.engine.services.servlets_jsp.server.container.WebContainer.deploy(WebContainer.java:104)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:387)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:290)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3027)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:467)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:294)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
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:95)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:482)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:294)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
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:95)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
Caused by: com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Application alias [uddi] for application [sap.com/tc~uddi] already exists in the HTTP Provider Service. The application that holds this alias is [sap.com/com.sap.uddi].
at com.sap.engine.services.servlets_jsp.server.container.DeployAction.deploy(DeployAction.java:144)
at com.sap.engine.services.servlets_jsp.server.container.WebContainer.deploy(WebContainer.java:104)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:387)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:290)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3027)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:467)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:294)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
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:95)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Application alias [uddi] for application [sap.com/tc~uddi] already exists in the HTTP Provider Service. The application that holds this alias is [sap.com/com.sap.uddi].
at com.sap.engine.services.servlets_jsp.server.container.DeployAction.deploy(DeployAction.java:144)
at com.sap.engine.services.servlets_jsp.server.container.WebContainer.deploy(WebContainer.java:104)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:387)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:290)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3027)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:467)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:294)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
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:95)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
at com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException.writeReplace(WebDeploymentException.java:99)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:896)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1011)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at com.sap.engine.services.rmi_p4.DispatchImpl.throwException(DispatchImpl.java:135)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:296)
... 8 more
For detailed information see the log file of the Deploy Service.
05/12/12 14:24:56 - ***********************************************************
Dec 12, 2005 2:24:56 PM Info: End of log messages of the target system.
Dec 12, 2005 2:24:56 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Dec 12, 2005 2:24:56 PM Error: Aborted: development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.4014.00.0000.20050606164207.0000':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/tc~uddi..
Reason: Application alias [uddi] for application [sap.com/tc~uddi] already exists in the HTTP Provider Service. The application that holds this alias is [sap.com/com.sap.uddi].; nested exception is:
com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Application alias [uddi] for application [sap.com/tc~uddi] already exists in the HTTP Provider Service. The application that holds this alias is [sap.com/com.sap.uddi].
at com.sap.engine.services.servlets_jsp.server.container.DeployAction.deploy(DeployAction.java:144)
at com.sap.engine.services.servlets_jsp.server.container.WebContainer.deploy(WebContainer.java:104)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:387)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:290)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3027)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:467)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:294)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
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:95)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Application alias [uddi] for application [sap.com/tc~uddi] already exists in the HTTP Provider Service. The application that holds this alias is [sap.com/com.sap.uddi].
at com.sap.engine.services.servlets_jsp.server.container.DeployAction.deploy(DeployAction.java:144)
at com.sap.engine.services.servlets_jsp.server.container.WebContainer.deploy(WebContainer.java:104)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:387)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:290)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3027)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:467)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:294)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
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:95)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Dec 12, 2005 2:24:57 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Dec 12, 2005 2:24:57 PM Info: --------------- Deployment was successful -----------------
Dec 12, 2005 2:24:57 PM Info: Summarizing the deployment results:
Dec 12, 2005 2:24:57 PM Error: Admitted: D:TempSAP_SP14J2EE-RUNT-CDJ2EE-ENGONLINESAPJTECHS14_0.SCA
Dec 12, 2005 2:24:57 PM Error: Processing error. Return code: 4 -
Dear Experts,
Since I have ERP 2005 SR2 installed the EP7 has SP09 and I am finding some problem with the installation of DI and other issues. So like to upgrade to SP14. I have downloaded the Support Pack stack from market place and was comparing the components required to go ahead. I found few of the components which I downloaded and what I have from the system information. Few are mentioned below.
JSPM 7.00 SP12 (1000.7.00.12.0.20070507080400)
CORE-TOOLS 7.00 SP9 (1000.7.00.9.0.20060827014400)
BASETABLES 7.00 SP9 (1000.7.00.9.0.20060827014300)
JLOGVIEW 7.00 SP9 (1000.7.00.9.0.20060827014700)
SAP-JEE 7.00 SP9 (1000.7.00.9.0.20060827014500)
SAP-JEECOR 7.00 SP9 (1000.7.00.9.1.20060913120000)
ADSSAP 7.00 SP9 (1000.7.00.9.0.20060827015200)
CAF 7.00 SP9 (1000.7.00.9.0.20060825071023)
BI_MMR 7.00 SP9 (1000.7.00.9.0.20060826182000)
UMEADMIN 7.00 SP9 (1000.7.00.9.0.20060811133141)
SAP_JTECHS 7.00 SP9 (1000.7.00.9.0.20060827014700)
CAF-UM 7.00 SP9 (1000.7.00.9.0.20060811133139)
KM-KW_JIKS 7.00 SP9 (1000.7.00.9.0.20060827014900)
LM-TOOLS 7.00 SP9 (1000.7.00.9.3.20061016113408)
BI_UDI 7.00 SP9 (1000.7.00.9.0.20060826185800)
EP-WDC 7.00 SP9 (1000.7.00.9.0.20060827063700)
EPBC2 7.00 SP9 (1000.7.00.9.0.20060827034600)
EPBC 7.00 SP9 (1000.7.00.9.2.20061026162900)
EP-PSERV 7.00 SP9 (1000.7.00.9.0.20060827063800)
WDEXTENSIONS 7.00 SP9 (1000.7.00.9.0.20060811133134)
SAPPCUI_GP 600 SP13 (1000.600.0.13.0.20080516101947)
IS-HER-CSS 600 SP6 (1000.600.0.6.0.20060831151934)
SAP-EU 7.00 SP9 (1000.7.00.9.0.20060811133132)
CAF-KM 7.00 SP9 (1000.7.00.9.0.20060811133145)
NET-PDK 7.00 SP9 (1000.7.00.9.0.20060827063700)
RTC 7.00 SP9 (1000.7.00.9.0.20060827105400)
KMC-BC 7.00 SP9 (1000.7.00.9.0.20060827081000)
KMC-CM 7.00 SP9 (1000.7.00.9.0.20060827100100)
KMC-COLL 7.00 SP9 (1000.7.00.9.1.20061017073300)
LM-PORTAL 7.00 SP9 (1000.7.00.9.0.20060807071043)
RTC-STREAM 7.00 SP9 (1000.7.00.9.0.20060827105400)
UWLJWF 7.00 SP9 (1000.7.00.9.0.20060827090500)
SAP_ESS 600 SP10 (1000.600.0.10.10.20071130064320)
SAP_ASR 600 SP6 (1000.600.0.6.0.20060920091843)
SAP_PSS 600 SP6 (1000.600.0.6.0.20060901025040)
SAP_MSS 600 SP6 (1000.600.0.6.0.20060831153355)
Have not mentioned about the BP above, which I will update all till SP10 once I have done with SP14 of portal. And the same with ESS/PSS/ASR/MSS I will upgrade till SP10( same as BP)
Apart from the above list, the underlined are not yet downloaded and want to know from you experts, that is it okay with all those mentioned above to go ahead with Portal SP14 or some components still needed?
Also I will take JSPM to SP14( now at SP12).
Important: Do I have to update my ABAP patch before I start with Portal? At present have the followin levels
SAP_BASIS SP10
SAP_ABA SP10
PI_BASIS SP10
SAP_BW SP09
SP_HR SP15
EA_HR SP15 and all others default.
Any link/doc will be highly appreciated.
I have gone through some of blog/threads and every where it is maintained that a backup. So backup of DB or whole system backup?
Regards
PrashJust forgot to mention that also the following 3 components are not yet downloaded.
VCBASE 7.00 SP9 (1000.7.00.9.0.20060828094000)
VCKITGP 7.00 SP9 (1000.7.00.9.0.20060828094000)
VCKITXX 7.00 SP9 (1000.7.00.9.0.20060828094000)
And regaring the BP do I need to download 1.0 SP10 or SP06 will do and only for BP_ERP5ESS and MSS will take it till SP10( same as SAP_ESS/MSS)
BP_ERP5*** 1.0 SP6 (1000.1.0.6.0.20060831150911)
BP_ERP5BUA 1.0 SP6 (1000.1.0.6.0.20060831150930)
BP_ERP5BUY 1.0 SP2 (1000.1.0.2.0.20051129013440)
BP_ERP5COM 1.0 SP2 (1000.1.0.2.0.20051129015614)
BP_ERP5DCO 1.0 SP2 (1000.1.0.2.0.20051129022003)
BP_ERP5HRA 1.0 SP6 (1000.1.0.6.0.20060831151041)
BP_ERP5INV 1.0 SP2 (1000.1.0.2.0.20051129035224)
BP_ERP5MSS 1.0 SP6 (1000.1.0.6.0.20060901115659)
BP_ERP5MTC 1.0 SP2 (1000.1.0.2.0.20051129043511)
BP_ERP5PLA 1.0 SP2 (1000.1.0.2.0.20051129014121)
BP_ERP5PRS 1.0 SP4 (1000.1.0.4.0.20060331022103)
BP_ERP5PSS 1.0 SP6 (1000.1.0.6.0.20060831151737)
BP_ERP5QIN 1.0 SP2 (1000.1.0.2.0.20051129021503)
BP_ERP5SAL 1.0 SP2 (1000.1.0.2.0.20051129012342)
BP_ERP5SUP 1.0 SP3 (1000.1.0.3.1.20060424231627)
SAPPCUI_GP 600 SP13 (1000.600.0.13.0.20080516101947) -
Portal Upgrade from EP6.0sp10 to EP6.0sp18
Hi All,
I am totally new to portal upgrade.we have current version of portal as follows:
portal version is: 6.0.10.2.0
KMC version is : 6.0.10.1.0 (NW04 SPS10 Patch 1)
Trex Version : 6.1.10.01
1. I am little confuse about whats the difference between Upgrading from EP6.0sp10 to "<b>EP6.0sp18/ NW04sp18</b>".Is the process for doing above is same or different.
2. I heard from SAP that TREX must be upgraded first before KMC and Portal.Is it true? whats is reason for that
?what should be latest SP and patch for TREX?any documents?
3. Is there any specific sequence to upgrade like TREX->WAS>portal>KMC?
4. What about customisations objects,will that be seriously affected after upgrade?How to prevent that?
can anybody give the Basic knowledge of upgrade and process flow.
Thanks in Advance.Help will be greatly appreciated.
AmitHi Amit,
EP6 SP18 ist the actual Service Pack for Enterprise Portal. NW04 SPS(!) 18 is the complete Service Pack Stack for the NetWeaver platform. So if you want SP18 for your portal installation, you should get the whole NetWeaver platform in use for that to SPS18 (as you wrote, for EP this is normally WAS, EP, KM, TREX, eventually NWDS).
TREX normally has the same counting as the rest, but in fact at the moment there is no SP18 for TREX, but it is renumbered again. The actual version reads TREX 6.1 Patch 26.
Sequence is WAS -> portal -> KMC -> TREX. Anyhow, you should not await a stable version if using mixed SPs, especially if mixing 10 with 18 So get all in line and then restart working with your installation.
As you normally shouldn't have customized standard objects but copied them into your own namespace and worked on these, there shouldn't be a problem. If you haven't gone this way, with such an update you will learn how urgent it is to keep this in mind --- never change standard objects...
Hope it helps
Detlev -
What is the impact of R/3 upgradation from 4.7 to ECC 6 on BI
Dear all,
Can any one tell me what will be the impact of R/3 Upgradation on BI... as we are shortly going to upgrade our R/3 from 4.7 to ECC 6.
Do we need to take any precautions in R/3 and aswell as BI
Please give the information...points will be given
Regards
venuHi
Please Refer this as this vll give u the Pros and Cons for upgrade.
Refer
http://wiki.ittoolbox.com/index.php/Upgrade_BW_to_Netweaver_2004s_from_v3.0B
This Wiki contains Rob Moore's ( BW Manager, Edwards Limited) teams experiences in upgrading Business Warehouse System from 3.0B to BW 7.0.
Contents
1 Upgrading from BW 3.0B to BW 7.0 (Netweaver 2004s)
2 Introduction
3 Overview & Scope
4 Drivers
5 Environment
6 Resource & Timescales
7 High Level Plan
8 Summary Task List
8.1 #Support Pack Hike
8.2 #Plug-in installation
8.3 #PREPARE process
8.4 #Dbase upgrades
8.5 #System Upgrade
9 Lessons Learnt
10 Issues & Fixes
10.1 Unfixed Issues
10.2 Fixed Issues
11 Regression Testing Process
11.1 Introduction
11.2 Set up
11.3 Actions
11.4 Security
12 Transport Freeze
13 Web Applications
13.1 Dashboards
13.2 Internet Graphics Server (IGS)
14 Detailed Task Lists
14.1 Support Pack Hike (detail)
14.2 Plug-in installation (detail)
14.3 Dbase upgrades (detail)
14.4 PREPARE Process (detail)
14.5 System Upgrade (detail)
Upgrading from BW 3.0B to BW 7.0 (Netweaver 2004s)
Introduction
This Wiki contains my teams experiences in upgrading our Business Warehouse System from 3.0B to BW 7.0.
Hopefully it will be useful to anyone else who's about to embark on this. If there's anything I've missed or got wrong, then please feel free to edit it or contact me and I'll try to explain.
Rob Moore - BW Manager, Edwards Limited.
Overview & Scope
This was to be a technical upgrade of BW only. The new BW 7.0 web functionality & tool suite which requires the Java stack rather than the ABAP stack was out of scope. We had heard that the latter was where most of the problems with the upgrade lay. Our plan is to wait for this part of BW 7.0 to become more stable. Also it has a big front end change and the business didn't have sufficient resource to cope with that much change management.
Drivers
3.0B at the end of its maintenance
Opportunities to do better reporting
Options to utilise BI Accelerator
Environment
Our R/3 system was at 4.6C and was not going to be upgraded. We have APO at version SCM4.0.
Our BW system is approximately 300 GB, with 125 global users. It was at version 3.0B SP 18
We have Development, Acceptance and Production environments.
Resource & Timescales
The Project ran for 3.5 months from Feb to May 2007. We used the following resources. The percentages are the approx. amount of their time spent on the project.
Project Manager * 1 70%
BW technical team * 3 50%
ABAP coder * 1 10%
SAP Systems Development expert * 1 20%
Basis * 1 25%
High Level Plan
These are the basic areas. We planned to complete this process for each environment in turn, learning our lessons at each stage and incorporating into revised plans for the next environment. However we did the Support Packs and Plug-Ins in quick succession on all environments to keep our full transport path open as long as possible.
Upgrade BW to the minimum support pack.
Install R/3 Plug-ins PI 2004.1
Run PREPARE on BW
Dbase upgrades (Database & SAP Kernel upgrade)
System Upgrade
Summary Task List
This list contains all the basic tasks that we performed. A more detailed check list is shown below for each of the headings.
#Support Pack Hike
We moved only to the minimum acceptable SP as this seemed most likely to avoid any problems with the 3.0B system prior to the upgrade.
Apply OSS 780710 & 485741
Run Baseline for Regression tests
Full Backup
Apply SP's (we were at SP18, going to SP20)
SPAU list review
Regression testing
#Plug-in installation
Apply SAP note 684844
Import and patch Basis plugin PI 2004.1
SPAU list review
#PREPARE process
BW Pre-Prepare tasks
BW - Inconsistent Data fix
Run PREPARE
Review of results
Any showstoppers from PREPARE?
#Dbase upgrades
Database Upgrade (FixPak)
SAP Kernel Upgrade
#System Upgrade
Reverse Transport of Queries
Reconnect DAB & SAB to AAE
Run Baseline for Regression tests
Full Backup
Run the Upgrade
SPAU list review
Regression testing
Lessons Learnt
Testing is all! We picked up on a lot of issues, but would have picked up more if we'd had a full copy of our production environment to test over.
Our approach of doing a full upgrade on each environment before moving to the next one paid dividends in giving us experience of issues and timescales.
Write everything down as you go, so that by the time you get to upgrading production you've got a complete list of what to do.
We succeeded because we had people on our team who had enough experience in Basis and BW to be able to troubleshoot issues and not just read the manual.
The SAP upgrade guide is pretty good, if you can understand what they're on about...
Remember the users! The fact that the loads have been successful doesn't count for anything unless the users can see the data in Excel! There's a tendency to get caught up in the technology and forget that it's all just a means to an end.
Issues & Fixes
I've listed the main issues that we encountered. I have not listed the various issues where Transfer rules became Inactive, DataSources needed replication or we had to reinstall some minor Business Content.
Unfixed Issues
We could not fix these issues, seems like SP 13 will help.
Cant delete individual request from ODS
After PREPARE had been run, if we had a load failure and needed to set an ODS request to Red and delete it, we found that we could not. We raised an OSS with SAP but although they tried hard we couldn't get round it. We reset the PREPARE and still the issue persisted. Ultimately we just lived with the problem for a week until we upgraded production.
Error when trying to save query to itself
Any query with a re-usable structure cannot be saved (more thsan once!)
OSS 975510 fixed the issue in Dev and Acc, but NOT in Production! SP 13 may solve this once it's released.
Warning message when running some queries post-upgrade
Time of calculation Before Aggregation is obsolete. Not a big issue so we haven't fixed this one yet!
Process Chain Scheduling Timing error
Process chains get scheduled for the NEXT day sometimes and has to be manually reset.
See OSS 1016317. Implement SP13 to fix this. We will live with it for now .
Fixed Issues
Duplicate Fiscal Period values in Query
If you open up a drop down box ("Select Filter Value") for Fiscal Year/Period to filter your query, you are presented with duplicate entries for Month & Year.
Due to Fiscal Year Period InfoObject taking data from Master Data not InfoProvider. Thus it picks up all available periods not just Z2.
Auto-Emails being delayed
Emails coming from BW from process chains are delayed 2 hours on BW before being released
Due to userids that send these emails (e.g. ALEREMOTE) being registered on a diffferent timeazone (i.e. CET) from the BW system (i.e. GMT)
Pgm_Not_Found short dump
Whenever a query is run via RRMX or RSRT
Call transaction RS_PERS_ACTIVATE to Activate History and Personalisation
Characteristics not found
When running a query the warning message Characteristic does not exist is displayed for the following: 0TCAACTVT, 0TCAIPROV, 0TCAVALID
We activated the three characteristics listed and the warnings stopped. NO need to make them authorisation-relevant at this stage.(also did 0TCAKYFNM)
System generated Z pgms have disappeared
Post-upgrade the system Z-pgms ceased to exist
Discovered in Development so we compared with pre-upgraded Production and then recreated them or copying them from production.
Conversion issues with some Infoobjects
Data fails to Activate in the ODS targets
For the InfoObjects in question, set the flag so as not to convert the Internal values for these infoobjects
InfoObject has Conversion routine that fails, causing load to fail
The routine prefixes numeric PO Numbers with 0s. SD loads were failing as it was not able to convert the numbers. Presumably the cause of the failure was the running of the Pre-Prepare RSMCNVEXIT pgm.
Check the Tick box in the Update rule to do the conversion prior to loading rather than the other way round.
Requests fail to Activate on numeric data
Request loads OK (different from above issue) but fails to Activate
Forced conversion within the update rules using Alpha routine. Deleted Request and reloaded from PSA.
Database views missing after pre-PREPARE work
Views got deleted from database, although not from data dictionary
Recreated the views in the database using SE14.
Workbook role assignations lost
We lost a few thousand workbook assignments when we transported the role they were attached to into Production
The workbooks did not exist in Development, thus they all went AWOL. We wrote an ABAP program to re-assign them in production
Regression Testing Process
Introduction
We were limited to what we could do here. We didn't have a sandbox environment available. Nor did we have the opportunity to have a replica of our production data to test with, due to lack of disk space in Acceptance and lack of sufficient Basis resource.
Set up
We manually replicated our production process chains into test. We didn't have any legacy InfoPackages to worry about. We asked our super-users for a list of their "Top 10" most important queries and did a reverse transport of the queries from Production back into test (as we do not generally have a dev/acc/prodn process for managing queries, and they are mostly created solely in prodn). We made sure every application was represented. In retrospect we should have done some Workbooks as well, although that didn't give us any problems.
Actions
Prior to the various changes we loaded data via the Process chains and ran the example queries to give ourselves a baseline of data to test against. After the change we ran the same queries again and compared the results against the baseline. We tried to keep R/3 test environments as static as possible during this, although it wasn't always the case & we often had to explain away small changes in the results. After upgrading BW Development we connected it to Acceptance R/3, so that we had pre-upgrade (BW Acceptance) and post-upgrade (BW Development) both taking data from the same place so we could compare and contrast results on both BW systems. We did the same thing once BW Acceptance had been upgrading by connecting it (carefully!) to Production R/3. To get round the lack of disk space we tested by Application and deleted the data once that Application had been signed off. Once we got to System test we involved super-users to sign off some of the testing.
Security
We chose to implement the new security schema rather than choosing the option to stick with old. For us, with a relatively small number of users we felt we could get away with this & if it all went wrong, just temporarily give users a higher level role than they needed. Our security roles are not complex: we have end user, power-user and InfoProvider roles for each BW application, together with some common default roles for all. In the event we simply modified the default "Reports" role that all our users are assigned, transported it and it all went smoothly. Apart from the fact that everyone's workbooks are assigned to this role and so we "lost" them all !
Transport Freeze
Once you've upgraded Development you've lost your transport path. We planned around this as best we could and when absolutely necessary, developed directly in Acceptance or Production, applying those changes back to Development once the project was complete. Depending on what other BW projects you have running this may or may not cause you pain!
Web Applications
Dashboards
We had various dashboards designed via Web Application Designer. All these continued to function on the upgraded system. However there were various formatting changes that occurred e.g. Bar graphs were changed to line graphs, text formats on axes changed etc. SAP provides an upgrade path for moving your Web applications by running various functions. However we took the view that we would simply re-format our dashboards manually, as we didn't have very many to do. Plus the external IGS (see below) powered all our environments and needs upgrading separately as part of the SAP method. Thus we couldn't have tested the SAP path in Development without risking Production. Sticking with manual mods was a lower risk approach for us. We did find we had to re-activate some templates from BC to get some of the reports to continue to work.
Internet Graphics Server (IGS)
We had an external IGS server with v3.0B. Post-upgrade the IGS becomes part of the internal architecture of BW and thge external server is redundant. We found no issues with this; after the upgrade BW simply stops using the external IGS and no separate config was needed.
Detailed Task Lists
Support Pack Hike (detail)
Apply OSS 780710 & 485741
Communicate outage to users
Warning msg on screen
Stop the jobs which extract data into delta queues
Clear the delta queues by loading into BW
Check RSA7 in PAE that delta queues are now empty
Run Baseline for Regression tests
Stop Delta queues
Lock Out users
Full Backup
Apply SP's
Upgrade the SAP kernel from 620 to 640
SPAU list review
Apply OSS Notes 768007 & 861890
Unlock Test users (inc. RFC id's on R/3)
Regression testing
Regression sign-off
Remove warning msg
Unlock users
User communication
Plug-in installation (detail)
Communicate outage to users
Warning msg on screen
Apply SAP note 684844
Lock out users
Full Backup
Empty CRM queues
Import and patch Basis plugin PI 2004.1
SPAU list review
Apply OSS 853130
Switch back on flag in TBE11 (app. BC-MID)
Remove warning msg
Unlock users
User communication
Dbase upgrades
Dbase upgrades (detail)
Communicate outage to users
Warning msg on screen
Run Baseline for Regression tests
Stop the Data extract jobs
Full Backup
Lock Out users
Apply FixPak13SAP to DB2 database
Upgrade the SAP kernel from 620 to 640
Apply OSS 725746 - prevents RSRV short dump
Unlock Test users (inc. RFC id's on R/3)
Regression testing
Regression sign-off
Remove warning msg
Unlock users
User communication
PREPARE Process (detail)
Pre-PREPARE Process
RSDG_ODSO_ACTIVATE
Repair Info objects and recreate the views
Communicate outage to users
Warning msg on screen
Run Baseline for Regression tests
Stop the Data extract jobs
Lock Out users
Full Backup
Run RSMDCNVEXIT Using BSSUPPORT ID
If there conversion process runs longer delay the regular backup
Re-run Baselines and sign off
If there conversion process Fails repeat the steps on Sunday after the regular backup
BW work
Back up customer-specific entries in EDIFCT (note 865142)
Activate all ODS objects
Execute report RSUPGRCHECK with flag "ODS objects" (note 861890)
Check Inconsistent InfoObjects - Upgr Guide 4.4; OSS 46272; Convert Data Classes of InfoCubes - Upgr Guide 4.3
Execute report SAP_FACTVIEWS_RECREATE (note 563201)
Make sure Delta queues are empty (RSA7)
Basis Work
Full Backup of BW
Lock users
Unlock id's RFC id's and designated test users
Confirm backup complete OK
Apply OSS 447341 Convert Inconsistent Characteristic Values - Upgr Guide 4.5
Confirm OK to PREPARE
Run PREPARE
Review of results
System Upgrade (detail)
Communicate outage to users
Process errors from PREPARE
Check disk space availability for PAB
Warning msg on screen
Reverse Transport Queries from PAB to SAB & DAB
Change BW to R/3 connection
Get backup put on hold, for Ops to release later
Ensure Saturday night backup is cancelled
Final run of PREPARE
Run Baseline for Regression tests
Clear Delta Queues
Delete Local Transports
Remove process chains from schedule
Lock Out users (with some exceptions)
Confirm to Ops and Angie that we're ready
Full Backup
Incremental backup of Unix files
UPGRADE "START"
Back up kernel
Unpack latest 700 kernel to upgrade directory
Check ids required for upgrade are unlocked
Check no outstanding updates
Turn off DB2 archiving
Open up the client for changes
Stop saposcol, & delete from exe directory
Run the Upgrade
Execute the saproot.sh script
Perform the database-specific actions
Perform follow-up activities for the SAP kernel
Reimport additional programs
Import Support Packages
Call transaction SGEN to generate ABAP loads
Transport Management System (TMS)
Handover to BW Team
SPAU list review
Apply OSS Notes from SPAU
Process Function Module XXL_FULL_API (part of SPAU)
Restore table EDIFCT (if required)
Transport Fixes from our BW Issue list
Convert the chart settings - manually
Perform activities in the Authorization Area
Activate hierarchy versions
Update the where-used list
Execute the conversion program for the product master
Transport New roles to PAB
Unlock selected users
Regression testing
Regression sign-off
Go / No Go decision
Restore if required
Remove warning msg
Tell Ops that the CR is now complete
Lock down PAB
Unlock users
User communication
Perform the follow-up activities for SAP Solution Manager
Reschedule background jobs
Reschedule weekly backup on Ctrl-M
Drinks all round.
Vendors mentioned: dBase
Hope this helps. -
Transport IR and ID obejcts from SP14 to SP20 ?
We have a dual XI development environment - DEV1 and DEV0 . DEV1 was recently upgraded to SP20 while DEV0 is on SP14.
While DEV1 was being upgraded, we had to make several changes to ID and IR obejcts in DEV0 for bug fixes as well as new development.
My question is, when DEV1 comes back up, can we transport the IR and ID changes from DEV0 to DEV1 ? Does anyone have any experience with transporting across SP levels - from SP14 to SP20 ?
Or do we have to make the changes manually in DEV1 ?
thanks
anilHi Anil,
We did import from SP19 to SP20 without any problem, but in your case it is a big difference SP14 to SP20.
I prefer to do it directly in DEV1.
-Pinkle -
I recently upgraded from 3Gs to Iphone4 and want to use my old 3Gs as an ipod. how can i update
the user ID on the 3gs to a new one that I have as it is still showing a previous user ID?Settings>Store...tap the ID shown...sign out...sign back in with the ID you want to use.
-
Is it really possible to upgrade from a Treo 650 to a Treo 750?
I am not a very happy customer at the moment, but any help would be greatly appreciated. I upgraded from my old Palm Tungsten to a Zire, then to a Cingular Treo 650, combining three devices into one. I have since discovered that the Treo 650 seems to have a faulty transmission mode, as I can rarely be clearly understood by whomever I call. Am on the second (or third, I have lost track) and continue to have the same problem. I get five bars of reception but can't be understood on the other end. A bit of a problem when one is trying to call 911. Am constantly told I am "breaking up". The repair shop says it "Can't duplicate the problem". OK, then I do not want to give up all the info I have stored in the fool thing, and the 750 seems to have a different system, so I thought I would try that. All the stuff I could find seemed to indicate it wouldn't be a problem to upgrade. When the 750 arrived, I tried to install the software from the CD on my Windows XP computer. No dice. Setup encounters an error and closes. Can't even look at the files, because setup tries to run any time I access the CD. From any drive. Gave it to my girlfiend to check on her computer, and the CD seemed to run fine. Other CDs work just fine on my computer. Must be some kind of conflict, but what? Tried calling the AT&T number that suggested they could help with setup, and was first connected to the business center, they routed me to the laptop center, who routed me to the network center, who said they would have to bring in the Palm customer service and connected me to a Mac guy that dumped me back to a menu that took me to someone for whom English is a second language with whom I was trying to communicate over a very poor satellite connection. They made no sense anyway. telling me first that I couldn't have two desktops running (wrong, my girlfriend has my old Zire and the CD worked fine) and then insisting that the serial number on my device had to start with a P, when it clearly does not have any alpha characters in it. Gave up on that route of assistance. Managed to get the new ActiveSync installed from my girlfriends computer over the network. Great. Now let's get my 650 synced with Outlook (which I have not used at home) and see if we can move on. Nope. First I have to update Outlook 2000 from the old Win98 to my current XP. Find the old CD, and square that away. OK, now sync to Outlook. Nope. The sync program gives an error, saying it will only sync with Outlook 98, 2000, and XP(2002). Good grief. I have Outlook 2000, and the software apparently does not recognize it. If the Palm doesn't work, there is no reason for me to keep this phone, and I am very close to returning it and abandoning the Palm entirely when I upgrade to something that works, although I dread re-entering all that information.
Post relates to: Treo 750 (AT&T)
This question was solved.
View Solution.Thanks for the feedback. Today I installed an Enterprise version of Office 2007 I purchased a while back, but had not yet installed. Microsoft presented a few challenges, but they were quickly resolved. I then downloaded the appropriate conduit from Palm, and synced the 650 with the handheld overwriting the computer. Then used Active Destop to sync the 750. Satisfied I had moved as much info as possible, I called AT&T and had them move the phone number to the new Treo.
Bonus! When the guy at AT&T called me on the new phone to verify it, he said it sounded better than my landline.
Sorry for the streaming paragraph. When it is late I tend to write like I think.
Dave
Post relates to: Treo 750 (AT&T) -
I upgraded from iPhone 3GS to iPhone 6. Everything converted fine. Yesterday I deleted an app in error. When I downloaded the software it from iTunes ( did this many times on the old 3GS), my account is no longer recognized by the app's host servers (Playtika), even though it did after the initial conversion. Can I go back and re-sync just one app from my old phone?
Try deleting what is called the iPod Photo Cache.
http://support.apple.com/kb/TS1314
Maybe you are looking for
-
Itunes wont open-reinstall doesnt solve
itunes wont open and when i try it says it cant open b/c some of its required files are missing and to reinstall itunes. so i went to this website and d/l it again and clicked repair. that didnt work. then i tried uninstalling/deleting everything and
-
How can I keep two macs in sync?
I'm not referring to just syncing the files as I know there are services like dropbox available or file sharing. I would like to keep the mac at my office and the one at home automatically in sync. For example, if I make a change to a document at the
-
How do I see my ICal events on my work Google Calendar?
how do I see my ICal events on my work Google Calendar?
-
Error with internet browser while running oracle 10g forms
Dears, Please do help if someone can. I m using Forms [32 Bit] Version 10.1.2.0.2 (Production) for some project development. I have a form "customers". Last night as i was shutting down my system, everything was OK. Next day as i started oc4j and com
-
Hi all, Currently my firm is doing the 4.6C to ECC6 upgrade, there's a few programs having obsolete errors and I'm tasked to correcting the coding of this certain program. Here is the coding and the errors i encounter: report YPU0014 line-size 360