SQL3700W Device "<device>" is full. There are "<active-devices>" other active devices. Please mount new media or take appropriate action.
Explanation: The media on the specified device is full. This device is one of the "<active-devices>" + 1 target devices to which unloaded data is being directed.
User Response: Take ONE of the following actions:
OR
OR
SQL3701W The lobpaths parameter was specified, but the table does not contain any LOB or Long data. This parameter will be ignored.
Explanation: The lobpaths parameter specifies a separate target for LOB and Long data. The table does not contain any LOB or Long data, so the targets specified by the lobpaths parameter will not be used.
User Response: No action required.
SQL3702W Warning. SQLCODE "<sqlcode>" was received for device "<device>". Unload will attempt to continue without this device.
Explanation: SQLCODE "<sqlcode>" was detected for the specified device which is one of the targets for the unload. Unload will continue but will ignore this device.
User Response: The media loaded on the specified device will not contain any unloaded data and should not be included with the media supplied to the LOAD utility when the unloaded data is being loaded. In order to fix the problem with the device, look up the returned SQLCODE in the Message Reference.
SQL3703W "<xxx>" of "<yyy>" number of type "<type>" pages have been unloaded and sent to be written out to the target media.
Explanation: The table being unloaded consists of "<yyy>" pages of the specified type of data. "<xxx>" of these have been processed by the UNLOAD utility and have been sent to a media writer which will write the data to the target media.
"<type>" is one of:
Note that for Long and LOB data, "<xxx>" may be less than "<yyy>" when unload is complete, because unused space is not unloaded, but will be recreated when the data is reloaded.
Even for regular data, a final message where "<xxx>" = "<yyy>" may not be issued. Instead message 3105 is used to indicate that the unload completed successfully.
User Response: This is an informational message. No action is required.
SQL3704N The num_buffers parameter specified is invalid.
Explanation: The num_buffers parameter determines the number of buffers that the utility will use. The minimum is 2 if the lobpaths parameter is not specified and 3 if the lobpaths parameter is specified. This is the minimum required to allow the utility to work. There is, however, an optimal number of buffers that the utility will use if this parameter is not specified. This optimal number is based on the number of internal processes that the utility will have running and whether or not the lobpaths parameter was specified. If the number of buffers specified is less than the optimal number, some processes will be waiting for buffers to use. Therefore, it is recommended to specify 0 for this parameter and let the utility choose the number of buffers. Only specify this parameter if, due to the size of the utility storage heap, it is necessary to limit the amount of memory that the utility uses.
User Response: Resubmit the command using a valid num_buffers parameter.
SQL3705N The buffer size parameter specified is not valid. The buffer size must be specified as 0 or be between 8 and 16384 inclusive. For multiple buffers, the total buffer size must not exceed 16384.
Explanation: The application calling the utility has supplied a buffer size parameter that is not valid. The buffer size is used to determine the internal buffer size. The value is the number of 4K pages that are obtained for this buffer. The value must be specified as 0 or be between 8 and 16384 inclusive. If there are multiple buffers, the number of buffers multiplied by the buffer size must not exceed 16834.
When 0 is specified:
User Response: Reissue the command with a valid buffer size.
SQL3706N A disk full error was encountered on "<path/file>".
Explanation: A disk full error was encountered during the processing of a database utility. The utility stops.
User Response: Ensure enough disk space is available for the utility or direct the output to other media such as tape.
SQL3707N The sort memory size parameter specified "<size1>" is not valid. The minimum size required is "<size2>".
Explanation: The sort memory size is not large enough for sorting the keys of the index(es).
User Response: Reissue the command with a valid sort memory size.
To ensure that only the minimum amount of storage is used, specify a value of 0 (to let it default). However, using more than the minimum should improve the performance of the sort.
SQL3783N An error was encountered while opening the copy location file. Open file error code is "<errcode>".
Explanation: During load recovery, an error was encountered while opening the copy location file. The operating system file open return code is returned.
User Response: Look at the error code in the message for more information. Correct the error, if possible, and resubmit the command.
SQL3784W Invalid data was encountered while reading from the copy location file. Failure occurred at line "<line-no>" with error type "<errtype>"
Explanation: During load recovery, invalid data was encountered while reading from the copy location file. The line number and error type are returned. The utility waits for a response to continue.
User Response: Correct the data in the copy location file and return to the utility with the correct caller action parameter to indicate if processing should continue or terminate.
SQL3785N Load recovery for table "<schema.tablename>" at time "<timestamp>" on node "<node-number>" failed due to error "<sqlcode>" with additional information "<additional-info>".
Explanation: A severe error occurred during load recovery. The utility stops processing.
(Note : if you are using a partitioned database server, the node number indicates which node the error occurred on. Otherwise, it is not pertinent and should be ignored.)
User Response: Examine the error code in the message for more information. Take corrective action and resubmit the command.
SQL3798W An invalid value was used for parameter "<parameter>" to invoke the roll-forward recovery API to continue load recovery.
Explanation: Load recovery is in progress and one of the parameters passed in is not valid for the current state of load recovery.
User Response: Correct the value in error and return to the utility with the correct caller action parameter to indicate if processing should continue or terminate.
SQL3799W Load recovery for table "<schema.tablename>" at time "<timestamp>" on node "<node-number>" is pending due to warning "<sqlcode>" with additional information "<additional-info>".
Explanation: A warning condition is encountered during load recovery. The utility waits for a response to continue.
(Note : if you are using a partitioned database server, the node number indicates which node the error occurred on. Otherwise, it is not pertinent and should be ignored.)
User Response: Examine the error code in the message for more information. Take corrective action and return to the utility with the correct caller action parameter to indicate if processing should continue or terminate.