Oninit cdi / Archive
Talk to an expert →

IDS w/ ADS 8.21 : Startup problem.

Posted in 1999

Topics: Performance & Tuning, Storage & Space Management, Server Administration, Transactions, Locking & Isolation, Logging & Checkpoints, Networking & sqlhosts Configuration

Maria Seagull — — source: Informix-list mailing list archive (1991-1998)

Hi, Here are the details of the problem we have , your attention and help is highly appreciated. Thanks. - Maria System : Informix server : IDS with ADS Version 8.21.UD4D1 Unix OS : HP release B.11.00 HP9000/V2200 Context: We were finetuning the engine shared memory, when we faced problems bringing up the server with a certain set of onconfig values(detailed below). Problem: Bringing up the server on-line with the following onconfig parameters: BUFFERS 60000 # Max. no. of shared buffers (4kb pages) SHMVIRTSIZE 345000 # initial virtual shared memorysegment size We were earlier able to bring it up with the following parameters: BUFFERS 50000 # Max. no. of shared buffers (4kb pages) SHMVIRTSIZE 305000 # initial virtual shared memorysegment size So in short we took some from virtual sh. mem and gave some to buffers (or so we thought ..:-) ) but the engine didn't seem to like it and failed to come up . Question: Why did it fail to come up? How to bring it up with increased buffers? Any ideas,hints,suggestions are welcome and would be appreciated. TIA. Relevant Details from the onconfig : (In case u need more details to "analyse this" , just let me know. Thanks ) # Shared Memory Parameters on onconfig file LOCKS 200000 # Maximum number of locks# this does not work BUFFERS 60000 # Maximum number of shared buffers (4 kb pages) BUFFERS 50000 # Maximum number of shared buffers (4 kb pages) NUMAIOVPS 2 # Number of IO vpsNUMFIFOVPS 2 # Number of FIFO vps #PHYSBUFF 32 # Physical log buffer size (Kbytes) #LOGBUFF 32 # Logical log buffer size (Kbytes) PHYSBUFF 64 # Physical log buffer size (Kbytes) LOGBUFF 64 # Logical log buffer size (Kbytes)LOGSMAX 110 # Maximum number of logical log files CLEANERS 32 # Number of buffercleaner processes #CLEANERS 64 # Number of buffer cleaner processes SHMBASE 0x0 # Shared memory base address#SHMBASE 0 # Shared memory base address SHMVIRTSIZE 250000 # initial virtual sharedmemory segment size #SHMVIRTSIZE 345000 # initial virtual shared memory segment size #SHMADD 16200 # Size of new shared memory segments (Kbytes) # cberner 09/11/1999 SHMADD 500 # Size of new sharedmemory segments (Kbytes) #SHMADD 16200 # Size of new shared memory segments (Kbytes) SHMTOTAL 0 # Total shared memory (Kbytes). 0=>unlimited #SHMTOTAL 1600000 # Total shared memory (Kbytes). 0=>unlimited CKPTINTVL 600 # Check point interval (in sec) LRUS 24 # Number of LRU queues#LRUS 32 # Number of LRU queues LRU_MAX_DIRTY 20 # LRU percent dirty begin cleaninglimit LRU_MIN_DIRTY 15 # LRU percent dirty end cleaninglimit LTXHWM 50 # Long transaction high water markpercentage LTXEHWM 60 # Long transaction high water mark (exclusive) TXTIMEOUT 300 # Transaction timeout (in sec) STACKSIZE 32 # Stack size (Kbytes) System Configuration SERVERNUM 1 # Unique id corresponding to a IDS ADinstance NETTYPE ipcshm,2,100,CPU # Override sqlhostsnettype parameters #NETTYPE ipcshm,2,100,NET # Override sqlhosts nettype parameters NETTYPE soctcp,2,200,NET # Override sqlhostsnettype parameters DEADLOCK_TIMEOUT 60 # Max time to wait of lock indistributed env. RESIDENT 1 # Forced residency flag (Yes = 1, No = 0) MULTIPROCESSOR 1 # 0 forsingle-processor, 1 for multi-processor NUMCPUVPS 2 # Number of user (cpu) vps SINGLE_CPU_VP 0 # If non-zero, limitnumber of cpu vps to one NOAGE 0 # Process aging AFF_SPROC 0 # Affinity start processor AFF_NPROCS 0 # Affinity number of processors DBSPACETEMP: # IDS AD equivalent of DBTEMP for SE. This is the list of dbspaces # that the IDS AD SQL Engine will use to create temp tables etc. # The list can be specified using various preset "sets" that are # ALL - all dbspaces can be used for temp files # TEMP - use only temporary dbspaces for temp files # NOTCRITICAL - use only non-critical dbspaces for temp files # Critical dbspaces are the rootdbspaces and dbspaces containing # log files. # The list can also be specified as an explicit list of dbspaces/dbslices # that exist when the IDS AD system is brought online. If not specified, # or if all dbspaces specified are invalid, various ad hoc queries will create # temporary files in /tmp instead. If a dbspaces in this list is # added to the system at a later point in time, it is automatically added # to the list of dbspaces that can be used for temp purposes. DBSPACETEMP NOTCRITICAL # Default temp dbspaces __________________________________________________ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com

