Hello,
We've just setup Datastage 8 with NLS enabled. Previously we were working on 7.5 without NLS. So I have no NLS experience
Our Oracle DB is set to american_america.al32utf8 , while the client connection is configured as NLS_LANG=AMERICAN_AMERICA.WE8MSWIN1252. (this is something that's working for a lot of other applications allready and something we can't change.)
Importing table structures into Datastage is no problem. When I set the NLS in datastage to windows-1252 I get no error and no records when viewing data.(there are records in the table) When I set to any other I get an error like:
The NLS character map <UTF-8> specified may not be compatible with
the character set specified by NLS_LANG;
you may get unexpected results from your database.
And also no records.
When I run the job with NLS as windows-1252 I get an info in the log:
'20952 Bus Error - core dumped'
(number changes every time) after which the job aborts.
I have no clue anymore, anyone with more experience?
NLS problem to Oracle DB
Moderators: chulett, rschirm, roy
-
ray.wurlod
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Please Search the forum for how to deal with NLS_LANG which is actually nothing at all to do with DataStage; it is an environment variable used by Oracle. Nonetheless it has to be set (correctly) for DataStage to interact successfully with Oracle.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
I don't have access to the premium content right now (request is in the internal pipeline...) so I can only see your first line.
I know NLS_LANG is an oracle specific thing. However I need to follow standards which are applied to our full unix environment. One of these is that no Oracle settings are coded in any environment. We need to call an overall set oracle profile script. Outcome of that is the situation above.
This is something that works for all other applications in our company.
One problem for me is that the names of the possible NLS values look alike but are not the same. Is there maybe some mapping between the Oracle names and the datastage-names?
I know NLS_LANG is an oracle specific thing. However I need to follow standards which are applied to our full unix environment. One of these is that no Oracle settings are coded in any environment. We need to call an overall set oracle profile script. Outcome of that is the situation above.
This is something that works for all other applications in our company.
One problem for me is that the names of the possible NLS values look alike but are not the same. Is there maybe some mapping between the Oracle names and the datastage-names?
So... you have a single Oracle script all jobs should use or different ones for different situations? Still suggest you search for previous NLS_LANG conversations, see if any help.Chulett,
We have a single oracle PROFILE script which is indeed used for all unix scripts. This script is offcource smarter then just setting the same environment for all scripts .
At this point we solve this with a workaround:
if we select from oracle using the 'table' option it fails. When changed to 'auto-generated sql' it works. We can continue with this for now, but will have problems in the future when we need to migrate an other project to this server where the migration effort will become bigger.
We have a single oracle PROFILE script which is indeed used for all unix scripts. This script is offcource smarter then just setting the same environment for all scripts .
At this point we solve this with a workaround:
if we select from oracle using the 'table' option it fails. When changed to 'auto-generated sql' it works. We can continue with this for now, but will have problems in the future when we need to migrate an other project to this server where the migration effort will become bigger.