alangibson / log4plsql Goto Github PK

Hi!
Do you practice this? Please give advice.
Kind regards,
Rustam

It may be usefull to add SID (as LSID field) into table TLOG and Log4J queues. LSID field helps to identify session's logging messages.

PLOGPARAM package definition has DEFAULT_USE_LOG4J constant for LOG4J output mode in lines.

There is a check if package PLOG_OUT_AQ is installed.

A package PLOG_OUT_AQ may be installed by user: see install.sql

If PLOG_OUT_AQ package is not installed, we got an error in default output context:

SQL> exec plog.fatal( 'text' );
BEGIN plog.fatal( 'text' ); END;

*
ERROR at line 1:
ORA-20200: Parameter USE_LOG4J is TRUE but no advanced queue output (package
PLOG_OUT_AQ) is installed
ORA-06512: at "PL_SQL.PLOG", line 1432
ORA-06512: at "PL_SQL.PLOG", line 1542
ORA-06512: at "PL_SQL.PLOG", line 1824
ORA-06512: at "PL_SQL.PLOG", line 3056
ORA-06512: at line 1

For the case a developer using log4plsql misses closing sections at the end of logical structures (i do that in procedures/functions) or in exception blocks, this might lead to an error at Plog.setbeginsection when Pctx.Lsection overflows and throws a ORA-6502 in Line 342 as it would be expected.

I'd prefer the logging does not throw exceptions though :) Hopefully you do, too.

BTW thanks for the nice updates!

Kind regards,

Michael