Dear All,

I have installed Informix Dynamic Server 9.30 in Windows NT work station machine (RAM size : 256K) and Harddisk space is "3 GB free space"

I created a data base "Schema" which contains my applications' table schema.

i have 1152 table in my application. After running 152 tables thru script in my informix server, it got choked and hanged. i cant' proceed from there and server gone to "Quiescent mode" and it saying "Logical logs are full - backup needed"

what are the settings need to be changed in "onconfig.std" and my "schema.std" files.

i want to set the logical and physical log file to be grown automaticaly with out specifying the size every time (manual)

this is my onconfig.std file

#************************************************* *************************
#
# INFORMIX SOFTWARE, INC.
#
# Title: onconfig.std
# Description: Informix Dynamic Server Configuration Parameters
#
#************************************************* *************************

# Root Dbspace Configuration

ROOTNAME rootdbs # Root dbspace name
ROOTPATH # Path for device containing root dbspace
ROOTOFFSET 0 # Offset of root dbspace into device (Kbytes)
ROOTSIZE 20000 # 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 2000 # Physical log file size (Kbytes)

# Logical Log Configuration

LOGFILES 6 # Number of logical log files
LOGSIZE 1500 # Logical log size (Kbytes)
LOG_BACKUP_MODE MANUAL # Logical log backup mode (MANUAL, CONT)

# Diagnostics

MSGPATH online.log # System message log file path
CONSOLE console.log # System console message path
ALARMPROGRAM # 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 \\.\TAPE0 # Tape device path
TAPEBLK 16 # Tape block size (Kbytes)
TAPESIZE 10240 # Maximum amount of data to put on tape (Kbytes)

# Log Archive Tape Device

LTAPEDEV \\.\TAPE1 # 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 OnLine instance
DBSERVERNAME # Name of default database server
DBSERVERALIASES # List of alternate dbservernames
NETTYPE onsoctcp,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 0 # 0 for single-processor, 1 for multi-processor
NUMCPUVPS 1 # 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 2000 # Maximum number of locks
BUFFERS 200 # Maximum number of shared buffers
NUMAIOVPS # Number of IO vps
PHYSBUFF 32 # Physical log buffer size (Kbytes)
LOGBUFF 32 # Logical log buffer size (Kbytes)
LOGSMAX 6 # Maximum number of logical log files
CLEANERS 1 # Number of buffer cleaner processes
SHMBASE 0xC000000L # Shared memory base address
SHMVIRTSIZE 8192 # 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 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
LTXHWM 50 # Long transaction high water mark percentage
LTXEHWM 60 # Long transaction high water mark (exclusive)
TXTIMEOUT 300 # 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
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_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 bar_act.log
BAR_MAX_BACKUP 0
BAR_RETRY 1
BAR_NB_XPORT_COUNT 10
BAR_XFER_BUF_SIZE 15
BAR_BSALIB_PATH libbsa.dll #Location of ISM XBSA dll

RESTARTABLE_RESTORE OFF #To support restartable restore..values on/off

# Informix Storage Manager variables
ISM_DATA_POOL ISMData
ISM_LOG_POOL ISMLogs

# Read Ahead Variables
RA_PAGES # Number of pages to attempt to read ahead
RA_THRESHOLD # 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 # 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 \tmp # 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 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 100 # Maximum allowed pdqpriority
DS_MAX_QUERIES 32 # Maximum number of decision support queries
DS_TOTAL_MEMORY 4096 # Decision support memory (Kbytes)
DS_MAX_SCANS 1048576 # Maximum number of decision support scans
DATASKIP # 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 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
LBU_PRESERVE 0 # 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

SBSPACENAME # Default smartblob space name

BLOCKTIMEOUT 3600 # Default timeout for system block

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



Please help me.
Thanks,
Roger Harper

If this a a development machine and you don't want
to save your logical logs, simply set your LTAPEDEV
to '/dev/null'. Maybe you have to set it to 'nul' on NT,
I'm not sure.

Because your logs are now full, after setting LTAPEDEV, you
should execute 'ontape -a' to release them.

