SystemGuardian for Oracle

Notification Report

(by SystemGuard, a division of Skyridge Systems Inc.)

Customer:   ACME Widgets Inc.
Generated at:   2003/09/15 14:18

Summary

Problems
Database New Changed Transient Cleared
dev 3 2 0 3
prod 11 3 0 4
Total: 14 5 0 7
 
Events
Database Quantity
dev 1
prod 2
Total: 3


Database: dev

Problems
Test Message New Chg Trn Clr
OTS-5-1 Object status is not VALID. 1 0 0 0
OTS-6-1 Data block buffer cache hit ratio is too low. 0 1 0 0
OTS-12-1 Synonym is invalid. 0 0 0 2
OTS-57-1 Segment has too many extents. 0 1 0 0
OTS-74-1 Privileges on object granted directly to PUBLIC. 1 0 0 0
OTS-103-1 The COMPATIBLE parameter is inconsistent with the database version. 0 0 0 1
OTS-108-1 Temporary tablespace has a PCTINCREASE value that is not 0. 1 0 0 0
Total: 3 2 0 3

Events
Test Message Qty
OTS-4-1 Initialization parameter changed. 1
Total: 1

New Problems - dev

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=PAYROLL_VIEW, objectType=VIEW, owner=FINANCE
Parameters: None.
Additional Info: ObjectStatus=INVALID
Detected at: 2003/09/08 23:50:00
Database: dev
Test: OTS-5-1
Ref. #: 4-00129707
Status: New

History:
  Date: 2003/09/03 23:50:00
  (current)

Test: OTS-74-1
Message: Privileges on object granted directly to PUBLIC.
Background: All privileges granted to PUBLIC are inherently granted to all users in the database. While privileges granted to PUBLIC do not pose a direct security threat in a database that is reasonably secure, the list of privileges granted to PUBLIC should be frequently reviewed to ensure that inappropriate privileges have not been inadvertently granted to all users. By default, objects owned by Oracle built-in users are not checked, since many objects owned by those users have grants to PUBLIC.
Recommendation: Review privileges on database objects that are granted to PUBLIC.

Privileges on object granted directly to PUBLIC: SELECT.
Item: objectName=USER_PRIMARY_KEY, objectType=VIEW, owner=ADMIN
Parameters: None.
Additional Info: ListOfPrivileges=SELECT
Detected at: 2003/09/08 23:57:48
Database: dev
Test: OTS-74-1
Ref. #: 4-00041348
Status: New

Test: OTS-108-1
Message: Temporary tablespace has a PCTINCREASE value that is not 0.
Background: Temporary tablespaces are used when large sorts are required to service statements issued by database users. These sorts create temporary segments for the duration of the sort and then destroy these segments when the sort is done. If the storage parameters for the temporary tablespace are incorrect, it can cause heavy fragmentation of the tablespace. Any tablespace specified as the temporary tablespace for one or more users, except for the SYSTEM tablespace, as well as all tablespaces flagged as temporary, are checked. The SYSTEM tablespace is not checked because it is generally accepted that no user should have a temporary tablespace of SYSTEM.

The PCTINCREASE default storage parameter specifies, as a percentage, how much larger the next extent allocated for the segment is than the last extent that was allocated for the segment. It is generally accepted that this value should always be 0 for temporary tablespaces so that each extent allocated is the same size as the last. This results in greatly reducing the rate at which the temporary tablespace becomes fragmented.
Recommendation: Set the PCTINCREASE default storage parameter for the tablespace to 0.

The temporary tablespace has a PCTINCREASE value of 50, desired value is 0.
Item: tablespaceName=TEMP3
Parameters: None.
Additional Info: PctIncrease=50
Detected at: 2003/09/08 23:47:02
Database: dev
Test: OTS-108-1
Ref. #: 4-00051613
Status: New

Changed Problems - dev

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 80.60712%, limit is 95.0%.
Parameters: behaviour=AUTO, bufferHitRatioLimit=95.0%
Additional Info: ConsistentGets=580736, DBBlockGets=44282, DataBlockBufferCacheHitRatio=80.60712%, PhysicalReads=121209
Detected at: 2003/09/07 23:46:56
Database: dev
Test: OTS-6-1
Ref. #: 4-00055544
Status: Changed

History:
  Date: 2003/09/08 23:52:56
  (current)
 
  Date: 2003/09/07 23:46:56
  Message: Data block buffer cache hit ratio is 71.84106%, limit is 95.0%.
  Parameters: behaviour=AUTO, bufferHitRatioLimit=95.0%
  Additional Info: ConsistentGets=959346, DBBlockGets=56477, DataBlockBufferCacheHitRatio=71.84106%, PhysicalReads=286045

