4. Setting Environment Variables and Logicals : Installation-Wide Environment Variables : User-Definable Environment Variables and Logicals : Environment Variables and Logicals that Cannot Be Reset
 
Share this page                  
Environment Variables and Logicals that Cannot Be Reset
The following Ingres environment variables and logicals must not be reset by users:
• II_BIND_SVC_xx
• II_C_COMPILER
• II_CHARSETxx
• II_CHECKPOINT
• II_CLIENT
• II_CONFIG
• II_CONNECT_RETRIES
• II_DATABASE
• II_DBMS_LOG
• II_DIRECT_IO
• II_DUMP
• II_ERSEND
• II_GCNxx_PORT
• II_INSTALLATION
• II_JOURNAL
• II_LOG_DEVICE
• II_MSGDIR
• II_NUM_SLAVES
• II_TUXEDO_LOC
• II_TUX_SHARED
• II_TUX_AS_MAX
• II_TUX_XN_MAX
• II_XA_TRACE_FILE
• ING_SYSTEM_SET
UNIX: These environment variables and logicals must not be visible using the env or printenv command.