Troubleshooting
Problem
After migrating an iBase DB from one SQL Server to another, there's an error message when trying to open the iBase DB.
The error message is :
Cannot open database "XXXXXX_SEC" requested by the login.The login failed
Under Details, there is :
Error #-2147467259 occurred in:
Microsoft OLE DB provider for SQL Server
idDBSystems:SFConnection
dDBSystems:CurrentUserGIDs
dDBSystems:OpenDB
dDBSystems:OpenDatabase
FMain:ValidatePage
Resolving The Problem
There are 2 possible causes for this problem.
From iBase Designer, you can Upsize the Database or the Security file.
When you upsize the Security file, the resulting SQL database has the _SEC suffix.
As the error message talks about the XXXXXXXX_Sec database, this means that iBase cannot connect to this SQL database, because the Login and/or password is wrong.
When you upsize the Security file, the resulting SQL database has the _SEC suffix.
As the error message talks about the XXXXXXXX_Sec database, this means that iBase cannot connect to this SQL database, because the Login and/or password is wrong.
But another possible problem is that when you migrated your iBase SQL databases from one SQL Server to another, you didn't tell iBase the location of the migrated Security SQL database.
So, we must first check this.
1. Open the iBase Database Configuration utility
2. Select only the Security file. do NOT enter the "normal" iBase DB filename.
3. Enter the login password. Click Next
4) It should tell you the SQL server name, the database name and the SQL login/password that is defined for this Security file.
5) Check that these informations are correct. They must point to the NEW SQL Server, and not the old one.
2. Select only the Security file. do NOT enter the "normal" iBase DB filename.
3. Enter the login password. Click Next
4) It should tell you the SQL server name, the database name and the SQL login/password that is defined for this Security file.
5) Check that these informations are correct. They must point to the NEW SQL Server, and not the old one.
Then,, you also need to test the connection to this database, outside of iBase.
There are different ways to do this.
1) If you have SQL Server Management Studio, connect the the new SQL Server with the account that is defined in the iBase Configuration tool.
One possible problem is if the SQL Server was configured to take the lower/upper case into account.
The name of the SQL database of the Security file should normally ends with "_SEC".
In the error message, we see that the DB name ends with "_Sec".
If the SQL Server is configured to differenciate the lower and upper case letters, Security__SEC and Security__Sec are 2 different databases.
There are different ways to do this.
1) If you have SQL Server Management Studio, connect the the new SQL Server with the account that is defined in the iBase Configuration tool.
One possible problem is if the SQL Server was configured to take the lower/upper case into account.
The name of the SQL database of the Security file should normally ends with "_SEC".
In the error message, we see that the DB name ends with "_Sec".
If the SQL Server is configured to differenciate the lower and upper case letters, Security__SEC and Security__Sec are 2 different databases.
2) On your Window desktop, create a new Test file (with the TXT extension). Display the files extensions.
Change the file's extension from TXT to UDL. For example, rename it from Test_SQL.txt to test_SQL.UDL
Double-click on this UDL file.
Change the file's extension from TXT to UDL. For example, rename it from Test_SQL.txt to test_SQL.UDL
Double-click on this UDL file.
Enter the SQL server name, and the SQL user's login/password.
Check to see if the connection works.
Check to see if the connection works.
If not, then either the SQL Server's name, and/or the SQL user's Name and/or password are wrong.
As long as you cannot make this UDL work, iBase will not work either.
As long as you cannot make this UDL work, iBase will not work either.
There are some pages that talk about upsizing the Security file :
Document Location
Worldwide
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSXW43","label":"i2 iBase"},"ARM Category":[{"code":"a8m50000000Ci9aAAC","label":"i2 iBase and i2 Analyst's WorkStation->Database->SQL Server"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)","Line of Business":{"code":"LOB24","label":"Security Software"}}]
Was this topic helpful?
Document Information
Modified date:
29 July 2020
UID
ibm16254365