PI_Basis Upgrade

We are going to upgrade stack level from 13 to 16.
Current SP level for PI_Basis is Release 2005_1_620 Patch 13.
I see Releases 2003_1_620, 2005_1_720 and 2006_1_620 in stack queue for 16 ( In service market place ).
My Question is :
Is it 2005_1_620 is equivalent to 2006_1_620 or i need to upgrade 2005_1_620 release to 2006_1_620 ?
Thanks

Hi,
You should upgrade to 2006_1_620 and then import the support packages for 2006_1_620.
Regards,
Olivier

Similar Messages

  • Upgrade-phase "CONFLICT_CHECK" fails with error

    Please help, I am trying to run the prepare for our BW 3.5 to BI 7.0 (SR2) upgrade and am running into an error in the CONFLICT_CHECK phase:
    Conflict check failed, rc = "-2", reason = "Internal error: OCS_COLLECT_ADDON_TASKS: MISSING_CMD_IMPORT SAPK
    INBC9D"
    When i ran this in our beta and dev environment I wasn't updating as many support packs and plug in's; and I did not run into this error.  Here are the addon's I am updating
    Addon       current version           upgraded version       how I am updating
    PI_BASIS     2005_1_640     2006_1_700     UPG With ADDON CD
    BI_CONT     353                     703                     UPG WITH SAINT PACK
    ST-A/PI     01F_BCO640     -                     DELETE
    ST-PI     2005_1_640     2005_1_700     UPG WITH SAINT PACK
    Here is the output file:
    more CONFLCHK.LOG
    1 ETQ201XEntering upgrade-phase "CONFLICT_CHECK" ("20071011155952")
    2 ETQ367 Connect variables are set for standard instance access
    4 ETQ399 System-nr = '30', GwService = 'sapgw30'
    4 ETQ399 Environment variables:
    4 ETQ399   dbs_ora_schema=SAPBWS
    4 ETQ399   auth_shadow_upgrade=0
    4 ETQ399 (trc) R3upExtendedInclusion: TRUE (default)
    4 ETQ399 (trc) R3upExtendedInclusion: TRUE (default)
    2 ETQ160 Starting conflict check
    4 ETQ010 Date & Time: 20071011155952 
    4 ETQ230 Starting RFC Login to: System = "BWS", GwHost = "sapbws", GwService = "sapgw30"
    4 ETQ233 Calling function module "SPDA_CONFLICT_CHECK" by RFC
    2 ETQ161 Conflict check failed, rc = "-2", reason = "Internal error: OCS_COLLECT_ADDON_TASKS: MISSING_CMD_IMPORT SAPK
    INBC9D"
    4 ETQ010 Date & Time: 20071011155952 
    As you can see it is looking for SAPKINBC9D.  This is not an addon package I selected.  The PI_BASIS uses SAPKINBC9A.  I checked SEPS (EPS admin) and do not see this.  I also tried to search for this file on service.sap.com and do not see it.  I have no idea what could be causing this.  Please help!
    Erika

    Hello,
    If I remember correctly it was the version of PI_BASIS.  I ended up upgrading the following addon's during the upgrade follows:
    PI_BASIS     2005_1_640     2005_1_700     Inst/UPG with STD CD
    BI_CONT     353     703     UPG WITH SAINT PACK
    ST-A/PI     01F_BCO640     -     DELETE
    ST-PI     2005_1_640     2005_1_700     UPG WITH SAINT PACK
    After the upgrade, I applied the PI_BASIS upgrade and support packs.

  • Upgrade of PI_BASIS 2005_1_620/16 in 4.7 to ECC 6.0 Upgrade

    We are currently upgrading our Enterprise 4.7x200 system to ECC 6.0 using the SR3 upgrade CD's. In the BIND_PATCH phase the system is reporting:
    WARNING: PI_BASIS - selected package level is 15, equivalence level is 16
    We have previously implemented PI_BASIS 2005_1_620 SP 16 in the system and it's not complaining that in order to successfully upgrade to 2005_1_700 we should go to SP 16 as well as part of the upgrade, however SP 16 for this release is not out yet so we can't include the SP in the upgrade.
    Our list currently shows...
    SAP_BASIS <none> 0015 0014 15
    SAP_ABA <none> 0015 0014 15
    PI_BASIS <none> 0016 0014 15
    ST-PI <none> 0006 0005 6
    SAP_BW <none> <none> 0016 17
    SAP_AP <none> <none> 0011 12
    SAP_HR <none> 0029 0022 30
    SAP_APPL <none> <none> 0011 13
    EA-IPPE <none> 0012 0011 13
    EA-APPL <none> <none> 0011 13
    EA-DFPS <none> <none> 0011 13
    EA-HR <none> 0029 0022 30
    EA-FINSERV <none> <none> 0011 13
    FINBASIS <none> <none> 0011 13
    EA-PS <none> <none> 0011 13
    EA-RETAIL <none> <none> 0011 13
    EA-GLTRADE <none> <none> 0011 13
    ERECRUIT <none> <none> 0011 13
    SEM-BW <none> <none> 0011 13
    LSOFE <none> <none> 0011 13
    SAP so far has responded that we need to wait until the SP16 is released, but this won't occur until the end of November as far as we can tell.  Waiting would delay the GoLive for the upgrade almost a year.
    They also suggested to revert to a version of our system that does not contain 2005_1_620 SP16, however this is not possible, as this SP has already moved to production and restoring the database would result in data loss.
    My most recent questions back to them, which I'm hoping someone here might be able to answer for me are....
    1) When is the next SP for PI_BASIS 2005_1_700 being made available.
    2) Is is possible to upgrade PI_BASIS 2005_1_470 to PI_BASIS 2006_1_470 prior to starting the upgrade and will we run into the same problems.
    3) It appears that PI_BASIS 2005_1_470 SP 16 contains only two objects... LIMU CLSD /SCMB/CL_DF_DOCUMENT & LIMU CPUB /SCMB/CL_DF_DOCUMENT. What would the impact be if we simply continued the PREPARE phase (ie, responded IGNORE to the warning message)?
    Any help would be appreciated.
    Thanks.

    Hi,
    Please check the following websites.
    1. http://service.sap.com/enterprises.
    2. http://service.sap.com/sp-stacks--> search for SAP R/3 4.7E of PI_BASIS pulg ins.
    3. No issues of those two objects.Once you have done upgrade PREPARE phase is successfull, almost upgrade is successfully.
    Regards,
    Srini Nookala

  • PI 7.1 upgrade - PI_BASIS patch level in ECC

    Hello
    We are looking at upgrading our XI 7.0 SP12 to PI 7.1. Our backend ECC system is at PI_BASIS SP11. Most of our interfaces with the backend are through ABAP proxies.
    Will an upgrade to PI 7.1 demand an upgrade to PI_BASIS in the backend ECC system as well?
    If not, what is the minimum SP level the PI_BASIS component in the backend ECC system should be at?
    I don't find this information in upgrade guide; where will this information be normally available?
    Thanks
    KK

    You can use PI 7.1 with any SAP system.
    However, if you want to use Abap proxies based on message interfaces of type "stateless" with WS-RM protocol, the ECC requires SP 14.
    The Abap proxies based on XI 3.0 protocol do not require any special patch level.
    Regards
    Stefan
    Edited by: Stefan Grube on Aug 28, 2008 4:34 PM

  • Not Getting SAPKINBC9A upgrade patch for PI_BASIS

    Hi All,
    I am implementing SPS 12 in my ECC 6.0 System. System is on oracle and linux. My PI_BASIS patch is on 2005_1_700 level and i need to upgrade the same on 2006-1_700. So i cannnot import any of 2006 patch before this component
    I am not getting the support pack SAPKINBC9A on OSS. Am i searching right patch or do i need to implement some other patch for this.
    Thanks in Advance
    Thanks,
    Bhanu Pratap Singh

    I got the patch. And i have implemented the same with SAINT.

  • PI_BASIS component  upgradation

    Hi
        We have the requirement of upgrade the PI_BASIS component from 2005_1_700 level 009 to 2006_1_700 level 000 .
    What are the pre-requisite and how to upgrade  this?
                 Due to low level of PI_BASIS  component we are getting errors in Development.
    Best Regards
    Srikanth

    Thanks Subash,
                                     One more issue, I have found 3 files in  support pack add-on  regarding PI_BASIS 2006_1_700.
    i.e 1. installation, 2.upgrade , 3. installation and Upgrade.
    Which file I can download ? I would like to upgrade from PI_BASIS 2005 to PI_ BASIS 2006 ?
    Thanks
    Srikanth

  • Upgrade to PI_BASIS, 2006_1_700

    I need to load support pack SAPKW0015, a prerequisite is to upgrade to PI BASIS 2006_1_700. When i try to do the upgrade i get a message that SAPKIPYM05 is a prerequisite. I cannot find support pack SAPKIPYM05 but only SAPKIPYM01 - 04.
    Please help

    Yes Paul u r right that we cannot find support pack SAPKIPYM05 but only SAPKIPYM01 - 04.
    This is the reason for it: All corrective software packages, for SAP NetWeaver 2004s and SAP Business Suite 2005 and beyond that are delivered after April 2nd, 2007 will ONLY be available via SAP Solution Manager's Maintenance Optimizer.
    U can't do it through download manager directly. Also , it is not showing SAPKW0015 support package in
    service market place.
    I think u have to configure the maintenance optimizer for it .
    Check here for more details: https://websmp105.sap-ag.de/solman-mopz (needs userid & password).
    Award point if helpful.
    Edited by: abinash sahu on Feb 25, 2008 10:04 AM

  • ERP5.0 to 6.0 upgrade-SAPup stuck after MAIN_SHDRUN/DDIC_UPG got canceled

    Hi Experts:
    We are currently upgrade SAP ERP 5.0 to ERP 6.0 EHP4 SR1 ABAP Based on SAP NW 7.0 eph1. During the upgrade, the SAPup process was canceled at MAIN_SHDRUN/DDIC_UPG phase of Preprocessing roadmap step by SIDadm. After that, it doesnu2019t allow user to continue or reset this step. The error message from SAPup.log is pasted below:
    CURRENTPHASE MAIN_SHDRUN/DDIC_UPG
    ...started at 20110316230706
    Reading Parameter File "C:\usr\sap\DEV\upg\abap\bin\APPEND.APP" at 20110316230706
    ...begin processing at 20110316233243
    -> received signal Ctrl C from keyboard and exited at 20110317021613
    ...CANCELED at 20110317021613.
    ...CANCELED at 20110317021613.
    Error message set: 'System error: Invalid access to memory location.
    ************************* SAPup started in UPGRADE mode *************************
    This is SAPup version 7.10/7 patch level 31.022 compile time 01:28:19 Sep  3 2010.
    This is UNICODE SAPup!
    Running in graphics mode batch.
    WARNING line 8029 in SYS file: Unknown id in line '4646     "20012" SFX;20110316233243;20110317021613;"";"C:
    usr
    sap
    DEV
    upg
    abap
    exe
    :MY'
    ERROR line 8030 in SYS file: Missing id in line '     "20012" SFX;20110316233243;20110317021613;"";"C:
    usr
    sap
    DEV
    upg
    abap
    exe
    :MY'
    Below is our system information:
    Database: Microsoft SQL Server 2005   9.00.4035
    Operating system:  Windows Server 2003 R2, Enterprise x64 Edition SP2
    Source System
    Release:  SAP ECC5.0
    Kernel:  640 patch 247
    R3trans version:  6400.364.18.43311
    Tp version:  6400, 352, 18, 23218
    Disp+work u2013V: 6400, 247, 15, 22555
    Support Pack Level:       
    SAP_ABA     640     19     SAPKA64019     Cross-Application Component
    SAP_BASIS     640     19     SAPKB64019     SAP Basis Component
    PI_BASIS     2005_1_640     9     SAPKIPYJ69     Basis Plug-In (PI_BASIS) 2005_1_640
    ST-PI     2008_1_640     0          -     SAP Solution Tools Plug-In
    SAP_BW     350     19     SAPKW35019     SAP_BW 350
    SAP_APPL     500     15     SAPKH50015     Logistics and Accounting
    SAP_HR     500     5     SAPKE50005     Human Resources
    EA-IPPE     300     4     SAPKGPIC04     EA-IPPE 300: Add-On Installation
    PI     2004_1_500     14     SAPKIPZI6E     PI 2003_1_470 : Add-On Delta Upgrade
    EA-APPL     500     5     SAPKGPAC05     SAP R/3 Enterprise PLM, SCM, Financials
    EA-DFPS     500     5     SAPKGPDC05     SAP R/3 ENTERPRISE DFPS
    EA-FINSERV     500     5     SAPKGPFC05     SAP R/3 Enterprise Financial Services
    EA-GLTRADE     500     5     SAPKGPGC05     SAP R/3 Enterprise Global Trade
    EA-HR     500     5     SAPKGPHC05     SAP R/3 Enterprise HR Extension
    EA-PS     500     5     SAPKGPPC05     SAP R/3 Enterprise Public Services
    EA-RETAIL     500     5     SAPKGPRC05     SAP R/3 Enterprise Retail
    P3A     V500     7     SAPKIAF507     P3A V500 : Add-On Installation
    ST-A/PI     01K_ECC500     0          -     Application Servicetools for ECC 500
    Target System 
    Release:  SAP ERP 6.0 Including Enhancement Package 4 Support Release 1 ABAP
                Based on SAP NetWeaver 7.0 Including Enhancement Package 1
    Kernel:  701 32
    R3trans version:  7010.129.18.43264
    Tp version:  7010.124.18.35265
    Upgrade type:  High resource use (archive off)
    Support Pack Level:       
    SAP_BASIS     701     0          -     SAP Basis Component
    SAP_ABA     701     0          -     Cross-Application Component
    PI_BASIS     701     0          -     Basis Plug-In
    ST-PI     2008_1_700     0          -     SAP Solution Tools Plug-In
    SAP_BW     701     0          -     SAP Business Warehouse
    SAP_BS_FND     701     0          -     SAP Business Suite Foundation
    WEBCUIF     700     0          -     SAP WEBCUIF 700
    SAP_AP     700     0          -     SAP Application Platform
    SAP_HR     600     0          -     Human Resources
    EA-IPPE     400     0          -     SAP iPPE
    EA-GLTRADE     600     0          -     SAP Enterprise Extension Global Trade
    FINBASIS     600     0          -     Fin. Basis
    EA-RETAIL     600     0          -     SAP Enterprise Extension Retail
    EA-PS     600     0          -     SAP Enterprise Extension Public Services
    EA-FINSERV     600     0          -     SAP Enterprise Extension Financial Services
    EA-DFPS     600     0          -     SAP Enterprise Extension Defense Forces & Public Security
    EA-APPL     600     0          -     SAP Enterprise Extension PLM, SCM, Financials
    EA-HR     600     0          -     SAP Enterprise Extension HR
    FI-CA     600     0          -     FI-CA
    SEM-BW     600     0          -     SEM-BW: Strategic Enterprise Management
    P3A     V604     4          -     P3A V604 : Add-On Installation
    ST-A/PI     01M_ECC600     1          -     Application Servicetools for ECC 600
    Would really appreciate it if anyone can help...

    Hello Ling Lu,
    this error points out to a corrupted MEMSAPehpi.dat file, probably when you terminated the session via Ctrl+C.
    You must comment out the last line(s) of this file in order to proceed. Please open it and look for a repeated or incomplete last line(s) and comment it out. Make a backup of the file first, then repeat the phase, it should work.
    Best regards,
    Tomas Black

  • Upgrade from R/3 4.6C to ECC 6.00 : languages

    Hi,
    We're trying to upgrade from SAP R/3 4.6C to ECC 6.00 under NT environment, having Oracle as database. During the preparation phase, we got the following error, and in our current SAP system R/3 we have 2 additional languages NL and FR (EN and DE are already in), can you please explain why this phase is blocking in this step, and if I continue I've to do a full language import, thanks in advance.
    The following language(s) could not be updated yet:
    - French       for component EA-APPL
    - French       for component EA-DFPS
    - French       for component EA-FINSERV
    - French       for component EA-GLTRADE
    - French       for component EA-HR
    - French       for component EA-IPPE
    - French       for component EA-PS
    - French       for component EA-RETAIL
    - French       for component ECC-DIMP
    - French       for component ERECRUIT
    - French       for component FI-CA
    - French       for component FI-CAX
    - French       for component FINBASIS
    - French       for component INSURANCE
    - French       for component IS-CWM
    - French       for component IS-H
    - French       for component IS-M
    - French       for component IS-OIL
    - French       for component IS-PS-CA
    - French       for component IS-UT
    - French       for component LSOFE
    - French       for component PI_BASIS
    - French       for component SAP_ABA
    - French       for component SAP_AP
    - French       for component SAP_APPL
    - French       for component SAP_BASIS
    - French       for component SAP_BW
    - French       for component SAP_HR
    - French       for component SEM-BW
    - French       for component ST-PI
    - Dutch        for component EA-APPL
    - Dutch        for component EA-DFPS
    - Dutch        for component EA-FINSERV
    - Dutch        for component EA-GLTRADE
    - Dutch        for component EA-HR
    - Dutch        for component EA-IPPE
    - Dutch        for component EA-PS
    - Dutch        for component EA-RETAIL
    - Dutch        for component ECC-DIMP
    - Dutch        for component ERECRUIT
    - Dutch        for component FI-CA
    - Dutch        for component FI-CAX
    - Dutch        for component FINBASIS
    - Dutch        for component INSURANCE
    - Dutch        for component IS-CWM
    - Dutch        for component IS-H
    - Dutch        for component IS-M
    - Dutch        for component IS-OIL
    - Dutch        for component IS-PS-CA
    - Dutch        for component IS-UT
    - Dutch        for component LSOFE
    - Dutch        for component PI_BASIS
    - Dutch        for component SAP_ABA
    - Dutch        for component SAP_AP
    - Dutch        for component SAP_APPL
    - Dutch        for component SAP_BASIS
    - Dutch        for component SAP_BW
    - Dutch        for component SAP_HR
    - Dutch        for component SEM-BW
    - Dutch        for component ST-PI
    Please mount another Language Disk for these language(s).
    If you do not have further Language Disk(s), you may
    continue, but the languages mentioned above will be lost
    after the upgrade. A full language import has to be
    performed after the upgrade to reinstall the language(s).
    ? continue
    ? cancel

    Hi Markus,
    I've introduce the following information:
    > MOUNT POINT 07 = S:\export\Data\CDLAN2
    > MOUNT POINT 01 = S:\export\Data\KN_WINDOWS_X86_64_AUPG
    > MOUNT POINT 06 = S:\export\Data\CDLAN1
    > MOUNT POINT 05 = S:\export\Data\CD3
    > MOUNT POINT 03 = S:\export\Data\CD1
    > MOUNT POINT 08 = S:\export\Data\UMN_WINDOWS_X86_64
    > MOUNT POINT 02 = S:\export\Data\KN_WINDOWS_X86_64
    > MOUNT POINT 04 = S:\export\Data\CD2
    And in mount point 06/07 we have the languages.
    The content of the trace file is:
    here's the complete trace:
    2007/07/05 16:35:01 *****************************
    2007/07/05 16:35:01 Checking directories ...
    2007/07/05 16:35:01 Searching for Data Carrier labeled AOXUPGR
    Adding path: S:\export\Data\KN_WINDOWS_X86_64_AUPG
    2007/07/05 16:35:01 Working on S:\export\Data\KN_WINDOWS_X86_64_AUPG ... no matching label
    Adding path: S:\export\Data\KN_WINDOWS_X86_64
    2007/07/05 16:35:01 Working on S:\export\Data\KN_WINDOWS_X86_64 ... no matching label
    Adding path: S:\export\Data\CD1
    2007/07/05 16:35:01 Resolving directory structure below S:\export\Data\CD1
    Adding path: S:\export\Data\CD1\UPG1
    Adding path: S:\export\Data\CD1\UPG2
    Adding path: S:\export\Data\CD1\UPG3
    Adding path: S:\export\Data\CD1\UPG4
    Adding path: S:\export\Data\CD1\UPG5
    Adding path: S:\export\Data\CD1\UPG6
    2007/07/05 16:35:01 Directory structure below S:\export\Data\CD1 resolved
    2007/07/05 16:35:01 Working on S:\export\Data\CD1 ... no matching label
    2007/07/05 16:35:01 Working on S:\export\Data\CD1\UPG1 ... no matching label
    2007/07/05 16:35:01 Working on S:\export\Data\CD1\UPG2 ... no matching label
    2007/07/05 16:35:01 Working on S:\export\Data\CD1\UPG3 ... no matching label
    2007/07/05 16:35:01 Working on S:\export\Data\CD1\UPG4 ... no matching label
    2007/07/05 16:35:01 Working on S:\export\Data\CD1\UPG5 ... no matching label
    2007/07/05 16:35:01 Working on S:\export\Data\CD1\UPG6 ... no matching label
    Adding path: S:\export\Data\CD2
    2007/07/05 16:35:01 Resolving directory structure below S:\export\Data\CD2
    Adding path: S:\export\Data\CD2\UPG7
    Adding path: S:\export\Data\CD2\UPG8
    Adding path: S:\export\Data\CD2\UPG9
    Adding path: S:\export\Data\CD2\UPG10
    Adding path: S:\export\Data\CD2\UPG11
    Adding path: S:\export\Data\CD2\UPG12
    2007/07/05 16:35:01 Directory structure below S:\export\Data\CD2 resolved
    2007/07/05 16:35:01 Working on S:\export\Data\CD2 ... no matching label
    2007/07/05 16:35:01 Working on S:\export\Data\CD2\UPG7 ... no matching label
    2007/07/05 16:35:01 Working on S:\export\Data\CD2\UPG8 ... no matching label
    2007/07/05 16:35:01 Working on S:\export\Data\CD2\UPG9 ... no matching label
    2007/07/05 16:35:01 Working on S:\export\Data\CD2\UPG10 ... no matching label
    2007/07/05 16:35:01 Working on S:\export\Data\CD2\UPG11 ... no matching label
    2007/07/05 16:35:01 Working on S:\export\Data\CD2\UPG12 ... no matching label
    Adding path: S:\export\Data\CD3
    2007/07/05 16:35:01 Resolving directory structure below S:\export\Data\CD3
    Adding path: S:\export\Data\CD3\UPG13
    Adding path: S:\export\Data\CD3\UPG14
    Adding path: S:\export\Data\CD3\UPG15
    Adding path: S:\export\Data\CD3\UPG16
    2007/07/05 16:35:01 Directory structure below S:\export\Data\CD3 resolved
    2007/07/05 16:35:01 Working on S:\export\Data\CD3 ... no matching label
    2007/07/05 16:35:01 Working on S:\export\Data\CD3\UPG13 ... no matching label
    2007/07/05 16:35:01 Working on S:\export\Data\CD3\UPG14 ... no matching label
    2007/07/05 16:35:01 Working on S:\export\Data\CD3\UPG15 ... no matching label
    2007/07/05 16:35:01 Working on S:\export\Data\CD3\UPG16 ... no matching label
    Adding path: S:\export\Data\CDLAN1
    2007/07/05 16:35:01 Resolving directory structure below S:\export\Data\CDLAN1
    Adding path: S:\export\Data\CDLAN1\LANG1
    Adding path: S:\export\Data\CDLAN1\LANG2
    Adding path: S:\export\Data\CDLAN1\LANG3
    Adding path: S:\export\Data\CDLAN1\LANG4
    2007/07/05 16:35:01 Directory structure below S:\export\Data\CDLAN1 resolved
    2007/07/05 16:35:01 Working on S:\export\Data\CDLAN1 ... no matching label
    2007/07/05 16:35:01 Working on S:\export\Data\CDLAN1\LANG1 ... no matching label
    2007/07/05 16:35:01 Working on S:\export\Data\CDLAN1\LANG2 ... no matching label
    2007/07/05 16:35:01 Working on S:\export\Data\CDLAN1\LANG3 ... no matching label
    2007/07/05 16:35:01 Working on S:\export\Data\CDLAN1\LANG4 ... no matching label
    Adding path: S:\export\Data\CDLAN2
    2007/07/05 16:35:01 Resolving directory structure below S:\export\Data\CDLAN2
    Adding path: S:\export\Data\CDLAN2\LANG5
    Adding path: S:\export\Data\CDLAN2\LANG6
    2007/07/05 16:35:01 Directory structure below S:\export\Data\CDLAN2 resolved
    2007/07/05 16:35:01 Working on S:\export\Data\CDLAN2 ... no matching label
    2007/07/05 16:35:01 Working on S:\export\Data\CDLAN2\LANG5 ... no matching label
    2007/07/05 16:35:01 Working on S:\export\Data\CDLAN2\LANG6 ... no matching label
    Adding path: S:\export\Data\UMN_WINDOWS_X86_64
    2007/07/05 16:35:01 Working on S:\export\Data\UMN_WINDOWS_X86_64 ... no matching label
    Regards,
    A.Kamel

  • SAP BW upgrade problem in phase lang_select

    Hello everybody,
    during our upgrade from SAP BW 3.0B to 3.5 a problem occurred in the phase “lang_select” running PREPARE. Unfortunately we did not find any up-to-date SAP note on this, except  in the note (212481), where the symptom is descried quite well, but the solution does not fit. By the way, the folder-names are already in upper-case (a different note told to do so). So I would be glad if anybody who does have any experience with upgrading from 3.0B could take a look at our problem as described below.
    <u>First of all our system information:</u>
    SAP Kernel 640 PL 115
    OS: IBM AIX 5.2.0
    DB: DB2 V8 FP 10
    actual release of SAP BW: 3.0B
    target release of SAP BW: 3.5 SR1
    R3trans: 6.13 (release 640)
    Tp: 340.16.12 (release 640)
    <u>Problem: PREPARE, phase lang_select</u>
    >> 08:56:19  PREPARE: START OF PHASE LANG_SELECT
    working on /software/51030722/LANG1 ...
    working on /software/51030722/LANG2 ...
    working on /software/51030722/LANG3 ...
    The following language(s) could not be updated yet:
    - German       for component PI_BASIS
    - German       for component SAP_ABA
    - German       for component SAP_BASIS
    - German       for component SAP_BW
    - English      for component PI_BASIS
    - English      for component SAP_ABA
    - English      for component SAP_BASIS
    - English      for component SAP_BW
    Please mount another Language Disk for these language(s).
    You need at least CDs which satisfy the vector "DE"
    (standard languages) for all components.
    It is not allowed to omit this update.
    <u>What we did until the message comes up:</u>
    - all by SAP recommended preparations on the OS, the DB and SAP BW 3.0B have been successfully implemented (as described in Component Upgrade Guide SAP BW 3.5 SR1)
    - we copied all the data from CD/DVD into directories on the server
    - we copied the fix FIX_WEBAS640SR1.SAR into “/usr/sap/put/”, which is required by PREPARE later on (SAP note 663240)
    - start of PREPARE on the command-line (the directory “/usr/sap/put/” is now filled with files and subdirectories are created)
    - overwriting R3trans and Tp with the newest versions (as mentioned at the beginning)
    - executing UaServer on the AIX, accessing the tool via web browser from a client
    - in the applet we start PREPARE
    - making entries for PREPARE
    - lang_select
    We did also examine the logs, here is what they say:
    <b>R3upchk.log</b>
    UPGRADEPHASE LANG_SELECT
    ...started at 20060308085619
    Phase log file: 'LANGSEL.LOG'
    Condition         #if 1 >= 0
    is evaluated as a TRUE expression, total status is TRUE, stack level 1
    ...begin dialogue at 20060308085623
    <b>Langsel.log</b>
    1 ETQ201XEntering upgrade-phase "LANG_SELECT" ("20060308085619")
    2 ETQ367 Connect variables are set for standard instance access
    4 ETQ399 System-nr = '10', GwService = 'sapgw10'
    4 ETQ399 Environment variables:
    4 ETQ399   dbs_db6_schema=SAP1
    4 ETQ399   auth_shadow_upgrade=0
    4 ETQ380 computing toolpath for request "TP_LANG_SELECT"
    4 ETQ381 request "TP_LANG_SELECT" means "create cofile in phase TP_LANG_SELECT"
    4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"
    4 ETQ383 translates to path "exe"
    4 ETQ383 translates to path "exe"
    4 ETG880 Language data requested for "" (without standard languages "DE")
    4 ETQ359 RFC Login to: System="1", Nr="10", GwHost="sap1", GwService="sapgw10"
    4 ETQ232 RFC Login succeeded
    <b>cdtrace.log</b>
    2006/03/08 08:56:19 Searching for Data Carrier labeled LANGUAGE
                        Adding path: /software/51030783
    2006/03/08 08:56:19 Resolving directory structure below /software/51030783
                        Adding path: /software/51030783/UM1
                        Adding path: /software/51030783/UM2
    2006/03/08 08:56:19 Directory structure below /software/51030783 resolved
    2006/03/08 08:56:19 Working on /software/51030783 ... no matching label
    2006/03/08 08:56:19 Working on /software/51030783/UM1 ... no matching label
    2006/03/08 08:56:19 Working on /software/51030783/UM2 ... no matching label
                        Adding path: /software/51030777
    2006/03/08 08:56:19 Resolving directory structure below /software/51030777
                        Adding path: /software/51030777/UPG1
                        Adding path: /software/51030777/UPG2
                        Adding path: /software/51030777/UPG3
    2006/03/08 08:56:19 Directory structure below /software/51030777 resolved
    2006/03/08 08:56:19 Working on /software/51030777 ... no matching label
    2006/03/08 08:56:19 Working on /software/51030777/UPG1 ... no matching label
    2006/03/08 08:56:19 Working on /software/51030777/UPG2 ... no matching label
    2006/03/08 08:56:19 Working on /software/51030777/UPG3 ... no matching label
                        Adding path: /software/51030630
    2006/03/08 08:56:19 Working on /software/51030630 ... no matching label
                        Adding path: /software/51030722
    2006/03/08 08:56:19 Resolving directory structure below /software/51030722
                        Adding path: /software/51030722/LANG1
                        Adding path: /software/51030722/LANG2
                        Adding path: /software/51030722/LANG3
    2006/03/08 08:56:19 Directory structure below /software/51030722 resolved
    2006/03/08 08:56:19 Working on /software/51030722 ... no matching label
    2006/03/08 08:56:19 Working on /software/51030722/LANG1 ... matches -> added to result list.
    2006/03/08 08:56:19 Working on /software/51030722/LANG2 ... matches -> added to result list.
    2006/03/08 08:56:19 Working on /software/51030722/LANG3 ... matches -> added to result list.
                        Adding path: /software/51030769
    2006/03/08 08:56:19 Resolving directory structure below /software/51030769
                        Adding path: /software/51030769/K01
                        Adding path: /software/51030769/K02
                        Adding path: /software/51030769/K03
                        Adding path: /software/51030769/K04
                        Adding path: /software/51030769/K05
                        Adding path: /software/51030769/K06
                        Adding path: /software/51030769/K07
                        Adding path: /software/51030769/K08
    2006/03/08 08:56:19 Directory structure below /software/51030769 resolved
    2006/03/08 08:56:19 Working on /software/51030769 ... no matching label
    2006/03/08 08:56:19 Working on /software/51030769/K01 ... no matching label
    2006/03/08 08:56:19 Working on /software/51030769/K02 ... no matching label
    2006/03/08 08:56:19 Working on /software/51030769/K03 ... no matching label
    2006/03/08 08:56:19 Working on /software/51030769/K04 ... no matching label
    2006/03/08 08:56:19 Working on /software/51030769/K05 ... no matching label
    2006/03/08 08:56:19 Working on /software/51030769/K06 ... no matching label
    2006/03/08 08:56:19 Working on /software/51030769/K07 ... no matching label
    2006/03/08 08:56:19 Working on /software/51030769/K08 ... no matching label
                        Adding path: /software/51030865
    2006/03/08 08:56:19 Working on /software/51030865 ... no matching label
    Well, we actually do not know what the problem is. It seems to us that the program is not able to identify the language source files. The point is why did the source-paths for the other data work, as we copied the CD/DVD-data into folders? What is different with the language-CD?
    Thanks a lot for your help,
    Peter

    I had the same problem but for upgrading SAP SOLUTION MANAGER 3.2 to 4.0 in the PREPARE PHASE "LANG_SELECT"
    In the PEVALLAN.<SAPSID> ,I realized that the path for the required DVD I entered was too long !!
    My real path was "C:\SAP_CDS\Upgrade_SOL4\51031485\51031485_1\SAP_CRM_LNG"
    and the PEVALLAN FILE in the IV_LANGDIR parameter it was
    ""C:\SAP_CDS\Upgrade_SOL4\51031485\51031485_1\SAP_CR"
    I've just shortened the path and it works now.
    This surprised me because from the beginning of the PREPARE phase, I had no problems with that kind of thing.

  • Upgrade to BI 70 - OS400/DB2 - Not able to proceed

    Hello
    I am in the process to upgrade our 3.5 environment and am running prepare as the first step. Its getting stuck and am not able to proceed further. Any help in this regard would definitely be appreciated. Please find the error log from CHECKS.LOG file:
    #=======================================================================
    #Starting new execution of PREPARE modules
         Parameter input
         Initialization
         Import
         Extension
         Integration
         Installation
         General checks
         Activation checks
         Necessary checks for conversions
         Optional checks for conversions
         Modification support
         Pre-processing
    at 20081016083015.
    #=======================================================================
    #=====================================================#
    Requests and information for module Parameter input #
    #=====================================================#
    #===============================================================#
    PREPARE module Parameter input finished with status succeeded #
    #===============================================================#
    #====================================================#
    Requests and information for module Initialization #
    #====================================================#
    INFO:    The version check of the R3trans in your active SAP kernel determined that it has a sufficient level.
    No update of R3trans is necessary.
    INFO:    The version check of the disp+work in your active SAP kernel determined that it has a sufficient level.
    No update of disp+work is necessary.
    INFO:    The version check of the tp in your active SAP kernel     determined that it has a sufficient level.
    No update of tp is necessary.
    ERROR:   The executable R3trans in /usr/sap/put/exe is too old.
    It needs a release date of 15.01.08 or later.
    Please proceed as described in note 19466.
    ERROR: The new SAP tools in /usr/sap/put/exe cannot connect to your database.
    Possible reasons are:
            - Environment variables are not properly set for the version of the database client which is used by the new tools.
            - Required database libraries are not accessible or cannot be found neither through a compiled-in path nor through explicit search via the shared library path.
            - Auxiliary files such as language files etc. are not compatible with this version of the database client.
    Please check database / OS specific upgrade notes for more help.
    The log file /usr/sap/put/log/DBCONNCHK.LOG contains more details about the failure.
    INFO:       The upgrade strategy for the addon BI_CONT is described in note: 1000822
    INFO:       The upgrade strategy for the addon PI_BASIS is described in note: 555060
    INFO:       The upgrade strategy for the addon SAP_BW is described in note: 632429
    #===========================================================#
    PREPARE module Initialization finished with status failed #
    #===========================================================#
    #===================================================================
    Execution of selected PREPARE modules finished but
    PREPARE modules
          Import
          Extension
          Integration
          Installation
          General checks
          Activation checks
          Necessary checks for conversions
          Optional checks for conversions
          Modification support
          Pre-processing
    could not be executed because their predecessors were not executed # successfully. Correct the errors and select the predecessors again.
    #====================================================================
    Any idea how to fix this error or how to proceed further?
    EmJay

    Any suggestions. Hard deadline and not able to proceed.
    Any help would be appreciated.
    Thanks

  • 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

  • TP version problem during upgrade from 4.7 sr2 to ECC6

    Hello All,
    i am doing an upgrade from 4.7 to ECC6 (ultimately i have to upgrade to EHP4). I am stuck in phase PREPARE module Initialization finished with status failed #. Below is the error i am getting. before pasting log file i tried my best to uprade TP level by upgrading the Patch level. but its not taking effact in to SAP system. If i check TP version in STMS >> system >> Check TP tool it shows me old version.
    below is the error log excerpt from file CHECKS.LOG
       #====================================================#
    Requests and information for module Initialization #
       #====================================================#
    ERROR:   The upgrade needs a patched version of R3trans which is
             build on 21.06.06 or later.
             The R3trans in your active SAP kernel is either older or
             the version could not be determined. Call it without
             any option to determine the build date.
             If the build date is too old, you have to replace it
             before you can continue the upgrade.
             Download the latest executable available from the SAP service
             market place and update it before you continue.
             Otherwise, the upgrade tools will be corrupted.
    INFO:    The version check of the disp+work in your active SAP kernel
            determined that it has a sufficient level.
             No update of disp+work is necessary.
    ERROR:   The upgrade needs a patched version of tp with version
             number 340.16.05 or higher.
             The tp in your active SAP kernel is either older or the
             version could not be determined. Call it without any option
             to determine the version.
             If the version is too old, you have to replace it before
             you can continue the upgrade.
             Download the latest executable available from the SAP service
             market place and update it before you continue.
             Otherwise, the upgrade tools will be corrupted.
    ERROR: To be able to use ASU Toolbox, your system requires
           the ST-PI software component with at least Support Package Level 8
          After the update is done, the module must be repeated!
           For more information, see the upgrade documentation
    INFO:       The upgrade strategy for the addon ABA_PLUS
                is described in note: 632429
    INFO:       The upgrade strategy for the addon APPINT
                is described in note: 632429
    INFO:       The upgrade strategy for the addon BP-R3PF
                is described in note: 632429
    INFO:       The upgrade strategy for the addon FINBASIS
                is described in note: 438521
    INFO:       The upgrade strategy for the addon LSO
                is described in note: 503468
    INFO:       The upgrade strategy for the addon LSOFE
                is described in note: 503907
    INFO:       The upgrade strategy for the addon PI
                is described in note: 700779
    INFO:       The upgrade strategy for the addon PI_BASIS
                is described in note: 555060
    INFO:       The upgrade strategy for the addon SLL_PI
                is described in note: 1306751
    INFO:       The upgrade strategy for the addon ST-A/PI
                is described in note: 69455
    INFO:       The upgrade strategy for the addon ST-PI
                is described in note: 539977
    INFO:       The upgrade strategy for the addon WP-PI
                is described in note: 632429
       #===========================================================#
    PREPARE module Initialization finished with status failed #
       #===========================================================#
    i downloaded the 47 kernel files SAPEXEDB_304-20001172.SAR and SAPEXE_304-20001172.SAR and installed the kernel file. if i check TP version from command level it shows me 340.16.62, but in SAP STMS it shows me 340.16.03. Can somebody explain what shoulkd i do?
    Can i know also if i can update SAP Kernel from 4.7 sr2 to NW7.0 without upgrading even started?
    If somebody can tell me the exact number of CDs to use to upgrade from 4.7 SR2 to ECC6 EHp4, that would be very
    nice.
    Mani

    Hi Mani,
    ERROR: The upgrade needs a patched version of R3trans which is
    build on 21.06.06 or later.
    ERROR: The upgrade needs a patched version of tp with version
    number 340.16.05 or higher.
    show that the tp and R3trans used by the source 470 system are old.
    You should download the latest tp and R3trans for kernel 470, and
    replace the old tp and R3trans with the downloaded ones under the 470 kernel directory. The 470 kernel directory is specified by parameter DIR_EXECUTABLE which is usually /usr/sap/<SID>/SYS/exe/run.
    Please note that there is also a kernel directory under /<DIR_PUT>/<SID>/SYS/exe which is for the the target system 700. Please do not replace tp and R3trans under this directory with the ones downloaded for kernel 470.
    NO, you cannot update SAP Kernel from 4.7 sr2 to NW7.0 without upgrading even started. Kernel upgrade will be done by SAPup automatically.
    With Best Regards
    Julia

  • Problem to change ST-A/PI to 01K_ECC600  during Prepare to upgrade  ERP60

    I tried to upgrade ERP2004 to ERP6.0. During in Prepare Phase, it prompt with below screen :
    Product update and media decision overview:
    Decide about update type and the Add On media kind.
    Select the Add-on you want to make or change a decision:
    Select no product, if you are finished.
             Add-on Id    Start Rel         Dest Rel       Status                             Note
    01)     EA-IPPE    300                 400              INST/UPG WITH STD CD  632429
    02)     PI_BASIS   2005_1_640    2005_1_700  INST/UPG WITH STD CD  555060
    03)     ST-PI         2005_1_640    2005_1_700   INST/UPG WITH STD CD  539977
    04)     P3A          V500               V600            UPG WITH SAINT PACK   1162521
    05)  X  ST-A/PI     01K_ECC500    ?               UNDECIDED                      69455
    I tried to change ST-A/PI to 01K_ECC600 with 'UPG SAINT' and I already unzipped the related file for  ST-A/PI  01K_ECC600 to  \usr\sap\trans. But it returned with "No matching SAINT package for 'ST-A/PI' found.".
    Pls advise.
    Thanks.
    Edward TSo

    Hi,
    You have to uncar the add-on in /usr/sap/trans/EPS/in directory.
    Keep your add-on sar/car file in /usr/sap/trans folder and use following command
    cd /usr/sap/trans
    SAPCAR -xvf xxxxxxxx.sar
    it will automatically unzip the files in /usr/sap/trans/EPS/in directory.
    Regards,
    Sachin Rane.

  • BW upgrade from 3.1 to 3.5

    Hello,
    We are planning to upgrade BW from the current version 3.1 to 3.5.
    The system component information is as follows:
    SAP_BASIS     620     0056     SAPKB62056
    SAP_ABA                     620     0056     SAPKA62056
    SAP_BW                     310     0017     SAPKW31017
    PI_BASIS                2003_1_620     0007     SAPKIPYH57
    BI_CONT                     310     0015     SAPKIBIAQ5
    Kernel : 620 patch level 1270.
    Can anyone tell if there is a need to upgrade the kernel or patch level of any of the components  mentioned above, prior to the upgrade?
    Regards,
    Sumit

    hi Sudesh,
    pls refer the following link.It has got all the useful links for BI
    /people/sap.user72/blog/2006/02/11/sap-netweaver-2004s--where-is-it-really-documented
    hope it helps,
    regards,
    Parth.

