assert_fatal

  public  assert_fatal(pi_assertion BOOLEAN, 
                       pi_application pst_application_name, 
                       pi_error_name pst_error_name, 
                       pi_error_arguments pt_error_arguments)

Checks the Assertion to TRUE and raises a named Exception to the specified Application and logs it to the specified Application if the Assertion fails with the programmable Log-Level FATAL.

If the Assertion fails then the Exception to the given Error Name will be raised.

The List of dynamic Content will be used to replace the Placeholder within the Exception Message with the real Values during the Runtime.

Example:

    ...
    -- Message for Exception CALC_STEP_WRONG_VALUE:
    -- Assertion failed Step %1: %2
    PKG_LEHS.assert (
      v_variable IS NOT NULL
     ,'Log Application'
     ,'CALC_STEP_WRONG_VALUE'
     ,'some Topic'
     ,PKG_LEHS.pt_error_arguments (
        TO_CHAR(1)
       ,'v_variable IS NULL'
      )
    )
 

Parameters:

pi_assertion - Assertion to be TRUE

pi_application - Name of the Application the named Exception applies to

pi_error_name - Name of the named Exception

pi_error_arguments - List of the dynamic Content

Throws:

ORA-20??? - User defined Exception as deposited to the named Exception

assert_fatal

  public  assert_fatal(pi_assertion BOOLEAN, 
                       pi_application pst_application_name, 
                       pi_topic VARCHAR2, 
                       pi_error_name pst_error_name, 
                       pi_error_arguments pt_error_arguments)

Checks the Assertion to TRUE and raises a named Exception to the specified Application and logs it to the specified Application if the Assertion fails with the programmable Log-Level FATAL.

If the Assertion fails then the Exception to the given Error Name will be raised.

The Exception Message will be applied to the given Log-Topic.
The List of dynamic Content will be used to replace the Placeholder within the Exception Message with the real Values during the Runtime.

Example:

    ...
    -- Message for Exception CALC_STEP_WRONG_VALUE:
    -- Assertion failed Step %1: %2
    PKG_LEHS.assert (
      v_variable IS NOT NULL
     ,'Log Application'
     ,'some Topic'
     ,'CALC_STEP_WRONG_VALUE'
     ,PKG_LEHS.pt_error_arguments (
        TO_CHAR(1)
       ,'v_variable IS NULL'
      )
    )
 

Parameters:

pi_assertion - Assertion to be TRUE

pi_application - Name of the Application the named Exception applies to

pi_topic - Log-Topic the Exception Message applies to at the Log

pi_error_name - Name of the named Exception

pi_error_arguments - List of the dynamic Content

Throws:

ORA-20??? - User defined Exception as deposited to the named Exception

assert_error

  public  assert_error(pi_assertion BOOLEAN, 
                       pi_application pst_application_name, 
                       pi_error_name pst_error_name, 
                       pi_error_arguments pt_error_arguments)

Checks the Assertion to TRUE and raises a named Exception to the specified Application and logs it to the specified Application if the Assertion fails with the programmable Log-Level ERROR.

If the Assertion fails then the Exception to the given Error Name will be raised.

The List of dynamic Content will be used to replace the Placeholder within the Exception Message with the real Values during the Runtime.

Example:

    ...
    -- Message for Exception CALC_STEP_WRONG_VALUE:
    -- Assertion failed Step %1: %2
    PKG_LEHS.assert (
      v_variable IS NOT NULL
     ,'Log Application'
     ,'CALC_STEP_WRONG_VALUE'
     ,'some Topic'
     ,PKG_LEHS.pt_error_arguments (
        TO_CHAR(1)
       ,'v_variable IS NULL'
      )
    )
 

Parameters:

pi_assertion - Assertion to be TRUE

pi_application - Name of the Application the named Exception applies to

pi_error_name - Name of the named Exception

pi_error_arguments - List of the dynamic Content

Throws:

ORA-20??? - User defined Exception as deposited to the named Exception

assert_error

  public  assert_error(pi_assertion BOOLEAN, 
                       pi_application pst_application_name, 
                       pi_topic VARCHAR2, 
                       pi_error_name pst_error_name, 
                       pi_error_arguments pt_error_arguments)

Checks the Assertion to TRUE and raises a named Exception to the specified Application and logs it to the specified Application if the Assertion fails with the programmable Log-Level ERROR.

