I have two physical servers, hosting 6 two node RAC databases running in version (both grid and database).

I'm told to have the grid software in version and the databases in the same version since there could be future plans to upgrade the database to a higher version.

Plan is to create new grid software ( and create a new ASM instance with new luns and create diskgroups with the new luns, create a new database and then export/import from old database to this new database. So that the new database will have the Grid and ASM running in and database in same

Perform the same activity for all 6 databases, post that uninstall software and binaries, resulting in the required result wherein only one ASM instance will be running (

Is the above mentioned activity feasible? I'm not in a situation to upgrade grid to higher version as I cannot afford downtime. But then the above mentioned activity will have two ASM instances running at the same time for some period.

I can add/clear doubts if the mentioned activity is unclear.

1 Answer 1


I'm sure that such approach is feasible. Technically Grid is fully compatible with RDBMS You just need to be accurate in some parameters. I believe that in a new grid you won't use very specific "compatible.rdbms" or "compatible.asm" attributes' value ('', e.g.) which might conflict with database. Ideally you should use the same default '' value in target GI.

You can clone databases from old to new GI, copy specific tablespaces if your schemas are compatible with transport_tablespaces approach. You can use logical dump created with datapump. It might be very useful to use dbms_file_transfer package to copy datafiles (and dumpfiles created by datapump as well) directly from source ASM to target ASM diskgroups.

Good luck.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.