ECC6.0 - upgrade from EHP4 to EHP6 - cross release transports.

Hi Experts
We are planning to upgrade our system from ECC6.0 -EHP4 to EHP6.
Source - ECC6.0-EHP4
Target - ECC6.0-EHP6(Enhancement pack6)
Current ECC version -
SAP_BASIS 701 0014 SAPKB70114 SAP Basis Component
SAP_APPL 604 0013 SAPKH60413 Logistics and Accounting
We would like to know during the project if we can do a transport
between upgraded development ECC6.0 -EHP6 to non upgrade production ECC6.0-EHP4.
We have data from note 1090842 and 1273566.
But last 10 lines of note 1090842 are contradictory wherein on one side it says you can do transports between Releases 7.0*, 7.3* and 7.4* and
on other it says it can be problem if support pack levels are different on same release.(if problem can happen on same release with different pack
level then there are greater chances of issues between different releases).Note 1273566 is clear and suggest no issues exist yet for
technical and logical transports between suggested version 700/701 to >=702
Also below is the extract from SUM guide - (SUM-1.0-SP07)
RECOMMENDATION
We strongly recommend that you perform transports only between systems of the same release or enhancement package level, and where the same business functions are activated. If you do not follow this recommendation, you do so at your own risk regarding potential problems.
Please suggest if we need to create Dual maintainance parallel landscape during the tenure of project where two development system co-exist.One
with current and one with upgraded version and changes need to be done on both in parallel.Support fixes and LTO’s go from non upgraded dev to non upgraded prod.
Thanks

Hello
I won't perform cross version transport even if it can be possible.
As of 7.02 cross version transport are prevented by default with option SP_TRANS_SYNC (see here under note).
The best way is, if possible, to have a manual dual maintenance. All corrections created in the Ehp4 dev should be manually recreated in the Ehp6 dev.
What is usually done is to upgrade at first a copy of production for test/discovery purpose, the aim is to identify most of the regressions/evolutions. This will reduce the time you will have to spend in the migrated dev to adjust your system. You then migrate dev and enter in a freeze period where you reduce activity on legacy Ehp4 system to the minimum (bug correction for prod).
One good thing with the manual reprocessing of changes on the Ehp6 system is that this kind of constraint will help consultants to reduce their activity.
Regards
1742547 - Information about component version check in TMS

Similar Messages

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

Excel layout changed after EHP5 upgrade from EHP4.

Hi All,
We have just finished the EHP5 upgrade from EHP4 for ECC 6.0 for our production system. BUT we noticed that The standard layout, (also known as Dynamic List Display) has been chagned in EHP5 compare to EHP4.
This is affected us as we have lot of macros enable for the excel files.
Request you all to help. Is there any sapnote, anyway we can resolved this issue.
Thanks

Hi Markus,
Thanks for reply.
I not sure how i can attached file over here? Is there anyway to attached files in the forum?. I have the before and after image of excel file.
But the position of the data which is downloaed in the excel sheet has been changed after upgrade. For example ,Before upgrade the column named "Description" in the production plan report was in the second column i.e. B where as after upgrade the "Description" column in the production plan report is in the first column i.e. A.
I mean the postion of the data changed in after upgrade. Therefore macro which are enable are not working anymore.
New Format Example
Production plan
Description                        Material                               Sales doc.
IRB 2600 M2004                 3HAC020536-018              104861
IRB 2600 M2004                 3HAC020536-018              2BT0615486
OLD Format
Production plan
                                      Description                    Material                               Sales doc.
                                      IRB 2600 M2004            3HAC020536-018               104861
                                      IRB 2600 M2004            3HAC020536-018               2BT0615486
Hope this above will help to make it clear.
After checking this message ... the output example given above seems to be not showing the way i itend to... But in above example in the old format the Description column was at column B instead of column A after upgrade.
Thanks
Edited by: deepak.shinde on Oct 11, 2011 8:34 AM
Edited by: deepak.shinde on Oct 11, 2011 8:36 AM

MaxDB 7.8 error upgrading from EHP4 to EHP5

