Troubleshoot: Changed data
When data is changed in the WebSphere Commerce database, it will sometimes appear not to have any effect on the server functionality -- specifically, when the values are modified directly through massload or through SQL statements. Certain tables are cached for performance reasons, and their values will not be reread by WebSphere Commerce until the server is restarted or the registry is refreshed. Examples of cached tables are the STORE table or the URLREG table.
To ensure that changed data is loaded by WebSphere Commerce, update the appropriate registry component.
Related concepts
Related tasks