LDAP application account aggregation error

Which IIQ version are you inquiring about?

8.4P1

Please share any images or screenshots, if relevant.


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

Getting two errors when running account aggregation for LDAP application type:

  1. An error occurred while attempting to create task partitions for Application: could not extract ResultSet,Application Name.
  2. org.hibernate.exception.SQLGrammarException: could not execute statement

Would like to know why is this occurring when I enable partitioning? FYI, if I uncheck partitioning, account aggreagtion is successful. What can I do to make ti successful with partitioning? Above is the error, and current settings in the account aggregation task.

Refer Could not extract ResultSet

Hi @Naidu_Reddi, the shared post did not share the exact steps they took to fix the issue. Could you elaborate?

  1. Open the ‘my.ini’ file under the MySQL server installation directory.
  2. Search for the ‘max_allowed_packet’ parameter. If the file does not have it, add the parameter.
  3. Set the value as needed. To set the value to 0.5GB, enter the value as one of the following: max_allowed_packet=536870912
  4. Restart the MySQL Server.

Hi @Naidu_Reddi,

Then I would like to understand why without partitioning the account aggreagtion works?

Hi @Naidu_Reddi

FYI, we are using AzureSQL, not MySQL

Hi @Naidu_Reddi , can I check how do I edit the value for AzureSQL?

Hi @shijingg,

Could you please share the log from Catalina? We encountered an error that states, “org.hibernate.exception.SQLGrammarException: could not execute statement.”

I notice a similar error occurs when the data length or format is unsupported for the account-level attribute size or data type. Please investigate this issue accordingly.

Thank you!
@SivaLankapalli

Hi @SivaLankapalli , but I would like to understand why does this only occur when the account aggregation task is partitioned?

Hi @shijingg,

It would be helpful if you could share only the error log and provide a solution

Have you created any account attributes?
Are you using optimized aggregation in full aggregation?

Thanks,
@SivaLankapalli