I'm upgrading ECC600 from EHP4 to EHP5 (ramp-up release) in a Maxdb 7.8 and Linux Suse 11 environment.
The source release have an 7.01 kernel.
With sapehpi, in the phase PREP_INTEGRATION/TABSPC_PREP, I have an error in GDBSSHD.LOG file:
TPERR- error in dbdd_get_size: 2
TPERR- msg: POS(60) Unknown column name:OWNER
Accordingly with notes 1142632 and 1447663, I installed the new 7.01 kernel (version 117) without changes.
I copied also the new dbsdbslib.so file in the installation directory, but there are no changes.
Any suggestion?
Thanks

Unfortunatelly, after the correction, I try to restart the SAPehpi and in the PREP_INTEGRATION/TABSPC_PREP phase I had another similar error; in the TABSPCP.LOG file there are this message:
4EETQ399 Execution of 'tp getdbobjsize' failed, rc=1
In the file TP.ECO the error is:
TRACE-INFO: 1: [dev trc     ,00000] Thu Apr 14 09:59:00 2011                                                         1789 0.001789
TRACE-INFO: 2: [dlux.c      ,00000] *** ERROR => DlLoadLib()==DLENOACCESS - dlopen("/sapdb/DVDEHP5/EHPI/abap/exe/dbsdbslib.so") FAILED
TRACE-INFO: 3:                          "/sapdb/DVDEHP5/EHPI/abap/exe/dbsdbslib.so: cannot open shared object file: No such file or directory"
TRACE-INFO: 4:                                                                                34 0.001823
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0249
tp finished with return code: 249
meaning:
connect failed due to DbSL load lib failure
I try the R3trans -d command but in the trans.log file there is the message:
4 ETW000 [dev trc     ,00000] Loading DB library '/usr/sap/IBS/SYS/exe/run/dbsdbslib.so' ...           118 0.000702
4 ETW000 [dlux.c      ,00000] *** ERROR => DlLoadLib()==DLENOACCESS - dlopen("/usr/sap/IBS/SYS/exe/run/dbsdbslib.so") FAILED
4 ETW000                          "/usr/sap/IBS/SYS/exe/run/dbsdbslib.so: cannot open shared object file: No such file or directory"
4 ETW000                                                                                272 0.000974
4 ETW000 [dbcon.c     ,00000] *** ERROR => Couldn't load library '/usr/sap/IBS/SYS/exe/run/dbsdbslib.so'
of course the file exists and I copied the same that are in exe and exenew directory.
Any suggestions?

Eror upgrading from EHP4 to EHP5 , Database : MAxDB 7.8.0.14

Hello
I have updated Max db from 7.6 to 7.8 recenlty required to Upgrade ECC6.0 EHP5
Current ECC 6.0 EHP4 , NW 7.00 EHP1
Below is the i am getting while upgrading EHP5 through SAPEHpi
TOOLOUT.LOG-->
SAPehpi> Starting subprocess tp.exe with id 5580 at 20110503154658
EXECUTING tp.exe pf=J:\EHP5_INST\EHPI\abap\bin\DEFAULT.TPP getdbinfo WT9
Environment: JAVA_HOME=C:\j2sdk1.4.2_11
Environment: PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\j2sdk1.4.2_11\bin;E:\usr\sap\WT9\SYS\exe\uc\NTAMD64;E:\sdb\programs\bin;E:\sdb\programs\pgm;E:\usr\sap\WT9\SYS\exe\uc\NTAMD64
Environment: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
Environment: auth_shadow_upgrade=0
Environment: dbms_type=SDB
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
HALT 20110503154658
ERROR: *Cannot determine database version, database type is not defined in profile. [tpconnect.c,1158]*ERROR: EXIT(16) -> process ID is: 3176
Process with ID 3176 terminated with status 204
Please help
Regads
Jain Pankaj

> EXECUTING tp.exe pf=J:\EHP5_INST\EHPI\abap\bin\DEFAULT.TPP getdbinfo WT9
> Environment: JAVA_HOME=C:\j2sdk1.4.2_11
You Java version is 32bit and is ancient where you platform seems to be 64bit. I highly suggest using a recent JDK.
> Environment: dbms_type=SDB
I guess this is the problem, dbms_type must be "ADA".
Markus

