Thank u so much for this helpful tutorial , i want to ask u if u have any tutorial on how we can read awr reports
@InfraXpertzz2 жыл бұрын
Glad you liked it. Sorry to say but as of now we don't have any tutorials on how to read awr report
@kirankumar-np7tc Жыл бұрын
Dont need to install 19c yum packages on both nodes ?
@thiruardura2 жыл бұрын
Can we use this method/steps to upgrade Oracle 12c SE2 RAC to Oracle 19c EE RAC?
@InfraXpertzz2 жыл бұрын
No sorry. You need to upgrade from se2 to ee separately
@thiruardura2 жыл бұрын
@@InfraXpertzz DBUA will not upgrade the SE2 RAC DB to 19c EE RAC DB?
@InfraXpertzz2 жыл бұрын
No it won't. You can give it a try. But it's a totally separate process
@Ayanasaiyad35323 жыл бұрын
Could you share this document link for download
@InfraXpertzz3 жыл бұрын
This session being upgrade using dbua, no documents have been made. U can refer to the silent installation video, where the blog link has been kept with
@Ayanasaiyad35323 жыл бұрын
@@InfraXpertzzthanks for reply could you share this silent upgrade doc link or drive link
@InfraXpertzz3 жыл бұрын
You can check all documents in the below link. Requesting you to go through them infraxpertzz.com/oracle-blogs/
@InfraXpertzz3 жыл бұрын
My bad. The upgrade using dbua blog is also present in the below link infraxpertzz.com/step-by-step-upgrade-oracle-rac-grid-infrastructure-and-database-from-12c-to-19c/
@Ayanasaiyad35323 жыл бұрын
Thanks
@SydneyIndian3 жыл бұрын
I did this upgrade successfully before 3 months. I did dry run for upgrade a day before actual upgrade, it helped me save 3 hours of activity time. As you said issues occur during dry run especially due to a bug services restart during dryrun. 1) to over come that bug we have to apply latest RU patch in 19c grid home before even executing gridsetup.sh for dry run. let me know if you want me to post the metalink document id for same. 2) as soon as u apply latest ru after unzipping grid home, you will face another issue due to ocw bug and u have to apply a patch with bug number 3070425 i guess, post applying both u will be able to run dry run without any issues. Also ensure umask of root is set as 0022 before running rootupgrade.sh and root.sh. i will see full video and add more experience.
@InfraXpertzz3 жыл бұрын
Thanks for the great comments. Please share your experience, which would help both myself and others gain more knowledge
@SydneyIndian3 жыл бұрын
@@InfraXpertzz sure. I had to plan quite extensively. As i ensured that the cluvfy returns successful before grid dry run upgrade, it was simply next,next, finish for me across all steps. I will comment steps and also learnings in this same comment.
@InfraXpertzz3 жыл бұрын
One more bug which is not mentioned in the video, even after notifying for applying patches prior upgrade in the dry run, the dry run was successful. Ideally the dryrun shouldn't be successful until and unless you have applied the prerequisite patches
@SydneyIndian3 жыл бұрын
@@InfraXpertzz you should have patched till jan-2020 proactive bundle patch as per standard requirement. But below two patches are also required to get dry run and actual grid upgrade to run successfully as per plan without any issues. 1) Unzip Grid home and move the unzipped binary to location in /u01 then apply latest RU to the unzipped 19c grid binary home. Follow the metalink article ID:1410202.1 to understand how to apply ru and oneoff patch before running dryrun. Using the command run and apply the latest ru in grid home. This should be done post moving software to location and before dry run. Also ensure inventory backup is available before this step. 2) even after applying latest RU in previous step now you will face another bug related to OCW for grid setup, after applying latest ru on unzipped 19c grid home, older patches will become invisible. Follow the metalink document ID:32568731.8 and apply the one off patch also before dry run to over come this issue. 3) enable sudo access for both grid and db os user and run cluvfy as root with syntax as type sudo and user grid os user name. This should return successful without any warnings at all. If above procedure is successful dry run and actual upgrade will be smooth over all.