get_log_info procedure

Related topics

Contained in package wwlog_api_admin.

Call this procedure to determine which of the two Oracle Portal log tables is being used:

A value of 1 represents wwlog_activity_log1$.

A value of 2 represents wwlog_activity_log2$.

The two values returned are passed into two number variables passed as parameters. If the two values are not the same, then the log indicated by p_new_log must be purged before a new log record is written to it.

procedure get_log_info

(

p_current_log in out number,

p_new_log out number

);

Version: Oracle Portal 3.0.6.6.5 or later

Parameters:

p_current_log

Returns a value that indicates the transaction log that is currently being written to.

Datatype: in out number

p_new_log

Returns a value that indicates the transaction log that should be used next.

Datatype: out number

Returns:

This procedure returns values that indicate which transaction log is currently in use, which should be used next, and if the log that should be used next must be purged before it can receive data.

Exceptions:

This procedure raises no user-defined exceptions.

Example:

wwlog_api_admin.get_log_info

(

p_current_log => l_current_log,

p_new_log => l_new_log

);

Version: Oracle Portal 3.0.6.6.5 or later
Parameters:
p_current_log	Returns a value that indicates the transaction log that is currently being written to. Datatype: in out number
p_new_log	Returns a value that indicates the transaction log that should be used next. Datatype: out number
Returns: This procedure returns values that indicate which transaction log is currently in use, which should be used next, and if the log that should be used next must be purged before it can receive data. Exceptions: This procedure raises no user-defined exceptions. Example: wwlog_api_admin.get_log_info ( p_current_log => l_current_log, p_new_log => l_new_log );

Related topics
Event logging API package	PDK PL/SQL API Reference - Home