Gary said...Undocumented but a dbms_metadata.get_ddl( object_type => 'PROCOBJ' on your scheduler jobs in 12.2 shows SET_ATTRIBUTE API now covers changing NLS values.
Before you had change the session settings and drop/recreate the job.
dbms_scheduler.set_attribute('JOB','NLS_ENV','NLS_LANGUAGE=''AMERICAN'' NLS_TERRITORY=''AUSTRALIA'' NLS_DATE_FORMAT=''YYYY-MM-DD'' NLS_DATE_LANGUAGE=''AMERICAN'' ');
Sorry it's taken so long, but I've finally checked this out and added it to the article. I gave you a shout out as well. :)
Raguram Venkateswar said...How to get this enabled
In one server I do not get the NLS attribute setting's ( I get the NLS setting on other server ) . Is there a way to enable this via setting
sys.dbms_scheduler.set_attribute('"FW2_BACKUP"','NLS_ENV','NLS_LANGUAGE=''AMERICAN'' NLS_TERRITORY=''AMERICA'' NLS_CURRENCY=''$'' NLS_ISO_CURRENCY=''AMERICA'' NLS_NUMERIC_CHARACTERS=''.,'' NLS_CALENDAR=''GREGORIAN
No idea. It's undocumented. :)
I guess all I can suggest is trying it with different users, with different levels of privilege. Maybe that will make a difference???
Also, it may be version specific? Try it on different versions and see if you see a pattern.
Raguram Venkateswar said...Thanks Tim...
Mikhail K. said...Hi, Tim
About ORA-27469: STATUS is not a valid resource attribute.
This looks like a documentation bug. Try attribute => 'STATE' instead of 'STATUS'.
In documentation we see "easter egg":
In "DBMS_SCHEDULER.CREATE_RESOURCE" procedure:
state => 'ENFORCE_CONSTRAINTS'
But state is not valid attribute for this procedure.
Thanks for the heads-up.
DO NOT ask technical questions here! They will be deleted!
These comments should relate to the contents of a specific article. Constructive criticism is good. Advertising and offensive comments are bad and will be deleted!
If you post personal information (name, email address etc.) you are agreeing to them being stored and displayed. Feel free to remain anonymous.