cosborne
New Member.
475 views

Identity Publication Issue

Hello Everyone,

I have and issue where I can collect Identities form NetIQ and AD, but when I go to publish I get stuck on this step, yesterday I let it run all night and it didn't move. Trying again this morning and stuck at same point, has anyone seen this issue before with Identity Publication?

1:42:38.537
04/26/2019
9:49:55.190 am
UNIFIER.RUNNING.RUNNING_PHASE_2
0:00:00.126
04/26/2019
9:50:11.098 am
04/26/2019
9:50:11.224 am
JoinAttributeValidation.validateJoinAttribute
0:29:43.952
04/26/2019
9:50:11.230 am
04/26/2019
10:19:55.182 am
NontrivialUnification.unify
0:06:01.431
04/26/2019
10:19:55.186 am
04/26/2019
10:25:56.617 am
Unification-PhaseI.DbPerfUtil.updateTableStatistics
0:00:00.249
04/26/2019
10:26:10.731 am
04/26/2019
10:26:10.980 am
analyzeUnification
0:01:03.809
04/26/2019
10:26:10.984 am
04/26/2019
10:27:14.793 am
SnapshotDAO.realizeUnificationSnapshot
0:10:58.407
04/26/2019
10:27:14.796 am
04/26/2019
10:38:13.203 am
UserRefResolution.resolveUserReferences
0:54:20.531
04/26/2019
10:38:13.206 am
TransitiveSubgroups.generate
0:00:07.281
04/26/2019
10:38:13.211 am
04/26/2019
10:38:20.492 am
TransitiveSubgroups.generate (distance=1)

[INFO] 2019-04-26 10:19:05 com.netiq.iac.persistence.util.DbPerfUtil logStatUpdate - [IG-DTP] Table SERVICE_INSTANCE was optimized: size changed by 30.0 percent or more.
[INFO] 2019-04-26 10:19:08 com.netiq.iac.persistence.util.DbPerfUtil logStatUpdate - [IG-DTP] Table STRANS_SUBGROUP was optimized: size changed by 20000 or more records.
[INFO] 2019-04-26 10:19:36 com.netiq.iac.persistence.util.DbPerfUtil logStatUpdate - [IG-DTP] Table SUSER was optimized: size changed by 20000 or more records.
[INFO] 2019-04-26 10:19:40 com.netiq.iac.persistence.util.DbPerfUtil logStatUpdate - [IG-DTP] Table SUSER_CUSERS was optimized: size changed by 20000 or more records.
[INFO] 2019-04-26 10:19:41 com.netiq.iac.persistence.util.DbPerfUtil logStatUpdate - [IG-DTP] Table SUSER_EMAIL was optimized: size changed by 20000 or more records.
[INFO] 2019-04-26 10:19:54 com.netiq.iac.persistence.util.DbPerfUtil logStatUpdate - [IG-DTP] Table SUSER_EXT_ATTR_VALUE was optimized: size changed by 20000 or more records.
[INFO] 2019-04-26 10:19:55 com.netiq.iac.persistence.util.DbPerfUtil logStatUpdate - [IG-DTP] Table QRTZ_SCHEDULER_STATE was optimized: size changed by 30.0 percent or more.
[INFO] 2019-04-26 10:25:56 com.netiq.iac.persistence.util.DbPerfUtil logStatUpdate - [IG-DTP] Table SACCOUNT_PERMISSION was optimized: size changed by 20000 or more records.
[INFO] 2019-04-26 10:34:30 com.netiq.iac.persistence.util.DbPerfUtil logStatUpdate - [IG-DTP] Table SACCOUNT_PERMISSION was optimized: size changed by 20000 or more records.
[INFO] 2019-04-26 10:34:50 com.netiq.iac.persistence.util.DbPerfUtil logStatUpdate - [IG-DTP] Table SGROUP_USER was optimized: size changed by 20000 or more records.
0 Likes
5 Replies
Micro Focus Expert
Micro Focus Expert

Re: Identity Publication Issue

