You can check the upgrade log for details of the steps carried out in the upgrade and any issues that were encountered. Any issues should be resolved before retrying the upgrade.
When an upgrade completes, your upgrade log is stored in the same location as the iBase database connection file (.idb). It contains information about the steps that were carried out, and any issues that were found in the upgrade process.
Rebuilding the Full Text Search Index
To solve this problem:
File 'sysft_i2Catalog' cannot be reused until after the next BACKUP LOG operation.
- Launch SQL Server Management Studio
- Right-click the iBase database, and select from the context menu.
- For Backup type, select Transaction log
- Perform the backup
Rolling back the upgrade
- Restore all SQL Server iBase databases, iBase audit log databases, and iBase security file databases overwriting the partially upgraded databases.
- Restore all .ids, .idb, .idl and .idx files.
Locating connection files
- The MRU list on a machine has been cleared, so the database was not reported.
- Searching the entire network for iBase databases is not feasible.
- A machine was overlooked during the machine identification phase of the upgrade.
- A machine that was used for iBase has been retired due to age or failure.
- The database still resides on a SQL Server machine even though the database connection file (.idb) is no longer in use (and may have been deleted).
- The original network share location for connecting files has been dropped or changed.
|Security file location||SQLServer:ConnectionFile||SYS:SecurityFile|
|Database location||Not applicable||SQLServer:ConnectionFile|