If you use Oracle WebLogic 10.0 MP2, you will notice can't write cache file messages similar to the following in the WebLogic:

[echo] *sys-package-mgr*: can't write cache file 
for
'/local/install/bea10_mp2/wlserver_10.0/server/lib/weblogic.jar'
[echo] *sys-package-mgr*: can't write cache file for
'/local/install/bea10_mp2/wlserver_10.0/server/lib/webservices.jar'
[echo] *sys-package-mgr*: can't write cache file for
'/tmp/_setup9366/products/deploywiz__92280__prt__xx__sp0__1/deploywiz/ant-launch
er.jar' 
[echo] *sys-package-mgr*: can't write cache file for
'/local/install/cfgsas2/SAS_mp2/SASVersionedJarRepository/9.2/eclipse/plugins/sa
s.rutil_902200.3.3.20090729190000_v920m2/sas.rutil.jar'
[echo] *sys-package-mgr*: can't write cache file for
'/local/install/cfgsas2/SAS_mp2/SASVersionedJarRepository/9.2/eclipse/plugins/Lo
g4J_1.2.13.0_SAS_20081023153014/log4j.jar'

Generation of this message in the log is a known issue in WebLogic when you run the WebLogic Scripting Tool (WLST) with multiple users on the same machine. This message appears because WLST creates a temporary directory (for example, /var/tmp/wlstTemp on a Solaris machine) that is shared by all users, and the tool is unable to differentiate between users. As a result, access to the directory is blocked when a user accesses the directory and that user is not the one who originally created the directory.

To resolve the issue, adjust the directory permissions manually for the temporary directory to 755.

More information about this WebLogic defect (CR280837) is available on the following pages:

• Oracle - Installation and Configuration Documentation
• Oracle - Thread: WLST log file

Operating System and Release Information