Test: OTS-57-1
Message: Segment has too many extents.
Background: Segments, such as tables or indexes, are stored in logical containers in the database called tablespaces. When a segment fills and requires additional space to store data, the database allocates a number of blocks in the tablespace to the segment according to the segment's next extent size. Although there is no problem associated with a segment that has many extents, it is often desirable to know. For example, if a segment acquires a large number of extents in a relatively short period of time, the segment could be in danger of reaching its maximum number of extents. Also, a large number of segments that are obtaining new extents very frequently could adversely affect database performance. The NEXT storage parameter for the segment indicates the size of the extent that will be allocated by the segment the next time it extends.
Recommendation: Optimize the value of the NEXT storage parameter for the segment and unload and reload the segment.

Segment currently has 139 extents, limit is 100.
Item: owner=BOBF, segmentName=CUSTOMER, segmentType=TABLE
Parameters: extentsLimit=100
Additional Info: SegmentExtents=139
Detected at: 2003/09/06 23:57:40
Database: dev
Test: OTS-57-1
Ref. #: 4-00041271
Status: Changed

History:
  Date: 2003/09/09 00:01:21
  (current)
 
  Date: 2003/09/06 23:57:40
  Message: Segment currently has 127 extents, limit is 100.
  Parameters: extentsLimit=100
  Additional Info: SegmentExtents=127

Cleared Problems - dev

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: 2003/09/07 23:58:04
Cleared at: 2003/09/08 23:53:46
Database: dev
Test: OTS-12-1
Ref. #: 4-00044801
Status: Cleared


Synonym is invalid.
Item: owner=CCHARLES, synonymName=DROY_XAR2
Parameters: None.
Additional Info: ReferencedObject=XAR2, ReferencedObjectOwner=DROY
Detected at: 2003/09/07 23:58:04
Cleared at: 2003/09/08 23:53:46
Database: dev
Test: OTS-12-1
Ref. #: 4-00044802
Status: Cleared

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: 2003/08/23 23:43:32
Cleared at: 2003/09/08 23:41:17
Database: dev
Test: OTS-103-1
Ref. #: 4-00066507
Status: Cleared

Events - dev

Test: OTS-4-1
Message: Initialization parameter changed.
Background: Initialization parameters are used to configure the database and fine tune performance. The values of some initialization parameters are derived from others, and so are dynamically changed when other parameters are modified. Although some of the user configurable parameters can be changed through Server Manager or SQL*Plus while the database is running, all of them can be changed in the init.ora file. The database must be restarted for a change in the init.ora file to take effect. Changes to initialization parameters can have a dramatic impact on the operation of the database, so it is important to ensure that all such changes are intentional.
Recommendation: Verify that the change in the initialization parameter's value was both intentional and desired.

New parameter value is 0, old parameter value was 20.
Item: name=license_sessions_warning
Parameters: None.
Additional Info: NewParameterValue=0, OldParameterValue=20
Detected at: 2003/09/08 23:33:09
Database: dev
Test: OTS-4-1
Ref. #: 4-00077298


Database: prod

Problems
Test Message New Chg Trn Clr
OTS-5-1 Object status is not VALID. 3 0 0 0
OTS-6-1 Data block buffer cache hit ratio is too low. 0 1 0 0
OTS-7-2 Storage available for too few additional extents. 0 1 0 0
OTS-10-1 Index is in the SYSTEM tablespace. 0 0 0 1
OTS-14-3 User's default tablespace does not have the desired status. 2 0 0 0
OTS-46-1 Log buffer space request ratio is too low. 1 0 0 0
OTS-60-2 Tablespace has too little free space. 1 0 0 0
OTS-64-2 Table has too many chained or migrated rows. 1 0 0 0
OTS-78-1 DBA level privileges granted directly to user. 0 1 0 0
OTS-81-1 Table resides in the SYSTEM tablespace. 0 0 0 1
OTS-82-1 Table resides in the same tablespace as one or more indexes that reference it. 0 0 0 1
OTS-96-1 Table has no primary key. 3 0 0 0
OTS-103-1 The COMPATIBLE parameter is inconsistent with the database version. 0 0 0 1
Total: 11 3 0 4

Events
Test Message Qty
OLT-1-11 Unable to allocate new log, checkpoint not complete. 2
Total: 2

New Problems - prod

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/09/08 23:41:46
Database: prod
Test: OTS-5-1
Ref. #: 4-00067720
Status: New


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/09/08 23:41:46
Database: prod
Test: OTS-5-1
Ref. #: 4-00067721
Status: New


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/09/08 23:41:46
Database: prod
Test: OTS-5-1
Ref. #: 4-00067722
Status: New

Test: OTS-14-3
Message: User's default tablespace does not have the desired status.
Background: A user's default tablespace is the tablespace in which all tables and indexes are created, unless another tablespace is specified at the object's creation time.

