The delimiters of the del file exported by DB2

The delimiters of the del file exported by DB2 are in the DB2 database. When exporting the DEL file, the default Delimiter is "and the field separator is (comma ). One requirement is to provide data for the Oracle database, so we want to use "|" as the field separator for data. After reading the export usage instructions, we found that in the file-mod mode of export, you can use CHARDELx and COLDELx to set the character separator and field separator respectively. However, when you run export to 'e: \ test.txt 'of del modified by chardel0x22 coldel0x7c select * from db2admin. after the test command, the error SQL3017N is displayed. The error description is as follows: The SQL3017N Delimiter is invalid or is used multiple times. Note: For "delimiters" ASCII (DEL) files, one of the following two errors occurs: * The specified column delimiter, string delimiter, or decimal character is invalid. * For SBCS or UTF-8 data, the valid range of delimiters is 0x00-0x7F (including 0x00 and 0x7F ). * For MBCS data, the valid range of delimiters is 0x00-0x3F (including 0x00 and 0x3F ). * For ebcdic mbcs data, the valid range of delimiters is 0x00-0x3F (including 0x00 and 0x3F). However, an exception is, the delimiters cannot be SHIFT-OUT (0x0E) or SHIFT-IN (0x0F) characters. * The same character is specified for multiple aforementioned projects. The command cannot be processed. User response: Check the validity and uniqueness of the specified delimiters. Re-submit the command and specify a valid delimiter to overwrite it. Originally, the delimiters of exported files were associated with the database code page. That is, in a database with the code page 819, any character (ASCII code) can be used as the data separator, however, databases with a code page of 1386 can only use characters with an ASCII code value in the range of 0x00-0x3F.