tag:blogger.com,1999:blog-7849367040589270673.post2653310296379858061..comments2024-03-21T22:50:39.997-07:00Comments on Obsessed with Oracle PL/SQL: PL/SQL 101: Three ways to get error message/stack in PL/SQLSteven Feuersteinhttp://www.blogger.com/profile/18405765731886460622noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-7849367040589270673.post-61454666194861252122019-10-14T06:12:31.792-07:002019-10-14T06:12:31.792-07:00Interesting... I've tried the LiveSQL commands...Interesting... I've tried the LiveSQL commands and my output is slightly different. Stack trace is included or omitted as you describe, but SQLERRM still contains the same output than DBMS_UTILITY.FORMAT_ERROR_STACK in every example. I've tested it in XE 11g, for what it matters.<br /><br />BTW, thanks to your article I found DBMS_UTILITY.FORMAT_ERROR_BACKTRACE() in Oracle documentation and it solved my immediate needs.kAlvarohttps://www.blogger.com/profile/04236929274597436375noreply@blogger.comtag:blogger.com,1999:blog-7849367040589270673.post-77894899307737690162019-10-14T04:37:31.674-07:002019-10-14T04:37:31.674-07:00Alvaro, please check out this LiveSQL script to se...Alvaro, please check out this LiveSQL script to see the differences - and verify them for yourself: https://livesql.oracle.com/apex/livesql/file/content_CSHKGPS5AHKCMUIAYYMTL1QYT.html<br /><br />They *can* be the same under some circumstances, but not always.Steven Feuersteinhttps://www.blogger.com/profile/16619706770920320550noreply@blogger.comtag:blogger.com,1999:blog-7849367040589270673.post-28919693177988967442019-10-14T04:22:26.866-07:002019-10-14T04:22:26.866-07:00DBMS_UTILITY.FORMAT_ERROR_STACK (at least in the 1...DBMS_UTILITY.FORMAT_ERROR_STACK (at least in the 11g server I have access to) contains exactly the same as SQLERRM (i.e., no strack trace or original line number, just plain error code and message).<br />:_(kAlvarohttps://www.blogger.com/profile/04236929274597436375noreply@blogger.comtag:blogger.com,1999:blog-7849367040589270673.post-13942391482380013212016-09-21T07:06:15.436-07:002016-09-21T07:06:15.436-07:00Ha! Yes, Erwin, you are absolutely correct. Will f...Ha! Yes, Erwin, you are absolutely correct. Will fix the post.Steven Feuersteinhttps://www.blogger.com/profile/18405765731886460622noreply@blogger.comtag:blogger.com,1999:blog-7849367040589270673.post-21137210450900117912016-09-21T00:00:14.584-07:002016-09-21T00:00:14.584-07:00Hi Steven,
Love the article (as usual). But wasn&#...Hi Steven,<br />Love the article (as usual). But wasn't UTL_CALL_STACK introduced in 12c instead of 11g?Anonymousnoreply@blogger.com