Other problem: We usually do a SuSE Linux "Default" installation and have never had any other problem than the above, same with the engineers (ours and Oracle). What did happen sometimes that another attempt to start any of the Java GUI tools was needed, but that was rare.

To avoid this, either turn autoextend OFF or at tablespace creation set MAXSIZE to 2147450880 (that is 2GB-32kByte, max. size of a block in Oracle).

Examples for the tablespace creation commands:

   CREATE DATABASE "TEST"
    maxdatafiles 254
    maxinstances 8
    maxlogfiles 32
    character set US7ASCII
    national character set US7ASCII
    DATAFILE '/opt/oracle/oradata/test/system01.dbf' SIZE 200M 
    AUTOEXTEND ON NEXT 640K MAXSIZE 2147450880
    ...
    ...;

  CREATE TABLESPACE "EXAMPLE" 
   DATAFILE '/data/oradata/tst/example01.dbf' SIZE 50M 
   AUTOEXTEND ON NEXT 640K MAXSIZE 2147450880;

Check the settings:

  SELECT file_name,AUTOEXTENSIBLE,to_char(maxbytes,'999999999999') 
  FROM dba_data_files;

Stefan Sels wrote:
I am running Oracle 8.1.17 on Suse 7.1. The listener makes some trouble: It stops working after a minute. If I restart it (lsnctrl stop, lsnctrl start) it works again (for a minute). I did not find a notice in the listener or alert log. Stefan Sels later wrote:
Because I got some respone from people who had the same problem, so here my solution which I found :
It had a relation with the MTS (MultiThreaded Server) stuff in initSID.ora. I commented everything that started wit MTS_ and after a restart of database and listener everything worked fine.

In SuSE Linux the environment variable $LS_COLORS is >256 Bytes in the default configuration. Unsetting this variable solved the problem! It seems there was some buffer overflow somewhere in Oracle.

Add this to your Oracle startup script:
    - Bourne shell: unset LS_COLORS
    - C shell: unsetenv LS_COLORS

Here is what your Pro-C/C++ configuration file $ORACLE_HOME/precomp/admin/pcscfg.cfg, which is completely empty after the installation, should look like (replace [ORACLE_HOME] with your ORACLE_HOME, the full path, no variable possible; make the first line ONE line, we added the line breaks for formatting on this page only):

sys_include=([ORACLE_HOME]/precomp/syshdr,
  /usr/lib/gcc-lib/i486-suse-linux/2.95.2/include,
  /usr/include,/usr/include/linux)
include=[ORACLE_HOME]/precomp/public
include=[ORACLE_HOME]/oracode/include
include=[ORACLE_HOME]/oracode/public
include=[ORACLE_HOME]/rdbms/include
include=[ORACLE_HOME]/rdbms/public
include=[ORACLE_HOME]/rdbms/demo
include=[ORACLE_HOME]/network/include
include=[ORACLE_HOME]/network/public
include=[ORACLE_HOME]/plsql/public
include=[ORACLE_HOME]/otrace/public
include=[ORACLE_HOME]/ldap/public
ltype=none

For C++ you may have to add a line parse=partial (or 'none'), please check the Pro-C/C++ docs for details, available on OTN.

Also check out http://govt.oracle.com/~tkyte/proc_makefile/ for a simple example how to make a Makefile for Pro-C files.

Do not forget to collect all patches for SuSE Linux from ftp://ftp.suse.com/pub/suse/i386/update/[version]. you can use YOU (YaST Online Update, SuSE Linux 7.1+) to do this, but not all patches are available via YOU yet (due to bandwidth considerations), so you should also check manually. An easy way to do this is to use YaST1->Package Management->Install packages->FTP (use the provided default URL, it already points to the update area for this version of SuSE Linux on the SuSE ftp server)

Note that ftp.suse.com has a restriction of currently ~32kByte/s per user to give everyone a chance. You may find that one of the mirrors is faster for you.

You may also need any updates for at least lvm, modutils and yast from the ./a1/ directory when you upgrade the kernel.

You can get the pre-compiled binary kernel rpm's or the sources.

To install from the kernel sources:

    rpm -Uvh kernel-source.rpm
    cd /usr/src/linux
    make cloneconfig dep clean bzlilo modules modules_install
    mk_initrd
    lilo
    reboot

To install the binary kernel rpm:

    rpm -Uvh [k_deflt|k_smp].rpm
    cp /boot/vmlinuz /boot/vmlinuz.suse
    mk_initrd
    lilo
    reboot
    

Note that if you are NOT using a kernel that has /proc/config.gz (original SuSE kernels do) the make cloneconfig will not work. If you changed lilo.conf in an incompatible way the make bzlilo may fail (if you didn't touch that file it will work).