You have to make these settings in your $ONCONFIG, not
"onconfig.std" (this is only a template delivered by Informix).

If this is a production system, you have think about a
backup strategy for your databaseserver.
Setting LTAPEDEV to '/dev/null' might not be the right
solution for production systems. Please read
the Informix 'Backup and Restore Guide' for details.

Also you should use a real operating system. Over 1000 tables
is a lot, migrating your databaseserver to a Linux or Unix box
will save you a lot of pain in the future.

HTH.

Best regards

Eric
--
IT-Consulting Herber
WWW: http://www.herber-consulting.de
Email: eric@herber-consulting.de

***********************************************
Download the IFMX Database-Monitor for free at:
http://www.herber-consulting.de/BusyBee
***********************************************

Dear Eric,

Thanks a lot for your quick response. where can i set "'/dev/null' for Windows NT OS.

Is there any specific file which has the settings details?

Please mail me.

Regards,
Roger Harper

Dear Eric,

Still i am facing the same problem after i set the NULL in "LTAPEDEV" in
config.std file and schema.std file.

I have executed the ontape -a also

"C:\Program Files\informix>ontape -a

Performing automatic backup of logical logs.

Please mount tape 1 on NULL and press Return to continue ...
Logbackup failed - function open tape device NULL failed code -1 errno 2

Program over. "


Please help me to fix this issue.

Regards,
Roger Harper

You need to specifiy 'nul' not 'null'.
This should work.

Dear Eric,

Thanks a lot, its working but i want a permanent solution to sort out this issue.

How can we specify maximum logical logs and physical logical logs while creating the DB itself (like SQL Server)

Please help me.

Thanks,
Roger Harper.

The physical log is always fixed but is a circular log,
so this is normally not a problem.

With IDS 9.30 there is a new feature called "dynamic logs".

But you might not need this. If you specify 'nul' as your
LTAPDEDEV, the logical logs will be automatically marked
free as soon as any open transactions (started in this) log
are committed.

After setting LTAPEDEV to 'nul', restart your dataseserver and
retry your statements. It should work now.

Best regards

Eric
--
IT-Consulting Herber
WWW: http://www.herber-consulting.de
Email: eric@herber-consulting.de

***********************************************
Download the IFMX Database-Monitor for free at:
http://www.herber-consulting.de/BusyBee
***********************************************

Dear Eric,

Once again thanks a lot for your timely help to sorted out that issue.

But i got error message "ISAM Error: Not Enough Storage"

what i did means, i have created a new chunk with size of 2GB.

My requirement how can i set automatic growth option to increase the chunk file whenever it got full.

Please help me to sort out this issue.

Thanks,
Roger Harper

Roger,

this is not possible with IFMX. You can't automatically increase
a dbspace (with additional chunks).

Did your dbspace fill during the "create table" phase ?

If this is the case, it has to do with your extent sizes in the
'create table' statements.

You might need to create additional dbspaces (and explicitly
create your tables in these dbspaces) or add further
chunks to your existing dbspace in order to be able to
create all your tables with the appropriate extent sizes.

You might reduce the first extent size of your tables and
therefore create a larger next size, for example:


create table t1
(
f1 int
) extent size 50000 next size 3000;

Here you might use "extent size 3000 next size 50000"
or something like that.
This ensures that you could create all your tables inside
the configured disk space.

Automatically extending dbspaces could be done, but you
have to write your own scripts for this.
The database monitor 'BusyBee' which could be downloaded
from my website (see URL at the end) observes the
filling degree of dbspaces and is able to trigger and external
script which for example might configure additional diskspace
for your databaseserver.
Unfortunately 'BusyBee' is only availabe for UNIX platforms.

I would really recommend that you switch your databaseserver platform to Linux or Unix.
Believe me, this will save you a lot of pain in the future.
Windows is not a real server platform and it will never be
that (in my opinion).


Eric
--
IT-Consulting Herber
WWW: http://www.herber-consulting.de
Email: eric@herber-consulting.de

***********************************************
Download the IFMX Database-Monitor for free at:
http://www.herber-consulting.de/BusyBee
***********************************************