Issue with Loging into Sailpoint IIQ Dev after trying to replicate TST DB onto Dev DB

Hi all,

Our Dev environment is completely out of sync and we thought of replicating test DB onto Dev to have it completely synced.

When DBA did that, the login URL is throwing 404 error.

Later DBA has rolled back to the actual Dev DB backup but 404 continued.

As suggested by support team, deleted the identityiq, identityqah and identityiqplugin DBs and reinstalled using the DB scripts.

After this the 404 error is gone but we are not even able to login atleast with spadmin user and when we search for this user in spt_identity table zero records are returned.

As suggested by support team ran init.xml too but it also errored out as below after creating the identity spadmin:

sailpoint.tools.GeneralException: org.hibernate.exception.SQLGrammarException: could not extract ResultSet

Can anyone suggest how to handle and fix this.

Thanks in advance.

Regards,

Sayanth

Hi @SayanthBR

I’m the last you mentioned that spadmin identity has been created. So, are you able to start your Sailpoint instance without errors ? Check if you are seeing errors over that log file.

Also try running iiq console command.

Thanks

can you check, if you have updated the iiq properties file with new database details?? If not , can you please update the url, username and password accordingly.

Launch Iiq console and see if you are able to do it .

Hi Naveen,

Yeah all of them are updated correctly and the URL is up. but there is no user to login.

The default should be spadmin right its not even available.

Hi Manish,

Yes, I am able to start the instance without any errors. But cannot login as there is no user(not even the default spadmin).

Did you imported the init.xml file to load your spadmin users.

Try connecting with your iiq console. And import the init.xml file.

Try launching the iiq console, and import.

Hi Manish and Naveen,

I did try to import init.xml by launching iiq console but it failed immediately after creating the spadmin identity with below error:

sailpoint.tools.GeneralException: org.hibernate.exception.SQLGrammarException: could not extract ResultSet

Hence, I can say init.xml is not completely imported here.

@SayanthBR

Check your spt_identity table of identityiq schema. Is it empty or do you have some rows in the table.

Hi Manish,

Schema of identityiq is not empty but there is no data in it.

Hi Sayanth,

I’m also facing the same issue, did you find solution for this?

Thanks,

Sushant

Hi Sushant,

I have redeployed the war file with the out of box war file and then the 404 error is gone.

Note: With this method I’m redeploying all my configs and files into Dev again and testing all the use cases needed.

I know this is not easy but even the support team mentioned that they can only help on the issues with OOTB configs only.

Seen the error happening when extendedSchema script hasn’t been run on the DB?
Is that in order? Might not be it tho.