Consider that a service has been divided into the required number of segments in Strategy Narrowcast Server 9.0.0 - 9.2.x, but has to wait for more than 24 hours for the segments to get assigned to an execution engine. In such a scenario, the segment fails over and ultimately errors out the service execution, with the following error logged in the DELogs:
Sample Code/Error
:5344:Service ID Execution ID Segment ID Service execution has been divided into 1 segment(s).
...
...
Get Subscription Set request returned from database with error-Execute Query failed. Error type: Odbc error. Odbc operation attempted: SQLExecDirect. SQL0204N "DSCASTOR.YY0CA60A45320E414B82AA2EB9097FCCD1B" is an undefined name. SQLSTATE=42704
:7752:Service ID Execution ID Segment ID Unexpected error while receiving recipient array.
Note that the above service gets divided into 1 segment at 07/29/2011 13:09:33.833, but this segment begins to get processed more than 24 hours later by 07/30/2011 15:39:18.361.
After a service has been divided into the required number of segments, the information about the recipients who are part of the segment is stored in temporary tables by Strategy Narrowcast Server 9.0.0 - 9.2.x. These tables usually have prefixes such as YY or GG. For more information on this, refer to the following Strategy Knowledge Base technical note:
KB6787: Why tables with prefixes YY and GG get created by MicroStrategy Narrowcast Server 8.x - 9.0.x?
By design, these temporary tables are cleaned up 24 hours after they are created by Strategy Narrowcast Server 9.0.0 - 9.2.x. Hence in the above scenario, the temporary table holding the segment recipient information has already been deleted when the segment is about to be processed by the execution engine. Since this table can no longer be found, the segment fails over. As this segment's recipient information can never be found subsequently during this execution of the service, any fail-over attempts of the segment will also result in the same error. Once the maximum fail-over count has been reached, the segment and the service will error out.
If services are taking longer than 24 hours to be assigned to the execution engine, a registry key called "DropTempTableTimeout" can be created on the Strategy Narrowcast Server 9.0.0 - 9.2.x Distribution Manager machine(s). This key is located at the following location:
1. For 32-bit machines: \HKEY_LOCAL_MACHINE\SOFTWARE\MicroStrategy\Strategy Broadcast Server\7.0\Temp Tables\DropTempTableTimeout
2. For 64-bit machines: \HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\MicroStrategy\Strategy Broadcast Server\7.0\Temp Tables\DropTempTableTimeout
This key is not created by default when installing Strategy Narrowcast Server 9.0.0 - 9.2.x, so must be created as "REG_DWORD", as shown:
The value for this key should be specified in hours, and it will indicate the desired value for the periodic deletion of temporary tables in Strategy Narrowcast Server 9.0.0 - 9.2.x.