If the Assertion fails then the Exception to the given Error Name will be raised.

The Exception Message will be applied to the given Log-Topic.
The List of dynamic Content will be used to replace the Placeholder within the Exception Message with the real Values during the Runtime.

Example:

    ...
    -- Message for Exception CALC_STEP_WRONG_VALUE:
    -- Assertion failed Step %1: %2
    PKG_LEHS.assert (
      v_variable IS NOT NULL
     ,'Log Application'
     ,'some Topic'
     ,'CALC_STEP_WRONG_VALUE'
     ,PKG_LEHS.pt_error_arguments (
        TO_CHAR(1)
       ,'v_variable IS NULL'
      )
    )
 

Parameters:

pi_assertion - Assertion to be TRUE

pi_application - Name of the Application the named Exception applies to

pi_topic - Log-Topic the Exception Message applies to at the Log

pi_error_name - Name of the named Exception

pi_error_arguments - List of the dynamic Content

Throws:

ORA-20??? - User defined Exception as deposited to the named Exception

assert_warn

  public  assert_warn(pi_assertion BOOLEAN, 
                      pi_application pst_application_name, 
                      pi_error_name pst_error_name, 
                      pi_error_arguments pt_error_arguments)

Checks the Assertion to TRUE and raises a named Exception to the specified Application and logs it to the specified Application if the Assertion fails with the programmable Log-Level WARN.

If the Assertion fails then the Exception to the given Error Name will be raised.

The List of dynamic Content will be used to replace the Placeholder within the Exception Message with the real Values during the Runtime.

Example:

    ...
    -- Message for Exception CALC_STEP_WRONG_VALUE:
    -- Assertion failed Step %1: %2
    PKG_LEHS.assert (
      v_variable IS NOT NULL
     ,'Log Application'
     ,'CALC_STEP_WRONG_VALUE'
     ,'some Topic'
     ,PKG_LEHS.pt_error_arguments (
        TO_CHAR(1)
       ,'v_variable IS NULL'
      )
    )
 

Parameters:

pi_assertion - Assertion to be TRUE

pi_application - Name of the Application the named Exception applies to

pi_error_name - Name of the named Exception

pi_error_arguments - List of the dynamic Content

Throws:

ORA-20??? - User defined Exception as deposited to the named Exception

assert_warn

  public  assert_warn(pi_assertion BOOLEAN, 
                      pi_application pst_application_name, 
                      pi_topic VARCHAR2, 
                      pi_error_name pst_error_name, 
                      pi_error_arguments pt_error_arguments)

Checks the Assertion to TRUE and raises a named Exception to the specified Application and logs it to the specified Application if the Assertion fails with the programmable Log-Level WARN.

If the Assertion fails then the Exception to the given Error Name will be raised.

The Exception Message will be applied to the given Log-Topic.
The List of dynamic Content will be used to replace the Placeholder within the Exception Message with the real Values during the Runtime.

Example:

    ...
    -- Message for Exception CALC_STEP_WRONG_VALUE:
    -- Assertion failed Step %1: %2
    PKG_LEHS.assert (
      v_variable IS NOT NULL
     ,'Log Application'
     ,'some Topic'
     ,'CALC_STEP_WRONG_VALUE'
     ,PKG_LEHS.pt_error_arguments (
        TO_CHAR(1)
       ,'v_variable IS NULL'
      )
    )
 

Parameters:

pi_assertion - Assertion to be TRUE

pi_application - Name of the Application the named Exception applies to

pi_topic - Log-Topic the Exception Message applies to at the Log

pi_error_name - Name of the named Exception

pi_error_arguments - List of the dynamic Content

Throws:

ORA-20??? - User defined Exception as deposited to the named Exception

assert_info

  public  assert_info(pi_assertion BOOLEAN, 
                      pi_application pst_application_name, 
                      pi_error_name pst_error_name, 
                      pi_error_arguments pt_error_arguments)

Checks the Assertion to TRUE and raises a named Exception to the specified Application and logs it to the specified Application if the Assertion fails with the programmable Log-Level INFO.

If the Assertion fails then the Exception to the given Error Name will be raised.

The List of dynamic Content will be used to replace the Placeholder within the Exception Message with the real Values during the Runtime.

