Does hard-coding schema names in procedure calls for Oracle jobs have any performance impact? A database application I'm working with uses Oracle scheduled jobs to perform certain tasks. The DBA insists that hard-coding the schema name in the procedures that organise these jobs improves performance, but I can't see how it makes any difference. (I'm not even sure why it's necessary to have the schema name in there at all - the procedures run by the jobs are always in the same schema as the the job definer.)

Can there possibly be any truth to this? In general, does specifying the schema name make any difference when calling a procedure in the same schema as the connected user?
There is no performance impact.