archiving log files for no reason

[jchen1011]

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

[shenanwei]

On Oct 24, 11:35 am, "jchen1011" <u38534@uwewrote:

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

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

[jchen1011 via DBMonster.com]

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?

sh*******@gmail.com wrote:

>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.

--
Message posted via http://www.dbmonster.com

[Ian]

jchen1011 via DBMonster.com wrote:

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.

[jchen1011 via DBMonster.com]

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

Ian wrote:

>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.

--
Message posted via DBMonster.com
http://www.dbmonster.com/Uwe/Forums....m-db2/200710/1