UTLRP.SQL - UTLIRP.SQL - UTLIP.SQL 区别

1. UTLRP.SQL - UTLIRP.SQL - UTLIP.SQL 区别
4. Which is best -> UTLRP.SQL -or- UTLIRP.SQL -or- UTLIP.SQL?
6. 关于 UTLRP.SQL
7. ===============
9. + What is UTLRP.SQL?
10. UTLRP.SQL是用来重新编译无效的存储过程.
11. NOTE: 但不会像 utlirp.sql 与 utlip.sql那样废除任何无效的PLSQL模块
12. + What this script does?
13. This is a fairly general script that can be used at any time to recompile all existing invalid
14. PL/SQL modules in a database If run as one of the last steps during migration/upgrade/downgrade
15. this script will validate all PL/SQL modules
16. (i.e. procedures, functions, packages, triggers, types, views, libraries) during the migration step itself.
18. + 何时使用UTLRP.SQL?
19. Although invalid PL/SQL modules get automatically recompiled on use, it is useful to run this script ahead of time
20. (e.g. as one of the last steps in your migration), since this will either eliminate or minimize subsequent
21. latencies caused due to on-demand automatic recompilation at runtime. Oracle highly recommends running
22. this script towards the end of any database migration/upgrade/downgrade.
26. About UTLIRP.SQL
27. ===============
29. + What is UTLIRP.SQL ?
30. UTLIRP.SQL用来废除无效的 PL/SQL modules viz.,
31. procedures, functions, packages, types, triggers, views in a database
32. This script expects standard.sql, dbmsstdx.sql files to be available in the current directory.
33. There should be no other DDL on the database while running the script.
35. + What UTLIRP.SQL does?
37. In 9i:
39. The utlirp.sql script recompiles existing PL/SQL modules in the FORMAT required
40. by the NEW DATABASE with the below steps:
42. A. This script first alters certain dictionary tables.
44. B. Then, it reloads package STANDARD and DBMS_STANDARD,
45. which are necessary for using PL/SQL.
47. C. Finally, it triggers a recompile of all PL/SQL modules, such as packages,
48. procedures, types, and so on. Primarily used for WORD-SIZE conversion
50. In 10g and higher:
52. The utlirp.sql script recompiles existing PL/SQL modules in the FORMAT required
53. by the NEW DATABASE with the below steps:
55. A. This script first alters certain dictionary tables.
57. B. Then, it reloads package STANDARD and DBMS_STANDARD, which are necessary for using PL/SQL. All DDL Triggers are compiled at this time as well.
59. C. Unlike in 9i, the database must be restarted and UTLRP.SQL run to recompile the remaining invalid objects.
62. + Any other script called within UTLIRP.SQL?
63. Yes. It invokes utlip.sql and utlrp.sql
65. + When it is best to run UTLIRP.SQL?
66. A) Must during WORD-SIZE conversion where it first Invalidates PLSQL modules and then recompiles PLSQL modules in the FORMAT required by the NEW DATABASE. This situation makes sense because an action was taken that caused the old code's format to be inconsistent with what it's supposed to be. e.g., when migrating a 32 bit database to a 64 bit database or vice-versa
68. B) Can also be run whenever UTLRP.SQL needs to be run to validate invalid objects as this script only invalidates and then validates all the PLSQL modules.
71. 关于 UTLIP.SQL
72. ==============
74. + What is UTLIP.SQL
75. This script Invalidates PL/SQL modules. This script can be used to invalidate all existing PL/SQL modules (i.e. procedures, functions, packages, types, triggers, views) in a database so that they will be FORCED to be RECOMPILED LATER on either automatically or deliberately. Run this script connected as SYSDBA from SQL*PLUS. This script expects the following files to be available in the current directory: standard.sql, dbmsstdx.sql, dbmssql.sql, prvtssql.plb, prvtsql.plb, plitblm.sql
76. There should be no other DDL on the database while running the script.
78. + What UTLIP.SQL does?
79. This script regenerates the compiled code because an action was taken that caused the old code's format to be inconsistent with what it's supposed to be. e.g., when migrating a 32 bit database to a 64 bit database or vice-versa. THIS IS THE ACTUAL SCRIPT WHICH DOES THE REGENERATION OF COMPILED CODE. The actual series of steps can be checked reading the script which has a few step by step operations
81. + Any other script called within UTLIP.SQL?
82. Yes. It calls standard, dbmsstdx
84. + When it is best to run UTLIP.SQL?
85. The best would be during WORD-SIZE conversion from 32bit to 64bit and vice-versa.
88. Where are these SCRIPTS located?
89. ============================
91. The scripts are found in the standard admin directory of the Oracle Home.
92. $ORACLE_HOME/rdbms/admin
95. Which script is better?
96. =================
98. -> UTLIP.SQL - This is the actual script which does the regeneration of compiled code.
100. -> UTLRP.SQL - Validates all invalid objects and can be run anytime. (this in-turn is called by utlirp.sql)
102. -> UTLIRP.SQL - Simply calls utlip.sql and utlrp.sql(9i only) which MUST be run during WORD-SIZE conversion (If utlip.sql is not run manually) and during normal validating of invalid objects. (if utlrp.sql is not run)
105. Summary
106. ========
108. The best would be to run UTLIRP.SQL which would do both regeneration of compiled code of PL/SQL modules (which UTLIP.SQL does) and then Recompiles all Invalid PL/SQL modules again. (which UTLRP.SQL does)