Oracle Discoverer Administrator Administration Guide 10g (9.0.4) Part Number B10270-01 |
|
Use this dialog to specify how you deal with folders that cannot be analyzed. For example, when you do not have analyze privileges on a particular database.
This dialog is also displayed as:
For more information, see:
Use this button to exclude folders that could not be analyzed.
Use this button to include folders that could not be analyzed.
Use this button to get more information about the folders that could not be analyzed.
In order to ANALYZE a table, you need one of the following:
Where one of the underlying tables that make up a folder does not fit the above rules, that folder will not be analyzed. This means that if one or more tables within a folder cannot be analyzed then the whole folder is treated as if it cannot be analyzed.
How you fix this depends on why a folder is marked as invalid.
To display the error message associated with an invalid folder go to View | Validate Folders.
If a folder refers to a table that resides on a database accessed over a DB-Link then ANALYZE will fail. This operation is not supported in the Oracle Server.
A Discoverer folder can contain more than one underlying database table and/or view. Getting a full set of the underlying tables might be impossible. For example:
This makes it impossible for the ASM user to see which database tables are actually used to make that view.
This should only really apply to the server dynamic tables (e.g. the V$ tables, and many DBA_tables). Not all these views and tables resolve to physical tables; some of them are stored in memory, thus they cannot be analyzed.
For example:
Although you can run queries on this kind of table/view, in practice it makes sense not to have summaries built on them as the summarized data would soon be out of date.
|
![]() Copyright © 1996, 2003 Oracle Corporation. All Rights Reserved. |
|