Kbase P104272: Error 1260 after a normal database shutdown.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Status: Unverified
FACT(s) (Environment):
Windows
SYMPTOM(s):
Error 1260 appears trying to start up the database via proserve <dbname>.
Error 1260 appears trying to truncate the before image file via proutil <dbname> -C truncate bi.
Shared memory in use by another process. (1260)
Database was shutdown normally via proshut.
There is no <dbname>.lk file.
proutil <dbname> -C holder does not return messages indicating that the database would be in use.
There is one active _mprshut process for the database in memory.
There is no corresponding active _mprosrv process for the database in memory.
CAUSE:
A proshut session, other than the one that brought down the database, is still active.
The first proshut session shut the database down as expected, but, because of the second proshut session, the shared memory allocated to the database has not been released. This is what causes error 1260 upon restart.
FIX:
Quit the second proshut session. This will ensure that the shared memory is released, and after that the database can be restarted without problems.
For the future, you may want to bring down the database via proshut -F -by: in this case, even if a second proshut session is active, the database is brought down, all processes attached to the shared memory are killed (and that includes the second proshut session) and finally shared memory is released. Please see Solution P3222 for further details on the effect of the -F option in conjunction with proshut.