On 4/26/19 2:34 PM, cosborne wrote:
>
> Hello Everyone,
>
> I have and issue where I can collect Identities form NetIQ and AD, but
> when I go to publish I get stuck on this step, yesterday I let it run
> all night and it didn't move. Trying again this morning and stuck at
> same point, has anyone seen this issue before with Identity Publication?
>
>
> 1:42:38.537
> 04/26/2019
> 9:49:55.190 am
> UNIFIER.RUNNING.RUNNING_PHASE_2
> 0:00:00.126
> 04/26/2019
> 9:50:11.098 am
> 04/26/2019
> 9:50:11.224 am
> JoinAttributeValidation.validateJoinAttribute
> 0:29:43.952
> 04/26/2019
> 9:50:11.230 am
> 04/26/2019
> 10:19:55.182 am
> NontrivialUnification.unify
> 0:06:01.431
> 04/26/2019
> 10:19:55.186 am
> 04/26/2019
> 10:25:56.617 am
> Unification-PhaseI.DbPerfUtil.updateTableStatistics
> 0:00:00.249
> 04/26/2019
> 10:26:10.731 am
> 04/26/2019
> 10:26:10.980 am
> analyzeUnification
> 0:01:03.809
> 04/26/2019
> 10:26:10.984 am
> 04/26/2019
> 10:27:14.793 am
> SnapshotDAO.realizeUnificationSnapshot
> 0:10:58.407
> 04/26/2019
> 10:27:14.796 am
> 04/26/2019
> 10:38:13.203 am
> UserRefResolution.resolveUserReferences
> 0:54:20.531
> 04/26/2019
> 10:38:13.206 am
> TransitiveSubgroups.generate
> 0:00:07.281
> 04/26/2019
> 10:38:13.211 am
> 04/26/2019
> 10:38:20.492 am
> *TransitiveSubgroups.generate (distance=1)*
>
> [INFO] 2019-04-26 10:19:05 com.netiq.iac.persistence.util.DbPerfUtil
> logStatUpdate - [IG-DTP] Table SERVICE_INSTANCE was optimized: size
> changed by 30.0 percent or more.
> [INFO] 2019-04-26 10:19:08 com.netiq.iac.persistence.util.DbPerfUtil
> logStatUpdate - [IG-DTP] Table STRANS_SUBGROUP was optimized: size
> changed by 20000 or more records.
> [INFO] 2019-04-26 10:19:36 com.netiq.iac.persistence.util.DbPerfUtil
> logStatUpdate - [IG-DTP] Table SUSER was optimized: size changed by
> 20000 or more records.
> [INFO] 2019-04-26 10:19:40 com.netiq.iac.persistence.util.DbPerfUtil
> logStatUpdate - [IG-DTP] Table SUSER_CUSERS was optimized: size changed
> by 20000 or more records.
> [INFO] 2019-04-26 10:19:41 com.netiq.iac.persistence.util.DbPerfUtil
> logStatUpdate - [IG-DTP] Table SUSER_EMAIL was optimized: size changed
> by 20000 or more records.
> [INFO] 2019-04-26 10:19:54 com.netiq.iac.persistence.util.DbPerfUtil
> logStatUpdate - [IG-DTP] Table SUSER_EXT_ATTR_VALUE was optimized: size
> changed by 20000 or more records.
> [INFO] 2019-04-26 10:19:55 com.netiq.iac.persistence.util.DbPerfUtil
> logStatUpdate - [IG-DTP] Table QRTZ_SCHEDULER_STATE was optimized: size
> changed by 30.0 percent or more.
> [INFO] 2019-04-26 10:25:56 com.netiq.iac.persistence.util.DbPerfUtil
> logStatUpdate - [IG-DTP] Table SACCOUNT_PERMISSION was optimized: size
> changed by 20000 or more records.
> [INFO] 2019-04-26 10:34:30 com.netiq.iac.persistence.util.DbPerfUtil
> logStatUpdate - [IG-DTP] Table SACCOUNT_PERMISSION was optimized: size
> changed by 20000 or more records.
> [INFO] 2019-04-26 10:34:50 com.netiq.iac.persistence.util.DbPerfUtil
> logStatUpdate - [IG-DTP] Table SGROUP_USER was optimized: size changed
> by 20000 or more records.
>
>

Greetings,

1) What is the exact version of the product you are using?

2) What Operating System is it installed on?

3) It appears you are using PostgreSQL as the database server, is that
correct?

4) Is the db server on the same machine as ID Gov?


--
Sincerely,
Steven Williams
Principal Enterprise Architect
Micro Focus
0 Likes
fp_idmworks Super Contributor.
Super Contributor.

Re: Identity Publication Issue

I am aware of this issue with this installation. Chiming in in case he isn't available right now.

Identity Governance is 3.5.0. It is installed on RHEL 7.6. Yes it is postgres, running on a different RHEL 7.6 box on the same subnet.

DB server was rebooted as well as the IG server, today. I had requested that the IG server have tomcat restarted in case it came up prior to the db server.

Any additional logging we can turn on or packet tracing? Any db maintenance we should look at?
0 Likes
Knowledge Partner
Knowledge Partner

Re: Identity Publication Issue

On 4/26/2019 3:54 PM, fp IDMWORKS wrote:
>
> I am aware of this issue with this installation. Chiming in in case he
> isn't available right now.
>
> Identity Governance is 3.5.0. It is installed on RHEL 7.6. Yes it is
> postgres, running on a different RHEL 7.6 box on the same subnet.
>
> DB server was rebooted as well as the IG server, today. I had requested
> that the IG server have tomcat restarted in case it came up prior to the
> db server.
>
> Any additional logging we can turn on or packet tracing? Any db
> maintenance we should look at?


Look through the XML logging config files in the tomcat/conf, there are
a ton of classes you can trying upping the logging.

I have found a couple of classes super helpful in troubleshooting. We
should probably start collecting notes on how to do that.


0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Identity Publication Issue

On 4/30/19 10:27 AM, Geoffrey Carman wrote:
> On 4/26/2019 3:54 PM, fp IDMWORKS wrote:
>>
>> I am aware of this issue with this installation. Chiming in in case he
>> isn't available right now.
>>
>> Identity Governance is 3.5.0. It is installed on RHEL 7.6. Yes it is
>> postgres, running on a different RHEL 7.6 box on the same subnet.
>>
>> DB server was rebooted as well as the IG server, today. I had requested
>> that the IG server have tomcat restarted in case it came up prior to the
>> db server.
>>
>> Any additional logging we can turn on or packet tracing? Any db
>> maintenance we should look at?

>
> Look through the XML logging config files in the tomcat/conf, there are
> a ton of classes you can trying upping the logging.
>
> I have found a couple of classes super helpful in troubleshooting. We
> should probably start collecting notes on how to do that.
>
>

Greetings,
There is a Service Request open on this and we are working it from
there.

--
Sincerely,
Steven Williams
Principal Enterprise Architect
Micro Focus
0 Likes
fp_idmworks Super Contributor.
Super Contributor.

Re: Identity Publication Issue

Updating to 3.5.1 addressed the issue.

We did have nested groups that were circular. There is a script from microsoft to find nested circular groups. Once fixed we still had the problem but there were issues addressed with publications in 3.5.1 that addressed it.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.