Installation guide

6.1 Building Pro*C Applications if PostgreSQL is Installed

If the postgresql-devel package is installed on the system, then you must

add the following directory to the beginning of the sys_include parameter in

the $ORACLE_HOME/precomp/admin/pcscfg.cfg file before building Pro*C

applications:

$ORACLE_HOME/precomp/public

If you do not make this change, then you may encounter errors similar to the

following when linking the applications:

/tmp/ccbXd7v6.o(.text+0xc0): In function ’drop_tables’:

: undefined reference to ’sqlca’

This issue is tracked with Oracle bug 3933309.

6.2 Encoding Information Not Present in Translated Help Files

If the system uses a European language, you might see corrupted characters in

Table of Contents of database tools, such as Database Configuration Assistant.

This issue is tracked with Oracle bug 3957096.

Workaround: If the system uses a European language, do not use the .UTF-8

locale. For example, if the system uses German, set the LANG and LC_ALL

environment variables to de_DE instead of de_DE.UTF-8.

6.3 Oracle Clusterware Files Issues

The following note applies if you are using Oracle Enterprise Linux 4.0, Oracle

Enterprise Linux 5.0, Red Hat Enterprise Linux 4.0, Red Hat Enterprise Linux 5.0,

or SUSE Linux Enterprise Server 10 and using raw devices to store the Oracle

Cluster Registry (OCR) and the voting disk for Oracle Clusterware, or using raw

devices for Automatic Storage Management (ASM) database files. For each raw

device used for the purposes listed, you must add two entries in the

/etc/rc.d/rc.local file on Oracle Enterprise Linux 4.0, Oracle Enterprise

Linux 5.0, Red Hat Enterprise Linux 4.0, and Red Hat Enterprise Linux 5.0, or the

/etc/init.d/after.local file on SUSE Linux Enterprise Server 10 after

running the root.sh script following the installation of Oracle Clusterware.

For each OCR file, the entries should look as follows, where oinstall is the

Oracle install group and /dev/raw/rawn is an individual device file:

chown root:oinstall /dev/raw/rawn

chmod 660 /dev/raw/rawnmar

For each voting disk file, the entries should look as follows, where oracle is the

Oracle user, oinstall is the Oracle install group, and /dev/raw/rawn is an

individual device file:

chown oracle:oinstall /dev/raw/rawn

chmod 644 /dev/raw/rawnmar

For each ASM file, the entries should look as follows, where oracle is the

Oracle user, oinstall is the Oracle install group, and /dev/raw/rawn is an

individual device file:

chown oracle:oinstall /dev/raw/rawn

chmod 660 /dev/raw/rawnmar