Example:

    ...
    -- Message for Exception CALC_STEP_WRONG_VALUE:
    -- Assertion failed Step %1: %2
    PKG_LEHS.assert (
      v_variable IS NOT NULL
     ,'Log Application'
     ,'CALC_STEP_WRONG_VALUE'
     ,'some Topic'
     ,PKG_LEHS.pt_error_arguments (
        TO_CHAR(1)
       ,'v_variable IS NULL'
      )
    )
 

Parameters:

pi_assertion - Assertion to be TRUE

pi_application - Name of the Application the named Exception applies to

pi_error_name - Name of the named Exception

pi_error_arguments - List of the dynamic Content

Throws:

ORA-20??? - User defined Exception as deposited to the named Exception

assert_info

  public  assert_info(pi_assertion BOOLEAN, 
                      pi_application pst_application_name, 
                      pi_topic VARCHAR2, 
                      pi_error_name pst_error_name, 
                      pi_error_arguments pt_error_arguments)

Checks the Assertion to TRUE and raises a named Exception to the specified Application and logs it to the specified Application if the Assertion fails with the programmable Log-Level INFO.

If the Assertion fails then the Exception to the given Error Name will be raised.

The Exception Message will be applied to the given Log-Topic.
The List of dynamic Content will be used to replace the Placeholder within the Exception Message with the real Values during the Runtime.

Example:

    ...
    -- Message for Exception CALC_STEP_WRONG_VALUE:
    -- Assertion failed Step %1: %2
    PKG_LEHS.assert (
      v_variable IS NOT NULL
     ,'Log Application'
     ,'some Topic'
     ,'CALC_STEP_WRONG_VALUE'
     ,PKG_LEHS.pt_error_arguments (
        TO_CHAR(1)
       ,'v_variable IS NULL'
      )
    )
 

Parameters:

pi_assertion - Assertion to be TRUE

pi_application - Name of the Application the named Exception applies to

pi_topic - Log-Topic the Exception Message applies to at the Log

pi_error_name - Name of the named Exception

pi_error_arguments - List of the dynamic Content

Throws:

ORA-20??? - User defined Exception as deposited to the named Exception

assert_debug

  public  assert_debug(pi_assertion BOOLEAN, 
                       pi_application pst_application_name, 
                       pi_error_name pst_error_name, 
                       pi_error_arguments pt_error_arguments)

Checks the Assertion to TRUE and raises a named Exception to the specified Application and logs it to the specified Application if the Assertion fails with the programmable Log-Level DEBUG.

If the Assertion fails then the Exception to the given Error Name will be raised.

The List of dynamic Content will be used to replace the Placeholder within the Exception Message with the real Values during the Runtime.

Example:

    ...
    -- Message for Exception CALC_STEP_WRONG_VALUE:
    -- Assertion failed Step %1: %2
    PKG_LEHS.assert (
      v_variable IS NOT NULL
     ,'Log Application'
     ,'CALC_STEP_WRONG_VALUE'
     ,'some Topic'
     ,PKG_LEHS.pt_error_arguments (
        TO_CHAR(1)
       ,'v_variable IS NULL'
      )
    )
 

Parameters:

pi_assertion - Assertion to be TRUE

pi_application - Name of the Application the named Exception applies to

pi_error_name - Name of the named Exception

pi_error_arguments - List of the dynamic Content

Throws:

ORA-20??? - User defined Exception as deposited to the named Exception

assert_debug

  public  assert_debug(pi_assertion BOOLEAN, 
                       pi_application pst_application_name, 
                       pi_topic VARCHAR2, 
                       pi_error_name pst_error_name, 
                       pi_error_arguments pt_error_arguments)

Checks the Assertion to TRUE and raises a named Exception to the specified Application and logs it to the specified Application if the Assertion fails with the programmable Log-Level DEBUG.

If the Assertion fails then the Exception to the given Error Name will be raised.

The Exception Message will be applied to the given Log-Topic.
The List of dynamic Content will be used to replace the Placeholder within the Exception Message with the real Values during the Runtime.

Example:

    ...
    -- Message for Exception CALC_STEP_WRONG_VALUE:
    -- Assertion failed Step %1: %2
    PKG_LEHS.assert (
      v_variable IS NOT NULL
     ,'Log Application'
     ,'some Topic'
     ,'CALC_STEP_WRONG_VALUE'
     ,PKG_LEHS.pt_error_arguments (
        TO_CHAR(1)
       ,'v_variable IS NULL'
      )
    )
 

Parameters:

pi_assertion - Assertion to be TRUE

pi_application - Name of the Application the named Exception applies to

pi_topic - Log-Topic the Exception Message applies to at the Log

pi_error_name - Name of the named Exception

pi_error_arguments - List of the dynamic Content

Throws:

ORA-20??? - User defined Exception as deposited to the named Exception

assert_trace

  public  assert_trace(pi_assertion BOOLEAN, 
                       pi_application pst_application_name, 
                       pi_error_name pst_error_name, 
                       pi_error_arguments pt_error_arguments)

Checks the Assertion to TRUE and raises a named Exception to the specified Application and logs it to the specified Application if the Assertion fails with the programmable Log-Level TRACE.

If the Assertion fails then the Exception to the given Error Name will be raised.

The List of dynamic Content will be used to replace the Placeholder within the Exception Message with the real Values during the Runtime.

Example:

    ...
    -- Message for Exception CALC_STEP_WRONG_VALUE:
    -- Assertion failed Step %1: %2
    PKG_LEHS.assert (
      v_variable IS NOT NULL
     ,'Log Application'
     ,'CALC_STEP_WRONG_VALUE'
     ,'some Topic'
     ,PKG_LEHS.pt_error_arguments (
        TO_CHAR(1)
       ,'v_variable IS NULL'
      )
    )
 

Parameters:

pi_assertion - Assertion to be TRUE

pi_application - Name of the Application the named Exception applies to

pi_error_name - Name of the named Exception

pi_error_arguments - List of the dynamic Content

Throws:

ORA-20??? - User defined Exception as deposited to the named Exception

assert_trace

  public  assert_trace(pi_assertion BOOLEAN, 
                       pi_application pst_application_name, 
                       pi_topic VARCHAR2, 
                       pi_error_name pst_error_name, 
                       pi_error_arguments pt_error_arguments)

Checks the Assertion to TRUE and raises a named Exception to the specified Application and logs it to the specified Application if the Assertion fails with the programmable Log-Level TRACE.

If the Assertion fails then the Exception to the given Error Name will be raised.

The Exception Message will be applied to the given Log-Topic.
The List of dynamic Content will be used to replace the Placeholder within the Exception Message with the real Values during the Runtime.

Example:

    ...
    -- Message for Exception CALC_STEP_WRONG_VALUE:
    -- Assertion failed Step %1: %2
    PKG_LEHS.assert (
      v_variable IS NOT NULL
     ,'Log Application'
     ,'some Topic'
     ,'CALC_STEP_WRONG_VALUE'
     ,PKG_LEHS.pt_error_arguments (
        TO_CHAR(1)
       ,'v_variable IS NULL'
      )
    )
 

Parameters:

pi_assertion - Assertion to be TRUE

pi_application - Name of the Application the named Exception applies to

pi_topic - Log-Topic the Exception Message applies to at the Log

pi_error_name - Name of the named Exception

pi_error_arguments - List of the dynamic Content

Throws:

ORA-20??? - User defined Exception as deposited to the named Exception

log_exception

  public  log_exception(pi_application pst_application_name, 
                        pi_topic VARCHAR2 DEFAULT NULL, 
                        pi_log_app_exception BOOLEAN DEFAULT FALSE, 
                        pi_log_level VARCHAR2 DEFAULT NULL)

Logs an unhandled, unnamed Exception to the specified Application.

The Exception Message will be assigned to the given Log-Topic.
This Procedure should be called at the End of every Procedure of the Application. Example

   CREATE OR REPLACE PROCEDURE xyz IS
     ...
   BEGIN
     ..
   EXCEPTION
     WHEN OTHERS THEN
       PKG_LEHS.log_exception ('App1', 'Topic1');
       RAISE;
   END;
 

Parameters:

pi_application - Application the Exception Message should be logged to

pi_topic - Log-Topic the logged Exception Message should be assigned to

pi_log_app_exception - Should a user defined named Exception of the Application be logged? (Default: FALSE)
If NULL then the Default will be taken.

pi_log_level - optional Log-Level for the Exception Log. If omitted or the Value is NULL the Exception Log-Level of the Application will be taken

log_exception_fatal

  public  log_exception_fatal(pi_application pst_application_name, 
                              pi_topic VARCHAR2 DEFAULT NULL, 
                              pi_log_app_exception BOOLEAN DEFAULT FALSE)

