- 论坛徽章:
- 0
|
我只弄了前边的核心参数的部分，有兴趣的兄弟把他补齐吧……
我这里的问题我标出来了
大家帮忙解释一下
E文太烂，大家原谅
- =================================
- MACHINE SPECIFIC NOTES
- FOR
- Informix Dynamic Server 7.31.UC2 PRODUCT RELEASE
- DATE: 18 May 1999
- =================================
- PORT NUMBER: 025581 (8MM CASSETTE) 025585 (DAT CARTRIDGE) 025577 (TAPE CARTRIDGE) 025589 (CD ROM)
- IRIS JOB NUMBER: 18833
- INFORMIX-OnLine Shared Memory Parameters (in Bytes):
- 共享内存参数（单位：字节）
- ===================================================
- SHMMAX: 409600000
- SHMMIN: 1
- SHMALL: 512
- SHMMNI: 100
- SHMSEG: 6
- LOCATION OF SHARED MEMORY:
- =========================
- SHMBASE 0x82000000L
- 谁知道这个是什么意思？？？
- Kernel Parameters recommended for Informix ONLINE:
- 推荐的核心参数设置
- ==================================================
- MAXUMEM:524287
- SEMMNI: 8192
- SEMMNS: 8192
- SEMMAP: 8192
- SEMMNU: 100
- SEMMSL: 25
- Kernel Parameters that might have to be changed
- depending on the Online configuration:
- 核心参数的更改必须依赖ONLINE的配置（这个是个大问题：对应关系是什么呢？？？那个TLI是什么东东？？？）
- ======================================
- MAXUP
- SEMMNI
- SEMMNS
- SEMMSL
- NFILE
- For TLI:
- NSTREAM
- NQUEUE
- NUMTIM
- NUMTRW
- Increasing the Number of SPX connections: Increase SPX_MAX_CONNECTIONS in
- /etc/conf/pack.d/spx/spx_tune.h
- (Related parameter is SPX_MAX_SOCKETS
- in /etc/conf/pack.d/ipx/ipx_tune.h)
- (上边的这一串到底应该如何翻译啊？？？)
- Machine Specific Notes:
- =======================
- 1. The following protocol(s)/interface(s) are supported on this platform:
- 平台支持下列协议或接口
- TLI using TCP/IP
- TLI using IPX/SPX
-
- To use TCP/IP, the NETTYPE in the ONCONFIG file and the nettype field
- in the sqlhosts file entry must contain "ontlitcp".
- 使用TCP/IP，sqlhosts文件的nettype字段必须设置成"ontlitcp"
- To use IPX/SPX, the NETTYPE in the ONCONFIG file and the nettype field
- in the sqlhosts file entry must contain "ontlispx".
- 使用TCP/IP，sqlhosts文件的nettype字段必须设置成"ontlispx"
- 2. On-Archive tape drivers:
- On-Archive has been tested on SCO OpenServer Release 5.0.5 with
- a 4mm DAT tape drive. It is only possible (at the time of release)
- to archive a single saveset per tape.
- To use onarchive to tape you should set compat mode = 0 in
- /etc/conf/pack.d/Stp/space.c and use a rewind device ie /dev/rmt/c0s0
- On older versions of the OS (5.0.0, 5.0.2) you may need to consult with
- SCO to get archiving to work.
- 3. TERMINFO is supported on this platform.
-
- 4. The Affinity feature, which allows the pinning of a CPU VP process to a
- processor in a multi-cpu configuration, is supported on this platform. This
- feature can be activated through the two ONCONFIG parameters AFF_SPROC
- and AFF_NPROCS.
- 5. The no aging feature that disables priority aging of CPU virtual
- processors by the operating system is supported on this port. This
- feature can be activated through the onconfig parameter NOAGE.
- 6. OS Auditing(Operation System Auditing) is supported and the related
- information is given below:
- To record INFORMIX-OnLine audit records in the OS audit log,
- a) user "informix" must have writeaudit privilege; To do so, run
- scoadmin to give user "informix" writeaudit privilege.
- b) user "informix" and group "informix" must be in the list of users
- and groups audited by OS. Run auditsh to add user "informix" and
- group "informix" in these user/group lists. Due to a current SCO
- bug in auditsh, individual users and groups cannot be entered.
- The workaround is to audit all users, by entering a space instead
- of a user name.
- c) INFORMIX OnLine uses "Audit Subsystem Events" to write INFORMIX
- OnLine audit records. Run auditsh to turn on "Audit Subsystem Events".
- Due to a current bug in SCO auditsh, all the events should be audited
- in order to audit Audit Subsystem Events.
- To select which INFORMIX-OnLine events are to be audited, specify audit
- masks by using the "onaudit" utility. To extract INFORMIX OnLine audit
- records from the operating system audit trail, use "onshowaudit -O".
- Refer to the INFORMIX-OnLine Trusted Facility Manual (TFM) and SCO Operating
- system documentation for further details.
- 7. The DB/Cockpit DBA monitoring tool is not available on this platform.
- 8. Kernel Asynchronous I/O (KAIO) is supported on this platform. However, it
- is DISABLED by default. To enable KAIO set the environment variable
- KAIOON. It is only effective on raw partitions.
- KAIOON=1; export KAIOON (for Bourne or Korn Shell)
-
- setenv KAIOON 1 (for C Shell)
-
- The following is a pre-requisite for using KAIO:
- - SCO AIO driver "aio" is installed and enabled.
- - SCO driver "suds" is installed and enabled.
- For information on how to install and enable driver "aio" and "suds",
- please check with your System Administrator.
- Limitation of SCO's KAIO Implementation:
- - Since SCO tries to optimize shared memory allocation for
- asynchronous I/O, it will attempt to allocate physically contiguous
- memory, lock the memory segment in the physical memory, and mark it
- for use by KAIO routines. Once the memory segment is locked, it
- can not be chosen for "pageout" by the Operating System. Therefore,
- there is a chance that the system will run out of memory. Of course,
- it depends on how large the memory is and how many processes are
- running on the system.
- To overcome the above limitation, you could either stop and restart
- the server -OR- just not enable the KAIO by NOT setting the KAIOON
- flag as suggested above. If KAIOON is already set, unset KAIOON
- environment variable, and stop and restart the server.
- - If the server is brought up with "KAIOON" and the client does not
- know about it, there is a slight chance that onstat will not work
- properly.
-
- Table 1: Relation of Onstat and Oninit with KAIO On or Off
- | KAIO | KAIO | KAIO | KAIO
- -------------------------------------
- oninit | ON | OFF | ON | OFF
- (server) | | | |
- -------------------------------------
- onstat | ON | OFF | OFF | ON
- (client) | | | |
- -------------------------------------
- error from onstat | NO | NO | NO | YES
- 9. The High Performance Loader is supported on this platform. The loader
- utilities, onpload and ipload, require minimum of 35 MB of memory and
- 70 MB of swap space in order to run.
- User-defined conversion routines must be provided in a dynamic,
- shared library called ipldd07a.so. This library must be located
- in /usr/lib (or must have a link provided in /usr/lib).
- 10. The Informix network shared libraries are not supported.
- 11. Shared memory residency is supported on this platfrom.
- 12. If the OnLine server and client run on different machines and connect
- to each other through TLITCP, the user thread "sqlexec" on the server
- side will remain alive for tcp_keepidle seconds when the physical
- connection between the two machines is broken. On SCO OpenServer
- Release 5, the value of tcp_keepidle is tunable. (See the onconfig
- man page for details.)
- 13. The Enterprise Replication (CDR) is supported on this platform.
- 14. Some of the functions called by ON-Bar are in a shared library
- supplied by third party storage management vendors. For ON-Bar to
- access the functions, the library has to be installed in one of the
- three ways noted below.
-
- 1. Rename the library to /usr/lib/ibsad001.so.
-
- 2. Create /usr/lib/ibsad001.so as a symbolic link to the library.
-
- 3. Set the BAR_BSALIB_PATH paramter in $INFORMIXDIR/etc/$ONCONFIG
- to the full pathname of the library.
- 15. The point-in-time (PIT) feature of ON-Bar is affected by a problem.
- The workarounds are noted below.
-
- 1. Use adjusted time on the command line. For example to restore
- on September 25 at 14:00 DST in the US/Pacific timezone, use
- the command: onbar -r -t "1996-09-25 13:00:00"
-
- 2. Set the time zone (TZ) environment variable for both the
- ON-Bar and the machine where the server runs accordingly. For
- example, for US/Pacific time zone, TZ must be set to PST8 rather
- than PST8DST7. This precludes the introduction of Daylight
- Savings Time.
-
- 16. The Online SNMP subagent(OnSNMP) is supported with this release.
- On SCO, OnSNMP is based on PEER Network's subagent Development Kit
- release 2.3. The distribution includes the following files installed
- under $INFORMIXDIR:
-
- bin/onsnmp the OnSNMP subagent itself, packaged as a separeate
- process.
-
- bin/onsrvapd the daemon which spawns a subagent for each server it
- discovers.
- snmp/peer/snmpdp PEER Network's master agent.
-
- snmp/peer/CONFIG PEER Network's configuration file.
-
-
- snmp/*V1.mib
- snmp/*V2.mib
- snmp/*.my MIB files defining the instrumentation provided with
- OnSNMP. Files with 'V1' conform to SNMP version 1 and
- share the widest acceptance; files with 'V2' conform
- to SNMP version 2; files with the 'my' extention are
- transitional that may be used as a last resort.
-
- Refer to the installation notes that accompany the master agent for
- more details.
-
- Note: OnSNMP is supported on a host that is running one and only one
- server. If multiple servers are running on the same host, then the
- values returned by the subagent are for the first server. All
- subagents for subsequent servers may fail to start.
- 17. IECC
-
- Informix Enterprise Command Center (IECC).
- IECC ServerAgent is NOT supported for this release on this platform.
- Because of this, only the following Tools within IECC Win NT/95 Client
- can be used against the 7.31 server.
-
- ISM Administrator
- Enterprise Replication
- SQL Editor
-
- For more information on how to configure and use these Tools please refer
- to IECC Tools section within IECC Users Guide. Be sure to also refer
- to IECC Client Release Notes.
- 18. ISM
- Informix Storage Manager version 2.00.UC1 is supported in this
- release. On OpenServer 5.0.5 on 4mm dat devices have been tested.
- To use ISM you must have Stp_compat=1 in /etc/conf/pack.d/Stp/space.c
- and use a non-rewind tape device ie /dev/rmt/c0s0n
- Backup Verification (a RAS utility) is supported on SCO
- when the server is online but not when the server is offline.
- This is documented in bug # 105881.
-
|
|
免费注册
发表于 2003-12-18 11:30
