How to Recreate AWR Jobs in OEM to upload data to AWR Repository without Dropping DB from AWR
(Doc ID 2599586.1)
Last updated on DECEMBER 03, 2019
Applies to:Enterprise Manager for Oracle Database - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
A database in OEM is configured as a repository for AWR Warehouse. This AWR repository can be single instance database or RAC with multiple instances.
The databases which are added as source databases to AWR, will upload AWR data to this AWR Warehouse repository. These source databases can be single instance database or RAC with multiple instances. All these source databases will have a CAW_TRANSFER job to upload the AWR dumpfiles per instance.
But some of the databases have not been uploading as expected. When verified these databases, found that these have lost the CAW_TRANSFER jobs. No upload is happening to AWR repository database.
Now you need to restart/re-create these CAW_TRANSFER job on every source database/instance where it is not running, to make sure the AWR data upload happening fine. Restarting/re-creating these CAW_TRANSFER job will not erase/loose any historic data uploaded to AWR repository database so far.
Note: Removing the database from AWR and adding it back will restart the CAW_TRANSFER job, but it will erase all the historic data of that particular database uploaded so far to AWR repository warehouse. So this is not recommended.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document