How to avoid backup pending tablespaces

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
yimwai
Participant
Posts: 46
Joined: Thu Jul 01, 2010 9:34 pm

How to avoid backup pending tablespaces

Post by yimwai »

We use connector to load data,
Bulk load write mode and append

When the job runs, the table space will become Backup pending
How to avoid this
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Which database? I have a guess but I'd rather not.
-craig

"You can never have too many knives" -- Logan Nine Fingers
MT
Premium Member
Premium Member
Posts: 198
Joined: Fri Mar 09, 2007 3:51 am

Re: How to avoid backup pending tablespaces

Post by MT »

Hi

More detailed information will get you better answers!

I guess - and I am very sure chulett as well - that you are talking about DB2.
Load in DB2 has several options to ensure consistency in the database while it does not use SQL and standard logging to add the data. You have giut a so called Copy option (also within DataStage) where you can define how DB2 behaves.
I urgently recommend you talk to your DBA!

A quick overview:
- Copy NO will place the tablespace in backup pending - the way out is to do a backup
- Copy Yes will store a copy of the loaded data and will not cause the backup pending state
- nonrecoverable load - which will leave the table nonrecoverable which means in case of a problem after the load and a db restore operation the table has to be dropped! So take care with this option.
regards

Michael
sam334
Premium Member
Premium Member
Posts: 145
Joined: Mon Aug 26, 2013 7:42 pm

Post by sam334 »

If you are using DB2 connector specifically, when you select Bulk load, there is a an option NON-RECOVERABLE LOAD- make sure its YES. It can solve the problem if proper tablespace is present in the database.
Post Reply