Why this Long Transaction?

Folks, I've run across something I'm not sure about and thought maybe the accumulated nettelligence could figure it out. Twelve hours ago my large database was shut down ungracefully, with a monster insert operation going on. About 2 million rows in the table, but I don't know how many were actually inserted. On restart, we went into that misnomer of all misnomers , "fast recovery". That was about 11.5 hours ago. It's been recovering since then. At about the 10.5 hour mark, my tbstat -t output showed a Long Transaction flag. My LTXHWM is 70% and my LTXEHWM is 80%. I'm currently at about 40% log usage and nothing else is running. So why the long transaction? Are there different rules for how the HWM's work in recovery? Is there some kind of time check? I know it won't make any difference and I'll still be recovering for another 45 minutes, but it's bothering my little monkey brain. Appropriate tbstat data follows: RSAM Version 4.10.UD4 -- Fast Recovery (LONGTX) -- Up 11:08:10 -- 18704 Kbytes Tblspaces n address flgs ucnt tblnum physaddr npages nused npdata nrows nextns 0 e0679028 1 1 1000001 10000e 2705 251 0 0 1 1 e067911c 1 1 2000001 400004 2955 2 0 0 1 2 e0679210 1 1 3000001 500004 16255 4253 0 0 1 3 e0679304 1 1 4000001 700004 2705 2 0 0 1 4 e06793f8 1 1 5000001 a00004 17205 3487 0 0 1 5 e06794ec 1 1 6000001 c00004 2705 20 0 0 1 6 e06795e0 3 1 6000013 c00016 70000 68960 43325 32442 5 7 active, 1500 total, 512 hash buckets Physical Logging Buffer bufused bufsize numpages numwrits pages/io P-2 24 128 719097 6226 115.50 phybegin physize phypos phyused %used 118992 6000 3367 2456 40.93 Logical Logging Buffer bufused bufsize numrecs numpages numwrits recs/pages pages/io L-1 9 64 2980511 23358 481 127.6 48.6 address number flags uniqid begin size used %used e06d25d8 1 U-B---- 3264 400b8e 30000 30000 100.00 e06d25f4 2 U-B---- 3265 4080be 30000 30000 100.00 e06d2610 3 U-B---- 3266 40f5ee 30000 30000 100.00 e06d262c 4 U-B---- 3267 10126e 30000 30000 100.00 e06d2648 5 U-B---- 3268 10879e 30000 30000 100.00 e06d2664 6 U-B---- 3269 10fcce 30000 11226 37.42 e06d2680 7 U------ 3270 416b1e 30000 30000 100.00 e06d269c 8 U---C-L 3271 800003 30000 3219 10.73 e06d26b8 9 F------ 0 700a94 30000 0 0.00 e06d26d4 10 F------ 0 707fc4 30000 0 0.00 e06d26f0 11 F------ 0 70f4f4 30000 0 0.00 e06d270c 12 F------ 0 716a24 30000 0 0.00 e06d2728 13 F------ 0 900003 30000 0 0.00 e06d2744 14 F------ 0 907533 30000 0 0.00 e06d2760 15 F------ 0 807533 30000 0 0.00 e06d277c 16 F------ 0 90ea63 30000 0 0.00 e06d2798 17 F------ 0 915f93 30000 0 0.00 e06d27b4 18 F------ 0 80ea63 30000 0 0.00 e06d27d0 19 F------ 0 815f93 30000 0 0.00 e06d27ec 20 U-B---- 3263 81d4c3 30000 30000 100.00 From $INFORMIXDIR/etc/tbconfig LTAPEDEV /dev/rmt2 # Log tape device path LTAPEBLK 16 # Log tape block size (Bytes) LTAPESIZE 3950000 # Max amount of data to put on log tape (Kbytes) LTXHWM 70 LTXEHWM 80 -- =========================================================================== jlumbley@netcom.com (Joe Lumbley) "If you believe that my statements Database Administrator represent my company, please send The Tigon Corporation money and I'll send you stock" Dallas, Texas Watch for my _INFORMIX DBA SURVIVAL GUIDE_ in Fall '94 from Prentice Hall! ===========================================================================