Troubleshooting
Problem
Symptom
Cause
Environment
Diagnosing The Problem
Resolving The Problem
1) Obtain a backup of the affected iBase security (.ids) file from just before the database was last accessible.
2) Ask any remaining users still in the database to close down iBase, to guarantee they are out of both the database and the security file (ids). We have seen instances where users who were in the database prior to the corruption could still work in the database, even though users trying to log in once the file is corrupted were unsuccessful.
3) Paste in your backup iBase.ids and ask your users to try logging in again.
Document Location
Worldwide
Was this topic helpful?
Document Information
More support for:
i2 iBase
Software version:
All Versions
Operating system(s):
Windows
Document number:
1075275
Modified date:
26 September 2019
UID
ibm11075275