Results 1 to 5 of 5
  1. #1
    Join Date
    Oct 2009
    Posts
    17

    Unanswered: DB2MOVE LOAD not putting the tablespace in Backup pending state!!?

    Hello,

    As i read from the IBM documentation. db2move LOAD will place the tablespace in Backup pending state, same like normal LOAD command.

    To contradictory, my tests does not put the tablesapce in backup pending state! why is it so???


    --- TEST USING LOAD COMMAND ------------------------------------------
    : db2 load from tab18.ixf of ixf insert into tt1
    SQL3109N The utility is beginning to load data from file
    .
    .
    .
    Number of rows read = 18
    Number of rows skipped = 0
    Number of rows loaded = 18
    Number of rows rejected = 0
    Number of rows deleted = 0
    Number of rows committed = 18
    ----
    : db2 list tablespaces show detail |grep -i state|grep -v 0x0000
    State = 0x0020
    ---------------------------------------------
    >>> here Tablespace is placed in backup pending state after the LOAD command

    >>> I expect the same with DB2MOVE LOAD. But "db2move load" is not placing the tablespace in backup pending state! (see below)


    ----TEST USING DB2MOVE LOAD COMMAND -----------------------------------------
    : db2move tstxat01 load

    Application code page not determined, using ANSI codepage 1208
    ***** DB2MOVE *****
    Action: LOAD
    Start time: Thu Dec 22 14:30:37 2016
    .
    .
    .

    -Rows read: 18
    -Loaded: 18
    -Rejected: 0
    -Deleted: 0
    -Committed: 18
    .
    .
    .
    ---
    : db2 list tablespaces show detail |grep -i state|grep -v 0x0000
    :
    : db2 list tablespaces show detail |grep -i state
    State = 0x0000
    State = 0x0000
    State = 0x0000
    State = 0x0000
    State = 0x0000
    State = 0x0000
    State = 0x0000
    State = 0x0000
    State = 0x0000
    State = 0x0000
    ---------------------------------------------

  2. #2
    Join Date
    Apr 2012
    Posts
    1,143
    Provided Answers: 27
    Check the details in the sysibmadm.db_history , to see if it was a recoverable load

  3. #3
    Join Date
    Oct 2009
    Posts
    17
    Quote Originally Posted by db2mor View Post
    Check the details in the sysibmadm.db_history , to see if it was a recoverable load

    From sysibmadm.db_history i can see, LOAD command was non-recoverable.. also db2move load was non-recoverable (COPY-NO).

    Below is snap from sysibmadm.db_history :

    FOR DB2MOVE COMMAND:
    [LOADID: 706.2016-12-22-14.21.29.782217.0 (7;256)] ...... OFFLINE LOAD Unknown file type AUTOMATIC INDEXING INSERT COPY NO TT1, CPU_PARALLELISM [4], DISK_PARALLELISM [2], DATA BUFFER [51751436], TEMPFILES PATH .......

    FOR LOAD COMMAND:
    [LOADID: 162.2016-12-22-14.30.41.242797.0 (7;256)] ...... OFFLINE LOAD Unknown file type AUTOMATIC INDEXING INSERT NON-RECOVERABLE TT1, CPU_PARALLELISM [4], DISK_PARALLELISM [2], DATA BUFFER [51784186], TEMPFILES PATH .......

  4. #4
    Join Date
    Apr 2012
    Posts
    1,143
    Provided Answers: 27
    confirm the database is in recoverable mode , and rows got loaded successfully, and no registry variable overrides the copy-no, and that no backup action happened after the load.

  5. #5
    Join Date
    Jul 2016
    Location
    Moscow
    Posts
    294
    Provided Answers: 45
    COPY NO <> NON-RECOVERABLE.
    What's the result of the following command?
    db2set DB2_LOAD_COPY_NO_OVERRIDE
    Regards,
    Mark.

Tags for this Thread

Posting Permissions

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