Check for Communications Server Process Errors on UNIX
If the Communications Server process (iigcc) did not start, follow this procedure:
1. Verify that no local environment variables are set in the local user environment that contain the string “GCC”. At the operating system prompt type the command:
BSD:
printent | grep GCC
System V:
env | grep GCC
The Ingres environment variable II_GCNxx_PORT is set in the Ingres symbol table. It is not visible from the UNIX environment using the printenv or env commands, but is visible in the Ingres environment. Verify this by typing ingprenv.
2. Check the value of the Ingres environment variable II_RUN with the following command entered at the operating system prompt:
ingprenv
a. If this machine is running Ingres Net, the value of II_RUN is either “,NET” or “,DBMS, NET”. If the value of the Ingres environment variable II_CLIENT is TRUE, II_RUN is “,NET”. If II_RUN is not set correctly, reset it using the command:
ingsetenv II_RUN ', DBMS, NET'
b. If this machine is an NFS client (that is, does not run a DBMS Server locally) the value of II_RUN is “,NET”. If II_RUN is not set correctly, reset it using the following command entered at the operating system prompt:
ingsetenv II_RUN', NET'
For details on setting environment variables, see the chapter "Setting Environment Variables and Logicals."
3. If you are still having problems, set the following trace to capture diagnostic data and attempt to restart the Communications Server:
Bourne Shell:
II_GCC_TRACE=4
II_GCA_LOG=stdio
export II_GCC_TRACE II_GCA_LOG
iirun iigcc
C Shell:
setenv II_GCC_TRACE 4
setenv II_GCA_LOG stdio
iirun iigcc
4. If you corrected a Communications Server problem, verify that Ingres starts normally:
a. Shut down the partially started installation with the ingstop command.
b. Restart the installation with the ingstart command.
Last modified date: 11/28/2023