Informix training materials
Chapter 1 Informix Overview
Informix Product Overview
1. Server product
Informix-se
Informix-online
2. Connection product
Informix-Net
Informix-Start
3. Application development and running tools
Informix-4GL
Informix-SQL
Informix-ESQL / C
Informix-menus
Informix-OpenCase
Wingz
Chapter II Informix Online Database Server End Product Installation
One. Establish Informix Group and Informix users
On SCO OpenServer 5.0:
Use the SCOADMIN command to establish Informix group and Informix users
Scoadminàaccountàgroupàadd
Scoadminàaccountàuseràadd
Note: Informix group number is greater than 100
The Informix user number should be greater than 100, and the user belongs to the Informix group.
two. Install Informix Database Product
l Register with root and set the installed environment variable
Informixdir = / usr / informix
Export Informixdir
PATH = $ PATH: $ informixdir / bin
Export Path
And change the current directory to / usr / informix
# Cd $ informixdir
l Insert the SQL CD into the optical drive
# Mount / dev / cdrom / mnt
# Cpio -icuvdmb
# ./Installsql
Informix-SQL Version 7.23.uc1
CopyRight (C) 1984-1997 Informix Software, Inc.
Installation Script
This Installation Procedure Must Be Run By Root (Super-User).
IT Will Change The Owner, Group, And Mode of All Files of this
Package in this Directory. There Must Be a User "Informix" and A
Group "Informix" known to the system.
Press Return to Continue,
Or the interrupt key (usually ctrl-c or del) TO ABORT.
ENTER Your Serial Number (for Example, INF # x999999)>
INF # x999999
Enter your serial number key (Uppercase Letters ONLY>
Aaabbb
Warning!
This Software, And ITS Authorized Use and Number of Users, Area
Subject to the applicable license agreement with Informix Software, Inc.
If the number of users exceedes the licensed number, The Excess Users MAY
Be prevented from using the software. unauthorized use OR COPYING MAY
Subject You and Your Company to Severe Civil and Criminal Liabilities.
Press Return to Continue, or The Interrupt Key (USUALLY CTRL-C Or Del) To Abort.
Installation of Informix-SQL Complete.
l Continue to install ESQL / C, 4GL, ONLINE, etc.
Chapter III Informix Online Database Server System Architecture
The Informix-Online dynamic server is implemented using a multi-cable architecture, which means that only less process complete database activity, but also means that a database process can be more than one application service in a clue form. It is often referred to as a set of processes for database servers. As needed, you can dynamically allocate a process for the database server, which is called a dynamic server.
Multi-line architecture can also have better scalability. This means that when more users are added, the database server only requires a small amount of additional resources, which is benefited from the efficiency of the multi-cable server to achieve essential scalability.
One. Process structure
The process structure forms a database server.
1. Virtual Processor: The process of forming a database server is called a virtual processor (VP). In the UNIX system, these processes are OnNit.
2. Virtual Processor Class: Each virtual processor data is a virtual processor class. The so-called virtual processor class is a set of processes to complete specific tasks.
two. Shared memory
1. Resident sections: including buffer pools and other system information. This part of the resident physical memory can be configured. Use is the data of the buffer buffer database table.
l buffer pool: data used to buffer disk
l Log Buffer: In order to reduce the physical I / O of the maintenance log, first write in the log buffer when writing the log, refresh to disk over a period of time
l Lrus: Online is tracked by some of the pointers connected together, called the LUN queue. Its function is to find the buffer to store the page when the data page is shared from the disk.
2. Virtual part
l Tracking session data: Each session stores its private data in its own memory pool, the name of the session pool is the user's session number, when the user is connected to the online connection, Online is assigned a unique session number, while the user exits When the ONLINE system, its session pool will be released
l Buffet data dictionary information: Data Dictionary Pool Buffer System Directory Table Information. When the data server reads the data page containing the system directory, in order to make the information of the access table more efficient, the database server stores them in a structure of shared memory. This structure is part of the shared memory dictionary buffer pool. Subsequent users can access the structure directly in the shared memory to get information about the table, resulting in time and memory.
l Storage Process Buffer: Used to buffer stored procedures. When a session is first necessary to use a stored procedure, the database server reads the system directory to retrieve storage process code, then convert these code into executable form, and store it in the virtual portion, once the stored procedure is buffered, its retrieval And execution ratio is much more effective in the system catalog table on the disk.
l Cluster information: The MT pool contains a clue stack, and some structures used by control clues.
l Sort: Temporary space allocated for sorting.
l Large buffer: Online's AIO VP uses a large buffer to write a larger page block to the disk.
l Global information: Some other information that is not a session is stored in the global pool.
3. Message part
Includes some messaging buffers, mainly used for local customers to communicate with the ONLINE system through shared memory. The client puts its request message in the message section, and takes the processing result of the ONLINE system from that section. Each user who accesses the ONLINE system in a shared memory requires about 12K message section.
three. Disk part
1. Chunks: It is a continuous physical space on disk, and Online data is finally stored here, we can set the number and size of Chunk. Therefore, Chunk is the physical storage entity of Online. 2. Page: The basic I / O unit used by INFORMIX-ONLINE is a page. All data is stored in the page. The size of the page is different from the computer and is not changeable.
3. Extent: It is a physical continuous page on the disk, and the space is assigned by EXTENT, and the Extent size of a table is described when the table is created.
4. Dbspace: It is a logical collection of a group of Chunk stores databases and tables. Each DBSpace is at least with a Chunk called an initial chunk. Dbspace can allocate anything more than a lot of CHUNK as needed. If you complete a space on a DBSpace, you can continue to assign new Chunk for it.
5. TBLSPACE: It is a logical collection assigned to a table, and a TBLSPACE can include one or more extents. The space of TBLSpace is not necessarily continuous, while an EXTENT internal space must be continuous.
6. Blobspace: When Online uses Byte and Text Data Types, BLOBSPACE is stored in Blobspace, which is a logical collection of Chunk. They are specifically used to store BLOB data types, data lines and indexes are not discharged in Blobspace, only store BLOV page and Related BLOB System Information Page.
7. Logical log: There is a number of logical log files on the disk, which is used to store transaction log information for all databases, which is reused. At least 3 logical logs, when initialization, they are placed in the root DBSPACE.
8. Physical Log: It is a continuous disk space in the Online system that contains a front image of the page modified since the checkpoint. Mainly used for fault-tolerant recovery mechanisms, which are also used for online backups, which are internal components of all Online systems.
Chapter 4 Informix Online Database Server Parameter Configuration and Initialization
One. Preparation for operating system
1. Store data to Online to allocate disk space
l Online data storage space with UNIX file
l Features: This way is convenient, simple, but low efficiency, not high security
Steps: Create a file in / usr / informix directory infordbs
As the storage space of Online
Root registration
# CD / usr / informix
# Cat / dev / null> Infordbs
# Chmod 664 infordbs
# Chown Informix Infordbs
# Chgrp informix infordbs
l Use the original disk space as an online data storage space
Features: This method is high, good security, but pay attention to installation
When operating the system, some disk space must be reserved, and
Formatting, you should also know the device name of the disk space and
size of space
Step: Setting / dev / rdsk / 0s2 to reserved the original
disk space
Root registration
# Chmod 664 / dev / rdsk / 0s2
# Chown Informix / DEV / RDSK / 0S2
# Chgrp informix / dev / rdsk / 0s2
2. Adjust UNIX core parameters
l In the SCO UNIX platform, INFORMIX online7 needs to adjust the following parameters:
Shared memory parameters: SHMMAX: 204800000 (the length of the maximum shared memory segment)
SHMMIN: 1
(The length of the minimum shared memory segment)
SHMALL: 512
(The maximum number of shared memory text segments)
SHMMNI: 100
(The maximum number of shared memory representations in the same existing
SHMSEG: 10
(The number of shared memory segments can be connected to each process)
Signal light parameter: SEMMAP: 8192
(Number of items in the control switch used by the signal light set)
Semmni: 8192
(The maximum number of signal lights)
Semmns: 8192
(Number of signal lights)
SemMnu: 100
(Number of UNDO data structure)
SEMMSL: 150
(The maximum number of signal lights for each signal light)
Clock parameters: ncall: 2048
(Define the number of output outgoing items, each entry indicates a function that is later to be called by the core clock processing program)
Process and memory parameters: NPROC: 2000
(Define the maximum number of processes allowed in the system)
MAXUP: 2048
(The system allows the number of non-super user processes at the same time)
Maxumem: 524283
(Define the user's maximum virtual address space in the page)
l How to operate:
a. Use the system management menu command:
SCOADMIN → Hardware / kernal Manager →
After listing the menu, select 9 Modify the shared memory parameters, select 8 Modify the signal light parameter, re-construct the UNIX core after setting, and restart the UNIX system.
b. Use the shell command to modify the core parameters:
# / Etc / conf / bin / idtune shmmax 134217728
# / Etc / conf / bin / idtune shmmin 1
# / Etc / conf / bin / idtune shmall 512
# / Etc / conf / bin / idtune shmseg 10
......
# / Etc / conf / bin / idbuild
# Reboot
Note: If the parameter exceeds the system to allow the maximum value, you should modify it.
/etc/conf/cf.d/mtune file, the maximum allowed system
The value is large, and the core is recombined.
two. Client / Server configuration
1. Set an environment variable
Set environment variables in /usr/informix/.profile file
Informixdir = / usr / informix
PATH = $ PATH: $ informixdir / bin
OnConfig = onconfig.bank
InformixServer = Bank_Online
Export Informixdir Path OnConfig InformixServer
2. Set the system hostname
View / etc / hosts file to determine the host name
3. Set the network service name
Root registration
Use VI to modify / etc / services files, join
SQL1 7000 / TCP
4. Prepare connection files SQLHOSTS
INFORMIX registration
$ CD / USR / INFORMIX / ETC
$ VI SQLHOSTS
DBSERVERNAME NETTYPE HOSTNAME SERVICENAMEONLINE_SHM ONIPCSHM BANK SQL1
Where: dbservername: The database server name specified by the Informix Server environment variable.
NetType: Describes the type of customer and database server connection
l Two characters represent database server products
* SE: Represents Informix-SE
* ON: Represents the Informix-Online Dynamic Server
* GW: Represents Informix-Gateway with DRDA
l Intermediate three characters indicate that the internal programming interface connection type allowed for communication
* IPC: Represents a communication (IPC) connection based on UNIX, only for local loopback connection
* TLI: Indicates the network interface of the transport layer interface (TLI) for local loopback connection and remote host connection.
* SOC: Represents a network interface of the socket type for local loopback connections and remote strains
l The last three characters represent a specific IPC mechanism or network protocol
* Pip: Indicates unnamed pipeline, only for local connection
* TCP: Represents TCP / IP protocol for network connection
* SPX: Represents IPX / SPX protocol, used for network connection
Hostname: Specifies the computer where the database server is located
ServiceName: Depending on the type of network connection specified in NetType
three. Initialization configuration
1. Prepare an onconfig configuration file
INFORMIX registration
$ CD / USR / INFORMIX / ETC
$ C onconfig.std onconfig.bank
2. Register with Informix and use the management command onMonitor to configure the online parameter.
3. Use the VI to modify the parameters in the onconfig.bank file.
Related files onconfig.bank content (see attachment)
Use the command to launch Online and initialize disk space
$ TBINIT -IY (5.0) $ oninit -iy (7.0)
Note: Perform this command, all the data on the online disk space will be destroyed, which can only be used in the first initialization of the online disk space.
four. Start and close
1. Launch Online
l Start online command: OnIit
Syntax: oninit [-i] [- p] [- s] [- y]
Description: Generate an OnInit process to monitor online processes
Option: -i Specifies the initialization disk space
-p does not search and delete a temporary table when initializing shared memory space
-s Let Online are in still a static manner after initialization
-y automatically responds to all prompt information 'yes'
l Start ONLINE when operating system boots
In the /etc/rc2.d directory, establish the online boot file named S90infor, the content is as follows:
Informixdir = / usr / informix
PATH = $ PATH: $ informixdir / bin
OnConfig = onconfig.bank
InformixServer = Bank_Online
Export Informixdir Path Oncofnig Informix Server
Oninit
2. Close ONLINE
l Close online command: onmode
Syntax: onmode [-kmsuycnr]
Description: Change mode and shared memory
Options: -y automatically answers 'Yes' for all prompt information
-k Mobile Online shares memory space and makes the ONLINE becomes an online way
-s prohibits new access to Online, but allows the current processing process to complete
-u Termination of the current handling so that online is still in a stationary method
-c mandatory checkpoint
-n immediately terminated the online sharing memory used for the conversation, but does not affect the mandatory memory parameters in the configuration file
-r Instantly starts Online sharing memory forced residential, but does not affect the mandatory memory parameters in the configuration file
l Automatically turn off online when the system is turned off.
In the /etc/rc0.d directory, establish a shutdown file K01Infor, the content is as follows:
Informixdir = / usr / informix
PATH = $ PATH: $ informixdir / bin
OnConfig = onconfig.bank
InformixServer = Bank_Online
Export Informixdir Path OnConfig InformixServer
Onmode -ky
Chapter 5 Informix Online Database Server Daily Management and Maintenance
One. Operation mode management
1. ONLINE operational status
l Off-line: Online system has no mode, and the shared memory has not been assigned.
l Initialization: Online system performs initialization and transforms from the OFF-LINE mode to the Quiescent mode.
l Quiescent: Online has started, shared memory has been assigned, but the system does not allow users to access, and only system administrators can access the system.
l On-line: The system has started and allows the user to access, which is the normal mode of the Online system.
l Shutdown: The system is running, and the current user continues to access the database, but new users are not allowed.
l Recovery: The system is recovered quickly or from the tape for system recovery.
2. State change
l oninit command
Syntax: oninit [-i] [- p] [- s] [- y]
OnInit -i specifies the initialization disk space
OnInit -p does not search and delete a temporary table when initializing the shared memory space
OnInit -s makes online after initialization
OnInit -y automatically responds to all prompt information 'yes'
l onmode command
Grammar: Onmode [-k] [- M] [- S] [- u] [- y]
OnMode -y automatically answers all prompt information 'Yes'
Onmode -k Mobile Online shares memory space and makes it offline
Onmode -m makes the online way becomes online
Onmode -s prohibits new access to Online, but allows the current processing process to complete
OnMode -u terminates the current process so that online is still in a stationary method.
two. Disk space management
1) CHUNK and DBSPACE
l Chunk: It is a continuous physical space on the disk, and Online data is finally stored here, we can set the number and size of Chunk. Therefore, Chunk is the physical storage entity of Online.
l Dbspace: It is a logically concept that is actually combined by one or more Chunk, so each DBSPACE contains at least one Chunk to store data.
l CHUNK and DBSPACE
When we establish a database or table, it is not directly established on dbspace, library, or table, stored in DBSPACE directly, and the data is finally placed on the dbspace which CHUNK is finally placed. The internal itself decides. When CHUNK in dbspace is full, you can add new Chunk. 2) CHUNK and DBSPACE
l In general, three dbspace should be established on the original disk device.
Rootdbs: Online Initialization is the default.
Workdbs: Store application system database data.
TMPDBS: Store system temporary file data.
l Rootdbs: ONLINE is initialized, a DBSpace called rootdbs is automatically established. This rootdbs stores ONLINE management information, including physical logs, logical logs, and more. When a database or table is established, if DBSpace is not specified, the database or table is built in RootDBS, so the library or table must be set in a DBSPACE, and the DBSpace name must be specified in the SQL statement.
l Attach CHUNK or DBSPACE, specify the original disk device name path, the required disk space size, and the offset of the block disk space in the original disk device. Among them, the offset is very critical, be careful, otherwise it is easy to cause overlapping and overlapping between the CHUNK block.
For example: assume the original disk device / dev / rdsk / 0s2 has 500m empty
Among them, Rootdbs uses to go to the first 100m if they want to be in / dev / rdsk /
A new DBSPACE offset should be more than 100m in 0S2.
l Use the onspaces command to establish dbspace and chunk
Syntax: onspace -c -d database name -P device file name
-o offset-S size
Onspace -a database name -P device file name
-o offset-S size
Options: -c Create a new DBSPACE
-d dbspace name
-a Add a CHUNK for the specified dbspace
-P original disk device full path name / dev / rdsk / 0s2
-o offset, in k byte
-s chunk size, in k byte
E.g:
Onspace -c -d Workdbs -P / DEV / RDSK / 0S2 -O 100000 -s 100000
Onspace -c -d tmpdbs -p / dev / rdsk / 0s2 -o 200000 -s 100000
Onspace -a Workdbs -P / DEV / RDSK / 0S2 -O 100000 -s 100000
three. Log management
1. Database log method
l includes: no log method
No buffer method
Belt buffer method
Compliance with ANSI standard log
Note: Informix recommends using a bicycle log approach to ensure that the transaction will not be lost, the database transaction log information is recorded in the /usr/informix/online.log file, usually view the online.log file information file, check the database Abnormal, and empty the files regularly to prevent the files from being too difficult to view.
l log method conversion
Use the ontape command
Format: ontape -s [-u | -n | -b] Database name
Options: -s Represents Archive
-U Open the database log, the log mode is a non-buffer mode
-N changed the database to no log method
-B Open the database log, log mode is a buffer method
2. Physical log management
Physical log saves data before modifying, its location and size can be changed
Use the command onparams to change the location and size of the physical log
Format: onparams -p -s size -d dbspace -y option :-P Represents physical log
-S new size, the size of the physical log of the K byte
-d explains the DBSPACE name of the physical log
-y to all questions to answer 'yes'
Note: After the ONLINE enters the static mode
The space assigned to the physical log must be continuous, so make sure that DBSpace has enough space before changing the physical log.
3. Logical log management
Logical log saves data in modified images
The size of the logical log space is the product of the number of logical log files and the logical log file.
After Online is initialized, the size of the logical log file is not modified, to change the logical log space size, only to modify the number of logical log files
The newly added logical log file size can be set to a new value, and the number of logical log files must not be less than 3
Use the command onparams to increase logical logs
l format: onparams -a -d rootdbs [-s size]
Options: -a Add a logical file
-S log size
Note: The newly added logical file is A (add), and the new logical log file can be used after the 0-level backup of rootdbs is established.
l Use the command onparams to cancel the log file
Format: onparams -d -l logid
Note: Before canceling a logical log file, you must do RootDBS 0-level backup.
Only logical log files (free) or A (add) logical log files can be canceled
four. Database backup and recovery
Content and purpose:
a. Data Backup: Back up the data status of a moment of a database, which is used to recover the system when the system appears.
b. Logical log backup: After the logical log file is full, you must back up before it can be emptied, continue to use, if all logical log files are filled, the system crashes. In addition, the logical log records a change in the database after the last data backup, and therefore, the logical log is also used to recover the system when the system occurs.
1. data backup
l Online provides a level 0, level 1, level 2 incremental backup
0 level: backup the entire database system
Level 1: Backup data that changes from 0 backup
Level 2: Backup data from changing from level 1 backup
l Use the ontape command backup data
Ontape -S
The system displays the input 0, 1, 2 backup level
l Before the entire system is officially run, do a 0-level backup, you should do data backup after the business system is completed, if the amount of data is not large, you can do a 0-level backup every day.
l Manage the backup tape, make a tag, such as: Date, time, backup level, the logical log number included
2. Logistic log file backup
l Timing backup logical log
Timed logical log file backup, the system only backs up the written logical log file to the tape, then fails to free and release these files. When you do schedule, you must do it before all logical log files are written, so if you use a timing backup, you should observe the logical log usage. Spirit, if you often have everything, you should avoid using timed backups, and use continuous backups to be more secure.
Command format: Ontape -a
l Continuous backup logical log
Continuous backup The logical log file is filled with one, then the backup, then the log file is unconfilled, so it is necessary to make a continuous backup, and there must be a tape in the tape drive. Continuous backups need to occupy a screen or terminal display information. When the magnetic tape is full, the system will be prompted to replace the tape.
Command format: ontape -c
Note: Informix recommends using a continuous backup, but continuous backup will always take a tape drive, if there is two tape drives, you can use as a physical log backup and logical log backup, if there is only one tape drive, it will conflict with data backup Replace the tape in time. 3. system recovery
When the system has an error, or if you want to restore the system to data for a point in time, you must use the data backup belt and the logical log backup to recover the system.
Data backups restore the system to the time point data status of the data backup, and the logical log backup can restore the system to the data state after the data backup time point.
Command format: ontape -r
According to the system prompt, recover the logical log after the last 0, 1, 2 data backup and data backups.
Chapter 6 Informix Online Monitoring and Utility
One. Monitor database status command onstat
Format: onstat [-abdghklmpstuzbdfrx] [- i] [- r seconds] [- o File] [Infile]
Description: Check the ONLINE operational status
Options: -A All information
-b buffer
-C system configuration
-d dbspace and chunks information
-g multi-line command
-i interactive mode
-H buffer hash link table
-k lock
-l log
-M message log
-P profile information
-s latch information
-t tblspaces information
-u user clue information
-z profile statistics
-B All buffer information
-C btree cleaning request
-D dbspace and chunks status
-R Lru queue
-X transaction information
-X buffer use and wait
-R repeat per n second
-o will share the memory to the specified file (default is onstat.out)
two. Check and fix the database command oncheck
Format: oncheck [clist] [- PLIST] [- QNY] [{Database [: [oowner.] Table] | TBLSPACE NUMBER | Chunk Number} {RowID | Page Number}]
Description: Check and restore the consistency and integrity of online database disk space, database, table, index, etc.
Options: -c check
R Reserved Page
e extents
C database directory [Database]
i Table index Database [: [oowner.] table]
I Table Indexes and Rowid Database [: [Owner.] Table]
R table index and recording check (must have I or I option)
D tblspace data record, including bitmap page Database [: [oowner.] table]
D tblspace data record, contain bitmap page, farewell page and blob page
Database [: [oowner.] TABLE]
-p display
R Reserved Page (-CR)
e extent report (-ce)
C Directory Report (-CC) [Database]
Keys (-CI) Database in K index [: [oowner.] table]
Keys and RowId (-CI) Database [: [Owner.] Table]
l Key (-CI) Database [: [owner.] table]
L Key and RowId (CI) Database [: [Owner. [Table]
D TBLSPACE Data Record (-CD)
D TBLSPACE Data Record (-CD), contains bitmap page, f minute page and blob page
Database [: [oowner.] Table] [Page Number]
T TBLspace Report Database [: [oowner.] TABLE]
T TBLSPACE Disk Usage Report Database [: [oowner.] Table] P Uplift the specified disk page according to the table and page
[Table and RowID | TBLSPACE AND PAGE NUMBER]
P Remove the disk page according to CHUNK and page number [Chunk Number and Page Number]
B Specify the spatial usage of the blobspace of the table
-Q stationary mode, only display error information
-n answers NO to all questions
-y answered all questions Yes
annex:
# 根 d dbspace configuration
Rootname rootdbs # root dbspace name
Rootpath / dev / rdsk / 0s2 #Path with DBSpace devices
Rootoffset 0 # Root DBSPACE offset in the device
Rootsize 1000000 # Size of DBSPACE (KB)
# Disk mirror configuration
Mirror 0 # Mirror Tag (YES = 1, NO = 0)
MirrorPath # contains root DBSPACE mirror device path
Mirroroffset 0 # Offset in the mirroring device (KB)
# 体动 log configuration
Physdbs rootdbs # contains DBSpace names for physical logs
Physfile 50000 # Size of physical log file (KB)
(Note: The total disk space occupied by the physical log and the logical log is about 20% of the online DBSPACE, the ratio of logical logs and physical log space is 3: 1)
# 日 配置
Logfiles 6 # logical log file number
Logsize 25000 # Size of each logical log (KB)
# Message file
Msgpath /usr/informix/online.log #OLINNE message log path name
Console / Dev / Console # System Console Message Path Name
#Archive tape equipment
TapeDev / dev / Rstp0 #archive tape device path name
Tapeblk 1024 #archive Tape Block Size (KB)
TapeSize 150000 # Maximum amount of data available for tape (KB)
# Log backup tape device
LTAPEDEV / DEV / RSTP0 # logical log tape device path name
LTAPEBLK 1024 # logical log tape block size (KB)
LTapeSize 150000 # log tape can accommodate maximum data
# Identifier parameter
ServerNum 0 # The only ID of the online instance
DBSERVERNAME PICC_OONLINE # The only name of the Online instance
# Share memory parameters
Resident 0 # Enforcer (Yes = 1, NO = 0)
User $ 20 # concurrent user process
(Note: The number of system user processes Cleaners 4 = User value)
Transactions 20 # The biggest number of concurrent transactions
(Note: Minimum = User value, usually default)
Locks 2000 # Maximum number of locks
(Note: Small impact on shared memory, minimum is 20 locks per user)
Buffers 200 # shared memory buffer's maximum number
(Physical Memory * 20% = Buffers * buffsize)
The maximum number of TBLspaces 200 # event TBLspace
(Note: TBLSPACE minimum 10 per user process)
The biggest number of chunks 8 #chunk
(Note: The maximum of the number of chunks takes one of the following two values:
The number of CHUNK entries (path name) that can accommodate the online page
The operating system allows the maximum number of files to be opened for 6)
Dbspaces 8 # dbspace, BLOBSPACE Maximum number
(Note: Is equal to CHUNK value)
Physbuff 32 # Physical log buffer size
(Note: Recommended value = page 16 * buffsize)
Logbuff 32 # logical log buffer size
(Note: Recommended value = page 16 * buffsize)
Logsmax 6 # logical log files for maximum number
(Note: Recommended value = logfile 3)
Cleaners 1 # Page Refresh Process Number
(Note: Recommended value = 1 / per physical device, maximum 8)
SHMBASE 0x400000 # Share memory base site
CKPinitvl 300 # checkpoint time interval (seconds)
Lrus 8 #LRU queue
Lru-Max-Dirty 60 #LRU starts refreshing modification page percentage
Lru-min-dirty 50 #LRU end refresh modification page percentage
LTXHWM 80 # long TX high water mark (percentage)
LTXEHWM 90 # long TX row high water tag (percentage)
# 主 主 主 和 and the parameters of a specific product
(Note: Only use one of the other products of INROMIX to affect the configuration)
DYNS / HMSZ 0 # Dynamic Shared Memory Size
Gtrid-Cmp-SZ 32 #Gtrid compares the number of bytes used
DeadLock-Timeout 60 # distributed environment waiting lock for the longest time
TXTIMEOUT 300 I-STAR's transaction
SPINCNT 0 # process application LATCH
Stageblob # Informix-Online
/ CD staging area
# The size of the system page
Buffsize 2 # page size (cannot be modified)
