craig_welton
Legendary Poster
Hello all,
Need a little help regarding table changes and deployment to the JAS server ...
E900, Websphere 6.1, TR 8.98.3.4, iseries enterprise
- Table X was changed to include a new column.
- Promoted to PY (with related objects that use the table), update package built and deployed.
- Table generated in PY.
- Enterprise server recognizes new table structure.
- Developer clients see changes and local web works fine.
+ JAS server reports [TABLE_SPECS_PHYSICAL_TABLE_MISMATCH] errors when application ER uses table IO to access the updated table. Databrowser works fine.
Services/instances bounced, no help.
What am I missing?
thanks,
Craig
Need a little help regarding table changes and deployment to the JAS server ...
E900, Websphere 6.1, TR 8.98.3.4, iseries enterprise
- Table X was changed to include a new column.
- Promoted to PY (with related objects that use the table), update package built and deployed.
- Table generated in PY.
- Enterprise server recognizes new table structure.
- Developer clients see changes and local web works fine.
+ JAS server reports [TABLE_SPECS_PHYSICAL_TABLE_MISMATCH] errors when application ER uses table IO to access the updated table. Databrowser works fine.
Services/instances bounced, no help.
What am I missing?
thanks,
Craig