My problem with Toplink upgrade from 2.5.1 to Release 2

Hi:
I met some confusions in upgrading our system from TOPLINK2.5.1 to TOPLINK Release 2(Oracle9.0.3).
And because I didn't use TOPLINK tools before this project, I spent one week to know the structure of our system. Unfortunately, Our company isn't a supported Oracle customer. We just bought Oracle product, didn't buy support service.
First of all, I'll describ our system structure. The system is Weblogic5.1 + Toplink 2.5.1 + Oracle8.1 .Using Toplink we mapping our EJB to Oracle. The results of this procedure aremany .table, .descriptor, .topclass under the mapping forlder, and weblogic-ejb-jar.xml, topling-cmp-XX.xml, ejb-jar.xml under the deploy forlder. That's all.
So, after our ant-build, we copy these results to Weblogic server directory, and compile with EJB, deploy them. It's correct?
OK, as my considering, I install TOPLINK Release 2 , use Renamer tool to rename my source code from old TOPLINK library to oracle.toplink, complie them again. And create new project in TOPLINK 9.0.3 , import classes, login Database correctly. Do mapping as in TOPLINK2.5.1. Generate packagename.ClassDescriptor.xml under Descriptor, forlder ClassRepository, Class, Table, Database generate xml files also.
Do the above process correct? OK, let's assume it' correct. But how can I modify my ant-build , you know the structure is difference between Weblogic 5.1 and Weblogic 6 or 7. Additionally, I don't know where should I copy new TOPLINK library to Weblogic directory. Yes, I know old TOPLINK library location, but I think it has difference.
So , please tell me I can use Weblogic5.1 + TOPLINK 9.0.3 + Oracle 8.1 , is it right? I will be appreciated if you can give me some detail steps in upgrading TOPLINK.
And perhaps we need to upgrade out system from TOPLINK 2.5.1 to TOPLINK 4.x first?
Thanks for your view.
Yours
Denver Yang
Software Engineer

Hello Denver,
If you are using CMP Entity Beans then TopLink 903 supports WebLogic 6.1 and 7.0. You would have to upgrade your WebLogic version at the same time you upgrade TopLink.
If you are using Java Objects (not CMP Entity Beans), then you can use any version of any app server with TopLink.
If you migrate from 2.5.1 to 903, you can send your project to support and they will update it. If you are not a supported customer, then you will have to do this manually (meaning you will have to remap in 903 from brand new).
You are correct that your build process will be different when you migrate, but this will be because of how WebLogic has changed deployment and how the EJB spec has evolved moreso than anything to do with TopLink. How to do deployment in 903 should be in the TopLink 903 docs.
Hope this helps,
- Don

Upgrade from Microsoft Word X Service Release 1

I may be posting in wrong forum, if so please let me know a more appropriate forum to post in.
When I originally made the heavenly switch to Apple, I purchased the student version of Microsoft Word X Service Release 1. It still works fine, except that I cannot open the latest version of PC-produced .docx files, and sometimes I lose things when opening a later version of excel docs.
My question(s), assuming I need those to versions, will upgrading to the latest version of Word for Mac correct it. Can I just upgrade or do I have to buy the whole office package again? Has anyone else upgraded successfully? Any comments/advice welcome. Thanks!

*"Can I just upgrade or do I have to buy the whole office package again?"*
You can try the converter:
http://www.microsoft.com/mac/downloads.mspx?pid=Mactopia_AddTools&fid=6B9238E1-C F69-48C4-BF2D-C4A8ACEEE520#viewer
If that doesn't work ,you'll need to pay for the upgrade to Office 2008.
Also, you may want to consider posting further questions regarding Office on Microsoft's own forums for their Mac products:
http://www.officeformac.com/productforums

Failed to upgrade from ERP 6.0 EHP4 to EHP5

