Kbase 15092: DB-DOWN - error 1260 at startup - duplicate inode
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
DB-DOWN - error 1260 at startup - duplicate inode
DB-DOWN - error 1260 at startup - duplicate inode
If you are trying to start up a stand-alone database (for the sake of
discussion we will call it AAA) and 1) the AAA.lg file reports error
1260 - shared memory in use by another process, and 2) promon
indicates that AAA exists but is pointing to BBB and 3) yes, BBB is
up and running (hence the error), this is an indication of an inode
conflict. (This was once observed after converting databases from
version 6.2 to version 6.3.)
Usually the content of AAA is correct and intact, but the inode used
to seed shared memory is the same as BBB.db's inode. The problem is
with AAA.db only; AAA.bi and AAA.lg are ok. The way to get AAA a
unique inode will depend on your system configuration. Here are
three possible scenarios:
1) If you have enough space in the same filesystem to have two copies
of the .db file:
a) login as root
b) mv AAA.db AAAbad.db #AAAbad.db retains the problem inode
c) cp AAAbad.db AAA.db #AAA.db gets a new inode
d) rm AAAbad.db #regain disk space, release problem inode.
2) If you have enough space in a different filesystem to hold a copy
of the .db file:
a) login as root
b) mv AAA.db /other-file-system/AAA.db
c) touch bad.inode
d) mv /other-file-system/AAA.db AAA.db
e) rm bad.inode
3) If you do not have enough disk space for an additional copy of the
.db file:
a)login as root
b) backup your database
c) make a second backup (just to be sure)
d) rm AAA.db
e) touch bad.inode
f) restore your backup
g) rm bad.inode
Progress Software Technical Support Note # 15092