Vastloper bij uitvoeren van opdracht nav consult van eergisteren

N.a.v. de Teams-meeting van gisteren:
De opdracht “alter persistent cache force refresh approach copy” liep zojuist vast met een melding over zoiets als doorvoersnelheid dit niet gehaald kon worden.

Moet ik de opdracht opnieuw starten of kan ik het hierbij laten?

Zekerheidshalve heb ik de opdracht opnieuw gestart.

In de tracefile tref ik onderstaande informatie aan:

10:58:12.07901-d0-t4: 10:58:11.64357-AUTO-NumberOfStatementsExecuted-8a720f23-8a0d-4458-85a4-d2770b48927c-12: Change number of executed statements from 1 to 2.
10:58:12.07901-d0-t4: 10:58:11.64957-WPF-ProgressNotifier-1e3c4ebb-efc9-4e84-9c53-d05d79ec123e-1: Hide progress notifier.
10:58:12.07901-d0-t4: 10:58:11.70157-WPF-RibbonWindowBase-8ff105de-d4c0-4ff0-a3c9-0c9cc10ba5cc-12: Instantiate 'ValidationException', ID 'a86f6e23-66a8-4bf0-9f49-b3b8058d2912', code 'itgenqtl056': Statement #2 'alter persist... approach copy' beginnend op regel 3 veroorzaakte een fout. 
10:58:12.07901-d0-t4: 10:58:12.07801-WPF-RibbonWindowBase-8ff105de-d4c0-4ff0-a3c9-0c9cc10ba5cc-12: *** Process exception 'itgendch493', show to user is True. ***
10:58:12.33452-d0-t4: 10:58:12.08001-WPF-RibbonWindowBase-8ff105de-d4c0-4ff0-a3c9-0c9cc10ba5cc-12: System.ComponentModel.Win32Exception
System.Data.SqlClient.SqlException
InvantiveSystemException
ValidationException
ValidationException
   at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
   at System.Environment.get_StackTrace()
   at IBC.MDJ.U()
   at Invantive.Basics.ErrorConstants.GetEnvironmentStackTrace(Boolean ignoreErrors, String valueOnError)
   at Invantive.Data.ExtensionMethods.GetAllStackTraces(Exception exception, GlobalState owner, ExecutionOptions executionOptions, Boolean deepestFirst, Boolean useDefaultStackTrace)
   at Invantive.Data.Error.HandleUnexpectedException(GlobalState owner, ExecutionOptions executionOptions, DataContextBase dataContext, Nullable`1 messageId, Exception exceptionRaised, Boolean askContinue, String customErrorMessageWithoutCode, Boolean showErrorToUser, String parameters, LoggingLevel loggingLevel, String applicationNameWithVersion, String applicationName, String applicationVersion, String windowTitle, Dictionary`2 metrics, IBasicProviderInfo originatingProvider, String kindRequest)
   at Invantive.Data.Error.HandleUnexpectedException(GlobalState owner, ExecutionOptions executionOptions, Nullable`1 messageId, Exception exceptionRaised, Boolean askContinue, String customErrorMessageWithoutCode, Boolean showErrorToUser, String parameters, LoggingLevel loggingLevel, String applicationNameWithVersion, String applicationName, String applicationVersion, String windowTitle, Dictionary`2 metrics, IBasicProviderInfo originatingProvider)
   at Invantive.Producer.ApplicationErrorHelper.HandleUnexpectedException(GlobalState owner, ExecutionOptions executionOptions, Nullable`1 messageId, Exception exceptionRaised, Boolean askContinue, String customErrorMessage, Boolean showErrorToUser, String parameters, LoggingLevel level, Dictionary`2 metrics, IBasicProviderInfo originatingProvider)
   at Invantive.Producer.Windows.Forms.QueryToolResults.VYU(GlobalState , ExecutionOptions , String , String , Boolean ) in C:\Users\gle3.WS212\Documents\ws-master\Invantive.Producer\src\Invantive.Producer.Windows.Forms\QueryTool\QueryToolResultsViewModel.cs:line 22
   at Invantive.Producer.Windows.Forms.QueryToolResults.ExecuteStatements(GlobalState owner, ExecutionOptions executionOptions) in C:\Users\gle3.WS212\Documents\ws-master\Invantive.Producer\src\Invantive.Producer.Windows.Forms\QueryTool\QueryToolResults.cs:line 0
   at Invantive.Producer.Windows.Forms.QueryToolDocumentViewModel.IA.LA.MoveNext()
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Runtime.CompilerServices.AsyncMethodBuilderCore.MoveNextRunner.Run()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
10:58:12.33552-d0-t4: 10:58:12.14202-PROP-MaximumNumberOfUsablePartitions-6c165438-81b3-4737-8608-02f943b6faae-12: Reduced maximum number of usable partitions from 100.000 to 10.000 due to license constraints of license contract code 'L206' with key ID 132472197442063556.
10:58:12.33552-d0-t4: 10:58:12.15867-PROP-MaximumNumberOfUsablePartitions-5807a918-41e4-407c-9f4d-2bc3cdac66b5-12: Reduced maximum number of usable partitions from 100.000 to 10.000 due to license constraints of license contract code 'L206' with key ID 132472197442063556.
10:58:12.33552-d0-t4: 10:58:12.19667-WPF-RibbonWindowBase-8ff105de-d4c0-4ff0-a3c9-0c9cc10ba5cc-12: Statement #2 'alter persist... approach copy' beginnend op regel 3 veroorzaakte een fout.

