ORA-27054 error handling

Source: Internet
Author: User

Today in the virtual machine environment experiment, when changing the rac environment to flashback on, reported a ORA-27054 error, the error code is as follows:

Errors in file /u01/app/oracle/admin/racdb/udump/racdb2_ora_25551.trc:ORA-38701: Flashback database log 2 seq 1 thread 2: "/u01/flashback/RACDB/flashback/o1_mf_%u_.flb"ORA-27054: NFS file system where the file is created or resides is not mounted with correct options 
From the error description, we can see that the flashback directory is implemented through the nfs file system. When the system mounts nfs, the incorrect parameter option is used, resulting in an oracle error. Check online information and solve the problem through document 359515.1. The contents are as follows: RACIn the table below
Binaries is the shared mount points where the Oracle Home and CRS_HOME is installed.
Datafiles shortdes Online Logs, Controlfile and Datafiles

Operating System

Mount options for Binaries Mount options for Oracle Datafiles Mount options for CRS Voting Disk and OCR
Sun Solaris *

Rw, bg, hard, nointr, rsize = 32768,

Wsize = 32768, proto = tcp,

Noac, vers = 3, suid

Rw, bg, hard, nointr, rsize = 32768,

Wsize = 32768, proto = tcp, noac,

Forcedirectio, vers = 3, suid

Rw, bg, hard, nointr, rsize = 32768,

Wsize = 32768, proto = tcp, vers = 3,

Noac, forcedirectio

AIX (5L )**

Rw, bg, hard, nointr, rsize = 32768,

Wsize = 32768, proto = tcp, vers = 3,

Timeo = 600.

Cio, rw, bg, hard, nointr, rsize = 32768,

Wsize = 32768, proto = tcp, noac,

Vers = 3, timeo = 600

Cio, rw, bg, hard, intr, and rsize = 32768,

Wsize = 32768, tcp, noac,

Vers = 3, timeo = 600

HPUX 11.23 ****-

Rw, bg, vers = 3, proto = tcp, noac,

Hard, nointr, timeo = 600,

Rsize = 32768, wsize = 32768, suid

Rw, bg, vers = 3, proto = tcp, noac,

Forcedirectio, hard, nointr, timeo = 600,

Rsize = 32768, wsize = 32768, suid

Rw, bg, vers = 3, proto = tcp, noac,

Forcedirectio, hard, nointr, timeo = 600

, Rsize = 32768, wsize = 32768, suid

Linux x86

#

Rw, bg, hard, nointr, rsize = 32768,

Wsize = 32768, tcp, vers = 3,

Timeo = 600, actimeo = 0

Rw, bg, hard, nointr, rsize = 32768,

Wsize = 32768, tcp, actimeo = 0,

Vers = 3, timeo = 600

Rw, bg, hard, nointr, rsize = 32768,

Wsize = 32768, tcp, noac, vers = 3,

Timeo = 600.

Linux x86-64 #

Rw, bg, hard, nointr, rsize = 32768,

Wsize = 32768, tcp, vers = 3,

Timeo = 600, actimeo = 0

Rw, bg, hard, nointr, rsize = 32768,

Wsize = 32768, tcp, actimeo = 0,

Vers = 3, timeo = 600

Rw, bg, hard, nointr, rsize = 32768,

Wsize = 32768, tcp, vers = 3,

Timeo = 600, noac

Linux-Itanium

Rw, bg, hard, nointr, rsize = 32768,

Wsize = 32768, tcp, vers = 3,

Timeo = 600, actimeo = 0

Rw, bg, hard, nointr, rsize = 32768,

Wsize = 32768, tcp, actimeo = 0,

Vers = 3, timeo = 600

Rw, bg, hard, nointr, rsize = 32768,

Wsize = 32768, tcp, noac, vers = 3,

Timeo = 600.

* NFS mount option "forcedirectio" is required on Solaris platforms when mounting the OCR/CRS files when using Oracle 10.1.0.4 or 10.2.0.2 or later (Oracle unpublished bug 4466428)

** AIX is only supported with NAS onAIX 5.3 TL04And higher with Oracle 10.2.0.1 and later (NetApp)

* ** NAS devices are only supportedHPUX 11.23Or higher ONLY

# These mount options are for Linux kernels 2.6 and above for older kernels please check Note 279393.1

Due to Unpublished bug 5856342, it is necessary to use the following init. ora parameter when using NAS
With all versions of RAC on Linux (x86 & X86-64 platforms) until 10.2.0.4. This bug is fixed and pinned in 10.2.0.4 patchset.
Filesystemio_options = DIRECTIOSingle Instance

Operating System

Mount options for Binaries Mount options for Oracle Datafiles

Sun Solaris *

(8, 9, 10)

Rw, bg, hard, rsize = 32768,

Wsize = 32768, vers = 3, nointr,

Proto = tcp, suid

Rw, bg, hard, rsize = 32768,

Wsize = 32768, vers = 3, [forcedirectio or llock],

Nointr, proto = tcp, suid

AIX (5L )**

Rw, bg, hard, rsize = 32768,

Wsize = 32768, vers = 3, intr,

Timeo = 600, proto = tcp

Rw, bg, hard, rsize = 32768,

Wsize = 32768, vers = 3, cio, intr,

Timeo = 600, proto = tcp

HPUX 11.23 ****

Rw, bg, hard, rsize = 32768,

Wsize = 32768, vers = 3, nointr,

Timeo = 600, proto = tcp, suid

Rw, bg, hard, rsize = 32768,

Wsize = 32768, vers = 3, nointr,

Timeo = 600, proto = tcp, suid

Linux x86

#

Rw, bg, hard, rsize = 32768,

Wsize = 32768, vers = 3, nointr,

Timeo = 600, tcp

Rw, bg, hard, rsize = 32768,

Wsize = 32768, vers = 3, nointr,

Timeo = 600, tcp, actime = 0 *

Linux x86-64 #

Rw, bg, hard, rsize = 32768,

Wsize = 32768, vers = 3, nointr,

Timeo = 600, tcp

Rw, bg, hard, rsize = 32768,

Wsize = 32768, vers = 3, nointr,

Timeo = 600, tcp, actime = 0 *

Linux-Itanium

Rw, bg, hard, rsize = 32768,

Wsize = 32768, vers = 3, nointr,

Timeo = 600, tcp

Rw, bg, hard, rsize = 32768,

Wsize = 32768, vers = 3, nointr,

Timeo = 600, tcp

* Actime = 0 or noac can be used

Modify the mount parameter as follows:
[root@node2 bdump]# cat /etc/rc.d/rc.local#!/bin/sh## This script will be executed *after* all the other init scripts.# You can put your own initialization stuff in here if you don't# want to do the full Sys V style init stuff.touch /var/lock/subsys/localservice iscsi restart#start_udevmodprobe hangcheck-timermount -t nfs -o rw,bg,noac,hard,nointr,rsize=32768,wsize=32768,nolock,proto=tcp,actimeo=0,vers=3,timeo=600 192.168.2.31:/u01/flashback/ /u01/flashback/
The problem is solved successfully!

In addition, you can use the following methods to find information on the Internet:

1: Set event 10298 level 32

Alter system set event = '2014 trace name context forever, level 32 'scope = spfile;

It takes effect after the database is restarted.

2: patching: 5146667

I have not tried it. If you are interested, try it.

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.