Patching Exadata cloud@customer (ExaCC) using console

In previous post, we have discussed, how to patch the db,grid and domU on ExaCC using Exadbcpatchmulti http://parwezexa.com/patching-exadata-cloud-at-customerexacc-using-exadbcpatchmulti/ utility .

In todays post , I will show how to do the same using the ExaCC console .

ExaCC console url is provided by Oracle to customers after they provision the private cloud machine in respective customer data centers .

ExaCC console is a powerful utility for creation,maintenance of resources of your private Exadata machine using few simple clicks .

This is how the home page of ExaCC console looks like . It will show you the current resources, like cpu,memory,storage,ips you have on your private Exadata machine.

Next, click on the database which you want to path, it will land you the specific database pages , which have all details about the database .

Go to administration , It will show you the patches available for the specific database .

Choose which patch set release you want to apply . Then run the Precheck by clicking the sandwich menu , available on right side of the patch.

Once precheck completed, the patch menu will look something like this . A verified sign indicates that precheck is completed successfully.


After successful completion of precheck , with no conflicts found . Its time to apply the actual patch .

Again, go to the same specific DB page and go to administration . Click the sandwich menu available on right side of the selected patch , and click Patch.

It will ask for some mandatory notes , write anything relevant and go ahead with clicking patch .

To check the apply status of the patch , Go to console home and then activity .

To check the status of the patch go to console home and then activity

After successful completion of patch , the activity will show something like this to confirm whether the patch is applied or failed .

Successful Patch
Failed Pathc

 1,087 total views,  1 views today

Leave a Reply

Your email address will not be published. Required fields are marked *