Fixes are available
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
The virtual member manager (VMM) database schema (wimdbproperties.xml) is missing the definition of the 'city' property, due to which tables created for the database repository will not contain the 'city' property.
Local fix
Ø 1) Fix the wimdbproperties.xml by adding definition to 'city' attribute. Drop the tables in the database, and create them again using '$AdminTask setupIdMgrDBTables' command. 2) In most cases, tables contain users/groups information, which cannot be deleted and re-created back. So we'll have to update the wimdbproperties.xml and manually add the entries to the DB tables. Below are the steps for manually adding the 'city' attribute to DB tables. - - - - - - - - - - - - - - - - - - - - - - - - - - Manual steps to add 'city' attribute in DB table: - - - - - - - - - - - - - - - - - - - - - - - - - - 1) Edit $WAS_HOME\etc\wim\setup\wimdbproperties.xml file, look for the entry <wimprop:property wimPropertyName="street" dataType="String" valueLength="128"> <wimprop:applicableEntityName> ... ... </wimprop:property> Just next the above entry, add a new property definition for 'city' as follows: <wimprop:property wimPropertyName="city" dataType="String" valueLength="128"> <wimprop:applicableEntityName> <wimprop:entityName>Person</wimprop:entityName> <wimprop:entityName>PersonAccount</wimprop:entityName> </wimprop:applicableEntityName> </wimprop:property> Save changes to wimdbproperties.xml. 2) Connect to the database (as defined for the DatabaseRepository, normally contained in the dbURL. Eg: OVWPSPV1). (a) Scan the PROP_ID column in DBPROP table (arrange the values for PROP_ID in ascending order) to determine the last entry (with highest value) say PROP_ID_MAX_VAL. (b) Then add(insert) another row to the DBPROP table, with the following values: (PROP_ID, NAME, TYPE_ID, META_NAME, DESCRIPTION, IS_COMPOSITE, VALUE_LENGTH, READ_ONLY, MULTI_VALUED, CASE_EXACT_MATCH, CLASSNAME, APPLICATION_ID) = (PROP_ID_MAX_VAL+1, 'city', 'STRING', 'DEFAULT', NULL, 0, 128, 0, 1, 1, NULL, 'com.ibm.websphere.wim') where, PROP_ID_MAX_VAL+1 evaluates to numerical value, one higher than the current highest value of PROP_ID in the table. Eg: If current highest value for PROP_ID is 10014, then set [PROP_ID_MAX_VAL+1] = 10015. (c) Update the DBPROPENT table, by adding(inserting) the following two entries: (PROP_ID, APPLICABLE_ENTTYPE, REQUIRED_ENTTYPE) = (PROP_ID_MAX_VAL+1, 'Person', 0) (PROP_ID, APPLICABLE_ENTTYPE, REQUIRED_ENTTYPE) = (PROP_ID_MAX_VAL+1, 'PersonAccount', 0) 3) Re-start database, WAS. 4) Perform operations such as create/update users, to include 'city' attribute and verify that the DBPROP and other tables are being populated successfully.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server virtual member manager (VMM) * **************************************************************** * PROBLEM DESCRIPTION: VMM 'city' property is missing in the * * VMM database schema definition. * **************************************************************** * RECOMMENDATION: * **************************************************************** The VMM database schema is missing the definition of a 'city' property, due to which tables created for the database repository will not contain the 'city' property.
Problem conclusion
The fix adds the 'city' property in the VMM database schema file. The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.39, 8.0.0.11 and 8.5.5.7. 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
PI36794
Reported component name
WEBSPHERE PORTA
Reported component ID
5724E7600
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-03-11
Closed date
2015-06-05
Last modified date
2015-06-05
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R700 PSY
UP
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
28 April 2022