Since procedures can depend on each other, it is possible that one procedure may get created first before its dependent procedure has been created. These objects will be validated when they are used. I am doing a full database export. Somebody dropped one of my tables before Export had a chance to export it. Export does not get locks on all the tables at the start of the session.
Export first gets a list of all the tables at the start of the session.
It is possible that the table may be dropped between the time that Export generated the table list and the time that the table was to be exported. Export will skip the table and continue. This is a warning condition. I have a read-only tablespace. The reason for this is because tablespaces are created before the table data is imported.