Logging

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

shsandeep - 24 Mar 2006 01:15 GMT

Q 1.
How do I come to know what type of logging has been enabled for a
particular database (circular/archival,etc.) ?

Q 2.
DataStage is loading data into the tables. A parameter has been set into
it to commit every 1000 rows. How to verify whether the commit is
happening every 1000 rows on the database side?

Thanks.

Cheers,
San.

Reply to this Message

Ian - 24 Mar 2006 01:42 GMT

> Q 1.
> How do I come to know what type of logging has been enabled for a
> particular database (circular/archival,etc.) ?

Look at the LOGRETAIN database config parameter.

> Q 2.
> DataStage is loading data into the tables. A parameter has been set into
> it to commit every 1000 rows. How to verify whether the commit is
> happening every 1000 rows on the database side?

Look at an application snapshot for the datastage process that's writing
data and compare the number of commit statements to rows inserted. The
ratio should be pretty close to 1:1000.

Reply to this Message

Bob [IBM] - 26 Mar 2006 22:42 GMT

>> Q 1.
>> How do I come to know what type of logging has been enabled for a
[quoted text clipped - 10 lines]
> data and compare the number of commit statements to rows inserted. The
> ratio should be pretty close to 1:1000.

If I am not mistaken, archival logging can also be turned on with
USEREXIT = ON and I do not think in that case the log retain is set to
ON. Have no system to check at this time however.

Bob

Reply to this Message

Peter Postlbauer - 27 Mar 2006 08:20 GMT

> If I am not mistaken, archival logging can also be turned on with
> USEREXIT = ON and I do not think in that case the log retain is set to
> ON. Have no system to check at this time however.
>
> Bob

First you have to turn on USEREXIT=ON then you can set LOG RETAIN = ON.
Per default userexit=off and circularlogging = on.
regards, peter

Reply to this Message

Bob [IBM] - 27 Mar 2006 18:07 GMT

>> If I am not mistaken, archival logging can also be turned on with
>> USEREXIT = ON and I do not think in that case the log retain is set to
[quoted text clipped - 7 lines]
>
>

Actually this is not correct -- turning USEREXIT =ON does in fact turn
on LOG RETAIN by default -- the switch does not show LOG RETAIN=RECOVERY
but as long as USEREXIT=ON LOGRETAIN=RECOVERY by default.

This is documented at : *http://tinyurl.com/bslng*

Reply to this Message

Bob [IBM] - 27 Mar 2006 18:09 GMT

>>> If I am not mistaken, archival logging can also be turned on with
>>> USEREXIT = ON and I do not think in that case the log retain is set to
[quoted text clipped - 12 lines]
>
> This is documented at : *http://tinyurl.com/bslng*

Just an addendum as my link not work propery -- search for USEREXIT on
the online documentation and this is documented:

"If this parameter is enabled, log retention logging is performed
_regardless of how the logretain parameter is set_. This parameter also
indicates that a user exit program should be used to archive and
retrieve the log files. Log files are archived when the database manager
closes the log file. They are retrieved when the ROLLFORWARD utility
needs to use them to restore a database."
"

Reply to this Message