Unexplained result of 'find' command

Given this bit of script:

retprd=$1
find ${extrnllogdir} -name "*.log" -mtime +$retprd -exec ls -l {} \;  >> $logfile

produces this (with 'set -x')

++ find /xfers/oracle/dw/data -name '*.log' -mtime +60 -exec ls -l '{}' ';'
find: /xfers/oracle/dw/data/cron: Permission denied

Where is he coming up with appending '/cron' onto the directory spec?

This is what find is expected to do. It descends the directory tree with the path you specified as starting point. Depending on your find implementation and OS there are options that prevent find from descending (maxdepth or prune).

hmm. there is a subdir named 'cron'. Hadn't noticed that. Kind of strange, too. What do you make of this:

oracle:dwprd$ ll|grep cron
drwxr-xr-- 2 smart1 smartusr      4096 Dec  1  2012 cron

2016-02-18 10:32:32
oracle:dwprd$ ll cron
total 0
?--------- ? ? ? ?            ? newcron.msg
?--------- ? ? ? ?            ? newcron.sh
?--------- ? ? ? ?            ? smart.20100208
?--------- ? ? ? ?            ? smart.20100803
?--------- ? ? ? ?            ? smart.20101027
?--------- ? ? ? ?            ? smart.20101101
?--------- ? ? ? ?            ? smart.20101109

In any event, I'll try the maxdepth option.

What user are you running that find under?

Any user that is not smart1 and is not a member of smartusr!
In this case the r-- permission for Others apply, leading to the funny output:
r bit => the directory can be read
no x bit => the files' inodes (type,permissions,owner,group,length,time,contents) cannot be accessed, therefore the ? marks.

so it is. I became smart (;)) and was then able to see the "correct" file listing. I'd never stumbled across anything quite like that before.

thanks to all for the assist.