| Customer: | ACME Widgets Inc. | |
|---|---|---|
| Period: | 2003/02/01 through 2003/03/01 |
| Test | Message | Quantity |
|---|---|---|
| Initialization parameter changed. | 2 |
| 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 20, old parameter value was 0. | |
| Item: | name=license_sessions_warning |
|---|---|
| Parameters: | None. |
| Additional Info: | NewParameterValue=20, OldParameterValue=0 |
| Detected at: | 2003/02/17 23:56:13 |
| Database: | dev |
| Test: | OTS-4-1 |
| Ref. #: | 4-00046412 |
| 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/02/27 23:57:35 |
| Database: | dev |
| Test: | OTS-4-1 |
| Ref. #: | 4-00046695 |
| Test | Message | Quantity |
|---|---|---|
| Unable to allocate new log, checkpoint not complete. | 2 |
| 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 599 Checkpoint not complete |
|
| Detected at: | 2003/02/19 12:55:57 |
|---|---|
| Database: | prod |
| Test: | OLT-1-11 |
| Ref. #: | 0-00000251 |
| Thread 1 cannot allocate new log, sequence 740 Checkpoint not complete |
|
| Detected at: | 2003/02/24 13:10:44 |
|---|---|
| Database: | prod |
| Test: | OLT-1-11 |
| Ref. #: | 0-00000294 |
|
|
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 | |||||