之前我也碰过类似情形,去 metalink 查了之后,修改一下 event 这个参数就可以了,给您参考...
Cause
From Oracle 10G R2 , Oracle checks the options with which a NFS mount is mounted on the filesystem.
and this is done to ensure that no corruption of the database can happen as incorrectly mounted NFS volumes can result in data corruption.
There are no single set of NFS mount options that work across all Oracle platforms
Please ensure that you have the proper mount options specified by the NAS vendor /Vendor user guide
The exact checks used for an NFS mounted disk vary between platforms but in general the basic checks will include the following checks
a) The mount table (eg; /etc/mnttab) can be read to check the mount options
b) The NFS mount is mounted with the "hard" option
c) The mount options include rsize>=32768 and wsize>=32768
d) For RAC environments, where NFS disks are supported, the "noac" mount option is used.
Please refer the section -- NFS Mount Options in OracleR Database Installation Guide10g Release 2 (10.2)
If you have ensured that the mount options are appropriate and still getting the errors then you are encountering symptoms as
in Bug 5146667 Fixed In Ver: 11.0. 0.0
And this issues is found to be port specific and reproducable on Solaris
.
Solution
To implement the solution, please execute the following steps:
From the erorrs that we see from the RMAN stack this looks like Bug 5146667
This behaviour has been observed on Solaris and AIX Platform.
WORKAROUND:
As suggested in the bug the workaround recommended is to use the Event 10298.
1) set the Event 10298 in the init file
event="10298 trace name context forever, level 32"
if you are using the spfile then the following can be done
SQL> alter system set event='10298 trace name context forever, level 32' scope= spfile ;
Once you set the above parameter restart the instance check as follows
SQL> select name, value from v$parameter where name = 'event';
NAME VALUE
---------- ------------------------------------------------------------
Event 10298 trace name context forever, level 32
1 row selected.
Then try the backups again
2) PATCH
Check if a one off patch for 10.2.0.1 for your platform is available
Please follow next steps to download and test it :
1. Login to Metalink
2. Go to Patches and Updates -> Simple Search
3. Enter patch number 5146667 and platform you are on ( your version of OS )
4. Download the patch
5. Read the README file for installation instructions and test it to see if it fixes your problem
Once the patch is shown as applied - you can do away with the event