↪ replying to Maria Seagull
David Williams — — source: Informix-list mailing list archive (1991-1998)

In article <7sfv9p$719$1@news.xmission.com>, Maria Seagull <maria_seagull@yahoo.com> writes > >Hi, >Here are the details of the problem we have , your >attention and help is highly appreciated. Thanks. >- Maria > >System : >Informix server : IDS with ADS Version 8.21.UD4D1 >Unix OS : HP release B.11.00 HP9000/V2200 > >Context: We were finetuning the engine shared memory, >when we faced problems >bringing up the server with a certain set of onconfig >values(detailed below). > >Problem: >Bringing up the server on-line with the following >onconfig parameters: >BUFFERS 60000 # Max. no. of shared buffers (4kb >pages) >SHMVIRTSIZE 345000 # initial virtual shared memory>segment size > >We were earlier able to bring it up with the following >parameters: >BUFFERS 50000 # Max. no. of shared buffers (4kb >pages) >SHMVIRTSIZE 305000 # initial virtual shared memory>segment size > >So in short we took some from virtual sh. mem and gave >some to buffers >(or so we thought ..:-) ) but the engine didn't seem >to like it and failed to come >up . > What errors do you get? Check kernel parameters allow enough shared memory segments to be created. Perhaps it needs that much virtual shared memory to start? start using oninit -v?? > > >Question: Why did it fail to come up? How to bring it >up with increased buffers? >Any ideas,hints,suggestions are welcome >and would be appreciated. TIA. > > > > >Relevant Details from the onconfig : >(In case u need more details to "analyse this" , just >let me know. Thanks ) > > > ># Shared Memory Parameters on onconfig file > > >LOCKS 200000 # Maximum number of locks># this does not work BUFFERS 60000 # >Maximum number of shared buffers (4 kb pages) >BUFFERS 50000 # Maximum number of shared >buffers (4 kb pages) > >NUMAIOVPS 2 # Number of IO vps>NUMFIFOVPS 2 # Number of FIFO vps >#PHYSBUFF 32 # Physical log buffer size (Kbytes) >#LOGBUFF 32 # Logical log buffer size (Kbytes) >PHYSBUFF 64 # Physical log buffer size (Kbytes) >LOGBUFF 64 # Logical log buffer size (Kbytes)>LOGSMAX 110 # Maximum number of logical log >files >CLEANERS 32 # Number of buffer>cleaner processes >#CLEANERS 64 # Number of buffer >cleaner processes >SHMBASE 0x0 # Shared memory base address>#SHMBASE 0 # Shared memory base address > > >SHMVIRTSIZE 250000 # initial virtual shared>memory segment size >#SHMVIRTSIZE 345000 # initial virtual shared >memory segment size > >#SHMADD 16200 # Size of new shared >memory segments (Kbytes) ># cberner 09/11/1999 >SHMADD 500 # Size of new shared>memory segments (Kbytes) >#SHMADD 16200 # Size of new shared >memory segments (Kbytes) >SHMTOTAL 0 # Total shared memory >(Kbytes). 0=>unlimited >#SHMTOTAL 1600000 # Total shared >memory (Kbytes). 0=>unlimited >CKPTINTVL 600 # Check point interval >(in sec) >LRUS 24 # Number of LRU queues>#LRUS 32 # Number of LRU queues >LRU_MAX_DIRTY 20 # LRU percent dirty begin cleaning>limit >LRU_MIN_DIRTY 15 # LRU percent dirty end cleaning>limit >LTXHWM 50 # Long transaction high water mark>percentage >LTXEHWM 60 # Long transaction high water mark >(exclusive) >TXTIMEOUT 300 # Transaction timeout (in sec) >STACKSIZE 32 # Stack size (Kbytes)> > >System Configuration > >SERVERNUM 1 # Unique id corresponding to a IDS AD>instance > > >NETTYPE ipcshm,2,100,CPU # Override sqlhosts>nettype parameters >#NETTYPE ipcshm,2,100,NET # Override sqlhosts >nettype parameters >NETTYPE soctcp,2,200,NET # Override sqlhosts>nettype parameters >DEADLOCK_TIMEOUT 60 # Max time to wait of lock in>distributed env. >RESIDENT 1 # Forced residency flag (Yes = 1, No = 0) > >MULTIPROCESSOR 1 # 0 for>single-processor, 1 for multi-processor >NUMCPUVPS 2 # Number of user (cpu) vps >SINGLE_CPU_VP 0 # If non-zero, limit>number of cpu vps to one > >NOAGE 0 # Process aging >AFF_SPROC 0 # Affinity start processor >AFF_NPROCS 0 # Affinity number of processors> > > > > DBSPACETEMP: ># IDS AD equivalent of DBTEMP for SE. This is the list >of dbspaces ># that the IDS AD SQL Engine will use to create temp >tables etc. ># The list can be specified using various preset >"sets" that are ># ALL - all dbspaces can be used for temp files ># TEMP - use only temporary dbspaces for temp files ># NOTCRITICAL - use only non-critical dbspaces for >temp files ># Critical dbspaces are the rootdbspaces and >dbspaces containing ># log files. ># The list can also be specified as an explicit list >of dbspaces/dbslices ># that exist when the IDS AD system is brought online. > If not specified, ># or if all dbspaces specified are invalid, various ad >hoc queries will create ># temporary files in /tmp instead. If a dbspaces in >this list is ># added to the system at a later point in time, it is >automatically added ># to the list of dbspaces that can be used for temp >purposes. > >DBSPACETEMP NOTCRITICAL # Default temp dbspaces> >__________________________________________________ >Do You Yahoo!? >Bid and sell for free at http://auctions.yahoo.com -- David Williams

