Cron Scripts Might Not Be Executed After A Fresh Install On Exadata (Doc ID 1323999.1)

Last updated on MAY 27, 2011

Applies to:

Oracle Exadata Hardware - Version: 11.2.0.2 and later   [Release: 11.2 and later ]
Information in this document applies to any platform.

Symptoms

Cron Scripts Might Not Be Executed After A Fresh Install On Exadata.
Cron scripts may not have execute permissions.
For example:

# dcli -l root -g ~/dbs_group "ls -l /etc/cron.daily/"

testdb01: total 32
testdb01: -rw------- 1 root root 379 Dec 30 2008 0anacron
testdb01: lrwxrwxrwx 1 root root 39 Feb 5 21:26 0logwatch -> /usr/share/logwatch/scripts/logwatch.pl
testdb01: -rw------- 1 root root 2050 Feb 5 21:21 cellos
testdb01: -rw------- 1 root root 180 Oct 31 2008 logrotate
testdb01: -rw------- 1 root root 418 Jun 6 2007 makewhatis.cron
testdb01: -rw------- 1 root root 137 Jul 2 2009 mlocate.cron
testdb01: -rw------- 1 root root 2181 Oct 31 2008 prelink
testdb01: -rw------- 1 root root 296 Sep 3 2009 rpm
testdb01: -rw------- 1 root root 328 Nov 1 2008 tmpwatch

these jobs could not be executed by cron process.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms