SQLGrammarException

IdentityIQ (IIQ) IIQ Discussion and Questions
,
1

Which IIQ version are you inquiring about?

Version 8.4

Share all details related to your problem, including any error messages you may have received.

Hi Community,

I have set up a Web services application, on running the aggregation I’m getting the below error please enlighten me what’s the error is about…

Error1: org.hibernate.exception.SQLGrammarException: could not execute statement

Error2: Exception during aggregation of Palma, Bernadette. Reason: org.hibernate.exception.SQLGrammarException: could not execute statement

2

This happens either one of the account level attribute or group attribute (searchable attribute) is having length more than the defined length in DB

Can you try one thing , uncheck promote managed attributes in the account aggregation task and run and see if this is happening?

Post that you may have to increase the length of db column.

1 Like
3

Hi Satish,

Promote managed attributes is unchecked and still getting the same error over multiple users when I’m running the aggregation.

This is happening only with few users not with all.

4

@charan18
Do you have the list of users and target data for those users? It is most likely because of the same reason I mentioned above, if you analyze the data for users for which it is failing we can find it.

1 Like
5

I have only 4 attributes in this application

  1. Employee id 6-character string,
  2. OnCallToday the value is either Yes or No.
  3. OnCallTomorrow the value is either Yes or No.
  4. IncentiveOnCall the value is either Yes or No.

image
image1763×764 72 KB

image
image1733×743 38.4 KB

please see the account aggregation, and task result snippets I have attached.

6

For this failed user , did you check the target data for attributes in schema, is everything good like native identity, Display name of the account.

1 Like
7

Hi @iamksatish I just saw that this account aggregation is working fine in one of the environments and not in lower environment anything with specific to environment which could cause this?

8

@charan18
Is the data or target connected from prod and non-prod are both same , if not definitely this error would be because of the data that is being aggregated as mentioned above

I think some test data of accounts which are larger than expected data size within IIQ, also are both your IIQ environments have properties related to link, managed attribute and other objects.

1 Like