ORA-06512/ORA-21560 [message #435124] |
Mon, 14 December 2009 07:40 |
danae.kiouf
Messages: 6 Registered: December 2009 Location: GREECE
|
Junior Member |
|
|
HELLO,
I AM TRYING TO RUN A CODE FROM ENTERPRISE MANAGER VIA A JOB(DATABASE SCHEDULER). IT RUNS FINE FOR SOME ROWS OF DATA AND THEN GIVES THE FOLLOWINF ERROR:
ORA-20001:
ORA-20001:
ERROR:-21560
ORA-21560: argument 3 is null, invalid, or out of range
ORA-06512: at "USERNAME.DATABASE", line 742
ORA-06512: at "USERNAME.CALL_LOADER", line 40
ORA-06512: at "USERNAME.EXECUTE_BATCH", line 10
ORA-06512: at "USERNAME.EXECUTE_BATCH", line 951
ORA-06512: at line 2
IF I RUN THE CODE FROM PL-SQL NO ERRORS APPEAR. DOES ANYBODY HAVE ANY IDEA ABOUT THIS?
THANKS IN ADVANCE
|
|
|
|
Re: ORA-06512/ORA-21560 [message #435127 is a reply to message #435126] |
Mon, 14 December 2009 07:58 |
danae.kiouf
Messages: 6 Registered: December 2009 Location: GREECE
|
Junior Member |
|
|
I have concluded that it is not a matter of a specific parameter.
This error is raised randomly and if i rerun again the process usually executes without problem.This process opens a file and copies tha last 4000 character in a lob field.
|
|
|
Re: ORA-06512/ORA-21560 [message #435128 is a reply to message #435127] |
Mon, 14 December 2009 07:59 |
|
ramoradba
Messages: 2457 Registered: January 2009 Location: AndhraPradesh,Hyderabad,I...
|
Senior Member |
|
|
ORA-21560: argument string is null, invalid, or out of range
Cause: The argument is expecting a non-null,
valid value but the argument value passed in is null,
invalid, or out of range.
Examples include when the LOB/FILE positional or size argument
has a value outside the range 1 through (4GB - 1),
or when an invalid open mode is used to open a file, etc.
Action: Check your program and correct the caller of the routine to not pass a null,
invalid or out-of-range argument value.
|
|
|
|
|
|
|
|
Re: ORA-06512/ORA-21560 [message #436424 is a reply to message #435169] |
Wed, 23 December 2009 08:51 |
danae.kiouf
Messages: 6 Registered: December 2009 Location: GREECE
|
Junior Member |
|
|
You should have known that the errors raised from oracle is not always the actual ones.
And more specifically the error i get is raised only when i call/execute the same part of code from a job and not from plsql developer test window.
So i have concluded that it is caused due to dinamic job generation from within another job that uses external sqlldr utility to load multiple parallel files.
so the issue is not so easy to identify
It has to do with system resources available
Thank you,
|
|
|