Dear SAP Gurus,
we are running ERP 6.00 with EHP4 (HCM-component) based on Windows 2003
SP2 X64 and SQL Server 2005 SP4 (64-bit).
We are using SAP Kernel Unicode 7.01 PL 133 (64-bit).
We intend to upgrade from EHP4 to EHP5.
Upon running SAPehpi, we encountered issue which stopped us from
proceeding with the upgrade.
Case 1: Direct upgrade to 605
The upgrade failed on PREP_INPUT/VERSCHK_INI with error message: The
following combination is not supported (SAP_APPL 600, SAP_BASIS 701,
SAP_ABA 701).
Case 2: Upgrade SAP_APPL component from 600 to 604 (due to the above
error message)
The upgrade failed on PREP_INPUT/VERSCHK_INI with error message:
Release '701' of component SAP_BASIS is too new.
Case 3: upgrade via SAINT is not supported by SAP. When uploading the
Stack XML file, we got error saying that the stack is not supported.
Attached is the complete list of the current SP Level of Installed
components.
Please advise on how we can perform the upgrade to EHP5.
Many thanks in advance.
regards,
Denny

The thing is Solution Manager was able to produce the XML file during the previous upgrade to 604 (the one without SAP_APPL 604).
So how can it not be supported by SAP?
If it is not supported by SAP, how can I proceed from here?
Component Software C SP-Level Support Package Short description of the component
SAP_ABA 701 0007 SAPKA70107 Cross-Application Component
SAP_BASIS 701 0007 SAPKB70107 SAP Basis Component
PI_BASIS 701 0007 SAPK-70107INPIBASIS Basis Plug-In
ST-PI 2008_1_700 0003 SAPKITLRD3 SAP Solution Tools Plug-In
SAP_BS_FND 701 0008 SAPK-70108INSAPBSFND SAP Business Suite Foundation
SAP_BW 701 0007 SAPKW70107 SAP Business Warehouse
SAP_AP 700 0021 SAPKNA7021 SAP Application Platform
WEBCUIF 700 0008 SAPK-70008INWEBCUIF SAP WEBCUIF 700
SAP_APPL 600 0018 SAPKH60018 Logistics and Accounting
SAP_HR 604 0035 SAPKE60435 Human Resources
EA-IPPE 400 0018 SAPKGPID18 SAP iPPE
EA-APPL 600 0018 SAPKGPAD18 SAP Enterprise Extension PLM, SCM, Financials
EA-DFPS 600 0018 SAPKGPDD18 SAP Enterprise Extension Defense Forces & Public Security
EA-FINSERV 600 0018 SAPKGPFD18 SAP Enterprise Extension Financial Services
EA-GLTRADE 600 0018 SAPKGPGD18 SAP Enterprise Extension Global Trade
EA-HR 604 0035 SAPK-60435INEAHR SAP Enterprise Extension HR
EA-PS 600 0018 SAPKGPPD18 SAP Enterprise Extension Public Services
EA-RETAIL 600 0018 SAPKGPRD18 SAP Enterprise Extension Retail
FINBASIS 600 0018 SAPK-60018INFINBASIS Fin. Basis
ECC-DIMP 600 0018 SAPK-60018INECCDIMP DIMP
ERECRUIT 600 0018 SAPK-60018INERECRUIT E-Recruiting
FI-CA 600 0018 SAPK-60018INFICA FI-CA
FI-CAX 600 0018 SAPK-60018INFICAX FI-CA Extended
INSURANCE 600 0018 SAPK-60018ININSURANC SAP Insurance
IS-CWM 600 0018 SAPK-60018INISCWM Industry Solution Catch Weight Management
IS-H 600 0023 SAPK-60023INISH SAP Healthcare
IS-M 600 0018 SAPK-60018INISM SAP MEDIA
IS-OIL 600 0018 SAPK-60018INISOIL IS-OIL
IS-PS-CA 600 0018 SAPK-60018INISPSCA IS-PUBLIC SECTOR CONTRACT ACCOUNTING
IS-UT 600 0018 SAPK-60018INISUT SAP Utilities/Telecommunication
LSOFE 600 0018 SAPK-60018INLSOFE SAP Learning Solution Front-End
SEM-BW 600 0018 SAPKGS6018 SEM-BW: Strategic Enterprise Management
ST-A/PI 01M_ECC600 0001 SAPKITAR7F Application Servicetools for ECC 600-605
VIRSAHR 530_700 0012 SAPK-53312INVIRSAHR SAP GRC Access Controls 5.3 for 700 HR S
VIRSANH 530_700 0014 SAPK-53314INVIRSANH SAP GRC Access Controls 5.3 for 700 HR a

