Re: Restoring a SQL collection library with constraints

should work...

maybe a silly question... do you have the proper authority to files
during the restore?

Constraints and triggers require different authority to apply.


On Thu, 2005-03-31 at 19:29, David Gibbs wrote:
> Folks:
> 
> I just tried to restore a customers database that was created with a
> 'create collection' command (via interactive SQL).  Many of the tables
> in this library are supposed to have primary key and foreign   key
> constraints.
> 
> However, some of the tables (in the restored library) that are supposed
> to have the constraints, do not.
> 
> I see a bunch of 'CPF9812-File ISSUES in library DATALIB not found.' and
> 'CPD32B0-Constraint is not valid.' (referring to the issues table)
> diagnostic messages in the joblog.
> 
> The CPD32B0 message is most concerning, because the file it was
> complaining about has not yet been restored.
> 
> At the end of the restore, the ISSUES table (and others) does not have a
> primary key constraint, even though it should.
> 
> Is there a special way I should be restoring the library to get the
> constraints applied correctly?  Or is it more likely that the table
> didn't have the constraint on it when it was saved?
> 
> Both the system that the database was saved from, and is being restored
> to, are V5R3.
> 
> Thanks!
> 
> david
-- 
"Bigamy is having one wife too many. Monogamy is the same."
-- Oscar Wilde