Error while access Tables using Crystal Reports
Posted in 2007
Topics: High Availability & Replication, Performance & Tuning, Storage & Space Management, Stored Procedures & SPL, Error Codes & Troubleshooting, Connectivity: ODBC / JDBC / .NET, Server Administration, Transactions, Locking & Isolation, Logging & Checkpoints, Networking & sqlhosts Configuration
When access the Informix Database Tables using Crystal Reports we get
the following error :-
Query Engine Error : HY000[Informix][Informix ODBC Driver]
[Informix]General exception error has occured in the optimizer.
The error has suddenly come up in our Production Server. We did a
restore of our Productoin Server into the test and tried to access the
tables using Crystal Report and we get the same error .
Can anybody help me our urgenlty..-- Dhaya, CB, Doha
Below is dump of the log file :-
Message Log File: C:\\Informix\\prime_test.log
11:09:49 Maximum server connections 0
11:10:20 Assert Failed: NT Exception!
11:10:20 See Also: C:\\tmp\\af.414fe6c
11:10:21 Assert Failed: Exception Caught. Type: MT_EX_OS, Context:mem
11:10:21 Informix Dynamic Server Version 9.30.TC1
11:10:21 Who: Session(6, cap@dhayapc1.cbq.com.qa, 3468, 0)
Thread(44, sqlexec, 0, 3)
File: mtex.c Line: 901
11:10:21 Action: Please notify Informix Technical Support.
11:10:21 stack trace for pid 780 written to C:\\tmp\\af.414fe6c
11:10:22 See Also: C:\\tmp\\af.414fe6c
11:10:35 Exception Caught. Type: MT_EX_OS, Context: mem
11:10:39 Booting Language <spl> from module <>
11:10:39 Loading Module <SPLNULL>
The ONCONFIG details are below :-
#**************************************************************************
#
# INFORMIX SOFTWARE, INC.
#
# Title: onconfig.std
# Description: Informix Dynamic Server Configuration Parameters
#
#**************************************************************************
# Root Dbspace Configuration
ROOTNAME rootdbs # Root dbspace name
ROOTPATH c:\\ifmxdata\\rootdbs.d01 # Path for device containing root
dbspace
ROOTOFFSET 0 # Offset of root dbspace into device
(Kbytes)
ROOTSIZE 512000 # Size of root dbspace (Kbytes)
# Disk Mirroring Configuration Parameters
MIRROR 0 # Mirroring flag (Yes = 1, No = 0)
MIRRORPATH # Path for device containing mirroredroot
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 79 # Number of logical log files
LOGSIZE 20000 # Logical log size (Kbytes)LOG_BACKUP_MODE MANUAL # Logical log backup mode (MANUAL,
CONT)
# Diagnostics
MSGPATH C:\\Informix\\prime_test.log # System message log file
path
CONSOLE C:\\Informix\\conprime_test.log # System console message
path
ALARMPROGRAM C:\\Informix\\etc\\log_full.bat # Alarm program path
TBLSPACE_STATS 1 # Maintain tblspace statistics
# System Diagnostic Script.
# SYSALARMPROGRAM - Full path of the system diagnostic script (e.g.
# c:\\informix\\etc\\evidence.bat.) Set this parameter
# if you want a different Diagnostic Script than
# {INFORMIXDIR}\\etc\\evidence.bat, which is default.
System Archive Tape Device
TAPEDEV S:primel0 # Tape device path
#TAPEDEV \\\\.\\TAPE0 # Tape #device path#TAPEDEV NUL # Tape device path
TAPEBLK 64 # Change 32 # Tape block size
(Kbytes)
TAPESIZE 50000000 # Maximum amount of data to put on tape
(Kbytes)
# Log Archive Tape Device
LTAPEDEV NUL # Log tape device path
LTAPEBLK 16 # Log tape block size (Kbytes)
LTAPESIZE 10240 # Max amount of data to put on log
tape (Kbytes)
# Optical
STAGEBLOB # Informix Dynamic Server/Optical
staging area
OPTICAL_LIB_PATH # Location of Optical Subsystem
driver DLL
# System Configuration
SERVERNUM 0 # Unique id corresponding to a serverinstance
DBSERVERNAME prime_test # Name of default Dynamic Server
DBSERVERALIASES # List of alternate dbservernames
NETTYPE onsoctcp,2,,NET # Override sqlhosts nettype parameters
#NETTYPE soctcp,1,,NET # Override sqlhosts nettypeparameters
DEADLOCK_TIMEOUT 60 # Max time to wait of lock indistributed 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 vpsto one
NOAGE 0 # Process aging
AFF_SPROC 0 # Affinity start processor
AFF_NPROCS 0 # Affinity number of processors
# Shared Memory Parameters
LOCKS 800000 #800000 # Maximum number oflocks
BUFFERS 200000 #128000 # Maximum number of sharedbuffers
NUMAIOVPS 1 # Number of IO vps
PHYSBUFF 512 # Physical log buffer size (Kbytes)
LOGBUFF 512 # Logical log buffer size (Kbytes)
CLEANERS 10 # Number of buffer cleaner processes
SHMBASE 0xc000000 # Shared memory base address
SHMVIRTSIZE 768000 # initial virtual shared memorysegment size
SHMADD 64000 # Size of new shared memory segments
(Kbytes)
SHMTOTAL 0 # Total shared memory (Kbytes).
0=>unlimited
CKPTINTVL 300 # Check point interval (in sec)
LRUS 32 # 8 Number of LRU queues
LRU_MAX_DIRTY 60 # LRU percent dirty begin cleaninglimit
LRU_MIN_DIRTY 50 # LRU percent dirty end cleaning limit
TXTIMEOUT 0x12c # Transaction timeout (in sec)
STACKSIZE 512 # 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 workerthreads
ON_RECVRY_THREADS 1 # Default number of online workerthreads
# Data Replication Variables
DRINTERVAL 30 # DR max time between DR buffer
flushes (in sec)
DRTIMEOUT 30 # DR network timeout (in sec)
DRLOSTFOUND \\tmp # 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 memory for any CDR queue
(
i would look in: C:\\tmp\\af.414fe6c which has more info. also phone
tech support.
it sounds like the optimizer barfed on something.
an example could be that npused on the partition page of the accessed
tables ended up being negative or????
this may cause bad stats.
you could try running run oncheck on the affected tables followed by
update statistics for the affected tables....
Superboer.
On 21 feb, 10:06, "sdhaya" <dhaya.sni...@gmail.com> wrote:
> When access the Informix Database Tables using Crystal Reports we get
> the following error :-
>
> Query Engine Error : HY000[Informix][Informix ODBC Driver]
> [Informix]General exception error has occured in the optimizer.
>
> The error has suddenly come up in our Production Server. We did a
> restore of our Productoin Server into the test and tried to access the
> tables using Crystal Report and we get the same error .
>
> Can anybody help me our urgenlty..-- Dhaya, CB, Doha
>
> Below is dump of the log file :-
>
> Message Log File: C:\\Informix\\prime_test.log
> 11:09:49 Maximum server connections 0
> 11:10:20 Assert Failed: NT Exception!
> 11:10:20 See Also: C:\\tmp\\af.414fe6c
> 11:10:21 Assert Failed: Exception Caught. Type: MT_EX_OS, Context:> mem
> 11:10:21 Informix Dynamic Server Version 9.30.TC1
> 11:10:21 Who: Session(6, c...@dhayapc1.cbq.com.qa, 3468, 0)
> Thread(44, sqlexec, 0, 3)
> File: mtex.c Line: 901
> 11:10:21 Action: Please notify Informix Technical Support.
> 11:10:21 stack trace for pid 780 written to C:\\tmp\\af.414fe6c
> 11:10:22 See Also: C:\\tmp\\af.414fe6c
> 11:10:35 Exception Caught. Type: MT_EX_OS, Context: mem
> 11:10:39 Booting Language <spl> from module <>
> 11:10:39 Loading Module <SPLNULL>>
> The ONCONFIG details are below :-
>
> #**************************************************************************
> #
> # INFORMIX SOFTWARE, INC.
> #
> # Title: onconfig.std
> # Description: Informix Dynamic Server Configuration Parameters
> #
> #**************************************************************************
>
> # Root Dbspace Configuration
>
> ROOTNAME rootdbs # Root dbspace name
> ROOTPATH c:\\ifmxdata\\rootdbs.d01> # Path for device containing root
> dbspace
> ROOTOFFSET 0 # Offset of root dbspace into device
> (Kbytes)
> ROOTSIZE 512000 # 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 79 # Number of logical log files
> LOGSIZE 20000 # Logical log size (Kbytes)> LOG_BACKUP_MODE MANUAL # Logical log backup mode (MANUAL,
> CONT)
>
> # Diagnostics
>
> MSGPATH C:\\Informix\\prime_test.log # System message log file
> path
> CONSOLE C:\\Informix\\conprime_test.log # System console message
> path
> ALARMPROGRAM C:\\Informix\\etc\\log_full.bat # Alarm program path
> TBLSPACE_STATS 1 # Maintain tblspace statistics>
> # System Diagnostic Script.
> # SYSALARMPROGRAM - Full path of the system diagnostic script (e.g.
> # c:\\informix\\etc\\evidence.bat.) Set this parameter
> # if you want a different Diagnostic Script than
> # {INFORMIXDIR}\\etc\\evidence.bat, which is default.
>
> System Archive Tape Device
> TAPEDEV S:primel0 # Tape device path
> #TAPEDEV \\\\.\\TAPE0 # Tape #device path> #TAPEDEV NUL # Tape device path
> TAPEBLK 64 # Change 32 # Tape block size
> (Kbytes)
> TAPESIZE 50000000 # Maximum amount of data to put on tape
> (Kbytes)>
> # Log Archive Tape Device
>
> LTAPEDEV NUL # Log tape device path
> LTAPEBLK 16 # Log tape block size (Kbytes)
> LTAPESIZE 10240 # Max amount of data to put on log
> tape (Kbytes)>
> # Optical
>
> STAGEBLOB # Informix Dynamic Server/Optical
> staging area
> OPTICAL_LIB_PATH # Location of Optical Subsystem
> driver DLL
>
> # System Configuration
>
> SERVERNUM 0 # Unique id corresponding to a server> instance
> DBSERVERNAME prime_test # Name of default Dynamic Server
> DBSERVERALIASES # List of alternate dbservernames
> NETTYPE onsoctcp,2,,NET # Override sqlhosts nettype parameters
> #NETTYPE soctcp,1,,NET # Override sqlhosts nettype> parameters
> 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 800000 #800000 # Maximum number of> locks
> BUFFERS 200000 #128000 # Maximum number of shared> buffers
> NUMAIOVPS 1 # Number of IO vps
> PHYSBUFF 512 # Physical log buffer size (Kbytes)
> LOGBUFF 512 # Logical log buffer size (Kbytes)
> CLEANERS 10 # Number of buffer cleaner processes
> SHMBASE 0xc000000 # Shared memory base address
> SHMVIRTSIZE 768000 # initial virtual shared memory> segment size
> SHMADD 64000 # Size of new shared memory segments
> (Kbytes)
> SHMTOTAL 0 # Total shared memory (Kbytes).
> 0=>unlimited
> CKPTINTVL 300 # Check point interval (in sec)
> LRUS 32 # 8 Number of LRU queues
> LRU_MAX_DIRTY 60 # LRU percent dirty begin cleaning> limit
> LRU_MIN_DIRTY 50 # LRU percent dirty end cleaning limit
> TXTIMEOUT 0x12c # Transaction timeout (in sec)
> STACKSIZE 512 # 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:@