By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,586 Members | 2,418 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,586 IT Pros & Developers. It's quick & easy.

Tablespace rollforward condition

P: n/a
Hello,

I have an oddity on a production database. I get the following from
the DB CFG :

Backup pending = NO

Database is consistent = NO
Rollforward pending = TABLESPACE
Restore pending = NO

but no tablespaces are in a state other than 0 when I do a list
tablespaces show detail. ?????

How can I find out which tablespace is in conflict?

Mairhtin O'Feannag

aka mairhtin at mairhtin dot com

Jan 30 '07 #1
Share this Question
Share on Google+
6 Replies


P: n/a
On Jan 30, 11:10 pm, "morch" <f...@mairhtin.comwrote:
Hello,

I have an oddity on a production database. I get the following from
the DB CFG :

Backup pending = NO

Database is consistent = NO
Rollforward pending = TABLESPACE
Restore pending = NO

but no tablespaces are in a state other than 0 when I do a list
tablespaces show detail. ?????

How can I find out which tablespace is in conflict?

Mairhtin O'Feannag

aka mairhtin at mairhtin dot com
Hi,

Kindly ensure whether your SYSCAT tablespace is in Consistent state..

it's
vj-dba

Feb 1 '07 #2

P: n/a
All tablespaces are state 0. Including syscat :

=db2 list tablespaces show detail | grep State
State = 0x0000
State = 0x0000
State = 0x0000
State = 0x0000
State = 0x0000
State = 0x0000
State = 0x0000
State = 0x0000
State = 0x0000
State = 0x0000
State = 0x0000
State = 0x0000
State = 0x0000
State = 0x0000
State = 0x0000
State = 0x0000
State = 0x0000
State = 0x0000
On Feb 1, 3:43 am, vijay...@gmail.com wrote:
On Jan 30, 11:10 pm, "morch" <f...@mairhtin.comwrote:
Hello,
I have an oddity on a production database. I get the following from
the DB CFG :
Backup pending = NO
Database is consistent = NO
Rollforward pending = TABLESPACE
Restore pending = NO
but no tablespaces are in a state other than 0 when I do a list
tablespaces show detail. ?????
How can I find out which tablespace is in conflict?
Mairhtin O'Feannag
aka mairhtin at mairhtin dot com

Hi,

Kindly ensure whether your SYSCAT tablespace is in Consistent state..

it's
vj-dba

Feb 1 '07 #3

P: n/a
Anyone? Anyone?

Mairhtin
On Jan 30, 10:10 am, "morch" <f...@mairhtin.comwrote:
Hello,

I have an oddity on a production database. I get the following from
the DB CFG :

Backup pending = NO

Database is consistent = NO
Rollforward pending = TABLESPACE
Restore pending = NO

but no tablespaces are in a state other than 0 when I do a list
tablespaces show detail. ?????

How can I find out which tablespace is in conflict?

Mairhtin O'Feannag

aka mairhtin at mairhtin dot com

Feb 13 '07 #4

P: n/a
C'MON... SOMEONE must have an answer to this. :) Please!!

Mairhtin

On Jan 30, 10:10 am, "morch" <f...@mairhtin.comwrote:
Hello,

I have an oddity on a production database. I get the following from
the DB CFG :

Backup pending = NO

Database is consistent = NO
Rollforward pending = TABLESPACE
Restore pending = NO

but no tablespaces are in a state other than 0 when I do a list
tablespaces show detail. ?????

How can I find out which tablespace is in conflict?

Mairhtin O'Feannag

aka mairhtin at mairhtin dot com

Feb 16 '07 #5

P: n/a
On 16 Feb., 23:28, "morch" <f...@mairhtin.comwrote:
C'MON... SOMEONE must have an answer to this. :) Please!!

Mairhtin

On Jan 30, 10:10 am, "morch" <f...@mairhtin.comwrote:
Hello,
I have an oddity on a production database. I get the following from
the DB CFG :
Backup pending = NO
Database is consistent = NO
Rollforward pending = TABLESPACE
Restore pending = NO
but no tablespaces are in a state other than 0 when I do a list
tablespaces show detail. ?????
How can I find out which tablespace is in conflict?
Mairhtin O'Feannag
aka mairhtin at mairhtin dot com
Weird - a pragmatic method to test it would be:

Just pick by random a table from each tablespace and do a "select *
with fetch first 1 rows only". If all selects work well then db2 cfg
lies - if not you'll know which tablespace has a problem. You can
generate the necessary select with a sql query like this:
with temp1 as
(SELECT max(rtrim(tabschema) concat '.' concat rtrim(TABNAME)) as
TABNAME,TBSPACEID
FROM SYSCAT.TABLES where tbspaceid 0
group by tbspaceid)
select 'SELECT * FROM ' concat tabname concat ' FETCH FIRST 1 ROWS
ONLY;' as SELECT_STMT from temp1

This method will not cover tablespaces where only indexes are stored
in. In this case you will need to modify the selects in such a way
that an index access will happen

HTH
Joachim

Feb 19 '07 #6

P: n/a
On Feb 19, 10:21 am, "Joachim Klassen" <JoKlas...@email.comwrote:
On 16 Feb., 23:28, "morch" <f...@mairhtin.comwrote:
C'MON... SOMEONE must have an answer to this. :) Please!!
Mairhtin
On Jan 30, 10:10 am, "morch" <f...@mairhtin.comwrote:
Hello,
I have an oddity on a production database. I get the following from
the DB CFG :
Backup pending = NO
Database is consistent = NO
Rollforward pending = TABLESPACE
Restore pending = NO
but no tablespaces are in a state other than 0 when I do a list
tablespaces show detail. ?????
How can I find out which tablespace is in conflict?
Mairhtin O'Feannag
aka mairhtin at mairhtin dot com

Weird - a pragmatic method to test it would be:

Just pick by random a table from each tablespace and do a "select *
with fetch first 1 rows only". If all selects work well then db2 cfg
lies - if not you'll know which tablespace has a problem. You can
generate the necessary select with a sql query like this:
with temp1 as
(SELECT max(rtrim(tabschema) concat '.' concat rtrim(TABNAME)) as
TABNAME,TBSPACEID
FROM SYSCAT.TABLES where tbspaceid 0
group by tbspaceid)
select 'SELECT * FROM ' concat tabname concat ' FETCH FIRST 1 ROWS
ONLY;' as SELECT_STMT from temp1

This method will not cover tablespaces where only indexes are stored
in. In this case you will need to modify the selects in such a way
that an index access will happen

HTH
Joachim
http://www-1.ibm.com/support/docview...=utf-8&lang=en

Looks like a known bug. I have a couple production databases showing
the same thing.

-T

Feb 19 '07 #7

This discussion thread is closed

Replies have been disabled for this discussion.