我现在的数据库服务器,在每天早上数据处理的时候。每次做checkpoint的时间都太长了,有时候甚至达到300s的长度。请大家能给点建议。
服务器为一HP小型机,4CPU,8G内存。OS为Linux系统。数据库为Informix10下面贴出我的onconfig内容
#**************************************************************************
#
# Licensed Material - Property Of IBM
#
# "Restricted Materials of IBM"
#
# IBM Informix Dynamic Server
# (c) Copyright IBM Corporation 1996, 2006 All rights reserved.
#
# Title: onconfig.std
# Description: IBM Informix Dynamic Server Configuration Parameters
#
#**************************************************************************
# Root Dbspace Configuration
ROOTNAME rootdbs # Root dbspace name
ROOTPATH /home/informix/db/rootdbs # Path for device containing root dbspace
ROOTOFFSET 0 # Offset of root dbspace into device (Kbytes)
ROOTSIZE 1500000 # 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 300000 # Physical log file size (Kbytes)
# Logical Log Configuration
LOGFILES 199 # Number of logical log files
LOGSIZE 2000 # Logical log size (Kbytes)
# Tablespace Tablespace Configuration in Root Dbspace
TBLTBLFIRST 0 # First extent size (Kbytes) (0 = default)
TBLTBLNEXT 0 # Next extent size (Kbytes) (0 = default)
# Security
# DBCREATE_PERMISSION:
# By default any user can create a database. Uncomment DBCREATE_PERMISSON to
# limit database creation to a specific user. Add a new DBCREATE_PERMISSION
# line for each permitted user.
#DBCREATE_PERMISSION informix
# DB_LIBRARY_PATH:
# When loading a (C or C++) shared object (for a UDR or UDT), IDS checks that
# the user-specified path starts with one of the directory prefixes listed in
# the comma-separated list of prefixes in DB_LIBRARY_PATH. The string
# "$INFORMIXDIR/extend" must be included in DB_LIBRARY_PATH in order for
# extensibility and IBM supplied blades to work correctly.
# DB_LIBRARY_PATH $INFORMIXDIR/extend
# IFX_EXTEND_ROLE:
# 0 (or off) => Disable use of EXTEND role to control who can register
# external routines.
# 1 (or on) => Enable use of EXTEND role to control who can register
# external routines. This is the default behaviour.
#
IFX_EXTEND_ROLE 1 # To control the usage of EXTEND role.
# Diagnostics
MSGPATH /home/informix/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 /home/informix/etc/alarmprogram.sh # Alarm program path
ALRM_ALL_EVENTS 0 # Triggers ALARMPROGRAM for any event occur
TBLSPACE_STATS 1 # Maintain tblspace statistics
# System Archive Tape Device
TAPEDEV /dev/null # Tape device path
TAPEBLK 32 # Tape block size (Kbytes)
TAPESIZE 10240 # Maximum amount of data to put on tape (Kbytes)
# Log Archive Tape Device
LTAPEDEV /dev/null # Log tape device path
LTAPEBLK 32 # Log tape block size (Kbytes)
LTAPESIZE 10240 # Max amount of data to put on log tape (Kbytes)
# Optical
STAGEBLOB # Informix Dynamic Server staging area
# System Configuration
SERVERNUM 0 # Unique id corresponding to a OnLine instance
DBSERVERNAME lssjsvr # Name of default database server
DBSERVERALIASES # List of alternate dbservernames
NETTYPE soctcp,1,200,CPU # Configure poll thread(s) for nettype
DEADLOCK_TIMEOUT 60 # Max time to wait of lock in distributed env.
RESIDENT 1 # 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 3 # Affinity number of processors
# Shared Memory Parameters
LOCKS 1000000 # Maximum number of locks
NUMAIOVPS 4 # Number of IO vps
PHYSBUFF 384 # Physical log buffer size (Kbytes)
LOGBUFF 128 # Logical log buffer size (Kbytes)
CLEANERS 7 # Number of buffer cleaner processes
SHMBASE 0x200000000 # Shared memory base address
SHMVIRTSIZE 2048000 # initial virtual shared memory segment size
SHMADD 512000 # Size of new shared memory segments (Kbytes)
EXTSHMADD 100000 # Size of new extension shared memory segments (Kbytes)
SHMTOTAL 0 # Total shared memory (Kbytes). 0=>unlimited
SHMVIRT_ALLOCSEG 0 # Values between 0 and .99 are %, values > 1 are
# KB - when this much virtual memory is used we
# try to get a new segment. 0 means "off". 2nd
# parameter is alarm level
CKPTINTVL 300 # Check point interval (in sec)
TXTIMEOUT 300 # Transaction timeout (in sec)
STACKSIZE 256 # Stack size (Kbytes)
# 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.
#
# In case of system configured with CDR, the difference between LTXHWM and
# LTXEHWM should be atleast 30% so that we could minimize log overrun issue.
DYNAMIC_LOGS 2
LTXHWM 70
LTXEHWM 80
# 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
# 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 /home/informix/etc/dr.lostfound # DR lost+found file path
DRIDXAUTO 0 # DR automatic index repair. 0=off, 1=on
# 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 # 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 /home/informix/bar_act.log # ON-Bar Log file - not in /tmp please
BAR_DEBUG_LOG /home/informix/bar_dbug.log # ON-Bar Debug Log - not in /tmp please
BAR_MAX_BACKUP 0
BAR_RETRY 1
BAR_NB_XPORT_COUNT 20
BAR_XFER_BUF_SIZE 31
RESTARTABLE_RESTORE ON
BAR_PROGRESS_FREQ 0
# Informix Storage Manager variables
ISM_DATA_POOL ISMData
ISM_LOG_POOL ISMLogs
# Read Ahead Variables
RA_PAGES 10 # Number of pages to attempt to read ahead
RA_THRESHOLD # 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 tempdbs # 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 /home/informix/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 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 # Maximum number of decision support queries
DS_TOTAL_MEMORY # Decision support memory (Kbytes)
DS_MAX_SCANS 1048576 # Maximum number of decision support scans
DS_NONPDQ_QUERY_MEM 128 # Non PDQ query memory (Kbytes)
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 1 # 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 /home/informix/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)
#Create Index Online Shared Memory usage limitation
ONLIDX_MAXMEM 5120 # Per pool per index (Kbytes)
#Timeout for client connection request
LISTEN_TIMEOUT 10 # Timeout (in Seconds)
#Following are the deprecated configuration parameters, instead of these
#use BUFFERPOOL configuration parameter
#BUFFERS, LRUS, LRU_MIN_DIRTY, LRU_MAX_DIRTY
IFX_FOLDVIEW 0 # fold multiple tables or union all view with ansi joins
# The following parameters are related to the buffer pool
BUFFERPOOL default,buffers=400000,lrus=8,lru_min_dirty=50.000000,lru_max_dirty=60.000000
BUFFERPOOL size=2K,buffers=400000,lrus=8,lru_min_dirty=50.000000,lru_max_dirty=60.000000
相关推荐
Informix数据库连接驱动jar包是Java应用程序与Informix关系型数据库管理系统进行交互的重要组件。这些jar文件包含了必要的类和资源,使得Java程序能够利用JDBC(Java Database Connectivity)API来执行SQL语句、管理...
【Informix数据库学习资料】 Informix数据库是一款高效且灵活的关系型数据库管理系统,广泛应用于企业级应用,尤其在金融、电信等领域。本学习资料集合包含了Informix数据库操作、SQL语法、编程、性能优化、服务器...
Informix 数据库锁表问题解决方案 在 Informix 数据库中,锁表问题是一个常见的错误,会导致系统性能下降和数据不一致。锁表问题的解决需要对数据库进行深入的分析和诊断。本文将讨论 Informix 数据库锁表问题的...
在 Informix 数据库的管理和维护过程中,可能会遇到各种问题,以下是一些常见问题的详细解答: 1. **怎样尽快获得 Informix 公司技术支持?** - 通常,你可以通过Informix官方支持网站或者客户服务热线联系技术...
标题中的“Informix数据库驱动(亲测)”指的是用于连接Informix数据库的Java驱动程序,它允许Java应用程序通过JDBC(Java Database Connectivity)接口与Informix数据库进行交互。这个驱动已经由发布者亲自测试并确认...
《Informix数据库详解》 Informix数据库是一款由IBM公司开发的高效能、高可用性的关系型数据库管理系统(RDBMS),广泛应用于企业级的数据存储和处理。本文档集合全面覆盖了Informix数据库的相关知识,包括SQL语法...
【Informix数据库全面解析】 Informix数据库管理系统,由IBM公司精心研发,是全球知名的RDBMS(关系数据库管理系统)之一,特别擅长处理在线事务处理(OLTP)工作负载。其强大的性能、高度的可扩展性和出色的稳定...
连接数据库informix的驱动jar包
【Informix 数据库备份方法详解】 在 Informix 数据库管理中,备份是保障数据安全的重要环节。本篇文章将深入探讨 Informix 的两种常见备份方法:dbexport 和 0级备份,以及它们各自的优缺点和使用场景。 1. **...
Informix for Windows 数据库安装配置详解 Informix 是 IBM 公司开发的一款关系数据库管理系统,提供了强大且灵活的数据存储和管理功能。在本文中,我们将详细介绍 Informix for Windows 数据库的安装配置过程,...
**Informix数据库培训文档和学习资料** Informix是一款由IBM公司开发的关系型数据库管理系统(RDBMS),在企业级应用中广泛使用。本压缩包包含了两份珍贵的学习资源:《INFORMIX培训教材.doc》和《informix探秘.pdf...
Informix 11.70 数据库的名称和端口 Informix 11.70 数据库的名称和端口是 Windows 系统下 Informix 数据库的重要组件。在本文中,我们将详细介绍如何获取 Informix 11.70 数据库的名称和端口,并且使用第三方工具...
Informix 数据库配置是一个关键步骤,确保数据库系统能够正确运行并提供高效的数据访问。以下是配置 Informix 数据库的详细步骤: 一、连接测试 在安装 Informix 完成后,首先要进行连接测试以验证数据库服务器的...
【Informix数据库基础】 在IT领域,数据库是存储和管理数据...随着课程的深入,我们将探讨更多关于Informix的特性和应用场景,例如事务处理、并发控制、备份恢复策略等,帮助学员成为一名熟练的Informix数据库管理员。
《Informix数据库与设计指南》是一本专注于Informix数据库系统及其设计原理的专业书籍。Informix是IBM公司的一款高性能、企业级的关系型数据库管理系统,广泛应用于各种行业和领域,以其高效的数据处理能力、强大的...
**Informix数据库教程** 在IT领域,数据库管理系统(DBMS)是支撑各类应用程序运行的重要基础设施,Informix便是其中的一款高效、可扩展的数据库解决方案。尤其在Linux环境下,Informix以其稳定性和高性能,深受...
在AIX操作系统上安装Informix数据库需要遵循一系列步骤,确保系统的正确配置和数据库的稳定运行。以下是对标题和描述中涉及的知识点的详细解释: 1. **空间分配**:在安装Informix数据库时,尤其需要注意`phydbs`、...
【Informix 数据库基本操作和常用配置】 Informix 数据库是一种高效、可扩展的关系型数据库管理系统,广泛应用于各种操作系统环境,包括Windows和Linux。本文将详细介绍如何在Windows和Linux环境下进行Informix...
### Informix数据库管理教程知识点概览 #### 一、Informix产品及安装配置 - **Informix产品简介** Informix是由IBM公司推出的一款高性能的关系型数据库管理系统(RDBMS)。它支持多种操作系统环境,如Unix、Linux...
**Informix 数据库常用命令介绍** Informix 是一个高性能、高度可扩展的数据库管理系统,用于支持各种业务应用程序。为了有效地管理和维护 Informix 数据库,熟悉其提供的命令行工具至关重要。以下是一些常用的 ...