SU25 after after EHP4 to EHP6 upgrade

Hi,
We have recently upgraded our development ECC system to ECC 6.0 EHP 6 from EHP4. We found there are lot of roles affected by
the upgrade in step 2c of SU25.All the proposed changes are due to step 2a which updates the objects/transactions which were never modified by the customer.
While we are still analysing the roles in DEV, the production upgrade date is fast approaching.
Is it advisable to upgrade the Production now and perform the SU25 in DEV later and promote the roles to Production after proper testing in QA?
or is it something we have to do immediately after the upgrade before releasing it to the end users?
Thank you in advance,
Silver

Hi Silver Surfer
Is it advisable to upgrade the Production now and perform the SU25 in DEV later and promote the roles to Production after proper testing in QA?
Do you mean - is it okay for EHP6 to be applied to Production and fix the security later? If so....
Your risk is if new authorisations checks have been introduced to existing transactions that are in design then users may start to receive authorisations errors. If you are willing to risk a flood of annoyed users complaining of lack of access it is technically possible.
Though, if you are moving from EHP4 to EHP6 was security testing along with functionality testing? If so, you may have covered a large portion of the risk.
As far as SU25 goes, it is to assist with fixing up SU24 values based on SAP proposals. Once you need to make changes to SU24 you need to adjust the roles (As per you Step 2c). I've been at places where they made the decision to execute Steps 2a and 2b and then go into PFCG for each impacted role and deactivate the new proposals (i.e. SU24 updated but PFCG remains unchanged from authorisation perspective). This approach enabled them to "technically" complete the security steps and move a transport through to test environment. However, they were relying on security testing of the roles to identify authorisations issues. If issue was identified, they would then fix the role.
Whatever your approach with SU25 is.... security roles need to be tested as part of an upgrade.
Regards
Colleen

ECC6 Upgrade and EHP 4 because of a CRM7 in the landscape?

Hi,
I am in the way to upgrade my SAP 4.6c system to ECC6.
In my overall landscape, I have a CRM 7 installed.
Do you believe I need to perform a simple ECC6 upgrade or a ECC6 upgrade including EHP4 SR1?
In other words, is it mandatory to go through the Upgrade + EhP4 because I have a CRM 7 around?
Thank you,
Chris

Hi,
according to my view upgrade from SAP 4.6c to ERP 6.0 EHP4 is easy because you can save your time in all preparation task that you to carry before starting upgrade as EHP upgrade itself takes time for preaprtion task....
also, you can reduce the downtime of your production environment if you will directly go to ERP EHP4..
As EHP4 takes significant downtime to upgrade the system ( also depends on hardware and database size)...
Also, you can reduce probablity of error free upgrade by carrying out one upgrade instead of carrrying out 2 upgrade (from SAP 4.6c to ERP6.0 then ERP6.0 to EHP4)...
Hope it clears to you...
Thanks
Sunny

ASA Firewall Upgrade from 8.2,8.4, to 9.0

Dear All ,
we have five firewalls with the following details:
First Firewall
Hardware:   ASA5550, 4096 MB RAM, CPU Pentium 4 3000 MHz, Flash 256MB , BIOS Flash1024KB , ASA IOS 8.4(3) ,Device Manager Version 6.4(7)
    my question can i upgrade ASA IOS 8.4(3) to 9.0 directly without any issues also can i upgrade Device manager 6.4(7) to 7.0 without upgrading the       ASA IOS itself
