Am 04.03.2013 15:57, schrieb Brookins, Neil (Philadelphia):
This looks like a bug in the patch itself causing it to not handle sparse zones in a user friendly way. Note that the three other Java patches do not have this issue. I don't think there is a problem with PCA itself; its simply reporting the errors that patchadd is reporting back.
Correct. I guess the way to go would be a support request to Oracle then.
rm: /a/usr/jdk/jdk1.5.0_40 not removed: Read-only file system rm: /a/usr/jdk/jdk1.5.0_40 not removed: Read-only file system ln: cannot create /a/usr/jdk/jdk1.5.0_40/jdk1.5.0: Read-only file system ln: cannot create /a/usr/java/jdk1.5.0_40: Read-only file system
I think I've seen different errors in the past when the system wasn't rebooted after installing e.g. a kernel patch (does "df" show a lot of these /a-mounts?). PCA and patchadd don't enforce reboots, so maybe that's worth a look.
Martin.
