WARNING: Next backup of DBspace rootdbs must be le
Hello All.
Recently, we saw the following Warning info in the online log every day.
There was no any other warning or errors in the log.
We do a level 0 backup every night.
Is there any idea why it keeps giving warning?
Program Name: onstat
Build Version: 11.10.UC2
Build Number: N158
Build Host: vach
Build OS: AIX 5.3
Build Date: Thu Oct 25 22:56:40 CDT 2007
GLS Version: glslib-4.50.UC2
Thanks,
Frank
.....................
00:27:14 Maximum server connections 121
00:27:14 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked
1, Plog used 702, Llog used 5443
00:32:15 Checkpoint Completed: duration was 1 seconds.
00:32:15 Mon Jul 13 - loguniq 128702, logpos 0x6996018, timestamp:
0x34b76338 Interval: 134341
00:32:15 Maximum server connections 121
00:32:15 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked
1, Plog used 636, Llog used 18456
00:37:15 WARNING: Next backup of DBspace rootdbs must be level-0 backup.
00:37:15 WARNING: Next backup of DBspace dbphylog must be level-0 backup.
00:37:15 WARNING: Next backup of DBspace dblog1 must be level-0 backup.
00:37:15 WARNING: Next backup of DBspace dblog2 must be level-0 backup.
00:37:15 WARNING: Next backup of DBspace dbdata00 must be level-0 backup.
00:37:15 WARNING: Next backup of DBspace dbdata01 must be level-0 backup.
00:37:15 WARNING: Next backup of DBspace dbdata02 must be level-0 backup.
00:37:15 WARNING: Next backup of DBspace dbdata03 must be level-0 backup.
00:37:15 WARNING: Next backup of DBspace dbdata04 must be level-0 backup.
00:37:15 WARNING: Next backup of DBspace dbdata05 must be level-0 backup.
00:37:15 WARNING: Next backup of sbspace dbsbdata00 must be level-0 backup.
00:37:15 WARNING: Next backup of sbspace dbsbdata01 must be level-0 backup.
00:37:15 WARNING: Next backup of sbspace dbsbdata02 must be level-0 backup.
00:37:15 WARNING: Next backup of BLOBspace dbbbdata00 must be level-0
backup.
00:37:15 WARNING: Next backup of DBspace dbdw00 must be level-0 backup.
00:37:15 WARNING: Next backup of DBspace dbdw01 must be level-0 backup.
00:37:15 WARNING: Next backup of DBspace dberdata must be level-0 backup.
00:37:15 WARNING: Next backup of sbspace dbersbdata must be level-0 backup.
00:37:15 WARNING: Next backup of DBspace dbdw02 must be level-0 backup.
00:37:15 WARNING: Next backup of DBspace dbdw03 must be level-0 backup.
00:37:15 WARNING: Next backup of DBspace dbdw06 must be level-0 backup.
00:37:15 WARNING: Next backup of DBspace dbdw07 must be level-0 backup.
00:37:15 Checkpoint Completed: duration was 0 seconds.
00:37:15 Mon Jul 13 - loguniq 128702, logpos 0x8d661cc, timestamp:
0x35e72af2 Interval: 134342
00:37:15 Maximum server connections 121
00:37:15 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked
1, Plog used 500, Llog used 9168
00:40:41 Logical Log 128702 Complete, timestamp: 0x37070dbe.
00:40:41 Logical Log 128702 - Backup Started
00:40:46 Logical Log 128702 - Backup Completed
00:42:16 Checkpoint Completed: duration was 0 seconds.
00:42:16 Mon Jul 13 - loguniq 128703, logpos 0x7e3018, timestamp:
0x378b26ae Interval: 134343
.......................
--0016364edd441ec332046e9950e7
In short, the last level 0 back up timestamp (just a counter timestamp=
,
not relating to time)
is over 2 Billion older than the current timestamp. At this point leve=
l 1
& 2 archives are
disabled. The following select will let you view the timestamps.
database sysmaster;
select dbsnum, stamp0, sh_stamp from sysdbstab, sysshmvals;
John F. Miller III
STSM, Support Architect
miller3@us.ibm.com
503-578-5645
IBM Informix Dynamic Server (IDS)
=
=
From: "FRANK" <yunyaoqu@gmail.com> =
=
=
=
To: ids@iiug.org =
=
=
=
Date: 07/13/2009 10:05 AM =
=
=
=
Subject: WARNING: Next backup of DBspace rootdbs must b.... [1636=
0] =
=
=
Sent by: ids-bounces@iiug.org =
=
=
=
Hello All.
Recently, we saw the following Warning info in the online log every day=
.
There was no any other warning or errors in the log.
We do a level 0 backup every night.
Is there any idea why it keeps giving warning?
Program Name: onstat
Build Version: 11.10.UC2
Build Number: N158
Build Host: vach
Build OS: AIX 5.3
Build Date: Thu Oct 25 22:56:40 CDT 2007
GLS Version: glslib-4.50.UC2
Thanks,
Frank
......................
00:27:14 Maximum server connections 121
00:27:14 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns bloc=
ked
1, Plog used 702, Llog used 5443
00:32:15 Checkpoint Completed: duration was 1 seconds.
00:32:15 Mon Jul 13 - loguniq 128702, logpos 0x6996018, timestamp:
0x34b76338 Interval: 134341
00:32:15 Maximum server connections 121
00:32:15 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns bloc=
ked
1, Plog used 636, Llog used 18456
00:37:15 WARNING: Next backup of DBspace rootdbs must be level-0 backup=
.
00:37:15 WARNING: Next backup of DBspace dbphylog must be level-0 backu=
p.
00:37:15 WARNING: Next backup of DBspace dblog1 must be level-0 backup.=
00:37:15 WARNING: Next backup of DBspace dblog2 must be level-0 backup.=
00:37:15 WARNING: Next backup of DBspace dbdata00 must be level-0 backu=
p.
00:37:15 WARNING: Next backup of DBspace dbdata01 must be level-0 backu=
p.
00:37:15 WARNING: Next backup of DBspace dbdata02 must be level-0 backu=
p.
00:37:15 WARNING: Next backup of DBspace dbdata03 must be level-0 backu=
p.
00:37:15 WARNING: Next backup of DBspace dbdata04 must be level-0 backu=
p.
00:37:15 WARNING: Next backup of DBspace dbdata05 must be level-0 backu=
p.
00:37:15 WARNING: Next backup of sbspace dbsbdata00 must be level-0 bac=
kup.
00:37:15 WARNING: Next backup of sbspace dbsbdata01 must be level-0 bac=
kup.
00:37:15 WARNING: Next backup of sbspace dbsbdata02 must be level-0 bac=
kup.
00:37:15 WARNING: Next backup of BLOBspace dbbbdata00 must be level-0
backup.
00:37:15 WARNING: Next backup of DBspace dbdw00 must be level-0 backup.=
00:37:15 WARNING: Next backup of DBspace dbdw01 must be level-0 backup.=
00:37:15 WARNING: Next backup of DBspace dberdata must be level-0 backu=
p.
00:37:15 WARNING: Next backup of sbspace dbersbdata must be level-0 bac=
kup.
00:37:15 WARNING: Next backup of DBspace dbdw02 must be level-0 backup.=
00:37:15 WARNING: Next backup of DBspace dbdw03 must be level-0 backup.=
00:37:15 WARNING: Next backup of DBspace dbdw06 must be level-0 backup.=
00:37:15 WARNING: Next backup of DBspace dbdw07 must be level-0 backup.=
00:37:15 Checkpoint Completed: duration was 0 seconds.
00:37:15 Mon Jul 13 - loguniq 128702, logpos 0x8d661cc, timestamp:
0x35e72af2 Interval: 134342
00:37:15 Maximum server connections 121
00:37:15 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns bloc=
ked
1, Plog used 500, Llog used 9168
00:40:41 Logical Log 128702 Complete, timestamp: 0x37070dbe.
00:40:41 Logical Log 128702 - Backup Started
00:40:46 Logical Log 128702 - Backup Completed
00:42:16 Checkpoint Completed: duration was 0 seconds.
00:42:16 Mon Jul 13 - loguniq 128703, logpos 0x7e3018, timestamp:
0x378b26ae Interval: 134343
........................
--0016364edd441ec332046e9950e7
***********************************************************************=
********
Forum Note: Use "Reply" to post a response in the discussion forum.
=
John,
Thanks very much for the info!!
I run the query and got the following. Yes, the difference is big since
sh_stamp has negative value.
We do a full Level 0 backup daily. no idea why the two values are such
different now ! No control on it, have we?
Thanks,
Frank
dbsnum stamp0 sh_stamp
1 1409410483 -1357725325
2 1409410483 -1357725325
3 1409410483 -1357725325
4 1409410483 -1357725325
5 0 -1357725325
6 0 -1357725325
7 0 -1357725325
8 1409410483 -1357725325
9 1409410483 -1357725325
10 1409410483 -1357725325
11 1409410483 -1357725325
12 1409410483 -1357725325
13 1409410483 -1357725325
14 1409410483 -1357725325
15 1409410483 -1357725325
16 1409410483 -1357725325
17 1409410483 -1357725325
18 1409410483 -1357725325
19 1409410483 -1357725325
20 1409410483 -1357725325
21 1409410483 -1357725325
22 1409410483 -1357725325
23 1409410483 -1357725325
24 1409410483 -1357725325
25 1409410483 -1357725325
On Mon, Jul 13, 2009 at 2:15 PM, John Miller iii <miller3@us.ibm.com> wrote:
> In short, the last level 0 back up timestamp (just a counter timestamp=
> ,
> not relating to time)
> is over 2 Billion older than the current timestamp. At this point leve=
> l 1
> & 2 archives are
> disabled. The following select will let you view the timestamps.
>
> database sysmaster;
> select dbsnum, stamp0, sh_stamp from sysdbstab, sysshmvals;>
> John F. Miller III
> STSM, Support Architect
> miller3@us.ibm.com
> 503-578-5645
> IBM Informix Dynamic Server (IDS)
>
> =
>
> =
>
> From: "FRANK" <yunyaoqu@gmail.com> =
>
> =
>
> =
>
> =
>
> To: ids@iiug.org =
>
> =
>
> =
>
> =
>
> Date: 07/13/2009 10:05 AM =
>
> =
>
> =
>
> =
>
> Subject: WARNING: Next backup of DBspace rootdbs must b.... [1636=
> 0] =
>
> =
>
> =
>
> Sent by: ids-bounces@iiug.org =
>
> =
>
> =
>
> =
>
> Hello All.
>
> Recently, we saw the following Warning info in the online log every day=
> ..
> There was no any other warning or errors in the log.
>
> We do a level 0 backup every night.
>
> Is there any idea why it keeps giving warning?
>
> Program Name: onstat
> Build Version: 11.10.UC2
> Build Number: N158
> Build Host: vach
> Build OS: AIX 5.3
> Build Date: Thu Oct 25 22:56:40 CDT 2007
> GLS Version: glslib-4.50.UC2
>
> Thanks,
> Frank
>
> .......................
>
> 00:27:14 Maximum server connections 121
> 00:27:14 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns bloc=
> ked
> 1, Plog used 702, Llog used 5443
>
> 00:32:15 Checkpoint Completed: duration was 1 seconds.
> 00:32:15 Mon Jul 13 - loguniq 128702, logpos 0x6996018, timestamp:
> 0x34b76338 Interval: 134341
>
> 00:32:15 Maximum server connections 121
> 00:32:15 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns bloc=
> ked
> 1, Plog used 636, Llog used 18456
>
> 00:37:15 WARNING: Next backup of DBspace rootdbs must be level-0 backup=
> ..
> 00:37:15 WARNING: Next backup of DBspace dbphylog must be level-0 backu=
> p.
> 00:37:15 WARNING: Next backup of DBspace dblog1 must be level-0 backup.=
>
> 00:37:15 WARNING: Next backup of DBspace dblog2 must be level-0 backup.=
>
> 00:37:15 WARNING: Next backup of DBspace dbdata00 must be level-0 backu=
> p.
> 00:37:15 WARNING: Next backup of DBspace dbdata01 must be level-0 backu=
> p.
> 00:37:15 WARNING: Next backup of DBspace dbdata02 must be level-0 backu=
> p.
> 00:37:15 WARNING: Next backup of DBspace dbdata03 must be level-0 backu=
> p.
> 00:37:15 WARNING: Next backup of DBspace dbdata04 must be level-0 backu=
> p.
> 00:37:15 WARNING: Next backup of DBspace dbdata05 must be level-0 backu=
> p.
> 00:37:15 WARNING: Next backup of sbspace dbsbdata00 must be level-0 bac=
> kup.
>
> 00:37:15 WARNING: Next backup of sbspace dbsbdata01 must be level-0 bac=
> kup.
>
> 00:37:15 WARNING: Next backup of sbspace dbsbdata02 must be level-0 bac=
> kup.
>
> 00:37:15 WARNING: Next backup of BLOBspace dbbbdata00 must be level-0
> backup.
> 00:37:15 WARNING: Next backup of DBspace dbdw00 must be level-0 backup.=
>
> 00:37:15 WARNING: Next backup of DBspace dbdw01 must be level-0 backup.=
>
> 00:37:15 WARNING: Next backup of DBspace dberdata must be level-0 backu=
> p.
> 00:37:15 WARNING: Next backup of sbspace dbersbdata must be level-0 bac=
> kup.
>
> 00:37:15 WARNING: Next backup of DBspace dbdw02 must be level-0 backup.=
>
> 00:37:15 WARNING: Next backup of DBspace dbdw03 must be level-0 backup.=
>
> 00:37:15 WARNING: Next backup of DBspace dbdw06 must be level-0 backup.=
>
> 00:37:15 WARNING: Next backup of DBspace dbdw07 must be level-0 backup.=
>
> 00:37:15 Checkpoint Completed: duration was 0 seconds.
> 00:37:15 Mon Jul 13 - loguniq 128702, logpos 0x8d661cc, timestamp:
> 0x35e72af2 Interval: 134342
>
> 00:37:15 Maximum server connections 121
> 00:37:15 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns bloc=
> ked
> 1, Plog used 500, Llog used 9168
>
> 00:40:41 Logical Log 128702 Complete, timestamp: 0x37070dbe.
> 00:40:41 Logical Log 128702 - Backup Started
> 00:40:46 Logical Log 128702 - Backup Completed
> 00:42:16 Checkpoint Completed: duration was 0 seconds.
> 00:42:16 Mon Jul 13 - loguniq 128703, logpos 0x7e3018, timestamp:
> 0x378b26ae Interval: 134343
> .........................
>
> --0016364edd441ec332046e9950e7
>
> ***********************************************************************=
> ********
>
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
> =
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--0016e645fabcba6f93046e9b6708
You have very little control over the timestamp. While there are a few
things to do, I would
first suggest that you contact Informix support to assist with this issue.
I would also suggest
that you monitor any load/batch jobs that execute after you complete the
archive.
Please note that the values go: 1, 2, 3, .... +2 billion, -2 billion, ....
-3, -2, -1
John F. Miller III
STSM, Support Architect
miller3@us.ibm.com
503-578-5645
IBM Informix Dynamic Server (IDS)
ids-bounces@iiug.org wrote on 07/13/2009 12:34:10 PM:
> [image removed]
>
> Re: WARNING: Next backup of DBspace rootdbs mu.... [16365]
>
> FRANK
>
> to:
>
> ids
>
> 07/13/2009 12:37 PM
>
> Sent by:
>
> ids-bounces@iiug.org
>
> Please respond to ids
>
> John,
>
> Thanks very much for the info!!
>
> I run the query and got the following. Yes, the difference is big since
> sh_stamp has negative value.
>
> We do a full Level 0 backup daily. no idea why the two values are such
> different now ! No control on it, have we?
>
> Thanks,
> Frank
>
> dbsnum stamp0 sh_stamp
>
> 1 1409410483 -1357725325
>
> 2 1409410483 -1357725325
>
> 3 1409410483 -1357725325
>
> 4 1409410483 -1357725325
>
> 5 0 -1357725325
>
> 6 0 -1357725325
>
> 7 0 -1357725325
>
> 8 1409410483 -1357725325
>
> 9 1409410483 -1357725325
>
> 10 1409410483 -1357725325
>
> 11 1409410483 -1357725325
>
> 12 1409410483 -1357725325
>
> 13 1409410483 -1357725325
>
> 14 1409410483 -1357725325
>
> 15 1409410483 -1357725325
>
> 16 1409410483 -1357725325
>
> 17 1409410483 -1357725325
>
> 18 1409410483 -1357725325
>
> 19 1409410483 -1357725325
>
> 20 1409410483 -1357725325
>
> 21 1409410483 -1357725325
>
> 22 1409410483 -1357725325
>
> 23 1409410483 -1357725325
>
> 24 1409410483 -1357725325
>
> 25 1409410483 -1357725325
>
> On Mon, Jul 13, 2009 at 2:15 PM, John Miller iii <miller3@us.ibm.com>
wrote:
>
> > In short, the last level 0 back up timestamp (just a counter timestamp=
> > ,
> > not relating to time)
> > is over 2 Billion older than the current timestamp. At this point leve=
> > l 1
> > & 2 archives are
> > disabled. The following select will let you view the timestamps.
> >
> > database sysmaster;
> > select dbsnum, stamp0, sh_stamp from sysdbstab, sysshmvals;> >
> > John F. Miller III
> > STSM, Support Architect
> > miller3@us.ibm.com
> > 503-578-5645
> > IBM Informix Dynamic Server (IDS)
> >
> > =
> >
> > =
> >
> > From: "FRANK" <yunyaoqu@gmail.com> =
> >
> > =
> >
> > =
> >
> > =
> >
> > To: ids@iiug.org =
> >
> > =
> >
> > =
> >
> > =
> >
> > Date: 07/13/2009 10:05 AM =
> >
> > =
> >
> > =
> >
> > =
> >
> > Subject: WARNING: Next backup of DBspace rootdbs must b.... [1636=
> > 0] =
> >
> > =
> >
> > =
> >
> > Sent by: ids-bounces@iiug.org =
> >
> > =
> >
> > =
> >
> > =
> >
> > Hello All.
> >
> > Recently, we saw the following Warning info in the online log every
day=
> > ..
> > There was no any other warning or errors in the log.
> >
> > We do a level 0 backup every night.
> >
> > Is there any idea why it keeps giving warning?
> >
> > Program Name: onstat
> > Build Version: 11.10.UC2
> > Build Number: N158
> > Build Host: vach
> > Build OS: AIX 5.3
> > Build Date: Thu Oct 25 22:56:40 CDT 2007
> > GLS Version: glslib-4.50.UC2
> >
> > Thanks,
> > Frank
> >
> > .......................
> >
> > 00:27:14 Maximum server connections 121
> > 00:27:14 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns
bloc=
> > ked
> > 1, Plog used 702, Llog used 5443
> >
> > 00:32:15 Checkpoint Completed: duration was 1 seconds.
> > 00:32:15 Mon Jul 13 - loguniq 128702, logpos 0x6996018, timestamp:
> > 0x34b76338 Interval: 134341
> >
> > 00:32:15 Maximum server connections 121
> > 00:32:15 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns
bloc=
> > ked
> > 1, Plog used 636, Llog used 18456
> >
> > 00:37:15 WARNING: Next backup of DBspace rootdbs must be level-0
backup=
> > ..
> > 00:37:15 WARNING: Next backup of DBspace dbphylog must be level-0
backu=
> > p.
> > 00:37:15 WARNING: Next backup of DBspace dblog1 must be level-0
backup.=
> >
> > 00:37:15 WARNING: Next backup of DBspace dblog2 must be level-0
backup.=
> >
> > 00:37:15 WARNING: Next backup of DBspace dbdata00 must be level-0
backu=
> > p.
> > 00:37:15 WARNING: Next backup of DBspace dbdata01 must be level-0
backu=
> > p.
> > 00:37:15 WARNING: Next backup of DBspace dbdata02 must be level-0
backu=
> > p.
> > 00:37:15 WARNING: Next backup of DBspace dbdata03 must be level-0
backu=
> > p.
> > 00:37:15 WARNING: Next backup of DBspace dbdata04 must be level-0
backu=
> > p.
> > 00:37:15 WARNING: Next backup of DBspace dbdata05 must be level-0
backu=
> > p.
> > 00:37:15 WARNING: Next backup of sbspace dbsbdata00 must be level-0
bac=
> > kup.
> >
> > 00:37:15 WARNING: Next backup of sbspace dbsbdata01 must be level-0
bac=
> > kup.
> >
> > 00:37:15 WARNING: Next backup of sbspace dbsbdata02 must be level-0
bac=
> > kup.
> >
> > 00:37:15 WARNING: Next backup of BLOBspace dbbbdata00 must be level-0
> > backup.
> > 00:37:15 WARNING: Next backup of DBspace dbdw00 must be level-0
backup.=
> >
> > 00:37:15 WARNING: Next backup of DBspace dbdw01 must be level-0
backup.=
> >
> > 00:37:15 WARNING: Next backup of DBspace dberdata must be level-0
backu=
> > p.
> > 00:37:15 WARNING: Next backup of sbspace dbersbdata must be level-0
bac=
> > kup.
> >
> > 00:37:15 WARNING: Next backup of DBspace dbdw02 must be level-0
backup.=
> >
> > 00:37:15 WARNING: Next backup of DBspace dbdw03 must be level-0
backup.=
> >
> > 00:37:15 WARNING: Next backup of DBspace dbdw06 must be level-0
backup.=
> >
> > 00:37:15 WARNING: Next backup of DBspace dbdw07 must be level-0
backup.=
> >
> > 00:37:15 Checkpoint Completed: duration was 0 seconds.
> > 00:37:15 Mon Jul 13 - loguniq 128702, logpos 0x8d661cc, timestamp:
> > 0x35e72af2 Interval: 134342
> >
> > 00:37:15 Maximum server connections 121
> > 00:37:15 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns
bloc=
> > ked
> > 1, Plog used 500, Llog used 9168
> >
> > 00:40:41 Logical Log 128702 Complete, timestamp: 0x37070dbe.
> > 00:40:41 Logical Log 128702 - Backup Started
> > 00:40:46 Logical Log 128702 - Backup Completed
> > 00:42:16 Checkpoint Completed: duration was 0 seconds.
> > 00:42:16 Mon Jul 13 - loguniq 128703, logpos 0x7e3018, timestamp:
> > 0x378b26ae Interval: 134343
> > .........................
> >
> > --0016364edd441ec332046e9950e7
> >
> >
**************************************************