Second Firewall
Hardware:   ASA5520,2048 MB RAM, CPU Pentium 4 2000MHz, Flash 256MB , BIOS Flash1024KB , ASA IOS 8.2(3) ,Device Manager Version
6.2(3)
my question can i upgrade ASA IOS 8.2(3) to 9.0 directly without any issues also can i upgrade Device manager 6.2(3) to 7.0 without upgrading the       ASA IOS itself
Third Firewall
Hardware:   ASA5520,2048 MB RAM, CPU Pentium 4 2000MHz, Flash 256MB , BIOS Flash1024KB , ASA IOS 8.4(3) ,Device Manager Version 6.4(7)
my question can i upgrade ASA IOS 8.4(3) to 9.0 directly without any issues also can i upgrade Device manager 6.4(7) to 7.0 without upgrading the       ASA IOS itself
Fourth Firewall
Hardware:   ASA5520,2048 MB RAM, CPU Pentium 4 2000MHz, Flash 256MB , BIOS Flash1024KB , ASA IOS 8.4(3) ,Device Manager Version 6.4(7)
my question can i upgrade ASA IOS 8.4(3) to 9.0 directly without any issues also can i upgrade Device manager 6.4(7) to 7.0 without upgrading the       ASA IOS itself
fifth Firewall:
Hardware:   ASA5520,2048 MB RAM, CPU Pentium 4 2000MHz, Flash 256MB , BIOS Flash1024KB , ASA IOS 8.2(3) ,Device Manager Version 6.2(3)
my question can i upgrade ASA IOS 8.2(3) to 9.0 directly without any issues also can i upgrade Device manager 6.2(3) to 7.0 without upgrading the       ASA IOS itself
please help i am doing the upgrading remotely using the ASDM and i don't want to do any upgrade could result disconnectivity.
Best regards

Hi Basel,
Honestly, I wouldn't suggest a direct upgrade from 8.2 to 9.0. This is a *major* upgrade. The recommended path to reach 9.0 would be from 8.2-->8.4-->9.0
Here are the release notes for 9.0:
http://www.cisco.com/en/US/docs/security/asa/asa90/release/notes/asarn90.html#wp690047
Per above document:
If you are upgrading from a pre-8.3 release, see also the Cisco ASA 5500 Migration Guide to Version 8.3 and Later
for important information about migrating your configuration.
Once you are on 8.3/8.4 (I would suggest 8.4 as a lot of issues were fixed post 8.3 as that was a huge transition from 8.2) upgrade to 9.0 is fairly simple.
Major part is upgrade from 8.2 to 8.4 as configuration changes and few things can be broken as a result. I would highly recommend you to check these docs before attempting an upgrade and also do it with some maintenence window so as to correct things in case they broke:
Following doc talks about 8.3 but it is applicable to direct upgrade to 8.4 as well:
https://supportforums.cisco.com/docs/DOC-12690
Release notes for 8.4:
http://www.cisco.com/en/US/docs/security/asa/asa84/release/notes/asarn84.html
Sourav

User Facing Features and Upgrades from 6.x and 7.x (MWI, DND, CFA, ...)

The 9.1.1 upgrade guide states:
"For upgrades from Cisco Unified Communications Manager Release 8.x, changes that are made to the following user-facing features get preserved after the upgrade completes ...".
What happens to user facing features like MWI and CFA for upgrades from 6.x and 7.x?

Hi,
you can refer the link which says
User Provisioning
For upgrades from Cisco Unified Communications Manager Release 4.x and 5.x, any provisioning that the end user performs to user-facing features after the upgrade begins could get lost.
For upgrades from Cisco Unified Communications Manager Release 6.x, changes that are made to the following user-facing features get preserved after the upgrade completes:
•Call Forward All (CFA)
•Message Waiting Indication (MWI)
•Privacy Enable/Disable
•Do Not Disturb Enable/Disable (DND)
•Extension Mobility Login (EM)
•Hunt Group Logout
•Device Mobility
•CTI CAPF status for end users and application users
•Credential hacking and authentication
•Recording enabling
•Single Number Reach enabling
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/cucos/7_1_2/cucos/osg_712_cm/iptpch7.html
regds,
aman

CCM Upgrade from 5.1.3 to 6.1.2

I want to know if I can upgare Call Manager from 5.1.3 to 6.1.2. Is this possible or I have to from 5.1.3 to 6.0 and then from 6.2 to 6.1.2.
Please let me know and also if any one know where to down the software from Cisco, please send me the link.
I downloaded the software, but that is from 6.0 to 6.1.2
Thanks!!!

