Sounds like the table is needing an integrity check. Read up on the
"Set Integrity" command.
Also, what do you mean by "...DB not to be able to save the rollback
info..." ? Rollback info are always written to logs. Did you hit a
log-full? And if so, did you terminate the application? Rollback is
not automatically unless you have an non-recoverable db.
[email]tomascalvohotmail.com[/email] (Tomas Calvo) wrote in message news:<e2fa73da.0307170632.443d8301posting.google. com>...> Hi there!
> I am using DB2 6.1 in Solaris. I have tried to delete several rows
> from one table. Unfortunately, the number of rows to be deleted was
> big enough to cause the DB not to be able to save the rollback info,
> so the query (DELETE FROM...) threw one error. After that, any query
> trying to delete/update/insert in that table brings back the following
> DB21034E The command was processed as an SQL statement because it was
> not a valid Command Line Processor command. During SQL processing it
> SQL0290N Table space access is not allowed. SQLSTATE=55039
> So, if I type "list tablespaces" I can see that the tablespace that
> table belongs to is in "backup pending" state.
> I have tried to restore it back to its "normal" state using the
> QUIESCE TABLESPACES FOR....
> with no success at all. Right now, I've got no idea of what to do. Can
> anyone help me???
> Thank you very much...
> Tomas Calvo