Hi,
analyzing an PL/SQL error stack is a common task for me. In order to do that I paste the error stack from the log file into the TOAD editor, i. E.:
faktura_job.buildSendungen(‘CoWVsS0’)
begin
*
ERROR at line 1:
ORA-01403: no data found
ORA-06512: at “VS_USER.WITT_PROZESS”, line 27
ORA-06512: at “VS_USER.AUFTRAG_MO_AUFTRAGPOOL”, line 383
ORA-06512: at “VS_USER.AUFTRAG_IF_AUFTRAGPOOL_SET”, line 80
ORA-06512: at “VS_USER.FAKTURA_MO_SENDUNG”, line 475
ORA-06512: at “VS_USER.FAKTURA_MO_SENDUNG”, line 548
ORA-06512: at “VS_USER.FAKTURA_JOB”, line 505
ORA-06512: at line 2
To find out what code the failing lines contain I use the “Describe (F4)”-Dialog. Everytime I like to jump to a error line I have to delete the double quotes from the respective line in the callstack.
It would be nice if the describe dialog could jump to the line with the double quotes in place.
Regards,
Wolfgang