Why would the archive log file sizes be so different, for example:

7210072 May 31 17:40 S0000580.LOG.040531174050.Z
8853 May 31 18:20 S0000581.LOG.040531182002.Z
1685094 May 31 18:40 S0000583.LOG.040531184049.Z
31895868 May 31 19:22 S0000584.LOG.040531192512.Z
29923649 May 31 19:25 S0000585.LOG.040531202059.Z
31135511 May 31 20:20 S0000586.LOG.040531202321.Z
31117548 May 31 20:23 S0000587.LOG.040531212052.Z
29273003 May 31 21:20 S0000588.LOG.040531212312.Z
31703735 May 31 21:23 S0000589.LOG.040531215833.Z
4282 May 31 22:20 S0000591.LOG.040531222032.Z
31194061 May 31 22:23 S0000592.LOG.040531222717.Z
1332789 May 31 22:40 S0000594.LOG.040531224042.Z
24224816 May 31 23:40 S0000595.LOG.040531234051.Z
38768849 Jun 01 00:26 S0000596.LOG.040601004630.Z
9008631 Jun 01 01:20 S0000598.LOG.040601012021.Z
35618051 Jun 01 02:20 S0000600.LOG.040601022022.Z
30971639 Jun 01 02:40 S0000601.LOG.040601024032.Z
8159727 Jun 01 03:40 S0000602.LOG.040601034024.Z
7841793 Jun 01 04:40 S0000603.LOG.040601044022.Z
5921237 Jun 01 05:40 S0000604.LOG.040601054016.Z

I have the size set at (LOGFILSIZ) = 30000.

It also looks like the database logfiles numbers are out of sequence. For instance:

400
401
404
405
406
409

When the last user disconnected from the database, the logfile is closed
and truncated and userexit program archive the file, not to hahave this
behaviour use activate database command.

when the backup is completed , the active log file is closed and truncated and archived, so that we have a complete set of archived files.This behaviour
can also be changed, but not recommended.

regards,

mujeeb

Uncompress the logfiles and check their sizes ...

Cheers
Sathyaram