There is a bug in the Sort for Creation involving public synonyms.
Unfortunately, we have a lot of “legacy” (i.e., written before I was
hired) code in triggers, stand-alone functions and procedures that reference
other subprograms via their public synonyms. This dependency is not being
considered when sorting the objects for creation. When I run the creation script
in an empty schema, I get the warning that many of the routines compile but with
errors, due to objects they reference through the public synonyms appearing
later in the create script. Then I’m forced to sift through the creation
script and manually rearrange the routines in proper dependency order.
This is true on both Toad 10.0 and the most recent 10.5 Beta.
The workaround is to run DBMS_UTILITY.compile_schema after the creation script.
But from our customers’ (and their DBA’s) point of view, a create
script shouldn’t have errors – you don’t get the warm, fuzzy
feeling that a clean create would provide.
Oracle Database Developer
C O N F L U E N C E
THE MATERIAL CONTAINED IN THIS MESSAGE IS CONFIDENTIAL AND IS SUBJECT TO
RESTRICTIONS ON ITS DISCLOSURE. The recipient acknowledges that the information
contained herein is the exclusive, proprietary and confidential property of
Confluence Technologies, Inc. and shall be at all times regarded, treated and
protected as such by the recipient. The use and disclosure of this information
is subject to the restrictions contained in the Software License Agreement
between the recipient (or the recipient’s employer or its affiliates) and
Confluence Technologies, Inc.