FUP Messages
File Utility Program (FUP) Reference Manual—523323-014
3-21
Cause. FUP ran out of internal memory space while trying to execute the command.
Effect. FUP ends abnormally.
Recovery. Restart FUP, and retry the command. If the same error occurs, call your
service provider.
Cause. The transfer of a file’s OWNER attribute failed during a duplicate operation
with the SAVEALL or SAVEID option to a remote node.
Effect. The OWNER attribute is not preserved.
Recovery. Use the GIVE command to change the owner. Remote logon might be
required.
Cause. When creating or altering a partitioned file, the numbering of the partitions was
not in the same order as the partial key values associated with the partitions.
Effect. The command fails.
Recovery. Retry the command after correcting the numbering of the partial key values
or the partitions.
Cause. The file attributes of the individual partitions of a partitioned file were
inconsistent with one another.
Effect. The command fails.
Recovery. Check the partitions, and ensure consistency by executing the necessary
FUP ALTER commands. For all partitions, check that:
ï‚·
The file type, record length, data-block length, key length, key offset, index-block
length, and index and data-compression (where applicable) attributes are the
same.
ï‚·
For relative and entry-sequenced files, the partition extent sizes are the same as
those specified when the primary partition was created.
OVERFLOW OF TABLE
OWNER NOT PRESERVED AT DESTINATION
PARTIAL KEY VALUE FOR A PARTITION IS NOT IN ASCENDING ORDER
PARTITION ATTRIBUTES ARE INCONSISTENT
PARTITION IS AN SQL OBJECT
To Next Page
Loading...
Need help?
General