Frequently Asked Questions on Actian X for Linux
Frequently Asked Questions
I installed Actian X using RPM on the command line but when I start Actian X using ingstart, it fails with "No Ingres servers have been configured to start up." What went wrong?
The setup portion of the installation process is performed by the Ingres service script. After you installed Actian X using the RPM command, you must run the service script, which configures and starts the instance. If you installed Actian X using the install.sh, the instance is started automatically; but if you installed Actian X using the RPM command, the setup must be run manually.
To run the service script, run:
% /sbin/service ingresXX start
where XX is the instance ID.
Alternatively to run the setup without starting the instance run:
%/sbin/service ingresXX configure
For more information, see the Installation Guide.
I notice that Ingres starts automatically when the machine is started. Does it also stop automatically when the machine is shut down?
Yes. The ingstop command is issued when the machine is shut down.
I am having trouble creating databases with the createdb program. The program is issuing error messages. Why?
Make sure that you are not running the “createdb” program that is provided by PostgreSQL. Make sure that the PATH setting for the shell from which you install and start Actian X includes Actian X executable directories before other executable directories.
How do I get the function keys to work with the forms-based Actian X applications on Linux?
The TERM_INGRES environmental variable defines the type of terminal you are using, so that the function keys will work when using the forms-based tools, such as CBF or QBF. On Linux, setting TERM_INGRES to konsolel will work for most terminals.
During installation, the value of TERM_INGRES is set to konsolel. You can change this value if it does not meet your needs.
How can I map function keys PFK1 through PFK4 for an xterm?
Running Actian X in an xterm, set TERM to xterm and set TERM_INGRES to vt100fx. Then use xmodmap to determine and set your function keys. To show current settings, use the command xmodmap –pke . (To determine the syntax for your version of xmodmap, use man xmodmap.)
You will probably find that there are no bindings for KP_F1 through KP_F4; you will need to bind them.
For example: to bind keys Shift+F1 through Shift+F4, create a file “mykeys” that contains:
keycode 67 = F1 KP_F1
keycode 68 = F2 KP_F2
keycode 69 = F3 KP_F3
keycode 70 = F4 KP_F4
Then issue the command:
xmodmap mykeys
Shift+F1 through Shift+F4 will now be defined as PFK1 through PFK4.
Do I need to modify system kernel parameters before running Actian X?
No. Standard kernels and kernels compiled with default values (without modifying the Linux source headers) should provide adequate resources. For additional information, see the Readme file.
You might, however, need to increase the maximum allowable size for shared memory segments. You can do this by running /sbin/sysctl –w kernel.shmmax=<new value> as root. Change is immediate and does not require a reboot.
Actian X will fail to start if any of the kernel parameters do not meet required values. You can check these parameters using the syscheck utility in $II_SYSTEM/ingres/utility, as follows:
syscheck
If syscheck reports any potential problems, use the following to generate a list of suitable parameters:
syscheck –c
The output is in the format expected by /sbin/sysctl. If the output is written to a file, the new values can be applied as follows:
syscheck –c > out.file
/sbin/sysctl –p outfile
What compiler and compiler switches were used to create the Linux version of Actian X? Are additional switches needed for compiling C-language application programs?
Actian X was compiled using the GCC compiler version 4.4.7 with the following switches:
-m64 -fsigned-char -fno-strength-reduce -fno-omit-frame-pointer -Wno-write-strings -D_REENTRANT -DLINUX -D_GNU_SOURCE -DXLIB_ILLEGAL_ACCESS -Werror=missing-prototypes -Werror=implicit-int -Werror=implicit-function-declaration -fPIC -O
Do I need to change the permissions for /dev/kmem to run Actian X on Linux?
No.
When I compile the Fortran code generated by the ESQLF pre-compiler using g77, it fails with 'Unrecognized statement name.....'. Why?
The g77 compiler (which is bundled with many, if not all, Linux distributions) does not support some of the statements that the ESQLF pre-compiler generates. More information is available at gnu.org.
When using alternative Actian X character sets, must I do anything other than setting II_CHARSETXX, to get the characters to display correctly?
If your terminal is using the same character set as Actian X, you should not have a problem. If characters are not displaying correctly, try starting the terminal with a specific character set.
For example, if you are using SHIFTJIS (Japanese Double Byte character set) as the II_CHARSETXX setting in a kterm, start the kterm with the following command:
kterm -km sjis
If you encounter problems using double byte character sets and kterm, try using the rxvt terminal instead. For example, to start the rxvt terminal with the SHIFTJIS character set, issue this command:
rxvt -km sjis