I have created two databases using Oracle dNFS clone. The backup image is stored on ASM and both clones are stored on NFS and use the same backup image. It's a plain simple single instance configuration with ASM, no RAC or RAC OneNode.

It s a setup I've always made with no major issues, until now. The only major difference between my previous setups and now is that NFS is configured in a loop, pointing to an export inside the own database machine. I know it's ugly, but I don't have a storage with sharing options available this time and no spare machine to work as NFS server either

On many operations on some large tables (`CREATE INDEX` or `CREATE TABLE AS SELECT` or even and `UPDATE` statement), I'm getting the following error:

The error is NOT consistent. Some times I try to create a large 'temporary' table to do some tests and it works... some time it doesn't. Creating indexes on big tables always trigger the error. `UPDATES` may or may not trigger the error.

All permissions on NFS are set to oracle:dba. I've tried chmod'ing everything to 777 or 1777, but the error remained.

I know it's a long post and a very complex and challenging scenario, but can anybody help me on this one? I'm trying to fix it for a couple a days now, but the ORA-15310 error is too generic and there's nothing on MOS to help me out. On top of that, I'm not sure which one, NFS or ASM, is to blame here.

John WatsonMessages: 7255Registered: January 2010 Location: Global Village

Senior Member

I cannot suggest a solution, but I can say that I do not think that using NFS with
a loopback is the problem. I have used that before for dNFS clones no problem.
though I have never done it on the scale that you are using.

I found something with a similar trace to mine, but with ORA-29701 (most of the calls after the error are similar). It mentions that's something with permissions on $GRID_HOME/auth/css/ , $GRID_HOME/auth/ and $GRID_HOME. I've tried setting them, but, again, the result's the same :/

It isn't only indexes Mahesh, unfortunately... Some times an ALTER TABLE ADD COLUMN fails, but if I try again a few minutes later, it succeeds, same for some UPDATE statements. Some times a CREATE TABLE AS SELECT * fails, but if I limit with WHERE ROWNUM<22000000 it succeeds. It's not a consistent error.

One thing about CREATE TABLE TMP_TABLE AS SELECT * FROM [SOME TABLE] WHERE ROWNUM<XXXXXX, is that there is a limit. For one of the tables, this limit is 22.002.127. Really weird. I tried deleting some rows beyond that point, but the result is the same.

It's just that Oracle usually asks for a bunch of useless non-related logs, takes a long time to answer (specially for QA environments) and, most of the times, I end up finding the answer by myself. But I figure I've got no choice right now.