Maximum user processes for logging - Hewlett Packard

This is a discussion on Maximum user processes for logging - Hewlett Packard ; Hello, we have a HP-3000, using minisoft's ODBC for our Web Portal applications. Yesterday, we received a turbo-image error, indicating our database transaction log file had reached its maximum number of user processes. Doing some research via DBAUDIT, I discovered ...

+ Reply to Thread
Results 1 to 6 of 6

Thread: Maximum user processes for logging

  1. Maximum user processes for logging

    Hello, we have a HP-3000, using minisoft's ODBC for our Web Portal applications.

    Yesterday, we received a turbo-image error, indicating our database transaction log file had reached its maximum number of user processes.
    Doing some research via DBAUDIT, I discovered one of our web applications did indeed have a large number of transactions.

    I found the following article on the FAQ section of the HP3000-L list:



    Concurrent accessors when using database logging on the HP3000





    Due to limits in MPE's internal tables, the maximum number of processes that can share a log process -- which in this case means the maximum number ofprocesses that can open a database with modify-access -- is 1140. Beware of this on limit on large systems.



    -- ChrisBartram - 18 May 2006







    My question: If I break-out the transactions from our heaviest web application (the heaviest one is from a separate database) into a separate db transaction log file (currently one log file shares a number of different database transactions), will this help reduce the number of problems with the above mentioned limitation?



    Heidi D. Wilker
    Systems Analyst
    Baltimore City Community College
    600 East Lombard Street Bard 301-G
    Baltimore, MD 21202
    Office: 410-986-3257
    Fax: 410-986-3277
    E-mail: hwilker@bccc.edu
    http://www.bccc.edu

    "It is in our moments of decision, that shape our destiny"


    * To join/leave the list, search archives, change list settings, *
    * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *


  2. Re: Maximum user processes for logging

    Sounds like a subtle hint to buy more HP3000s (so you can have less
    users per DB. :O )

    Some places have turned on DB logging to meet SOX requirements. With
    growth, they are pushing the limits of this utility.

    Tracy Johnson
    Measurement Specialties Inc.
    BT






    NNNN

    > -----Original Message-----
    > From: HP-3000 Systems Discussion
    > [mailto:HP3000-L@RAVEN.UTC.EDU] On Behalf Of Wilker, Heidi
    > Sent: Tuesday, July 29, 2008 8:22 AM
    > To: HP3000-L@RAVEN.UTC.EDU
    > Subject: [HP3000-L] Maximum user processes for logging
    >
    > Hello, we have a HP-3000, using minisoft's ODBC for our Web
    > Portal applications.
    >
    > Yesterday, we received a turbo-image error, indicating our
    > database transaction log file had reached its maximum number
    > of user processes.
    > Doing some research via DBAUDIT, I discovered one of our web
    > applications did indeed have a large number of transactions.
    >
    > I found the following article on the FAQ section of the HP3000-L list:
    >
    >
    >
    > Concurrent accessors when using database logging on the HP3000
    >
    >
    >
    >
    >
    > Due to limits in MPE's internal tables, the maximum number of
    > processes that can share a log process -- which in this case
    > means the maximum number of processes that can open a
    > database with modify-access -- is 1140. Beware of this on
    > limit on large systems.
    >
    >
    >
    > -- ChrisBartram
    > - 18 May 2006
    >
    >
    >
    >
    >
    >
    >
    > My question: If I break-out the transactions from our
    > heaviest web application (the heaviest one is from a separate
    > database) into a separate db transaction log file (currently
    > one log file shares a number of different database
    > transactions), will this help reduce the number of problems
    > with the above mentioned limitation?
    >
    >
    >
    > Heidi D. Wilker
    > Systems Analyst
    > Baltimore City Community College
    > 600 East Lombard Street Bard 301-G
    > Baltimore, MD 21202
    > Office: 410-986-3257
    > Fax: 410-986-3277
    > E-mail: hwilker@bccc.edu
    > http://www.bccc.edu
    >
    > "It is in our moments of decision, that shape our destiny"
    >
    >
    > * To join/leave the list, search archives, change list settings, *
    > * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
    >


    * To join/leave the list, search archives, change list settings, *
    * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *


  3. Re: Maximum user processes for logging

    The answer is yes.

    The limit is 1140 processes PER logid.

    So, by splitting the transactions among more that one logid (ie: more
    than one transaction log file) you proportionately increase the total
    number of active log processes - although you are still constrained
    by the 1140 max. per logid.

    At 08:22 AM 08-07-29, Wilker, Heidi wrote:
    >Hello, we have a HP-3000, using minisoft's ODBC for our Web Portal
    >applications.
    >
    >Yesterday, we received a turbo-image error, indicating our database
    >transaction log file had reached its maximum number of user processes.
    >Doing some research via DBAUDIT, I discovered one of our web
    >applications did indeed have a large number of transactions.
    >
    >I found the following article on the FAQ section of the HP3000-L list:
    >
    >
    >
    >Concurrent accessors when using database logging on the HP3000
    >
    >
    >
    >
    >
    >Due to limits in MPE's internal tables, the maximum number of
    >processes that can share a log process -- which in this case means
    >the maximum number of processes that can open a database with
    >modify-access -- is 1140. Beware of this on limit on large systems.
    >
    >
    >
    >-- ChrisBartram
    > - 18 May 2006
    >
    >
    >
    >
    >
    >
    >
    >My question: If I break-out the transactions from our heaviest web
    >application (the heaviest one is from a separate database) into a
    >separate db transaction log file (currently one log file shares a
    >number of different database transactions), will this help reduce
    >the number of problems with the above mentioned limitation?
    >
    >
    >
    >Heidi D. Wilker
    >Systems Analyst
    >Baltimore City Community College
    >600 East Lombard Street Bard 301-G
    >Baltimore, MD 21202
    >Office: 410-986-3257
    >Fax: 410-986-3277
    >E-mail: hwilker@bccc.edu
    >http://www.bccc.edu
    >
    >"It is in our moments of decision, that shape our destiny"
    >
    >
    >* To join/leave the list, search archives, change list settings, *
    >* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
    >
    >
    >No virus found in this incoming message.
    >Checked by AVG - http://www.avg.com
    >Version: 8.0.138 / Virus Database: 270.5.6/1579 - Release Date:
    >7/29/2008 6:43 AM


    -------------------------------------------------------------------------------------------------
    Gilles Schipper
    GSA Inc.
    HP System Administration Specialists
    300 John Street, Box 87651 Thornhill, ON Canada L3T 7R4
    Voice: 905.889.3000 Fax: 905.889.3001
    email: gilles@gsainc.com web: http://www.gsainc.com
    -------------------------------------------------------------------------------------------------

    * To join/leave the list, search archives, change list settings, *
    * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *


  4. Re: Maximum user processes for logging

    IN 7.5

    By Jyothi BS Commercial Systems Division Background
    Current Limit

    At present 1140 user processes (users) are allowed access per User
    logging process. With an increased number of high-end systems and
    increased number of users, this limit may become a roadblock to many
    that employ User Logging.

    The Objective of the solution is to increase the maximum number of user
    level processes to 2851 from the current 1140 level.
    How to Increase the Limit in SYSGEN

    1.

    Go to 'log (lo)'
    2.

    Set the limit by the command 'ulog usersperproc = 2851'

    This changes the current value of # users per logging process to
    2851.
    3.

    The system has to be booted again to implement this change.


    Wilker, Heidi wrote:
    > Hello, we have a HP-3000, using minisoft's ODBC for our Web Portal applications.
    >
    > Yesterday, we received a turbo-image error, indicating our database transaction log file had reached its maximum number of user processes.
    > Doing some research via DBAUDIT, I discovered one of our web applications did indeed have a large number of transactions.
    >
    > I found the following article on the FAQ section of the HP3000-L list:
    >
    >
    >
    > Concurrent accessors when using database logging on the HP3000
    >
    >
    >
    >
    >
    > Due to limits in MPE's internal tables, the maximum number of processes that can share a log process -- which in this case means the maximum number of processes that can open a database with modify-access -- is 1140. Beware of this on limit on large systems.
    >
    >
    >
    > -- ChrisBartram - 18 May 2006
    >
    >
    >
    >
    >
    >
    >
    > My question: If I break-out the transactions from our heaviest web application (the heaviest one is from a separate database) into a separate db transaction log file (currently one log file shares a number of different database transactions), will this help reduce the number of problems with the above mentioned limitation?
    >
    >
    >
    > Heidi D. Wilker
    > Systems Analyst
    > Baltimore City Community College
    > 600 East Lombard Street Bard 301-G
    > Baltimore, MD 21202
    > Office: 410-986-3257
    > Fax: 410-986-3277
    > E-mail: hwilker@bccc.edu
    > http://www.bccc.edu
    >
    > "It is in our moments of decision, that shape our destiny"
    >
    >
    > * To join/leave the list, search archives, change list settings, *
    > * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
    >


  5. Re: Maximum user processes for logging

    > The limit is 1140 processes PER logid.

    unless you are on MPE/iX 7.5 where it was increased to 2851...

    see http://docs.hp.com/en/30216-90336/ch05s18.html

    Regards, Lars.

    * To join/leave the list, search archives, change list settings, *
    * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *


  6. Re: Maximum user processes for logging

    HP-3000 Systems Discussion wrote:
    >> The limit is 1140 processes PER logid.

    >
    > unless you are on MPE/iX 7.5 where it was increased to 2851...
    >
    > see http://docs.hp.com/en/30216-90336/ch05s18.html
    >
    > Regards, Lars.
    >


    Thanks for pointing that out. I just updated the FAQ as well.

    -Chris Bartram

    * To join/leave the list, search archives, change list settings, *
    * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *


+ Reply to Thread