Roberto, November 12, 2017 - 6:02 pm UTC
This is happening again. I did open a case with support but we havent made much progress. I did set an event to dump the error stack when the error happens and I have provided it to support multiple times (because it is not always the same).
What other options do we have to identify what is going on? The issue comes and goes. It is not always the same SQL and/or even the same PeopleSoft program -- but always on SQR programs.
November 13, 2017 - 3:27 pm UTC
I would log a call with Support and provide that trace.
A reader, November 13, 2017 - 4:05 pm UTC
November 14, 2017 - 1:15 am UTC
If you're unhappy with the response from Support, ask for an escalation. You pay good money for Support - use it to your best advantage.
Other avenues of exploration - are you using a multibyte characterset ? I'm wondering whether a characterset conversion somewhere along the line is taking you over a limit.
Server error triggers
Rajeshwaran Jeyabal, November 14, 2017 - 12:16 pm UTC
November 15, 2017 - 2:05 am UTC
Certainly worth looking at.
Gh, November 14, 2017 - 6:43 pm UTC
DIAGNOSTIC_DEST parametrr value?
ORA-01460 in 12cR1 and 12cR2
suk, August 15, 2018 - 5:25 am UTC
Run this code Block in 12cR1 and 12cR2 will have different behavior. Maybe this will help.
l_str varchar2(4001) := rpad('x', 4001, 'k');
l_x := substr(l_str, 1, 1);
select substr(rpad('x', 4001, 'k'), 1, 1) into l_x from dual;
select substr(l_str, 1, 1) into l_x from dual;
August 22, 2018 - 1:44 am UTC
Thanks for the input.
Facing same issue
Ruperto Herrera, September 23, 2022 - 3:05 pm UTC
Was there a resolution to this problem? Random ORA-01460 errors also starting popping up at our institution. Same symptoms as reported here: PeopleSoft, while executing SQRs.
In our case, restarting the SQR doesn't fix it, and the only reliable solution we've found so far is to either restart the database or flush the shared pool.
Oracle support has also not been helpful.
Any input will be appreciated.
September 26, 2022 - 10:31 am UTC
Have you captured a full errorstack?
alter system set events '1460 trace name errorstack level 3';
for one ocurrence, or
alter system set events '1460 trace name errorstack level 3, forever'
for all of them?
That's what Support will need.
thanks for suggestion
Ruperto Herrera, September 28, 2022 - 9:32 pm UTC
Thanks for the suggestion on the errorstack. It's been set, and we now wait for the next occurrence.
September 29, 2022 - 12:29 am UTC
glad to help - keep us posted on how things go