> >To FB Gurus, is there a way of doing a metadata only restore from a
> >database that contains data as well? This would be a useful feature
> >for data pumping if you had to restore one at a time, then correct,
> >then pump.
>
> Not clear what you mean by this. There is the -o[ne_at_a_time]
> switch that enables you to restore tables...well....one at at
> time. :-) So it will stop during the restoration of a table with
> metadata errors (unlikely) or error-prone data.

Often the 'one at a time' switch allows you to recover the all the
data.

I have seen problems before where a parameter was changed in a stored
procedure that was nested inside another stored procedure, and for
whatever reason the dependency was not detected. Others have had
problems where there are duplicates in the primary key due to an old
bug where you could deactivate the PK index.

In both these cases, all of the data itself is recovered but the
indices, stored procedures, and constraints are in a bit of a mess.
Take for example a duplicate PK value (however it got there). You can
identify the value and delete the duplicate. Now your database is
fine, but you need to enable indices and create constraints. This
goes into the too much work basket, and you create an empty structure
and use a datapump tool.

At the moment (from what I can see), you either need to have a blank
with the same structure, or have access to a database with the same
structure (which of course you should). But the structure is
correctly stored in the fbk file, it is simply the data you are
trying to restore into it is bad. I can't see any reason why a
metadata only restore could not be made from a backup file which also
contained the data, you would just skip it. This metadata only
restore would be a good basis to use as a datapump destination.

Adam