Databases Reference
In-Depth Information
Solution
You can find out the number of RMAN server sessions using this formula:
Number of sessions = C+N+2
where the following is true:
•
C is the number of channels allocated.
•
N is the number of “connect” options used in the allocate channel commands (if no connect
options are used, N has the value of 1).
If you're using a recovery catalog, there are always at least two sessions: one for connecting to the recovery
catalog and the other for the default connection to the target database. The default connection is needed to perform
tasks such as applying archived redo logs during a recovery task.
You can find out exactly who is currently running the RMAN client by issuing a command such as
ps -ef
on a
Unix system:
RMAN> host 'ps -ef|grep rman';
oracle 15960 7412 2 11:57 pts/2 00:00:00 rman target /
oracle 15986 15960 0 11:57 pts/2 00:00:00 /bin/bash -c ps -ef|grep rman
oracle 15988 15986 0 11:57 pts/2 00:00:00 grep rman
host command complete
RMAN>
Having a list of RMAN client sessions like this, you can pick one in which you're interested. Say, for example, that
you're interested in the session for process ID 9255. You can then issue the following command, which will find all the
child processes associated with that instance of the client:
RMAN> host 'ps -ef|grep 15960';
oracle 15960 7412 0 11:57 pts/2 00:00:00 rman target /
oracle 15965 15960 0 11:57 ? 00:00:00 oracleorcl (DESCRIPTION=(LOCAL=YES)
(ADDRESS=(PROTOCOL=beq)))
oracle 15966 15960 0 11:57 ? 00:00:00 oracleorcl (DESCRIPTION=(LOCAL=YES)
(ADDRESS=(PROTOCOL=beq)))
oracle 16041 15960 0 11:58 pts/2 00:00:00 /bin/bash -c ps -ef|grep 15960
oracle 16043 16041 0 11:58 pts/2 00:00:00 grep 15960
host command complete
RMAN>
To identify the Oracle session ID of the RMAN session, look for the following types of messages in the RMAN log:
channel ch2: sid=12 devtype=SBT_TAPE
On a Windows server, you can use the Task Manager to identify the RMAN client sessions. Then you can drill
down into associated server processes by clicking the Process tab and clicking the relevant server process under the
process list.
