Results 1 to 5 of 5
  1. #1
    Join Date
    Oct 2005
    Posts
    12

    Problem with NOCOPYPEND

    OS version: Z OS 1.4
    DB2 version: 7.1

    After running LOAD REPLACE with NOCOPYPEND option, TS is in COPY PENDING status. We get RC=0 after LOAD. SYSIBM.SYSCOPY catalog table reflects FULL IMAGE copy at time T1 and LOAD REPL LOG(NO) at T2 (T2>T1).

    Any hint?

    TIA

  2. #2
    Join Date
    Aug 2004
    Posts
    330
    DB2 ignores a NOCOPYPEND specification if you also specified COPYDDN to make a local site inline image copy during the LOAD.

  3. #3
    Join Date
    Dec 2005
    Posts
    273
    And if the tablespace was already in a copypending status before the load utility started, that status will NOT be resetted by load NOCOPYPEND.

  4. #4
    Join Date
    Oct 2005
    Posts
    12
    We don't specify COPYDDN. Thanks anyway.

    We don't know for sure the state of this TS before loading, but there's no evidence in SYSCOPY of any previous utility that could leave the TS in such a state (as far as I know REORG LOG NO and LOAD LOG NO are the only ones...)

    TIA.

  5. #5
    Join Date
    Apr 2006
    Posts
    1

    Talking

    Dear ORSIPMP, have you thought about the MODIFY utility? MODIFY is able to
    become a TS in copy pending status.
    Very often MODIFY brings us surprises.


Posting Permissions

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