This weekend Oracle updated to oVirt 4.3, Yeah! See instruction below how to upgrade to oVirt 4.3 and if/when you version locked the sos package.
Oracle was still using oVirt Release 4.2 repositories for Oracle Linux 7.7. The vdsm-4.20.46 conflicted with sos 3.7-11 from the ‘latest’ Oracle Linux 7 repository, which features Oracle Linux 7.7, not 7.6.
The fix is in vdsm-4.30.something, from the oVirt 4.3 repo’s, and now they are offering it!
Continue readingWhen you get ‘Command returned failure code 1 during SSH session’ during adding a KVM host with the Oracle Linux Virtualization Manager, there might be something wrong with the libvertd deamon on the host you want to add.
I had this issue with adding a Oracle Linux 7.7 host.
Please check on the KVM host the following:
Continue readingREHL 7 and Oracle Linux 7 was not released when Oracle database 11.2.0.4 came out, so the installer does give some issues in the pre-requisites and when installing the software. I advice to do a software only installation first, because of an issue that you will need to fix with a patch after software installation, but before creating a database.
These issues popped-up when I was installing a 11.2.0.3 database on RHEL7 (not a Certified product combination!), but the solutions given for 11.2.0.4 worked for it as well:
When you run Oracle Grid 12c ‘cluvfy stage -pre crsinst’ on Linux 7 (Oracle Enterprise Linux 7.2 in my case) you will get the following error:
Starting check for /dev/shm mounted as temporary file system ... ERROR: PRVE-0421 : No entry exists in /etc/fstab for mounting /dev/shm PRVE-0421 : No entry exists in /etc/fstab for mounting /dev/shm PRVE-0421 : No entry exists in /etc/fstab for mounting /dev/shm PRVE-0421 : No entry exists in /etc/fstab for mounting /dev/shm Check for /dev/shm mounted as temporary file system failed
When you do a ‘df -h’ you will see that ‘/dev/shm’ actually is mounted:
Filesystem Size Used Avail Use% Mounted on devtmpfs 24G 0 24G 0% /dev tmpfs 24G 0 24G 0% /dev/shm
This is due to a bug (Doc ID 2065603.1) which comes from the case that the cluvfy check does not check the actual mount of the file system, but looks for the persistence line of this mount in ‘/etc/fstab’ like it did in Linux 6. In Linux 7 you get this tmpfs mount by default.