My Oracle Support Banner

Rman Tape Restore is Not Parallelising Despite Having Multiple Channels Allocated (Doc ID 351922.1)

Last updated on APRIL 03, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 9.2.0.1 to 10.2.0.3 [Release 9.2 to 10.2]
Information in this document applies to any platform.
This problem can occur on any platform.

Symptoms

RMAN tape restore of database using multiple channels (the same number as used for the backup) does NOT
parallelise the restore process.

RMAN debug trace shows 4 channels were allocated and 4 distinct pl/sql programs were generated to do the restore in parallel however only channel 1 runs.

For each of the other channels we see :

DBGRPC:        krmqgns: channel <channel_name> could not find any other channel to run step 4, trying anyway (krmqgns)
DBGMISC:       channel <channel_name> could not lock media [PORAPOOL] [15:40:25.164] (krmqgns)
DBGRPC:        krmqgns: channel <channel_name> could not find any other channel to run step 5, trying anyway (krmqgns)
DBGMISC:       channel <channel_name> could not lock media [PORAPOOL] [15:40:25.164] (krmqgns)
DBGRPC:        krmqgns: channel <channel_name> could not find any other channel to run step 6, trying anyway (krmqgns)
DBGMISC:       channel <channel_name> could not lock media [PORAPOOL] [15:40:25.164] (krmqgns)
DBGRPC:        krmqgns: no work found for channel <channel_name> (krmqgns)

The media manager is IBM Tivoli Data Protection for Oracle V 5.3

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.