Upgrade from NW 7.0 EHP1 to NW 7.3

Hi All,
I am upgrading NW 7.0 EHP1 to NW 7.3 and reached the downtime phase.
I got halted by an error in UNDEPLOY_THE_OLD_DB_CONTENT phase of downtime step.
The logs are as follows :
UNDEPLOY_THE_OLD_DB_CONTENT_UTO_01.LOG
Aug 31, 2011 5:47:16 AM Info: com.sap.sdt.j710.db.DBContentUtilImpl [Threadmain,5,main]: T
he /usr/sap/EHD/JC00/SDM/root/origin/sap.com/tc/TechSrv/XML_DAS_Init/SAP AG/0/7.0103.20081105085233.0000/XML_DAS_Init.sda sda archive will be undeploy.
Aug 31, 2011 5:47:16 AM Error: com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:883) [Threadmain,5,main]:
Exception has occurred during the execution of the phase.
Aug 31, 2011 5:47:16 AM Error: com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:884) [Threadmain,5,main]:
java.io.FileNotFoundException: testconn.log (No such file or directory)
Aug 31, 2011 5:47:16 AM Error: com.sap.sdt.j710.db.DBContentUtilImpl.undeploySDAContent(DBContentUtilImpl.java:131) [Threadmain,5,main]:
java.io.FileNotFoundException: testconn.log (No such file or directory)
Aug 31, 2011 5:47:16 AM Error: com.sap.sdt.j2ee.phases.PhaseTypeUndeployDBContent.execute(PhaseTypeUndeployDBContent.java:79) [Threadmain,5,main]:
Error during undeployment of DB content. Details:java.io.FileNotFoundException: testconn.log (No such file or directory)
java.io.FileNotFoundException: testconn.log (No such file or directory)
Aug 31, 2011 5:47:16 AM Info: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:925) [Threadmain,5,main]: P
hase UPGRADE/OFFLINE_MIGRATION/UNDEPLOY_THE_OLD_DB_CONTENT has been completed.
I suppose that it is not able to find testconn.log (No such file or directory) but not sure where it will be.
Please provide a solution or workaround.
Thanks

Hi,
The log files are ideally created in the upgrade folder - log subdirectory:
/usr/sap/<SID>/upg/java/log/
Please check in this folder if the file exists. Also check if the read/write permissions to this folder are fine for user <sid>adm. It could be that the file is getting created due to lack of permissions.
Regards,
Srikishan

