background image
<< Using Locale-Dependent Functions | Deploying a Database Application >>
<< Using Locale-Dependent Functions | Deploying a Database Application >>

Unacceptable NLS Parameters

Using Locale-Dependent Functions with NLS Parameters
Working in a Global Environment 6-33
Unacceptable NLS Parameters in SQL Functions
You cannot use the NLS parameters
NLS_LANGUAGE
,
NLS_TERRITORY
, and
NLS_
DATE_FORMAT
in SQL functions except for
NLSSORT
.
The
NLS_LANGUAGE
parameter can interfere with the session value of
NLS2008
LANGUAGE
. For example, if you specify
NLS_LANGUAGE
in the
TO_CHAR
function,
Oracle Database will ignore its if it different from the
NLS2008LANGUAGE
parameter value for the session.
The
NLS2008FORMAT
and
NLS_TERRITORY_FORMAT
parameters are not accepted
as parameters because they can interfere with the required format models. A date
format must be specified if an NLS parameter is used in a
TO_CHAR
or
TO_DATE
function, so
NLS2008FORMAT
and
NLS_TERRITORY_FORMAT
parameters are not
valid for these conversion functions. Oracle Database will return an error if you
specify
NLS2008FORMAT
or
NLS_TERRITORY_FORMAT
in the
TO_CHAR
or
TO_
DATE
functions.
See Also:
Specifying NLS Parameters in SQL Functions
on page 6-31
Oracle Database Globalization Support Guide for a complete
discussion of locale-dependent SQL functions with optional NLS
parameters