
|
If you were logged in you would be able to see more operations.
|
|
|
| Product Version: |
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
|
| Operating System: |
IBM-AIX
|
After applying 10.2.0.4.0 PatchSet into 10.2.0.3.0, catupgrd.sql logs shows the following:
|
|
Description
|
After applying 10.2.0.4.0 PatchSet into 10.2.0.3.0, catupgrd.sql logs shows the following:
|
Show » |
|
There were both SYS.PLAN_TABLE as a table and PUBLIC.PLAN_TABLE as a public synonym in the database:
SQL> select owner,object_name,object_type from dba_objects where owner in ('SYS','PUBLIC') and upper(object_name) like 'PLAN_TABLE%'; OWNER ------------------------------ OBJECT_NAME -------------------------------------------------------------------------------- OBJECT_TYPE ------------------- PUBLIC PLAN_TABLE SYNONYM SYS PLAN_TABLE TABLE OWNER ------------------------------ OBJECT_NAME -------------------------------------------------------------------------------- OBJECT_TYPE ------------------- SYS PLAN_TABLE$ TABLE SQL> select TABLE_OWNER,TABLE_NAME from dba_synonyms where OWNER='PUBLIC' and SYNONYM_NAME='PLAN_TABLE'; TABLE_OWNER TABLE_NAME ------------------------------ ------------------------------ SYS PLAN_TABLE$ SQL>But, not all columns of SYS.PLAN_TABLE table and PUBLIC.PLAN_TABLE synonym are same:
Since table access takes precedence on synonym access, SYS.PLAN_TABLE table was used. But, this table doesn't have a column named OTHER_XML, which caused the problem.
After dropping SYS.PLAN_TABLE table, PUBLIC.PLAN_TABLE synonym used:
Applying PatchSet did not give INVALID status: