> >> > Perhaps the indices for the PKs are inactive. Can you try

re-activating

> >> > it?
> >>
> >> I didn't know a PK could be made inactive. I dropped the PK and

recreated

> > it
> >> and now things are normal.
> >
> > Well, normally, this shouldn't be possible.
> >
> > But it might have happened when restoring the database with indices
> > disabled. Is that something that could be possible in your case?
> >
> >> Strange that all the PK's are doing the same thing - I wonder how this
> > could
> >> happen?
>
> Martijn
> I checked, and all the primary indexes are disabled ie. RDB$INDEX_INACTIVE

=

> 1
> when I try and reactivate them with alter index rdb$primary28 active I get
> an error "index unexpectedly deleted"
> how do I fix this?

I must admit I don't know... Perhaps something went terribly wrong
while restoring?

Dropping the constraints and re-creating them should do the job though.

With regards,

Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Server
Upscene Productions
http://www.upscene.com