Page History
...
To avoid using the MS-SQL fully automatic configuration function, change the following parameters:
- Maximum server memory (MB). Should be 80% of the server's RAM.
- Minimum memory per query (KB). Should be 512 instead of 1024.
An example to configure a parameter is the following command from the Query Analyzer:
EXEC sp_configure 'max server memory (MB)', [new value] RECONFIGURE WITH OVERRIDE
GO
Maintenance operations
Check the table and index status by running the following command:
...
| Setting | Description | Value |
|---|---|---|
| Size of the datafile | The default size when the PMDB is created. | 2 GB |
| Size of the log file | The default size when the PMDB is created. | 500 MB |
| Auto Extent size for datafiles and logs | The size of the new segment to be allocated. | 30% of initial datafile (for example, if the datafile is initially 1 GB, the auto extent size should be 300 MB). |
| Tempdb location | Put the |
...
Install the Precise environment before configuring the Oracle-based PMDB. Before applying the information in this section, refer to the Precise Installation Guide. For an Oracle-based PMDB, use an Oracle dedicated instance.
Verify that you are creating the database with the proper NLS_CHARACTERSET. When the monitored Oracle instances use a multiple byte character set, use UTF8. AL32UTF8 is not supported by the PMDB.
...
| Parameter | Value | Improvement | ||
|---|---|---|---|---|
| db_block_size | Minimum 8 KB (16 KB recommended) | This value defines the Oracle block size. The block size is set when creating the database and cannot be changed afterwards. A value of at least 8 KB ensures that the PMDB can perform smoothly. A lower value may cause serious performance problems. If you are installing on a legacy database, verify that the database block size is 8 KB or higher. If not, try to install the PMDB on a different Oracle instance.
|
Required INIT.ORA changes
...
| Parameter | Value | Improvement / Remarks |
|---|---|---|
sort_area_size | (1/8th of the physical memory) / (concurrent users + 10), up to 6 MB. | For example: If you have 2 GB of Physical Memory and 90 users, then the calculation will be: (2 GB / 8) / 100 ~= 2.5 MB |
db_block_buffers | 1/3rd of the physical memory divided by the size of the | The given values help to keep the I/O wait of the PMDB queries low. |
...
| Parameter | Value | Improvements / Remarks |
|---|---|---|
db_cache_size | Replaces parameter | |
pga_aggregate_target | 1/3rd of the physical memory. | |
workarea_size_policy | Auto | This parameter should be set to auto when we use the pga_aggregate_targetparametertarget parameter. |
| session_cached_cursors | 300 | |
DB-cache_advice | Verify that this parameter is set to | This parameter checks the work on the database and helps determine the recommended size of the Buffer pool. But this damages performance, so verify that it is on only for a short period. |
Table 6-6 Oracle 10g parameter
...
The following information is taken from the Oracle Database Administration Guide. In version 10.0 and 10.1 use the following command:
alter system set "_recyclebin"=FALSE scope=BOTH;
In version 10.2, use the following command:
alter system set recyclebin=off scope=BOTH
| Anchor | ||||
|---|---|---|---|---|
|
To enable Automatic Undo Management (AUM), you must create a new tablespace and set the init.ora parameters. For additional information on how to enable AUM, see the Oracle Database Administrator's Guide, “Managing "Managing Undo Space.”"
To enable Automatic Undo Management (AUM)
- Create the
undo tablespaceby running the following command:CREATE UNDO TABLESPACE tablespace_name DATAFILE 'datafile name' SIZE 32M REUSE AUTOEXTEND ON EXTENT MANAGEMENT LOCAL - Set the following
init.oraparameters:- undo_management = AUTO
- undo_tablespace = tablespace_name
- undo_retention = 900
If the undo tablespace size is too large, you may decrease the number of seconds.
...