Jump to content
The ibi Community has moved to a new platform: Please Sign In and choose Forgot Password to continue

Hello all Has anyone seen the following error related SQL Re...


Naeem Sufi 3

Recommended Posts

Hello all

Has anyone seen the following error related SQL Repository

[2022-03-02 15:28:35,941] INFO [main:IBFSService] - DB Driver=com.microsoft.sqlserver.jdbc.SQLServerDriver

[2022-03-02 15:28:36,238] ERROR [main:ibfssystem] -

[2022-03-02 15:28:36,238] ERROR [main:ibfssystem] - *********************************************

[2022-03-02 15:28:36,238] ERROR [main:ibfssystem] -

[2022-03-02 15:28:36,238] ERROR [main:ibfssystem] - *** Failed to loadCachedInfo Failed to process the database schema changes in the repository DB. ***

java.lang.IllegalStateException: Failed to process the database schema changes in the repository DB.

if you can share what you did to resolve this issue

Thanks

Link to comment
Share on other sites

Naeem. A couple of things here. If this is a new install with a new webfocus repository, check that you have entered the jdbc driver for SQL Server in the install script, down to the .jar file. If this is a new install, using an existing webfocus repository from an older version, the install may not be able to make needed changes to the old version repository
Link to comment
Share on other sites

Ron This is a new install New Repository on SQL Server 2019 . SQL driver we have in the folder is mssql-jdbc-8.4.1.jre8 suggested by support team so the issue with the driver was resolved but now we are getting the above mentioned error , have not heard back from support , so just reaching out here if anyone had this issue

Thanks

Link to comment
Share on other sites

naeem.sufi:

 

Failed to loadCachedInfo

 

 

Naaem, Did you check the installation requirements regarding the repository options (page 32 in my manualTIBCO WebFOCUS Installation and Configuration for Windows). Specifically for Microsoft SQLServer the database collation must be set to case sensitive. I have seen that failing to do so causes this this type of error.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
  • Create New...