Kbase P8376: 1260 error on database startup after system crash
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
21/11/2005 |
|
Status: Verified
SYMPTOM(s):
Error occurs after system crash when starting database with proserve command
Some databases start successfully others fail with 1260 error
Shared memory in use by another process. (1260)
SYSTEM ERROR: Unspecified shared memory error (1180)
SYSTEM ERROR: Memory violation. (49)
Does not have duplicate inode
Truncating bi file seems to workaround the issue
CAUSE:
Bug #: 20010717-002
CAUSE:
Creation of shared memory segments where not validating fully qualified database name.
FIX:
Fixed in Progress Service Pack 9.1D02 A change was made with regards to the shared memory segment so that the fully qualified database name is included in the header of the shared memory segment. When attempts are made to connect to shared memory the database name stored in the segment header is compared to the database name being connected to. If the names are not identical,then the DB connection is not performed.