Re: IFMX Command Center hangs!

The problem is that Informix' GUI utilities centered around the Server Administration port you define (go to Setup in Command Center even though Command Center is not working. The port definitions are in there) do not handle large memory areas well. As a result, after a certain amount of RAM has been allocated for the Informix instance, the utilities stop working. The Database Explorer works on the Database Administration port and does not have this problem. You can temporarily fix this by: 1) stopping Informix (and any related software such as Baan) 2) Editting your onconfig file and changing the following parameters: BUFFERS <= 9000 LOCKS <= 9000 LOGFILES <= 20 and reduce any other parameter that is creating demand for RAM (such as SHM_VIRTSIZE, LOG_BUFFERS, etc). 3) Re-start your database. Unfortunately, this makes your database's resource usage considerably smaller which will affect its performance. Particularly for Baan, this should ONLY BE DONE TO USE THE GUI utilities. All settings should be restored after the DB admin is done so that normal users do not have reduced performance. For most folks, this is not a good choice however and they end up simply using the command line utilities. Informix will have this fixed (hopefully) in the upcoming version release of 7.23 -dt In article <jlumbleyEL01o7.7oA@netcom.com>, jlumbley@netcom.com (Joe Lumbley) wrote: > > Eric R. Gavin (Eric_Gavin@maf.org) wrote: > : I'm running ODS7.23 on NT4 and when I try to use any of the Command Center > : GUI utilities, they will all hang and eventually go "Not Responding..." once > : the database server is selected and a username and password is entered (I > : have the ask password at runtime option set in SetNet32) > > : HOWEVER, the Database Explorer works just fine!! AND, all of the Command > : Line Utilities work just fine as well. > > : The case mentioned above happens both when I'm using the Command Center > : utilities from a remote machine (one on the LAN) and at the local server > : itself. > > : Because of restrictions placed by the Baan software running on the same > : server, the NT Server is NOT part of our domain -- if that helps any. > > I'm not totally sure about this, as I'm debugging the same problem on one > of my systems, but I think it has to do with not having administrator > permissions on the server's domain. I haven't been able to test it yet > because our network administrator is so anal-retentive that nobody else can > get network admin permissions and it's not worth fighting about. > > Anybody know the answer for sure? > > joe > : Can anybody offer insight into this problem? > > : TIA, > > : Eric Gavin > > -- > --------------------------------------------------------------------------- > Joe Lumbley(jlumbley@netcom.com) author of: "INFORMIX DBA Survival Guide" > > Slaving away on "INFORMIX DEBUGGERS Survival Guide", available early 1998 > from Prentice Hall/Informix Press. If you have debugging tips, tools, or > ideas to share, please send me some e-mail. > --------------------------------------------------------------------------- -------------------==== Posted via Deja News ====----------------------- http://www.dejanews.com/ Search, Read, Post to Usenet