Update stats...running slow

IDS 7.30 UC2 on SOlaris 2.5.1 Suddenly my update statistics start running slow. Nothing has changed on box. Before it used to take 2 hrs, now it's taking 8 hrs. It's a simple update statistics medium command. Following is my onconfig file. #************************************************************************** # # INFORMIX SOFTWARE, INC. # # Title: onconfig.std # Description: INFORMIX-OnLine Configuration Parameters # #************************************************************************** # Root Dbspace Configuration ROOTNAME sopp1root # Root dbspace name ROOTPATH /dbsopp1_01/p1/system/sopp1root # Path for device containing root dbspace ROOTOFFSET 0 # Offset of root dbspace into device (Kbytes) ROOTSIZE 200000 # 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 sopp1phys # Location (dbspace) of physical log PHYSFILE 198894 # Physical log file size (Kbytes) # Logical Log Configuration LOGFILES 40 # Number of logical log files LOGSIZE 4096 # Logical log size (Kbytes) # Diagnostics MSGPATH /opt/ifmx/sopp1/logs/messages/sopp1msgfile # System message log file path CONSOLE /opt/ifmx/sopp1/logs/console/sopp1confile # System console message path ALARMPROGRAM /opt/ifmx/sopp1/admin/bar/alarm.sh # Alarm program path # System Archive Tape Device TAPEDEV /dev/tapedev # Tape device path#TAPEDEV /dev/null # Tape device path TAPEBLK 32 # Tape block size (Kbytes) TAPESIZE 20000000 # Maximum amount of data to put on tape (Kbytes) # Log Archive Tape Device LTAPEDEV /dev/tapedev # Log tape device path#LTAPEDEV /dev/null # Log tape device path LTAPEBLK 32 # Log tape block size (Kbytes) LTAPESIZE 20000000 # Max amount of data to put on log tape (Kbytes) # Optical STAGEBLOB # INFORMIX-OnLine/Optical staging area # System Configuration SERVERNUM 1 # Unique id corresponding to a OnLineinstance DBSERVERNAME sopp1 # Name of default database server DBSERVERALIASES sopp1_tcp # List of alternate dbservernames DEADLOCK_TIMEOUT 60 # Max time to wait of lock indistributed env. RESIDENT 1 # Forced residency flag (Yes = 1, No = 0) MULTIPROCESSOR 1 # 0 for single-processor, 1 formulti-processor NUMCPUVPS 8 # Number of user (cpu) vps SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vpsto one NOAGE 1 # Process aging AFF_SPROC 4 # Affinity start processor AFF_NPROCS 8 # Affinity number of processors # Shared Memory Parameters LOCKS 40000 # Maximum number of locks#BUFFERS 20000 # Maximum number of shared buffers - DSS BUFFERS 425000 # Maximum number of shared buffers -NORMAL NUMAIOVPS 18 # Number of IO vps PHYSBUFF 32 # Physical log buffer size (Kbytes) LOGBUFF 32 # Logical log buffer size (Kbytes)LOGSMAX 100 # Maximum number of logical log files CLEANERS 10 # Number of buffer cleaner processes (1/drive) SHMBASE 0xa000000 # Shared memory base address#SHMVIRTSIZE 2100000 # initial virtual shared memory segment size - DSS SHMVIRTSIZE 600000 # initial virtual shared memory segmentsize - NORMAL SHMADD 16384 # Size of new shared memory segments (Kbytes) SHMTOTAL 0 # Total shared memory (Kbytes). 0=>unlimited#CKPTINTVL 1800 # Check point interval (in sec) CKPTINTVL 300 # Check point interval (in sec) LRUS 10 # Number of LRU queues LRU_MAX_DIRTY 70 # LRU percent dirty begin cleaninglimit LRU_MIN_DIRTY 50 # LRU percent dirty end cleaning limit LTXHWM 45 # Long transaction high water markpercentage LTXEHWM 50 # Long transaction high water mark (exclusive) TXTIMEOUT 0x12c # Transaction timeout (in sec) STACKSIZE 32 # Stack size (Kbytes) # To determine the page size used by OnLine on your platform # see the last line of output from the command, 'onstat -b'. # Recovery Variables # OFF_RECVRY_THREADS: # Number of parallel worker threads during fast recovery or an offline restore. # ON_RECVRY_THREADS: # Number of parallel worker threads during an online restore. OFF_RECVRY_THREADS 12 # Default number of offline workerthreads ON_RECVRY_THREADS 12 # Default number of online workerthreads # Data Replication Variables # DRAUTO: 0 manual, 1 retain type, 2 reverse type DRAUTO 0 # DR automatic switchover DRINTERVAL 30 # DR max time between DR buffer flushes (in sec) DRTIMEOUT 30 # DR network timeout (in sec) DRLOSTFOUND /opt/ifmx/723UC4/etc/dr.lostfound # DR lost+found filepath # Read Ahead Variables RA_PAGES 128 # Number of pages to attempt to readahead RA_THRESHOLD 120 # Number of pages left before nextgroup # DBSPACETEMP: # OnLine equivalent of DBTEMP for SE. This is the list of dbspaces # that the OnLine SQL Engine will use to create temp tables etc. # If specified it must be a colon separated list of dbspaces that exist # when the OnLine 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. DBSPACETEMP sopp1temp_01:sopp1temp_02:sopp1temp_03:sopp1temp_04:sopp1temp_05:sopp1temp_06:sopp1temp_07:sopp1temp_08:sopp1temp_09:sopp1temp_10:sopp1temp_11:sopp1temp_12:sopp1temp_13 # Default temp dbspaces # DUMP*: # The following parameters control the type of diagnostics information which # is preserved when an unanticipated error condition (assertion failure) occurs # during OnLine operations. # For DUMPSHMEM, DUMPGCORE and DUMPCORE 1 means Yes, 0 means No. #DUMPDIR /dev/null # Preserve diagnostics in this directory DUMPDIR /tmp # Preserve diagnostics in thisdirectory # DUMPSHMEM 1 # Dump a copy of shared memory DUMPSHMEM 0 # Dump a copy of shared memory @@NL@

