Different Behaviors When Querying Various V$ Views From Application Root
(Doc ID 2398776.1)
Last updated on MAY 11, 2020
Applies to:
Oracle Database - Enterprise Edition - Version 12.2.0.1 and laterOracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
The symptom is seen when using 12.2 new feature "Application Container".
When querying views like v$lock or v$session from Application Root,
the query returns rows from con_id 0 and the Application Root's con_id.
However, when querying v$latch, rows from application root and
the application PDBs are queried. con_id=0 is not shown.
Changes
The issue is seen when querying v$latch from inside Application Root.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |