Why Oracle Commands Fail After Reboot and How to Fix Them with UUID‑Based fstab
This guide explains how a missing automatic mount for the Oracle data partition caused command failures after a Linux reboot, and shows step‑by‑step how to use UUIDs in /etc/fstab to ensure reliable mounting and restore Oracle ASM functionality.
After installing ASM and Oracle on a Linux server, Oracle commands stopped being recognized after a reboot.
1. Screenshot of the error:
2. Environment variables were checked with a command and appeared normal.
3. The boot process displayed a long file‑system loading message, indicating a mount problem.
4. Disk mount points were examined; the command used is shown.
5. The root cause was that the sdc1 partition, originally mounted at /oradata, was not set to mount automatically at boot, while sdb1 (mounted at /oracle) was, causing Oracle to fail to start.
6. The /etc/fstab file was edited to mount sdc1 using its UUID, ensuring consistent device identification.
7. The article explains the benefits of using UUIDs: they are truly unique, device names can change between boots, and many Ubuntu features now rely on UUIDs.
8. After updating /etc/fstab, the system was rebooted, the partitions mounted correctly, and Oracle ASM status was verified as normal.
9. The final summary emphasizes checking command failures, reviewing boot logs, and using UUID‑based mounts to avoid similar issues.
Author: 我主梁缘 Source: http://xiaocao13140.blog.51cto.com/6198256/1930577
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