Logs an unhandled, unnamed Exception to the specified Application and logs it with the programmable Log-Level FATAL.

The Exception Message will be assigned to the given Log-Topic.
This Procedure should be called at the End of every Procedure of the Application. Example

   CREATE OR REPLACE PROCEDURE xyz IS
     ...
   BEGIN
     ..
   EXCEPTION
     WHEN OTHERS THEN
       PKG_LEHS.log_exception ('App1', 'Topic1');
       RAISE;
   END;
 

Parameters:

pi_application - Application the Exception Message should be logged to

pi_topic - Log-Topic the logged Exception Message should be assigned to

pi_log_app_exception - Should a user defined named Exception of the Application be logged? (Default: FALSE)
If NULL then the Default will be taken.

log_exception_error

  public  log_exception_error(pi_application pst_application_name, 
                              pi_topic VARCHAR2 DEFAULT NULL, 
                              pi_log_app_exception BOOLEAN DEFAULT FALSE)

Logs an unhandled, unnamed Exception to the specified Application and logs it with the programmable Log-Level ERROR.

The Exception Message will be assigned to the given Log-Topic.
This Procedure should be called at the End of every Procedure of the Application. Example

   CREATE OR REPLACE PROCEDURE xyz IS
     ...
   BEGIN
     ..
   EXCEPTION
     WHEN OTHERS THEN
       PKG_LEHS.log_exception ('App1', 'Topic1');
       RAISE;
   END;
 

Parameters:

pi_application - Application the Exception Message should be logged to

pi_topic - Log-Topic the logged Exception Message should be assigned to

pi_log_app_exception - Should a user defined named Exception of the Application be logged? (Default: FALSE)
If NULL then the Default will be taken.

log_exception_warn

  public  log_exception_warn(pi_application pst_application_name, 
                             pi_topic VARCHAR2 DEFAULT NULL, 
                             pi_log_app_exception BOOLEAN DEFAULT FALSE)

Logs an unhandled, unnamed Exception to the specified Application and logs it with the programmable Log-Level WARN.

The Exception Message will be assigned to the given Log-Topic.
This Procedure should be called at the End of every Procedure of the Application. Example

   CREATE OR REPLACE PROCEDURE xyz IS
     ...
   BEGIN
     ..
   EXCEPTION
     WHEN OTHERS THEN
       PKG_LEHS.log_exception ('App1', 'Topic1');
       RAISE;
   END;
 

Parameters:

pi_application - Application the Exception Message should be logged to

pi_topic - Log-Topic the logged Exception Message should be assigned to

pi_log_app_exception - Should a user defined named Exception of the Application be logged? (Default: FALSE)
If NULL then the Default will be taken.

log_exception_info

  public  log_exception_info(pi_application pst_application_name, 
                             pi_topic VARCHAR2 DEFAULT NULL, 
                             pi_log_app_exception BOOLEAN DEFAULT FALSE)

Logs an unhandled, unnamed Exception to the specified Application and logs it with the programmable Log-Level INFO.

The Exception Message will be assigned to the given Log-Topic.
This Procedure should be called at the End of every Procedure of the Application. Example

   CREATE OR REPLACE PROCEDURE xyz IS
     ...
   BEGIN
     ..
   EXCEPTION
     WHEN OTHERS THEN
       PKG_LEHS.log_exception ('App1', 'Topic1');
       RAISE;
   END;
 

Parameters:

pi_application - Application the Exception Message should be logged to

pi_topic - Log-Topic the logged Exception Message should be assigned to

pi_log_app_exception - Should a user defined named Exception of the Application be logged? (Default: FALSE)
If NULL then the Default will be taken.

log_exception_debug

  public  log_exception_debug(pi_application pst_application_name, 
                              pi_topic VARCHAR2 DEFAULT NULL, 
                              pi_log_app_exception BOOLEAN DEFAULT FALSE)

Logs an unhandled, unnamed Exception to the specified Application and logs it with the programmable Log-Level DEBUG.

The Exception Message will be assigned to the given Log-Topic.
This Procedure should be called at the End of every Procedure of the Application. Example

   CREATE OR REPLACE PROCEDURE xyz IS
     ...
   BEGIN
     ..
   EXCEPTION
     WHEN OTHERS THEN
       PKG_LEHS.log_exception ('App1', 'Topic1');
       RAISE;
   END;
 

Parameters:

