Numerous Very Small Log Files

David Franit

Hello,

On a v81 UDB AIX system, LOGFILSZ is set to 4000 (4KB pages) for a
database. LOGPRIMARY and LOGSECONDARY are set to reasonable values.
However, the log files, instead of being 16MB in size, are about
16KB or 17KB in size.

Thus, there are numerous log sizes, the log directory is unresponsive,
etc..

What would cause this type of behaviour? Could it be a SQL
statement, continuously executed by mistake, causing the logs
to switch? It seems to me that the database manager and database
configuration are fine.


Thanks.

Nov 12 '05 #1

Ian

David Franit wrote:

Hello,

On a v81 UDB AIX system, LOGFILSZ is set to 4000 (4KB pages) for a
database. LOGPRIMARY and LOGSECONDARY are set to reasonable values.
However, the log files, instead of being 16MB in size, are about
16KB or 17KB in size.

Thus, there are numerous log sizes, the log directory is unresponsive,
etc..

What would cause this type of behaviour? Could it be a SQL
statement, continuously executed by mistake, causing the logs
to switch? It seems to me that the database manager and database
configuration are fine.

When the database is deactivated, it closes the current log file.
Activating the database opens a new log file.

Unless you have issued the "activate database" command, then the
first connection implicitly activates the database, and the last
connection that disconnects will implicitly deactivate it.


-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----

Nov 12 '05 #2

David Franit

Ian <ia*****@mobileaudio.com> wrote in message news:<41********@corp.newsgroups.com>...

David Franit wrote:

Hello,

On a v81 UDB AIX system, LOGFILSZ is set to 4000 (4KB pages) for a
database. LOGPRIMARY and LOGSECONDARY are set to reasonable values.
However, the log files, instead of being 16MB in size, are about
16KB or 17KB in size.

Thus, there are numerous log sizes, the log directory is unresponsive,
etc..

What would cause this type of behaviour? Could it be a SQL
statement, continuously executed by mistake, causing the logs
to switch? It seems to me that the database manager and database
configuration are fine.
When the database is deactivated, it closes the current log file.
Activating the database opens a new log file.

Unless you have issued the "activate database" command, then the
first connection implicitly activates the database, and the last
connection that disconnects will implicitly deactivate it.

Hi Ian,

Thanks for the response. Can I issue the 'Activate Database' command
dynamically at any time, or should I do it, say, after the database
starts, but before users log on?

You are likely correct, as there are many users connecting to the
database. Thus, perhaps the issue is that after 'db2start' is invoked,
the databases are not started or activated, and that they are
constantly activated and deactivated as people connect.
Thanks



-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----

Nov 12 '05 #3

Ian

David Franit wrote:

Ian <ia*****@mobileaudio.com> wrote in message news:<41********@corp.newsgroups.com>...

David Franit wrote:

Hello,

On a v81 UDB AIX system, LOGFILSZ is set to 4000 (4KB pages) for a
database. LOGPRIMARY and LOGSECONDARY are set to reasonable values.
However, the log files, instead of being 16MB in size, are about
16KB or 17KB in size.

Thus, there are numerous log sizes, the log directory is unresponsive,
etc..

What would cause this type of behaviour? Could it be a SQL
statement, continuously executed by mistake, causing the logs
to switch? It seems to me that the database manager and database
configuration are fine.

When the database is deactivated, it closes the current log file.
Activating the database opens a new log file.

Unless you have issued the "activate database" command, then the
first connection implicitly activates the database, and the last
connection that disconnects will implicitly deactivate it.

Hi Ian,

Thanks for the response. Can I issue the 'Activate Database' command
dynamically at any time, or should I do it, say, after the database
starts, but before users log on?

You can issue the activate database command at any time, whether users
are connected or not (you will get a warning if there are already users
on the system).

Also note that to do an offline backup you must deactivate the database.

-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----

Nov 12 '05 #4