Maybe you are looking for

  • Assigning roles to users by code without SecurityAdministration permission

    Hello! I'm a begginer working with VS Lightswitch and all the ASP.NET stuff.  Here is my problem: I have an application where users follow a certain hierarchy: we have employees, Area Managers, Department Managers, ... When creating a new employee he

  • How to crop a video in Premiere Elements 13?

    How do I crop a video in Premiere Elements 13?  I see 'pan and zoom.'   And, it retains the aspect ratio automatically, but I don't always need the 'pan' or the 'zoom' -- just want a tight shot on an actresses' sunglasses, which reflect something she

  • Bridge Keywords Dupliacte Problem.

    What are the Italicized duplicate keywords in Bridge and How do I get rid of them permanently? I'm using Design Premium CS5 with all the updates on windows 7 64bit. In the keyword panel, I have the same keyword in several places in the hierarchy. The

  • Photostream/Cameraroll Photos not showing up on iPhone 4S

    I have been taking photos from lock screen (home button twice, photo icon on screen, plus volume button), and the photos are not showing up in Camera Roll on the iphone 4s. They show up in Photostream on mac, but not on the phone its self. Help, Idea

  • Decimal Factors in Internal Order Report S_ALR_87012993

    Hi, I need to add the decimal factor in the report to view the 2 digits after .full stop.I am able to do it in my User id.But how can i activate this for all users in the client place. Kindly advice me.. Thanks Supriya