6500 Upgrade Rommon procedure

Experienced a problem with a 6509 chassis that the recommendation was to upgrade the rommon level on the sup720s which have msfc3 and native IOS. I have a procedure that shows an upgrade of an individual supervisor and a procedure for upgrading an MSCF3 on a sup720. Both procedures show different code families. I will attach a "sh version" output. Are there a combination of codes that need to be deployed together? For example: a rommmon code for the supervisor, one for the MSFC3, and one for the DFC3. We also deploy redundant supervisors in the switch. Can someone recommend the proper software to upgrade with and the proper procedure for upgrading redundant supervisors? Can you do the upgrade on one supervisor and have it automatically synchronize the redundant supervisor, or do you upgrade each supervisor separately, one at a time?

I think you have upgrade each supervisor separately. But afgter upgradation, the new configuration changes made in Active Sup can be synchronised with Redundant sup using RPR or RPR+.

Similar Messages

VSS 6500 Upgrade Procedure

Hi all,
I searching for a best practice paper which explains the detailed procedure for a VSS upgrade on a Catalyst 6509 with a single SUP2T.
As far as I know it isn't posible to do a ISSU because we must upgrade from 12.2SX to 15.1SY.
Thanks for helping....
Udo

I think you have upgrade each supervisor separately. But afgter upgradation, the new configuration changes made in Active Sup can be synchronised with Redundant sup using RPR or RPR+.

Business Content Upgrade Activation Procedure

Hello Everyone,
I'm looking for a procedure or best practices document that will help me with the steps I need to follow when activating business content due to an upgrade when some of the objects have already been activated and are being used in PRoduction. As an example, we upgraded our BW system to 3.5 but didn't activate any of the Business Content so everything continued to run just fine. Now we activated a new InfoArea that overlapped some of the objects that were already active. A good example is 0REGION. The DataSource in R/3 changed to use a different table for the view so new fields are now available which are actually the same as the fields that were already there but with different names. So the transfer rules show as modified/inactive. I transferred the new structure from R/3, replicated in BW, and changed the transfer rules to use the new fields. Is this the procedure that needs to be followed for any object that was put on the tranport? I've also noticed that many InfoObjects are on the transport but the only change I can see is that the content version changed so if the InfoObject didn't really have any changes, why the version change?
As I mentioned, this is the first time we've activated new content after an upgrade and I'm totally in the dark as to what the procedure should be to follow to get everything cleaned up and up to date.
When you are activating a new area, do you pick and choose which objects you want to activate/match or do you generally just activate the entire InfoCube or InfoArea?
Thanks for any insight,
Diane Merrill

Hi Diane,
I think you should go with infosource or may be with application component. Collect everything of that area and let the system check the already active objects so that it is not just activating the new content but enhancing already active objects with the new content features. But take care, this option is only available when you start this activation in foreground. In background there is only a overwrite mode available which might lead to a loss of developments.
regards
Siggi

Upgrade Supervisor Procedure

What is the proper procedure when upgrading dual supervisor module on a 6513 switch.
1) Do you upgrade the primary / secondary supervisor first, with the secondary / primary supervisor hanging halfway out of the switch?
2) Do you disable HA?
3) Do you reboot the switch or module after you upload the new image to the primary and secondary supervisor?
4) If your not careful can the supervisor in slot-2 take over as the primary supervisor?
I have the document on upgrading the image but what I'm looking for is a step by step on upgrade a primary and secondary sup and also making sure the secondary sup in slot-2 does not take over as the primary.
Thanks,

Hi Friend,
Just have a look at this link will guide you how to upgrade your redundant sup if you are running CATOS or if you are running Native IOS
http://www.cisco.com/warp/customer/473/161.html#maintask3
HTH, if yes please rate the post
Ankur

Help:Upgraded webdb22 procedure urls fail w/http 404

