Tablespace in RESTORE PENDING state

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

satish mullapudi - 31 Aug 2006 11:27 GMT

Hi All,
I am using Db2 UDB v 8.2 on RHEL . I have performed a load operation on
a table. Now that tablespace has been switched into RESTORE PENDING
state. Now I can only read the data in the table. I can't modify the
data in the table as it is giving me an error saying "Tablespace Access
denied". How can I bring the tablespace out of RESTORE PENDING state?
Please help me out

Thnak you in Advance.......

Reply to this Message

Mark A - 31 Aug 2006 13:56 GMT

> Hi All,
> I am using Db2 UDB v 8.2 on RHEL . I have performed a load operation on
[quoted text clipped - 5 lines]
>
> Thnak you in Advance.......

Look in the "Messages and Codes, Vol 2" for the SQL error you received, and
it will tell you what to do to resolve the problem.

Reply to this Message

satish mullapudi - 31 Aug 2006 14:10 GMT

> > Hi All,
> > I am using Db2 UDB v 8.2 on RHEL . I have performed a load operation on
[quoted text clipped - 8 lines]
> Look in the "Messages and Codes, Vol 2" for the SQL error you received, and
> it will tell you what to do to resolve the problem.

I have referred the Message Reference Vol 2 and this is the error
message I am getting:

DB21034E The command was processed as an SQL statement because it was
not a
valid Command Line Processor command. During SQL processing it
returned:
SQL0290N Table space access is not allowed. SQLSTATE=55039

Please help me out....

Reply to this Message

Norbert Munkel - 31 Aug 2006 16:00 GMT

satish mullapudi schrieb:

> SQL0290N Table space access is not allowed. SQLSTATE=55039
>
> Please help me out....

create a backup of this tablespace to make it accessible again.

regards,

Norbert

Reply to this Message

Mark A - 31 Aug 2006 16:09 GMT

> create a backup of this tablespace to make it accessible again.
>
> regards,
>
> Norbert

Assuming that the tablespace is in RESTORE PENDING and not BACKUP
PENDING state, it probably means the LOAD has failed.

To remove the load in progress table state (if the load operation has
failed, or was interrupted), do one of the following:

- Restart the load operation. First, address the cause of the failure;
for example, if the load utility ran out of disk space, add containers
to the table space before attempting a load restart operation.

- Terminate the load operation.

- Invoke a LOAD REPLACE operation against the same table on which a
load operation has failed.

- Recover table spaces for the loading table by using the RESTORE
DATABASE command with the most recent table space or database backup,
and then carry out further recovery actions.

Reply to this Message

Norbert Munkel - 31 Aug 2006 18:38 GMT

Hi,

thank you very much for putting me right. I think, "RESTORE PENDING" was
not written big enough in Subject and Mail-Body. ;-)

regards,

Norbert

>> create a backup of this tablespace to make it accessible again.

> Assuming that the tablespace is in RESTORE PENDING and not BACKUP
> PENDING state, it probably means the LOAD has failed.

Well.

Reply to this Message

satish mullapudi - 31 Aug 2006 19:00 GMT

> Hi,
>
[quoted text clipped - 11 lines]
>
> Well.

Hi all,
Thank you for guiding me. But here I am not able to take the backup of
the USERSPACE1 tablespace. This is the error I am getting:
SQL2048N An error occurred while accessing object "2". Reason code:
"6".
Where 2 is the hex code of my tablespace.
Now what I want is how can I bring back my tablespace (USERSPACE1 )
into NORMAL state which is currently in RESTORE PENDING state.

Thanks in Advance......

Reply to this Message

Phil Sherman - 31 Aug 2006 16:08 GMT

Connect to the database as an administrator and issue the command:
list tablespaces

This will give you a hex code describing the tablespace state. The
latest versions of this command also give a textual explanation of the code.

The likeliest problem (see Norbert's reply) is that you need to make a
backup. This is caused by having databse parameters set to allow
recovery from logs. Load, when it doesn't log changes, forces the
tablespace into a "backup pending" state that will not allow updates but
will allow reads.

Phil Sherman

>>> Hi All,
>>> I am using Db2 UDB v 8.2 on RHEL . I have performed a load operation on
[quoted text clipped - 19 lines]
>
> Please help me out....

Reply to this Message