Permission denied on a file I own??

Question

OL 5.7 64bit
What's up with this?
I'm logged on as user 'oracle'.
User 'oracle' owns the directory OPatch, which has full permissions for the owner.
Yet, when I try to rename (mv) it, I get 'permission denied'.
oracle:+ASM$ ls -ld OP*
drwxr-xr-x 8 oracle oinstall 4096 Jul 24 14:15 OPatch
oracle:+ASM$ mv OPatch OPatch.old
mv: cannot move `OPatch' to `OPatch.old': Permission denied
oracle:+ASM$ id
uid=54321(oracle) gid=54321(oinstall) groups=54321(oinstall),54322(dba)
oracle:+ASM$

Answer 1

As you have discovered, directory maintenance operations such as:
rm(1)
mv(1)
rmdir(1)
rely on your permissions on the directory containing the object, not those of the object itself. Get these permissions like this:
$ ls -ld .However, as a courtesy of dubious merit, the GNU version of these tools check the writable status of the object as well so they can complain if you try this:
$ ls -ld .
drwx------. 79 tommy tommy 12288 Jul 28 09:32 .
$ touch foo
$ chmod foo 0444 foo
-r--r--r--.  1 tommy tommy 12288 Jul 28 09:33 foo
$ rm foo
rm: remove write-protected regular empty file `foo'?See, strictly-speaking rm(1) should have removed the file silently, since I have write permissions for foo's resident directory. The original rm(1) did in fact perform the delete.
Just for fun, try this:
$ mkdir foo
$ cd foo
$ date >now
$ chmod 0555 .
$ rm now
$ rm -f now
$ cd ..
$ rm -rf fooWe create a r/w object foo, set the directory to be read-only and then try to delete it. And then try very hard to delete it. And then try even harder.
So, the rule is that permissions for the directory rule.