pi_application - Application the Exception Message should be logged to

pi_topic - Log-Topic the logged Exception Message should be assigned to

pi_log_app_exception - Should a user defined named Exception of the Application be logged? (Default: FALSE)
If NULL then the Default will be taken.

log_exception_trace

  public  log_exception_trace(pi_application pst_application_name, 
                              pi_topic VARCHAR2 DEFAULT NULL, 
                              pi_log_app_exception BOOLEAN DEFAULT FALSE)

Logs an unhandled, unnamed Exception to the specified Application and logs it with the programmable Log-Level TRACE.

The Exception Message will be assigned to the given Log-Topic.
This Procedure should be called at the End of every Procedure of the Application. Example

   CREATE OR REPLACE PROCEDURE xyz IS
     ...
   BEGIN
     ..
   EXCEPTION
     WHEN OTHERS THEN
       PKG_LEHS.log_exception ('App1', 'Topic1');
       RAISE;
   END;
 

Parameters:

pi_application - Application the Exception Message should be logged to

pi_topic - Log-Topic the logged Exception Message should be assigned to

pi_log_app_exception - Should a user defined named Exception of the Application be logged? (Default: FALSE)
If NULL then the Default will be taken.

is_named_exception

  public BOOLEAN is_named_exception(pi_application pst_application_name, 
                                    pi_error_code BINARY_INTEGER)

Does the given Error Code correspond to any named Exception of the specified Application?

Parameters:

pi_application - Log-Application the Error Code should be checked against

pi_error_code - Error Code as got by the BuiltIn-Function SQLCODE

Returns:

• TRUE ... The Error-Code is assigned to a registered named Exception of the specified Application
• FALSE ... The Error-Code is not assigned to any registered named Exception of the specified Application

is_named_exception

  public BOOLEAN is_named_exception(pi_application pst_application_name, 
                                    pi_error_code BINARY_INTEGER, 
                                    pi_error_name pst_error_name)

Does the given Error Code correspond to the given named Exception of the specified Application?

Parameters:

pi_application - Log-Application the Error Code should be checked against the named Exception

pi_error_code - Error Code as got by the BuiltIn-Function SQLCODE

pi_error_name - named Exception of the specified Application to be checked

Returns:

• TRUE ... The Error-Code is assigned to the given named Exception of the specified Application
• FALSE ... The Error-Code is not assigned to the given named Exception of the specified Application

add_transaction_key

  public  add_transaction_key(pi_application pst_application_name, 
                              pi_transaction_id pst_log_transaction, 
                              pi_key VARCHAR2, 
                              pi_value CLOB)

Adds an alphanumeric Key to the given Log-Transaction.

Additional Log-Transaction Keys can be found by the View USER_LEHS_TRANSACTIONS.

Parameters:

pi_application - Log-Application the Keyword should be added

pi_transaction_id - Transaction-ID the Keyword should be added

pi_key - Name of the Key

pi_value - Value of the Key

Throws:

ORA-20001 - [MISSING PARAMETER] missing mandatory Parameter

ORA-20008 - [LOG TRANSACTION NOT EXISTS] The given Log-Transaction doesn't exist to the specified Log-Application

ORA-20008 - [LOG TRANSACTION NOT OPEN] The specified Log-Transaction is no longer in State OPEN for the specified Log-Application

add_transaction_key

  public  add_transaction_key(pi_application pst_application_name, 
                              pi_transaction_id pst_log_transaction, 
                              pi_key VARCHAR2, 
                              pi_value VARCHAR2)

Adds an alphanumeric Key to the given Log-Transaction.

Additional Log-Transaction Keys can be found by the View USER_LEHS_TRANSACTIONS.

Parameters:

pi_application - Log-Application the Keyword should be added

pi_transaction_id - Transaction-ID the Keyword should be added

pi_key - Name of the Key

pi_value - Value of the Key

Throws:

ORA-20001 - [MISSING PARAMETER] missing mandatory Parameter

ORA-20008 - [LOG TRANSACTION NOT EXISTS] The given Log-Transaction doesn't exist to the specified Log-Application

ORA-20008 - [LOG TRANSACTION NOT OPEN] The specified Log-Transaction is no longer in State OPEN for the specified Log-Application

add_transaction_key

  public  add_transaction_key(pi_application pst_application_name, 
                              pi_transaction_id pst_log_transaction, 
                              pi_key VARCHAR2, 
                              pi_value NUMBER)

