Red Hat Bugzilla – Bug 504268
[RFE] Check Oracle tablespace capacity before importing package metadata
Last modified: 2015-01-04 16:56:54 EST
Created attachment 346622 [details]
Exception during satellite-sync -- tablespace usage exceeding issue
Description of problem:
During import of package metadata in satellite-sync the exception was thrown about inability of extending Oracle index.
But no advise of how to resolve the issue (would be nice to see something similar to: "check/extend your Oracle tablespaces")
Actually the simple "db-control extend DATA_TBS" is resolving the issue.
So, is it possible to check the tablespace capacity first: before starting package metadata import process, and in case of possible collisions print out some helpful toDo-s?
Attached is a log of this exception.
Version-Release number of selected component (if applicable):
Always when DATA_DBS usage is near to 100%.
Steps to Reproduce:
1. Import some channels up to getting DATA_DBS Oracle tablespace usage close to 100% usage. (to check it su as "oracle" and run "db-control report").
2. Then start sync of one more big channel.
An exception should thrown out. Process is interrupted and not possible to recover without extending tablespace size.
Not to start package metadata importing process before checking the capacity of DATA_DBS.
Not for 5.3.0 - too late in cycle, moving off to sat600-triage for review for post 5.3.0 inclusion.