In order for a user to read and write data to a segment in their default tablespace, the tablespace must have a status of ONLINE. If the tablespace's status is READ ONLY, data can only be read from segments within it. If the tablespace has a status of OFFLINE, the user will be unable to access any data within the tablespace.
Recommendation: Alter the user's default tablespace to have the desired status or assign the user a new default tablespace with the appropriate status.

User's default tablespace of USERS_T has a status of READ ONLY, desired status is ONLINE.
Item: username=MARTIN
Parameters: desiredStatus=ONLINE
Additional Info: DefaultTablespaceName=USERS_T, DefaultTablespaceStatus=READ ONLY
Detected at: 2003/09/08 23:47:02
Database: prod
Test: OTS-14-3
Ref. #: 4-00051623
Status: New


User's default tablespace of USERS_T has a status of READ ONLY, desired status is ONLINE.
Item: username=JAMESQ
Parameters: desiredStatus=ONLINE
Additional Info: DefaultTablespaceName=USERS_T, DefaultTablespaceStatus=READ ONLY
Detected at: 2003/09/08 23:47:02
Database: prod
Test: OTS-14-3
Ref. #: 4-00051624
Status: New

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.967705%, limit is 99.98%.
Parameters: behaviour=AUTO, spaceRequestRatioLimit=99.98%
Additional Info: LogBufferSpaceRequestRatio=99.967705%, RedoEntries=359197, RedoLogSpaceRequests=116
Detected at: 2003/09/08 23:41:30
Database: prod
Test: OTS-46-1
Ref. #: 4-00071011
Status: New

Test: OTS-60-2
Message: Tablespace has too little free space.
Background: As part of normal database operation, segments grow within their tablespaces as data is added to them. When a tablespace does not have sufficient free space to allocate an extent to a segment, that segment will not be able to grow further until the tablespace is enlarged.
Recommendation: Allocate additional space to the tablespace by adding a new datafile or increasing the size of one or more existing datafiles.

14.572088% of space in the tablespace is free space, limit is 15.0%.
Item: tablespaceName=SYSTEM
Parameters: freeSpaceLimit=15.0%
Additional Info: TablespaceFreeSpace=14.572088%, TablespaceSize=184549376 bytes
Detected at: 2003/09/08 23:42:13
Database: prod
Test: OTS-60-2
Ref. #: 4-00125191
Status: New

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/09/08 23:41:13
Database: prod
Test: OTS-64-2
Ref. #: 4-00088544
Status: New

Test: OTS-96-1
Message: Table has no primary key.
Background: Primary keys are a column or a group of columns that uniquely identify the rows in a table. It is generally accepted, with few exceptions, that all application tables should have primary keys. The process of defining a primary key helps to ensure that table data is represented in a normalized fashion. Tables owned by Oracle built-in users are ignored.
Recommendation: Determine which columns uniquely identify each row of the table and create a primary key using those columns.

Table has no primary key.
Item: owner=MSTEEVES, tableName=X1
Parameters: None.
Additional Info: None.
Detected at: 2003/09/08 23:47:02
Database: prod
Test: OTS-96-1
Ref. #: 4-00051640
Status: New


Table has no primary key.
Item: owner=MSTEEVES, tableName=X2
Parameters: None.
Additional Info: None.
Detected at: 2003/09/08 23:47:02
Database: prod
Test: OTS-96-1
Ref. #: 4-00051641
Status: New


Table has no primary key.
Item: owner=MSTEEVES, tableName=X3
Parameters: None.
Additional Info: None.
Detected at: 2003/09/08 23:47:02
Database: prod
Test: OTS-96-1
Ref. #: 4-00051642
Status: New

Changed Problems - prod

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 75.17247%, limit is 95.0%.
Parameters: behaviour=AUTO, bufferHitRatioLimit=95.0%
Additional Info: ConsistentGets=2234618, DBBlockGets=1109198, DataBlockBufferCacheHitRatio=75.17247%, PhysicalReads=830187
Detected at: 2003/09/07 23:55:35
Database: prod
Test: OTS-6-1
Ref. #: 4-00040274
Status: Changed

History:
  Date: 2003/09/08 23:55:44
  (current)
 
  Date: 2003/09/07 23:55:35
  Message: Data block buffer cache hit ratio is 90.24012%, limit is 95.0%.
  Parameters: behaviour=AUTO, bufferHitRatioLimit=95.0%
  Additional Info: ConsistentGets=3733132, DBBlockGets=7942567, DataBlockBufferCacheHitRatio=90.24012%, PhysicalReads=1139534

Test: OTS-7-2
Message: Storage available for too few additional extents.
Background: Segments, such as tables or indexes, are stored in logical containers in the database called tablespaces. When a segment fills its allocated space, the database allocates a new extent to the segment in the tablespace in which it resides. An extent consists of a number of database blocks from a tablespace and can only be used by the segment to which it has been allocated. The size of extent allocated to the segment is dependent on the segment's NEXT_EXTENT and PCT_INCREASE storage parameter values.

