Informix Error -26386: Could not parse r macro in CLOBDIR %s.
Cause and resolution
Could not parse r macro in CLOBDIR %s.
Could not parse the formatting macro r in CLOBDIR string. Refer to the example below for the correct usage:
CREATE EXTERNAL TABLE exttab (col1 INTEGER, col2 BLOB, col3 CLOB) USING ( DATAFILES ( "DISK:/tmp/ext_byte.dat.%r(1..2); CLOBDIR:/tmp/clobdir1.%r(1..2); BLOBDIR=/tmp/blobdir1.%r(1..2)" ), DELUXE, DELIMITER "%", recordend "\n", maxerrors 20, rejectfile "/tmp/ext_byte.log" );
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-26386 fires when the %r macro in a CLOBDIR string can't be parsed — per the official
guidance.
- Incorrect
%rmacro syntax in theCLOBDIRstring, per the official guidance — the direct, only cause.
Solutions / Resolution
- Correct the
%rmacro's syntax inCLOBDIR, per the official guidance, e.g.CLOBDIR:/tmp/clobdir1.%r(1..2).
Examples
N/A
No specific triggering statement is documented beyond malformed %r macro syntax; see
the official guidance's own CLOBDIR:/tmp/clobdir1.%r(1..2) example for correct usage.
Diagnostic Checks
- Check the
CLOBDIRstring's%rmacro syntax, and correct it.
Related Errors / Related Topics
- -26385 — "Could not parse r macro in BLOBDIR %s." The same class of
%r-macro parsing error, forBLOBDIRrather thanCLOBDIR. - -26388 — "Cannot use r macro in CLOBDIR %s without having a matching macro in
filename %s." A related
%r-macro error, on a missing matching macro in theDATAFILESfilename rather than theCLOBDIRmacro's own syntax. - -26390 — "Range for r macro in CLOBDIR %s does not match range in filename %s." A
related
%r-macro error, on a range mismatch rather than the macro's own syntax.
The %r macro in a CLOBDIR string couldn't be parsed — correct its syntax.