After upgrading webdb 2.2 to 3.0.6 (on the way to 3.0.9)all procedure urls error with http 404. Packages are valid, packages run when accessed through database objects, created public synonyms for them, granted execute to public, granted schema access to public, ...still the same error. Some of the packages are in different schemas than the site schema. All worked in webdb. Any ideas???

I think that the message below (from your post) might be a clue...
:: Unlocking encrypted volumes: [BUSY]
It shows that decryption is still busy and therefore not completed. You may not have encryption set up correctly and your volumes are not ready.

Upgrade SW Procedures for 15454

Can someone provide me with doc's or knowledge of the steps needed to upgrade from 3.2.1 to 4+. I have 7 node's that need to upgrade and I need to know the good and bad.
Do all have to be upgraded at the same time?
How long does an upgrade typically take?
Can it be done remotely or not recommended? etc.
I know this is kind of open ended but any and all info is appreciated. Thanks

I've only upgraded from 2.1.2 to 2.2.0 during new turn-ups, but those were easily done remotely. You will want to make sure your TCC/TCC+ cards are not in alarm before the upgrade. They don't have to be upgraded right at the same time.

Question on 4510E+R with Sup7E, redundant sups, both IOS and ROMMON upgrade

I found the procedure for a non-disruptive IOS upgrade for a dual-Sup7E 4510E+R using the...
redundancy reload peer
redundancy force-switchover
.....commands to maintain switch availability during IOS upgrades.
Can I use the same procedure for a ROMMON upgrade? I will not have console access and must do it remotely.
This is what I have:
Current ROM: 15.0(1r)SG5
Current IOS: bootflash:cat4500e-universalk9.SPA.03.03.02.SG.151-1.SG2.bin
This is where I want to go:
New ROMMON: cat4500-e-ios-promupgrade-150-1r-SG11
New IOS: cat4500e-universalk9.SPA.03.04.05.SG.151-2.SG5.bin
config-register is currently 0x2102
Current bootvar:
boot system flash bootflash:cat4500e-universalk9.SPA.03.03.02.SG.151-1.SG2.bin
Questions:
1) Can I upgrade the ROMMON first, then IOS?
2) If #1 is true, is there any problems with a temporary scenario where each Sup is running a different ROMMON version?
Proposed proceedure:
3a) Upgrade ROMMON on standby Sup
3b) switchover to make the standby active
3c) Upgrade ROMMON on the original active Sup
3d) Upgrade IOS on the original active Sup
3e) switchover to make the original Sup active
3f) Upgrade IOS on the original standby Sup.
Thanks for any feedback.

Hi Eric,
There are 2 ways to upgrade:
1-Load the IOS version you want to both Sups, change the boot variable, so the switch can load the new IOS after the reboot and finally reboot the chassis.
2-Use ISSU see link:
http://www.cisco.com/c/en/us/products/collateral/switches/catalyst-4500-series-switches/prod_white_paper0900aecd806f0663.html
As for the ROMMON, you usually don't need to upgrade it often and you can always do that later if you need to. I think, some of the newer versions of IOS upgrade the ROMOM as well as the main image but I am not sure exactly for what platforms.
HTH

Router ROMMON upgrade - your opinions

Hello,
I've read in several documents that there is only a need to upgrade ROMMON if there are new features in new ROMMON versions.But, e.g. the ROMMON upgrades for the Cisco 2800 platform, the changelog for 12.4(13r)T5 says "Enhancement for device access in certain Cisco routers.",
12.4(13r)T6 says "DRAM access optimization" and 12.4(13r)T11 says "write/erase timeout increase + status read changes".
Or with the Cisco 2900 platform, the changelog for 15.0(1r)M10 says:
Saving of IOS config sometimes fails on some 2900s (Fix in ROMMON)
-    Bootflash access timing parameter change.
Compact Flash timing parameter changes (ROMMON)
-    Compact flash access timing parameter change.
I think the bug "Saving of IOS config sometimes fails" is not a small one. And I don't know what "DRAM access optimization" or "write/erase timeout increase + status read changes" exactly does.
Is it still true to upgrade ROMMON just in case there are new features which are needed. Or should the ROMMON be upgraded just as the IOS if a new version with fixes is available?
Thank you for your opinions.

