OCP 1Z0 053 94

94.Multiple RMAN sessions are connected to the database instance. 
Examine the following output when backup commands are running in server sessions: What could have 
helped you to correlate server sessions with channels? 

A. Implement RMAN multiplexing 
B. Set the DEBUG ON in the RMAN script 
C. Specify the command ID in the RMAN script 
D. Use a tag with the RMAN BACKUP command 
Answer: C 

http://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmarchi.htm#BRADV105

RMAN Channels

The RMAN client directs database server sessions to perform all backup and recovery tasks. What constitutes a session depends on the operating system. For example, on Linux, a server session corresponds to a server process, whereas on Windows it corresponds to a thread within the database service.

The RMAN client itself does not perform backup, restore, or recovery operations. When you connect the RMAN client to a target database, RMAN allocates server sessions on the target instance and directs them to perform the operations.

An RMAN channel represents one stream of data to a device, and corresponds to one database server session. The channel reads data into PGA memory, processes it, and writes it to the output device. See "Basic Concepts of RMAN Performance Tuning" for a low-level description of how channels work.

Most RMAN commands are executed by channels, which must be either configured to persist across RMAN sessions, or manually allocated in each RMAN session. As illustrated in Figure 3-2, a channel establishes a connection from the RMAN client to a target or auxiliary database instance by starting a server session on the instance.

Figure 3-2 Channel Allocation