Common User Errors and Corrections
The following is a partial list of common data adapter error messages that you may
encounter and their solutions.
- (FOC1351 or FOC2567) ACCESS FILE NOT FOUND
- Ensure that each Master File has an associated Access File. If this is the case,
check that the Access File exists in a library allocated to ddname FOCSQL for
MVS or has a filetype of FOCSQL for VM/CMS. The MVS member names or
CMS file names for both Master and Access Files must be identical.
- (FOC1356 or FOC2566) NO TABLE NAME FOR THE SEGMENT IN THE ACCESS FILE
- Check that both the database and table names specified by the TABLENAME
keyword in the Access File are valid. Verify that the SEGNAME values in the
Master and Access Files match.
- (FOC1377) TERADATA TABLE MUST NOT HAVE KEYS=0
- Each Teradata table used in a MODIFY procedure must have a primary key.
Edit the Master and Access Files for this table to define the primary key (see
Describing Tables to FOCUS) and resubmit the procedure.
- (FOC1388 or FOC2554) INTEGER FIELDS FOR SQL MUST HAVE ACTUAL FORMAT OF I2
OR I4
- Only ACTUAL=I2 or ACTUAL=I4 may be used in describing an integer in the
Master File. The Teradata Data Adapter supports the Teradata data types
BYTEINT, SMALLINT, and INTEGER.
- (FOC2555) ACTUAL FORMAT F IS INVALID FOR SQL, USE FORMAT D
(FOC2557) ACTUAL FORMAT Z IS INVALID FOR SQL, USE FORMAT A
- The field type equivalent of the Teradata floating-point data type, FLOAT, is D.
Currently, there are no Teradata equivalents for the single-precision
floating-point field type F or the zoned-decimal field type Z. Therefore, these
field types (F and Z) may not be used.
- (FOC1410) SQL COLUMN NOT FOUND. CHECK FIELDNAME AND ALIAS KEYWORDS
- Check the spelling of the ALIAS value in the Master File. Also, verify this in the
long field name declaration in the Access File. Check with your database
administrator to make sure the column exists in the table or re-run the
AUTODBC facility to refresh the description.
- (FOC1413) USER HAS INSUFFICIENT AUTHORITY FOR REQUESTED OPERATION
- The RDBMS has determined that you do not possess the authority to perform
the requested operation. Notify the database administrator to resolve the
error. A trace of the requested operation is recommended to identify the
RDBMS object and the type of operation causing the violation.