В дополнение к моему посту:
Symptom
- Required locales are not available on Solaris OS (SunOS)
- Errors in locale character properties (CTYPE, WCTYPE)
Other terms
Locale, SunOS, Solaris, TCP0C, character properties, CTYPE, WCTYPE
Reason and Prerequisites
This document addresses some issues with OS locales in an R/3
environment on the Sun Solaris platform:
1. There are several reasons why a locale required by R/3 is not
available on the OS level:
1. Locale package is not installed. In this case, identify
the package name and install it. One common problem has been
that only the 32 bit locale is installed while the 64 bit
locale is required.
A typical R/3 error message for a missing locale is
TEXTENV_INVALID in the work process developer trace.
2. Change in locale name due to change in relevant standards like
ISO-639 or ISO-3166. This affects migrations between Solaris
releases.
3. Change in locale name due to adoption of X/Open compliant naming
scheme:
xx_YY.codepage
where xx : Language as defined in ISO-639
YY : Country as defined in ISO-3166
codepage : Codepage used for locale (e. g. ISO-8859-X)
This also affects migrations between Solaris releases.
4. Documentation errors (e. g. some erroneous locale names in
Solaris 2.5 Internationalization Guide)
5. Errors in setup of R/3 table TCP0C (e. g. locale zh_TH.big5)
2. Other problems are differences in the Sun and SAP specification of
character properties in some locales. These are typically minor but
should be corrected nevertheless.
Depending on the Solaris release (2.6, 7 or
, there are patches
available to fix most of the problems. In a few rare cases (described
below), a patch could not be created and some changes need to be done
by a user with root authority.
Some background technical information:
- Solaris locales consist of several files located under
/usr/lib/locale/<locale>/ (32 bit)
/usr/lib/locale/<locale>/sparcv9/ (64 bit, Solaris 7 and later)
One central part of a locale is a shared object file
32 bit, Solaris 2.6 and earlier:
/usr/lib/locale/<locale>/<localename>.so.1
32 bit, Solaris 7 and later:
/usr/lib/locale/<locale>/<localename>.so.2
64 bit, Solaris 7 and later:
/usr/lib/locale/<locale>/sparcv9/<localename>.so.2
This file contains e. g. the character properties in a given locale.
Besides that, more complex locales may contain other files required
for a complete implementation.
- Over the years, the naming scheme for locales has evolved, and now
the X/Open compliant naming scheme menitoned above is widely
accepted
For backward compatibility, Solaris supports a number of older
locale names. This is typically implemented via soft links to the
files implementing the locale with the X/Open compliant name. This
is a strategy employed by a number of the Solaris patches described
in this note.
Through these soft links, application programs (like SAP R/3)
looking for a given locale name are ensured to work even if they do
not specifically search for an X/Open compliant locale name.
- Other patches described in this note replace the shared object file
to correct problems with character properties specified in them.
- Important note: NONE of the patches described below contains
COMPLETE locale packages! These are corrections to EXISTING locales.
Some confusion was created when, after installing a patch,
it appeared on the OS level that new locales were
installed. This is due to a problem when checking for installed
locales (see below).
The patch descriptions below contain lists of the Solaris packages
required for the locales corrected by the patch.
Solution
Please see note 39473 and install the latest version of TCP0C. The
following hints require that this has been completed. If you still
have a problem after installing latest TCP0C, read on the following
text.
This section contains the following subsections:
1. How to check for existing locales
2. A list of known problems an their solutions
3. How to create locale links
4. A suggested workflow for diagnosing locale problems (feedback
from the field)
1. To check for existing locales, several options exist, and each
option has pros and cons:
a. All Solaris releases:
ls -al /usr/lib/locale
b. Solaris 2.5 and later also offer this option:
locale -a
which pretty much executes the same command as option a.
c. Note that neither a. nor b. performs a functional check of a
locale. In addition, a. and b. can be fooled by directories
created under the /usr/lib/locale path, i. e. each directory
there is reported as a locale name, even if the directory is
empty! This is a situation that can be created when some of the
patches below are applied.
For a functional check of a locale, SAP provides the nls_check
tool (see OSS note 40815). nls_check is a binary executable
which can be downloaded and run on the system to test.
It is important to make sure the correct locales are tested,
since nls_check can test 32 and 64 bit locales. So if it is
unclear whether a 32 or a 64 bit SAP kernel is being used, one
simple approach to answer this is to change to the directory
where the disp+work executable (which is the SAP kernel) is
located and issue the Solaris "file" command:
# file disp+work
This reports whether this is a 32 or a 64 bit kernel, and thus
which locales need to be tested using nls_check.
d. For most locales, it is sufficient to check for the existence of
the shared objects mentioned above:
32 bit, Solaris 2.6 and earlier:
ls -al /usr/lib/locale/<localename>/<localename>.so.1
32 bit, Solaris 7 and later:
ls -al /usr/lib/locale/<localename>/<localename>.so.2
64 bit, Solaris 7 and later:
ls -al /usr/lib/locale/<localename>/sparcv9/<localename>.so.2
The files can be present as flat files or as soft links. In the
latter case, it is recommended to use additionally
32 bit, Solaris 2.6 and earlier:
ls -lL /usr/lib/locale/<localename>/<localename>.so.1
32 bit, Solaris 7 and later:
ls -lL /usr/lib/locale/<localename>/<localename>.so.2
64 bit, Solaris 7 and later:
ls -lL /usr/lib/locale/<localename>/sparcv9/<localename>.so.2
to make sure the link target exists, too.
Missing locales have to be installed on the OS level before
applying any patches. A number of cases are covered in the rest of
this note. Ask your hardware vendor for help if necessary.
2. Please also check this list of known problems and their solution:
2.1. Locale: en and en_US
- Problem:
- The English locale was named "en" up to (and including)
Solaris 2.5.1 and "en_US" as of Solaris 2.6
- Solution:
- Appropriate links need to be created
on the OS level (see section 4. on how to do this)
2.2. Locale: ar
- Problem:
- Minor changes in character properties required
- Solution:
- Apply these patches:
109560 (Solaris 7)
110053 (Solaris
- Required packages:
SUNWploc1 : for 32 bit, Solaris 7
SUNWplc1x : for 64 bit, Solaris 7
SUNWnafos : for 32 bit, Solaris 8
SUNWnafox : for 64 bit, Solaris 8
2.3. Locales: su and en_UK
Note: From release 7.00 support package SAPKB70005 on there should be no problem.
For older releases the following problem exists:
- The names of these locales changed when moving from
Solaris 2.6 to Solaris 7:
en_UK -> en_GB
su -> fi
- Solution:
- Apply these patches:
107900 (Solaris 7)
109778 (Solaris
- Note that no patch has been created for Solaris 9 or later.
At some point support for such obsolete information
has to be discontinued.
If these old locale names are still required on these OS
versions, please use the procedure to create OS links
as described section 3 for 32 and 64 bit, as necessary.
- Note that these patches work for the 32 bit locales only.
Since su and en_UK were available on Solaris 2.6 and
earlier releases, no 64 bit locales ever existed and thus
no links for 64 bit locales are created by these patches
on the Solaris releases supporting 64 bit
(Solaris 7 and
.
- Note that if 64 bit support is required for any of
these locales, the operating system links need to be
created manually as outlined in section 3. For the reasons
described above, this is necessary for _all_ Solaris
versions of 7 and later, if 64 bit support is required.
- Required packages:
SUNWploc : for locale en_GB, 32 bit, Solaris 7
SUNWploc1 : for locale fi, 32 bit, Solaris 7
SUNWweuos : for locale en_GB, 32 bit, Solaris 8 and 9
SUNWneuos : for locale fi, 32 bit, Solaris 8 and 9
2.4. Locales: cs, iw, ro, sh, sk
- Problem:
- These locale names are contained in older versions of the
R/3 table TCP0C. An investigation of Solaris releases
2.5.1, 2.6, 7 and 8 revealed that said locales never
existed in any release, so they have been replaced in the
latest revisions of this table.
- The most likely reason for inclusion of these locales in
table TCP0C was a documentation error in the Solaris 2.5
release, where these locales were listed as supported
- This is the current Solaris support matrix for these
languages:
Language R/3 2.5 2.6 7 8 ISO
------------------------------------------------------
Czech cs cz cz cz cz cs
cs_CZ
cs_CZ.ISO8859-2
Hebrew iw - - he he he
he_IL he_IL
Romanian ro - - ro_RO ro_RO ro
ro_RO.ISO8859-2
Serbo-Cr. sh - - - sh_BA -
sh_BA.ISO8859-2@bosnia
Slovak sk - - sk_SK sk_SK sk
sk_SK.ISO8859-2
------------------------------------------------------
(ISO-639 was taken from the URL
http://www.loc.gov/standards/iso639-2/bibcodes.html)
- Solution:
Use the latest Version of TCP0C as described in note
39473.
2.5. Locales: da, de_CH, en_US, en_UK, es, fi, fr, he, hu,
is_IS.ISO8859-1, it, nl, nl_BE, no, pl, pt,
ro_RO, sk_SK, su, sv
- Problem:
- Minor changes in character properties required (please
also note the remarks on locales cs, iw, ro, sh and sk
above)
- Solution:
- Apply these patches:
109281 (Solaris 2.6)
109776 (Solaris 7, 32 bit)
110425 (Solaris 7, 64 bit)
109778 (Solaris
Note: 109778-09 and higher supersede 109357. If 109357
is installed on a system, it needs to be removed
before applying 109778.
- Required packages (Solaris 2.6):
SUNWploc : for locales de, en_AU, en_CA, en_UK, en_US,
es, fr, it
SUNWploc1 : for locales cz, da, de_AT, de_CH, el, en_IE,
en_NZ, et, fr_BE, fr_CA, fr_CH, hu,
lt, lv, nl, nl_BE, no, pl, pt,
pt_BR, ru, su, tr
- Required packages (Solaris 7, 32 bit):
SUNWploc : for locales de, en_AU, en_CA, en_GB, en_US,
es, fr, it, sv
SUNWploc1 : for locales bg_BG, cz, da, de_AT, de_CH, el,
en_IE, en_NZ, et, fi, fr_BE, fr_CA,
fr_CH, he, hr_HR, hu, lt, lv, mk_MK,
nl, nl_BE, no, pl, pt, pt_BR, ro_RO,
ru, sk_SK, sl_SI, tr
- Required packages (Solaris 7, 64 bit):
SUNWplcx : for locales de, en_AU, en_CA, en_GB, en_US,
es, fr, it, sv
SUNWplc1x : for locales bg_BG, cz, da, de_AT, de_CH, el,
en_IE, en_NZ, et, fi, fr_BE, fr_CA,
fr_CH, he, hr_HR, hu, lt, lv, mk_MK,
nl, nl_BE, no, pl, pt, pt_BR, ro_RO,
ru, sk_SK, sl_SI, tr
- Required packages (Solaris 8, 32 bit):
SUNWceuos : for locales de_CH, hu, pl, sk_SK
SUNWeeuos : for locale ro_RO
SUNWmeaos : for locale he
SUNWnamos : for locale en_US
SUNWneuos : for locales da, su, is_IS.ISO8859-1, no, sv
SUNWseuos : for locales es, it, pt
SUNWweuos : for locales en_UK, fr, nl, nl_BE
- Required packages (Solaris 8, 64 bit):
SUNWceuox : for locales de_CH, hu, pl, sk_SK
SUNWeeuox : for locale ro_RO
SUNWmeaox : for locale he
SUNWnamox : for locale en_US
SUNWneuox : for locales da, is_IS.ISO8859-1, no, sv
SUNWseuox : for locales es, it, pt
SUNWweuox : for locales fr, nl, nl_BE
2.6. Locales: th, ko, zh, zh_TW.BIG5
- Problem:
- Minor changes in character properties required
- Solution:
- Apply these patches:
111190 (Solaris 7)
111188 (Solaris
- Required packages:
SUNWtleu : 32 bit, Solaris 7 and 8
SUNWtleux : 64 bit, Solaris 7 and 8
2.7. Locale: zh_TW.big5
- Problem:
- This locale name appears in older versions of table TCP0C.
In more recent versions, this has been corrected to
zh_TW.BIG5, which corresponds to the Solaris locale name
which was available as of version 2.6.
- Solution:
- No patch is available for this problem due to its nature.
Using the latest version of TCP0C should solve the
problem. If zh_TW.big5 is required, appropriate links
need to be created on the OS level (see section 4. on how
to do this)
2.8. Locales: da, de, de_CH, el, es, fr, fr_BE, fr_CA, fr_CH, hu,
it, nl, nl_BE, no, pl, pt, ru, sv, tr
- Problem:
- Backward compatibility was broken for these locales in
their 64 bit version when moving from Solaris 7 to
Solaris 8 after these locale names were made X/Open
compliant.
- The 32 bit locales are not affected by this
- Solution:
- Apply these patches:
109778 (Solaris
- Required packages (32 bit):
SUNWweuos : for locale en_UK
SUNWneuos : for locale su
- Required packages (64 bit):
SUNWceuox : for locales de, de_CH, fr_CH, hu, pl
SUNWeeuox : for locales ru, tr
SUNWnamox : for locale fr_CA
SUNWneuox : for locales da, no, sv
SUNWseuox : for locales el, es, it, pt
SUNWweuox : for locales fr, fr_BE, nl, nl_BE
2.9. Locales: sh_BA, he_IL, nl_BE
- Problem:
- The 64 bit locale links are missing in Solaris 9, thus
these locales do not work correctly for 64 bit
applications.
- Solution:
- Apply patch 113228 (Solaris 9)
- Note that this applies to the Solaris 9 FCS version.
This bug is supposed to be fixed in subsequent
updates to Solaris 9.
- Note also that several other missing 64 bit locale
links are created for locales not used by SAP. Check
the README file of this patch for details.
2.10. Locales: ja_JP.SJIS and ja_JP.PCK
- Problem:
- The Japanese locale was named "ja_JP.SJIS" up to (and
including) Solaris 2.5.1 and "ja_JP.PCK" as of Solaris 2.6
- Solution:
- Appropriate links need to be created
on the OS level (see section 4. on how to do this)
- Note that as of R/3 release 4.5B, table TCP0C contains the
locale name "ja_JP.PCK"
2.11. Locale: hu
- Problem:
- The collation sequence in the locale is wrong,
resulting in incorrect sorting results
- Solution:
- Apply these patches:
110271 (Solaris 2.6)
109625 (Solaris 7)
110251 (Solaris
- Required packages: see section 2.5.
2.12. Baltic locale support:
- Problem:
- Support for the Baltic locales (et, lt, lv) within the
SAP system is based on codepage ISO8859-4, which is not
compatible with the codepages used by Solaris.
- Solution:
- Sun has created patches to support the three
Baltic locales et, lt, and lv as of Solaris 8 with
the codepage ISO8859-4. Note that these are point
patches, meaning that they are supported for SAP use only.
How to obtain these patches:
- go to
http://sunsolve.sun.com/point
- read the note and continue
- enter the patch number including the revision to
download the file. Currently, enter these numbern:
114311-03 for Solaris 8
114888-01 for Solaris 9
2.13. A specific customer problem:
One customer with Solaris 2.5 and R/3 4.0B reported, that
long running jobs died after two hours with TEXTENV_INVALID.
A test program to search for that problem is RSCP0118. For
that customer, the problem was solved by installing the
latest Solaris kernel patches which then also required the
jumbo-patches 103594-18, 103612-51, 103627-08, 103640-26,
103663-15, 103934-09, 104735-02 and 105732-02.
3. Technical background information: How to create locale links
To make an existing locale available under a different name at the
OS level, follow these steps:
Example: - locale 'fo_FO' exists on the OS level
- locale 'fo' is required, but not available
- the properties required for locale 'fo' are available
in the locale 'fo_FO', i. e. it is required to make
locale 'fo' available via links to locale 'fo_FO'
1. Acquire root authority
2. cd /usr/lib/locale
3. Create the directories:
mkdir fo (Solaris 2.6 and earlier)
mkdir -p fo/sparcv9 (Solaris 7 and later)
The access rights must be drwxr-xr-x .
4. Create the 32 bit link:
cd fo
ln -sf ../fo_FO/fo_FO.so.2 ./fo.so.2
cd ..
Similarly for all other shared libraries (*.so.*) in the same
directory.
5. Create the 64 bit link (on Solaris 7 and later only):
cd fo/sparcv9
ln -sf ../../fo_FO/sparcv9/fo_FO.so.2 ./fo.so.2
cd ../..
Similarly for all other shared libraries (*.so.*) in the same
directory.
4. Suggested workflow when suspecting locale problems:
4.1. Read the appropriate SAP notes:
a) 39739
b) 360438
c) 39473
d) 42781
e) 15023
4.2. Add all desired language (locale) packages:
The language packages must be added prior to applying the
required patches.
Some international languages are available on CD only if the
international CD set was ordered. They are not normally
supplied in the "standard U.S." CD set.
Here is what's supported on the main Solaris 8 CD:
SUNWauaox Australasia 64-bit OS Support
SUNWauaos Australasia OS Support
SUNWcamox Central America 64-bit OS Support
SUNWcamos Central America OS Support
SUNWceuox Central Europe 64-bit OS Support
SUNWceuos Central Europe OS Support
SUNWeeuox Eastern Europe 64-bit OS Support
SUNWeeuos Eastern Europe OS Support
SUNWsamox Southern America 64-bit OS Support
SUNWsamos Southern America OS Support
SUNWseuox Southern Europe 64-bit OS Support
SUNWseuos Southern Europe OS Support
SUNWweuox Western Europe 64-bit OS Support
SUNWweuos Western Europe OS Support
Other languages are supported on the International versions,
please see
http://www.sun.com/solaris/global/
International versions of Solaris 8 contain a CD labeled
Solaris 8 Installation Multilingual SPARC Platform Edition
-or -
Solaris 8 Installation Multilingual Intel Platform Edition
instead of the English version of the SPARC or IA
installation CD.
International versions also include two CDs labeled:
Solaris 8 Documentation European SPARC/Intel Platform Edition,
which contains English, French, German, Italian, Spanish, and
Swedish documentation
Solaris 8 Documentation Asian SPARC/Intel Platform Edition,
which contains Simplified and Traditional Chinese, Japanese,
and Korean documentation instead of the CD labeled Solaris
8 Documentation English SPARC/Intel Platform Edition.
Only international versions of Solaris 8 contain the CD
labeled Solaris 8 Languages SPARC Platform Edition or Solaris
8 Languages Intel Platform Edition.
4.3. For Solaris 8, apply this patch:
109778
If you have applied these before installing the language
support (locale), back them out, install the language support,
and apply them again. Even though the patch summaries may not
appear applicable to the language or locale support, all three
of these patches are required.
Important note: NONE of these patches contains COMPLETE
locale packages! These are corrections to EXISTING locales.
4.4. Verify that all the required locales are available in all
required versions (e. g. 32 and/or 64 bit) using the methods
described in subsection 1.
4.5. Restart R/3 to verify whether the problem is silved. No
reboot of the server is required.
Вход
Регистрация
FAQ пользователя
Поиск
