Results 1 to 4 of 4

Thread: Backup Failure

  1. #1
    Join Date
    Mar 2011
    Posts
    41

    Unanswered: Backup Failure

    Hello,

    I 'm getting the following error when I schedule a backup in DB13 .

    Please help .

    Job started
    Step 001 started (program RSDBAJOB, variant &0000000000012, user ID BASIS)
    Backup_Devatabase Backup to Device
    Backup_Dev:started by CL_DB6_JOB_BACKUP_DEVICE on server billing202
    Backup_Dev:Parameter TESTMODE has not been set
    Backup_Dev:Parameter RUNTIME has not been set
    Backup_Dev:Parameter BACKUP_MODE has been set to "ONLINE"
    Backup_Dev:Parameter PARTITION has not been set
    Backup_Dev:Parameter BACKUP_TYPE has been set to ""
    Backup_Dev:Parameter COMPRESS has been set to "COMPRESS"
    Backup_Dev:Parameter INCLUDE LOGS has been set to "INCLUDE LOGS"
    Backup_Dev:Parameter NUMBER_BUFFERS has been set to " 0"
    Backup_Dev:Parameter BUFFER_SIZE has been set to " 0"
    Backup_Dev:Parameter PARALLELISM has been set to " 0"
    Backup_Dev:Parameter UTIL_IMPACT_PRIORITY has not been set
    Backup_Dev:Parameter FILE_PATH has been set to "/nfs_backup/NPD/NPD_ONL_LOGS_SAT"
    Backup_Dev:Command ' BACKUP DATABASE NPD ON DBPARTITIONNUM (0 ) ONLINE TO"/nfs_backup/NPD/NPD_ONL_LOGS_SAT" CO
    Backup_Dev:MPRESS INCLUDE LOGS 'failed
    Exception CX_DB6_CON in program CL_DB6_JOB_BACKUP=============CP / CL_DB6_JOB_BACKUP=============CM002 at line ADBC error with r
    Backup_Dev:Exception CX_DBA_JOB in class CL_DB6_JOB_BACKUP
    Backup_Dev: Kernel Error ID:
    Backup_DevYSID:
    Backup_Dev: SY-SUBRC: 1208
    Backup_Dev: SY-TABIX: 0
    Backup_Dev: Message: ADBC error
    Backup_Dev: Database:
    Backup_Dev:caused by
    Backup_Dev:Exception CX_DB6_ADMINCMD in class CL_DB6_ADMIN_CMD method SSV_BACKUP
    Backup_Dev:line 66
    Backup_Dev: Kernel Error ID:
    Backup_Dev: SYSID: NPD
    Backup_Dev: SY-SUBRC: 1208
    Backup_Dev: Message: ADBC error
    Backup_Dev: Command:BACKUP DATABASENPD ON DBPARTITIONNUM ( 0 ) ONLINE TO"/nfs_ba
    Backup_Dev: ckup/NPD/NPD_ONL_LOGS_SAT" COMPRESS INCLUDE LOGS
    Backup_Dev: Database:
    Backup_Dev:caused by
    Backup_Dev:Exception CX_SQL_EXCEPTION in class CL_SQL_STATEMENT
    Backup_Dev: Kernel Error ID:
    Backup_Dev: DB Error: Yes
    Backup_Dev: SQL Code: 902-
    Backup_Dev: SQL Message: SQL0902C A system error (reason code = "9") occurred.
    Backup_Dev: Subsequent SQL statements cannot be processed. SQLSTATE=58005 row=1
    Backup_Dev: DB Object Exists: No
    Backup_Dev: Duplicated Key: No
    Backup_Dev: Internal Error: 1
    Backup_Dev: Invalid Cursor: No
    Backup_Dev: Unknown Connection: No
    Backup_Dev: Connection Closed: No
    Exception CX_DBA_JOB in class CL_DB6_JOB_BACKUP method line 40
    Backup_Dev:terminated with error
    REASON=ADBC error
    Job finished


    Regards
    Satish

  2. #2
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650
    Satish
    Are you expecting us to go through the message and find the SQL code and reason code for you ? Most of us reading the forum are lazy to find the info.

    So, can you post the SQLCODE and reason code and also the db2 version and operating system. Has the same operation from DB13 ever been successful.


    ---
    Visit the new-look IDUG Website , register to gain access to the excellent content.

  3. #3
    Join Date
    Mar 2011
    Posts
    41
    Apologies .

    I thoought it would be easy if I provide the detailed info .

    Here is the error code :

    Backup_Dev: SQL Message: SQL0902C A system error (reason code = "9") occurred.
    Backup_Dev: Subsequent SQL statements cannot be processed. SQLSTATE=58005 row=1

    Environment :
    AIX 6.1 DB2 9.7 FP2

    Regards
    Satish

  4. #4
    Join Date
    Nov 2010
    Posts
    14
    Satish,

    SQL0902C translates generally a system error which is not controlled by DB2 (I mean, error external to DB2). Mostly an error triggered by an Operating system call.

    Reason Code = 9; It is an AIX RC which translates "Bad file descriptor" (EBADF). This could be due to many issues. Check whether there is any corruption in the database containers. db2diag.log may give further information.

    Cheers,
    SK Chandra

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •