>In my case I dropped all of the relevant foreign keys and primary keys and
created them again. However, more than once, when I did that, the rows in
the FK table disappeared, so do backup or unload data for table before you
try to correct.

 

That's how I first discovered the issue.  Lost 700,000  invoices PK after
adding a new column, (or dropping one).  All FK tables appeared OK but they
the PK FK relationship is broken.

 

Pretty scary  at 3:00 AM.  Glad I had several backups of the database.

 

Kenny

 

From: [email protected] [mailto:[email protected]] On Behalf Of Bill Downall
Sent: Wednesday, May 02, 2012 12:50 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: Constraint troubleshooting?

 

Karen,

 

I have seen that error -- several times, actually, in the same database --
but in my case a LIST CONSTRAINTS showed Primary Key where it should have
said Primary Key Referenced.  I haven't seen it for a long time. That
database has been healthy for many months.

 

In my case I dropped all of the relevant foreign keys and primary keys and
created them again. However, more than once, when I did that, the rows in
the FK table disappeared, so do backup or unload data for table before you
try to correct.

 

Bill

On Wed, May 2, 2012 at 12:47 PM, <[email protected]> wrote:

We used "unload all" to recreate the database for a recent upgrade from 7.6
to 9.1 64-bit.   An autochk on the database gives us 6 instances of an error
"A foreign key references a table not known to be referenced" on various
tables.  

First I used some existing code I had to create a cursor thru all FK columns
and write out what PK column/table it references per the sys_indexes table,
and also displayed the "referenced" flag of that PK.   Everything looks
great.

So then I did an "unload schema" and looked at the bottom at all the FKs
(luckily only 25 of them) and all of them reference good tables & columns.
If I list each PK table, each one shows "PK referenced".

Anyone have a clue what that message means and how I can find out what the
offending entries are?    If we reload the database, the reloaded copy shows
the same errors.

Karen

 

Reply via email to