Kan gegevens niet laden voor tabelpartitieversie '611.255 - Seeding v2 (table 92 - ExactOnlineREST.Incremental.TransactionLinesIncremental, partition 69 - 2274689).

SQL Server is not capable of handling the first bulk load of 3.000 rows into '[INVANTIVE-EOL].dbo.dcd_ed1c5' within 3600 seconds.

Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.

The wait operation timed out.
10:58:12.33552-d0-t4: 10:58:12.19784-WPF-RibbonWindowBase-8ff105de-d4c0-4ff0-a3c9-0c9cc10ba5cc-12: Please contact your system administrator or hire a SQL Server consultant to optimize throughput.
10:58:12.33552-d0-t4: 10:58:12.30151-WPF-RibbonWindowBase-8ff105de-d4c0-4ff0-a3c9-0c9cc10ba5cc-12: Send message 'itgendch493' of level 'Error' across Invantive Producer provider.
10:58:12.33552-d0-t4: 10:58:12.30652-WPF-RibbonWindowBase-8ff105de-d4c0-4ff0-a3c9-0c9cc10ba5cc-12: Manage execution of action 'LogError'.
10:58:12.33552-d0-t4: 10:58:12.31352-WPF-RibbonWindowBase-8ff105de-d4c0-4ff0-a3c9-0c9cc10ba5cc-12: Provider 'Invantive.Producer' handled action 'LogError' successfully.
10:58:12.33552-d0-t4: 10:58:12.31352-WPF-RibbonWindowBase-8ff105de-d4c0-4ff0-a3c9-0c9cc10ba5cc-12: Total execution time: 7 ms for -1 rows at level 0: 'Execute action LogError.'.
10:58:12.33552-d0-t4: 10:58:12.31352-WPF-RibbonWindowBase-8ff105de-d4c0-4ff0-a3c9-0c9cc10ba5cc-12: Message not registered through Invantive Producer provider.
10:58:12.33552-d0-t4: 10:58:12.31352-WPF-RibbonWindowBase-8ff105de-d4c0-4ff0-a3c9-0c9cc10ba5cc-12: Could not register message in central log since no provider handled it.
10:58:12.33552-d0-t4: 10:58:12.31452-WPF-RibbonWindowBase-8ff105de-d4c0-4ff0-a3c9-0c9cc10ba5cc-12: Start outbound logging message queue handler. Force send = False
10:58:12.33552-d0-t4: 10:58:12.31452-WPF-RibbonWindowBase-8ff105de-d4c0-4ff0-a3c9-0c9cc10ba5cc-12: Sender has status 'WaitingForActivation'.
10:58:12.33552-d0-t4: 10:58:12.31452-WPF-RibbonWindowBase-8ff105de-d4c0-4ff0-a3c9-0c9cc10ba5cc-20: Prepare to process queued Customer Service messages. Waiting for other handlers to complete.
10:58:12.33552-d0-t4: 10:58:12.31452-WPF-RibbonWindowBase-8ff105de-d4c0-4ff0-a3c9-0c9cc10ba5cc-12: At most 1 Customer Service envelopes left to process after adding one with approximate size of 297.822 bytes: a86f6e23-66a8-4bf0-9f49-b3b8058d2912-itgendch493
10:58:12.33552-d0-t4: 10:58:12.31452-WPF-RibbonWindowBase-8ff105de-d4c0-4ff0-a3c9-0c9cc10ba5cc-20: Processing queued Customer Service messages.
10:58:12.33552-d0-t4: 10:58:12.31652-WPF-RibbonWindowBase-8ff105de-d4c0-4ff0-a3c9-0c9cc10ba5cc-20: 0 customer service envelopes left to process after processing 0 simple envelopes in context 'regular'.
10:58:12.33552-d0-t4: 10:58:12.31652-WPF-RibbonWindowBase-8ff105de-d4c0-4ff0-a3c9-0c9cc10ba5cc-20: Sending 1 aggregated logging messages with approximately 297.822 bytes. Context 'regular'.
10:58:12.33552-d0-t4: 10:58:12.32752-WPF-RibbonWindowBase-8ff105de-d4c0-4ff0-a3c9-0c9cc10ba5cc-20: Post 142.254 bytes of data to URL '***'. Compress: False.
10:58:12.33552-d0-t4: 10:58:12.33452-WPF-RibbonWindowBase-8ff105de-d4c0-4ff0-a3c9-0c9cc10ba5cc-12: Use Invoke for dispatcher to handle 'PresentErrorToUser'.
10:58:12.59253-d0-t4: 10:58:12.39852-WPF-RibbonWindowBase-8ff105de-d4c0-4ff0-a3c9-0c9cc10ba5cc-1: Show error dialog with message: Statement #2 'alter persist... approach copy' beginnend op regel 3 veroorzaakte een fout.

