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

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.