AnsweredAssumed Answered

Sub-Group Resolutions from Multi-App ADCs are Failing

Question asked by Riddhish Chakraborty Employee on May 12, 2020
Latest reply on May 15, 2020 by Mostafa Helmy

Environment:-

Version 7.1.0.154425 P03
Environment: PRD
Application Server Name: JBOSS
Appliance: false
Soft Appliance: true
Database: DB_REMOTE


Customer is using a combination of regular ADCs and Multi-App ADCs in their environment to collect groups. Many of these groups have sub-group memberships with groups that were collected from another ADC. Customer noticed an issue where groups collected from Multi-App ADCs are not resolved successfully in the Sub-Group Resolution Rule of another ADC.

 

Here is an example of the issue:

1. “Regular 1 ADC” contained within “Directory 1” collects a group named “Regular ADC 1 – Group”
2. “Regular 2 ADC” contained within “Directory 2” collects a group named “Regular ADC 2 – Group”
3. “Multi-App ADC” collects a group named “Multi-App ADC – Group” and places it in “Application 1”
4. “Regular 1 ADC” is configured to collect sub-group memberships.

 

The following memberships are defined:

Group Sub-Group
Regular ADC 1 - Group Regular ADC 2 - Group
Regular ADC 1 - Group Multi-App ADC - Group

5. “Regular 1 ADC” has Sub-Group Resolution Rules configured to ensure that the sub-group names are resolved against the “Regular 2 ADC” and “Multi-App ADC” collectors
6. The collector is run and the “Raw Data” of the collector shows that “Regular ADC 2 - Group” was resolved successfully but “Multi-App ADC - Group” failed with an error:

 

Reference resolutions failed.

 

Please refer to the attached screenshots.

 

I tested this scenario by importing the customer's metadata and following was the observation:

1. Ran the collection.
2. Checked the multi-app collection history and got an error-

Group data is invalid.
Group-membership-Rejected is 3.
Reference resolution failed.

 

AveksaServer.log shows the following errors:

04/13/2020 07:30:23.730 ERROR (Exec Task Consumer#0) [com.aveksa.server.xfw.TaskExecutor] Failed method=Execute ExecutionTask[TaskID=2299665 RunID=3478870 Source=24 Type=DataPreProcessing Status=InProgress]
com.aveksa.server.xfw.ExecutionException: com.aveksa.server.collector.DataProcessorException: java.sql.BatchUpdateException: ORA-01653: unable to extend table AVUSER.STX_ACC_24_3478870 by 128 in tablespace DATA_1M

at com.aveksa.server.xfw.DataPreProcessingExecutor.executeFullTask(DataPreProcessingExecutor.java:151)
at com.aveksa.server.xfw.DataPreProcessingExecutor.executeTask(DataPreProcessingExecutor.java:64)
at com.aveksa.server.xfw.TaskExecutor.execute(TaskExecutor.java:99)
at com.aveksa.server.xfw.ExecutionTaskQueue$Worker.run(ExecutionTaskQueue.java:116)
at java.lang.Thread.run(Thread.java:748)
Caused by: com.aveksa.server.collector.DataProcessorException: java.sql.BatchUpdateException: ORA-01653: unable to extend table AVUSER.STX_ACC_24_3478870 by 128 in tablespace DATA_1M

at com.aveksa.server.xfw.DefaultAccountDataPreProcessingFilter.createSTXTables(DefaultAccountDataPreProcessingFilter.java:254)
at com.aveksa.server.xfw.DefaultAccountDataPreProcessingFilter.process(DefaultAccountDataPreProcessingFilter.java:161)
at com.aveksa.server.xfw.DefaultAccountDataPreProcessingFilter.process(DefaultAccountDataPreProcessingFilter.java:124)
at com.aveksa.server.xfw.DataProcessor.process(DataProcessor.java:85)
at com.aveksa.server.xfw.DataProcessor.process(DataProcessor.java:64)
at com.aveksa.server.xfw.DataPreProcessingExecutor.executeFullTask(DataPreProcessingExecutor.java:136)
... 4 more
Caused by: java.sql.BatchUpdateException: ORA-01653: unable to extend table AVUSER.STX_ACC_24_3478870 by 128 in tablespace DATA_1M

at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:12296)
at oracle.jdbc.driver.OracleStatementWrapper.executeBatch(OracleStatementWrapper.java:246)
at org.jboss.jca.adapters.jdbc.WrappedStatement.executeBatch(WrappedStatement.java:1190)
at com.aveksa.server.db.FileToTable.commitBatchToDB(FileToTable.java:388)
at com.aveksa.server.db.FileToTable.process(FileToTable.java:363)
at com.aveksa.server.xfw.DefaultAccountDataPreProcessingFilter.createSTXTables(DefaultAccountDataPreProcessingFilter.java:212)


Please let me know if these error is relevant to the customer's scenario and also if this is a configuration problem.

Outcomes