Some issues during the Oracle RAC installation on openSUSE 15.2

  • A+

In last week, I installed an Oracle RAC on openSUSE 15.2 and got some issues. Although the installation was successful finally, it still took me much more time than the same thing on RHEL.

I list them here and hope to help more people.

1. No gcc48

zypper addrepo
zypper refresh
zypper install gcc48

More details could be found on below link:

gcc48 on SuSE/OpenSUSE

2. Passwordless SSH connectivity check will be failed

Workaround : (if your unix admin allows it)
Before installation, as root user: (please change the path if the location of your "scp" is not the same with below)
# Rename the original scp.
mv /usr/bin/scp /usr/bin/scp.orig

# Create a new file </usr/bin/scp>.
vi /usr/bin/scp

# Add the below line to the new created file </usr/bin/scp>.
/usr/bin/scp.orig -T $*

# Change the file permission.
chmod 555 /usr/bin/scp
After installation:
mv /usr/bin/scp.orig /usr/bin/scp

Another temporary solution is by downgrading openssh to earlier version(openssh-7.6p1-7.8.x86_64) on the installation node, then retry.

3. dbca will fail

vi $GRID_HOME/cv/admin/cvu_config
vi $ORACLE_HOME/cv/admin/cvu_config

[If you are getting error in case of oracle 12C prerequisites check then set CV_ASSUME_DISTID=SUSE12 parameter in database/stage/cvu/cv/admin/cvu_config file and retry. ]

4. After reboot, the crsd failed to start

Please find note Doc ID 2270947.1 for more detail.

Or here: Installation of Oracle Clusterware 12c(12cR1 & 12cR2) on SLES 12 fails with CRS-8503 [Signal Exception 11] (Doc ID 2270947.1)

I did below part and this problem was fixed.

Modify the /etc/ adding /lib64/noelision as the FIRST entry. It should look similar to the following:
include /etc/*.conf
# /lib64, /lib, /usr/lib64 and /usr/lib gets added
# automatically by ldconfig after parsing this file.
# So, they do not need to be listed.

3. Create a link in $GI_HOME/lib for the noelision version of the libpthread library:
# ln -s /lib64/noelision/ $GI_HOME/lib/

So you'd better do the workaround before the installation for the issue 4.

For the production environments, I always recommend the certified operating systems.


:?: :razz: :sad: :evil: :!: :smile: :oops: :grin: :eek: :shock: :???: :cool: :lol: :mad: :twisted: :roll: :wink: :idea: :arrow: :neutral: :cry: :mrgreen: