Topic
9 replies Latest Post - ‏2012-12-07T07:52:57Z by ada4ko
ada4ko
ada4ko
12 Posts
ACCEPTED ANSWER

Pinned topic backup and error SQL0901N

‏2012-11-23T11:56:47Z |
I can't make a backup because of this error.
After command

db2 BACKUP DATABASE SPIDERDB TO e:\db2_kopie\

i get error

SQL0901N Komenda lub instrukcja SQL zakończyła się niepowodzeniem z powodu
błędu systemowego bazy danych. (Przyczyna "121"). SQLSTATE=58004

I've checked this link http://pic.dhe.ibm.com/infocenter/db2luw/v10r1/index.jsp?topic=%2Fcom.ibm.db2.luw.messages.sql.doc%2Fdoc%2Fmsql00901n.html and
I disable federation. Statistics are quite fresh.

In attachement db2diag.log.

How to fix it?

DB2 Express-C 10.1 Win x64

Adam

Attachments

Updated on 2012-12-07T07:52:57Z at 2012-12-07T07:52:57Z by ada4ko
  • SystemAdmin
    SystemAdmin
    5837 Posts
    ACCEPTED ANSWER

    Re: backup and error SQL0901N

    ‏2012-11-23T13:42:17Z  in response to ada4ko
    Hello Adam,

    It looks like you encounter a "Remote I/O error" :

    $ db2diag -rc 0x83000079

    Input ZRC string '0x83000079' parsed as 0x83000079 (-2097151879).

    ZRC value to map: 0x83000079 (-2097151879)
    V7 Equivalent ZRC value: 0xFFFFB079 (-20359)

    ZRC class :
    Unexpected Operating System error (Class Index: 3)
    Component:
    Unknown component (Component Index: 0)
    Undefined as of DB2 v9.7.0.7; s121002
    Operating system reason code (errno):
    0x00000079 (121) = Remote I/O error

    Does the directory e:\db2_kopie\ exist ?
    Has the instance owner permission to write in it ? Is disk drive e: mounted ? etc...

    Hope this helps.
    Regards.

    Yves-Antoine Emmanuelli
    • ada4ko
      ada4ko
      12 Posts
      ACCEPTED ANSWER

      Re: backup and error SQL0901N

      ‏2012-11-23T14:24:59Z  in response to SystemAdmin
      Yes e:\db2_kopie\ exists and it is another hard disc in computer.
      Instance owner has write permissions for this path.
      For testing purpose I gave write permission to "Everyone" - with no luck.
      Adam
      • nivanov1
        nivanov1
        53 Posts
        ACCEPTED ANSWER

        Re: backup and error SQL0901N

        ‏2012-11-23T19:25:35Z  in response to ada4ko
        I think the problem is actually with reading data, not writing:
        ==============================================================
        2012-11-23-12.01.08.822000+060 E18435518F679 LEVEL: Error
        PID : 11808 TID : 21420 PROC : db2syscs.exe
        INSTANCE: DB2 NODE : 000 DB : SPIDERDB
        APPHDL : 0-17 APPID: *LOCAL.DB2.121123110054
        AUTHID : ADMINISTRATOR HOSTNAME: WIN-9C5D246P5E8
        EDUID : 21420 EDUNAME: db2bm.22280.0 (SPIDERDB)
        FUNCTION: DB2 UDB, database utilities, sqlubReadDMS, probe:360
        MESSAGE : ZRC=0x83000079=-2097151879

        DATA #1 : Pool ID, PD_TYPE_POOL_ID, 2 bytes
        2
        DATA #2 : unsigned integer, 4 bytes
        96
        DATA #3 : unsigned integer, 4 bytes
        96
        DATA #4 : unsigned integer, 4 bytes
        0
        ==============================================================

        POOL_ID 2 is USERSPACE1. Is it really 360 GB in size? Windows may have problems with files that large.
        • ada4ko
          ada4ko
          12 Posts
          ACCEPTED ANSWER

          Re: backup and error SQL0901N

          ‏2012-11-23T21:57:10Z  in response to nivanov1
          Yes it is really 360GB and there is only one table space because few months ago I don't think data will grow so fast.
          • ada4ko
            ada4ko
            12 Posts
            ACCEPTED ANSWER

            Re: backup and error SQL0901N

            ‏2012-12-04T21:37:37Z  in response to ada4ko
            So what should I do to make it work?
            • nivanov1
              nivanov1
              53 Posts
              ACCEPTED ANSWER

              Re: backup and error SQL0901N

              ‏2012-12-05T01:57:09Z  in response to ada4ko
              The way I see it, DB2 has trouble reading the container(s) for the tablespace USERSPACE1. If you are positive there are no OS errors, you can use DB2DART to verify that the tablespace is (or is not) OK.
              • ada4ko
                ada4ko
                12 Posts
                ACCEPTED ANSWER

                Re: backup and error SQL0901N

                ‏2012-12-06T13:07:50Z  in response to nivanov1
                Disc was checked - no errors.
                OS - no errors.

                DB2DART output
                The requested DB2DART processing has completed successfully!
                All operation completed without error;
                no problems were detected in the database.

                I create few tablespaces and move tables to new tablespaces (1 table 1 tablespace).
                Then tablespace USERSPACE1 was reduced.
                Nothing changed.

                New db2diag.log attached.

                Attachments

                • nivanov1
                  nivanov1
                  53 Posts
                  ACCEPTED ANSWER

                  Re: backup and error SQL0901N

                  ‏2012-12-06T17:20:40Z  in response to ada4ko
                  > Nothing changed.
                  The underlying error is still coming from Windows. Did you try simply copying the tablespace container(s) while DB2 is stopped?

                  $ db2diag -rc 0x83000079

                  Input ZRC string '0x83000079' parsed as 0x83000079 (-2097151879).

                  ZRC value to map: 0x83000079 (-2097151879)
                  V7 Equivalent ZRC value: 0xFFFFB079 (-20359)

                  ZRC class :
                  Unexpected Operating System error (Class Index: 3)
                  Component:
                  Unknown component (Component Index: 0)
                  Undefined as of DB2 v10.1.0.1; s120821
                  Operating system reason code (errno):
                  0x00000079 (121) = Remote I/O error
                  • ada4ko
                    ada4ko
                    12 Posts
                    ACCEPTED ANSWER

                    Re: backup and error SQL0901N

                    ‏2012-12-07T07:52:57Z  in response to nivanov1
                    I just dropped this tablespace. After that backup ended successfully.