Similar Messages

  • ABAP/J2EE upgrade from 7.0 to EHP1...failed at START_J2EE_EP

    Hi experts,
    I'm currently running a dual stack upgrade from 7.0 to EHP1 SR1 on a 32bit windows system.  I'm using SAPup and Jup and I'm currently stuck on the Java step START_J2EE_EP the main clue I get from the logs is "Can't open shared memory administration (rc = 3)"......there's also another similar message with a different return code - " Can't open shared memory administration (rc = -107)"....
    I can't seem to find anything that has resolved the problem.
    Any help would be much appreciated.
    Cheers,
    JB

    Hi Martin,
    Thanks for the info.
    I basically changed the phase list xml file so that I could skip over this step as well as others that depended on waiting for the events from the parallel ABAP upgrade.
    So I was able to finish the uprade successfully.  But I tried to update the java stack with the latest support pack stack and it failed part way through.  Now my server0 won't start......I'll be posting the problem shortly in a new thread.
    Thanks again!
    JB

  • SAP Solman Upgrade from 7.0 to EHP1

    Hi Experts,
    We want to have upgrade for our solution manager from 7.0 to EHP1.
    Need your quick help to fix the plan of action.
    Regards,
    Abhinav

    Hi,
    There is nothing available read made.
    Yes,  i hope 2 days time is more than enough, more over its depends upon your system environment.
    We advice you to use Mopz for downloading all packages to avoid any discrepancy later.
    You might want to look into SAP Note
    Note 1169247 - Additional info for Solution Manager 7.0 EHP1 update[ Note 1169247 - Additional info for Solution Manager 7.0 EHP1 update|https://service.sap.com/sap/support/notes/1169247]
    All the best.
    Regards,
    Gagan Deep Kaushal

  • CRM Upgrade from 7.0 to EhP1 Error - The requested resource does not exist

    Hello All,
    We have recently upgrade our pilot system in CRM from CRM 7.0 to Ehp1. The upgrade was successful.
    However, when I login into the WebUI, I get an error message as follows:
    404 Not Found
    The requested resource does not exist
    Details: Go to main page of this application
    I got in touch with the Basis team and tried to activate some services through SICF that were deactivated because of the upgrade. But we still encounter the above error everytime I tried logging into WebUI.
    I kindly request to provide some pointers towards the resolution of the same.
    Thanks and regards,
    VSK.

    Hi,
    please try to activate all SICF services under sap->bc->bsp.
    If needed deactivate them and activate afterwards again to be sure all services are active.
    Good luck
    Kind regards
    Manfred

  • How to upgrade from Solman 7.0 to 7.0 EHP1?

    Hi,
    In the SAP note 1169247, it talks about doing the upgrade from 7.0 to EHP1 using SAINT and JSPM. But in the Upgrade Guide SAP Enhancement Package 1 for Solution Manager 7.0 - UNIX Oracle˝, it talks about running the upgrade using an Upgrade MAster DVD.
    1. Now is this the same as the EHP installer? If so, why is it not mentioned anywhere in the upgrade guide that we have to use EHPI? If not, what is this Upgrade Master installer?
    2. Should I use SAINT/JSPM for the upgrade to solman 7.01?
    Your answers to these questions will be highly appreciated.
    Thanks,
    Ajay

    Hi Ajay,
    I had the same question a few day's ago.
    The difference between these two methods are the word updarte and upgrade.
    If you are on Solman 7.0 you have to do a update with SPAM/SAINT.
    If you are on Solman 3.0 or something you have to do a upgrade with the master dvds. You can read this on one of the first sites of the upgrade guide.
    So you have to use SPAM/SAINT, and the Update Guide for EHP1 Using SPAM/SAINT will help you.
    [Update Guide on Marketplace|https://websmp101.sap-ag.de/~sapidb/011000358700000427772009E.PDF]
    Regards
    Tobias

  • 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 PM

    This 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

  • Upgrading from PI 7.1 to PI 7.1 Ehp1

    Hi,
      We are planing to upgrade from PI7.1 SP7 to PI 7.1 EHP1.
    How much time will take to do  complete upgrade -
    After upgrade doe's it will effect any EDI scenario's or webserice scenario's
    and what kind of issues we may face while doing upgrade.
    and what else precations we need to take care.
    If there any docuemnt upgradeing from PI 7.1 to EHP1 please provide me the link.
    appriciate your help.
    Regards,
    Venu.

    Hi Venu,
    Please refer this link , it will give you insight to PI 7.1 EHP1 details.
    SAP Enhancement Package 1 for SAP NetWeaver Process Integration 7.1 - Details [original link is broken]
    regards,
    Srinivas

  • Upgrade to PI 7.1 EHP1 from PI7.0 - Stability of the Product

    Dear Experts,
    We are currently working on PI7.0 from last two year and it is working quite fine. We are now in the process of upgrading it to PI7.1 EHP1 SP3/4. We want to upgrade it mainly for using PI's SOA and advance adapter engine functionality.
    We would like to know whether PI7.1 EHP1 is stable and whether it is fine to go ahead with this now. We are planning for Production upgrade in next month.
    Please comments and would like to have all inputs related to upgrade.
    with regards,
    Ravi Siddam

    Hi Ravi,
        I worked on 7.0,7.1 and now on 7.1 EHP1,stability point of view there is no doubt PI7.0 is solid.
    I experienced the same with P.1 and 7.1EHP1 too.so you can upgrade to PI7.1 EHP1.
    But if you want to implement new features like Adavced Adapter Engine ,there are some limitaions think before to implementing the same.
    to improve performace better to go for message packaging it significantly improve the performace,i expericed the same.
    implementing SOA Concepts and reusing the same,you need to put lot off effort to analyse the existing servieces,but it will be really helpfull.
    Cheers,
    Raj

  • How to upgrade from PI 7.1 SP8 to PI EhP1

    Hello
    We plan to upgrade from PI 7.1 SP8  to PI 7.1 EhP1,but  we do not know how to apply it. ..
    Please tell us the obtaining destination of the material of the installation guide etc.
    any other info that you can share.

    refer this link for details about new features for Enhancement Package 1 of the new release SAP NetWeaver Process Integration 7.1 will be presented. This will cover the new functions planned for the Enterprise Services Repository , Services Registry, and the Service Bus.
    [http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b054300d-6b36-2b10-6187-86065808e88e]

  • BI Upgrade from 7.0 EHP1 to 7.3

    Hi All,
    Our BI ABAP is on 7.0 EHP1. We are planning to upgrade it to BI 7.3.
    Doubts:
    1. I am looking for BI specific upgrade document.
    2. And the SAPup tool version to be used for this and any related document for this.
    3. Is there any known issues after upgrade to BI 7.3
    Thanks
    Goldy

    Hi,
    please check below thread for same discussion:
    BI Upgrade from 7.0 EHP1 to BI 7.3
    Thanks
    Sunny

  • Upgrade from SCM 5.1 to SCM 7.0 SR1 (with NW 7.0 EHP1 SR1)

    Hi folks,
    we are trying to upgrade our SCM5.1 to SCM 7.0 SR1. There seems to be a problem in the phase, where SAPup is trying to detect the needed CDs / DVDs. SAPup recognizes that "FRP" is used within the system. There appears a dialog to enter the mount points for the DVDs required for the upgrade.
    It says <<Enter at least the mount point for the DVD titled "FRP Software DVD">>. All other needed media is accepted, but not the DVD with the FRP-Software.
    SAP Note "1300960"  explains, that as of SAP Business Suite 2008 onward, no media without a MID.XML file will be accepted for upgrades (e.g. media containing Add-Ons).
    I have opended a message to SAP Support, but there is no solution / workaround until now. I cannot skip the phase and therefore it is not possible to launch / continue the entire upgrade.
    SAPup Version is "7.10/7, build 31.010 for UNICODE"
    Has anyone faced the same problem with no-MID.XML based media?
    Thank you for any advice!
    Kind regards,
    Marcel Jentsch

    Hi,
    We just upgraded from SCM 5.0 to 7.0 sp9.
    You need not deactivate the DP planning areas before upgrade.
    We did not face any issues because of this.
    Regards,
    Ashok

  • Upgrade from 4.6C to ERP6.0 EHP4 NW7.01 fails on EHP_INCLUSION

    Hello dear friends at SDN forums,
    We are performing an upgrade from a 4.6C Non Unicode source release to a SAP ERP 6.0 EHP4 based on NW 7 EHP1 Non Unicode.
    Every phase has gone more or less fine until the current phase EHP_INCLUSION in SAP EHPI tool.
    We are trying to specify the stack file manually, cosu00B4  SAP EHPI does not find it automatically via RFC against Solution Manager. I donu00B4t discard a possible missconfiguration in the RFC destination "BACK" configuration (the one that points from our target system to the Solution Manager), but thatu00B4s another story.
    Anyway, that shoulnu00B4t be relevant for the trouble Iu00B4m expressing.
    As we are on source release 4.6C  I must make use of the .txt stack file and not the .xml file, as per SAP notes.
    The symptom: everytime I retry that EHP_INCLUSION phase, it complaints about "Sever errors detected. Error Code = -1. Reason: The stack configuration does not contain a product stack".
    Iu00B4ll also paste here the contents of the EHP_INCLUSION.log trace file:
    1 ETQ201 Entering upgrade-phase "EHP_INCLUSION" ("20100715150020")
    2 ETQ367 Connect variables are set for standard instance access
    4 ETQ399 System-nr = '00', GwService = 'sapgw00'
    4 ETQ399 Environment variables:
    4 ETQ399   dbs_ora_schema=SAPR3
    4 ETQ399   auth_shadow_upgrade=0
    4 ETQ380 computing toolpath for request "TP_DEFAULT"
    4 ETQ382 translates to group "R3UP_TOOL_GROUP_OLD"
    4 ETQ383 translates to path "D:\usr\sap\CES\SYS\exe\run"
    4 ETQ383 translates to path "exe"
    4 ETQ399 Set environment for standard connect:
    4 ETQ399 ENV: dbs_ora_schema=SAPR3
    4 ETQ399 ENV: auth_shadow_upgrade=0
    4 ETQ399 Set RFC variables for standard connect:
    4 ETQ399 System-nr = '00', GwService = 'sapgw00'
    4 ETQ399 Set tool parameters for standard connect:
    4 ETQ399   default TPPARAM: DEFAULT.TPP
    1 ETQ200 Executing actual phase 'PREP_EXTENSION/EHP_INCLUSION'.
    1 ETQ399 Phase arguments:
    2 ETQ399 Arg[0] = 'ADDONEHP.DMP'
    2 ETQ399 Arg[1] = 'NAVERSEHP.DMP'
    2 ETQ399 Arg[2] = 'SPDA_EHP_INCLUSION.LOG'
    2 ETQ399 Arg[3] = ''
    2 ETQ730 Starting upload of all package files in "
    dbapru001\sapmnt\trans\EPS\in"
    4 ETQ010 Date & Time: 20100715150020
    4 ETQ230 Starting RFC Login to: System = "CES", GwHost = "dbapru001", GwService = "sapgw00"
    4 ETQ359 RFC Login to: System="CES", Nr="00", GwHost="dbapru001", GwService="sapgw00"
    4 ETQ232 RFC Login succeeded
    4 ETQ233 Calling function module "SPDA_PREPARE_PATCH" by RFC
    4 ETQ234 Call of function module "SPDA_PREPARE_PATCH" by RFC succeeded
    4 ETQ239 Logging off from SAP system
    4 ETQ010 Date & Time: 20100715150024
    2 ETQ732 Package descriptions uploaded successfully
    4 ETQ399 EhP stack selection ...
    4 ETQ399 Reading stack content ...
    4 ETQ399 ... reading stack configuration file "C:\SMSDXML_CES.txt"
    4 ETQ230 Starting RFC Login to: System = "CES", GwHost = "dbapru001", GwService = "sapgw00"
    4 ETQ359 RFC Login to: System="CES", Nr="00", GwHost="dbapru001", GwService="sapgw00"
    4 ETQ232 RFC Login succeeded
    4 ETQ233 Calling function module "SPDA_GET_STACK_INFO" by RFC
    2 ETQ399 Returned table ET_STACK_NCVERS:
    2 ETQ399 Returned table ET_STACK_PACKAGES:
    4 ETQ399 ... Error reading stack info (rc=-1, reason="The stack configuration does not contain a product stack")
    That file was generated from Solman Mopz, was saved with a short path name just in case it could be problematic.
    The Solman is on version NW 7 EHP1. Our 4.6C SPAM version is 50 (the latest available).
    Iu00B4ve been fighting this issue for several days unsuccessfully, and it seems like thereu00B4s no documentation on it.
    Iu00B4ve re-read SAP notes , master, EHP and upgrade guides several times, and also similar problems (but not exactly the same as mine) here at SDN forums.
    Besides, now Iu00B4m having a problem to create customer messages to OSS which will last a few days (due an issue with our old installation number in SAP Service Marketplace). Thatu00B4s why Iu00B4m trying to obtain support from this forum, before we can obtain a response from SAP OSS.
    Has anybody experienced something similar?
    Thanks in advance for your help.
    Javier

    Hi FDK,
    As far as I´m concerned, I promise I will write how we solved it when we get it.
    The news are: at last we could create a customer message to SAP Support, and SAP has told us to:
    1) Ensure that our Solution Manager is in a sufficiently high SP Stack level. In our case, as we have a Sol. Manager based on NW 7 EHP 1 with SP Stack level 20, they are asking us to apply SP Stack level 22 as first meassure.
    2) In case we cannot afford to do the mentioned meassure immediately, then they suggest us another possibly working option: to downgrade our SPAM 4.6C from level 50 to 48. There is a SAP Note that explains how a reimport of a Support Package for SPAM can be done (and it seems like it´s even possible to downgrade the SPAM level, I didn´t know that):
    SAP Note 684564: Re-importing a SPAM/SAINT update
    So, now we are working on these suggestions. As the Solution Manager is really not "ours", but belongs to our SAP VAR (partner), we need to wait until they can schedule this technical task.
    So, right now the immediate task I´m trying to perform is downgrading our  SPAM 4.6C from level 50 to 48.
    But, I have a problem and have just let know it to SAP in the customer message: I have no way to get such level 48 of SPAM 46C. SAP always only hosts the last (or the 2 most recent as much) version of SPAM in the Software Download Center of SAP Service Marketplace. Thus, right now if you navigate in SAP Service Marketplace you´ll only find the 50 level version of SPAM 4.6C. I´m again waiting for SAP ´s response concerning this.
    Best regards,
    Javier

  • Upgrade from 3.0B (release 620) to BI 7.1 (release 710)

    Hi,
    Please guide me whether it is possible to upgrade from BW 3.0B system to BI 7.1, I am in release 620 now.
    Can you please help me locate upgrade guide for the same?
    Looking forward for your replies
    Thank you
    Rajath

    lol
    There is nothing called as NW BI 7.1,
    I found the upgarde guide for NW 7.0 BI : https://websmp205.sap-ag.de/~sapidb/011000358700001461642008E#q2
    in SMP,
    We can upgrade to SAP NETWEAVER 7.0 from the following basis release:
    SAP BW 2.0B; SAP BW 2.1C; SAP BW 3.0B; SAP BW 3.1 CONTENT;
    From there we can install EHP1 for NW 7.0 i.e of basis 701.
    Thank you all for taking your time to resolve my problem.
    Cheers!
    Rajath

  • Upgrading to PI 7.1 EHP1

    Hello,
    We are in the middle of upgrading from PI 7.0 SP9 to PI 7.1 EHP1. During the JAVA Configuration phase we are getting an error during the RUN_PREPARE_MIG_CONTROLLERS phase. The error we are getting in the logs is:
    Could not execute MTI process. See log files /usr/sap/XID/upg/java/log/JMT_FRAMEWORK_MJA_01.OUT and /usr/sap/XID/upg/java/log/JMT_FRAMEWORK_MJA_01.ERR.
    The logs for the JMT_FRAMEWORK_MJA_01.OUT shows the following errors several times:
    thread_cpu_time: sanity error, might lead to negative CPU time.
        measured thread: 1286
        old measurements done by thread 4113: 439000, 0
        new measurements done by thread 4113: 230000, 1270000
        invocations: 36 number of errors: 2
    The JMT_FRAMEWORK_MJA_01.ERR shows the following error:
    #2.0 #2010 06 02 08:51:55:383#0-500#Error#com.sap.sdt.jmt.migrationtool.err#
    ###C000AC10FBD900000000000031D1FC02###com.sap.sdt.jmt.migrationtool.err########Thread[main,5,main]#Plain##
    java.lang.NullPointerException:
         at com.sap.aii.af.jpr.library.migration.LibraryMigrationManagerImpl.migrateJPRLibraries(LibraryMigrationManagerImpl.java:73)
         at com.sap.aii.af.component.migration.JPRMigrationController.migrateFileSystemData(JPRMigrationController.java:65)
         at com.sap.sdt.jmt.mc.FileSystemMigrationExecuter.executeController(FileSystemMigrationExecuter.java:60)
         at com.sap.sdt.jmt.mc.AbstractMigrationControllerExecuter.executeMigrationController(AbstractMigrationControllerExecuter.java:394)
         at com.sap.sdt.jmt.mc.AbstractMigrationControllerExecuter.execute(AbstractMigrationControllerExecuter.java:357)
         at com.sap.sdt.jmt.migrationtool.MigrationToolImport.execute(MigrationToolImport.java:863)
         at com.sap.sdt.jmt.migrationtool.MigrationToolImport.migrateMigrationControllerData(MigrationToolImport.java:1326)
         at com.sap.sdt.jmt.migrationtool.MigrationToolImport.startTool(MigrationToolImport.java:610)
         at com.sap.sdt.jmt.migrationtool.MigrationToolImport.main(MigrationToolImport.java:1190)
         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:585)
         at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:161)
    Has anyone seen this before in their upgrades? We are running our PI system on the AS/400 platform as well.
    Thanks,
    Dale Dingmann

    Download the latest 7.11 SPXX SAPXIAF_XX.sca patch from the ServiceMarketplace.
    Extract the com.sap.aii.af.jpr.migration archive (using WinRAR)
    Deploy the com.sap.aii.af.jpr.migration archive by following the steps in the attached note #1311608, which it shows how the patched migrations can be applied.
    -credit to Lucas Santos SAP@KR@Support Consultant

  • Upgrade from CE 7.2 to Portal 7.3 or higher

    Hi Experts,
    We are planning to upgrade portal from CE7.2 to 7.31 or higher.
    First of all I want to know which will be the best version to upgrade from CE7.2 ?
    From SAP installation and upgrade guide I can see this will be a simple EHP upgrade if we goes for 7.3 EHP1 .
    Now I wan to know after upgrade what will be the effect/issues on below mentioned custom application areas.
    1. Portal Branding (theme)
    2. CAF components (EJB)
    3. Portal custom DB table.
    4. BPM applications
    5. Service Registry
    6. Web services
    Please let me know your inputs on this.
    Thanks & Regards,
    Sambaran Chakraborty

    Hi,
    Of course upgrade from CE 7.11 to CE 7.2 IS POSSIBLE. We are doing this in our landscape.
    Please refer to the following guide:
    Update Guide CE 7.2 (Update from CE 7.1/CE 7.1 EHP1) - SP<nn>
    from:
    service.sap.com/instguidesnwce72 --> Update --> SP<nn>.
    Only this one guide is sufficient. This upgrade is just like SPS update.
    Regards,
    Shitij

Maybe you are looking for

  • Can not start mysql server

    I recently installed mysql server on my mac os 10.6.8, earlier i had installed XAMPP on my machine but i have uninstalled it(deleted it & ran few commands in terminal), but now when i try to start server from preference pane it doesn't start & not fr

  • Why does my Apple wireless mouse suddenly need batteries changed every week?

    I'm getting "running low on batteries" messages regularly now. This never happened before. The mouse is about five years old.

  • Dupulilcate contacts

    I recently replaced my Treo 680...and during the hotsync operation ended up with duplicate contacts...How do I go about deleting duplicate entries.  Otherwise, my contact entries are now doubled   Post relates to: Treo 680 (AT&T)

  • How do I resort files and folders by name in Column View of Finder when Arrange by Name doesn't work?

    I was using the arrange by function to select different arrangements of the files and folders in Finder (column view) but now that I want to return to having them arranged by Name, it is not rearranging the files/folders by name.  Instead they stay i

  • Administrator's Name...

    When trying to install adobe flash player....what does it mean to "type in an administrator's name and password to allow this?" What username and password are we supposed to be typing in because I've tried everything I could think of. I really need s