Troubleshooting
Problem
Need a way to globally set the option "Disable NFC" Loading some UTF8 data in table throws the following error message “not NFC - combining marks are not in canonical order”.
Diagnosing The Problem
Loading some UTF8 data in table throws the following error message
“not NFC - combining marks are not in canonical order”.
This is the correct error message. However, this has a workaround of using “disableNFC” option with nzload and external table.
Automated load job fails because of such UTF8 characters which actually represent good data.
Resolving The Problem
In order to disable the NFC option globally, a registry variable “disableNfcGlobally” has been included in 7.2.1.5-P2 release.
Default value of the variable is off.
a) To enable the feature temporarily, perform the following steps:
1. Pause the system by executing the following command:
nzsystem pause
2. Set the value of the “host.disableNfcGlobally” registry variable to yes or on by issuing the nzsystem set -arg command. An example follows:
nzsystem set -arg host.disableNfcGlobally=yes
3. Resume the system by executing the following command:
nzsystem resume
b) To enable the feature so that it remains in effect after a NPS system restart, perform the following steps:
1. Log in to the system as the root user.
2. Using a text editor such as vi, edit the /nz/data/config/system.cfg file.
3. Set the value of the host.disableNfcGlobally registry variable to yes or on. An example follows:
host.disableNfcGlobally=yes
4. Save and close the system.cfg file.
The changes to the system configuration file take effect when the NPS system restarts.
If option “disableNfcGlobally” is set, you need not additionally use “-disableNFC” option in nzload or ‘using’ clause of the external table. If existing scripts still use these options, it should not have any adverse effect as disableNfcGlobally takes precedence over command line argument.
Was this topic helpful?
Document Information
Modified date:
17 October 2019
UID
swg22013207