PLSQLLOG Configuration

As user PLSQLLOG you can create new log sources, delete or customize present log sources.
A log source can be seen as an identifier for the configuration entry. If no log source is set for the logging session or the set log source does not exist, the default log source is used. The default log source must not be deleted.

Please note All changes are visible to existing sessions using PLSQLLOG only after re-reading the configuration manually by calling
begin
  PLSQLLOG.LOGGER.read_configuration;
end;
/

To create a new log source call the following procedure
begin
  LOGGER_CONFIGURATION_ADM.add_log_source (
    log_source_i => 'NewLogSourceName',
    log_level_i => PLSQLLOG.PLSQLLOG_CONSTANTS.LOGLEVEL_DEBUG,
    log_target_i => PLSQLLOG.PLSQLLOG_CONSTANTS.LOGTARGET_TABLE + PLSQLLOG.PLSQLLOG_CONSTANTS.LOGTARGET_FILE,
    log_target_name_i => 'NewLogTargetName'
  );
end;
/

To Modify a log source call the following procedure
begin
  LOGGER_CONFIGURATION_ADM.update_log_source (
    log_source_i => 'NewLogSourceName',
    log_level_i => PLSQLLOG.PLSQLLOG_CONSTANTS.LOGLEVEL_DEBUG,
    log_target_i => PLSQLLOG.PLSQLLOG_CONSTANTS.LOGTARGET_TABLE + PLSQLLOG.PLSQLLOG_CONSTANTS.LOGTARGET_FILE,
    log_target_name_i => 'ChangedLogTargetName'
  );
end;
/

To Delete a log source call the following procedure
begin
  LOGGER_CONFIGURATION_ADM.delete_log_source (
    log_source_i => 'NewLogSourceName'
  );
end;
/

You might prefere the more convenient procedures:
PROCEDURE LOGGER_CONFIGURATION_ADM.set_debug (log_source_i IN PLSQLLOG_CONSTANTS.T_LOGSOURCE);  
PROCEDURE LOGGER_CONFIGURATION_ADM.set_info (log_source_i IN PLSQLLOG_CONSTANTS.T_LOGSOURCE);  
PROCEDURE LOGGER_CONFIGURATION_ADM.set_warn (log_source_i IN PLSQLLOG_CONSTANTS.T_LOGSOURCE);  
PROCEDURE LOGGER_CONFIGURATION_ADM.set_error (log_source_i IN PLSQLLOG_CONSTANTS.T_LOGSOURCE);  
PROCEDURE LOGGER_CONFIGURATION_ADM.set_fatal (log_source_i IN PLSQLLOG_CONSTANTS.T_LOGSOURCE);  
PROCEDURE LOGGER_CONFIGURATION_ADM.set_nolog (log_source_i IN PLSQLLOG_CONSTANTS.T_LOGSOURCE);  
 
PROCEDURE LOGGER_CONFIGURATION_ADM.set_target_console (log_source_i IN PLSQLLOG_CONSTANTS.T_LOGSOURCE);  
PROCEDURE LOGGER_CONFIGURATION_ADM.set_target_table (log_source_i IN PLSQLLOG_CONSTANTS.T_LOGSOURCE);  
PROCEDURE LOGGER_CONFIGURATION_ADM.set_target_file (log_source_i IN PLSQLLOG_CONSTANTS.T_LOGSOURCE);  
PROCEDURE LOGGER_CONFIGURATION_ADM.set_target_console_table (log_source_i IN PLSQLLOG_CONSTANTS.T_LOGSOURCE);  
PROCEDURE LOGGER_CONFIGURATION_ADM.set_target_console_file (log_source_i IN PLSQLLOG_CONSTANTS.T_LOGSOURCE);  
PROCEDURE LOGGER_CONFIGURATION_ADM.set_target_console_table_file (log_source_i IN PLSQLLOG_CONSTANTS.T_LOGSOURCE);  
PROCEDURE LOGGER_CONFIGURATION_ADM.set_target_table_file (log_source_i IN PLSQLLOG_CONSTANTS.T_LOGSOURCE);  
 
PROCEDURE LOGGER_CONFIGURATION_ADM.set_target_name (
    log_source_i IN PLSQLLOG_CONSTANTS.T_LOGSOURCE,
    target_name_i IN PLSQLLOG_CONSTANTS.T_LOGTARGET_NAME);

The numeric values for the log level are
LOGLEVEL_DEBUG CONSTANT NUMBER := 1;
LOGLEVEL_INFO CONSTANT NUMBER := 2;
LOGLEVEL_WARN CONSTANT NUMBER := 4;
LOGLEVEL_ERROR CONSTANT NUMBER := 8;
LOGLEVEL_FATAL CONSTANT NUMBER := 16;
LOGLEVEL_OFF CONSTANT NUMBER := 32;

The numeric values for the log targets are
LOGTARGET_CONSOLE CONSTANT NUMBER := 1;
LOGTARGET_TABLE CONSTANT NUMBER := 2;
LOGTARGET_FILE CONSTANT NUMBER := 4;
LOGTARGET_ALERT CONSTANT NUMBER := 8;

The default values are
DEFAULT_LOGLEVEL CONSTANT NUMBER := LOGLEVEL_INFO;
DEFAULT_LOGSOURCE CONSTANT T_LOGSOURCE := 'DEFAULT SOURCE';
DEFAULT_LOGTARGET CONSTANT NUMBER := LOGTARGET_TABLE + LOGTARGET_CONSOLE;
DEFAULT_LOGTARGET_NAME CONSTANT T_LOGTARGET_NAME := 'LOG_TABLE';

Last modified by Administrator on 2010/07/30 10:18
GDBUtil
A Java based generic database utility with configurable content. Database browsing, charts, console, etc. Visit...
ERMT
An entity relationship modelling tool. Visit...

This wiki is licensed under a Creative Commons 2.0 license
XWiki Enterprise 2.0.2.24645 - Documentation