Work to be done after Oracle patches Exadata

Oracle's patching of Exadata tightens security, which causes inconvenience in day-to-day work. For example, I like to keep /var/log/messages at mode 644. Patching changes it to 600. Here's a list of the things to do or watch after the patching.

As root:
* chmod 644 /var/log/messages* /var/log/maillog* /var/log/sa/sa*
* Uncomment user_allow_other in /etc/fuse.conf, otherwise FUSE (Filesystem in Userspace) such as DBFS may not mount.

As oracle:
* +ASM instance parameter use_large_pages may be changed to 'true' if it was some other value. Since +ASM is up before RDBMS, functionally 'true' has the same effect as 'only'. Allocate enough HugePages for +ASM, 3GB in 12c.
* In /etc/oratab, some entries such as +ASM* may be removed. Add back.
* Make sure rlwrap still works. This is the utility that allows you to press UP key in sqlplus.
* Comment out TMOUT in /etc/profile (or make sure to unset TMOUT in .bash_profile for oracle, root etc.)
* Reinstall Tivoli client if broken.