PM18034: UPDATING AN ENTRY BY THE UNIQUEID AND REPOSID MAY FAIL.

Fixes are available

APAR status

Closed as program error.

Error description

When updating an entry by the repository Id and uniqueId, each
repository is checked for the entry.  If the entry exists in the
database repository, but not in LDAP, an error as shown below
may occur.


[LDAP: error code 50 - Search operation not permitted ];
remaining name
'o=DBRepository'

LdapConnectio 1 com.ibm.ws.wim.adapter.ldap.LdapConnection
getAttributes Exception caught:
javax.naming.NameNotFoundException:
[LDAP: error code 32 - No Such Object];  remaining name
'o=DBRepository'


The correct behavior is for virtual member manager (VMM) to
only check the repository referenced in the reposId.

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V6.1 and V7.0                        *
****************************************************************
* PROBLEM DESCRIPTION: Update() to an entry by UniqueID and    *
*                      ReposId fails with                      *
*                      NameNotFoundExecption                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Update to an entry with ReposId and UniqueName keeps checking
all repositories and fails, because an entry does not exist in
the other repositories. For example, say a user user1 is in DB
and one attempts to update it with ReposId db1 and uniqueID
someUniqueID. Then even though we specified the reposID
it goes to LDAP and as the entry is not there, it throws a
NameNotFoundException and fails.

Problem conclusion

The given ReposId should will used and only the referred
repository will be used.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.35 and 7.0.0.15.  Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM18034
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61I
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-07-07
Closed date
2010-09-30
Last modified date
2011-08-03

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PM18034: UPDATING AN ENTRY BY THE UNIQUEID AND REPOSID MAY FAIL.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?