Re: oninit -r

Thuc Nguyen wrote: > > Hi everyone, > > I restored a full system from the tape and then started online. I checked > onlog file. The warning message: 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 threats. > WHERE CAN I FIND THE INFORMATION ON CONCURRENT USER > THREATS? I cant find it in the onconfig. > I don't know whether it's a good idea to tell you the following: Try to set the physical log file size to: t = maximum number of concurrent user threads l = maximum transaction space neccessary for one of these users-threads physicallogsize = t * l * (2/3) If you can't find a value for "t" or "l", simply use the follwoing: physicallogsize = ( total logical log size ( all files ) ) / 3 > Also I checked ps -eaf | grep informix and noticed that it was 8 oninit -r > after restoration and online started. I thought it should be oninit -s. What you will see in the output of the "ps -ef" command is just the command line of the origin command. You didn't start up the system by "onmonitor -> Startup" or "oninit -s", but by "oninit -r". The restore process brings your system up in "Quiescent Mode" and you used "onmode -m" or "onmonitor" to switch the system to "OnLine" mode. Therefore, th eoutput of your "ps -ef" command is correct. Next time, when you restart your system again, you will see the regular "oninit -s" command line. Have a nice day, Stefan