What could have helped you to correlate server sessions with channels?

Multiple RMAN sessions are connected to the database instance.
Examine the following output when backup commands are running in server sessions:
SQL> SELECT s.sid, p.spid, s.client _info FROM v$process p, v$session s
WHERE p.addr = s.paddr
AND CLIENT _INFO LIKE ‘rman%’;
SID SPID CLIENT_INFO
— —– —————————-
103 25280 rman channel 1=ORA_DISK_1
151 25292 rman channel 1=ORA_DISK_2
What could have helped you to correlate server sessions with channels?

Multiple RMAN sessions are connected to the database instance.
Examine the following output when backup commands are running in server sessions:
SQL> SELECT s.sid, p.spid, s.client _info FROM v$process p, v$session s
WHERE p.addr = s.paddr
AND CLIENT _INFO LIKE ‘rman%’;
SID SPID CLIENT_INFO
— —– —————————-
103 25280 rman channel 1=ORA_DISK_1
151 25292 rman channel 1=ORA_DISK_2
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



Leave a Reply 1

Your email address will not be published. Required fields are marked *


iimax

iimax

RUN { SET COMMAND ID TO ‘sess1’; BACKUP DATABASE; }
RUN { SET COMMAND ID TO ‘sess2’; BACKUP DATABASE; }
SELECT SID, SPID, CLIENT_INFO FROM V$PROCESS p, V$SESSION s WHERE p.ADDR = s.PADDR AND CLIENT_INFO LIKE ‘%id=sess%’;

SID SPID CLIENT_INFO
—- ———— ——————————
11 8358 id=sess1
15 8638 id=sess2
14 8374 id=sess1,rman channel=c1
9 8642 id=sess2,rman channel=c1