 |
Message Data
|
|
|
Reported
|
Settlement
|
Planned
|
|
|
|
76.04.12 |
Rejected |
76.06.10 |
|
|
|
|
Created
|
Processed
|
Completed
|
Affected OS
|
|
|
2008-04-17 |
|
|
All |
|
|
|
Description
|
Top |
|
|
<![CDATA[Restart/Recovery: error during redo log
After crash of an instance, the instance could not be restarted due to the following problem
2008-04-04 09:49:15 29 20006 Log 26 queues, flushmode is 'MaximizeSafety', devstate is 'Okay'
2008-04-04 09:49:15 29 20007 Log Oldest not saved is ioseq 1855693015 @ off 1391458
2008-04-04 09:49:15 29 20008 Log First known on LogVolume is ioseq 1853671208 @ off 1466545
2008-04-04 09:49:15 29 20005 Log Restart from ioseq 1855724714 @ off 1423157 to ioseq 1855768101 @ off 1466544
...
2008-04-04 09:49:21 26 ERR 20011 MOVECODE Bad parameter: source size [196] dest size [8192],
source addr [0X8000022DD3883E20]+159, dest addr [0X8000022DD3885
2008-04-04 09:49:21 26 ERR 20011 MOVECODE E20]+159, 42 bytes to copy
2008-04-04 09:49:21 26 6 KernelCo Rst_RedoReadTask::GetOrCreateRedoTransaction, Error code 400 "cancelled"
2008-04-04 09:49:21 26 20012 Log last-redo-read non empty errlist
#2260:TR862777814(0)[1855724918]@1423361.5280'InsertRecord':20080404:85659
2008-04-04 09:49:21 26 6 KernelCo Rst_RedoReadTask::GetOrCreateRedoTransaction, Error code 400 "cancelled"
2008-04-04 09:49:21 29 53000 OBJECT Stop active garbage coll: 1
2008-04-04 09:49:21 29 53000 OBJECT Garbage coll stopped: 0
2008-04-04 09:49:21 29 ERR 51080 SYSERROR -9407 unexpected error
2008-04-04 09:49:21 29 ERR 3 Admin Database state: OFFLINE
2008-04-04 09:49:21 29 ERR 6 KernelCo + Rst_RedoReadTask::GetOrCreateRedoTransaction, Error code 400 "cancelled"
The problem seems to be related to the seqence in which the logentries will be wriiten to the log volume.
It is possible that log entries which have been created before a savepoint will be written to the log volume behind the logentry for the savepoint, especially if more then one log queue is used.
In case that a data page where modifications have already been applied to has been written to the data volume for the converter version which belongs to the savepoint logentry,
but the log inforimation which reflects the applied changes are written behind the log entry for the savepoint, these modifications have to "redo" in case of a recocery.
This can force problems under certain circumstances ...]]>
|
|
| |
|
<![CDATA[PTS was accidently copied twice => reject this one]]>
|
|
| |
|
Id
|
Type
|
Description
|
Settlement
|
Planned Delivery
|
|
| |
1154516 |
Error |
Restart/Recovery: error during redo log
After crash of an instance, the instanc... |
76.06.10 |
5 |
|
| |
1154519 |
Error |
Restart/Recovery: error during redo log
After crash of an instance, the instanc... |
77.07.16 |
3 |
|
| |
1154522 |
Error |
Restart/Recovery: error during redo log
After crash of an instance, the instanc... |
77.04.39 |
3 |
|
| |
1154525 |
Error |
Restart/Recovery: error during redo log
After crash of an instance, the instanc... |
77.07.16 |
3 |
|
| |
1154528 |
Error |
Restart/Recovery: error during redo log
After crash of an instance, the instanc... |
76.04.17 |
3 |
|
| |
1154531 |
Error |
Restart/Recovery: error during redo log
After crash of an instance, the instanc... |
76.03.17 |
3 |
|
| |
1154543 |
Error |
Restart/Recovery: error during redo log
After crash of an instance, the instanc... |
78.00.19 |
5 |
|
| |
1154982 |
Error |
Restart/Recovery: error during redo log
After crash of an instance, the instanc... |
78.00.03 |
4 |
|
| |
|