My Oracle Support Banner

Mboxlist DB Transaction Log File Accumulation When Using Rehostuser (Doc ID 1493480.1)

Last updated on DECEMBER 12, 2024

Applies to:

Oracle Communications Messaging Server - Version 7.0.4 to 7.0.4 [Release 7.0.0]
Information in this document applies to any platform.

Symptoms

The mboxlist DB transaction log files seem to have stopped processing.  A listing of the mboxlist directory, collected by dbhang, showed:

% cat mboxlist.ls
total 1540644
drwx------   4 <USER>   <GROUP>      46 Sep 18 12:31 .
drwx------   6 <USER>   <GROUP>       6 Jan 29  2012 ..
-rw-------   1 <USER>   <GROUP>       0 Jan 30  2012 .loglock
-rw-------   1 <USER>   <GROUP>  122880 Sep 18 11:38 annotate.db
-rw-------   1 <USER>   <GROUP> 167309312 Sep 18 12:32 folder.db
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 11:37 log.0000032129
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 11:39 log.0000032130
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 11:41 log.0000032131
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 11:43 log.0000032132
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 11:45 log.0000032133
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 11:47 log.0000032134
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 11:49 log.0000032135
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 11:51 log.0000032136
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 11:53 log.0000032137
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 11:54 log.0000032138
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 11:56 log.0000032139
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 11:58 log.0000032140
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 12:00 log.0000032141
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 12:01 log.0000032142
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 12:02 log.0000032143
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 12:03 log.0000032144
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 12:04 log.0000032145
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 12:06 log.0000032146
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 12:07 log.0000032147
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 12:08 log.0000032148
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 12:10 log.0000032149
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 12:12 log.0000032150
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 12:13 log.0000032151
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 12:15 log.0000032152
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 12:16 log.0000032153
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 12:18 log.0000032154
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 12:19 log.0000032155
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 12:21 log.0000032156
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 12:23 log.0000032157
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 12:25 log.0000032158
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 12:26 log.0000032159
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 12:28 log.0000032160
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 12:30 log.0000032161
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 12:31 log.0000032162
-rw-------   1 <USER>   <GROUP> 10485760 Sep 18 12:32 log.0000032163
drwx------   2 <USER>   <GROUP>       4 Sep 18 11:36 logarchive
-rw-------   1 <USER>   <GROUP>    8192 Jan 29  2012 lright.db
drwx------   2 <USER>   <GROUP>       9 Sep 18 11:53 mqueue
-rw-------   1 <USER>   <GROUP> 202575872 Sep 18 12:32 peruser.db
-rw-------   1 <USER>   <GROUP> 15651840 Sep 18 12:32 quota.db
-rw-------   1 <USER>   <GROUP> 37773312 Sep 18 12:32 subscr.db

Notice the time stamp of the oldest log file is 11:37.  Watching this over time, that same file remains the oldest and its date/time does not change.

These log files should be processed by stored once per minute, by the txn_checkpoint function.

Eventually msprobe will notices there are more than the number specified by the local.store.maxlog configutil option, which defaults to 50.  That will cause a restart, with a message from msprobe like:

mboxlist db log file accumulated, number of log files: %d (%u-%u). Restart server now!

A rehostuser command was started about the same time as the oldest transaction log file:

  <USER> S  59 16669 16667  0.0  0.1 592800 20688 11:36:36       00:01    1   - rehostuser -u <USERID> -d ...

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.