Jobs and Environment
I have this strange problem concerning jobs on two identical Orcale 9i Databases on two different Solaris servers.
When I create a job, one machine keeps the NLS environment parameters set on the server (as it should), but the other takes the environment from the client and uses this for the job to run on the server (which then promptly throws an error).
This problem is independent of the clients used.
The date format is the actual problem, but does anyone know how to tell the server to ignore the environment parameters of the client?
if you set NLS parameters at client side then it will be used, compare the environment variables
That's the strange thing about it. The problem lies somewhere on the server side, because independently of the local client environment settings (tested with several clients), one server responds correctly and the other takes the client environment.
Click Here to Expand Forum to Full Width