Results 1 to 6 of 6
  1. #1
    Join Date
    Aug 2005
    Posts
    14

    Unanswered: Linux DB2 into 3590 tape drive

    Hi all,

    We have DB2 8.2 under SuSE Linux 9 and we have the problem that follows:

    - We want to make a database backup
    - We want to do it on a 3590 tape drive
    - We cannot achieve this because of error:

    db2inst1@atlas:~> db2 BACKUP DATABASE LNXR89 TO "/dev/btibm0" WITH 2 BUFFERS BUFFER 32 PARALLELISM 1;
    SQL2031W Warning! Please mount the target or source media on device "/dev/btibm0".

    Do you want to continue(c), terminate this device only(d), abort the utility(t) ? (c/d/t) c

    SQL2059W A device full warning was encountered on device "/dev/btibm0".
    Do you want to continue(c), terminate this device only(d), abort the utility(t) ? (c/d/t) c
    SQL2059W A device full warning was encountered on device "/dev/btibm0".
    Do you want to continue(c), terminate this device only(d), abort the utility(t) ? (c/d/t) c
    ...
    and so on...

    Help please !!

    Jose R. Baron
    CALCULO S.A.
    jbaron@calculo-sa.es

  2. #2
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650
    What do your db2diag.log messages say ?

    By default the file is under /<instowner home>/sqllib/db2dump

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

  3. #3
    Join Date
    Aug 2005
    Posts
    14
    It says this:

    2006-03-16-12.33.46.166889-240 I20659556A385 LEVEL: Warning
    PID : 18872 TID : 2199082268736PROC : db2agent (LNXR89)
    INSTANCE: db2inst1 NODE : 000 DB : LNXR89
    APPHDL : 0-454 APPID: *LOCAL.db2inst1.060316163343
    FUNCTION: DB2 UDB, database utilities, sqlubSetupJobControl, probe:2025
    MESSAGE : Starting an offline db backup.

    2006-03-16-12.33.49.283460-240 I20659942A318 LEVEL: Warning
    PID : 18890 TID : 2199082268736PROC : db2med.18872.0
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, database utilities, sqluMCWriteToDevice, probe:40
    MESSAGE : Media controller -- End of tape encountered on /dev/btibm0

    2006-03-16-12.33.49.284007-240 I20660261A357 LEVEL: Warning
    PID : 18890 TID : 2199082268736PROC : db2med.18872.0
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, oper system services, sqlodelete, probe:110
    MESSAGE : errno:
    DATA #1 : Hexdump, 4 bytes
    0x000003FFFFFFBDB0 : 0000 000D ....

    2006-03-16-12.33.49.284198-240 I20660619A243 LEVEL: Warning
    PID : 18890 TID : 2199082268736PROC : db2med.18872.0
    INSTANCE: db2inst1 NODE : 000
    MESSAGE : Path/Filename
    DATA #1 : String, 11 bytes
    /dev/btibm0

    2006-03-16-12.33.50.816155-240 I20660863A444 LEVEL: Severe
    PID : 18872 TID : 2199082268736PROC : db2agent (LNXR89)
    INSTANCE: db2inst1 NODE : 000 DB : LNXR89
    APPHDL : 0-454 APPID: *LOCAL.db2inst1.060316163343
    FUNCTION: DB2 UDB, database utilities, sqlubcka, probe:10
    MESSAGE : DiagData
    DATA #1 : Hexdump, 4 bytes
    0x0000000172AB51D4 : 0000 0002 ....

    2006-03-16-12.33.50.816407-240 I20661308A348 LEVEL: Severe
    PID : 18872 TID : 2199082268736PROC : db2agent (LNXR89)
    INSTANCE: db2inst1 NODE : 000 DB : LNXR89
    APPHDL : 0-454 APPID: *LOCAL.db2inst1.060316163343
    FUNCTION: DB2 UDB, database utilities, sqlubcka, probe:85
    MESSAGE : DiagData

    2006-03-16-12.33.50.915084-240 I20661657A359 LEVEL: Severe
    PID : 18872 TID : 2199082268736PROC : db2agent (LNXR89)
    INSTANCE: db2inst1 NODE : 000 DB : LNXR89
    APPHDL : 0-454 APPID: *LOCAL.db2inst1.060316163343
    FUNCTION: DB2 UDB, database utilities, sqlubcka, probe:140
    MESSAGE : Backup Terminated.

  4. #4
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650
    Media controller -- End of tape encountered on /dev/btibm0

    is likely to be the reason .. Rewind the tape, if it isn't already

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

  5. #5
    Join Date
    Aug 2005
    Posts
    14
    Yes, I know. I have done so but it keeps reporting the same problem.

    I have executed the command:

    mt -f /dev/rtibm0 erase

    To erase the tape contents to make sure I am accessing a blank tape. But still I have another problem:

    db2inst1@atlas:~/sqllib/db2dump> db2 BACKUP DATABASE LNXR89 TO "/dev/btibm0" WITH 2 BUFFERS BUFFER 32 PARALLELISM 1 ;
    SQL2031W Warning! Please mount the target or source media on device
    "/dev/btibm0".
    Do you want to continue(c), terminate this device only(d), abort the utility(t) ? (c/d/t) c
    SQL2031W Warning! Please mount the target or source media on device
    "/dev/btibm0".
    Do you want to continue(c), terminate this device only(d), abort the utility(t) ? (c/d/t) c
    SQL2031W Warning! Please mount the target or source media on device
    "/dev/btibm0".
    ...
    and so on

    If I cat db2diag.log this is what I can see:

    2006-03-16-13.24.59.206342-240 I20671138A326 LEVEL: Warning
    PID : 21012 TID : 2199082268736PROC : db2med.19018.0
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, database utilities, sqluInitFileDevice, probe:65
    MESSAGE : Media controller -- first tape warning. MC reason code = 0x850f000c

    2006-03-16-13.24.59.206424-240 I20671465A327 LEVEL: Warning
    PID : 21012 TID : 2199082268736PROC : db2med.19018.0
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, database utilities, sqluMCInitBackupMC, probe:80
    MESSAGE : Media controller -- device initialization warning (zrc = 0x850f000c)

    2006-03-16-13.24.59.206552-240 I20671793A463 LEVEL: Severe
    PID : 19018 TID : 2199082268736PROC : db2agent (LNXR89)
    INSTANCE: db2inst1 NODE : 000 DB : LNXR89
    APPHDL : 0-16 APPID: *LOCAL.db2inst1.060316172429
    FUNCTION: DB2 UDB, database utilities, sqlubMWResponse, probe:5
    MESSAGE : DiagData
    DATA #1 : Hexdump, 16 bytes
    0x0000000172AB5230 : 0000 07EF 2F64 6576 2F62 7469 626D 3000 ..../dev/btibm0.

    2006-03-16-13.24.59.604052-240 I20672257A355 LEVEL: Warning
    PID : 21012 TID : 2199082268736PROC : db2med.19018.0
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, oper system services, sqloopenp, probe:80
    MESSAGE : errno:
    DATA #1 : Hexdump, 4 bytes
    0x000003FFFFFFB790 : 0000 001C ....

    2006-03-16-13.24.59.604244-240 I20672613A243 LEVEL: Warning
    PID : 21012 TID : 2199082268736PROC : db2med.19018.0
    INSTANCE: db2inst1 NODE : 000
    MESSAGE : Path/Filename
    DATA #1 : String, 11 bytes
    /dev/btibm0

    2006-03-16-13.24.59.604328-240 I20672857A362 LEVEL: Severe
    PID : 21012 TID : 2199082268736PROC : db2med.19018.0
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, database utilities, sqluInitFileDevice, probe:49
    MESSAGE : DiagData
    DATA #1 : Hexdump, 4 bytes
    0x000003FFFFFFBED8 : 850F 000C ....

  6. #6
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650
    0x850f000c - means disk full ..

    I haven't experienced this before - so am not sure if I can offer any useful suggestions .. Apologies.

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

Posting Permissions

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