We use Red Hat Linux, OE 10.2B06 and it has worked well. I'm sure Progress has a KB that says not to do this though.
Like Rob suggests, we occasionally have a monitor that begins to read the _Lock table, only to have it increase to a large value. We don't have anything in place that would...
Sorry - I meant the _DbStatus._DbStatus-NumLocks. I should have said if the current number of locks is below ....
On 10.2B06 in non production environments we have scanned _Lock tables with 500,000 locks or so and the results are back in a minute or 2.
on 10.2B06 we use _Lock to collect the info. In prod, we check to make sure the current locks are below a set amount - like 10,000 and then go through the table.
upgrading from 10.2B to 11.5.
start the admin server - works fine.
start asbroker1 or NS1 - fail with no error.
If I add the -Xms32m -Xmx512m to asbroker1, then asbroker1 will start.
has anyone else experienced something like this ?
I have never been able to get this to work in a prod environment with shared memory users.
For dev / test environments though, I have been able to make small increases to resources which don't require adding a shared memory segment, for example adding an extra 10,000 locks will usually work.
I'm guessing disk io is the cause of performance issues since the memory is so low and the db uses Type I storage areas. Do you have stats on what tables are read the most ?
Usually there are 5 to 10 tables which comprise a large percent of the total reads in the db. If some of those tables...
I would recommend generating a protrace of the process to see what shows up in the "Persistent procedures/Classes" section of the protrace file. We have found thousands of persistent procedures loaded in memory due to bad code. Redhat -> kill -s USR1 <pid>. then go to the current working...
we had a similar issue with Solaris many years back. If I recall correctly, we changed the default setting of the TCP Keepalive parameter. make sure you are running a watch dog process.
I wrote a script that tailed the db log looking for the word vv_flush and if found it disconnected the user...
Windows Perfmon is able to track disk stats now without setting some flag and rebooting the server. I would highly recommend tracking the disk queue on the storage system with perfmon.
Avoiding NUMA architecture is hard to do for large servers. I was recently bit by NUMA, the effects were...
We are 10.2B and linux / unix. We use OEE in some non prod environments and we use OEM in some prod environments.
We use app servers so OEE is a way to quickly make config changes to the app servers rather than use mergeprop. That is the only item we use it for.
We use OEM in prod for a few...
we used Fusion IO cards for a trial basis on HP servers. The performance was really good, each card was around 600gb of storage. Not sure how different those are from the setup you are talking about. We ended up going with a solid state disk system with around 25TB from a different vendor.
Why not just test it during a weekend or other time when client isn't using system ? Run a binary dump during off hours and then load it in a 2nd copy.
its only 8gb so you probably have enough space.
we use proshut to display users and WDOG appears along with the other background processes. This also appears in certain promon screens.
usr pid time of login user id tty Limbo?
5 1395 Wed Jun 18 02:36:17 2014 APW /dev/pts/40 no
6...
use ifnull function to determine if the field is null, if it isn't use an update statement to set the value of the field. IfNull isn't going to update the record.
look in $DLC/properties/ubroker.properties for the settings for the SrvrInstance. It seems like some app server agents are being trimmed.
initialSrvrInstance: 5
maxSrvrInstance: 5
minSrvrInstance: 5
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.