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
How to avoid backup pending tablespaces
Moderators: chulett, rschirm, roy
Re: How to avoid backup pending tablespaces
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.
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
Michael