Automic Workload Automation

Hi,

The Oracle database which hosts our UC4 database schema get's patch every quarter.

For production, we always bring down the Engine during this patching.

For our test environment, we never have brought down our engine during Db Patching and there have been no repercussions.

During patching our DB goes down for between 7-15 minutes.

For the most recent test DB patch, we did notice slowness with all Jobs and subsequently and had to recycle our engine to fix.

Just wondering what others out there do when their DB goes down for a short period of time like this?

Do you always bring down engine?

Thanks,

John.

Hi

Yes.

Except its a hickup - e.g. caused by a resource switch (virtual DB server was switched to another host)

cheers Wolfgang

Hi,

for a scheduled maintenance window I would say yes, it will make the stop of Oracle faster and its downtime window faster.

1st: I would recommend to stop the client in the AE and have a look that nothing is in status generating and no scheduled file-transfer, maybe transferring a huger file is running. This should also not the time where the AE Utility Reorg, Unload, Load, ... is scheduled - Please check! At least check your schedule objects if there is any activation defined during the time the AE is down.

2nd: If you don't see anything in status generating stop the AE with shutdown (no immediate stop).

3rd: Now you can give a go or green light to the Team what is doing the upgrade. A Oracle shout down transactional or immediate should be fast now an not blocking them because of open transactions.

4th: after Patch window is finished start the AE, check that all Agents are reconnected well and your schedule object that nothing has been skipped in the time frame where the AE and Oracle was down. If required please start it out of the schedule object manually.