Oninit cdi / Archive
Talk to an expert →

onstat -u and IDS maximum concurrent sessions

Posted in 2006

Topics: Backup & Restore, Versions, Editions & End-of-Life

Peter J Diaz de — — source: IIUG Forums & Mailing Lists

I keep out IDS test environments instances in sync by bringing over the latest level-0 OnBar archive and doing a cold restore. When I issue an onstat -u the output reports the maximum concurrent at the bottom. My question are as follows. Is the maximum concurrent reset during reboots? Is the maximum concurrent that being reported in our test environment, actually the maximum concurrent for the production server since the test environment is a level-0 cold restore from production? The environment is: RH 3.0 ES IDS 9.40.UC7 Thanks Peter

↪ replying to Peter J Diaz de
Robert — — source: IIUG Forums & Mailing Lists

I believe it's the maximum amount of user threads that the db has allocated control blocks for, up to the current snapshot. Bob Roussey Unix / Informix Administration Robert.Roussey@SpiritAir.com -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Peter J Diaz de Leon Sent: Wednesday, October 25, 2006 11:32 AM To: ids@iiug.org Subject: onstat -u and IDS maximum concurrent sessions [7674] I keep out IDS test environments instances in sync by bringing over the latest level-0 OnBar archive and doing a cold restore. When I issue an onstat -u the output reports the maximum concurrent at the bottom. My question are as follows. Is the maximum concurrent reset during reboots? Is the maximum concurrent that being reported in our test environment, actually the maximum concurrent for the production server since the test environment is a level-0 cold restore from production? The environment is: RH 3.0 ES IDS 9.40.UC7 Thanks Peter ************************************************************************ ******* Forum Note: Use "Reply" to post a response in the discussion forum.

↪ replying to Robert
SANJIT — — source: IIUG Forums & Mailing Lists

The 'maximum concurrent' in the last line of 'onstat -u' output, indicates that the maximum number of user threads that were running concurrently since you initialized the database server. I believe to get the right number on development environment; you need to bounce the database server after restore complete. -Sanjit

↪ replying to SANJIT
Noel Murphy — — source: IIUG Forums & Mailing Lists

"maximum concurrent" gets reset with an onstat -z -----Original Message----- From: SANJIT CHAKRABORTY [mailto:c_sanjit@lycos.com] Sent: 26 October 2006 15:03 To: ids@iiug.org Subject: Re: RE: onstat -u and IDS maximum concurrent s.... [7679] The 'maximum concurrent' in the last line of 'onstat -u' output, indicates that the maximum number of user threads that were running concurrently since you initialized the database server. I believe to get the right number on development environment; you need to bounce the database server after restore complete. -Sanjit ************************************************************************ ******* Forum Note: Use "Reply" to post a response in the discussion forum. ________________________________________________________________________ This email has been scanned for all viruses by the MessageLabs Email Security System before entering the GFM Network. If you have any queries please contact Systems Administration or IT. ________________________________________________________________________ ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________

Related threads

Glossary