Unix Technical Forum

Error -9791 when execute routine (procedure) - pls asap.....

This is a discussion on Error -9791 when execute routine (procedure) - pls asap..... within the Informix forums, part of the Database Server Software category; --> Current Environment: IDS9.40.FC4, O/S: AIX4.3 Dear folks I got a problem, When SPL(Stored Procedure Language) program is performed from ...


Go Back   Unix Technical Forum > Database Server Software > Informix

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 04-20-2008, 07:50 AM
abdoell
 
Posts: n/a
Default Error -9791 when execute routine (procedure) - pls asap.....

Current Environment:
IDS9.40.FC4, O/S: AIX4.3

Dear folks

I got a problem, When SPL(Stored Procedure Language) program is
performed from 4gl or PowerBuilder program, an error occured, In this
case, Informix system is going to DOWN.
here is the log:
################################################## ##################
10:15:10 Assert Failed: Exception Caught. Type: MT_EX_OS, Context:
mem
10:15:10 IBM Informix Dynamic Server Version 9.40.FC4
10:15:10 Who: Session(40492, larry@152.202.30.10, 3852,
700000070400068)
Thread(53579, sqlexec, 7000000703c6488, 3)
File: mtex.c Line: 377
10:15:10 Action: Please notify IBM Informix Technical Support.
10:15:10 stack trace for pid 274566 written to /IDS0/dumb/af.d533c85c
10:15:10 See Also: /IDS0/dumb/af.d533c85c
10:15:12 Exception Caught. Type: MT_EX_OS, Context: mem
10:15:12 (-9791): ERROR: Routine execution trap -- procname=<Lr01spl>
procid=430
reason: mem
10:15:14 Assert Failed: No Exception Handler
10:15:14 IBM Informix Dynamic Server Version 9.40.FC4
10:15:14 Who: Session(40492, larry@152.202.30.10, 3852,
700000070400068)
Thread(53579, sqlexec, 7000000703c6488, 3)
File: mtex.c Line: 431
10:15:14 Results: Exception Caught. Type: MT_EX_OS, Context: mem
10:15:14 Action: Please notify IBM Informix Technical Support.
10:15:14 stack trace for pid 274566 written to /IDS0/dumb/af.d533c85c
10:15:14 See Also: /IDS0/dumb/af.d533c85c
10:15:16 mtex.c, line 431, thread 53579, proc id 274566, No Exception
Handler.
10:15:16 Fatal error in ADM VP at mt.c:12298
10:15:16 Unexpected virtual processor termination, pid = 274566, exit
= 0x100

10:15:16 PANIC: Attempting to bring system down
10:29:52 IBM Informix Dynamic Server Started
################################################## ###########

HERE is the onconfig file:
################################################## ###########################
ROOTNAME rootdbs # Root dbspace name
ROOTPATH /IDS0/dev/rootdbsm # Path for device containing root
dbspace
ROOTOFFSET 0 # Offset of root dbspace into device
(Kbytes)
ROOTSIZE 500000 # 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 30000 # Physical log file size (Kbytes)

# Logical Log Configuration

LOGFILES 40 # Number of logical log files
LOGSIZE 40000 # Logical log size (Kbytes)

# Diagnostics

MSGPATH /IDS0/logs/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 /IDS0/etc/no_log.sh # Alarm program path
TBLSPACE_STATS 1 # Maintain tblspace statistics

# System Archive Tape Device

TAPEDEV /dev/rmt0 # Tape device path
TAPEBLK 16 # Tape block size (Kbytes)
TAPESIZE 40000000 # Maximum amount of data to put on
tape (Kbytes)

# Log Archive Tape Device

LTAPEDEV /dev/rmt0 # Log tape device path
LTAPEBLK 16 # Log tape block size (Kbytes)
LTAPESIZE 40000000 # Max amount of data to put on log
tape (Kbytes)

# Optical

STAGEBLOB # Informix Dynamic Server staging area

# System Configuration

SERVERNUM 1 # Unique id corresponding to a OnLine
instance
DBSERVERNAME post_shm # Name of default database server
DBSERVERALIASES # List of alternate dbservernames
NETTYPE soctcp,2,150,CPU # Configure poll thread(s) for
nettype
NETTYPE ipcshm,1,50,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 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

# Shared Memory Parameters

