SYMPTOM:
When running a Transaction Services document and clicking submit to execute the transaction against the data warehouse, it is seen that the data is not inserted to the warehouse even though Strategy Web shows that the transaction was successful.
SQL Trace shows that no SQL was executed by the Intelligence Server, but Kernel XML indicates the Intelligence Server did receive the command from Strategy Web to execute the transaction
CAUSE:
A possible cause for this issue is that due to high memory usage on the Intelligence Server machine, the document instance of this Transaction Services document is swapped out of memory and into disk. Because of this, the document's data is lost. When the manipulation, such as sumbitting the transaction is applied, the document instance is reloaded into memory, and it is checked if the document instance needs to be re-executed.
There is a known issue in Strategy 9.4.1 that causes the document instance not to be re-executed even though it is required for the transaction to be successful.
ACTION:
This issue has been fixed in Strategy 9.4.1 Hotfix4. Upgrade to this version to take advantage of the fix.
WORKAROUND:
A workaround for this issue is increasing the Working Set RAM:
KB8617: What is the 'Working Set' governor setting in Strategy Intelligence Server 9.4.x-10.x?
Note: If any of the information is collected from external sources, please be sure to cite the source (i.e., give the author and his or her company appropriate credit). Technical notes should provide all the necessary information for solving an issue. Links to other technical notes or web pages should only provide additional information for further user reference.
WARNING MESSAGES: Only insert the appropriate one(s) if necessary
47127
