Bug 9577583 – False ORA-942 or other errors when multiple schemas have identical object names (文档 ID 9577583.8)
Affects
| Product (Component) | Oracle Server (Rdbms) |
| Range of versions believed to be affected | Versions >= 10.2 but BELOW 12.1 |
| Versions confirmed as being affected | |
| Platforms affected | Generic (all / most platforms affected) |
Note that this fix can cause / expose the problem described in Bug:13080778
Fixed
| This issue is fixed in | ||||
| Symptoms: | Related To: | |||
Description
ORA-942, or other unexpected errors, can occur when running in a setup
where multiple schemas have identical objects and users are only expected
to access objects in their own schemas.
The problem can cause a SQL built for a given user to incorrectly
have dependency / translation / access table entries for other
users objects:
– If there is no permission on those objects then various errors can occur.
– If the current user does have permission on those objects then SQL may
execute using objects from the wrong schema leading to wrong results
or logical data corruption.
This problem can also lead to various dumps when executing PLSQL
especially when the PLSQL is executed from RMAN or Internal Errors
due to memory corruptions.
Rediscovery Notes:
A library_cache dump of the problem cursor shows that the child
cursor has incorrect entries in the dependency table.
Note:
This fix can expose the issue described in bug 13080778.
If using this fix it is advisable to also get the fix for bug 13080778
and 10165083 . All 3 fixes conflict and so a merge patch may be needed,
depending on which release you are on.
Getting a Fix
Use one of the “Fixed” versions listed above
(for Patch Sets / bundles use the latest version available as
contents are cumulative – the “Fixed” version listed above is
the first version where the fix is included)
or
You can check for existing interim patches here: Patch:9577583