Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I built two RHEL 6.5 servers that will have Oracle DBs running on them. I created a udev-disk file in /etc/udev/rules.d/ that includes the scsi ids, user/group ownership, devices names, etc. After I was done I ran partprobe and start_udev. All is good, devices names show under /dev with the correct permissions.
Problem, after reboots, disk devices show root:root as the owners. I then run command start_udev and then correct permissions appear, in this case oracleracle.
How do I fix it, so oracleracle stay after reboot?
He may be using the disks as raw table spaces - in which case, the Oracle database has total control over the disk and allocations. This can be a bit more efficient (less overhead specifically) than using a filesystem to hold files for tablespaces.
What he needs is for udev to set the ownership of the device names to that of the oracle database (last I knew this was the "oracle" login).
Yes jpollard, you are correct. Oracle has control of the devices, so no entries in /etc/fstab, no pvcreate/vgcreate/lvcreate. Basically you only partition the disks with fdisk and configure UDEV.
The linux servers I configured use Quest/VAS to authenticate to the domain. After reboot the UDEV service started before the VAS service, so the oracle owners could not be authenticated, therefore assigning root:root.
The fix: use the uid and gid of the owner:group in place of the names within the udev-asm file created at /etc/udev/rules.d/. Below is what inside of the file looks like, for one disk.
I have also faced Oracle db cluster user/group ownership issues with devices after server reboot (RHEL 6.8 64bit).
I found that there is a bug in package "udev-147-2.73.el6_8.1.x86_64" (RHEL 6.8)
The problem solved after updating package to "udev-147-2.73.el6_8.2.x86_64"
The temporary work around was to run #/sbin/start_udev to set permissions on devices under /dev/