Corresponding Parameter Names

The configuration system in Ingres 6.4 differs from that of subsequent releases, so you need to know how the Ingres 6.4 server parameters correspond to the new Ingres parameters.

All corresponding Ingres parameters listed here are found in the DBMS Server component. Ingres parameters that do not have any corresponding Ingres 6.4 parameters are not listed.

Parameters in 6.4 rundbms.opt File

The following table lists Ingres 6.4 parameters and their corresponding parameter names in the new Ingres.

Note: Parameters of type Cache are repeated for each cache page size.

Ingres 6.4 Parameter	Ingres Parameter	Type
active_sessions	active_limit	Derived
cache_name	cache_name
connected_sessions	connect_limit
cpu_statistics	cpu_statistics	Derived
cursors_per_session	cursor_limit
database_count	database_limit	Derived
dblist	database_list	Databases
define	define_address	Derived
dmf.cache_size	dmf_cache_size	Cache, Derived
dmf.count_read_ahead	dmf_group_count	Cache, Derived
dmf.dbcache_size	dmf_db_cache_size
dmf.flimit	dmf_free_limit	Cache, Derived
dmf.memory	dmf_memory	Cache, Derived
dmf.mlimit	dmf_modify_limit	Cache, Derived
dmf.scanfactor	dmf_scan_factor	Cache
dmf.size_read_ahead	dmf_group_size	Cache
dmf.tblcache_size	dmf_tbl_cache_size
dmf.tcb_hash	dmf_hash_size
dmf.wbend	dmf_wb_end	Cache, Derived
dmf.wbstart	dmf_wb_start	Cache, Derived
events	event_limit
fast_commit	fast_commit	Derived
flatten	query_flattening (ON)
image	image_name
maximum_working_set	unix_maximum_working_set
names	name_service (ON)
noflatten	query_flattening (OFF)
nonames	name_service (OFF)
opf.active	opf_active_limit	Derived
opf.aggregate_flatten	qflatten_aggregate (ON)	Derived
opf.complete	opf_complete (ON)
opf.cpufactor	opf_cpu_factor
opf.exactkey	opf_exact_key
opf.memory	opf_memory	Derived
opf.noaggregate_flatten	qflatten_aggregate (ON)	Derived
opf.nocomplete	opf_complete (OFF)
opf.nonkey	opf_non_key
opf.rangekey	opf_range_key
opf.repeatfactor	opf_repeat_factor
opf.sortmax	opf_sort_max
opf.timeoutfactor	opf_timeout_factor
priority	unix_priority
psf.memory	psf_memory	Derived
qef.qep_size	qef_qep_mem
qef.sort_size	qef_sort_mem
qsf.pool_size	qsf_memory	Derived
quantum	quantum_size
rdf.max_tbls	rdf_max_tbls
rdf.memory	rdf_memory	Derived
rdf.tbl_cols	rdf_tbl_cols
rdf.tbl_idxs	rdf_tbl_idxs
rule_depth	rule_depth
scf.row_estimate	scf_rows
server_class	server_class
session_accounting	session_accounting
shared_cache	cache_sharing (ON)
sole_cache	cache_sharing (OFF)
sole_server	sole_server	Derived
stack_size	stack_size
write_behind	dmf_write_behind (see notes)	Cache

Notes on Specific DBMS Server Parameters

Note the following:

The 6.4 QEF sorting algorithm is unsuited to large qef_sort_mem settings. All recent Ingres versions use a different sort that does not degrade with large qef_sort_mem settings. The 6.4 standard setting is much smaller than the Ingres default.
Recent Ingres versions typically require significantly less qsf_memory than Ingres 6.4 does, perhaps as little as half. After upgrading, start with the same qsf_memory setting as Ingres 6.4, but monitor QSF memory usage with trace point QS501 and tune qsf_memory appropriately.
The quantum_size parameter in an internal threads (slaves) installation is often set to a small number (50 to 100) to improve responsiveness. Quantum_size has a different meaning in an OS threads installation, where it should not be set to less than 300, or excessive polling of the session communications channel will occur. A quantum_size of 1000 is usually appropriate when OS threads are in use.
The 6.4 write_behind parameter is a thread count. Starting with 2.5, the dmf_write_behind parameter is simply ON or OFF, and the server dynamically allocates threads. Prior to Ingres II 2.5, the write_behind parameter means the same as it did in 6.4.
A stack_size of 64 KB is typical with 6.4. Recent Ingres versions use more stack, so the stack size should be set to 128 KB (or more, if sporadic session failures occur).
6.4 VMS installations can have a few additional non-UNIX parameters, which have the same or almost the same names in recent Ingres versions.

Locking and Logging System Parameters

These parameters are set with iistartup -init, or rcpconfig, in Ingres 6.4.

Ingres 6.4 Parameter	Ingres Parameter	Type
Log buffers in memory	buffer_count	Log
Transactions in the logging system	tx_limit	Log, Derived
Databases in the logging system	database_limit	Log, Derived
Maximum C.P. interval for invoking the archiver	archiver_interval	Log, Derived
Block size of the log file	block_size	Log
Log-full limit	full_limit	Log
Percentage of log for consistency point	cp_interval	Log, Derived
Force-abort limit	force_abort_limit	Log, Derived
Size of the lock hash table	hash_size	Lock, Derived
Size of the resource hash table	resource_hash	Lock, Derived
Maximum number of locks in the locking system	lock_limit	Lock, Derived
Maximum number of lock lists	list_limit	Lock, Derived
Maximum number of locks per transaction	per_tx_limit	Lock

Notes on Specific Logging and Locking Parameters

Note the following:

There is no 6.4 equivalent to the Ingres log_writer parameter. Although the log_writer default is 1, it is usually advantageous to start your Ingres installation with log_writer set to 4 or 5. If you are using dual logging, double the setting.
The default rule for computing lock_limit (and the new parameter resource_limit) tend to compute very high numbers-hundreds of thousands, or more. You can allow more locks than you did in 6.4. As an initial setting, a doubling of lock_limit is usually more than sufficient.
Ingres 2006 requires at least 35 log buffers. The install or upgrade will raise the log buffer count to a minimum of 35.
Configurator may compute a different archiver_interval than you used in 6.4. Carry over the 6.4 setting.