Search results

After restoring OpenEdge Release 10.1C04 database, we got Progress error 395, complaining about the lock file value in admprod, but only through the GUI MfgPro screen (not in character). Progress recommends adding the -nolkctr client parameter, but we were able to resolve this by restarting...

Hello, installed MSW/PSW in QAD SE2009 Progress 10, and the workbenches don't start. When clicked, QAD spins for a second and then nothing happens. Went back over the install (licensing, NETUI packages, schema add, data load, help file load, etc) and everything seems okay, all the other MSW...

YES! Finally figured it out. 1) change the propath in connmgr.[env] 2) go into Connection Manager in [env] and choose Restart Connection Manager 3) enjoy your new propath I was able to replicate this a few times, very confident now. The literature is very misleading, the ubroker.properties...

Thanks, but that's what I tried originally and it didn't work. Maybe I'll try it again though, in case I missed something. We actually rebooted the entire box (for unrelated reasons) and it still didn't pick up the new propath from connmgr or ubroker.properties. Very odd. I think next I might...

So, surprise surprise, changing connmgr back did not change the propath back, even after restarting the broker (I modified a QAD program to display the propath). And it's not using the ubroker.properties propath either -- it's definitely using the old connmgr propath that I successfully changed...

Aha, apparently it IS connmgr. Not sure why it didn't seem to work before, but I have Prod and Test pointing to different code now so good enough,

Well, apparently that wasn't it, and neither were the connmgr/telnet scripts that mfgutil generates. Any ideas? Also checked web-disp.p. The webspeed broker claims to have the test directory at the front when I check it from IE, but it won't actually run anything there. Also tried opening...

Ah, looks like this happens in ubroker.properties in DLC/properties. Will try this tomorrow. qad.com/Documents/TrainingGuides/printondemand/70-2831A.pdf

Hello, I inherited a smallish EB2.1 NETUI 2.81.4.87 Progress 10C setup in which there is currently no test code directory. I want to make the NETUI Test client point to my new test code directories, but I haven't had to deal with this before -- where is the propath set for NETUI clients? Is...

Never mind, found the problem in a screwy setting. Thanks anyway!

Nope, already tried that. No help at all.

Updated licenses for 10.1C on Linux, databases now return this error: Unable to read progress.cfg, reason=-4. (1732) Unable to read progress.cfg, reason=-4. (1732) Unable to read progress.cfg, reason=-4. (1732) Unable to read progress.cfg, reason=-4. (1732) Unable to read progress.cfg...

Rob -- thanks for the response. I agree on -9, but we can't wait to schedule an outage when large numbers of users are already hung and unable to work. It was "kill or restart db now". Promon shows the tx, but says the user is disconnected. VSTs also show the transaction. "Zombie" is what...

Thanks Rob, here's what I can quickly respond on that before I fall asleep and mash the keyboard with my forehead: -- users are only kicked for sitting in QAD maintenance screens, we are very careful about transaction scoping, and the kick log is monitored, long-running transactions would be...

Had to reboot our ancient, rusty 8.3A QAD (running on HP-UX 11i) database today due to a nasty issue relating to users who were either kicked through an automated proshut script (it kicks users after about 10 minutes of holding open a transaction, to protect the BI file from hitting 1G and...

Just an update: with -spin, it appears we've passed our Monday acid test with flying colors. Performance has remained optimal this morning. Thanks again to Tom for that suggestion. Possibly interesting side note: this whole database is apparently now running on solid-state disks. Users...

I did the test both ways again just to be sure I wasn't fooling myself, and -spinlock 10000 totally eliminates the performance issue in Test. Just for the hell of it, I ran the 34-process spawner 4 more times in one test, checking performance each time, so eventually I had 170 processes...

Spinlock FTW! Tried that on our test server -- my 34-process spawning script previously brought the database to its knees, performance was horrible, .01 records per ms. With -spinlock 10000, performance is normal. Thanks a bunch Tom, I think this was our issue. Keeping fingers crossed for our...

Thanks Rob. After doing some more reading, I'm increasingly optimistic about the block size change. The DB HWM is only 4.2G and with an 8K block size we can put 4G, or nearly the entire database, into memory (vs the 150MB we have today) and the server has 20G with ~14G normally free today. It's...

Well, I wrote a script to beat on the database in much the same way the users are (it spawns 34 processes to do reads against a couple tables -- this is more or less what's happening). This nicely replicates our conditions at the problem times (8-10A) during which times about 34 users all want...