LOCKS 800000 # Maximum number of locks
BUFFERS 300000 # Maximum number of shared buffers
NUMAIOVPS 3 # Number of IO vps
PHYSBUFF 64 # Physical log buffer size (Kbytes)
LOGBUFF 32 # Logical log buffer size (Kbytes)
CLEANERS 22 # Number of buffer cleaner processes
SHMBASE 0x700000010000000 # Shared memory base address
SHMVIRTSIZE 81920 # initial virtual shared memory
segment size
SHMADD 8192 # Size of new shared memory segments
(Kbytes)
SHMTOTAL 0 # Total shared memory (Kbytes).
0=>unlimited
CKPTINTVL 300 # Check point interval (in sec)
LRUS 32 # Number of LRU queues
LRU_MAX_DIRTY 20.000000 # LRU percent dirty begin cleaning
limit
LRU_MIN_DIRTY 10.000000 # LRU percent dirty end cleaning limit
TXTIMEOUT 0x12c # Transaction timeout (in sec)
STACKSIZE 64

# 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.

DYNAMIC_LOGS 0
LTXHWM 40
LTXEHWM 50

# 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
# 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
DRINTERVAL 30 # DR max time between DR buffer
flushes (in sec)
DRTIMEOUT 30 # DR network timeout (in sec)
DRLOSTFOUND /IDS0/etc/dr.lostfound # DR lost+found file path

# CDR Variables
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_NIFCOMPRESS 0 # Link level compression (-1 never, 0
none, 9 max)
CDR_SERIAL 0,0 # Serial Column Sequence
CDR_DBSPACE # dbspace for syscdr database
CDR_QHDR_DBSPACE # CDR queue dbspace (default same as
catalog)
CDR_QDATA_SBSPACE # List of CDR queue smart blob
spaces

# CDR_MAX_DYNAMIC_LOGS
# -1 => unlimited
# 0 => disable dynamic log addition
# >0 => limit the no. of dynamic log additions with the specified
value.
# Max dynamic log requests that CDR can make within one server
session.

CDR_MAX_DYNAMIC_LOGS 0 # Dynamic log addition disabled
by default

# Backup/Restore variables
BAR_ACT_LOG /IDS0/logs/bar_act.log # ON-Bar Log file - not in /tmp
please
BAR_DEBUG_LOG /IDS0/logs/bar_dbug.log
# ON-Bar Debug Log - not in /tmp
please
BAR_MAX_BACKUP 0
BAR_RETRY 1
BAR_NB_XPORT_COUNT 10
BAR_XFER_BUF_SIZE 61440
RESTARTABLE_RESTORE on
BAR_PROGRESS_FREQ 0
BAR_BSALIB_PATH /usr/tivoli/tsm/client/informix/bin64/bsashr10.o

# Informix Storage Manager variables
ISM_DATA_POOL ISMData
ISM_LOG_POOL ISMLogs

# Read Ahead Variables
RA_PAGES 20 # Number of pages to attempt to read
ahead
RA_THRESHOLD 5 # Number of pages left before next
group

# 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 tempdbs1:tempdbs2:tempdbs3:tempdbs4 # 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 /IDS0/dumb # Preserve diagnostics in this directory
DUMPSHMEM 1 # Dump a copy of shared memory
DUMPGCORE 0 # Dump a core image using 'gcore'
DUMPCORE 0 # Dump a core image (Warning:this
aborts OnLine)
DUMPCNT 1 # Number of shared memory or gcore
dumps for
# a single user's session

FILLFACTOR 90 # Fill factor for building indexes

# method for OnLine 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 100 # Maximum allowed pdqpriority
DS_MAX_QUERIES 5 # Maximum number of decision support
queries
DS_TOTAL_MEMORY 8000 # Decision support memory (Kbytes)
DS_MAX_SCANS 10000 # Maximum number of decision support
scans
DATASKIP off
# 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 2 # To hint the optimizer

DIRECTIVES 1 # Optimizer DIRECTIVES ON (1/Default)
or OFF (0)

ONDBSPACEDOWN 2 # Dbspace down option: 0 = CONTINUE, 1
= ABORT, 2 = WAIT
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

SBSPACENAME # Default smartblob space name - this
is where blobs
# go if no sbspace is specified when the smartblob is
# created. It is also used by some datablades as
# the location to put their smartblobs.
SYSSBSPACENAME # Default smartblob space for use by
the Informix
# Server. This is used primarily for Informix Server
# system statistics collection.

BLOCKTIMEOUT 3600 # Default timeout for system block
SYSALARMPROGRAM /IDS0/etc/evidence.sh # System Alarm program path

# Optimization goal: -1 = ALL_ROWS(Default), 0 = FIRST_ROWS
OPT_GOAL -1

ALLOW_NEWLINE 0 # embedded newlines(Yes = 1, No = 0 or
anything but 1)

#
# The following are default settings for enabling Java in the
database.
# Replace all occurrences of /usr/informix with the value of
$INFORMIXDIR.

