FWIW, In 9.0 (64) the sys% table list is as follows.

Number of Tables in Database KC is 53.
Number of Columns in Database KC is 328.
Number of Indexes in Database KC is 77.
Number of users connected: 1.
   Tables in the Database KC

   Name                  Columns      Rows   Comments
--------------------- ------- --------- ---------------------------------
   SYS_COLUMNS                14       316
   SYS_COMMENTS                2        34
   SYS_CONSTRAINTS             7        52
   SYS_DEFAULTS                4        28
   SYS_FORMS                   3         0
   SYS_FORMS2                  4         0
   SYS_FORMS3                  7        24
   SYS_INDEXES                24        77
   SYS_LABELS                  3         0
   SYS_LABELS2                 4         0
   SYS_LABELS3                 7         0
   SYS_LAYOUTS                 2         0
   SYS_LAYOUTS3                3         1
   SYS_MERGE                   6         0
   SYS_PROCEDURES             10         8
   SYS_PROC_COLS              10         4
   SYS_PROC_MODS               8        34
   SYS_REPORTS                 3         0
   SYS_REPORTS2                4         0
   SYS_REPORTS3                7         5
   SYS_RULES                   6         0
   SYS_SERVERS                 4         0
   SYS_TABLES                 11        51
   SYS_TRIGGERS                4         0
   SYS_TYPES                  14        14
   SYS_VIEWS                   3         4


On 24/01/2011 8:27 AM, [email protected] wrote:

Two issues with the LOAD.

1: The mentioned table is included in the UNLOADed structure file. So I need to confirm

that it should not be included and that I should delete it out.

2: This database has several ODBC tables (64 total), none of which correctly connect

back when loading the UNLOADED file. The process always errors out due to unsupported

data types and unsupported column names in the foreign ODBC tables. I will have to develop

a routine to properly attach all these ODBC tables before I can do a complete Unload / Load

procedure. Surprisingly, this is no small task as many of the tables have 100+ columns.

(However, it is a function I need to get completed one of these days.)

So for now, I need confirmation that the suspect table Sys_Comment_ID indeed should be

eliminated.

Thanks,

-Bob





----- Original Message -----
From: "Jim Belisle" <[email protected]>
To: "RBASE-L Mailing List" <[email protected]>
Sent: Monday, January 24, 2011 9:06:20 AM
Subject: [RBASE-L] - RE: Corrupt or invalid table

Were you able to do an UNLOAD LOAD since the last corruption last week?

That may tell you what the problem is.

James Belisle

------------------------------------------------------------------------

*From:*[email protected] [mailto:[email protected]] *On Behalf Of *[email protected]
*Sent:* Monday, January 24, 2011 8:58 AM
*To:* RBASE-L Mailing List
*Subject:* [RBASE-L] - Corrupt or invalid table

I seem to have a corrupt or invalid table in my database.

R>list table sys_comment_id

   Table: SYS_COMMENT_ID       No Lock(s)

   Triggers:
 No. Column Name        Attributes
--- ------------------ ------------------------------------------------------
   1 SYS_COMMENT_ID     Type   : INTEGER
                        Index  : SINGLE-COLUMN
   Current number of rows:      0

I am assuming that this "sys_comment_id" table is not correct.

I had a database corruption last week and another this morning.  I

suspect it has to do with something related to this possibly errant table.

Seems like I have seen this on the list sometime in the distant past.

(version 7.5)

Any suggestions?

Thanks,

Bob



Reply via email to