I'm having an ongoing problem with indexes are inactive.

When I run this query, all I.RDB$Index_Inactive values = 1 (Inactive)

select R.RDB$CONSTRAINT_NAME, R.RDB$INDEX_NAME as REFINDEXNAME,
I.RDB$INDEX_NAME as REALINDEX, I.RDB$RELATION_NAME,
I.RDB$INDEX_INACTIVE
from RDB$INDICES I RIGHT JOIN RDB$RELATION_CONSTRAINTS R on
I.RDB$INDEX_NAME = R.RDB$INDEX_NAME
where R.RDB$CONSTRAINT_TYPE = 'FOREIGN KEY' or R.RDB$CONSTRAINT_TYPE
= 'PRIMARY KEY'
order by R.RDB$CONSTRAINT_NAME

This is on a newly created DB, so I looked at another older DB and
they all show RDB$Index_Inactive = 0 (Active).

So I uninstalled FB Super Server and reininstalled v1.5.4.4910. Then
I created a new DB and created one table:

CREATE TABLE TEST
(
IDNUM INTEGER NOT NULL,
NAME CHAR( 10) COLLATE ISO8859_1,
CONSTRAINT PK_TEST PRIMARY KEY (IDNUM)
);

Now when I run the index query, the RDB$Index_Inactive shows as
<null>, which does not seem correct.

On the real DB, if I try to activate the PK index with

"Alter Index <table name> Active

Then run the index query, I get a message:

ISC ERROR CODE:335544333

ISC ERROR MESSAGE:
internal gds software consistency check (can't continue after
bugcheck)

and the fb log shows:

internal gds software consistency check (partner index description
not found (175))

Then I have to run a backup and restore to get an operations DB again.

I have a feeling this has something to do with my installation of FB,
however since I already did an uninstall/reinstall, I don't know what
else to do?

Short of specific suggestions from one of the experts here, can
someone just try to create a new table like my "Test" table above,
run the index query, and let me know if the RDB$Index_Inactive value
is <null>?

Thanks,

Rick