#VPCLASS jvp,num=1 # Number of JVPs to start with

JVPJAVAHOME /IDS0/extend/krakatoa/jre
# JRE installation root directory
JVPHOME /IDS0/extend/krakatoa # Krakatoa installation
directory

JVPPROPFILE /IDS0/extend/krakatoa/.jvpprops # JVP property file
JVPLOGFILE /IDS0/jvp.log # JVP log file.

JDKVERSION 1.3 # JDK version supported by this server

# The path to the JRE libraries relative to JVPJAVAHOME
JVPJAVALIB /bin

# The JRE libraries to use for the Java VM

JVPJAVAVM hpi:jvm:java:net:zip:jpeg

# use JVPARGS to change Java VM configuration
#To display jni call
#JVPARGS -verbose:jni

# Classpath to use upon Java VM start-up (use _g version for
debugging)

#JVPCLASSPATH /IDS0/extend/krakatoa/krakatoa_g.jar:/usr/informix/extend/krakatoa/jdbc_g.jar
JVPCLASSPATH /IDS0/extend/krakatoa/krakatoa.jar:/usr/informix/extend/krakatoa/jdbc.jar

You're help in this case would be greatly appreciated...!!!!
Rgds
Abdul
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #2 (permalink)  
Old 04-20-2008, 07:50 AM
rkusenet
 
Posts: n/a
Default Re: Error -9791 when execute routine (procedure) - pls asap.....


"abdoell" <abdoell@yahoo.com> wrote in message news:e05e140c.0410062234.5e3d27b5@posting.google.c om...
> Current Environment:
> IDS9.40.FC4, O/S: AIX4.3
>
> Dear folks
>
> I got a problem, When SPL(Stored Procedure Language) program is
> performed from 4gl or PowerBuilder program, an error occured, In this
> case, Informix system is going to DOWN.
> here is the log:
> STACKSIZE 64


Is there a deep nested level calling of stored procedures. Try increasing
STACKSIZE to 320 or more.



Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #3 (permalink)  
Old 04-20-2008, 07:50 AM
scottishpoet
 
Posts: n/a
Default Re: Error -9791 when execute routine (procedure) - pls asap.....

do you have "nested" stored procedures?

If so , I reckon this is a known problem.

Contact your support provider

If its what I think it is it should be fixed in FC5


