Troubleshooting
Problem
When trying to migrate an iBase database (DB) from iBase 5 to iBase 8, you get the following error message : "Could not find stored procedure 'sp_Rename'" This is due to the database collation, that is defined as Case Sensitive, instead of Case Insensitive.
Cause
IBM i2 iBase is only compatible with Case Insensitive databases.
Diagnosing The Problem
You must check the 3 levels of collation for your iBase database.
- Open SQL Server Management Studio, and connect to the SQL Server where the iBase DB is stored.
- Right-click on the main Server, and select Properties.
You should see a screen like the one below:

You must check for the "Server Collation" line. What is important is the _CI_ part, this is for Case Insensitive.
If you have xxxx_CS_xx, then the SQL Server is in Case Sensitive collation, and this is not supported by iBase.
Then, exit this window, and right-click on the iBase Database, and select the Properties command.
Again, a window will popup :

This is for the Database Collation.
Again, the value should be xxxx_CI_xx (for Case Insensitive).
Lastly, drill down at one Column level, and right-click to select Properties.

Again, this shows that at the Column level, the fields are Case Insensitive (xxxx_CI_xx).
WARNING : The 3 levels of collation must be exactly the same. Not only the case collation, but also the accent collation and the language collation.
Resolving The Problem
You must change the collation to case insensitive.
This process is directly linked to the SQL Server process, and therefore is outside the scope of the IBM Technical Support.
However, there are several sites that explains how to change the collation:
Step by step instructions on how to change collation on a database.
Instructions on how to transfer a database from one collation to another collation in SQL Server
Please be aware that there are 3 levels of collation :
- The SQL Server level
- The database level
- The columns level
All three levels must be changed to that the collation is the same on all 3. Otherwise, the iBase migration will fail.
Of course, you must backup your database before doing any change.
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21680326