10298 trace name context forever, level 32

psufnxk2000發表於2013-09-27
Context
APPLIES TO:

Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 11.1.0.7 - Release: 10.1 to 11.1
IBM AIX on POWER Systems (64-bit)
IBM AIX Based Systems (64-bit)
AIX5L Based Systems (64-bit)

***Checked for relevance on 17-Jan-2012***
SYMPTOMS

Datapump export failed with:         --匯出資料時有下面的報錯

Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production
With the Partitioning, OLAP and Data Mining Scoring Engine options
ORA-39001: invalid argument value
ORA-39000: bad dump file specification
ORA-31641: unable to create dump file "/full.Wed.dmp"
ORA-27054: NFS file system where the file is created or resides is not mounted with correct options
Additional information: 6

The dumpfile directory is located on a NFS file system.         --因為是NFT引起的

OR

Create database failed with:

CREATE DATABASE "test2" 
* 
ERROR at line 1: 
ORA-1501: CREATE DATABASE failed 
ORA-200: control file could not be created 
ORA-202: control file: '/control01.ctl' 
ORA-27054: NFS file system where the file is created or resides is not mounted with correct options 
Additional information: 6

CAUSE

This seems to be a limitation on AIX platforms. All mount point information is supposed to be present in the '/etc/filesystems' file located on the system.  When mount information is not present in this file it can lead to errors. 
在aix上，沒有在 /etc/filesystems裡出現的，會有這種情況

The behavior. is described in base bug:

BUG 4719334 NFS FILE SYSTEM WHERE THE FILE IS CREATED OR RESIDES IS NOT MOUNTED ORA-27054

closed as 'OS-Vendor problem', specific for AIX platforms.

Another bug:

BUG 4968488 NEED A WAY TO AVOID FATAL ORA-27054 ERRORS FROM SKGFIFI FOR NFS FILES

Offers a possibility to workaround this.

SOLUTION

Disallow MOUNT POINT checks with event:
"10298 trace name context forever, level 32"     ---使用這個事件不去檢查mount點

Event 10298 disables the NFS checks in the 10.2 code


SOLUTION 
=========
解決方法 ：
1 不使用NFS 
2  把NFS檔案 加到 /etc/filesystems裡
3 加10298 trace name context forever, level 32 事件
To implement the solution, please execute one the following steps:

1. Don't use NFS to create the  files. 

Or

2. Add the NFS filesys to '/etc/filesystems' 
--&gt This is also applicable for 11G
Or

3. Edit init.ora, add the line:
    event="10298 trace name context forever, level 32"

and bounce the database again, if it already exist so that the new parameter is active.

Then retry the failed operation

REFERENCES

NOTE:329942.1 - ORA-27054 while Relocating datafiles to an NFS Mount Point

來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/25099483/viewspace-773443/，如需轉載，請註明出處，否則將追究法律責任。

相關文章