Home

PL'N'SQL LOGGER

This package provides logging functionality inspired by log4j for Oracle database. Logging is done to dbms_output and into a specific table. It basically provides:

• setting of a global logging level with procedure SET_LEVEL
• overriding of logging level on granularity of package and function/procedure with procedure INSERT_LEVEL_OVERRIDE or direct inserts into override table (see GC_LOG_LEVEL_OVERRIDE_TAB_NAME). Overriding can be done at run time!
• logging in levels with procedures TRACE, DEBUG, INFO, WARN, ERROR and FATAL
• switching on/off of table logging with procedures ENABLE_TABLE_LOGGING/DISABLE_TABLE_LOGGING - defaulted to OFF
• switching on/off of loggging to DBMS_OUTPUT with procedures ENABLE_DBMS_OUTPUT_LOGGING/DISABLE_DBMS_OUTPUT_LOGGING - defaulted to ON
• partial self logging
• splitting of text at the last white space character at or before a given length with
• self setup (done automagically if not switched off (see next points) with procedure SET_UP
• switching on/off of installation of objects used by it with procedures ENABLE_DB_OBJECT_INSTALL/ DISABLE_DB_OBJECT_INSTALL - defaulted to ON
• switching on/off of dropping of persistent objects (like tables) with procedures ENABLE_PERSIST_OBJ_DROPPING/ DISABLE_PERSIST_OBJ_DROPPING - defaulted to OFF
• text to log can be up to 32767 bytes. For table logging, the text gets split up into several parts when longer than 4000 bytes.
• when using FATAL, tracing information gets logged also.
• Logging to database table is done asynchronously to save time with the execution of the driving session.
• Table logs can be outputted to DBMS_OUTPUT later

Project Members:

• Thiemo Kellner (admin)