7 Replies Latest reply on Dec 11, 2012 12:09 PM by 961716

    why does it show RMAN is still running...

      I am using RMAN in Oracle 11.2.

      I tried kicking off RMAN a few times to test my script, and then did a kill -9 on the process numbers.
      But I found out that RMAN was still running in the database, and was using a lot of System I/O (from what I could see in OEM).

      I see the session in Toad and killed them from within Toad, and the system I/O dropped off.
      I could also see in OEM that my RMAN processes were killed off.

      So, first, why didn't the kill -9 actually kill the processes running in the database?
      Next, when I still look in V$RMAN_BACKUP_JOB_DETAILS, it shows I have some jobs still running.

      How do I terminate these processes?

      I need to do this as soon as possible. Please help if you can.
        • 1. Re: why does it show RMAN is still running...
          Please, give more details about this RMAN process running.

          Post the information shown in v$session, about this RMAN process.

          • 2. Re: why does it show RMAN is still running...
            There is nothing there any longer.

            But it still shows up in V$RMAN_BACKUP_JOB_DETAILS.
            SQL> select username, program, status from v$session where status = 'ACTIVE' and username is not null order by 1;
            USERNAME                 PROGRAM                                          STATUS
            ------------------------ ------------------------------------------------ ---------
            ARADMIN                  oracle@cassini (P003)                            ACTIVE
            ARADMIN                  arserverd@gonzo.nnet (TNS V1-V3)                 ACTIVE
            ARADMIN                  oracle@cassini (P002)                            ACTIVE
            DBSNMP                   emagent@cassini (TNS V1-V3)                      ACTIVE
            SYS                      sqlplus@cassini (TNS V1-V3)                      ACTIVE
            SYSMAN                   OMS                                              ACTIVE
            6 rows selected.
            SQL>  select username, program, status from v$session where username = 'SYS';
            USERNAME                 PROGRAM                                          STATUS
            ------------------------ ------------------------------------------------ ---------
            SYS                      OMS                                              INACTIVE
            SYS                      sqlplus@cassini (TNS V1-V3)                      ACTIVE
            SYS                      OMS                                              INACTIVE
            3 rows selected.
            But, yet if I query V$RMAN_BACKUP_JOB_DETAILS, you see it says it is running.
                SESSION_KEY INPUT_TYPE    STATUS    START_TIME     END_TIME           HRS
            --------------- ------------- --------- -------------- -------------- -------
                       4252 DB INCR       COMPLETED 12/10/12 01:00 12/10/12 01:07     .13
                       4258 DB INCR       RUNNING   12/10/12 13:53
                       4260 DB INCR       RUNNING   12/10/12 13:57
                       4262 DB INCR       RUNNING   12/10/12 14:03
                       4264 DB INCR       RUNNING   12/10/12 14:06
                       4266 DB INCR       RUNNING   12/10/12 14:08
            • 3. Re: why does it show RMAN is still running...
              Well, let's see if I can get back to the basic question:

              why after I did a kill -9 on the rman processes and confirmed there were no more processes (ps -ef |grep rman), that there were still rman processes running in the database that were using up lots of I/O?
              • 4. Re: why does it show RMAN is still running...

                V$RMAN_BACKUP_JOB_DETAILS is based on V$RMAN_STATUS which stores its data in the control file. The data will disappear when there is space pressure in the control file.

                Best Regards

                1 person found this helpful
                • 5. Re: why does it show RMAN is still running...
                  Thank you mseberg.

                  I selected * from V$RMAN_STATUS where RECID = '4266' and it shows that the SID is '0'.
                  Very strange.

                  Naturally for my own curiousity, I selected from v$session where sid='0', but didn't get anything back.

                  • 6. Re: why does it show RMAN is still running...
                    Hello again;

                    Kind of hard to recreate but I only get this on my test system :
                    SQL> select distinct status from V$RMAN_STATUS;
                    COMPLETED WITH ERRORS
                    SQL> select distinct status from V$RMAN_BACKUP_JOB_DETAILS;
                    If I killed a running RMAN job I might get the recreate.

                    h2. Later

                    Found this :

                    Bug 11872103  RMAN RESYNC CATALOG very slow / V$RMAN_STATUS incorrectly shows RUNNING

                    I'm already patched so I have no chance to recreate if this is it.

                    Best Regards


                    Edited by: mseberg on Dec 10, 2012 3:02 PM
                    1 person found this helpful
                    • 7. Re: why does it show RMAN is still running...
                      Thanks again Mseberg.

                      yes, I believe I may have hit the bug you mentioned. Thank you for finding it.
                      It is disturbing that the bug also causes catalog resync to run slow.

                      Now, I still need to understand how to kill an RMAN job.
                      I'm going to open this as a separate thread since this was the original issue that caused performance impact.