Kan gegevens niet laden voor tabelpartitieversie '611.255 - Seeding v2 (table 92 - ExactOnlineREST.Incremental.TransactionLinesIncremental, partition 69 - 2274689).

SQL Server is not capable of handling the first bulk load of 3.000 rows into '[INVANTIVE-EOL].dbo.dcd_ed1c5' within 3600 seconds.

Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.

The wait operation timed out.
10:58:12.59354-d0-t4: 10:58:12.42653-WPF-RibbonWindowBase-8ff105de-d4c0-4ff0-a3c9-0c9cc10ba5cc-1: Show WPF error dialog with message 'Statement #2 'alter persist... approach copy' beginnend op regel 3 veroorzaakte een fout.

Kan gegevens niet laden voor tabelpartitieversie '611.255 - Seeding v2 (table 92 - ExactOnlineREST.Incremental.TransactionLinesIncremental, partition 69 - 2274689).

SQL Server is not capable of handling the first bulk load of 3.000 rows into '[INVANTIVE-EOL].dbo.dcd_ed1c5' within 3600 seconds.

Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.

The wait operation timed out.'.

Het is een grote foutmelding, ook omdat Data Replicator massief parallel gegevens verwerkt. Het essentiële deel is:

Hierin is te lezen dat de gebruikte SQL Server instance een timeout geeft bij het laden van 3.000 rijen. De gebruikte timeout is 1 uur (3600 seconden).

Advies is om de SQL Server DBA de instellingen te laten controleren.

1 Like

het aantal cores op de PZ-SQL02 en het intern geheugen is uitgebreid