| Customer: | ACME Widgets Inc. | |
|---|---|---|
| Period: | 2003/02/01 through 2003/03/01 |
| Test | Message | Quantity |
|---|---|---|
| Data block buffer cache hit ratio is too low. | 2 | |
| Synonym is invalid. | 2 | |
| The COMPATIBLE parameter is inconsistent with the database version. | 1 |
| Test: | OTS-6-1 |
|---|---|
| Message: | Data block buffer cache hit ratio is too low. |
| Background: | The data block buffer cache is a component of the SGA (System Global Area) used to hold data blocks that are read from segments in the database. When data is accessed, it must be read from disk and stored in the data block buffer cache before it is passed on to the process that requested it, unless the requested data is already in the cache. The data block buffer cache is managed using a least recently used (LRU) algorithm. This means that the most frequently requested data should always remain in the data block buffer cache. A low data block buffer hit ratio indicates that the cache is not large enough to store the most frequently accessed data in the database, resulting in re-reading it from disk. |
| Recommendation: | Add additional block buffers to the data block buffer cache by increasing the value of DB_BLOCK_BUFFERS in the init.ora file and restart the database for the change to take effect. |
| Data block buffer cache hit ratio is 86.49123%, limit is 95.0%. | |
| Parameters: | behaviour=AUTO, bufferHitRatioLimit=95.0% |
|---|---|
| Additional Info: | ConsistentGets=8441145, DBBlockGets=1232510, DataBlockBufferCacheHitRatio=86.49123%, PhysicalReads=1895724 |
| Detected at: | 2003/02/13 00:03:23 |
| Cleared at: | 2003/02/20 23:49:52 |
| Database: | dev |
| Test: | OTS-6-1 |
| Ref. #: | 4-00046167 |
| History: | ||
|---|---|---|
| Date: | 2003/02/15 23:57:06 | |
| (current) | ||
| Date: | 2003/02/13 00:03:23 | |
| Message: | Data block buffer cache hit ratio is 92.19101%, limit is 95.0%. | |
| Parameters: | behaviour=AUTO, bufferHitRatioLimit=95.0% | |
| Additional Info: | ConsistentGets=93651923, DBBlockGets=499940, DataBlockBufferCacheHitRatio=92.19101%, PhysicalReads=79459710 | |
| Data block buffer cache hit ratio is 82.878136%, limit is 95.0%. | |
| Parameters: | behaviour=AUTO, bufferHitRatioLimit=95.0% |
|---|---|
| Additional Info: | ConsistentGets=3621871, DBBlockGets=114147, DataBlockBufferCacheHitRatio=82.878136%, PhysicalReads=639676 |
| Detected at: | 2003/02/19 23:57:20 |
| Cleared at: | 2003/02/28 23:59:04 |
| Database: | dev |
| Test: | OTS-6-1 |
| Ref. #: | 4-00046449 |
| Test: | OTS-12-1 |
|---|---|
| Message: | Synonym is invalid. |
| Background: | Synonyms are logical names that refer to objects, such as tables or views, that exist within the database. Synonyms become invalid when the object they reference becomes inaccessible for any reason. Although invalid synonyms do not cause database problems, they may indicate that the referenced object has been inadvertently dropped or the privileges granted on the referenced object have changed. In the case of a chain of synonyms in which the final synonym in the chain is invalid, only the final synonym is reported. |
| Recommendation: | Drop the synonym if it is no longer required, or fix the problem with the referenced object so that the synonym becomes valid. |
| Synonym is invalid. | |
| Item: | owner=CCHARLES, synonymName=DROY_XAR1 |
|---|---|
| Parameters: | None. |
| Additional Info: | ReferencedObject=XAR1, ReferencedObjectOwner=DROY |
| Detected at: | 2002/12/27 23:55:09 |
| Cleared at: | 2003/02/05 23:59:59 |
| Database: | dev |
| Test: | OTS-12-1 |
| Ref. #: | 4-00040028 |
| Synonym is invalid. | |
| Item: | owner=CCHARLES, synonymName=DROY_XAR2 |
|---|---|
| Parameters: | None. |
| Additional Info: | ReferencedObject=XAR2, ReferencedObjectOwner=DROY |
| Detected at: | 2002/12/27 23:55:09 |
| Cleared at: | 2003/02/05 23:59:59 |
| Database: | dev |
| Test: | OTS-12-1 |
| Ref. #: | 4-00040056 |
| Test: | OTS-103-1 |
|---|---|
| Message: | The COMPATIBLE parameter is inconsistent with the database version. |
| Background: | The COMPATIBLE initialization parameter is used to maintain backward compatibility of the database with the version of server software specified. This parameter is often used when upgrading the Oracle server software to ensure it is possible to revert to the previous version if problems arise during or after the upgrade. For example, when upgrading from Oracle 7.3.2.3.0 to Oracle 7.3.4.0.1, the COMPATIBLE parameter can be set to 7.3.2.3.0 to ensure the database remains compatible with the 7.3.2.3.0 server software after the upgrade. However, no new database functionality introduced after version 7.3.2.3.0 will be available. The default value of the COMPATIBLE initialization parameter is the earliest version with which compatibility is possible. Normally, COMPATIBLE should be set to the current Oracle server release. |
| Recommendation: | Set the COMPATIBLE initialization parameter to match the current Oracle server release. |
| The COMPATIBLE parameter is set to 8.0.5, database version is 8.1.6.0.0. | |
| Parameters: | versionCompareDepth=3 |
|---|---|
| Additional Info: | CompatibleValue=8.0.5, DBVersion=8.1.6.0.0 |
| Detected at: | 2002/11/11 23:46:41 |
| Cleared at: | 2003/02/12 23:56:01 |
| Database: | dev |
| Test: | OTS-103-1 |
| Ref. #: | 4-00129727 |
| Test | Message | Quantity |
|---|---|---|
| Object status is not VALID. | 3 | |
| Index is in the SYSTEM tablespace. | 1 | |
| Log buffer space request ratio is too low. | 1 | |
| Table has too many chained or migrated rows. | 1 | |
| Table resides in the SYSTEM tablespace. | 1 | |
| Table resides in the same tablespace as one or more indexes that reference it. | 1 | |
| The COMPATIBLE parameter is inconsistent with the database version. | 1 |
| Test: | OTS-5-1 |
|---|---|
| Message: | Object status is not VALID. |
| Background: | Objects within the database can be invalid, and therefore not available to be used. An invalid object will usually be a view, trigger or package that needs to be recompiled because another object that it references has changed. |
| Recommendation: | Validate the specified object by recompiling or recreating the object as appropriate. |
| Object status is INVALID, desired status is VALID. | |
| Item: | objectName=PB_TEST1, objectType=PACKAGE BODY, owner=BSMITH |
|---|---|
| Parameters: | None. |
| Additional Info: | ObjectStatus=INVALID |
| Detected at: | 2003/02/14 23:41:46 |
| Cleared at: | 2003/02/15 23:52:59 |
| Database: | prod |
| Test: | OTS-5-1 |
| Ref. #: | 4-00067701 |
| Object status is INVALID, desired status is VALID. | |
| Item: | objectName=PB_TEST2, objectType=PACKAGE BODY, owner=BSMITH |
|---|---|
| Parameters: | None. |
| Additional Info: | ObjectStatus=INVALID |
| Detected at: | 2003/02/14 23:41:46 |
| Cleared at: | 2003/02/15 23:52:59 |
| Database: | prod |
| Test: | OTS-5-1 |
| Ref. #: | 4-00067702 |
| Object status is INVALID, desired status is VALID. | |
| Item: | objectName=PB_TEST3, objectType=PACKAGE BODY, owner=BSMITH |
|---|---|
| Parameters: | None. |
| Additional Info: | ObjectStatus=INVALID |
| Detected at: | 2003/02/14 23:41:46 |
| Cleared at: | 2003/02/17 23:58:26 |
| Database: | prod |
| Test: | OTS-5-1 |
| Ref. #: | 4-00067703 |
| Test: | OTS-10-1 |
|---|---|
| Message: | Index is in the SYSTEM tablespace. |
| Background: | Indexes contain selected columns from tables and therefore are added to, deleted from and updated whenever the table they index is added to, deleted from or updated. For this reason, it is generally accepted that indexes should not reside in the SYSTEM tablespace, unless owned by an Oracle built-in user. This is to help ensure that needless fragmentation of the SYSTEM tablespace does not occur. |
| Recommendation: | Move the index to an appropriate tablespace, if possible. |
| Index is in the SYSTEM tablespace. | |
| Item: | indexName=FJ_CACHE_I, owner=FJONES |
|---|---|
| Parameters: | None. |
| Additional Info: | None. |
| Detected at: | 2003/02/01 23:55:01 |
| Cleared at: | 2003/02/12 23:45:09 |
| Database: | prod |
| Test: | OTS-10-1 |
| Ref. #: | 4-00036285 |
| Test: | OTS-46-1 |
|---|---|
| Message: | Log buffer space request ratio is too low. |
| Background: | The log buffer is a small shared memory structure that Oracle uses for temporary storage of redo entries. LGWR writes redo entries from the log buffer to the currently active redo log group as user processes commit transactions. LGWR normally writes fast enough to ensure that space is always available in the buffer for new entries, even when redo activity is heavy. If LGWR is unable to write fast enough, user processes begin waiting for space in the log buffer, which results in a performance lag. The log buffer space request ratio is the ratio of redo entries since the database was last started to the number of requests for space in the log buffer. The number of waits should always be near 0, resulting in a ratio approaching 100%. A low ratio can indicate that the log buffer is too small, or that there is excessive checkpointing or log switching. As of Oracle8, additional LGWR slave processes can be created to help copy redo entries from the log buffer more quickly. |
| Recommendation: | Increase the size of the redo log buffer, if necessary, by changing the value of the initialization parameter LOG_BUFFER. The value of this parameter, expressed in bytes, must be a multiple of DB_BLOCK_SIZE. Optimize the checkpointing and log switching, if necessary. Add additional LGWR slave processes for Oracle8 and higher, if appropriate. |
| Log buffer space request ratio is 99.97164, limit is 99.98%. | |
| Parameters: | behaviour=AUTO, spaceRequestRatioLimit=99.98% |
|---|---|
| Additional Info: | LogBufferSpaceRequestRatio=99.97164, RedoEntries=260850, RedoLogSpaceRequests=311 |
| Detected at: | 2003/02/21 23:51:21 |
| Cleared at: | 2003/02/23 23:42:16 |
| Database: | prod |
| Test: | OTS-46-1 |
| Ref. #: | 4-00046510 |
| Test: | OTS-64-2 |
|---|---|
| Message: | Table has too many chained or migrated rows. |
| Background: | The term 'chained rows' is normally used to refer to both chained and migrated rows within the database. If an update occurs to a given row and there is not sufficient space in the current block to contain the row after the update, the row will either be continued in a new block (chained row) or be completely moved to a new block (migrated row). Reading a single chained or migrated row results in two or more physical block reads. In light of this, excessive numbers of chained or migrated rows have a negative impact on performance. |
| Recommendation: | Unload and reload the table, ensuring the storage parameters on the tables are set to minimize chaining in the future. If chaining has occurred because rows exist in the table that are larger than the database block size, recreating the database using a sufficiently larger block size will help. |
| 5.223881% of rows in the table are chained or migrated, limit is 5.0%. | |
| Item: | owner=ADMIN, tableName=MEETING |
|---|---|
| Parameters: | chainedRowsLimit=5.0% |
| Additional Info: | ChainedRows=5.223881% |
| Detected at: | 2003/02/07 23:58:09 |
| Cleared at: | 2003/02/08 23:57:49 |
| Database: | prod |
| Test: | OTS-64-2 |
| Ref. #: | 4-00045948 |
| Test: | OTS-81-1 |
|---|---|
| Message: | Table resides in the SYSTEM tablespace. |
| Background: | It is generally accepted that user and application tables should not reside in the SYSTEM tablespace. This is to help ensure that needless fragmentation of the SYSTEM tablespace does not occur. Tables owned by Oracle built-in users are ignored. |
| Recommendation: | Move the table to an appropriate tablespace, if possible. |
| Table resides in the SYSTEM tablespace. | |
| Item: | owner=FJONES, tableName=FJ_CACHE_T |
|---|---|
| Parameters: | None. |
| Additional Info: | None. |
| Detected at: | 2003/02/03 23:43:19 |
| Cleared at: | 2003/02/26 23:56:17 |
| Database: | prod |
| Test: | OTS-81-1 |
| Ref. #: | 4-00129725 |
| Test: | OTS-82-1 |
|---|---|
| Message: | Table resides in the same tablespace as one or more indexes that reference it. |
| Background: | When a table and one of its indexes are stored in the same tablespace, the response times of any queries done on the table using the index are extended since Oracle is unable to access both the table and index information at the same time. If the table and index reside in different tablespaces, preferably on separate disks, then Oracle can access the table and index simultaneously. Tables owned by Oracle built-in users are ignored. |
| Recommendation: | Move the table or index to another tablespace, preferably on separate disks, so Oracle can access the table and index simultaneously. |
| Table resides in the same tablespace as one or more indexes that reference it. | |
| Item: | owner=FJONES, tableName=FJ_CACHE_T |
|---|---|
| Parameters: | None. |
| Additional Info: | ListOfIndexes=FJ_CACHE_I, TablespaceName=SYSTEM |
| Detected at: | 2003/02/09 23:41:14 |
| Cleared at: | 2003/02/11 23:19:33 |
| Database: | prod |
| Test: | OTS-82-1 |
| Ref. #: | 4-00063130 |
| Test: | OTS-103-1 |
|---|---|
| Message: | The COMPATIBLE parameter is inconsistent with the database version. |
| Background: | The COMPATIBLE initialization parameter is used to maintain backward compatibility of the database with the version of server software specified. This parameter is often used when upgrading the Oracle server software to ensure it is possible to revert to the previous version if problems arise during or after the upgrade. For example, when upgrading from Oracle 7.3.2.3.0 to Oracle 7.3.4.0.1, the COMPATIBLE parameter can be set to 7.3.2.3.0 to ensure the database remains compatible with the 7.3.2.3.0 server software after the upgrade. However, no new database functionality introduced after version 7.3.2.3.0 will be available. The default value of the COMPATIBLE initialization parameter is the earliest version with which compatibility is possible. Normally, COMPATIBLE should be set to the current Oracle server release. |
| Recommendation: | Set the COMPATIBLE initialization parameter to match the current Oracle server release. |
| The COMPATIBLE parameter is set to 8.0.5, database version is 8.1.6.0.0. | |
| Parameters: | versionCompareDepth=3 |
|---|---|
| Additional Info: | CompatibleValue=8.0.5, DBVersion=8.1.6.0.0 |
| Detected at: | 2002/11/04 23:34:43 |
| Cleared at: | 2003/02/17 01:21:14 |
| Database: | prod |
| Test: | OTS-103-1 |
| Ref. #: | 4-00129726 |
|
|
SystemGuard, a division of Skyridge Systems Inc. | ||||
| 196 Robinson Street | Tel: | 506-854-7997 | |||
| Suite 201 | Email: | info@systemguard.com | |||
| Moncton, NB | Web: | www.systemguard.com | |||
| E1C 5C4 | |||||
| Canada | |||||