Oracle backup job goes into queued state indefinitely when excludes are defined in Backup Exec
| Article:TECH190660 | | | Created: 2012-06-08 | | | Updated: 2012-06-08 | | | Article URL http://www.symantec.com/docs/TECH190660 |
| NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made. |
Problem
Oracle backup job goes into queued state indefinitely when excludes are defined in the backup job or globally.
Solution
Workaround:
Remove the excludes from the backup job. Also remove any global excludes if defined.
OR
Run DBA initiated backp to backup Oracle databases.
Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.
This issue is currently under investigation by Symantec Corporation. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release. If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Symantec Sales representative or the Symantec Sales group to discuss these concerns. For information on how to contact Symantec Sales, please see www.symantec.com Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.
|
|
| Source | ETrack |
| Value | 2698277 |
| Description | ORACLE: Backup job goes to queued state indefinitely when selections contain exactly one exclude item |
Related Articles
Article URL http://www.symantec.com/docs/TECH190660
Terms of use for this information are found in Legal Notices
Thank you.