Re: Logical Logs U----B------ status
If the logs aaren't important, then turn logging off for this database.
Neil Truby
Londis Stores
Hampton Hill,UK
Doug Castell wrote in message ...
>NT4 svc pk 3 with IDS 7.30.TC7
>
>I have been monkeying with my logical logs attempting to feel out the right
size
>to accommodate a huge insert I've been having long transaction problems
with. .
>. I've been able to insert large amounts of information, but this
particular
>table has almost twice as many records as I have previously been able to
insert.
>. . The one giving me problems has 3.9 million records. It seems to die
at
>1.9 million over and over. I added the three additional (odd sized ones)
that
>stand out in the below onstat -l information to no avail. . . In fact, it
seems
>to die much earlier now :(
>
>I have my logs set to continuously backup to NUL.
>
>I really am not concerned about my logs as my data is unimportant and
rolling it
>back is unimportant. It's all for load testing my application anyway. :)
>
>The following is the output of onstat -l :
>
>Physical Logging
>Buffer bufused bufsize numpages numwrits pages/io
> P-1 0 16 96 9 10.67
> phybegin physize phypos phyused %used
> 100a83 1000 70 0 0.00
>
>Logical Logging
>Buffer bufused bufsize numrecs numpages numwrits recs/pages pages/io
> L-2 0 8 621 61 55 10.2 1.1
> Subsystem numrecs Log Space used
> OLDRSAM 621 42796
>
>address number flags uniqid begin size used %used
>c312d24 1 U---C-L 4721 100233 125 9 7.20
>c312d40 2 U-B---- 4709 1002b0 125 1 0.80
>c312d5c 3 U-B---- 4710 10032d 125 2 1.60
>c312d78 4 U-B---- 4711 1003aa 125 1 0.80
>c312d94 5 U-B---- 4712 100427 125 1 0.80
>c312db0 6 U-B---- 4713 1004a4 125 1 0.80
>c312dcc 7 U-B---- 4714 100521 125 1 0.80
>c312de8 8 U-B---- 4715 10059e 125 1 0.80
>c312e04 9 U-B---- 4716 10061b 125 1 0.80
>c312e20 10 U-B---- 4717 100698 125 1 0.80
>c312e3c 11 U-B---- 4718 a00035 2500 1 0.04
>c312e58 12 U-B---- 4719 a009f9 25000 1 0.00
>c312e74 13 U-B---- 4720 a06ba1 17500 2 0.01
>
>I'm wondering why I can't get the logs freed. The documentation tells me
that
>to free U---B--- logs I need to simply go from on-line to quiescent mode.
I
>do this via onmode -u (and/or onmode -sy) and the onstat output above
doesn't
>change. . . even onmode -l through all of the logs one-by-one doesn't
entirely
>free them up. (that's how they got the way they are above. . . most of
them
>WERE at 100% for the most part)
>
>Attempting to do an ontape -a produces an error saying that I can't backup
to
>NUL
>
>
>Below are the log-related items from my onconfig (lemmie know if I left
anything
>out or have configured something very badly :o) :
>
>LOGFILES 13 # Number of logical log files
>LOGSIZE 4000 # Logical log size (Kbytes)>LOG_BACKUP_MODE CONT # Logical log backup mode (MANUAL, CONT)
>LTAPEDEV NUL # Log tape device path
>LTAPEBLK 64 # Log tape block size (Kbytes)
>LTAPESIZE 30000 # Max amount of data to put on log tape
(Kbytes)
>LOGBUFF 32 # Logical log buffer size (Kbytes)>LOGSMAX 15 # Maximum number of logical log files
>LTXHWM 50 # Long transaction high water markpercentage
>LTXEHWM 60 # Long transaction high water mark
(exclusive)>
>Any help would be greatly appreciated :)
>
>------------------
>Doug Castell
>
>
>