DB2 drop of a Inaaccessible table after roll forward recovery

Nageswara Pedas

DB2 drop of a Inaaccessible table after roll forward recovery

Hi,

I restored a Database and did a rollforward recovery of DB2 9.5 UDB database. After openining the Database I can see some tables are in accessible state and getting below message.

SQL1477N For table "xx.xxxxxx" an object "4" in table space "23" cannot
be accessed. SQLSTATE=55019

I am not able to drop this table too as this table was not accessible. Can someone Please let me know if there is any way to be able to drop these tables .

Nagesh.

 

Greg Palgrave

RE: DB2 drop of a Inaaccessible table after roll forward recovery
(in response to Nageswara Pedas)

You should be able to drop it, but you may need to reset your connection first:

db2 connect reset

db2 terminate

Then connect again and try the drop.

If you're using the GUI, then disconnect, close the GUI, then try again. DB2 caches a bit of information on the client connection, which is not always a good thing.

If you look at the detail of the error message (db2 ? SQL1477N ) your choices are drop/recreate the object, or restore to a later point in time, if it is due to a non-recoverable operation.

Have you checked that object "4" in table space "23" is a table, and not an index?

Cheers

Greg


In Reply to Nageswara Pedas:

Hi,

I restored a Database and did a rollforward recovery of DB2 9.5 UDB database. After openining the Database I can see some tables are in accessible state and getting below message.

SQL1477N For table "xx.xxxxxx" an object "4" in table space "23" cannot
be accessed. SQLSTATE=55019

I am not able to drop this table too as this table was not accessible. Can someone Please let me know if there is any way to be able to drop these tables .

Nagesh.

 

Charles Brown

DB2 drop of a Inaaccessible table after roll forward recovery
(in response to Greg Palgrave)
Hmmm!! Are you sure you didn’t get any error messages during the restore process — just wondering? Are you sure? Sounds quite unusual for db2 — anyway! Your thoughts!

Chas/b
NZ dba

Sent from my iPhone

> On Oct 23, 2017, at 7:54 PM, Greg Palgrave <[login to unmask email]> wrote:
>
> You should be able to drop it, but you may need to reset your connection first:
>
> db2 connect reset
>
> db2 terminate
>
> Then connect again and try the drop.
>
> If you're using the GUI, then disconnect, close the GUI, then try again. DB2 caches a bit of information on the client connection, which is not always a good thing.
>
> If you look at the detail of the error message (db2 ? SQL1477N ) your choices are drop/recreate the object, or restore to a later point in time, if it is due to a non-recoverable operation.
>
> Have you checked that object "4" in table space "23" is a table, and not an index?
>
> Cheers
>
> Greg
>
>
> In Reply to Nageswara Pedas:
>
> Hi,
>
> I restored a Database and did a rollforward recovery of DB2 9.5 UDB database. After openining the Database I can see some tables are in accessible state and getting below message.
>
> SQL1477N For table "xx.xxxxxx" an object "4" in table space "23" cannot
> be accessed. SQLSTATE=55019
>
> I am not able to drop this table too as this table was not accessible. Can someone Please let me know if there is any way to be able to drop these tables .
>
> Nagesh.
>
>
>
>
> Site Links: View post online View mailing list online Start new thread via email Unsubscribe from this mailing list Manage your subscription
>
> This email has been sent to: [login to unmask email]
> Setup a data refresh task in less time than it takes to make a cup of coffee + save up to 90% in CPU
> ESAi's BCV5 & XDM fast data refresh & Test Data Mgmt products will make you a hero to users. See
> http://www.ESAIGroup.com/idug
>
> Use of this email content is governed by the terms of service at:
> http://www.idug.org/p/cm/ld/fid=2
>

Nageswara Pedas

RE: DB2 drop of a Inaaccessible table after roll forward recovery
(in response to Charles Brown)

Hi Greg,

 

Thank you so much for quickly answering this. Yes , terminating the connection and reconnecting and dropping worked out very well. Thanks again !!!.

Nagesh