DSXchange

We are using Information Analyzer 8.1.2 fix pack 3 on IIS client/server. If the length of user name used to run IA jobs is less than 64 characteres, all IA jobs run fine. On the other hand if the length of user name used to run IA jobs is more than 64 characters, we get the below error.

------------------------------------------------------------------------
[10/6/10 9:33:48:919 UTC] 00000037 ExceptionUtil E CNTR0020E: EJB
threw an unexpected (non-declared) exception during invocation of
method "setTaskScheduleStatus" on bean "BeanId(ACS_server.
ear#ACS_server.jar#SchedulerListener, null)". Exception data: javax.ejb.
EJBException: nested exception is: com.ascential.acs.scheduling.server.
impl.TaskScheduleDAOException: com.ascential.asb.util.sandbox.
DataAccessException: com.ascential.xmeta.exception.data.
DataLengthConstraintViolationException: A data length constraint was
violated on attribute "_xmeta_modified_by_user". The maximum allowed
length is 64, but the length of the value is 66. The value is "uid=s-
piiisadmlab-u-global,ou=ServiceAccounts,ou=Global,o=ikea.com". The RID
of the object is "d70c6594.80cb2b5c.47d676fc.197d6919-179b-4bf2.be21.
bb0f22bb218c". The displays attribute "null" has the value "null"
com.ascential.acs.scheduling.server.impl.TaskScheduleDAOException: com.
ascential.asb.util.sandbox.DataAccessException: com.ascential.xmeta.
exception.data.DataLengthConstraintViolationException: A data length
constraint was violated on attribute "_xmeta_modified_by_user". The
maximum allowed length is 64, but the length of the value is 66. The
value is "uid=s-piiisadmlab-u-global,ou=ServiceAccounts,ou=Global,
o=ikea.com". The RID of the object is "d70c6594.80cb2b5c.47d676fc.
197d6919-179b-4bf2.be21.bb0f22bb218c". The displays attribute "null"
has the value "null"
------------------------------------------------------------------------

Any help on this is appreciated.

Could be worth checking the XMETA database to determine whether the job name property for an IA job is data type VarChar(64). At the moment (weekend) I can't perform that check. But that would be my guess as to the cause.

Thanks for the information Ray.

I have logged a PMR with IBM on this issue and this is a known problem in version 8.1 and will be addressed in upcoming version 8.5 as per IBM. Thanks anyway.

Do you have a really long user id? Is "s-piiisadmlab-u-global" part of your user id? Just wondering if you could fix this problem by creating a shorter user name.

Actually we are using external registry (LDAP) and here it takes the complete qualified user name in case of IA. In this case the qualified user name is uid=s-piiisadmlab-u-global,ou=ServiceAccounts,ou=Global,o=ikea.com and its length comes out to be 66 characters.

As a work around, we have started creating LDAP users with qualified user name length less than 64 characters.

Perhaps using some of the IKEA product names?