RMAN Session in Hung Status

Hi ,
We have observed  few issue while backing up the  archive logs through tapes ( Symantec Backup). Backup team told us that they are not able to see the jobs at their end running , while we are triggering the backup . Later on we find lot of rman session active in the database ( 27 RMAN Session in v$session)
I have few question :
> If there are already rman session which are in hung state , Even if we trigger the new backup , Will that complete trigger or they will also went into the hug state. ( I think new session will also goes into the hung state) . Symantec backup team said they don't have any issue at their end.
>Generally we kill the all the backup processes at OS level ( ps -ef | grep rman & ps -ef | grep backup ) , Is that possible still few RMAN session doesn't get killed  from v$session. ( I am not sure about this , As per my understanding , if we kill any rman session at the OS level , it should be killed from the v$session)
Database Version : 11gR2
OS : AIX 6.1
BACKUP : Symantec backup
REgards
Sourabh GUpta

Hi ,
We are just trying to find the RCA for this , I have few doubts based on that I will troubleshoot this :
> If there are already rman session which are in hung state , Even if we fire  the new backup , Will that complete  or they will also went into the hug state. ( I think new session will also goes into the hung state) . Symantec backup team said they don't have any issue at their end.
>Generally we kill the all the backup processes at OS level ( ps -ef | grep rman & ps -ef | grep backup ) , Is that possible still few RMAN session doesn't get killed  from v$session. ( I am not sure about this , As per my understanding , if we kill any rman session at the OS level , it should be killed from the v$session)
Regards
Sourabh Gupta

