just for another scenario, if upgrading crs will fail. - shutdown db and and crs (optional) - install 10.1.0.4 on different directory - disable cluster db - upgrade the software & db to 10.2.0.3 - if successful, install fresh crs and software 10.2.0.1 upgrade it to 10.2.0.3 - open the db by new crs and db software (clusterable) regards ujang On 6/27/07, Yavor Ivanov <Yavor_Ivanov@xxxxxxxx> wrote:
Hello, gurus We are planning upgrade from 10.1.0.4 to 10.2.0.3 of HP-UX PA-RISC based system. Everything is on raw devices (no CFS or ASM). We can afford downtime (starting Friday evening). I am planning it this way: - shutdown everything. make lots of backups - install 10.2.0.1 CRS. It wll upgrade OCR - install 10.2.0.3 patchset on CRS home. It may patch the OCR - start the database (still on 10.1.0.4) to see if CRS is fine - shutdown the database. - install 10.2.0.1 database software + patchset 10.2.0.3 - upgrade the database. I've made lots of database upgrades, but never upgraded CRS. All I found in metalink and the docs is how to make rolling upgrade. So I think non-rolling upgrade have to be quite straightforward. I want to ask if anybody of you have done that and is there any problem you encountered -- Regards, Yavor Ivanov Senior Database Expert Stemo Ltd -- //www.freelists.org/webpage/oracle-l
-- regards ujang -- //www.freelists.org/webpage/oracle-l