Adds a numeric Key to the given Log-Transaction.

Additional Log-Transaction Keys can be found by the View USER_LEHS_TRANSACTIONS.

Within the View USER_LEHS_TRANSACTIONS the Value will be formatted automatically with the builtin Function TO_CHAR, which takes advantage of the actual Session-Parameter NLS_NUMERIC_CHARACTERS.

Parameters:

pi_application - Log-Application the Keyword should be added

pi_transaction_id - Transaction-ID the Keyword should be added

pi_key - Name of the Key

pi_value - Value of the Key

Throws:

ORA-20001 - [MISSING PARAMETER] missing mandatory Parameter

ORA-20008 - [LOG TRANSACTION NOT EXISTS] The given Log-Transaction doesn't exist to the specified Log-Application

ORA-20008 - [LOG TRANSACTION NOT OPEN] The specified Log-Transaction is no longer in State OPEN for the specified Log-Application

add_transaction_key

  public  add_transaction_key(pi_application pst_application_name, 
                              pi_transaction_id pst_log_transaction, 
                              pi_key VARCHAR2, 
                              pi_value DATE)

Adds a Date Key to the given Log-Transaction.

Additional Log-Transaction Keys can be found by the View USER_LEHS_TRANSACTIONS.

Within the View USER_LEHS_TRANSACTIONS the Value will be formatted automatically with the builtin Function TO_CHAR, which takes advantage of the actual Session-Parameter NLS_DATE_FORMAT.

Parameters:

pi_application - Log-Application the Keyword should be added

pi_transaction_id - Transaction-ID the Keyword should be added

pi_key - Name of the Key

pi_value - Value of the Key

Throws:

ORA-20001 - [MISSING PARAMETER] missing mandatory Parameter

ORA-20008 - [LOG TRANSACTION NOT EXISTS] The given Log-Transaction doesn't exist to the specified Log-Application

ORA-20008 - [LOG TRANSACTION NOT OPEN] The specified Log-Transaction is no longer in State OPEN for the specified Log-Application

add_transaction_key

  public  add_transaction_key(pi_application pst_application_name, 
                              pi_transaction_id pst_log_transaction, 
                              pi_key VARCHAR2, 
                              pi_value DSINTERVAL_UNCONSTRAINED)

Adds a Day to Second Interval Key to the given Log-Transaction.

Additional Log-Transaction Keys can be found by the View USER_LEHS_TRANSACTIONS.

Within the View USER_LEHS_TRANSACTIONS the Value will be formatted automatically with the builtin Function TO_CHAR, but unfortunately there is no separate Session-Parameter where you can configure the Format of the Character Conversion of this Parameter.

Parameters:

pi_application - Log-Application the Keyword should be added

pi_transaction_id - Transaction-ID the Keyword should be added

pi_key - Name of the Key

pi_value - Value of the Key

Throws:

ORA-20001 - [MISSING PARAMETER] missing mandatory Parameter

ORA-20008 - [LOG TRANSACTION NOT EXISTS] The given Log-Transaction doesn't exist to the specified Log-Application

ORA-20008 - [LOG TRANSACTION NOT OPEN] The specified Log-Transaction is no longer in State OPEN for the specified Log-Application

add_transaction_key

  public  add_transaction_key(pi_application pst_application_name, 
                              pi_transaction_id pst_log_transaction, 
                              pi_key VARCHAR2, 
                              pi_value YMINTERVAL_UNCONSTRAINED)

Adds a Year to Month Interval Key to the given Log-Transaction.

Additional Log-Transaction Keys can be found by the View USER_LEHS_TRANSACTIONS.

Within the View USER_LEHS_TRANSACTIONS the Value will be formatted automatically with the builtin Function TO_CHAR, but unfortunately there is no separate Session-Parameter where you can configure the Format of the Character Conversion of this Parameter.

Parameters:

pi_application - Log-Application the Keyword should be added

pi_transaction_id - Transaction-ID the Keyword should be added

pi_key - Name of the Key

pi_value - Value of the Key

Throws:

ORA-20001 - [MISSING PARAMETER] missing mandatory Parameter

ORA-20008 - [LOG TRANSACTION NOT EXISTS] The given Log-Transaction doesn't exist to the specified Log-Application

