The execution of catalog.sql results in just 5 errors which has been tested successully in both 9i and 10g. The errors are listed below, any other error besides what is given below is sure a matter of concern for the DBA which needs to be sorted out appropriately based on the error.
UNIX$> grep "^ORA-" catalog.log
ORA-01432: public synonym to be dropped does not exist
ORA-01432: public synonym to be dropped does not exist
ORA-00942: table or view does not exist
ORA-01921: role name 'EXP_FULL_DATABASE' conflicts with another user or role
ORA-01921: role name 'IMP_FULL_DATABASE' conflicts with another user or role
Now, the catproc.sql reports quite a lot of errors, all of which can be ignored. The number of errors that get reported during the execution of catproc.sql vary from platform to platform and from release to release. The number of errors generated in a 10.2.0.4 - 64 bit database on a 64-bit sparc Solaris machine are 435.
UNIX$> grep -c "^ORA-" catproc.log
435
Below is a list of all the errors that formed the number 435,
ORA-04043
ORA-00942
ORA-02289
ORA-01434
ORA-01432
ORA-29807
UNIX$> grep "^ORA-" catproc.log|grep -v "ORA-04043"|grep -v "ORA-00942" |\
> grep -v "ORA-02289"|grep -v "ORA-01434"|grep -v "ORA-01432"|grep -v "ORA-29807"
As it is evident that bypassing the above list of 6 types of ORA- errors does not show up any more errors in the catproc.log, so the count of ORA- errors does not really matter but the actual ORA- error does.
Posts