Hi Rohan,
Both of these upgrades will require you to order the Media Kits and License via PUT;
Upgrade Paths To Cisco Unified Communications Manager 6.1(2)
You can upgrade directly to Cisco Unified Communications Manager 6.1(2) from:
â¢4.2(3x)
â¢5.1(2x)
â¢5.1(3x)
â¢6.0(1a)
â¢6.1(1x)
Caution: Use the ISO files that are mentioned in the "Upgrading from Cisco Unified Communications Manager Release 6.0.(1a) or higher to Release 6.1(2) by Using the UCSInstall File" section for upgrades from 6.1(1x)only.
Upgrading from Unified CM 4.x and 5.x
If you are upgrading from 4.1.3, 4.2.3, 5.1.1, 5.1.2, or 5.1.3, use the Product Upgrade Tool (PUT) or the PUT that is for registered customers only to obtain a media kit and license or to purchase the upgrade from Cisco Sales.
To use the PUT, youmust enter your Cisco contract number (Smartnet, SASU or ESW) and request the CD/CD set. If you do not have a contract for Cisco Unified Communications Manager, you must purchase the upgrade from Cisco Sales.
For more information about supported Unified CM upgrades, see the Cisco Unified Communications Manager Compatibility Matrix at the following URL:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_device_support_tables_list.html
From these good release notes;
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/6_1_2/cucm-rel_note-612.html#wp396032
Upgrade Paths To Cisco Unified Communications Manager 6.1(1b)
It is possible to upgrade directly to Cisco Unified Communications Manager 6.1(1b) from:
â¢4.1(3x)
â¢4.2(3x)
â¢5.1(1x)
â¢5.1(2x)
â¢5.1(3x)
â¢6.0(1x)
â¢6.1(1x)
Caution: Use the iso files mentioned in the "Upgrading from Cisco Unified Communications Manager Release 6.0(1a) or 6.1(1a) to Release 6.1(1b) Using the UCSInstall File" section for upgrades from 6.0(1a) or 6.1(1a) to 6.1(1b) only.
Upgrading from CUCM 4.x and 5.x
If you are upgrading from 4.1.3, 4.2.3, 5.1.1, 5.1.2, or 5.1.3, use the Product Upgrade Tool (PUT) or the PUT for registered customers only to obtain a media kit and license or purchase the upgrade from Cisco Sales.
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/6_1_1/cucm-rel_note-611b.html#wp253846
Hope this helps!
Rob

Planning for Mobile Service Pack Upgrade from 2007 SP2 to SP6

Hello Mobile Gurus,
We are planning for upgrading mobile from 2007 SP2 to SP6. Can anyone of you guess a time line for achieving this?
I mean, how long will it take in dev env to upgrade commstation, mrs, mdw etc. apart from upgrading the field laptops?
thanks

Hello Mahesh
had missed 5th point. ie Rollout to the client laptops . the amount of time it takes will be based on the kind of customization and kind of issues that you face in your application . etc.
Repostiroy upgrade from n to n+1 release will take approx 1-2 hours (with out additinal language) and it is correct.
I have given you the rough estimates so that you will get a fair idea how much time it is going to take.
Best Regards
Shankar

Follow up activities after SAP (CU&UC) upgrade from SAP 4.6c to ECC6 EHP4

Dear Friends
We have completed SAP (CU&UC) upgrade from SAP 4.6c to ECC6 EHP4.
We refereed the upgrade guide for follow activities and we required confirmation before performing the activities.
Could you please help us what needs to be done immediately after upgrade.
Regards,
Bharathi

Dear Nils,
Thanks for the support.
Yes, we are following the same document 'CUUC46C_to_NW701SP07' for unicode conversion after the upgrade from the note 928729.
Please suggest us in that document which are the steps should be carried out after ECC6.0 EHP4 upgrade,
1. Preparation
2. Unicode Preconversion Phase in SAP Basis 4.6C
3. Upgrade Process
4. Unicode Conversion Phase
5. Unicode Conversion Completion Phase
6. SAP Notes
Regards,
Bharathi

ECC6.0 - upgrade from EHP4 to EHP6 - cross release transports.

Similar Messages

Maybe you are looking for