VPCLASS 'cpu' not enough physical procs for affinity

Hi, I keep seeing this message "VPCLASS 'cpu' not enough physical procs for affinity" in the "online.log". We are running our application in a Sun V890 Server with 4CPU , 16GB RAM using "Informix Version 10.00.FC5" . Please advise if there any issues with configuration file. Find below the output of "uname -X", "onstat - " and the "onconfig" file, part of the online.log file. -bash-3.00$ uname -X System = SunOS Node = primesun-test Release = 5.10 KernelID = Generic_118833-24 Machine = sun4u BusType = <unknown> Serial = <unknown> Users = <unknown> OEM# = 0 Origin# = 1 NumCPU = 4 -bash-3.00$ onstat - IBM Informix Dynamic Server Version 10.00.FC5 -- On-Line -- Up 01:25:37 -- 8130560 Kbytes #************************************************************************** ## Licensed Material - Property Of IBM # # "Restricted Materials of IBM" # # IBM Informix Dynamic Server # (c) Copyright IBM Corporation 1996, 2005 All rights reserved. # # Title: onconfig.std # Description: IBM Informix Dynamic Server Configuration Parameters # #************************************************************************** # Root Dbspace Configuration ROOTNAME rootdbs # Root dbspace nameROOTPATH /dev/informix/rootdbs.d01 # Path for device containing root dbspace ROOTOFFSET 50 # Offset of root dbspace into device (Kbytes) ROOTSIZE 1000000 # Size of root dbspace (Kbytes) # Disk Mirroring Configuration Parameters MIRROR 0 # Mirroring flag (Yes = 1, No = 0) MIRRORPATH # Path for device containing mirrored root MIRROROFFSET 0 # Offset into mirrored device (Kbytes) # Physical Log Configuration PHYSDBS rootdbs # Location (dbspace) of physical log PHYSFILE 200000 # Physical log file size (Kbytes) # Logical Log Configuration LOGFILES 170 # Number of logical log files LOGSIZE 2000 # Logical log size (Kbytes)LOG_BACKUP_MODE MANUAL # Logical log backup mode (MANUAL, CONT) # Tablespace Tablespace Configuration in Root Dbspace TBLTBLFIRST 0 # First extent size (Kbytes) (0 = default) TBLTBLNEXT 0 # Next extent size (Kbytes) (0 = default) # Security # DBCREATE_PERMISSION: # By default any user can create a database. Uncomment DBCREATE_PERMISSON to # limit database creation to a specific user. Add a new DBCREATE_PERMISSION # line for each permitted user. #DBCREATE_PERMISSION informix # DB_LIBRARY_PATH: # When loading a (C or C++) shared object (for a UDR or UDT), IDS checks that # the user-specified path starts with one of the directory prefixes listed in # the comma-separated list of prefixes in DB_LIBRARY_PATH. The string # "$INFORMIXDIR/extend" must be included in DB_LIBRARY_PATH in order for # extensibility and IBM supplied blades to work correctly. # DB_LIBRARY_PATH $INFORMIXDIR/extend # IFX_EXTEND_ROLE: # 0 (or off) => Disable use of EXTEND role to control who can register # external routines. # 1 (or on) => Enable use of EXTEND role to control who can register # external routines. This is the default behaviour. # IFX_EXTEND_ROLE 1 # To control the usage of EXTEND role. # Diagnostics MSGPATH /export/home/informix/online.log # System message log file path CONSOLE /dev/console # System console message path # To automatically backup logical logs, edit alarmprogram.sh and set # BACKUPLOGS=Y ALARMPROGRAM /export/home/informix/etc/alarmprogram.sh # Alarm program path ALRM_ALL_EVENTS 0 # Triggers ALARMPROGRAM for any eventoccur TBLSPACE_STATS 1 # Maintain tblspace statistics # System Archive Tape Device #TAPEDEV /dev/null # Tape device path TAPEDEV /backup/Level0 # Log tape device path TAPEBLK 256 # Tape block size (Kbytes) TAPESIZE 60000000 # Maximum amount of data to put on tape (Kbytes) # Log Archive Tape Device LTAPEDEV /dev/null # Tape device path#LTAPEDEV /export/home/informix/level0 # Log tape device path LTAPEBLK 32 # Log tape block size (Kbytes) LTAPESIZE 10240 # Max amount of data to put on log tape (Kbytes) # Optical STAGEBLOB # Informix Dynamic Server staging area # System Configuration SERVERNUM 0 # Unique id corresponding to a OnLine instance DBSERVERNAME primesun_test # Name of default database server DBSERVERALIASES primesun_testtcp # List of alternate dbservernames NETTYPE ipcshm,1,100,CPU # Configure poll thread(s) for nettype NETTYPE tlitcp,1,200,NET # TCP/IP protocol for connection DEADLOCK_TIMEOUT 60 # Max time to wait of lock in distributed env. RESIDENT 0 # 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 vpsto one NOAGE 0 # Process aging AFF_SPROC 2 # Affinity start processor AFF_NPROCS 4 # Affinity number of processors # Shared Memory Parameters LOCKS 800000 # Maximum number of locks NUMAIOVPS 10 # Number of IO vps PHYSBUFF 64 # Physical log buffer size (Kbytes) LOGBUFF 64 # Logical log buffer size (Kbytes) CLEANERS 10 # Number of buffer cleaner processes SHMBASE 0x10A000000L # Shared memory base address SHMVIRTSIZE 1500000 # initial virtual shared memory segmentsize SHMADD 100000 # Size of new shared memory segments (Kbytes) EXTSHMADD 60000 # Size of new extension shared memory segments (Kbytes) SHMTOTAL 0 # Total shared memory (Kbytes). 0=>unlimited CKPTINTVL 300 # Check point interval (in sec) TXTIMEOUT 300 # Transaction timeout (in sec) STACKSIZE 64 # Stack size (Kbytes) # Dynamic Logging # DYNAMIC_LOGS: # 2 : server automatically add a new logical log when necessary. (ON) # 1 : notify DBA to add new logical logs when necessary. (ON) # 0 : cannot add logical log on the fly. (OFF) # # When dynamic logging is on, we can have higher values for LTXHWM/ LTXEHWM, # because the server can add new logical logs during long transaction rollback. # However, to limit the number of new logical logs being added, LTXHWM/ LTXEHWM# can be set to smaller values. # # If dynamic logging is off, LTXHWM/LTXEHWM need to be set to smaller values # to avoid long transaction rollback hanging the server due to lack of logical # log space, i.e. 50/60 or lower. # # In case of system configured with CDR, the difference between LTXHWM and # LTXEHWM should be atleast 30% so that we could minimize log overrun issue. DYNAMIC_LOGS 2 LTXHWM 70 LTXEHWM 80 # System Page Size # BUFFSIZE - OnLine no longer supports this configuration parameter. # To determine the page size used by OnLine on your platform # see the last line of output from the command, 'onstat - b'. # Recovery Variables@@NL

you could try: AFF_SPROC 0 # Affinity start processor Superboer.

On Jun 22, 11:26 am, Superboer <superbo...@t-online.de> wrote: > you could try: > > AFF_SPROC 0 # Affinity start processor> > Superboer. Will try and let you know... Thanks Dhaya

On Jun 22, 4:21 am, sdhaya <dhaya.sni...@gmail.com> wrote: > Hi, > > I keep seeing this message "VPCLASS 'cpu' not enough physical procs > for affinity" in the "online.log". We are running our application in a > Sun V890 Server with 4CPU , 16GB RAM using "Informix Version > 10.00.FC5" . > > Please advise if there any issues with configuration file. > > Find below the output of "uname -X", "onstat - " and the "onconfig" > file, part of the online.log file. Sun doesn't number it's CPUs sequentially and the CPU number for the first CPU may or may not be 0 or 1. There is a Sun utility that will give you the CPU #s of your CPUs (depends on what slots the CPU cards are in). Then you can select one of those for AFF_SPROC. Once it gets the number of the first CPU, IDS can determine the others to use. Probably on your system there is no CPU #2. Art S. Kagel

Art S. Kagel wrote: > On Jun 22, 4:21 am, sdhaya <dhaya.sni...@gmail.com> wrote: > >>Hi, >> >>I keep seeing this message "VPCLASS 'cpu' not enough physical procs >>for affinity" in the "online.log". We are running our application in a >>Sun V890 Server with 4CPU , 16GB RAM using "Informix Version >>10.00.FC5" . >> >>Please advise if there any issues with configuration file. >> >>Find below the output of "uname -X", "onstat - " and the "onconfig" >>file, part of the online.log file. > > > Sun doesn't number it's CPUs sequentially and the CPU number for the > first CPU may or may not be 0 or 1. There is a Sun utility that will > give you the CPU #s of your CPUs (depends on what slots the CPU cards > are in). Then you can select one of those for AFF_SPROC. Once it > gets the number of the first CPU, IDS can determine the others to > use. Probably on your system there is no CPU #2. > > Art S. Kagel > > psrinfo