Troubleshooting
Problem
The security file corresponding to the database has been lost or has become corrupt. There is currently no way to login to the database through iBase.
If the security file is not upsized, then it is an Access file with an .ids ending. The security file stores vital information such as usernames and permissions. You can verify whether your security file is upsized by opening up SQL Server Management Studio and checking whether a _SEC database exists. If the _SEC database exists, then the security file has been upsized. The security file also hosts some internal parameters such as the Unicode level.
If the security file is upsized, then the .ids file simply acts as a connection file to the newly created SQL Server database (_SEC). Information on how to upsize a security file can be found here: https://www.ibm.com/support/knowledgecenter/SSXW43_8.9.13/com.ibm.i2.ibase.designer.doc/upsizing_security.html
Symptom
Unable to login to the database though iBase.
Cause
Lost security file.
Lost credentials to security file.
Corrupt security file.
Environment
iBase
SQL Server
Resolving The Problem
To resolve the issue, we will backup our existing database, create a new database with a new security file and restore our old database into the new one.
1. Create a folder on your desktop named "New Database"
2. Open iBase Designer
3. First, we will create a new security file. File -> New Security File and name it: "New_Database" (the account for this new security file will be SYSADMIN/SYSADMIN. You can change this later on and add users/groups as you need)
4. Now, we will create a new empty database. File -> New Database and name it "New_Database", pointing it to your SQL Server.
5. Once the new database has been created, you may close out of iBase and open up SQL Server Management Studio. You should be able to view both "Original_Database" and "New_Database". At this point, "Old_Database" has all the data, but is inaccessible, while "New_Database" has no data, but is accessible.
6. You will need to create a backup of the "Original_Database" if you do not already have one created. Right-click on your database -> Tasks -> Backup and create a Full backup of the database. By default, this backup will be created in C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Backup, but it could be in a different location depending on your environment.
7. Now we will restore "Original_Database" onto "New_Database". Right-click on your new database and select Tasks->Restore->Database
8. On the "General" tab, select the "Device" radio button and ensure that the Destination database is set to "New_Database"
9. On the "Files" tab, ensure that the path under "Restore As" points to the new database.
10. On the "Options" tab, ensure that the "Overwrite" option is checked.
11. Now click "Ok" and the "Original_Database" should restore into "New_Database". After this has completed, open up iBase Designer and login to your newly created security file and then your "New_Database". You can now verify that your data, entities and links, exists in the new database.
If you run into any issues during this process, please open a case with the i2 support team: https://ibm.com/mysupport
Document Location
Worldwide
[{"Line of Business":{"code":"LOB24","label":"Security Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSXW43","label":"i2 iBase"},"ARM Category":[{"code":"a8m500000008ZHtAAM","label":"i2 iBase and i2 Analyst's WorkStation"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]
Was this topic helpful?
Document Information
Modified date:
08 December 2020
UID
ibm16379818