One of the new features of 11G is error logging in SQL*PLUS.
When executing scripts from SQLPLUS, we will have to spool the output and then check for any errors in the spool file. But if we forget to spool, we will not be able to find out the errors.
In 11G we can simply turn on the error logging and all the errors will be stored in a special table called SPERRORLOG.
Example:
SQL> show errorlogging
errorlogging is OFF
SQL> set errorlogging on
SQL> select 1/0 from dual;
select 1/0 from dual
SQL> commit;
Then we can query from any other session and see the errors:
select * from sperrorlog;
One has to commit in order to see the data in other session
We can pin all the errors to a message:
SQL> set errorlogging on identifier ‘RELEASE 2.4.0′
One has to have 11G client in order to make use of this feature.