Disclaimer
The    Author of this posting offers the information contained within this    posting without consideration and with the reader's understanding that    there's no implied or expressed suitability or fitness for any purpose.   Information provided is for informational purposes only and should not   be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In    no event shall Author be liable for any damages whatsoever (including,   without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Just like with IOS upgrades, generally most would upgrade if there's a new feature or bug fix that pertains to you. When neither is true, most prefer to not upgrade; "it ain't broke, don't fix it".
Consider many software releases are for bug fixes, so although you might not have bumped into a known defect, you may. This would argue for upgrading all maintenance fixes. However, sometimes, maintenance for defects introduces other defects. This argues only do an upgrade if operationally necessary.
So, whether it's an IOS or ROMMON upgrade, it's really what you think is best.
PS:
BTW, for some platforms like the 2800, I recall an effective ROMMON update would force an immediate reload, unlike a IOS upgrade which can be loaded onto flash and the reload scheduled for later. (Suspect this is why Leo insures there's a new IOS on the 2800 before he does the ROMMON upgrade.)

2921 ISR G2 ROMMON Upgrade fails

Hi,
I need to upgrade the rom monitor of a 2921 ISR G2 from currently installed 15.0(1r)M15 to the latest one 15.0(1r)M16.
The upgrade command is running without any problems:
# upgrade rom-monitor file tftp://10.10.10.1/C1900_2900_RM2.srec.SPA.150-1r.M16
Loading C1900_2900_RM2.srec.SPA.150-1r.M16 from 10.10.10.1 (via GigabitEthernet0/0): !!!!!!!!!!!!
[OK - 2819002 bytes]
Platform Field Upgradeable ROMMON LOAD test
ROM: Digitally Signed Production Software
This command will result in a 'power-on reset' of the router!
Continue? [yes/no]: y
ROMMON image upgrade in progress.
Erasing boot flash eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
Programming boot flash pppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppp
Now Reloading
But after the reload the router comes up with the old rom version
System Bootstrap, Version 15.0(1r)M15, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 2011 by cisco Systems, Inc.
Total memory size = 1536 MB - On-board = 512 MB, DIMM0 = 1024 MB
Upgrade ROMMON programming not complete.
Falling to ReadOnly ROMMON
CISCO2921/K9 platform with 1572864 Kbytes of main memory
Main memory is configured to 72/72(On-board/DIMM0) bit mode with ECC enabled
Any ideas how to solve this?
Many thanks!

Hi Leo,
I re-downloaded the ROMmon Image, and I also tried it with older versions (M9, M6) and on a second Cisco 2921 ISR G2 router (which has the M15 version installed): Same result.
Any more ideas?
Thanks!

CRS-1/8 upgrade from 3.9.2 to 4.3.0

Hi everybody!
I'm trying to upgrade a CRS-1/8 from 3.9.2 to 4.3.0
1) It's a CRS-1 with redundant RPs, I think it's not a problem.
http://www.cisco.com/en/US/partner/prod/collateral/routers/ps5763/product_bulletin_c25-663499.html
2) Current rommon version is 1.54. Also looks fine.
http://www.cisco.com/en/US/partner/docs/routers/crs/software/crs_r4.3/rommon/configuration/guide/b_rommon_cg_43xcrs_chapter_0110.html
3) Procedure:
To minimize downtime I used a PCMCIA card with 4.3.0 previously installed in a LAB router.
Without powering down the router I removed both RPs.
I inserted my disk0: with 4.3.0 in RP0 and inserted RP0.
The router started to boot up, but it went into a boot up loop. It didn't show any errors or failures.
I broke the loop with Ctrl+c, and in rommon could't see disk0:.
To recover, I used this procedure, but didn't try the upgrade again.
https://supportforums.cisco.com/message/4045146#4045146
Bootflash was corrupted. I assume I did it myself, but what should I do to prevent this from happening again?
Any advice?
Thanks, Diego.

