ARC1260 Cannot use ALL PARTITIONS for table %s.%s when backup was not created with a well-defined PARTITIONS WHERE condition.
Explanation:
The ALL PARTITIONS option can only be specified on a restore statement if the bounding condition for the archived PPI table is well defined . The bounding condition is considered to be ell-defined if it can be used to determine which partitions must be deleted during a restore/copy operation.
For Whom:
End User.
Notes:
The bounding condition is generated by the database from the PARTITIONS WHERE option when the backup is generated. It defines the logical scope of rows stored on the archive file. However, there are cases such as when the UNKNOWN partition is backed up where the restore semantics may be imprecise. A restore/copy that invokes the ALL PARTITIONS option uses the bounding condition stored on the archive file to define the logical scope of what partitions are deleted and restored so we want to ensure precise semantics. This particular error message is generated when the ALL PARTITIONS option was specified on the restore/copy statement but the bounding condition stored on the archive file is inappropriate to use.
Remedy:
Correct the RESTORE/COPY statement to explicitly define the PARTITIONS WHERE clause to use.