Activating a Rowkey for a Logical Unit hangs and eventually times out after roughly 30 minutes, even though the underlying table has only a handful of rows — both the Direct option and the Background Job option fail, and the background job can't easily be stopped without DBA involvement.

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

If the ROWKEY column already physically exists in the table, check for existing rows with a NULL ROWKEY value — populate any such NULL rows with a generated GUID directly via SQL first: UPDATE <table_name> SET ROWKEY = SYS_GUID() WHERE ROWKEY IS NULL; COMMIT;, then attempt the Rowkey activation through IFS again. This specific scenario commonly arises when a Rowkey was previously activated, then deactivated, and a later re-activation attempt is being made, or in environments where a related module is installed but a prerequisite table's Rowkey was never activated.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions