Using Oracle9i Language and Definition Files with Oracle Database 18c

Changes are made to the content of some of the language and territory definition files in Oracle Database 10g and later releases.

Changes are made to the content of some of the language and territory definition files in Oracle Database 10g and later releases. These updates are necessary to correct the legacy definitions that no longer meet the local conventions in some of the languages and territories that Oracle Database supports.

Oracle Database 18c customers must review their existing application code to ensure that the correct cultural conventions, which were introduced and defined in Oracle Database 10g, are being used.

For customers who are not able to make the necessary code changes to support their applications, Oracle Database offers Oracle9i locale definition files with this release of Oracle Database. If the Oracle Database server installation has been configured to use the Oracle9i files, then you must enable this functionality in each client installation as well.

To enable this functionality, perform the following steps:

1. Run the cr9idata.pl script, which by default is in the following location:

   ORACLE_HOME\nls\data\old

   If the installation type you chose does not include this directory, you can find the cr9idata.pl script in the same directory path in a default Oracle Database Client installation.

2. Set the ORA_NLS10 environment variable to point to the directory ORACLE_HOME\nls\data\9idata, into which cr9idata.pl copies the new language and territory definition files. ORA_NLS10 must have this value each time the affected client programs are started. Therefore, set the variable permanently in a startup script or, on the Microsoft Windows platform, set it in the Windows Registry.