Hi Diego,
to run 4.3.0 on CRS you need to upgrade rommonA and B with a version ≥ 2.01 beforehand.
Please note we officially support a PIE upgrade N+2. I.e. A direct upgrade from 3.9.2 to 4.3.0 is not supported officially.
It may work, though.
The alternatives you have is either Turboboot or an interim step e.g. 3.9.2 to 4.1.2, then 4.1.2 to 4.3.0.
But nevertheless you have to upgrade rommon first.
Regards
Frank

Upgrading CRS1 to CRS3

Hi guys,
given the following thread and relative official documentation:
https://supportforums.cisco.com/discussion/11298231/ask-expertupgrading-crs1-system-crs3
since the activity would cause several outage hours, I would like to be sure about the correct procedure and confirm the activity plan we are supposed to follow. We will perform the upgrade on 3 nodes which system snapshot is:
- CRS-1 8 slot
- IOS XR 3.9.2
- CRS-8-RP
We purchased the CRS-3-UPGRADE-BUN upgrade hardware and we are going to equip CRS-CGSE-PLUS Service Card and 14X10GBE-WL-XFP.
Our 8 steps draft plan is:
1) upg XR 3.9.2 -> 4.2.3
2) reload
3) upg fabric 40G -> 140G
4) upg RP -> PRP-6G (implicit reload)
5) upg XR 4.2.3 -> 5.2.2 (due to features constraints)
6) reload
7) install 14X10GBE-WL-XFP and/or install CRS-CGSE-PLUS
8) activate Licenses
Any comment or drawback warning?
Thanks in advance

