ERR-01002 ( 4098) Invalid character in use#
Overview#
This document describes the cause of the ERR-01002 ( 4098) Invalid character in use error, which can occur when Altibase encounters a character that cannot be interpreted using the database character set, and explains how to resolve it.
Version#
All versions
Symptom#
The following error may occur while processing character data, for example, when a LIKE operation is performed on Korean text.
ERR-01002 ( 4098) Invalid character in use
Cause#
This error may occur when Altibase encounters a character that cannot be interpreted using the database character set while processing character data.
For example, if the database character set is KSC5601 and the table contains a character outside the range supported by KSC5601, this error may occur during character string processing.
Action#
Check the database and client character sets, and then identify the data that causes the error.
Check the Character Sets#
Run the following query to check the database and current session character sets.
SELECT *
FROM V$NLS_PARAMETERS;
Check the following parameters:
NLS_CHARACTERSET: Database character setNLS_USE: Client character set
The client character set must be compatible with the characters stored in the database.
Identify the Problematic Data#
Identify the table and character column where the error occurs.
If the error occurs only for specific data, narrow the query range using a primary key or another condition to identify the affected row.
After identifying the row, use the DUMP function to check the byte values stored in the column.
SELECT ID,
DUMP(NAME)
FROM T1
WHERE ID = 100;
Based on the DUMP result, verify whether the stored byte sequence represents a valid character in NLS_CHARACTERSET.
For example, if the database character set is KSC5601 and the byte sequence represents a character that is not defined in KSC5601 but is defined in MS949, the stored data contains a character outside the range supported by the database character set.
If the Character Set Configuration Is Incorrect#
If the client character set does not match the actual character set of the input data, change NLS_USE to the appropriate character set.
If Invalid Character Data Is Found#
Back up the affected data, replace the unsupported character with one that can be represented by the database character set, and reload the corrected data.