↪ replying to Maria Seagull
Tim Schaefer — — source: Informix-list mailing list archive (1991-1998)

Maria, How much memory do your computer(s) REALLY have? It may be that you are not allocating the right amount of memory. Keep in mind your BUFFERS affects the total memory. How many coservers do you have? I didn't see the COSERVER references at all in your ONCONFIG, so it's hard to tell what you're doing. So in other words, how many physical computers are actually using this instance?? Is it just one computer with virtual coservers? If you are using more than one physical computer, did you propagate your ONCONFIG from the master coserver to all the other computers if you have other physical coservers connected, or are you NFS-mounting the ONCONFIG?? ( Bad idea but they actually teach this in training! ) Tim Maria Seagull wrote: > > Hi, > Here are the details of the problem we have , your > attention and help is highly appreciated. Thanks. > - Maria > > System : > Informix server : IDS with ADS Version 8.21.UD4D1 > Unix OS : HP release B.11.00 HP9000/V2200 > > Context: We were finetuning the engine shared memory, > when we faced problems > bringing up the server with a certain set of onconfig > values(detailed below). > > Problem: > Bringing up the server on-line with the following > onconfig parameters: > BUFFERS 60000 # Max. no. of shared buffers (4kb > pages) > SHMVIRTSIZE 345000 # initial virtual shared memory> segment size > > We were earlier able to bring it up with the following > parameters: > BUFFERS 50000 # Max. no. of shared buffers (4kb > pages) > SHMVIRTSIZE 305000 # initial virtual shared memory> segment size > > So in short we took some from virtual sh. mem and gave > some to buffers > (or so we thought ..:-) ) but the engine didn't seem > to like it and failed to come > up . > > > Question: Why did it fail to come up? How to bring it > up with increased buffers? > Any ideas,hints,suggestions are welcome > and would be appreciated. TIA. > > Relevant Details from the onconfig : > (In case u need more details to "analyse this" , just > let me know. Thanks ) > > # Shared Memory Parameters on onconfig file > > LOCKS 200000 # Maximum number of locks> # this does not work BUFFERS 60000 # > Maximum number of shared buffers (4 kb pages) > BUFFERS 50000 # Maximum number of shared > buffers (4 kb pages) > > NUMAIOVPS 2 # Number of IO vps> NUMFIFOVPS 2 # Number of FIFO vps > #PHYSBUFF 32 # Physical log buffer size (Kbytes) > #LOGBUFF 32 # Logical log buffer size (Kbytes) > PHYSBUFF 64 # Physical log buffer size (Kbytes) > LOGBUFF 64 # Logical log buffer size (Kbytes)> LOGSMAX 110 # Maximum number of logical log > files > CLEANERS 32 # Number of buffer> cleaner processes > #CLEANERS 64 # Number of buffer > cleaner processes > SHMBASE 0x0 # Shared memory base address> #SHMBASE 0 # Shared memory base address > > SHMVIRTSIZE 250000 # initial virtual shared> memory segment size > #SHMVIRTSIZE 345000 # initial virtual shared > memory segment size > > #SHMADD 16200 # Size of new shared > memory segments (Kbytes) > # cberner 09/11/1999 > SHMADD 500 # Size of new shared> memory segments (Kbytes) > #SHMADD 16200 # Size of new shared > memory segments (Kbytes) > SHMTOTAL 0 # Total shared memory > (Kbytes). 0=>unlimited > #SHMTOTAL 1600000 # Total shared > memory (Kbytes). 0=>unlimited > CKPTINTVL 600 # Check point interval > (in sec) > LRUS 24 # Number of LRU queues> #LRUS 32 # Number of LRU queues > LRU_MAX_DIRTY 20 # LRU percent dirty begin cleaning> limit > LRU_MIN_DIRTY 15 # LRU percent dirty end cleaning> limit > LTXHWM 50 # Long transaction high water mark> percentage > LTXEHWM 60 # Long transaction high water mark > (exclusive) > TXTIMEOUT 300 # Transaction timeout (in sec) > STACKSIZE 32 # Stack size (Kbytes)> > System Configuration > > SERVERNUM 1 # Unique id corresponding to a IDS AD> instance > > NETTYPE ipcshm,2,100,CPU # Override sqlhosts> nettype parameters > #NETTYPE ipcshm,2,100,NET # Override sqlhosts > nettype parameters > NETTYPE soctcp,2,200,NET # Override sqlhosts> nettype parameters > DEADLOCK_TIMEOUT 60 # Max time to wait of lock in> distributed env. > RESIDENT 1 # Forced residency flag (Yes = 1, No = 0) > > MULTIPROCESSOR 1 # 0 for> single-processor, 1 for multi-processor > NUMCPUVPS 2 # Number of user (cpu) vps > SINGLE_CPU_VP 0 # If non-zero, limit> number of cpu vps to one > > NOAGE 0 # Process aging > AFF_SPROC 0 # Affinity start processor > AFF_NPROCS 0 # Affinity number of processors> > DBSPACETEMP: > # IDS AD equivalent of DBTEMP for SE. This is the list > of dbspaces > # that the IDS AD SQL Engine will use to create temp > tables etc. > # The list can be specified using various preset > "sets" that are > # ALL - all dbspaces can be used for temp files > # TEMP - use only temporary dbspaces for temp files > # NOTCRITICAL - use only non-critical dbspaces for > temp files > # Critical dbspaces are the rootdbspaces and > dbspaces containing > # log files. > # The list can also be specified as an explicit list > of dbspaces/dbslices > # that exist when the IDS AD system is brought online. > If not specified, > # or if all dbspaces specified are invalid, various ad > hoc queries will create > # temporary files in /tmp instead. If a dbspaces in > this list is > # added to the system at a later point in time, it is > automatically added > # to the list of dbspaces that can be used for temp > purposes. > > DBSPACETEMP NOTCRITICAL # Default temp dbspaces> > __________________________________________________ > Do You Yahoo!? > Bid and sell for free at http://auctions.yahoo.com -- . .- .-- .--- .---- Tim Schaefer .----- tschaefe@bellsouth.net .---- http://www.inxutil.com .--- http://www.datad.com .-- .- .

Glossary