Troubleshooting RMAN<\/p>\n\n\n\n
Run the following command to find if RMAN sessions exist in the database instance (format the output for readability):<\/p>\n\n\n\n
SELECT p.SPID,
s.EVENT,
s.SECONDS_IN_WAIT AS SEC_WAIT,
sw.STATE,
s.CLIENT_INFO
FROM V$SESSION_WAIT sw,
V$SESSION s,
V$PROCESS p
WHERE sw.EVENT LIKE ‘?ckup%’
AND s.SID=sw.SID
AND s.PADDR=p.ADDR;<\/p>\n\n\n\n
If the sessions are “WAITING” for resources, then kill the sessions using OS command “kill -9” at OS level (prompt). <\/p>\n\n\n\n
Some platforms include a command-line utility called orakill that enables you to terminate a specific thread. From a command prompt, run the following command, where sid identifies the database instance to target, and the thread_id is the SPID value from the query. <\/p>\n\n\n\n
orakill sid thread_id<\/p>\n\n\n\n
And restart the backup process.<\/p>\n","protected":false},"excerpt":{"rendered":"
Troubleshooting RMAN Run the following command to find if RMAN sessions exist in the database instance (format the output for readability): SELECT p.SPID, s.EVENT, s.SECONDS_IN_WAIT AS SEC_WAIT, sw.STATE, s.CLIENT_INFOFROM V$SESSION_WAIT sw, V$SESSION s, V$PROCESS pWHERE sw.EVENT LIKE ‘?ckup%’AND s.SID=sw.SIDAND s.PADDR=p.ADDR; If …<\/p>\n