Database Administration (MOSC)

MOSC Banner

Recover from an Archive Log Directory reached 100% full.

edited Mar 30, 2015 5:34PM in Database Administration (MOSC) 1 commentAnswered ✓

Morning,

Oracle Reps are on site to fix our broken tape system.

Unfortunately, during the repair wait our archive log directory reached 100%.

Archive logs were physically preserved by manually copying the files to another directory.

(Q)Before running the full backup what steps should I take to prevent getting RMAN errors because we have archive logs in another directory?

If I catalog them would the Netbackup process go to that physical location and back them up?

Is it best to just tar the archive logs from both directories, run the crosscheck RMAN command and then backup the database?

I know that I could create an alternate destination for future archive logs but this would not let oracle know where I had manually placed the archive log files prior to this to free up space.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center