ECC-600 EHP4 upgrade with VIRSAHR 520 700 - PREP_EXTENSION/ADDON_QCALC

Hi
We are getting following error at phase PREP_EXTENSION/ADDON_QCALC in the ECC 6.0 upgrade:
3 ETN256 You want to install the following add-on components:
3 ETN248 Component: "VIRSAHR" rel. "520_700", Support Package
level: "0" (component type "A")
3 ETN248 Component: "VIRSANH" rel. "520_700", Support Package
level: "0" (component type "A")
2 ETN085X"2. Adding Add-on Installation Queue" " " " " " "
3 ETN262 Calculating queue part for add-on "VIRSAHR" rel. "520_700"
3 ETN490 Use the Add-On installation package "SAPK-523EXINVIRSAHR"
(type &4"AOX") for Add-On &2"VIRSAHR" rel.&3"520_700"
3 ETN245 The following import prerequisites of OCS Package "SAPK-
523EXINVIRSAHR" have not been met:
3 ETN264 In the (alternatively) Requirement set "01":
3WETN491 Required software component "SAP_HR" rel."600" is not installed2WETN543 OCS package "SAPK-523EXINVIRSAHR" does not match the current
software component vector
1 ETN214X."**************************************************"
We have alreacy checked note 1002147, which clearly states that we have to include SAPK-523EXINVIRSAHR in the upgrade. SAP_HR is part of the upgrade.
We have included SAP_HR and other Support Package as per the queue generated by Solution Manager, but we did not include VIRSAHR & VIRSANH Packages until we got to this phase. We then included these support packages in eps\in directory, but we are now getting this error now.
Any ideas?
Regards
Chandu

Hi
This is what the solution provided by SAP Support:
Quote:
we have finally found the problem, it's a bug in the package upload
functionality used by the upgrade. The consequence of this bug is that
Support Packages whose EPS files (.PAT files) have a certain string in
the name, namely the string 0000000 after the _ and before .PAT
extension, are not properly uploaded to the ABAP system and hence are
not visible or known to the upgrade.
This bug will be fixed in the next upgrade tool fix, but in the meantimeyou can use the following workaround:
Check your EPS/in directory after the CAR/SAR Archives of the SPs are
extracted and rename all .PAT and .ATT files, which have a name like
*_0000000.PAT (or *_0000000.ATT), by changing the string 0000000 to
9000000. For example, for the VIRSANH SP SAPK-52302INVIRSANH rename the
file VS30020106486_0000000.PAT to VS30020106486_9000000.PAT
Afterwards, the upgrade will upload the informations about the SP
properly and the SP can be included into the upgrade.
Files:
31/01/2007 07:32 329 VS30020106486_0000000.ATT
31/01/2007 07:32 554,073 VS30020106486_0000000.PAT
If these two files are renamed to e.g.
VS30020106486_9000000.ATT
VS30020106486_9000000.PAT
the affected VIRSANH SP2 is uploaded correctly by the upgrade
functionality and the SP inclusion of the VIRSANH SPs works.
Sorry, as of now I cannot promise you a date when the tool fix will be
available. I have found this bug only today in the evening (german time)and will discuss this with the responsible colleagues tomorrow.
Afterwards, I will know more...
Unquote:
Hope this helps. We have decided against upgrading to 530_700 as it will involve upgrading GRC system and also new version has lot of new functionalities, which we like explore it after the ECC upgrade.
Also, I would not suggest deleting VIRSAHR as all the config and customising done for VIRSAHR will be lost.
Regards
Chandu
Edited by: Chandu Cheeti on Jan 17, 2010 11:19 AM

