IDS Forum

Re: oncheck -cc errors

Posted By: ART KAGEL, BLOOMBERG/ 731 LEXIN
Date: Monday, 28 February 2005, at 4:20 p.m.

In Response To: oncheck -cc errors (Steve Willcoxon)

Looks like someone changed the NEXTSIZE in the systables entry in the database
instead of using ALTER TABLE. The REAL next size is stored on the table's
partition header page or tablespace tablespace entry. Oncheck validates the one
against the other and is reporting the descrepency. Manually modifying system
catalog table records is a serious no-no and can cause severe data access
problems including loss of access to your data altogether.

Art S. Kagel
----- Original Message -----
From: Steve Willcoxon <stevew@shubertorg.com>
At: 2/28 15:02

> We have just upgraded from IDS 9.30.FC1X6 to IDS 9.40.FC3 and now have =
> the following 'oncheck -cc' errors.
> OS =3D Dec TRU64 UNIX 5.1B.
> Any ideas on how to get rid of them. They do not seem to affect =
> anything.
> The 5000 is the correct sysindices nextsize .
>
> Steven Willcoxon
> The Shubert Organization
>
>
>
> -----------------------------------------
> Beginning Oncheck Script
> Starting oncheck -cc
> Mon Feb 28 09:23:17 EST 2005
>
> Validating database sysutils
>
> Validating systables for database sysutils
>
> Validating syscolumns for database sysutils
>
> Validating sysindexes for database sysutils
>
> Validating systabauth for database sysutils
>
> Validating syscolauth for database sysutils
>
> Validating sysdepend for database sysutils
>
> Validating syssyntable for database sysutils
> WARNING:No syssyntable records found.
>
> Validating sysviews for database sysutils
>
> Validating sysconstraints for database sysutils
>
> Validating database production
>
> Validating systables for database production
> ERROR: informix.sysindices nextsize 5000 !=3D tblspace.nxtsize 8
> TBLspace name sysindices
> Owner informix
> TBLspace number b00170
> Tabid 3
> Row size 3307
> Number of columns 14
> Number of indexes 2
> Number of rows 1343
> Date created 05/14/2002
> TBLspace major version number 3
> TBLspace minor version number 127
> TBLspace type T
> Locking level R
> Number of pages used 292
> First extent size 16
> Next extent size 10000
> Flags 0
> Site =20
> Database name =20
> ERROR: informix.sysconstraints nextsize 5000 !=3D tblspace.nxtsize 8
> TBLspace name sysconstraints
> Owner informix
> TBLspace number b00172
> Tabid 11
> Row size 335
> Number of columns 7
> Number of indexes 3
> Number of rows 5467
> Date created 05/14/2002
> TBLspace major version number 3
> TBLspace minor version number 127
> TBLspace type T
> Locking level R
> Number of pages used 305
> First extent size 16
> Next extent size 10000
> Flags 0
> Site =20
> Database name =20
> ERROR: informix.sysprocedures nextsize 5000 !=3D tblspace.nxtsize 8
> TBLspace name sysprocedures
> Owner informix
> TBLspace number b00171
> Tabid 16
> Row size 5270
> Number of columns 30
> Number of indexes 3
> Number of rows 859
> Date created 05/14/2002
> TBLspace major version number 3
> TBLspace minor version number 127
> TBLspace type T
> Locking level R
> Number of pages used 174
> First extent size 16
> Next extent size 10000
> Flags 0
> Site =20
> Database name =20
>
> Validating syscolumns for database production
>
> Validating sysindexes for database production
>
> Validating systabauth for database production
>
> Validating syscolauth for database production
>
> Validating sysdepend for database production
>
> Validating syssyntable for database production
> WARNING:No syssyntable records found.
>
> Validating sysviews for database production
>
> Validating sysconstraints for database production
>
> Validating database sysmaster
>
> Validating systables for database sysmaster
>
> Validating syscolumns for database sysmaster
>
> Validating sysindexes for database sysmaster
>
> Validating systabauth for database sysmaster
>
> Validating syscolauth for database sysmaster
>
> Validating sysdepend for database sysmaster
>
> Validating syssyntable for database sysmaster
> WARNING:No syssyntable records found.
>
> Validating sysviews for database sysmaster
>
> Validating sysconst

Messages In This Thread

• oncheck -cc errors
  Steve Willcoxon -- Monday, 28 February 2005, at 2:50 p.m.
  • Re: oncheck -cc errors
    ART KAGEL, BLOOMBERG/ 731 LEXIN -- Monday, 28 February 2005, at 4:20 p.m.
  • RE: oncheck -cc errors
    Sebastian, Norma J. -- Monday, 28 February 2005, at 5:04 p.m.
  • Re: oncheck -cc errors Fixed
    Steve Willcoxon -- Monday, 28 February 2005, at 5:33 p.m.

IDS Forum is maintained by Administrator with WebBBS 5.12.