The segment specified is not able to obtain the specified number of extents because there is not sufficient contiguous free space within the tablespace.
Recommendation: Review the segment's storage parameters and either reduce the size of subsequent extents or allocate additional space to the tablespace, as appropriate.

Storage available for 2 additional extents, limit is 5.
Item: owner=APP1, segmentName=COMPANY_INFO, segmentType=TABLE
Parameters: availableExtentsLimit=5
Additional Info: AdditionalExtents=2, CurrentExtents=5, NextExtent=102400, PercentIncrease=0, TablespaceName=APP1_T
Detected at: 2003/09/07 23:45:38
Database: prod
Test: OTS-7-2
Ref. #: 4-00124610
Status: Changed

History:
  Date: 2003/09/08 23:46:37
  (current)
 
  Date: 2003/09/07 23:45:38
  Message: Storage available for 3 additional extents, limit is 5.
  Parameters: availableExtentsLimit=5
  Additional Info: AdditionalExtents=3, CurrentExtents=5, NextExtent=102400, PercentIncrease=0, TablespaceName=APP1_T

Test: OTS-78-1
Message: DBA level privileges granted directly to user.
Background: DBA level privileges are usually administrative privileges within the database. These privileges are considered a security risk and should only be granted to those users who require them. As such, care should be taken when granting these privileges to users. The list of privileges that are considered to be DBA level, by default, is documented and available upon request. Privileges granted to Oracle built-in users are not reported.
Recommendation: Revoke DBA level privileges from this user.

DBA level privileges granted directly to user: ALTER USER, CREATE ANY SYNONYM, CREATE USER, DROP USER, SELECT ANY TABLE, UNLIMITED TABLESPACE.
Item: username=ADMIN
Parameters: additionalPrivileges=null, excludedPrivileges=null
Additional Info: ListOfDBALevelPrivilegesHeld=ALTER USER, CREATE ANY SYNONYM, CREATE USER, DROP USER, SELECT ANY TABLE, UNLIMITED TABLESPACE
Detected at: 2003/08/08 23:43:50
Database: prod
Test: OTS-78-1
Ref. #: 4-00066766
Status: Changed

History:
  Date: 2003/09/08 23:51:52
  (current)
 
  Date: 2003/08/08 23:43:50
  Message: DBA level privileges granted directly to user: ALTER USER, CREATE ANY SYNONYM, CREATE USER, DROP USER, SELECT ANY TABLE.
  Parameters: additionalPrivileges=null, excludedPrivileges=null
  Additional Info: ListOfDBALevelPrivilegesHeld=ALTER USER, CREATE ANY SYNONYM, CREATE USER, DROP USER, SELECT ANY TABLE

Cleared Problems - prod

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/09/07 23:37:40
Cleared at: 2003/09/08 23:36:55
Database: prod
Test: OTS-10-1
Ref. #: 4-00091916
Status: Cleared

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/09/07 23:41:34
Cleared at: 2003/09/08 23:36:55
Database: prod
Test: OTS-81-1
Ref. #: 4-00091737
Status: Cleared

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/05/17 23:38:18
Cleared at: 2003/09/08 23:48:04
Database: prod
Test: OTS-82-1
Ref. #: 4-00068023
Status: Cleared

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: 2003/07/12 23:42:01
Cleared at: 2003/09/08 23:45:16
Database: prod
Test: OTS-103-1
Ref. #: 4-00129708
Status: Cleared

Events - prod

Test: OLT-1-11
Message: Unable to allocate new log, checkpoint not complete.
Background: A checkpoint causes DBWR to write all the modified database buffers in the SGA to the data files. Checkpoints are used to ensure that frequently accessed data is written to the datafiles regularly and they also help expedite the recovery of a database. A checkpoint on an online redo log must complete before that log can be used again by the LGWR process. If LGWR cannot access a redo log then database operations suspend until one becomes available.
Recommendation: If this does not occur frequently and is not causing a problem then it can likely be ignored.

Increasing the frequency at which checkpoints occur by modifying the LOG_CHECKPOINT_INTERVAL and LOG_CHECKPOINT_TIMEOUT parameters or increasing the number of online redo logs will help alleviate this problem.

Thread 1 cannot allocate new log, sequence 682
Checkpoint not complete
Detected at: 2003/09/08 14:05:46
Database: prod
Test: OLT-1-11
Ref. #: 0-00000268


Thread 1 cannot allocate new log, sequence 691
Checkpoint not complete
Detected at: 2003/09/08 14:16:40
Database: prod
Test: OLT-1-11
Ref. #: 0-00000269

  SystemGuard, a division of Skyridge Systems Inc. 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