Hello,
Another method you might want to consider is pre-baking the PRPs with 4.2.3 or 5.2.2
If you chose, especially, 5.2.2, then upgrade ROMMON first on all cards (http://www.cisco.com/c/en/us/support/docs/routers/crs-1-16-slot-line-card-chassis/117700-technote-rommon-00.html).
For either code you can simply power down the router, pull out the fabric cards and RPs, and replace them with the CRS-3 fabric cards and PRP.
If you cannot pre-bake the images then you will need to do the RP -> PRP migration or a turboboot on the PRPs, which really a turboboot to 5.2.2 might be faster then taking the hit of upgrading to 4.2.3 -> PRP migration -> upgrade to 5.2.2 but if you do this then again the manual ROMMON upgrade is recommended.
Thanks,
Sam

EBS 12.1.3 Upgrade issue

Hi,
I installed 12.1.1 with the Vision Database on my machines which has a 64 bit Linux 5 update 5 operating system and everything went fine. After that I decided to upgrade to 12.1.3. I installed the following patches in order they are given below :
1) R12.AD.B.DELTA.3 Patch 9239089
2) Patch 9239090
3) Patch 9239095
4) 9817770:R12.ATG_PF.B POST-R12.ATG_PF.B.DELTA.3CONSOLIDATED PATCH
5) 9966055:R12.FND.B [TRANSLATED VERSION OF FNDSCSGN NOT LAUNCHED
The only issues I had was during the compilation of one form library I got an error in Patch 923090 and I said to continue. The patches completed successfully (I think) since I can log into applications. My issue is I have a lot of invalid objects. I tried to manually compile them but failed then followed one of the other threads to run utlrp.sql and utlirp.sql scripts as per (R12.1.1 - Invalid Objects After Patching [ID 1093163.1])
I have followed that document and tried to run but my invalid count stays the same. Here is the snapshot when I query the database :
SQL> SELECT COUNT(*), OWNER FROM DBA_OBJECTS WHERE STATUS='INVALID'
2 GROUP BY OWNER;
COUNT(*) OWNER
1 RE
2 CA
4 PUBLIC
1 HERMAN
228 APPS
2 FLOWS_010500
SQL> @$ORACLE_HOME/rdbms/admin/utlrp.sql
TIMESTAMP
COMP_TIMESTAMP UTLRP_BGN 2012-04-05 07:23:05
DOC> The following PL/SQL block invokes UTL_RECOMP to recompile invalid
DOC> objects in the database. Recompilation time is proportional to the
DOC> number of invalid objects in the database, so this command may take
DOC> a long time to execute on a database with a large number of invalid
DOC> objects.
DOC>
DOC> Use the following queries to track recompilation progress:
DOC>
DOC> 1. Query returning the number of invalid objects remaining. This
DOC> number should decrease with time.
DOC> SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);
DOC>
DOC> 2. Query returning the number of objects compiled so far. This number
DOC> should increase with time.
DOC> SELECT COUNT(*) FROM UTL_RECOMP_COMPILED;
DOC>
DOC> This script automatically chooses serial or parallel recompilation
DOC> based on the number of CPUs available (parameter cpu_count) multiplied
DOC> by the number of threads per CPU (parameter parallel_threads_per_cpu).
DOC> On RAC, this number is added across all RAC nodes.
DOC>
DOC> UTL_RECOMP uses DBMS_SCHEDULER to create jobs for parallel
DOC> recompilation. Jobs are created without instance affinity so that they
DOC> can migrate across RAC nodes. Use the following queries to verify
DOC> whether UTL_RECOMP jobs are being created and run correctly:
DOC>
DOC> 1. Query showing jobs created by UTL_RECOMP
DOC> SELECT job_name FROM dba_scheduler_jobs
DOC> WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>
DOC> 2. Query showing UTL_RECOMP jobs that are running
DOC> SELECT job_name FROM dba_scheduler_running_jobs
DOC> WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>#
PL/SQL procedure successfully completed.
TIMESTAMP
COMP_TIMESTAMP UTLRP_END 2012-04-05 07:24:29
DECLARE
ERROR at line 1:
ORA-00904: "FALSE": invalid identifier
ORA-06512: at line 13
DOC> The following query reports the number of objects that have compiled
DOC> with errors (objects that compile with errors have status set to 3 in
DOC> obj$). If the number is higher than expected, please examine the error
DOC> messages reported with each object (using SHOW ERRORS) to see if they
DOC> point to system misconfiguration or resource constraints that must be
DOC> fixed before attempting to recompile these objects.
DOC>#
OBJECTS WITH ERRORS
4
DOC> The following query reports the number of errors caught during
DOC> recompilation. If this number is non-zero, please query the error
DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors
DOC> are due to misconfiguration or resource constraints that must be
DOC> fixed before objects can compile successfully.
DOC>#
ERRORS DURING RECOMPILATION
4
PL/SQL procedure successfully completed.
Invoking Ultra Search Install/Upgrade validation procedure VALIDATE_WK
Ultra Search VALIDATE_WK done with no error
PL/SQL procedure successfully completed.
However for some reason the job utlrp.sql only shows 4 invalids as shown when I run it. But the number changes once the script is finished and I am not sure why. If I query SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6) now after utlrp.sql has finished running I get the below
SQL> SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);
COUNT(*)
234
But if I query the same query while utlrp.sql is running I get a number as low as 10 I have seen but once the script finishes it goes back up. I don't know what to do. I have run autoconfig on both the db and apps tier. Is there anything anyone can suggest me ? I am totally lost on this.
Thanks..

