There's certain LOAD utility parameters that sets copypending status after the utility has ended, like: REPLACE when the table has data before the loading and RESUME YES. To avoid this, you can use the NOCOPYPEND parameter, define COPYDDN or SYSCOPY or run a separate COPY utility job on the table space after the LOAD.
Joined: 19 May 2007 Posts: 1512 Location: Virginia, USA
Srihari Gonugunta wrote:
Its LOG YES option with LOAD that sets the copypending status after the utility has ended.
From the DB2 Utilities Manual
LOG Tells whether logging is to occur during the RELOAD phase of the load process.
YES Specifies normal logging during the load process. All records loaded are logged.
The default is YES. NO Specifies no logging of data during the load process. The NO option sets the COPY-pending restriction against the table space or partition that the loaded table resides in. No table or partition in the table space can be updated until the restriction is removed. For ways to remove the restriction, see "Resetting the COPY-pending status" in topic 188.8.131.52.