Hi Paul,

When you dropped and recreated the constraint, the associated index was
created with a new name. It would appear that one of your stored procedures
is referencing the old name in a PLAN statement, which is risky anyway when
the index is an RDB$ type index. In fact, the restore may be renaming a lot
of the RDB$ indexes.

Look through all your SP and triggers for PLANS, and remove them. Then
backup and restore.

If you need PLANS, then make sure the plan only references your own named
indexes.

Vince

Replication Technologies
South Africa

----- Original Message -----
From: pgrobler <paul@...>
To: <ib-support@yahoogroups.com>
Sent: Thursday, 16 May, 2002 1:07 PM
Subject: [ib-support] Urgent Help needed: Restore Error


> Hi,
>
> We have a interbase 5.6 database which had a corrupted constraint
> index. I drop and recreated the index. The first restore we did
> alerted us to the fact that the index was a problem. When we rerun
> the backup and restore process the restore failed and the following
> reason was generated:
>
> gbak: creating indexes
> gbak: ERROR: index RDB$PRIMARY42 cannot be used in the specified
> plan
> gbak: Exiting before completion due to errors
>
> Restore exited unsuccessfully on Thu May 16 04:27:08 2002
>
> The index RDB$PRIMARY42 is the index that was dropped and recreated
> but with a new name. I need to drop any reference to the
> RDB$PRIMARY42 constraint.
>
> Please help!
>
> Thanks
> Paul Grobler
> Blake & Associates
> Tel: (031) 5384000
> Fax: (031) 5384971
> Email: paul@...
>
>
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>