archiving log files for no reason

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

jchen1011 - 24 Oct 2007 16:34 GMT

I have a reporting database running DB2 LUW 8.2 on a RedHat Linux. It is
configured to archive log files automatically. I notice that although no
activities on the database, it keeps archive the log files frequently. Each
archived file has the same size, which is about 12288 bytes. The reporting db
is a restore from a production db backup. Both have the same settings.
However, the production db has no such a behavior. I am wondering what ghost
triggers the archiving? Can any body shed some light on the issue I am facing?

Thanks

Reply to this Message

shenanwei@gmail.com - 24 Oct 2007 18:27 GMT

> I have a reporting database running DB2 LUW 8.2 on a RedHat Linux. It is
> configured to archive log files automatically. I notice that although no
[quoted text clipped - 5 lines]
>
> Thanks

That size is all about head of the log, everytime the database is
deactivated, log archive will be triggered automatically.

Reply to this Message

jchen1011 - 24 Oct 2007 22:20 GMT

Thank for your response.
Based on what you said, does it mean that there is a database activating
activity, or some usage of the database?

>> I have a reporting database running DB2 LUW 8.2 on a RedHat Linux. It is
>> configured to archive log files automatically. I notice that although no
[quoted text clipped - 4 lines]
>That size is all about head of the log, everytime the database is
>deactivated, log archive will be triggered automatically.

Reply to this Message

Ian - 25 Oct 2007 05:30 GMT

> Thank for your response.
> Based on what you said, does it mean that there is a database activating
> activity, or some usage of the database?

By default, the first connection to a database activates it, and the
database will deactivate after the last application disconnects.
If you want to avoid this, you can activate the database explicity,
using the 'activate database' command.

This will stop the behavior that you're seeing.

Reply to this Message

jchen1011 - 25 Oct 2007 19:31 GMT

Yes, using those commands has solved my problem.
Many Thanks.

>> Thank for your response.
>> Based on what you said, does it mean that there is a database activating
[quoted text clipped - 6 lines]
>
>This will stop the behavior that you're seeing.

Reply to this Message