Summary Wizard (ASM): Not Analyzed dialog

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:

Not Analyzed dialog

For more information, see:

"Managing Summary Folders"

_ out of _ folders could not be analyzed. Would you like those folders to be excluded from the automatic summary creation?


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.


Use these notes to understand, and help resolve the following issues:

  • You do not have ANALYZE privileges for a given object/table

    To ANALYZE a table, you need one of the following:

    • to be the owner of that table

    • to have general ANALYZE privileges for the database (for example, through 'grant ANALYZE any to me')

    Where one of the underlying tables that make up a folder does not fit the above rules, that folder is not analyzed. In other words, if one or more tables within a folder cannot be analyzed then the whole folder is treated as if it cannot be analyzed.

  • When a folder is Invalid

    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.

  • You are trying to ANALYZE over a DB-Link

    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.

  • When Discoverer cannot determine or access the full list of tables that constitute a folder.

    A Discoverer folder can contain more than one underlying database table or view. Getting a full set of the underlying tables might be impossible. For example:

    • Where a view is based upon another view and the ASM user has access to the top level view, but not to the referenced view underneath.

    This makes it impossible for the ASM user to see which database tables are actually used to make that view.

  • When folders do not fully resolve to tables

    This should only really apply to the server dynamic tables (for example, 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:

    • V$_LOCKS

    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.