Are you using the High performance loader? There is a bug that is newly fixed (don't know which versions it will be fixed in or its number) where HPL sets a flag that is in in express moed (if it is indeed in express mode) and never unsets it. What this means is that if you do more loads with deluxe or express mode, it will still not use empty pages (it's supposed to in deluxe). This results in an interesting situation where you keep grabbing extents and there are a bunch of empty pages. The result is that even though the amount of data in your table may not change, your queries will become slower and slower whenever they have to do a sequential scan (update stats, index builds...). Of course, if that isn't your situation, then it is just an FYI for others. sanjeev sagar (sanjeevsagar@yahoo.com) wrote: : IDS 7.30 UC2 on SOlaris 2.5.1 : Suddenly my update statistics start running slow. Nothing has changed : on box. Before it used to take 2 hrs, now it's taking 8 hrs. It's a : simple update statistics medium command. : Following is my onconfig file. [SNIP] : Thanks for the attention. : Sanjeev K. Sagar : _________________________________________________________ : Do You Yahoo!? : Get your free @yahoo.com address at http://mail.yahoo.com -- Rob Wilson rwilson@ntsource.com

where, and what version does it exist in. Rob Wilson <rwilson@ntsource.com> wrote in message news:0WoV2.189$wq.1012@newsfeed.slurp.net... > Are you using the High performance loader? There is a bug that is newly > fixed (don't know which versions it will be fixed in or its number) where HPL > sets a flag that is in in express moed (if it is indeed in express mode) and > never unsets it. What this means is that if you do more loads with deluxe > or express mode, it will still not use empty pages (it's supposed to in deluxe). > This results in an interesting situation where you keep grabbing extents and > there are a bunch of empty pages. The result is that even though the amount > of data in your table may not change, your queries will become slower and > slower whenever they have to do a sequential scan (update stats, index > builds...). > > Of course, if that isn't your situation, then it is just an FYI for others. > > > sanjeev sagar (sanjeevsagar@yahoo.com) wrote: > > > > : IDS 7.30 UC2 on SOlaris 2.5.1 > > : Suddenly my update statistics start running slow. Nothing has changed > : on box. Before it used to take 2 hrs, now it's taking 8 hrs. It's a > : simple update statistics medium command. > > : Following is my onconfig file. > > [SNIP] > > : Thanks for the attention. > > : Sanjeev K. Sagar > : _________________________________________________________ > : Do You Yahoo!? > : Get your free @yahoo.com address at http://mail.yahoo.com > > > -- > Rob Wilson > rwilson@ntsource.com >

Where does this bug exist, what version is it fixed in. We are planning to move about 200 or so gig of data using a series of opload commands and I would like to know what the proble is and how can I fix it. Carlos Bolden Harrahs Entertainment; cbolden@harrahs.com cbolden1@midsouth.rr.com Rob Wilson <rwilson@ntsource.com> wrote in message news:0WoV2.189$wq.1012@newsfeed.slurp.net... > Are you using the High performance loader? There is a bug that is newly > fixed (don't know which versions it will be fixed in or its number) where HPL > sets a flag that is in in express moed (if it is indeed in express mode) and > never unsets it. What this means is that if you do more loads with deluxe > or express mode, it will still not use empty pages (it's supposed to in deluxe). > This results in an interesting situation where you keep grabbing extents and > there are a bunch of empty pages. The result is that even though the amount > of data in your table may not change, your queries will become slower and > slower whenever they have to do a sequential scan (update stats, index > builds...). > > Of course, if that isn't your situation, then it is just an FYI for others. > > > sanjeev sagar (sanjeevsagar@yahoo.com) wrote: > > > > : IDS 7.30 UC2 on SOlaris 2.5.1 > > : Suddenly my update statistics start running slow. Nothing has changed > : on box. Before it used to take 2 hrs, now it's taking 8 hrs. It's a > : simple update statistics medium command. > > : Following is my onconfig file. > > [SNIP] > > : Thanks for the attention. > > : Sanjeev K. Sagar > : _________________________________________________________ > : Do You Yahoo!? > : Get your free @yahoo.com address at http://mail.yahoo.com > > > -- > Rob Wilson > rwilson@ntsource.com >