abdoell@yahoo.com (abdoell) wrote in message news:<e05e140c.0410062234.5e3d27b5@posting.google. com>...
> Current Environment:
> IDS9.40.FC4, O/S: AIX4.3
>
> Dear folks
>
> I got a problem, When SPL(Stored Procedure Language) program is
> performed from 4gl or PowerBuilder program, an error occured, In this
> case, Informix system is going to DOWN.
> here is the log:
> ################################################## ##################
> 10:15:10 Assert Failed: Exception Caught. Type: MT_EX_OS, Context:
> mem
> 10:15:10 IBM Informix Dynamic Server Version 9.40.FC4
> 10:15:10 Who: Session(40492, larry@152.202.30.10, 3852,
> 700000070400068)
> Thread(53579, sqlexec, 7000000703c6488, 3)
> File: mtex.c Line: 377
> 10:15:10 Action: Please notify IBM Informix Technical Support.
> 10:15:10 stack trace for pid 274566 written to /IDS0/dumb/af.d533c85c
> 10:15:10 See Also: /IDS0/dumb/af.d533c85c
> 10:15:12 Exception Caught. Type: MT_EX_OS, Context: mem
> 10:15:12 (-9791): ERROR: Routine execution trap -- procname=<Lr01spl>
> procid=430
> reason: mem
> 10:15:14 Assert Failed: No Exception Handler
> 10:15:14 IBM Informix Dynamic Server Version 9.40.FC4
> 10:15:14 Who: Session(40492, larry@152.202.30.10, 3852,
> 700000070400068)
> Thread(53579, sqlexec, 7000000703c6488, 3)
> File: mtex.c Line: 431
> 10:15:14 Results: Exception Caught. Type: MT_EX_OS, Context: mem
> 10:15:14 Action: Please notify IBM Informix Technical Support.
> 10:15:14 stack trace for pid 274566 written to /IDS0/dumb/af.d533c85c
> 10:15:14 See Also: /IDS0/dumb/af.d533c85c
> 10:15:16 mtex.c, line 431, thread 53579, proc id 274566, No Exception
> Handler.
> 10:15:16 Fatal error in ADM VP at mt.c:12298
> 10:15:16 Unexpected virtual processor termination, pid = 274566, exit
> = 0x100
>
> 10:15:16 PANIC: Attempting to bring system down
> 10:29:52 IBM Informix Dynamic Server Started
> ################################################## ###########
>
> HERE is the onconfig file:
> ################################################## ###########################
> ROOTNAME rootdbs # Root dbspace name
> ROOTPATH /IDS0/dev/rootdbsm # Path for device containing root
> dbspace
> ROOTOFFSET 0 # Offset of root dbspace into device
> (Kbytes)
> ROOTSIZE 500000 # 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 30000 # Physical log file size (Kbytes)
>
> # Logical Log Configuration
>
> LOGFILES 40 # Number of logical log files
> LOGSIZE 40000 # Logical log size (Kbytes)
>
> # Diagnostics
>
> MSGPATH /IDS0/logs/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 /IDS0/etc/no_log.sh # Alarm program path
> TBLSPACE_STATS 1 # Maintain tblspace statistics
>
> # System Archive Tape Device
>
> TAPEDEV /dev/rmt0 # Tape device path
> TAPEBLK 16 # Tape block size (Kbytes)
> TAPESIZE 40000000 # Maximum amount of data to put on
> tape (Kbytes)
>
> # Log Archive Tape Device
>
> LTAPEDEV /dev/rmt0 # Log tape device path
> LTAPEBLK 16 # Log tape block size (Kbytes)
> LTAPESIZE 40000000 # Max amount of data to put on log
> tape (Kbytes)
>
> # Optical
>
> STAGEBLOB # Informix Dynamic Server staging area
>
> # System Configuration
>
> SERVERNUM 1 # Unique id corresponding to a OnLine
> instance
> DBSERVERNAME post_shm # Name of default database server
> DBSERVERALIASES # List of alternate dbservernames
> NETTYPE soctcp,2,150,CPU # Configure poll thread(s) for
> nettype
> NETTYPE ipcshm,1,50,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 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
>
> # Shared Memory Parameters
>
> LOCKS 800000 # Maximum number of locks
> BUFFERS 300000 # Maximum number of shared buffers
> NUMAIOVPS 3 # Number of IO vps
> PHYSBUFF 64 # Physical log buffer size (Kbytes)
> LOGBUFF 32 # Logical log buffer size (Kbytes)
> CLEANERS 22 # Number of buffer cleaner processes
> SHMBASE 0x700000010000000 # Shared memory base address
> SHMVIRTSIZE 81920 # initial virtual shared memory
> segment size
> SHMADD 8192 # Size of new shared memory segments
> (Kbytes)
> SHMTOTAL 0 # Total shared memory (Kbytes).
> 0=>unlimited
> CKPTINTVL 300 # Check point interval (in sec)
> LRUS 32 # Number of LRU queues
> LRU_MAX_DIRTY 20.000000 # LRU percent dirty begin cleaning
> limit
> LRU_MIN_DIRTY 10.000000 # LRU percent dirty end cleaning limit
> TXTIMEOUT 0x12c # Transaction timeout (in sec)
> STACKSIZE 64
>
> # 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.
>
> DYNAMIC_LOGS 0
> LTXHWM 40
> LTXEHWM 50
>
> # 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
> # 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
> DRINTERVAL 30 # DR max time between DR buffer
> flushes (in sec)
> DRTIMEOUT 30 # DR network timeout (in sec)
> DRLOSTFOUND /IDS0/etc/dr.lostfound # DR lost+found file path
>
> # CDR Variables
> 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_NIFCOMPRESS 0 # Link level compression (-1 never, 0
> none, 9 max)
> CDR_SERIAL 0,0 # Serial Column Sequence
> CDR_DBSPACE # dbspace for syscdr database
> CDR_QHDR_DBSPACE # CDR queue dbspace (default same as
> catalog)
> CDR_QDATA_SBSPACE # List of CDR queue smart blob
> spaces
>
> # CDR_MAX_DYNAMIC_LOGS
> # -1 => unlimited
> # 0 => disable dynamic log addition
> # >0 => limit the no. of dynamic log additions with the specified
> value.
> # Max dynamic log requests that CDR can make within one server
> session.
>
> CDR_MAX_DYNAMIC_LOGS 0 # Dynamic log addition disabled
> by default
>
> # Backup/Restore variables
> BAR_ACT_LOG /IDS0/logs/bar_act.log # ON-Bar Log file - not in /tmp
> please
> BAR_DEBUG_LOG /IDS0/logs/bar_dbug.log
> # ON-Bar Debug Log - not in /tmp
> please
> BAR_MAX_BACKUP 0
> BAR_RETRY 1
> BAR_NB_XPORT_COUNT 10
> BAR_XFER_BUF_SIZE 61440
> RESTARTABLE_RESTORE on
> BAR_PROGRESS_FREQ 0
> BAR_BSALIB_PATH /usr/tivoli/tsm/client/informix/bin64/bsashr10.o
>
> # Informix Storage Manager variables
> ISM_DATA_POOL ISMData
> ISM_LOG_POOL ISMLogs
>
> # Read Ahead Variables
> RA_PAGES 20 # Number of pages to attempt to read
> ahead
> RA_THRESHOLD 5 # Number of pages left before next
> group
>
> # 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 tempdbs1:tempdbs2:tempdbs3:tempdbs4 # 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 /IDS0/dumb # Preserve diagnostics in this directory
> DUMPSHMEM 1 # Dump a copy of shared memory
> DUMPGCORE 0 # Dump a core image using 'gcore'
> DUMPCORE 0 # Dump a core image (Warning:this
> aborts OnLine)
> DUMPCNT 1 # Number of shared memory or gcore
> dumps for
> # a single user's session
>
> FILLFACTOR 90 # Fill factor for building indexes
>
> # method for OnLine 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 100 # Maximum allowed pdqpriority
> DS_MAX_QUERIES 5 # Maximum number of decision support
> queries
> DS_TOTAL_MEMORY 8000 # Decision support memory (Kbytes)
> DS_MAX_SCANS 10000 # Maximum number of decision support
> scans
> DATASKIP off
> # 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 2 # To hint the optimizer
>
> DIRECTIVES 1 # Optimizer DIRECTIVES ON (1/Default)
> or OFF (0)
>
> ONDBSPACEDOWN 2 # Dbspace down option: 0 = CONTINUE, 1
> = ABORT, 2 = WAIT
> 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
>
> SBSPACENAME # Default smartblob space name - this
> is where blobs
> # go if no sbspace is specified when the smartblob is
> # created. It is also used by some datablades as
> # the location to put their smartblobs.
> SYSSBSPACENAME # Default smartblob space for use by
> the Informix
> # Server. This is used primarily for Informix Server
> # system statistics collection.
>
> BLOCKTIMEOUT 3600 # Default timeout for system block
> SYSALARMPROGRAM /IDS0/etc/evidence.sh # System Alarm program path
>
> # Optimization goal: -1 = ALL_ROWS(Default), 0 = FIRST_ROWS
> OPT_GOAL -1
>
> ALLOW_NEWLINE 0 # embedded newlines(Yes = 1, No = 0 or
> anything but 1)
>
> #
> # The following are default settings for enabling Java in the
> database.
> # Replace all occurrences of /usr/informix with the value of
> $INFORMIXDIR.
>
> #VPCLASS jvp,num=1 # Number of JVPs to start with
>
> JVPJAVAHOME /IDS0/extend/krakatoa/jre
> # JRE installation root directory
> JVPHOME /IDS0/extend/krakatoa # Krakatoa installation
> directory
>
> JVPPROPFILE /IDS0/extend/krakatoa/.jvpprops # JVP property file
> JVPLOGFILE /IDS0/jvp.log # JVP log file.
>
> JDKVERSION 1.3 # JDK version supported by this server
>
> # The path to the JRE libraries relative to JVPJAVAHOME
> JVPJAVALIB /bin
>
> # The JRE libraries to use for the Java VM
>
> JVPJAVAVM hpi:jvm:java:net:zip:jpeg
>
> # use JVPARGS to change Java VM configuration
> #To display jni call
> #JVPARGS -verbose:jni
>
> # Classpath to use upon Java VM start-up (use _g version for
> debugging)
>
> #JVPCLASSPATH /IDS0/extend/krakatoa/krakatoa_g.jar:/usr/informix/extend/krakatoa/jdbc_g.jar
> JVPCLASSPATH /IDS0/extend/krakatoa/krakatoa.jar:/usr/informix/extend/krakatoa/jdbc.jar
>
> You're help in this case would be greatly appreciated...!!!!
> Rgds
> Abdul

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #4 (permalink)  
Old 04-20-2008, 07:51 AM
Claus Samuelsen
 
Posts: n/a
Default Re: Error -9791 when execute routine (procedure) - pls asap.....

abdoell wrote:

> Current Environment:
> IDS9.40.FC4, O/S: AIX4.3
>


Is this supported? I thought IDS 9.40.FC4 was only released for AIX 5.2
and 5.3
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


All times are GMT. The time now is 09:16 AM.


Powered by vBulletin® Version 3.6.5
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
SEO by vBSEO 3.2.0
www.UnixAdminTalk.com