Similar Messages

  • Execution of Reports phase error during SAP EHP4 upgrade with EHPi

    I started getting an error message in the "Execution of reports after put" phase
    (within the Downtime phase) during the SAP EHP4 upgrade with Enhancement
    Package Installer.
    ***** LIST OF ERRORS
    AND RETURN CODES *****
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~XPRA ERRORS and RETURN CODE in SAPRB70104.OPQ
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~1AETR012XProgram terminated (job: "RDDEXECL", no.: "09064300") Long
    text: Cause Program "&V#&", which was started in the background, was
    terminated abnormally. System Response The system created a job log for
    the terminated program. What to do Proceed as follows: Log onto the
    system in which the program was executed. The system is specified at the
    beginning of the transport log. Then call transaction SM37 to display the
    job log. Enter "&V#&" as job name and "DDIC" as user name. Restrict the
    starting date to the starting date specified in the transport log. For
    the other selection criteria, select only jobs with the status
    "cancelled". Then press <LS>Execute</>. A list of the jobs satisfying the
    selection criteria is displayed. You can display the log by pressing
    <LS>Job log</>. If the list contains several jobs, you can select the job
    with the ID " &V#&" with <LS>Display</> -> <LS>Job details</> or define
    further details for the selection criteria in the initial screen of
    transaction SM37. If the ABAP processor reports cancellation,
    double-clicking on the corresponding message in the job log branches to
    the display of the corresponding short dump. 1AEPU320 See job
    log"RDDEXECL""09064300""OPQ" 1 ETP111 exit code : "12" >>> PLEASE READTHE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<< XPRAs are
    application reports that run at the end of an upgrade.
    Most XPRA reportshave a report documentation that explains what the report does and how
    errors can be corrected. Call transaction se38 in the SAP system, enter
    the report name, select 'Documentation' and click the 'Display' button.
    >>> The problematic XPRAs are mentioned in messages of type PU132 above
    <<<
    I tried to follow the instructions in note 1269960, but the enhancement spot
    CLASSIFICATION_TOOL was already active. I activated it again and reran the phase
    but got the same error. Also, I couldn't implement the note using SNOTE because it is
    the middle of the upgrade process.
    I also found the following long text in ST22
    "Internal error during syntax check: ("//bas/710_REL/src/krn/gen/scsymb.c#11"
    Processing had to be terminated because an internal error
    occurred when generating the ABAP/4 program
    "CL_CLS_BADI_CHARACTERIZATION==CP".
    The internal system error cannot be fixed by ABAP means only."
    I am on a 64 bit System with CentOS Linux. 8 GB RAM, 250 GB HD with 20 GB free space.
    So far, I could not find any information on this. Any help would be greatly appreciated!
    Thanks,
    Victor

    Hi Victor,
    Go to SM37 and put in the username as DDIC and see the job log.
    Also check  Sm50 and see whether you have BTC processes available.
    Last but not the least check your filesystem space  usage too.
    Gerard

  • ACLDL, Vistex Vendor Keys - Invalid from 46C to ECC 6 (EHP4) upgrade

    HI
    We are upgrading our system from 4.6C to ECC6 (EHP4) directly using
    CUUC approach.
    In the IS_SELECT phase we have got three add-ons
    ACLDL
    IRMGLB
    IRMIPM
    The note 632429 is mentioned to be referred to get the vendor keys.
    But there is no vendor key for the above three addons mentioned.
    I have referred the note 1069063 - Vistex IP Module Upgrade Guidelines.
    It has given three keys
    Target version
    " ECC60                  3406956 1295006
      ECC60 w/ EhP            See below, depends on SAP_BASIS release
    For ECC60 w/ EHP only, if your system is on SAP_BASIS release 700 when starting the update with SAPehpi, then use these keys:
            IRMGLB = 1408873 IRMIPM = 1131158
    For ECC60 w/ EHP only, if your system is already on SAP_BASIS release 701 when starting the update with SAPehpi, then use these keys:
            IRMGLB = 1103857 IRMIPM = 1162672
    I tried all the above three keys, but all are invalid.
    Can anyone help us to provide the valid vendor keys for
    ACLDL (source version - 400)
    IRMGLB (source version - 30B)
    IRMIPM (source version - 30B)
    Thanks & Regards
    Senthil

    Hi ,  we are doing upgrade from R/3 4.6 c to ERP6.0 with EHP4 -SP08.
    during sandbox , I have removed ACCL component and continue the upgrade. I have created OSS messgae and they said check with your ACC vendor team.
    As of now I don't received any issues either development team during UT/IT. ( Integration Testing is going on)
    We are planing to do mock upgrades and let me know if you have any data loss or any issues during testing without ACCDL component.
    Finally , I check with customer and they said we are not using any more ....
    Please advice if any thing is missing ! Appreciate your help.
    Regards,
    Hari

  • ECC 6.0 UPGRADE WITH AFS 6.0

    Hi ,
       We try to upgrade our R/3 Server to ECC 6.0 , The Upgrade was successfully completed . But iam not able to install the IS ADDON AFS 6.0 after the upgrade . The error shows the ECC DIMP has not to be installed .
    Kindly tell me solution for this problem , It is possible to include AFS 6.0 during the upgrade phase , if it is possible , kindly tell me the steps .
    Or tell me the solution for this problem .
    Regards
    PalaniSelvan

    As I replied in your other three or four threads with almost the same question:
    It's not enough to just try to import AFS, you have to import the corresponding CRTs as mentioned in
    Note 1029517 - SAP AFS V600 : CRTs and Support Packages
    Markus

  • 4.6C to ECC 6.0 Upgrade with EP 6.0

    HI
    We are planning to upgrade from 4.6C to ECC 6.0 . We have the Following as of now
    SAP ITS 6.2 standalone.
    ESS/MSS Business Packages for 4.6C
    SAP EP 6.0
    I understand that
    a) Migrating to Integrated ITS is a must
    b) EP 6.0 works with SAP ECC 6.0 as a product
    Now my question is
    a) It is required to Upgrade EP 6.0 to EP 7.0 . Is this Mandotary?
    b) What happens to ESS/MSS Business packages in the Upgraded ECC 6.0 System, Does this need any adjustments and can still work with SAP EP 6.0?
    Regards
    Deepak

    Hello there,
    I assume you mean Enterprise Portal. The general recommendation is that the portal must be based upon an equivalent or newer Netweaver version than the backend system. As the backend is going to be upgraded to a Netweaver 7  based released, EP 7 would be preferrable to staying with EP 6.
    EP 6 would work, but the colleagues from EP support told me EP 7 would be recommended.
    Best regards,
    Miguel Ariñ

  • ECC 6.0 UPGRADE - BW 3.10

    We are planning to upgrade our source system from 4.6C to ECC 6.0.  We are on BW 3.10 ( But planning to upgrade to BI 7.0 once after ECC 6.0 upgrade)
    Would like to know,
    1. Do we need apply any plug-in requirements to accommodate the ECC 6.0 compatibility?
    2. Will the existing BW 3.10 work without any issue with ECC 6.0?
    ( We are not going to do any change with new Business content available with ECC 6.0)
    3. What are the other precautions, we need to take in order to work BW 3.10 with ECC 6.0?
    Advance Thanks.

    refer replies here:
    Re: ECC 6.0 Upgrade with BW 3.5

  • Smart form Addon after Upgrade to ECC 6 EHP4

    Hi,
    I have succesfully upgraded my system from R/3 4.7 EXT 1 to ECC 6 EHP4.
    During upgrade i had to delete Pre configured smart forms Addon ( According to note 572392 ) .
    Since we are on EHP4 and no smart forms configured we are not able to print.
    The latest pre configured smart form addon ( Best Practice all in one)  available is for EHP3.
    Please let me how to proceed with this situation as there may be other compaines who are on EHP4 and use pre configured smart forms.
    Appreciate your help.
    Thanks,
    FBK

    If you have old system copy try to copy forms into the new.
    Kind regards,
    Mirek

  • EHP4 upgrade from ECC 6.0

    Hi experts,
    We are planning to upgrade to EHP4 from ECC6.0
    We have the following systems installed on non-unicode,
    SAP ECC 6.0
    SAP NETWEAVER 7.0
    SAP SRM 3.0
    Currently, we have customized ESS java webdynpro on our ESS portal, with the EHP4 upgrade and EHP1 on SAP Netweaver 7.0, would there be any implications to the customized ESS iviews ?
    Our ECC 6.0 is on a non-unicode system, is it advisable to take this opportunity to convert to a unicode for scalability aspect ?
    what would be the implications if we remains as non-unicode after EHP4 upgrade ?
    All advices are appreciated !!
    Thanks in advance

    Hi,
    You can find all the relevant information at the below link,
    https://service.sap.com/erp-ehp
    Regards,
    Vishnu

  • SAP ECC 6.0 EHP4 Compatible with MDSD 3.0?

    Hi Folks,
    Is SAP ECC 6.0 EHP4 compatible with MDSD 3.0? I have read the documentation but its not clear for me if this would be possible.
    It says that MDSD 3.0 is compatible with SAP ECC 6.0 EHP3, but i would like to know if compatible with EHP4.
    Thanks for your help.
    Regards,
    Gilberto Li

    Hi Gilberto,
    yes, this should work fine. We just have one client who did the upgrade and he has not experienced issues up to now - even he is still in testing phase.
    Regards,
    Oliver

  • 46C- ECC6 upgrade with EHP4 SAP_BASIS package not found

    We are executing an upgrade from 46C to ECC6 SR3 and binding in EHP4.
    We have successfully downloaded EHP4 using Solution Manager MOPZ and
    provided the generated "XML" file during the PREPARE.
    During the phase EHP_INCLUSION, PREPARE is stopping with a message "No
    matching SAINT package for 'SAP_BASIS' found".
    The KB70102.SAR and KB70103.SAR packages from EHP4 have definitely been unpacked
    and are available in /usr/sap/trans/EPS/in and we have prompted PREPARE to search EPS/in but it just returns to the previous error after searching.
    It appears from the logs that the upgrade is expecting a "SAINT"
    install package for SAP_BASIS and does not consider the KB70102/3
    patches as acceptable?
    Any clues as to why PREPARE is not accepting the SAP_BASIS packages and looking for a SAINT install?
    Below is an excerpt from the EHP_INCLUSION.LOG
    2 ETQ732 Package descriptions uploaded successfully
    4 ETQ399 Looking for SAINT package for 'SAP_BASIS' ...
    4 ETQ399 ... Read uploaded packages calling function module:
    4 ETQ399      current: name = 'SAP_BASIS', release = '700'
    4 ETQ399      patch type = 'U', ncvers-component = 'SAP_BASIS'
    4 ETQ399 R3upReadNewPackages:
    4 ETQ399   patchType='U', langVect='DEFS'
    4 ETQ359 RFC Login to: System="CB1", Nr="00", GwHost="dbusrcb1", GwService="sapgw00"
    4 ETQ232 RFC Login succeeded
    4 ETQ233 Calling function module "spda_read_new_packages" by RFC
    4 ETQ399   ismovesVersion='0'
    4 ETQ399 R3upReadNewPackages: exit: rc=0
    4 ETQ399 ... No matching package found.
    Regards,
    Mike Tarr

    Ok, I was able to download the K-701DHINSAPBASIS package from Service Marketplace and this resolved the SAP_BASIS problem.  Thank you Markus for this solution.
    I also downloaded the SAP_ABA, SAP_BW, and the PI_BASIS components and unpacked those as well in /usr/sap/trans/EPS/in.    My upgrade is now stuck asking for a SAINT package for SAP_ABA!  I'm sure the SAP_ABA install, K-701DHINSAPABA, is unpacked and available in /usr/sap/trans/EPS/in.
    The SAP_ABA files are definitely readable and there are entries in table PAT03_SDA for them.
    I have a ticket open with SAP support but they have not had a solution yet for the SAP_ABA
    Solution Manager failed to identify any of these packages as required in MOPZ.
    I'm starting to wonder if anybody has ever done a 4.6C to ECC6 upgrade with EHP4 bound before?
    Any ideas on the SAP_ABA would be appreciated.  Here's a section of the EHP_INCLUSION.LOG file from PREPARE.  
    4 ETQ399 R3upReadNewPackages: exit: rc=0
    4 ETQ399      Found: name = 'SAP_BASIS', release = '701', package = 'SAPK-701DHINSAPBASIS'
    4 ETQ399 ... Matching package found: 'SAP_BASIS','701','SAPK-701DHINSAPBASIS'
    4 ETQ399 (trc) R3upPatchDisassembleQueue: 1 package queue entries
    4 ETQ399 (trc) R3upPatchDisassembleQueue: force=NO
    4 ETQ399 (trc) R3upPatchDisassembleQueue: 0 packages will be disassembled
    4 ETQ399 ... ... INST/UPG SAINT decision ok
    4 ETQ399 ... EhP component SAP_ABA, 701
    4 ETQ399 Looking for SAINT package for 'SAP_ABA' ...
    4 ETQ399 ... Read uploaded packages calling function module:
    4 ETQ399      current: name = 'SAP_ABA', release = '700'
    4 ETQ399      patch type = 'U', ncvers-component = 'SAP_ABA'
    4 ETQ399 R3upReadNewPackages:
    4 ETQ399   patchType='U', langVect='DEFS'
    4 ETQ359 RFC Login to: System="CB1", Nr="00", GwHost="dbusrcb1", GwService="sapgw00"
    4 ETQ232 RFC Login succeeded
    4 ETQ233 Calling function module "spda_read_new_packages" by RFC
    4 ETQ399   ismovesVersion='0'
    4 ETQ399 R3upReadNewPackages: exit: rc=0
    4 ETQ399 ... No matching package found.
    4 ETQ010 Date & Time: 20090511150018

  • EHP4 upgrade on ECC 6.0

    Hi Experts,
    we are planning to install EHP4 on our ECC 6.0.
    We have other systems like
    SAP ECC 6.0
    SAP NETWEAVER 7.0
    SAP SCM 7.0
    SAP SRM 4.0
    As i have read that EHP4 upgrade requires SAP NETVEAWER 7.0 EHP1 upgrade. Does it means that if SAP ECC 6.0 is upgraded with EHP4 that SAP NETWEAVER 7.0 system should also have EHP1 ?
    Thanks in advance.
    regards
    Vishal

    HI
    Both possibilities are within reach.
    You can upgrade ECC 6.0 EHP4 on Sap Netweaver 7.01 or on Sap Netweaver 7.00.
    When you calcule queue in mopz (SOLUTION MANAGER) you can select your upgrade, both options are available.
    I recommend you do the upgrade on Sap Netweaver 7.01.
    more info:
    http://service.sap.com/instguides
    Regards
    William Neira

  • Query to calculate downtime while upgrading from ECC to EHP4

    Hi Folks,
    I am having below doubts for calculating downtime phase for ehp4 downtime.
    1.Do the end users will be able to work (In Production)  in pre-processing phase in EHP4 upgrade u2026?  (I think yes)
    2.How we will count the downtime  like from Preprocessing phase  to until System is up ? or we will count  from Downtime Phase. (I think from downtime phase)
    Regards,
    Sahil

    Hi,
    >
    > 1.Do the end users will be able to work (In Production)  in pre-processing phase in EHP4 upgrade u2026?  (I think yes)
    >
    Yes. Users will be able to work till pre-processing phase.
    > 2.How we will count the downtime  like from Preprocessing phase  to until System is up ? or we will count  from Downtime Phase. (I think from downtime phase)
    >
    There is no formula to calculate downtime as it depends upon number of factors like system resources (RAM &CPU), no. of R3load processes, no. of background processes, Parameters tuning etc.
    Do a test upgrade on your sandbox system (copy of production system) to get idea of downtime required.
    Thanks
    Sunny

  • EHP4 upgrade - win 32 bit

    Hello All,
    SAP is running om win 32 bit with oracle 10.2.0.5. pls check the below SP and kernel details .
    Can you pls advise any prechecks i have to perform before ehp4 upgrade as well sap note and sap standard document .
    Kernel release    700
    Compilation       NT 5.2 3790 Servic
    Sup.Pkg lvl.      353
    Database system      ORACLE
    Release              10.2.0.5.0
    Component version    SAP ECC 6.0
    Unicode System       Yes
    SAP_BASIS
    700
    0027
    SAPKB70027
    SAP Basis Component
    SAP_ABA
    700
    0027
    SAPKA70027
    Cross-Application Component
    PI_BASIS
    2006_1_700
    0017
    SAPKIPYM17
    Basis Plug-In (PI_BASIS) 2006_1_700
    ST-PI
    2005_1_700
    0006
    SAPKITLQI6
    SAP Solution Tools Plug-In
    SAP_BW
    700
    0029
    SAPKW70029
    SAP NetWeaver BI 7.0
    SAP_AP
    700
    0028
    SAPKNA7028
    SAP Application Platform
    SAP_APPL
    600
    0022
    SAPKH60022
    Logistics and Accounting
    SAP_HR
    600
    0086
    SAPKE60086
    Human Resources
    EA-IPPE
    400
    0022
    SAPKGPID22
    SAP iPPE
    EA-APPL
    600
    0022
    SAPKGPAD22
    SAP Enterprise Extension PLM, SCM, Financials
    EA-DFPS
    600
    0022
    SAPKGPDD22
    SAP Enterprise Extension Defense Forces & Public Security
    EA-FINSERV
    600
    0023
    SAPKGPFD23
    SAP Enterprise Extension Financial Services
    EA-GLTRADE
    600
    0022
    SAPKGPGD22
    SAP Enterprise Extension Global Trade
    EA-HR
    600
    0086
    SAPKGPHD86
    SAP Enterprise Extension HR
    EA-PS
    600
    0022
    SAPKGPPD22
    SAP Enterprise Extension Public Services
    EA-RETAIL
    600
    0022
    SAPKGPRD22
    SAP Enterprise Extension Retail
    FINBASIS
    600
    0022
    SAPK-60022INFINBASIS
    Fin. Basis
    ECC-DIMP
    600
    0022
    SAPK-60022INECCDIMP
    DIMP
    ERECRUIT
    600
    0022
    SAPK-60022INERECRUIT
    E-Recruiting
    FI-CA
    600
    0022
    SAPK-60022INFICA
    FI-CA
    FI-CAX
    600
    0022
    SAPK-60022INFICAX
    FI-CA Extended
    INSURANCE
    600
    0022
    SAPK-60022ININSURANC
    SAP Insurance
    Thanks

    Hi John,
    Few checks before you start the upgrade
    1) Check PAM for checking OS and DB compatibility with EHP4
    2) I could see apart from core ECC , you have HR module being implemented and used.
       So check upgrade release info for HR module if there is any dependecy
    3) For EHP4 related information refer SAP upgrade guide.
    Hope this helps.
    Regards,
    Deepak Kori

  • EHP4 upgrade: Error in Phase ACT_UPG

    Hi All,
    While upgrading to EHP4 on ECC 6 system, we got error in phase MAIN_SHDRUN/ACT_UPG
    Checks after phase MAIN_SHDRUN/ACT_UPG were negative!
    Last error code set: Unresolved requests in buffer RH4 Check logfiles 'ACTUPG.ELG' and '/sapdump/SAPehpi/EHPI/abap/log/SAPehpi.ECO'
    ACT_UPG log:
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    DDIC ACTIVATION ERRORS and RETURN CODE in SAPA-604DMINISPSCA.RH4
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    1 ETP111 exit code           : "12"
    Log of SAPA-604DMINISPSCA.RH4
    1 ETP155 ACTIVATION OF DD-OBJECTS
    1 ETP101 transport order     : "SAPK-604DMINISPSCA"
    1 ETP102 system              : "RH4"
    1 ETP108 tp path             : "/sapdump/SAPehpi/EHPI/abap/exe/tp"
    1 ETP109 version and release : "372.04.70" "700"
    1 ETP198
    3 EPU324 See log for request "/sapdump/SAPehpi/EHPI/abap/tmp/SAPAB70015.RH4" (timestamp "01:26:08", system "RH4")
    1AETR012XProgram terminated (job: "RDDMASGL", no.: "01260600")
    1AEPU320 See job log"RDDMASGL""01260600""RH4"
    1 ETP155 ACTIVATION OF DD-OBJECTS
    1 ETP110 end date and time   : "20091012033215"
    1 ETP111 exit code           : "12"
    1 ETP111 exit code           : "12"
    Job RDDMASG log :
    Job cancelled with following log
    2.10.2009 01:26:07 Job started                                                               00           516          S
    2.10.2009 01:26:07 Step 001 started (program RDDMASGL, variant IMPACTMRG, user ID DDIC)      00           550          S
    2.10.2009 01:26:08 Start of mass activation 01:26:08                                         AD           010          S
    when tried to log into shadow instance after getting error, it is giving error
    RH4: system message
    work process restarted; session terminated;
    we restarted shadow system. There is no dumps in the shadow system.
    Work process getting killed after 7800s
    checked in work directory of Shadow system:  devdisp log :_*
    Mon Oct 12 04:49:46 2009
    rdisp/http_min_wait_dia_wp : 1 -> 1
    ***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c   1694]
    ***LOG Q0K=> DpMsAttach, mscon ( HW136799) [dpxxdisp.c   12639]
    DpStartStopMsg: send start message (myname is >HW136799_RH4_22                         <)
    DpStartStopMsg: start msg sent
    Warning: Swap space is configured quite small with 20477 MB.
    It should be configured with at least 20 GB on 64 bit systems.
    See note 153641 for more information.
    Warning: tmpfs at /dev/shm is configured quite small with 1972 MB!
    Minimum value is 8192 MB.
    Recommended size is 75 % of RAM + swap.
    CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
    Mon Oct 12 04:49:47 2009
    DpMsgAdmin: Set release to 7000, patchlevel 0
    MBUF state PREPARED
    MBUF component UP
    DpMBufHwIdSet: set Hardware-ID
    ***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1050]
    DpMsgAdmin: Set patchno for this platform to 221
    Release check o.K.
    MBUF state ACTIVE
    DpModState: change server state from STARTING to ACTIVE
    Mon Oct 12 06:57:01 2009
    ERROR => DpWPCheck: W8 (pid 9769) died (severity=0, status=7) [dpxxdisp.c   15776]
    child (pid=9769) killed with signal 7
    Mon Oct 12 06:57:43 2009
    ERROR => DpWPCheck: W7 (pid 9768) died (severity=0, status=7) [dpxxdisp.c   15776]
    child (pid=9768) killed with signal 7
    Please let us know what needs to be cheked for the problem
    Thanks,
    Ramesh Ramagowni

    Hi Markas and All,
    Thanks for the information. /dev/shm was 100% full. now, the issue is solved after deleting its contents. and we have finished with EHP4 upgrade.
    After upgrade, SAP_AP component still showing as 700
    SAP_AP - 700 - 0015 - SAPKNA7015 -SAP Application Platform
    Can we delete old tablespace PSAPSR3700, it is showing as 0% used in brspace at present.
    Also while trying to move some datafiles using brtools after upgrade we are getting following error,
    BR0280I BRTOOLS time stamp: 2009-10-20 01.45.52
    BR0670I Enter 'c[ont]' to continue, 'b[ack]' to go back, 's[top]' to abort:
    c
    BR0280I BRTOOLS time stamp: 2009-10-20 01.45.54
    BR0257I Your reply: 'c'
    BR0259I Program execution will be continued...
    BR0252E Function fopen() failed for '/oracle/RH4/sapbackup/.user.pas' at location BrToolCall-2
    BR0253E errno 13: Permission denied
    BR0669I Cannot continue due to previous warnings or errors - you can go back to repeat the last action
    BR0280I BRTOOLS time stamp: 2009-10-20 01.45.54
    BR0671I Enter 'b[ack]' to go back, 's[top]' to abort:
    There is no file in the directory '/oracle/RH4/sapbackup/.user.pas'
    Please suggest what needs to be for this issue..Do we need to upgrade BRTOOLS..
    Thanks,
    Ramesh R

  • ECC-DIMP 604 upgrade

    Hi exports,
    I had alredy upgraded my ECC 6.0 Ready to EHP4, know i am trying to upgrade the component ECC-DIMP using SAINT.
    My OS platform is HP-UX IA and DB is Oracle.
    In the SAINT queue i had put both ECC-DIMP 603 and 604, along with stack.xml
    While import during DDIC_ACTIVATION phase it failed and the log file shows "tp ended with return code 12 ".
    I had checked the file system and data base tables, it seems ok.
    Recently i had upgrated my kernel to 117, which is the latest one.
    Also i had alredy gone through all the below mention notes, and taken action as necessary
    Note 822380 - Problems w/ add-on inst/upgrade to SAP NW 7.0 AS ABAP
    Note 874473 - Release strategy for ECC-DIMP as of ECC 6.0
    Note 874471 - Additions for installing or activating ECC-DIMP on ECC 6.0
    Note 1083533 - Installation of Enhancement Package 3 on SAP ERP 6.0
    Note 822379 - Known problems with Support Packages in SAP NW 7.0x AS ABAP
    Note 822379 - Known problems with Support Packages in SAP NW 7.0x AS ABAP
    Note 1118803 - ECC 600 Support Packages and ERP enhancement packages
    Note 1119856 - Description, tips and tricks for Attribute Change Packages
    Note 1258938 - DDIC_ACTIVATION error during EhP4 installation
    Please provide your valuable suggestion
    Thanks & Regards
    Dusmanta

    Hi,
    The problem is solved after applying SAP Note 1476315 - Error in activation protocol for switch framework.
    You need to implement the coding corrections of the note to your system and restart import . If the note cannot be
    implemented via SNOTE, as most likely the note assistant may be locked . Please ask one of your developers to perform the changes manually via SE80/SE24
    Regards
    Dusmanta.

Maybe you are looking for