Hi I did set the disablefast_validate=TRUE and re-ran only utlrp.sql to re-compile now I have a lot more packages compiled but I still have some invalids. I just want to know can I ignore these and move on or are they important packages / objects in APPS which may impact functionality ?
below is the results of the invalid objects.
Thanks
OWNER,OBJECT_NAME,SUBOBJECT_NAME,OBJECT_ID,DATA_OBJECT_ID,OBJECT_TYPE,CREATED,LAST_DDL_TIME,TIMESTAMP,STATUS,TEMPORARY,GENERATED,SECONDARY,NAMESPACE,EDITION_NAME
PUBLIC,WWV_FLOW_LIST_OF_VALUES_DATA,,1006661,,SYNONYM,09-FEB-07,09-FEB-07,2007-02-09:00:33:03,INVALID,N,N,N,1,ORA$BASE
PUBLIC,WWV_FLOW_LISTS_OF_VALUES$,,1006663,,SYNONYM,09-FEB-07,09-FEB-07,2007-02-09:00:33:03,INVALID,N,N,N,1,ORA$BASE
PUBLIC,WWV_FLOW_GENERIC,,1006687,,SYNONYM,09-FEB-07,09-FEB-07,2007-02-09:00:33:03,INVALID,N,N,N,1,ORA$BASE
PUBLIC,WWV_FLOW_FIELD_TEMPLATES,,1006699,,SYNONYM,09-FEB-07,09-FEB-07,2007-02-09:00:33:03,INVALID,N,N,N,1,ORA$BASE
RE,RE_PROFILER,,1207268,0,PACKAGE BODY,17-NOV-04,05-APR-12,2012-04-05:10:52:51,INVALID,N,N,N,2,
HERMAN,RDT_1,,1713973,1713973,TABLE,18-JAN-06,18-JAN-06,2006-01-18:13:18:02,INVALID,N,N,N,1,
APPS,XLA_00707_AAD_C_000026_PKG,,2362389,0,PACKAGE BODY,03-AUG-07,05-APR-12,2012-04-05:10:52:52,INVALID,N,N,N,2,
APPS,XLA_20065_AAD_C_000030_PKG,,2370236,0,PACKAGE BODY,16-AUG-07,05-APR-12,2012-04-05:10:53:05,INVALID,N,N,N,2,
APPS,FSAH_DUPLICATE_PKG,,2385307,0,PACKAGE BODY,23-AUG-07,05-APR-12,2012-04-05:10:53:08,INVALID,N,N,N,2,
APPS,XLA_00707_AAD_C_000044_PKG,,2661674,0,PACKAGE BODY,14-JAN-08,05-APR-12,2012-04-05:10:53:08,INVALID,N,N,N,2,
APPS,MSD_DEM_OBI_DEMANTRA_MV,,3255317,,MATERIALIZED VIEW,09-JUL-08,09-JUL-08,2008-07-09:09:14:28,INVALID,N,N,N,19,
CA,F,,3260665,3260665,TABLE,24-SEP-08,24-SEP-08,2008-09-24:16:00:14,INVALID,N,N,N,1,
CA,G,,3260683,3260683,TABLE,24-SEP-08,24-SEP-08,2008-09-24:16:00:15,INVALID,N,N,N,1,

Multiple Oracle_home (best way to upgrade) ??

hello all,
I was going thru the below link and found this very cool trick that i didnt know.
http://searchoracle.techtarget.com/tip/0,289483,sid41_gci1252556,00.html?track=NL-93&ad=587723&asrc=EM_NLT_1354356
it goes something like this
*My favorite best practice is the one about multiple Oracle Homes. Here it how it goes. When applying a patch or a patchset, I recommend against applying to the existing Oracle Home. Instead, I suggest creating a new Oracle Home, and apply the patches there.
I create the first Oracle Home at /app/oracle/db_1, for instance. When a patch comes out, I install the whole Oracle software in a different home -- /app/oracle/db_2 -- and then apply the patch there. During the process of installation and patch application, the database is up and running, as it runs off the home /db_1. When the outage window comes, all I have to do is to shut down Oracle; change Oracle Home to db_2 and bring the database up. If there is a problem, I can reset the Oracle Home back to the old one.
So, here is the conventional approach:
1. Shut down the database
2. Apply patch to the Oracle Home
3. Start the database
4. In case of problems:
5. Shut down the database
6. Roll back the patch
7. Start the database
Steps 2 and 6 could take as much as three hours depending on the amount of patching. The database is down during these times.
In the new approach:
1. Install new Oracle Home
2. Apply the patch to the new Home
3. Shut down the database
4. Change Oracle Home to the new location
5. Start the database
6. In case of problems:
7. Shut down the database
8. Change Oracle Home to the old one
9. Start the database
The database is down only during steps 4 and 8, which takes a couple of minutes at the most, not hours.*
But my question comes here...first of all is it possible ?? i am sure it is becoz Arup Nanda one of the know oracle guys wrote this article. so here are my Q?
1- So if i get this right...if i want to upgrade to 11g...and my database is on 10g...all i need to do this create a new 11g home...shutdown my 10g database...set my oracle_home to 11g and start my database up...and its all upgraded ????
2- Another thing that worries me is how this might behave in RAC environment. Any idea
on that? i know RAC provides the rollover upgrade so we might
not need this. but would be cool to know how it behaves...ANY IDEAS ?
3- Also, I wonder how CRS and ASM home like this idea ??

