Spurious phys/log log-related messages in message log?
We recently brought a new Solaris 2.6 x86-based server online for
application development. It sports 512 MB memory, 2 processors and 4 x
4.23 GB disk drives. We're running IDS 7.30.UC2 and using cooked files.
I've moved phys and logical logs to a separate dbspace, increasing them
in number and/or size. No database uses logging and our LTAPEDEV is
/dev/null. Whenever I start Informix, the following error messages
appear in the message log:
08:02:06 WARNING! Physical Log size 0 is too small. Physical Log overflows may occur during peak activity.
Recommended minimum Physical Log size is 20 times maximum
concurrent user threads.
08:02:06 WARNING! Logical log layout may cause Dynamic Server to getinto
a locked state. Recommended smallest logical log size
is 2 times maximum concurrent user threads.
I suspect these are themselves in error -- here's clip from onconfig
file:
# Physical Log Configuration
PHYSDBS logdbs # Location (dbspace) of physical log
PHYSFILE 75000 # Physical log file size (Kbytes)
# Logical Log Configuration
LOGFILES 30 # Number of logical log files
LOGSIZE 750 # Logical log size (Kbytes)
And onstat -l output:
amdd-1:/home/informix: onstat -l
Informix Dynamic Server Version 7.30.UC2 -- On-Line -- Up 23:59:59 --
333088
bytes
Physical Logging
Buffer bufused bufsize numpages numwrits pages/io
P-2 0 32 13321 440 30.27
phybegin physize phypos phyused %used
802c27 37500 4495 0 0.00
Logical Logging
Buffer bufused bufsize numrecs numpages numwrits recs/pages pages/io
L-3 0 32 1021242 34007 1223 30.0 27.8
Subsystem numrecs Log Space used
OLDRSAM 1021242 68327928
address number flags uniqid begin size used %used
501164c0 7 U-B---- 2557 800035 375 375 100.00
501164dc 8 U-B---- 2558 8001ac 375 375 100.00
501164f8 9 U-B---- 2559 800323 375 375 100.00
50116514 10 U-B---- 2560 80049a 375 375 100.00
50116530 11 U-B---- 2561 800611 375 375 100.00
5011654c 12 U-B---- 2562 800788 375 375 100.00
50116568 13 U-B---- 2563 8008ff 375 375 100.00
50116584 14 U-B---- 2564 800a76 375 375 100.00
501165a0 15 U-B---- 2565 800bed 375 375 100.00
501165bc 16 U-B---- 2566 800d64 375 375 100.00
501165d8 17 U-B---- 2567 800edb 375 375 100.00
501165f4 18 U-B---- 2568 801052 375 375 100.00
50116610 19 U-B---- 2569 8011c9 375 375 100.00
5011662c 20 U-B---- 2570 801340 375 375 100.00
50116648 21 U---C-L 2571 8014b7 375 212 56.53
50116664 22 U-B---- 2542 80162e 375 375 100.00
50116680 23 U-B---- 2543 8017a5 375 375 100.00
5011669c 24 U-B---- 2544 80191c 375 375 100.00
501166b8 25 U-B---- 2545 801a93 375 375 100.00
501166d4 26 U-B---- 2546 801c0a 375 375 100.00
501166f0 27 U-B---- 2547 801d81 375 375 100.00
5011670c 28 U-B---- 2548 801ef8 375 375 100.00
50116728 29 U-B---- 2549 80206f 375 375 100.00
50116744 30 U-B---- 2550 8021e6 375 375 100.00
50116760 31 U-B---- 2551 80235d 375 375 100.00
5011677c 32 U-B---- 2552 8024d4 375 375 100.00
50116798 33 U-B---- 2553 80264b 375 375 100.00
501167b4 34 U-B---- 2554 8027c2 375 375 100.00
501167d0 35 U-B---- 2555 802939 375 375 100.00
501167ec 36 U-B---- 2556 802ab0 375 375 100.00
Has anyone else seen these error messages? Is there an explanation, or
am I simply missing something?
TIA
>
> # Physical Log Configuration
>
> PHYSDBS logdbs # Location (dbspace) of physical log
> PHYSFILE 75000 # Physical log file size (Kbytes)
Hm! Why dbspace with physical log is called 'logdbs' ? Is this correct ?
>
> # Logical Log Configuration
>
> LOGFILES 30 # Number of logical log files
> LOGSIZE 750 # Logical log size (Kbytes)
First of all, check your $ONCONFIG environment variable. Probably,
Informix sarted with incorrect ROOTPATH entry in onconfig. Then check
whether chunks with logs (both logical and physical) are present in
system, and files are located correctly (if raw devices, check links).
>
> And onstat -l output:
>
> amdd-1:/home/informix: onstat -l
>
> Informix Dynamic Server Version 7.30.UC2 -- On-Line -- Up 23:59:59 -
-
> 333088
> bytes
>
> Physical Logging
> Buffer bufused bufsize numpages numwrits pages/io
> P-2 0 32 13321 440 30.27
> phybegin physize phypos phyused %used
> 802c27 37500 4495 0 0.00
>
> Logical Logging
> Buffer bufused bufsize numrecs numpages numwrits recs/pages
pages/io
> L-3 0 32 1021242 34007 1223 30.0 27.8
> Subsystem numrecs Log Space used
> OLDRSAM 1021242 68327928
>
> address number flags uniqid begin size used %
used
> 501164c0 7 U-B---- 2557 800035 375 375
100.00
> 501164dc 8 U-B---- 2558 8001ac 375 375
100.00
> 501164f8 9 U-B---- 2559 800323 375 375
100.00
> 50116514 10 U-B---- 2560 80049a 375 375
100.00
> 50116530 11 U-B---- 2561 800611 375 375
100.00
> 5011654c 12 U-B---- 2562 800788 375 375
100.00
> 50116568 13 U-B---- 2563 8008ff 375 375
100.00
> 50116584 14 U-B---- 2564 800a76 375 375
100.00
> 501165a0 15 U-B---- 2565 800bed 375 375
100.00
> 501165bc 16 U-B---- 2566 800d64 375 375
100.00
> 501165d8 17 U-B---- 2567 800edb 375 375
100.00
> 501165f4 18 U-B---- 2568 801052 375 375
100.00
> 50116610 19 U-B---- 2569 8011c9 375 375
100.00
> 5011662c 20 U-B---- 2570 801340 375 375
100.00
> 50116648 21 U---C-L 2571 8014b7 375 212
56.53
> 50116664 22 U-B---- 2542 80162e 375 375
100.00
> 50116680 23 U-B---- 2543 8017a5 375 375
100.00
> 5011669c 24 U-B---- 2544 80191c 375 375
100.00
> 501166b8 25 U-B---- 2545 801a93 375 375
100.00
> 501166d4 26 U-B---- 2546 801c0a 375 375
100.00
> 501166f0 27 U-B---- 2547 801d81 375 375
100.00
> 5011670c 28 U-B---- 2548 801ef8 375 375
100.00
> 50116728 29 U-B---- 2549 80206f 375 375
100.00
> 50116744 30 U-B---- 2550 8021e6 375 375
100.00
> 50116760 31 U-B---- 2551 80235d 375 375
100.00
> 5011677c 32 U-B---- 2552 8024d4 375 375
100.00
> 50116798 33 U-B---- 2553 80264b 375 375
100.00
> 501167b4 34 U-B---- 2554 8027c2 375 375
100.00
> 501167d0 35 U-B---- 2555 802939 375 375
100.00
> 501167ec 36 U-B---- 2556 802ab0 375 375
100.00
>
And Informix starts with this errors ? Please send complete log
fragment related to Informix start. But I think, Informix can't start
with zero physical log.
--
With best regards, Yuri Dovgart,
SAP R/3, Informix consultant,
"Telecominvest" company.
E-mail y_dovgart@tci.ukrtel.net
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
Ooh, ooh, oooooh, I know this one! You have set LRUS to 128. There is a
bug in all version that I have tested prior to 7.31 that causes these two
completely harmless and fully spurious messages to be displayed if LRUS is
set to exactly 128 (the maximum value). Just reduce LRUS to 127 and the
messages will go away and your performance will not be significantly
affected, or live with the messages until you upgrade. I reported this
one to Informix with version 7.21 and it just never got a high enough
priority to get fixed, only the LRU rewrite in 7.31 seems to have finally
fixed it accidentally.
Art S. Kagel
Red Valsen wrote:
>
> We recently brought a new Solaris 2.6 x86-based server online for
> application development. It sports 512 MB memory, 2 processors and 4 x
> 4.23 GB disk drives. We're running IDS 7.30.UC2 and using cooked files.
>
> I've moved phys and logical logs to a separate dbspace, increasing them
> in number and/or size. No database uses logging and our LTAPEDEV is
> /dev/null. Whenever I start Informix, the following error messages
> appear in the message log:
>
> 08:02:06 WARNING! Physical Log size 0 is too small.> Physical Log overflows may occur during peak activity.
> Recommended minimum Physical Log size is 20 times maximum
> concurrent user threads.
>
> 08:02:06 WARNING! Logical log layout may cause Dynamic Server to get> into
> a locked state. Recommended smallest logical log size
> is 2 times maximum concurrent user threads.
>
> I suspect these are themselves in error -- here's clip from onconfig
> file:
>
> # Physical Log Configuration
>
> PHYSDBS logdbs # Location (dbspace) of physical log
> PHYSFILE 75000 # Physical log file size (Kbytes)>
> # Logical Log Configuration
>
> LOGFILES 30 # Number of logical log files
> LOGSIZE 750 # Logical log size (Kbytes)>
> And onstat -l output:
>
> amdd-1:/home/informix: onstat -l
>
> Informix Dynamic Server Version 7.30.UC2 -- On-Line -- Up 23:59:59 --
> 333088
> bytes
>
> Physical Logging
> Buffer bufused bufsize numpages numwrits pages/io
> P-2 0 32 13321 440 30.27
> phybegin physize phypos phyused %used
> 802c27 37500 4495 0 0.00
>
> Logical Logging
> Buffer bufused bufsize numrecs numpages numwrits recs/pages pages/io
> L-3 0 32 1021242 34007 1223 30.0 27.8
> Subsystem numrecs Log Space used
> OLDRSAM 1021242 68327928
>
> address number flags uniqid begin size used %used
> 501164c0 7 U-B---- 2557 800035 375 375 100.00
> 501164dc 8 U-B---- 2558 8001ac 375 375 100.00
> 501164f8 9 U-B---- 2559 800323 375 375 100.00
> 50116514 10 U-B---- 2560 80049a 375 375 100.00
> 50116530 11 U-B---- 2561 800611 375 375 100.00
> 5011654c 12 U-B---- 2562 800788 375 375 100.00
> 50116568 13 U-B---- 2563 8008ff 375 375 100.00
> 50116584 14 U-B---- 2564 800a76 375 375 100.00
> 501165a0 15 U-B---- 2565 800bed 375 375 100.00
> 501165bc 16 U-B---- 2566 800d64 375 375 100.00
> 501165d8 17 U-B---- 2567 800edb 375 375 100.00
> 501165f4 18 U-B---- 2568 801052 375 375 100.00
> 50116610 19 U-B---- 2569 8011c9 375 375 100.00
> 5011662c 20 U-B---- 2570 801340 375 375 100.00
> 50116648 21 U---C-L 2571 8014b7 375 212 56.53
> 50116664 22 U-B---- 2542 80162e 375 375 100.00
> 50116680 23 U-B---- 2543 8017a5 375 375 100.00
> 5011669c 24 U-B---- 2544 80191c 375 375 100.00
> 501166b8 25 U-B---- 2545 801a93 375 375 100.00
> 501166d4 26 U-B---- 2546 801c0a 375 375 100.00
> 501166f0 27 U-B---- 2547 801d81 375 375 100.00
> 5011670c 28 U-B---- 2548 801ef8 375 375 100.00
> 50116728 29 U-B---- 2549 80206f 375 375 100.00
> 50116744 30 U-B---- 2550 8021e6 375 375 100.00
> 50116760 31 U-B---- 2551 80235d 375 375 100.00
> 5011677c 32 U-B---- 2552 8024d4 375 375 100.00
> 50116798 33 U-B---- 2553 80264b 375 375 100.00
> 501167b4 34 U-B---- 2554 8027c2 375 375 100.00
> 501167d0 35 U-B---- 2555 802939 375 375 100.00
> 501167ec 36 U-B---- 2556 802ab0 375 375 100.00
>
> Has anyone else seen these error messages? Is there an explanation, or
> am I simply missing something?
> TIA