When tuning an Oracle® backend database, you should first read the information below. You want the information you obtain to be sufficient enough for you to make decisions about the initial setup and configuration of the Oracle backend. Once the backend is operational, a DBA should use Oracle tools to check the parameters of execution and adjust them based on the observed behavior.
The following are the Foglight® Management Server backend database usage characteristics:
|
• |
|
• |
|
• |
The following sections elaborate on specific aspects of Oracle® parameters.
We recommend you consult Oracle® analysis tools to check the effectiveness of indices used by the Foglight® Management Server. There are no known backend operations through the Management Server that would invalidate specific indices on particular events. Indices should only be rebuilt at the discretion of the DBA, after a thorough analysis of the behavior of the backend at runtime has been performed.
|
Oracle has the ability to analyze database tables and change its data access/management strategies. | |
|
The DBA should use Oracle analysis tools to check for strategy effectiveness. | |
|
exec dbms_utility.analyze_schema(‘FOGLIGHT’, ‘COMPUTE’); exec dbms_utility.analyze_schema(‘FOGLIGHT’, ‘ESTIMATE’); // Note: Estimate is likely to be quicker than Compute, but it is not as thorough. |
At the moment, there is no direct correlation between the amount of memory required by the Foglight® Management Server and the amount of memory required for the database. The management tools that ship with Oracle® can provide some tuning information to help you understand how much memory the database requires at load time.
© ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center