Basically when you switch from the old home to the new Oracle home you are following manual database upgrade procedures so you would need to run whatever scripts are contained in the instructions. Normally for an upgrade that is catalog and catproc and you would run these immediately after bringing the database up on the new home. For a patch there might be an upgrade script or no database level scripts may be necessary. That is the patch may effect only the binary.
What we actually do is in test install new copy of existing Oracle then patch/upgrade to current level. Next build an empty database and populate it. Next test. When OK shut it down and apply patch. Startup and follow Readme or Upgrade manual procedures. If test works fine and the upgrades tests OK then we remove the new test db, switch the actual in-use test databases over to the new patched home, run upgrade scripts as necessary, and continue.
After a few weeks we start getting maintenance windows to do production. Since we have multiple databases we usually do not do all of them at once.
HTH -- Mark D Powell --

Upgrade question on WSC4507R-E

HI all,
I have a couple questions about upgrading the IOS on our WS C4507R-E. We have 3 installed cards:
2 WS-X45-SUP6L-E supervisor modules running 12.2(54)SG * running Active/Standby
1 WSX4606-X2-E 10G card
ROMMON is currently at 12.2(44r)SG5
I'm a bit confused by all the available IOS "trees" but I am pretty sure I want to upgrade to: 15.0.2-SG9(MD), at least that is what is recommended when I search for IOS downloads. I don't think I need to upgrade ROMMON, I believe I'm at the minimum required version for this IOS. I may upgrade ROMMON after IOS, there was a note about not doing it first on older IOS versions.
So, my questions are....is the above info correct, regarding ROMMON and the recommended IOS version for my platform?
If so, how would I do the upgrade on the redundant sup modules? The instructions I found didn't address redundant sups.
Anything I need to be aware of that I haven't mentioned?
Thanks for any assistance you can provide!

Hi Eric,
There are 2 ways to upgrade:
1-Load the IOS version you want to both Sups, change the boot variable, so the switch can load the new IOS after the reboot and finally reboot the chassis.
2-Use ISSU see link:
http://www.cisco.com/c/en/us/products/collateral/switches/catalyst-4500-series-switches/prod_white_paper0900aecd806f0663.html
As for the ROMMON, you usually don't need to upgrade it often and you can always do that later if you need to. I think, some of the newer versions of IOS upgrade the ROMOM as well as the main image but I am not sure exactly for what platforms.
HTH

How to handle the interfaces in upgradation from 4.6c to ECC6.0

we are going for the upgrade from 4.6c to ECC6.0
actually we are using n number of interfaces like webmethods, informatica powercenter, ALE, EDI....
powercenter was created some programs in SAP R/3, when we are upgrading from 4.6c to ECC6.0, what kind of issues we will face regarding this informatica. what is strategy we have to follow to upgrade this informatica in SAP, if anyone have the documents regarding informatica powercenter please help me and guide me
if anyone have documents regarding this interfaces upgradation or procedures bestpractices, common issues please forward me
thanks,
chandra

thanks

6500 Upgrade Rommon procedure

Similar Messages

Maybe you are looking for