backup pending because of load command, please help!!!!

M_RAS · #1 (**permalink**) 01-31-06, 19:44

I use db2 v8.2.2 and aix 5.2

archive logging in database is ON, when I ran load command tabale space went to backup pending and made a lot of touble in production box, yes I know I should take a backup and continue or restore and turn OFF archive logging and run load command, my question is if I use IMPORT command instead of LOAD it seems is ok and I will not get backup pending

Am I right?

I am a little bit panick, I want to use import and I want sure I will not get any problem, please help.

Marcus_A · #2 (**permalink**) 01-31-06, 20:26

Import uses inserts (which are logged, so you will not get any copy pending). Make sure you set the commitcount parm so you take commits every 1000 or so inserts to keep the active log from filling up.

M_RAS · #3 (**permalink**) 01-31-06, 20:32

Quote:

Originally Posted by Marcus_A

Import uses inserts (which are logged, so you will not get any copy pending). Make sure you set the commitcount parm so you take commits every 1000 or so inserts to keep the active log from filling up.

Thank you so much Marcus_A

murali_sb · #4 (**permalink**) 01-31-06, 21:09

You won't get backup pending state if you use nonrecoverable option in your load statement. Load is much faster than import so if data is huge you might be better off with load. However you need to ensure integrity is set once load is over.

M_RAS · #5 (**permalink**) 02-01-06, 08:24

Quote:

Originally Posted by murali_sb

You won't get backup pending state if you use nonrecoverable option in your load statement. Load is much faster than import so if data is huge you might be better off with load. However you need to ensure integrity is set once load is over.

Thank you murali_sb for your help

Internet Services

Web Development

Digital Marketing

Consumer Tech