UNIX-Box slow down while execute stored procedure

Ask a Question related to Informix, Design and Development.

  1. #1

    Default UNIX-Box slow down while execute stored procedure

    Hi,

    Sorry for my "special english".

    We are on a DGUX-Box with IDS 7.31 ( 4 P3/700 / 2 GB Mem )

    We have a problem with a stored procedure (ca. 1500 lines) for
    reportings.
    The short version of procedure:

    CREATE TEMP TABLE xxx ... WITH NO LOG FRAGMENT BY ROUND ROBIN;
    (testet with 2 and 4 tempdbs on different dics)
    INSERT INTO xxx .... SELECT FROM second DATABASE via SYNONYMS; (ca 5
    000 rows per month)
    ca. 20x UPDATE xxx SELECT FROM second DATABASE via SYNONYMS....
    FOREACH SELECT RETURN ...

    The procedure runs, when a user starts an Report (via Crystal Reports
    over "onsoctcp").

    Informix is configured for an OLTP - Environment (onconfig below)
    there are up to 100 (OLTP)Users. If the Procedure runs for up to 8
    month of data (up to 40 000 rows) there is no problem (5-8 min).
    when report starts e.g. for 9 Month AND when it is the "normal
    worktime" the unix-System "freeze" up to an hour. If then the
    procedure returns the results to Crytal Reports , Unix is comming up
    to normal reaction. If the procedure runs in evening time (up to 30
    OLTP Users) the procedure produce syscalls, disk i/o esp. on the
    tempdbs-Disks but there is no problem with the OLTP-Users and
    unix-Sessions.

    So it is hard to find out what the problem is ...
    The Unix-System is at the "problem time" too slow to start everything
    like onstats, nsar etc.

    We playing with PDQ:
    MAX_PDQPRIORITY 100, 50, 1; SET PDQPRIORITY 20, 3, 0 (in the
    procedure)
    - nothings helps.

    All ideas are more than welcome.

    Thanks in advance for your help on
    the subject.

    Kai

    onconfig:

    Configuration File: /usr/local/informix/etc/onconfig
    # Root Dbspace Configuration
    ROOTNAME rootdbs # Root dbspace name
    ROOTPATH /usr/opt/informix/dbspaces/dbs_root #ntaining root
    dbspace
    ROOTOFFSET 100 # Offset of root dbspace into device
    (Kbytes)
    ROOTSIZE 245000 # 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 logdbs # Location (dbspace) of physical log
    PHYSFILE 20000 # Physical log file size (Kbytes)
    # Logical Log Configuration
    LOGFILES 64 # Number of logical log files
    LOGSIZE 8000 # Logical log size (Kbytes)
    # Diagnostics
    MSGPATH /usr/local/informix/online.log # System message log
    file path
    CONSOLE /dev/console # System console message path
    ALARMPROGRAM /usr/opt/informix/lfb/alarm # Alarm program path
    SYSALARMPROGRAM /usr/local/informix/etc/evidence.sh # System Alarm
    program path
    TBLSPACE_STATS 1
    # System Archive Tape Device
    ###TAPEDEV /dev/null
    TAPEDEV /usr/opt/informix/dbspaces/tape_arc
    TAPEBLK 256 # Tape block size (Kbytes)
    TAPESIZE 20000000 # Maximum amount of data to put on
    tape (Kbytes)
    # Log Archive Tape Device
    LTAPEDEV /dev/null # Log tape device path
    LTAPEBLK 256 # Log tape block size (Kbytes)
    LTAPESIZE 20000000 # Max amount of data to put on log
    tape (Kbytes)
    # Optical
    STAGEBLOB # Informix Dynamic Server/Optical
    staging area
    # System Configuration
    SERVERNUM 0 # Unique id
    DBSERVERNAME xxxxx # Name of default database server
    DBSERVERALIASES xxxxxx # List of alternate dbservernames
    NETTYPE ipcshm,3,199,CPU # Configure poll thread(s) for
    nettype
    NETTYPE tlitcp,3,199,NET # Configure poll thread(s) for
    nettype
    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 3 # 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
    # Shared Memory Parameters
    LOCKS 2560000 # Maximum number of locks
    BUFFERS 350000 # Maximum number of shared buffers
    NUMAIOVPS 6 # Number of IO vps
    PHYSBUFF 512 # Physical log buffer size (Kbytes)
    LOGBUFF 512 # Logical log buffer size (Kbytes)
    LOGSMAX 64 # Maximum number of logical log files
    CLEANERS 127 # Number of buffer cleaner processes
    SHMBASE 0x20000000 # Shared memory base address
    SHMVIRTSIZE 131072 # initial virtual shared memory
    segment size
    SHMADD 24576 # Size of new shared memory segments
    (Kbytes)
    SHMTOTAL 0 # Total shared memory (Kbytes).
    0=>unlimited
    CKPTINTVL 1800 # Check point interval (in sec)
    LRUS 127 # Number of LRU queues
    LRU_MAX_DIRTY 1 # LRU percent dirty begin cleaning
    limit
    LRU_MIN_DIRTY 0 # LRU percent dirty end cleaning limit
    LTXHWM 50 # Long transaction high water mark
    percentage
    LTXEHWM 60 # Long transaction high water mark
    (exclusive)
    TXTIMEOUT 0x12c # Transaction timeout (in sec)
    STACKSIZE 64 # Stack size (Kbytes)
    # System Page Size
    # BUFFSIZE - Dynamic Server no longer supports this configuration
    parameter.
    # To determine the page size used by Dynamic Server 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 10 # Default number of offline worker
    threads
    ON_RECVRY_THREADS 1 # Default number of online worker
    threads
    # 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 /usr/local/informix/etc/dr.lostfound # DR lost+found
    # CDR Variables
    CDR_LOGBUFFERS 2048 # size of log reading buffer pool
    (Kbytes)
    CDR_EVALTHREADS 1,2 # evaluator threads
    (per-cpu-vp,additional)
    CDR_DSLOCKWAIT 5 # DS lockwait timeout (seconds)
    CDR_QUEUEMEM 4096 # Maximum amount of memory for any CDR
    queue (Kbytes)
    CDR_LOGDELTA 30 # % of log space allowed in queue
    memory
    CDR_NUMCONNECT 16 # Expected connections per server
    CDR_NIFRETRY 300 # Connection retry (seconds)
    CDR_NIFCOMPRESS 0 # Link level compression (-1 never, 0
    none, 9 max)
    # Backup/Restore variables
    BAR_ACT_LOG /tmp/bar_act.log
    BAR_MAX_BACKUP 0
    BAR_RETRY 1
    BAR_NB_XPORT_COUNT 10
    BAR_XFER_BUF_SIZE 31
    # Informix Storage Manager variables
    ISM_DATA_POOL ISMData # If the data pool name is changed, be
    sure to
    # update $INFORMIXDIR/bin/onbar. Change to
    # ism_catalog -create_bootstrap -pool <new name>
    ISM_LOG_POOL ISMLogs
    # Read Ahead Variables
    RA_PAGES 16 # Number of pages to attempt to read
    ahead
    RA_THRESHOLD 8 # Number of pages left before next
    group
    # DBSPACETEMP:
    # Dynamic Server equivalent of DBTEMP for SE. This is the list of
    dbspaces
    # that the Dynamic Server SQL Engine will use to create temp tables
    etc.
    # If specified it must be a colon separated list of dbspaces that
    exist
    # when the Dynamic Server 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 tmpdbs0,tmpdbs1,tmpdbs2,tmpdbs3 #
    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 Dynamic Server operations.
    # For DUMPSHMEM, DUMPGCORE and DUMPCORE 1 means Yes, 0 means No.
    DUMPDIR /usr/local/informix/tmp # this directory
    DUMPSHMEM 0 # Dump a copy of shared memory
    DUMPGCORE 0 # Dump a core image using 'gcore'
    DUMPCORE 0 # Dump a core image (Warning:this
    aborts Dynamic Server)
    DUMPCNT 1 # Number of shared memory or gcore
    dumps for
    # a single user's session
    FILLFACTOR 90 # Fill factor for building indexes
    # method for Dynamic Server to use when determining current time
    USEOSTIME 0 # 0: use internal time(fast), 1: get
    time from OS(slow)
    # Parallel Database Queries (pdq)
    MAX_PDQPRIORITY 50 # Maximum allowed pdqpriority
    DS_MAX_QUERIES 256 # Maximum number of decision support
    queries
    DS_TOTAL_MEMORY 32768 # Decision support memory (Kbytes)
    DS_MAX_SCANS 1048576 # Maximum number of decision support
    scans
    DATASKIP off # List of dbspaces to skip
    # OPTCOMPIND
    # 0 => Nested loop joins will be preferred (where
    # possible) over sortmerge joins and hash joins.
    # 1 => If the transaction isolation mode is not
    # "repeatable read", optimizer behaves as in (2)
    # below. Otherwise it behaves as in (0) above.
    # 2 => Use costs regardless of the transaction isolation
    # mode. Nested loop joins are not necessarily
    # preferred. Optimizer bases its decision purely
    # on costs.
    OPTCOMPIND 0 # To hint the optimizer
    ONDBSPACEDOWN 1 # Dbspace down option: 0 = CONTINUE, 1
    = ABORT, 2 = WAIT
    LBU_PRESERVE 1 # Preserve last log for log backup
    OPCACHEMAX 0 # Maximum optical cache size (Kbytes)
    # HETERO_COMMIT (Gateway participation in distributed transactions)
    # 1 => Heterogeneous Commit is enabled
    # 0 (or any other value) => Heterogeneous Commit is disabled
    HETERO_COMMIT 0
    # Optimization goal: -1 = ALL_ROWS(Default), 0 = FIRST_ROWS
    OPT_GOAL -1
    # Optimizer DIRECTIVES ON (1/Default) or OFF (0)
    DIRECTIVES 1
    # Status of restartable restore
    RESTARTABLE_RESTORE on
    Kai Guest

  2. Similar Questions and Discussions

    1. execute stored procedure
      Does anybody know how I can execute one of the system stored procedures from master database. for example this is throwing error: <cfquery...
    2. Execute permission denied on 'stored procedure' dbo
      How to solve the problem from the above topic. I can execute the stored procedure through the web service. I am using Integrated Security connection...
    3. Problem with execute to make a stored procedure
      I have to maintain a piece of code. One of the things that is done is a create procedure: CREATE PROCEDURE PROC_22_ RETURNS(IEXTENSION...
    4. Cannot execute dynamic query in stored procedure
      Hi, I'm using ADO.NET to execute a stored proc. The stored proc contains a dynamic sql which will build the INSERT or UPDATE statement for...
    5. How can I execute a stored procedure in .net?
      Hello all, Is there anyone who can tell me how to execute a stored procedure in .net. More detailed, I want to pass some parameters to the...
  3. #2

    Default RE: UNIX-Box slow down while execute stored procedure


    Start with ...

    When you run the procedure from dbaccess on the server how long does it
    take?
    Do you have the explain plan for the sqls in the procedure? (set explain on;
    update statistics for your_procname;)

    MW
    > -----Original Message-----
    > From: [email]owner-informix-list@iiug.org[/email]
    > [mailto:owner-informix-list@iiug.org]On Behalf Of Kai
    > Sent: Tuesday, 21 October 2003 11:15 a.m.
    > To: [email]informix-list@iiug.org[/email]
    > Subject: UNIX-Box slow down while execute stored procedure
    >
    >
    > Hi,
    >
    > Sorry for my "special english".
    >
    > We are on a DGUX-Box with IDS 7.31 ( 4 P3/700 / 2 GB Mem )
    >
    > We have a problem with a stored procedure (ca. 1500 lines) for
    > reportings.
    > The short version of procedure:
    >
    > CREATE TEMP TABLE xxx ... WITH NO LOG FRAGMENT BY ROUND ROBIN;
    > (testet with 2 and 4 tempdbs on different dics)
    > INSERT INTO xxx .... SELECT FROM second DATABASE via SYNONYMS; (ca 5
    > 000 rows per month)
    > ca. 20x UPDATE xxx SELECT FROM second DATABASE via SYNONYMS....
    > FOREACH SELECT RETURN ...
    >
    > The procedure runs, when a user starts an Report (via Crystal Reports
    > over "onsoctcp").
    >
    > Informix is configured for an OLTP - Environment (onconfig below)
    > there are up to 100 (OLTP)Users. If the Procedure runs for up to 8
    > month of data (up to 40 000 rows) there is no problem (5-8 min).
    > when report starts e.g. for 9 Month AND when it is the "normal
    > worktime" the unix-System "freeze" up to an hour. If then the
    > procedure returns the results to Crytal Reports , Unix is comming up
    > to normal reaction. If the procedure runs in evening time (up to 30
    > OLTP Users) the procedure produce syscalls, disk i/o esp. on the
    > tempdbs-Disks but there is no problem with the OLTP-Users and
    > unix-Sessions.
    >
    > So it is hard to find out what the problem is ...
    > The Unix-System is at the "problem time" too slow to start everything
    > like onstats, nsar etc.
    >
    > We playing with PDQ:
    > MAX_PDQPRIORITY 100, 50, 1; SET PDQPRIORITY 20, 3, 0 (in the
    > procedure)
    > - nothings helps.
    >
    > All ideas are more than welcome.
    >
    > Thanks in advance for your help on
    > the subject.
    >
    > Kai
    >
    > onconfig:
    >
    > Configuration File: /usr/local/informix/etc/onconfig
    > # Root Dbspace Configuration
    > ROOTNAME rootdbs # Root dbspace name
    > ROOTPATH /usr/opt/informix/dbspaces/dbs_root #ntaining root
    > dbspace
    > ROOTOFFSET 100 # Offset of root dbspace into device
    > (Kbytes)
    > ROOTSIZE 245000 # 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 logdbs # Location (dbspace) of physical log
    > PHYSFILE 20000 # Physical log file size (Kbytes)
    > # Logical Log Configuration
    > LOGFILES 64 # Number of logical log files
    > LOGSIZE 8000 # Logical log size (Kbytes)
    > # Diagnostics
    > MSGPATH /usr/local/informix/online.log # System message log
    > file path
    > CONSOLE /dev/console # System console message path
    > ALARMPROGRAM /usr/opt/informix/lfb/alarm # Alarm program path
    > SYSALARMPROGRAM /usr/local/informix/etc/evidence.sh # System Alarm
    > program path
    > TBLSPACE_STATS 1
    > # System Archive Tape Device
    > ###TAPEDEV /dev/null
    > TAPEDEV /usr/opt/informix/dbspaces/tape_arc
    > TAPEBLK 256 # Tape block size (Kbytes)
    > TAPESIZE 20000000 # Maximum amount of data to put on
    > tape (Kbytes)
    > # Log Archive Tape Device
    > LTAPEDEV /dev/null # Log tape device path
    > LTAPEBLK 256 # Log tape block size (Kbytes)
    > LTAPESIZE 20000000 # Max amount of data to put on log
    > tape (Kbytes)
    > # Optical
    > STAGEBLOB # Informix Dynamic Server/Optical
    > staging area
    > # System Configuration
    > SERVERNUM 0 # Unique id
    > DBSERVERNAME xxxxx # Name of default database server
    > DBSERVERALIASES xxxxxx # List of alternate dbservernames
    > NETTYPE ipcshm,3,199,CPU # Configure poll thread(s) for
    > nettype
    > NETTYPE tlitcp,3,199,NET # Configure poll thread(s) for
    > nettype
    > 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 3 # 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
    > # Shared Memory Parameters
    > LOCKS 2560000 # Maximum number of locks
    > BUFFERS 350000 # Maximum number of shared buffers
    > NUMAIOVPS 6 # Number of IO vps
    > PHYSBUFF 512 # Physical log buffer size (Kbytes)
    > LOGBUFF 512 # Logical log buffer size (Kbytes)
    > LOGSMAX 64 # Maximum number of logical log files
    > CLEANERS 127 # Number of buffer cleaner processes
    > SHMBASE 0x20000000 # Shared memory base address
    > SHMVIRTSIZE 131072 # initial virtual shared memory
    > segment size
    > SHMADD 24576 # Size of new shared memory segments
    > (Kbytes)
    > SHMTOTAL 0 # Total shared memory (Kbytes).
    > 0=>unlimited
    > CKPTINTVL 1800 # Check point interval (in sec)
    > LRUS 127 # Number of LRU queues
    > LRU_MAX_DIRTY 1 # LRU percent dirty begin cleaning
    > limit
    > LRU_MIN_DIRTY 0 # LRU percent dirty end cleaning limit
    > LTXHWM 50 # Long transaction high water mark
    > percentage
    > LTXEHWM 60 # Long transaction high water mark
    > (exclusive)
    > TXTIMEOUT 0x12c # Transaction timeout (in sec)
    > STACKSIZE 64 # Stack size (Kbytes)
    > # System Page Size
    > # BUFFSIZE - Dynamic Server no longer supports this configuration
    > parameter.
    > # To determine the page size used by Dynamic Server 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 10 # Default number of offline worker
    > threads
    > ON_RECVRY_THREADS 1 # Default number of online worker
    > threads
    > # 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 /usr/local/informix/etc/dr.lostfound # DR lost+found
    > # CDR Variables
    > CDR_LOGBUFFERS 2048 # size of log reading buffer pool
    > (Kbytes)
    > CDR_EVALTHREADS 1,2 # evaluator threads
    > (per-cpu-vp,additional)
    > CDR_DSLOCKWAIT 5 # DS lockwait timeout (seconds)
    > CDR_QUEUEMEM 4096 # Maximum amount of memory for any CDR
    > queue (Kbytes)
    > CDR_LOGDELTA 30 # % of log space allowed in queue
    > memory
    > CDR_NUMCONNECT 16 # Expected connections per server
    > CDR_NIFRETRY 300 # Connection retry (seconds)
    > CDR_NIFCOMPRESS 0 # Link level compression (-1 never, 0
    > none, 9 max)
    > # Backup/Restore variables
    > BAR_ACT_LOG /tmp/bar_act.log
    > BAR_MAX_BACKUP 0
    > BAR_RETRY 1
    > BAR_NB_XPORT_COUNT 10
    > BAR_XFER_BUF_SIZE 31
    > # Informix Storage Manager variables
    > ISM_DATA_POOL ISMData # If the data pool name is changed, be
    > sure to
    > # update
    > $INFORMIXDIR/bin/onbar. Change to
    > # ism_catalog -create_bootstrap
    > -pool <new name>
    > ISM_LOG_POOL ISMLogs
    > # Read Ahead Variables
    > RA_PAGES 16 # Number of pages to attempt to read
    > ahead
    > RA_THRESHOLD 8 # Number of pages left before next
    > group
    > # DBSPACETEMP:
    > # Dynamic Server equivalent of DBTEMP for SE. This is the list of
    > dbspaces
    > # that the Dynamic Server SQL Engine will use to create temp tables
    > etc.
    > # If specified it must be a colon separated list of dbspaces that
    > exist
    > # when the Dynamic Server 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 tmpdbs0,tmpdbs1,tmpdbs2,tmpdbs3 #
    > 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 Dynamic Server operations.
    > # For DUMPSHMEM, DUMPGCORE and DUMPCORE 1 means Yes, 0 means No.
    > DUMPDIR /usr/local/informix/tmp # this directory
    > DUMPSHMEM 0 # Dump a copy of shared memory
    > DUMPGCORE 0 # Dump a core image using 'gcore'
    > DUMPCORE 0 # Dump a core image (Warning:this
    > aborts Dynamic Server)
    > DUMPCNT 1 # Number of shared memory or gcore
    > dumps for
    > # a single user's session
    > FILLFACTOR 90 # Fill factor for building indexes
    > # method for Dynamic Server to use when determining current time
    > USEOSTIME 0 # 0: use internal time(fast), 1: get
    > time from OS(slow)
    > # Parallel Database Queries (pdq)
    > MAX_PDQPRIORITY 50 # Maximum allowed pdqpriority
    > DS_MAX_QUERIES 256 # Maximum number of decision support
    > queries
    > DS_TOTAL_MEMORY 32768 # Decision support memory (Kbytes)
    > DS_MAX_SCANS 1048576 # Maximum number of decision support
    > scans
    > DATASKIP off # List of dbspaces to skip
    > # OPTCOMPIND
    > # 0 => Nested loop joins will be preferred (where
    > # possible) over sortmerge joins and hash joins.
    > # 1 => If the transaction isolation mode is not
    > # "repeatable read", optimizer behaves as in (2)
    > # below. Otherwise it behaves as in (0) above.
    > # 2 => Use costs regardless of the transaction isolation
    > # mode. Nested loop joins are not necessarily
    > # preferred. Optimizer bases its decision purely
    > # on costs.
    > OPTCOMPIND 0 # To hint the optimizer
    > ONDBSPACEDOWN 1 # Dbspace down option: 0 = CONTINUE, 1
    > = ABORT, 2 = WAIT
    > LBU_PRESERVE 1 # Preserve last log for log backup
    > OPCACHEMAX 0 # Maximum optical cache size (Kbytes)
    > # HETERO_COMMIT (Gateway participation in distributed transactions)
    > # 1 => Heterogeneous Commit is enabled
    > # 0 (or any other value) => Heterogeneous Commit is disabled
    > HETERO_COMMIT 0
    > # Optimization goal: -1 = ALL_ROWS(Default), 0 = FIRST_ROWS
    > OPT_GOAL -1
    > # Optimizer DIRECTIVES ON (1/Default) or OFF (0)
    > DIRECTIVES 1
    > # Status of restartable restore
    > RESTARTABLE_RESTORE on
    sending to informix-list
    Murray Wood \(IList\) Guest

  4. #3

    Default Re: UNIX-Box slow down while execute stored procedure

    "Murray Wood \(IList\)" <ifxmaillist@quanta.co.nz> wrote in message news:<bn22qc$7b0$1@terabinaries.xmission.com>...
    > Start with ...
    >
    > When you run the procedure from dbaccess on the server how long does it
    > take?
    > Do you have the explain plan for the sqls in the procedure? (set explain on;
    > update statistics for your_procname;)
    >
    from dbaccess it is the same problem (run up to an hour and kills the
    unix-performance)

    the explain shows some sequential scans when the update(s) runs for
    all entries or when the where-clause goes over the temp table columns
    whitout an index.
    We have testet with some indexes (seq. scans replaces with index path)
    but nothing helps ... the session require too many - whatever
    Kai Guest

Posting Permissions

  • You may not post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139