ORA-20008 - [LOG TRANSACTION NOT OPEN] The specified Log-Transaction is no longer in State OPEN for the specified Log-Application

add_transaction_key

  public  add_transaction_key(pi_application pst_application_name, 
                              pi_transaction_id pst_log_transaction, 
                              pi_key VARCHAR2, 
                              pi_value TIMESTAMP_UNCONSTRAINED)

Adds a Timestamp Key to the given Log-Transaction.

Additional Log-Transaction Keys can be found by the View USER_LEHS_TRANSACTIONS.

Within the View USER_LEHS_TRANSACTIONS the Date-Value will be formatted automatically with the builtin Function TO_CHAR, which takes advantage of the actual Session-Parameter NLS_TIMESTAMP_FORMAT.

Parameters:

pi_application - Log-Application the Keyword should be added

pi_transaction_id - Transaction-ID the Keyword should be added

pi_key - Name of the Key

pi_value - Value of the Key

Throws:

ORA-20001 - [MISSING PARAMETER] missing mandatory Parameter

ORA-20008 - [LOG TRANSACTION NOT EXISTS] The given Log-Transaction doesn't exist to the specified Log-Application

ORA-20008 - [LOG TRANSACTION NOT OPEN] The specified Log-Transaction is no longer in State OPEN for the specified Log-Application

add_topic

  public  add_topic(pi_application pst_application_name, 
                    pi_topic VARCHAR2, 
                    pi_topic_parent VARCHAR2, 
                    pi_topic_predecessor VARCHAR2)

Adds a new Log-Topic to the specified Application.

If the Topic already exists to this Application it would only be moved under the hierarchical Level of pi_topic_parent after the Topic pi_topic_predecessor

Parameters:

pi_application - Log-Application the Log-Topic should be created to

pi_topic - Name of the new Topic

pi_topic_parent - Name of the parent Topic the new Topic should be arranged below

pi_topic_predecessor - Name of the predecessor Topic the new Topic should be arranged after
If the predecessing Topic should have an other parent Topic than the new Topic the Parent Topic of the predecessing Topic would be taken instead.

add_topic

  public  add_topic(pi_application pst_application_name, 
                    pi_topic VARCHAR2, 
                    pi_topic_parent VARCHAR2, 
                    pi_position BINARY_INTEGER DEFAULT NULL)

Adds a new Log-Topic to the specified Application.

If the Topic already exists to this Application it would only be moved to the new Position specified by pi_position under the hierarchical Level as pi_topic_parent

Parameters:

pi_application - Log-Application the Log-Topic should be created to

pi_topic - Name of the new Topic

pi_topic_parent - Name of the parent Topic the new Topic should be arranged below

pi_position - Position of the new Topic within the horizontal Order (0,1 = first Position, NULL = last Position)

add_message

  public  add_message(pi_application pst_application_name, 
                      pi_error_name pst_error_name, 
                      pi_error_code BINARY_INTEGER, 
                      pi_message CLOB, 
                      pi_show_error_stack BOOLEAN DEFAULT TRUE, 
                      pi_nls_language VARCHAR2 DEFAULT pc_default_language)

Add a new or change an existing Exception Message for the specified Application.

Parameters:

pi_application - Application the Exception Message should be added/changed

pi_error_name - Error Name of the Exception Message (named Exception) The Error Name will always be uppercased automatically.

pi_error_code - Error Code the Exception Message will be assigned to. (Should between ORA-20999 and ORA-20000)

pi_message - parametrized Exception Message (Placeholder for Parameters are %1 to %9).

pi_show_error_stack - When the named Exception will be raised should any existing Error-Stack also be raised with this named Exception (look at BuiltIn-Function RAISE_APPLICATION_ERROR, 3rd Parameter
(Default: TRUE)

pi_nls_language - NLS-Language of the Exception Message. Default or NULL: AMERICAN

get_last_exception_name

  public PKG_LEHS.pst_error_name get_last_exception_name(pi_application PKG_LEHS.pst_application_name)

resync

  public  resync()

Resynchronize the internal Buffer Cache (useful, when the Data of the Log-System has been changed.

resync_on_modification

  public  resync_on_modification()

Resynchronize the internal Buffer Cache when the Log-Application has been modified by PKG_LEHS_SYSTEM.

If no change has been made then the buffer will not be refreshed

get_version

  public VARCHAR2 get_version()

Returns the Version of LEHS

Returns:

Version of LEHS