Autoupgrade looks to be a much simpler way to perform the upgrades, thanks for the demo! One question: if I want to upgrade, like this - do the 12c and 19c instances both need to be running, at the same time, when I perform the analyze? In the past (after testing, of course), we just shutdown a previous instance, before opening (in upgrade mode) it again in the new version - then upgrade manually. So, never two instances up, at the same time. As the CDB needs to be created beforehand - does this mean that both need to be opened concurrently? Or, is it possible to shut down the original 12c instance, then create the new 19c CDB - then follow your steps from here? Memory allocation is my reason for asking :)
Hi Ken, Thanks for your feedback. Much appreciated. Both databases must be running in advance - the non-CDB database and the target CDB. When the non-CDB is plugged into the CDB it is shut down, and added as a PDB into the CDB. So in the end there will only be one instance running. If you are concerned about the memory usage, you can create the CDB with little memory to begin with. In AutoUpgrade you can add parameters before, during, and after upgrade. I suggest that you raise the memory in the "during" and "after" pfile setting. That way, the CDB will have more memory once you plug in the non-CDB (and thus the non-CDB is no longer running). Regards, Daniel
Hi, That is doable as well. See this blog post for information on how to set the parameter TARGET_PDB_COPY_OPTION: mikedietrichde.com/2020/07/21/more-information-on-autoupgrades-target_pdb_copy_operation Regards, Daniel
No. AutoUpgrade is available in all releases of Oracle Database. If you want to get the latest version, you must have a support agreement. Regards, Daniel
Hi, You can use this feature for ASM as well. See this blog post for information on how to set the parameter TARGET_PDB_COPY_OPTION: mikedietrichde.com/2020/07/21/more-information-on-autoupgrades-target_pdb_copy_operation Regards, Daniel
@@upgradenow Thanks, and What about Cluster? If i upgrade cluster with traditiobnal Rolling upgrade and use autoupgrade.jar to upgrade the database, will that do?
It’s always refreshing watching you demo
Thanks for the nice feedback. I will pass it on to Mike.
Regards,
Daniel
Thank you so much.^^ So great seminar.
Glad you enjoyed it!
Thank you very much Mike :-).Awesome , Happy Learning, splendid explanation. Expecting more Videos for continuous learning ...
Glad you liked it!
Thank you very much!
You're welcome! We're glad you liked it. Be sure to subscribe for even more great content.
Regards,
Daniel
Autoupgrade looks to be a much simpler way to perform the upgrades, thanks for the demo!
One question: if I want to upgrade, like this - do the 12c and 19c instances both need to be running, at the same time, when I perform the analyze?
In the past (after testing, of course), we just shutdown a previous instance, before opening (in upgrade mode) it again in the new version - then upgrade manually. So, never two instances up, at the same time. As the CDB needs to be created beforehand - does this mean that both need to be opened concurrently? Or, is it possible to shut down the original 12c instance, then create the new 19c CDB - then follow your steps from here?
Memory allocation is my reason for asking :)
Hi Ken,
Thanks for your feedback. Much appreciated.
Both databases must be running in advance - the non-CDB database and the target CDB. When the non-CDB is plugged into the CDB it is shut down, and added as a PDB into the CDB. So in the end there will only be one instance running.
If you are concerned about the memory usage, you can create the CDB with little memory to begin with. In AutoUpgrade you can add parameters before, during, and after upgrade. I suggest that you raise the memory in the "during" and "after" pfile setting. That way, the CDB will have more memory once you plug in the non-CDB (and thus the non-CDB is no longer running).
Regards,
Daniel
Thank you very much Mike,
How about source(11.2.0.4) and target(19c) on different servers with target on ASM?
Hi,
That is doable as well. See this blog post for information on how to set the parameter TARGET_PDB_COPY_OPTION: mikedietrichde.com/2020/07/21/more-information-on-autoupgrades-target_pdb_copy_operation
Regards,
Daniel
Is there a license cost for this tool?
No. AutoUpgrade is available in all releases of Oracle Database. If you want to get the latest version, you must have a support agreement.
Regards,
Daniel
How can we use this for ASM/RAC?
Hi,
You can use this feature for ASM as well. See this blog post for information on how to set the parameter TARGET_PDB_COPY_OPTION: mikedietrichde.com/2020/07/21/more-information-on-autoupgrades-target_pdb_copy_operation
Regards,
Daniel
@@upgradenow Thanks, and What about Cluster? If i upgrade cluster with traditiobnal Rolling upgrade and use autoupgrade.jar to upgrade the database, will that do?
@@rahulwankhede99 Yes it should. The GI upgrade and database upgrade are two separate processes.
Regards,
Daniel