Similar Messages

  • How to minimize the incident where SOAPUI project is in hung status

    Hi
    Has anyone faced the issue where SOAP UI Project is in hung status. We are using it for BPM service invocation which points as service entries to SOAP UI during testing to get BPM service invoked. Is it the fact that unresponsive request to SOAPUI project keeps the open connection and is there a limit on the services configured in SOAP UI project. Please let me know how we can avoid these issues
    Thanks
    Anish

    Hi
    You should see that the database time should be always less,
    Let the ABAP processing time is little more
    so first fetch all the required data for all dates from the database table  into an internal table
    then loop that Internal table.
    and with in that ITAB loop do whatever calculations and modifications you wants to do and display as per your requirement
    Regards
    Anji

  • No session found with status "New" or "Error"

    Hi,
    I put the statement after the CLOSE GROUP to process the BDC automatically:
      SUBMIT RSBDCSUB AND RETURN
             EXPORTING LIST TO MEMORY
             WITH MAPPE = SESSION.
             WITH VON = SY-DATUM
             WITH BIS = L_NEXT_DAY
             WITH Z_VERARB = 'X'
             WITH FEHLER = ' '.
    And when I ran it I got an error that says
    <i>No session found with status "New" or "Error"</i>
    When I go to SM35, I see the session in the 'New' tab.  How can I get this to process completely without manual intervention or first thing first no error from running the program?
    Thanks,
    Will

    Hi Rob,
    I will try the COMMIT. I think because I processing mutltiple GS01 transaction in one program.
    Hi Sudheer,
    I am actually usinng the INCLUDE that was given to me when I did the recording.  Here is the complete code from the include.
    ***INCLUDE BDCRECX1.
    for programs doing a data transfer by creating a batch-input session
    and
    for programs doing a data transfer by CALL TRANSACTION USING
    SELECTION-SCREEN BEGIN OF LINE.
      PARAMETERS SESSION RADIOBUTTON GROUP CTU.  "create session
      SELECTION-SCREEN COMMENT 3(20) TEXT-S07 FOR FIELD SESSION.
      selection-screen position 45.
      PARAMETERS CTU RADIOBUTTON GROUP  CTU.     "call transaction
      SELECTION-SCREEN COMMENT 48(20) TEXT-S08 FOR FIELD CTU.
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN BEGIN OF LINE.
      SELECTION-SCREEN COMMENT 3(20) TEXT-S01 FOR FIELD GROUP.
      selection-screen position 25.
      PARAMETERS GROUP(12).                      "group name of session
      SELECTION-SCREEN COMMENT 48(20) TEXT-S05 FOR FIELD CTUMODE.
      selection-screen position 70.
      PARAMETERS CTUMODE LIKE CTU_PARAMS-DISMODE DEFAULT 'N'.
                                          "A: show all dynpros
                                          "E: show dynpro on error only
                                          "N: do not display dynpro
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN BEGIN OF LINE.
      SELECTION-SCREEN COMMENT 3(20) TEXT-S02 FOR FIELD USER.
      selection-screen position 25.
      PARAMETERS: USER(12) DEFAULT SY-UNAME.     "user for session in batch
      SELECTION-SCREEN COMMENT 48(20) TEXT-S06 FOR FIELD CUPDATE.
      selection-screen position 70.
      PARAMETERS CUPDATE LIKE CTU_PARAMS-UPDMODE DEFAULT 'L'.
                                          "S: synchronously
                                          "A: asynchronously
                                          "L: local
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN BEGIN OF LINE.
      SELECTION-SCREEN COMMENT 3(20) TEXT-S03 FOR FIELD KEEP.
      selection-screen position 25.
      PARAMETERS: KEEP AS CHECKBOX.       "' ' = delete session if finished
                                          "'X' = keep   session if finished
      SELECTION-SCREEN COMMENT 48(20) TEXT-S09 FOR FIELD E_GROUP.
      selection-screen position 70.
      parameters E_GROUP(12).             "group name of error-session
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN BEGIN OF LINE.
      SELECTION-SCREEN COMMENT 3(20) TEXT-S04 FOR FIELD HOLDDATE.
      selection-screen position 25.
      PARAMETERS: HOLDDATE LIKE SY-DATUM.
      SELECTION-SCREEN COMMENT 51(17) TEXT-S02 FOR FIELD E_USER.
      selection-screen position 70.
      PARAMETERS: E_USER(12) DEFAULT SY-UNAME.    "user for error-session
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN BEGIN OF LINE.
      SELECTION-SCREEN COMMENT 51(17) TEXT-S03 FOR FIELD E_KEEP.
      selection-screen position 70.
      PARAMETERS: E_KEEP AS CHECKBOX.     "' ' = delete session if finished
                                          "'X' = keep   session if finished
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN BEGIN OF LINE.
      SELECTION-SCREEN COMMENT 51(17) TEXT-S04 FOR FIELD E_HDATE.
      selection-screen position 70.
      PARAMETERS: E_HDATE LIKE SY-DATUM.
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN SKIP.
    SELECTION-SCREEN BEGIN OF LINE.
      SELECTION-SCREEN COMMENT 1(33) TEXT-S10 FOR FIELD NODATA.
      PARAMETERS: NODATA DEFAULT '/' LOWER CASE.          "nodata
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN BEGIN OF LINE.
      SELECTION-SCREEN COMMENT 1(33) FOR FIELD SMALLLOG.
      PARAMETERS: SMALLLOG as checkbox.  "' ' = log all transactions
                                         "'X' = no transaction logging
    SELECTION-SCREEN END OF LINE.
      data definition
          Batchinputdata of single transaction
    DATA:   BDCDATA LIKE BDCDATA    OCCURS 0 WITH HEADER LINE.
          messages of call transaction
    DATA:   MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
          error session opened (' ' or 'X')
    DATA:   E_GROUP_OPENED.
          message texts
    TABLES: T100.
      at selection screen                                                *
    AT SELECTION-SCREEN.
    group and user must be filled for create session
      IF SESSION = 'X' AND
         GROUP = SPACE OR USER = SPACE.
        MESSAGE E613(MS).
      ENDIF.
      open dataset                                                       *
    FORM OPEN_DATASET USING P_DATASET.
      OPEN DATASET P_DATASET
                   FOR INPUT IN TEXT MODE
                   ENCODING DEFAULT.
      IF SY-SUBRC <> 0.
        WRITE: / TEXT-E00, SY-SUBRC.
        STOP.
      ENDIF.
    ENDFORM.
      close dataset                                                      *
    FORM CLOSE_DATASET USING P_DATASET.
      CLOSE DATASET P_DATASET.
    ENDFORM.
      create batchinput session                                          *
      (not for call transaction using...)                                *
    FORM OPEN_GROUP.
      IF SESSION = 'X'.
        SKIP.
        WRITE: /(20) 'Create group'(I01), GROUP.
        SKIP.
      open batchinput group
        CALL FUNCTION 'BDC_OPEN_GROUP'
             EXPORTING  CLIENT   = SY-MANDT
                        GROUP    = GROUP
                        USER     = USER
                        KEEP     = KEEP
                        HOLDDATE = HOLDDATE.
        WRITE: /(30) 'BDC_OPEN_GROUP'(I02),
                (12) 'returncode:'(I05),
                     SY-SUBRC.
      ENDIF.
    ENDFORM.
      end batchinput session                                             *
      (call transaction using...: error session)                         *
    FORM CLOSE_GROUP.
      IF SESSION = 'X'.
      close batchinput group
        CALL FUNCTION 'BDC_CLOSE_GROUP'.
        WRITE: /(30) 'BDC_CLOSE_GROUP'(I04),
                (12) 'returncode:'(I05),
                     SY-SUBRC.
      ELSE.
        IF E_GROUP_OPENED = 'X'.
          CALL FUNCTION 'BDC_CLOSE_GROUP'.
          WRITE: /.
          WRITE: /(30) 'Fehlermappe wurde erzeugt'(I06).
          E_GROUP_OPENED = ' '.
        ENDIF.
      ENDIF.
    ENDFORM.
           Start new transaction according to parameters                 *
    FORM BDC_TRANSACTION USING TCODE.
      DATA: L_MSTRING(480).
      DATA: L_SUBRC LIKE SY-SUBRC.
    batch input session
      IF SESSION = 'X'.
        CALL FUNCTION 'BDC_INSERT'
             EXPORTING TCODE     = TCODE
             TABLES    DYNPROTAB = BDCDATA.
        IF SMALLLOG <> 'X'.
          WRITE: / 'BDC_INSERT'(I03),
                   TCODE,
                   'returncode:'(I05),
                   SY-SUBRC,
                   'RECORD:',
                   SY-INDEX.
        ENDIF.
    call transaction using
      ELSE.
        REFRESH MESSTAB.
        CALL TRANSACTION TCODE USING BDCDATA
                         MODE   CTUMODE
                         UPDATE CUPDATE
                         MESSAGES INTO MESSTAB.
        L_SUBRC = SY-SUBRC.
        IF SMALLLOG <> 'X'.
          WRITE: / 'CALL_TRANSACTION',
                   TCODE,
                   'returncode:'(I05),
                   L_SUBRC,
                   'RECORD:',
                   SY-INDEX.
          LOOP AT MESSTAB.
            SELECT SINGLE * FROM T100 WHERE SPRSL = MESSTAB-MSGSPRA
                                      AND   ARBGB = MESSTAB-MSGID
                                      AND   MSGNR = MESSTAB-MSGNR.
            IF SY-SUBRC = 0.
              L_MSTRING = T100-TEXT.
              IF L_MSTRING CS '&1'.
                REPLACE '&1' WITH MESSTAB-MSGV1 INTO L_MSTRING.
                REPLACE '&2' WITH MESSTAB-MSGV2 INTO L_MSTRING.
                REPLACE '&3' WITH MESSTAB-MSGV3 INTO L_MSTRING.
                REPLACE '&4' WITH MESSTAB-MSGV4 INTO L_MSTRING.
              ELSE.
                REPLACE '&' WITH MESSTAB-MSGV1 INTO L_MSTRING.
                REPLACE '&' WITH MESSTAB-MSGV2 INTO L_MSTRING.
                REPLACE '&' WITH MESSTAB-MSGV3 INTO L_MSTRING.
                REPLACE '&' WITH MESSTAB-MSGV4 INTO L_MSTRING.
              ENDIF.
              CONDENSE L_MSTRING.
              WRITE: / MESSTAB-MSGTYP, L_MSTRING(250).
            ELSE.
              WRITE: / MESSTAB.
            ENDIF.
          ENDLOOP.
          SKIP.
        ENDIF.
    Erzeugen fehlermappe ************************************************
        IF L_SUBRC <> 0 AND E_GROUP <> SPACE.
          IF E_GROUP_OPENED = ' '.
            CALL FUNCTION 'BDC_OPEN_GROUP'
                 EXPORTING  CLIENT   = SY-MANDT
                            GROUP    = E_GROUP
                            USER     = E_USER
                            KEEP     = E_KEEP
                            HOLDDATE = E_HDATE.
             E_GROUP_OPENED = 'X'.
          ENDIF.
          CALL FUNCTION 'BDC_INSERT'
               EXPORTING TCODE     = TCODE
               TABLES    DYNPROTAB = BDCDATA.
        ENDIF.
      ENDIF.
      REFRESH BDCDATA.
    ENDFORM.
           Start new screen                                              *
    FORM BDC_DYNPRO USING PROGRAM DYNPRO.
      CLEAR BDCDATA.
      BDCDATA-PROGRAM  = PROGRAM.
      BDCDATA-DYNPRO   = DYNPRO.
      BDCDATA-DYNBEGIN = 'X'.
      APPEND BDCDATA.
    ENDFORM.
           Insert field                                                  *
    FORM BDC_FIELD USING FNAM FVAL.
      IF FVAL <> NODATA.
        CLEAR BDCDATA.
        BDCDATA-FNAM = FNAM.
        BDCDATA-FVAL = FVAL.
        APPEND BDCDATA.
      ENDIF.
    ENDFORM.
    Thanks
    Will
    I awarded points to everyone. Thanks so much.
    Message was edited by:
            Will Ferrell

  • Monitoring RMAN Session

    I am using RMAN Duplicate command to clone production database to auxiliary database. My environment is Oracle 9.2.0.8 64 bit AIX 5.3
    I have following scenario:
    Duplicate database from server A to server B (Non ASM)
    Primary Database SID: jldr
    Duplicate Database SID: odsarch
    RMAN Catalog SID: CATALOG
    [email protected]:/home/oracle/dba/scripts>rman target sys/passwd@JLDR catalog rman/passwd@CATALOG auxiliary /
    Recovery Manager: Release 9.2.0.8.0 - 64bit Production
    Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
    connected to target database: JLDR (DBID=628146835)
    connected to recovery catalog database
    connected to auxiliary database: odsarch (not mounted)
    RMAN> run {
    set until time "to_date('Jun 01 2010 00:00:00','Mon DD YYYY HH24:MI:SS')";
    ALLOCATE AUXILIARY CHANNEL c1 DEVICE TYPE sbt PARMS 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/TDPO.dw3_tdp)';
    duplicate target database to orsarch NOFILENAMECHECK;
    }2> 3> 4> 5>
    channel c1: starting datafile backupset restore
    channel c1: specifying datafile(s) to restore from backup set
    restoring datafile 00001 to /u01/oradata/jldr_sys/data/system01.dbf
    restoring datafile 00004 to /u01/oradata/jldr_sys/data/drsys01.dbf
    restoring datafile 00048 to /u01/oradata/jldr_ods/index/ods_idx09.dbf
    restoring datafile 00081 to /u02/oradata/jldr_ods/index/ods_idx21.dbf
    restoring datafile 00084 to /u01/oradata/jldr_ods/data/ods37.dbf
    restoring datafile 00085 to /u01/oradata/jldr_jbl/index/jbloader_idx04.dbf
    restoring datafile 00090 to /u02/oradata/jldr_ods/data/ods40.dbf
    restoring datafile 00091 to /u02/oradata/jldr_ods/index/ods_idx24.dbf
    restoring datafile 00094 to /u02/oradata/jldr_ods/data/ods42.dbf
    restoring datafile 00096 to /u02/oradata/jldr_ods/index/ods_idx26.dbf
    restoring datafile 00097 to /u01/oradata/jldr_ods/data/ods44.dbf
    restoring datafile 00099 to /u02/oradata/jldr_ods/data/ods46.dbf
    restoring datafile 00102 to /u02/oradata/jldr_ods/data/ods48.dbf
    restoring datafile 00104 to /u02/oradata/jldr_ods/data/ods50.dbf
    restoring datafile 00105 to /u02/oradata/jldr_ods/data/ods51.dbf
    restoring datafile 00107 to /u02/oradata/jldr_ods/data/ods53.dbf
    restoring datafile 00109 to /u02/oradata/jldr_ods/data/ods55.dbf
    restoring datafile 00111 to /u02/oradata/jldr_ods/data/ods57.dbf
    restoring datafile 00112 to /u02/oradata/jldr_ods/index/ods_idx28.dbf
    restoring datafile 00123 to /u01/oradata/jldr_eai/index/jbloader03.dbf
    restoring datafile 00135 to /u01/oradata/jldr_eai/index/ods61.dbf
    restoring datafile 00136 to /u01/oradata/jldr_ssr/index/ssr_idx02.dbf
    released channel: c1
    released channel: c2
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 06/23/2010 23:48:52
    RMAN-03015: error occurred in stored script Memory Script
    ORA-19501: read error on file "kelf146d_1_1", blockno 530547201 (blocksize=512)
    ORA-27190: skgfrd: sbtread2 returned error
    ORA-19511: Error received from media manager layer, error text:
    ANS1017E (RC-50) Session rejected: TCP/IP connection failure
    RMAN> run {
    set until time "to_date('Jun 01 2010 00:00:00','Mon DD YYYY HH24:MI:SS')";
    ALLOCATE AUXILIARY CHANNEL c1 DEVICE TYPE sbt PARMS 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo_ods.opt)';
    ALLOCATE AUXILIARY CHANNEL c2 DEVICE TYPE sbt PARMS 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo_ods.opt)';
    duplicate target database to orsarch NOFILENAMECHECK;
    skipping datafile 11; already restored to file /u01/oradata/jldr_jbl/data/jbloader01.dbf
    skipping datafile 12; already restored to file /u01/oradata/jldr_ods/data/ods01.dbf
    skipping datafile 90; already restored to file /u02/oradata/jldr_ods/data/ods40.dbf
    skipping datafile 94; already restored to file /u02/oradata/jldr_ods/data/ods42.dbf
    skipping datafile 97; already restored to file /u01/oradata/jldr_ods/data/ods44.dbf
    skipping datafile 99; already restored to file /u02/oradata/jldr_ods/data/ods46.dbf
    skipping datafile 102; already restored to file /u02/oradata/jldr_ods/data/ods48.dbf
    skipping datafile 104; already restored to file /u02/oradata/jldr_ods/data/ods50.dbf
    skipping datafile 105; already restored to file /u02/oradata/jldr_ods/data/ods51.dbf
    skipping datafile 107; already restored to file /u02/oradata/jldr_ods/data/ods53.dbf
    skipping datafile 109; already restored to file /u02/oradata/jldr_ods/data/ods55.dbf
    skipping datafile 111; already restored to file /u02/oradata/jldr_ods/data/ods57.dbf
    skipping datafile 119; already restored to file /u01/oradata/jldr_eai/index/scratch02.dbf
    skipping datafile 123; already restored to file /u01/oradata/jldr_eai/index/jbloader03.dbf
    skipping datafile 135; already restored to file /u01/oradata/jldr_eai/index/ods61.dbf
    skipping datafile 136; already restored to file /u01/oradata/jldr_ssr/index/ssr_idx02.dbf
    skipping datafile 108; already restored to file /u02/oradata/jldr_ods/data/ods54.dbf
    skipping datafile 110; already restored to file /u02/oradata/jldr_ods/data/ods56.dbf
    skipping datafile 118; already restored to file /u01/oradata/jldr_eai/index/scratch01.dbf
    skipping datafile 131; already restored to file /u02/oradata/jldr_ods/data/ods58.dbf
    skipping datafile 133; already restored to file /u02/oradata/jldr_ods/data/ods59.dbf
    skipping datafile 134; already restored to file /u01/oradata/jldr_ods/data/ods60.dbf
    skipping datafile 128; already restored to file /u01/oradata/jldr_ods/index_16k/ods_idx01_16K.dbf
    channel c1: starting datafile backupset restore
    channel c1: specifying datafile(s) to restore from backup set
    restoring datafile 00003 to /u01/oradata/jldr_sys/data/cwmlite01.dbf
    restoring datafile 00005 to /u01/oradata/jldr_sys/data/example01.dbf
    restoring datafile 00006 to /u01/oradata/jldr_eai/index/eai_idx01.dbf
    restoring datafile 00008 to /u01/oradata/jldr_sys/data/tools01.dbf
    restoring datafile 00010 to /u01/oradata/jldr_sys/data/xdb01.dbf
    restoring datafile 00014 to /u01/oradata/jldr_jbl/index/jbloader_idx01.dbf
    restoring datafile 00015 to /u01/oradata/jldr_ods/data/business_objs01.dbf
    restoring datafile 00016 to /u01/oradata/jldr_ods/data/tivoliorts.dbf
    restoring datafile 00018 to /u01/oradata/jldr_ods/data/ACCTMIS.dbf
    restoring datafile 00021 to /u01/oradata/jldr_mstmt/data/mis_stmt01.dbf
    restoring datafile 00042 to /u01/oradata/jldr_jbl/index/jbloader_idx03.dbf
    restoring datafile 00044 to /u01/oradata/jldr_ods/index/ods_idx08.dbf
    restoring datafile 00051 to /u01/oradata/jldr_ods/index/ods_idx10.dbf
    restoring datafile 00057 to /u01/oradata/jldr_ods/index/ods_idx12.dbf
    restoring datafile 00062 to /u01/oradata/jldr_ods/index/ods_idx14.dbf
    restoring datafile 00065 to /u01/oradata/jldr_ssr/data/ssr01.dbf
    restoring datafile 00066 to /u01/oradata/jldr_ssr/index/ssr_idx01.dbf
    restoring datafile 00072 to /u02/oradata/jldr_ods/index/ods_idx18.dbf
    restoring datafile 00074 to /u01/oradata/jldr_enjaz/index/enjazfawri_idx01.dbf
    restoring datafile 00078 to /u02/oradata/jldr_ods/index/ods_idx20.dbf
    restoring datafile 00083 to /u02/oradata/jldr_ods/index/ods_idx22.dbf
    restoring datafile 00086 to /u01/oradata/jldr_ods/data/ods38.dbf
    restoring datafile 00087 to /u02/oradata/jldr_ods/index/ods_idx23.dbf
    restoring datafile 00089 to /u01/oradata/jldr_eai/index/jbloader02.dbf
    restoring datafile 00093 to /u02/oradata/jldr_ods/index/ods_idx25.dbf
    restoring datafile 00100 to /u02/oradata/jldr_ods/index/ods_idx27.dbf
    restoring datafile 00113 to /u02/oradata/jldr_ods/index/ods_idx29.dbf
    restoring datafile 00115 to /u02/oradata/jldr_ods/index/ods_idx31.dbf
    restoring datafile 00120 to /u01/oradata/jldr_sys/undo/undotbs02.dbf
    channel c2: starting datafile backupset restore
    channel c2: specifying datafile(s) to restore from backup set
    restoring datafile 00001 to /u01/oradata/jldr_sys/data/system01.dbf
    restoring datafile 00004 to /u01/oradata/jldr_sys/data/drsys01.dbf
    restoring datafile 00007 to /u01/oradata/jldr_sys/data/odm01.dbf
    restoring datafile 00009 to /u01/oradata/jldr_sys/data/users01.dbf
    restoring datafile 00013 to /u01/oradata/jldr_eai/index/eai_idx02.dbf
    restoring datafile 00019 to /u01/oradata/jldr_ods/data/ACCOUNT.dbf
    restoring datafile 00022 to /u01/oradata/jldr_mstmt/index/mis_stmt_idx01.dbf
    restoring datafile 00075 to /u02/oradata/jldr_ods/index/ods_idx19.dbf
    restoring datafile 00081 to /u02/oradata/jldr_ods/index/ods_idx21.dbf
    restoring datafile 00085 to /u01/oradata/jldr_jbl/index/jbloader_idx04.dbf
    restoring datafile 00091 to /u02/oradata/jldr_ods/index/ods_idx24.dbf
    restoring datafile 00096 to /u02/oradata/jldr_ods/index/ods_idx26.dbf
    restoring datafile 00112 to /u02/oradata/jldr_ods/index/ods_idx28.dbf
    restoring datafile 00114 to /u02/oradata/jldr_ods/index/ods_idx30.dbf
    restoring datafile 00116 to /u02/oradata/jldr_ods/index/ods_idx32.dbf
    restoring datafile 00121 to /u01/oradata/jldr_sys/data/audit.dbf
    Now, when I connect to database and try to see rman jobs:
    sqlplus>select SID, START_TIME,TOTALWORK, sofar, (sofar/totalwork) * 100 done, sysdate + TIME_REMAINING/3600/24 end_at from v$session_longops where totalwork > sofar AND opname NOT LIKE '%aggregate%' AND opname like RMAN%' ;
    SQL> @longops_rman.sql
    SID START_TIME TOTALWORK SOFAR DONE END_AT
    10 27/06/10 10:24:12 4654592 0 0
    12 27/06/10 10:24:36 15918960 0 0
    However, when we see from IBM TSM, it shows data is being moved from the tape storage to the machine by rman session. However, I cannot see anything in rman job inside database. Remember db is in 'startup nomount' state.
    Br,
    Anjum

    Hi,
    Just a thought that having the TIMED_STATISTICS parameter set to FALSE or failing to gather the statistics for the objects using DBMS_STATS are two possible reasons for no data through the v$session_longops.
    regards

  • BDC Sessions in Error Status

    Hello!
    I have a customer that usually have error status in BDC Sessions and they expect that original users clean up their sessions.
    But they are looking for some task in background to help them, is it possible?
    And he has another doubt:
    "How does the system store the data used in the BDC session?  If we have an error and need to correct the data or re-run the session, where will the tool pull the data for that session?  We are trying to determine if failed sessions are leaving data on the unix filesystems, etc."
    Thanks in advance,
    Daniel Kaoro Kobashigawa

    Hi,
    If you are using the BDC session methos then the error logs and other ino are stored in teh session in SM36
    We can re-process the sessiions that are error ones seen in the Error records.
    Search SDN more on this.
    We have many threads on this issue.
    If you are using the Call Transaction then we dont get the exact error but we can see the error records using BDCMSGCOLL.
    Usually both are combined to handle the data in a accurate manner.
    Regards
    Lekha

  • I can't run visa interactive control window. ERROR MESSAGE: "Unable to open session "ASrl::INSTR" Status name VI_ERROR-RSRC BUSY Visa cannot curently access this resource.

    I cant run tds220 (driver for oscilloscope).
    Error message:
    VISA: (Hex 0xBFFF000E) The given session or object reference is invalid.
    Furthermore
    I cant run Visa INteractive control.
    Error message:
    "Unable to open session to "ASRL1::INSTR" Return value 0xBFFF0072 Status name VI-ERROE-RSRC-BUSY . VISA csnnot currently access this resource."
    Then change ports, this message appears for another port.
    Thanks for answer.
    Gita

    The port is open by another resource. You note that you should also get an error if you try to access the port in hyperterminal. Try rebooting your computer and the first thing you try is opening a VISA session with Visa Interactive control(VISAIC).
    If that fails, then you have a driver accessing your ports.
    If it works then it was just two applications that were trying to access your port (LabVIEW and VISAIC are seperate apps even thought they both may be using VISA.)
    Closing VISA sessions:
    LabVIEW will only *automatically* close VISA sessions if you have this option set: Tools>>options>>Automatically close VISA sessions.
    Otherwise you need to explicitly call a Visa close on the resource.

  • 10 Grid Control oem - job hung status running

    I installed 10g oem recently.
    Created an host job using the same target as oem is installed (simple os command echo test) and the job initiated and is hung in status running with no update.
    Any logs I can check to see why it not running?

    sometime a job may be show running in GC, there is an example in following thread , have a look this might help you
    Re: Can't delete/stop problem execution??

  • RMAN session

    Hi ,
    The DB version is 10.2.0.4. Whenever the archive log destination is full, the users were not able to login in to the database which means no new sessions are created. Using RMAN i used to delete the old archives older than n days. How does rman make a connection , creates a session to the database for this delete process??
    baskar.l

    baskar.l wrote:
    Hi ,
    The DB version is 10.2.0.4. Whenever the archive log destination is full, the users were not able to login in to the database which means no new sessions are created. Using RMAN i used to delete the old archives older than n days. How does rman make a connection , creates a session to the database for this delete process??
    baskar.lRMAN uses the Sys connection . If you check the alert log , it says, connect as Internal user . Since the internal was desupported since 9i and Sys has got the same functionality, RMAN can work using it.
    Aman....

  • RMAN's success/failure status

    Version: 10gR2
    For tracking/documentation purposes, we would like to know if our daily RMAN backup job was a success or failure.
    I've searched Oracle documentation for views like
    RC_BACKUP_CORRUPTION
    RC_BACKUP_SET_DETAILS
    .etc for this. But this doesn't seem to provide an accurate answer.
    How do you guys track the status of your daily RMAN backups?

    If you are using a FULL a query like this might be enough.
    (I always check the RMAN Log daily)
    SELECT OPERATION, STATUS, OBJECT_TYPE, TO_CHAR(START_TIME,'MM/DD/YYYY:hh:mi:ss') as START_TIME,
    TO_CHAR(END_TIME,'MM/DD/YYYY:hh:mi:ss') as END_TIME
    FROM sys.V_\$RMAN_STATUS WHERE START_TIME > SYSDATE -1 AND OPERATION = 'BACKUP'
    and object_type = 'DB FULL'
    order by start_time desc

  • V$RMAN_BACKUP_JOB_DETAILS view showing rman status running

    Hi,
    There is no rman session running in the database but still V$RMAN_BACKUP_JOB_DETAILS shows status as running
    select SID,username, opname,to_char(START_TIME,'dd mm yyyy hh:mm:ss'),TOTALWORK, sofar, (sofar/totalwork) * 100 done,TIME_REMAINING/3600/24,
    to_char(sysdate + TIME_REMAINING/3600/24,'dd mm yyyy hh:mm:ss') end_at
    from v$session_longops
    where totalwork > sofar
    AND opname NOT LIKE '%aggregate%'
    AND opname like 'RMAN%'SQL>   2    3    4    5    6
      7  ;
    no rows selected
    SQL> select sid, CLIENT_INFO ch, seq#, event, state from v$session where program like '%rman%';
    no rows selected
    SQL> select SESSION_KEY,SESSION_RECID,START_TIME,END_TIME,STATUS from V$RMAN_BACKUP_JOB_DETAILS where START_TIME > sysdate-3;
    SESSION_KEY SESSION_RECID START_TIM END_TIME  STATUS
           2853          2853 20-NOV-12 20-NOV-12 COMPLETED
           2862          2862 22-NOV-12           RUNNING
           2864          2864 22-NOV-12 22-NOV-12 COMPLETEDplease can anyone shed some light on it
    Thanks

    Fixed.
    In my solution I grabbed the command id from the details view and then matched that with the sid in the status view
    SQL> select session_key, command_id, status, time_taken_display from v$rman_backup_job_details where command_id='2012-11-27T22:30:37';
    SESSION_KEY COMMAND_ID                        STATUS
    TIME_TAKEN_DISPLAY
            602 2012-11-27T22:30:37               RUNNING WITH ERRORS
    16:32:53
    SQL> select sid from v$rman_status where COMMAND_ID='2012-11-27T22:30:37';
           SID
             4
             4
    SQL>then I made sure I was sys, before grabbing the session info and killing the session
    SQL> select user from user_users;
    USER
    SYS
    SQL>
    SQL> select sid,serial#,inst_id from gv$session  where sid=4 and serial#=3;
           SID    SERIAL#    INST_ID
             4          3          2
    SQL> alter system kill session '4,3,@2' immediate;
    System altered.
    SQL> let me know if this worked for you.
    hope this helps, C

  • What to do if there is abrupt termination of RMAN during a backup session

    Hi All,
    I am trying to automate the Level 0 and Level 1 backups which we ought to take. Following the is the RMAN related part of it for L1 backup:
    CONFIGURE CONTROLFILE AUTOBACKUP ON;"
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '${BKP_LOCATION}/${LType}_%F';"
    run {"
    allocate channel c1 type disk;"
    backup"
    incremental level 1 cumulative tag = $BTAG"
    format '${BKP_LOCATION}/${LType}_%d_set%s_piece%p_%T_%U.bkp'"
    (database include current controlfile tag $CTAG) ;"
    sql 'alter system archive log current';"
    sql 'alter system archive log current';"
    backup archivelog from sequence ${CSEQ} tag $ATAG"
    format '${BKP_LOCATION}/${LType}_Arch_%d_set%s_piece%p_%T_%U.bkp';"
    release channel c1;"
    exit;"
    In the above snippet, the variables are substituted for within a shell script and then put into a command file for RMAN. I am a novice in the backup and recovery. I got above piece of code from someone working on RMAN and built my automation logic around it.
    The script works fine and I am trying to build to script level recovery feature around it. My question is:
    -- What happens if I invoke the script, the backup session starts and then there is abrupt termination of the RMAN session either because of losing the db connection or receiving an interrupt signal or a kill signal or some other weird reason.
    -- What if I re-invoke my script? Will it start from the point where it was stopped earlier or would it start from the point where we had last successful Level 1 backup completed?
    Thanks in Advance.

    Hi user781131,
    What happens if I invoke the script, the backup session starts and then there is abrupt termination of the RMAN session either because of losing the db
    connection or receiving an interrupt signal or a kill signal or some other weird reason?The backup set which rman was creating is not commited due to the abnormal termination but all succesfull backup sets can be used.
    What if I re-invoke my script? Will it start from the point where it was stopped earlier or would it start from the point where we had last successful Level 1 backup
    completed?In your backup script you do not use the < NOT BACKED UP SINCE TIME > clause so it will again do a level 1 backup off all datafiles.
    See:
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta009.htm#i1017236
    This option is a convenient way to back up files that were not backed up during a previous failed backup. For example, you back up the database, but the instance fails halfway through. You can restart the backup with the NOT BACKED UP SINCE TIME clause and avoid backing up those files that you already backed up. If AS BACKUPSET is set, then this feature is only useful if RMAN generates multiple backup sets during the backup.
    Regards,
    Tycho
    Edited by: tychos on 28-jan-2010 15:21

  • RMAN Catalog - Identify session for a specific SID

    Dear all,
    is it possible to identify the rman session on the recovery-catalog database that is currently backing up a specific SID?
    Or in other words: Is the SID of the target database visible somewhere in the V$-Views on the catalog database when a backup is running?
    Kind regards
    Carsten

    The recovery catalog stores metadata about RMAN operations,but it does not record ongoing processes. There's a catalog view,which holds HISTORICAL data:
    http://download.oracle.com/docs/cd/B28359_01/backup.111/b28273/rcviews050.htm#i84920
    Werner

  • Regarding rman user session

    hi all,
    i need to create a trigger for tracing a particular user session or rman session so that only one trace file is used throughout, regardless of there number of logins or logoff
    thanks

    Create a logon trigger, that checks for a certain login-name
    We do the same for checking applications that log on.
    Remember that if you're calling a procedure from the logon trigger, you have to disable the trigger every time you work/develop on the procedure.
    Otherwise the trigger gets Invalid and all logons are denied
    I can't show you the code we use now, because our storage-network has failed
    Edit: Back online
    The code
    CREATE OR REPLACE TRIGGER check_logon_logging
      after logon on database
    begin
      illegal_appl_prc;
    end;

  • Session that has been killed hangs around

    Hi,
    This is probably an old issue and many may have figured out but I haven't and need your help. We have noticed that when the application sessions get hung in the Oracle server (we are running Oracle 9.0.1 on AIX 4.3.3), we kill them with ALTER SYSTEM command. The session status shows it has been KILLED but it does not vanish. Then we look for associated PID and do "ps -ef" but the process is no longer there. How we get rid of sessions that are hung and subsequently KILLED but have not gone away ? The only we have figured out to clean them up is by restarting the instance. We can't afford to restart the instance in production to handle this. Can someone let me know how to handle this ?
    Thanks in advance.

    the killed sessions will show in v$session until PMON clears them up (yes, during startup).
    the unix process is dead, and the killed session is not taking ANY resource. it shows KILLED in v$session just like INACTIVE sessions do. why do you mind them?
    from Note:100859.1:
    PMON will not delete the session object itself until the client connected to
    that session notices that it has been killed. Therefore, the sequence of
    events is:
    1) alter system kill session is issued - the STATUS of the session object in
    V$SESSION becomes KILLED, its server becomes PSEUDO.
    2) PMON cleans up the resources allocated to the session
    (i.e., rolls back its transaction, releases its locks, etc).
    3) the entry in V$SESSION remains there until the client of that session (the
    client is the process associated with the OSUSER,MACHINE,PROCESS columns in
    the V$SESSION view) tries to do another request.
    4) the client attempts another SQL statement and gets back ORA-28.
    5) PMON can now remove the entry from V$SESSION.
    This behavior is necessary because the client still has pointers to the
    session object even though the session has been killed. Therefore, the
    object cannot be deleted until the client is no longer pointing at it.
    hope this helps, Nogah.

  • Clear the entry for killed/sniped session in v$session

    Dear all,
    In our production database(11.2.0.1.0) running on windows 2008 server many client session showing inactive from last 4-5 hour and I want to kill those session because all sessions are dedicated so for this I created a resource plan set its idle time after certain interval session status is showing killed but it is not removing entries from v$session but our client demand is it must be clear from v$session so for this i was using DOS command taskkill utility to kill particular os process so I want to know what is the smartest way to do this.

    This is known behavior, not an issue.
    In a dedicated server environment when the session is killed and the rollback completes the process goes away so a join between v$session and v$process will fail. The v$session entry also usually goes away rather quickly, though I have seen cases where the v$session entry hung around till the instance was bounced. But normally Oracle will overlay the v$session entry with a new session using the same sid but a different serial# within seconds on a busy system.
    Mark @ http://dbaspot.com/oracle-server/40419-killed-sessions.html
    Metalink doc id 1023442.6 is also something confirming it.
    See also below link and last reply by Mr. Braj Kishore Mahto.
    http://dbaforums.org/oracle/index.php?showtopic=3039
    Regards
    Girish Sharma
    Edited by: Girish Sharma on Nov 21, 2012 5:35 PM
    So, what is best in this regard :
    ALTER SYSTEM DISCONNECT SESSION
    The ALTER SYSTEM DISCONNECT SESSION syntax is an alternative method for killing Oracle sessions. Unlike the KILL SESSION command which asks the session to kill itself, the DISCONNECT SESSION command kills the dedicated server process (or virtual circuit when using Shared Sever), which is equivalent to killing the server process from the operating system. The basic syntax is similar to the KILL SESSION command with the addition of the POST_TRANSACTION clause. The SID and SERIAL# values of the relevant session can be substituted into one of the following statements.
    SQL> ALTER SYSTEM DISCONNECT SESSION 'sid,serial#' POST_TRANSACTION;
    SQL> ALTER SYSTEM DISCONNECT SESSION 'sid,serial#' IMMEDIATE;
    http://www.oracle-base.com/articles/misc/killing-oracle-sessions.php#disconnect_session

Maybe you are looking for

  • Client-server database application...

    Hi there! I'm about to write a database-application and I wonder if the following approach is to prefer or not: I want to use a MySQL-database and there shall be about eight client-applications which all shall be able to use it. I think of solving th

  • Inspire 5.1 5500 decoder failed

    Greetings everyone! The decoder for my Inspire 5500 speakers has failed. When the decoder is off, the standby power light (red) will go out and the speakers will begin popping about once per second. When I try to power up the decoder, some of the gre

  • Adobe Acrobat Updater is an application downloaded...

    This message pops up every 3 days and I don't know why. How do I get rid of it? "Adobe Acrobat Updater is an application downloaded from the internet. Are you sure you want to open it? Safari downloaded this file on October 19, 2009."

  • (Urgent) Using java to invoke other programs

    Guys.. is there any way possible to use java to invoke other programs eg. java.open(TextPad) or java.execute(NotePad) something like this Thx guys

  • PC Companion not working

    I recently bought a new Sony Ericsson Xperia mini pro (not the X10, the new one). I've had this "new software update" on the display so I decided to finally update the phone. Now the problem is that PC Companion does NOT recognize my phone no matter