SQL Server ERRORLOG entries during VDB Provision and Refresh operations (KBA10716)

Issue

When performing VDB Provision or VDB Refresh operations, some or all of the following messages may appear in the SQL Server ERRORLOG.

Database preparation and provisioning

RESTORE DATABASE successfully processed 0 pages in 0.178 seconds (0.000 MB/sec).
Setting database option SINGLE_USER to ON for database 'DevDB'.
Setting database option MULTI_USER to ON for database 'DevDB'.
Setting database option NEW_BROKER to ON for database 'DevDB'.
Setting database option RECOVERY to SIMPLE for database 'DevDB'.
Setting database option SINGLE_USER to ON for database 'DevDB'.
Setting database option READ_WRITE to ON for database 'DevDB'.
Setting database option MULTI_USER to ON for database 'DevDB'.

Service Broker Messages

Setting database option NEW_BROKER to ON for database 'DevDB'.

Error: 9645, Severity: 16, State: 3.
Could not start Service Broker for database id: 7. A problem is preventing SQL Server from starting Service Broker. Check the SQL Server error log for additional messages.

An error occurred in the service broker manager, Error: 3602, State: 145.

Setting database option DISABLE_BROKER to ON for database 'DevDB'.

Database cleanup and recovery messages

Starting up database 'DevDB'.
RemoveStaleDbEntries: Cleanup of stale DB entries called for database ID: [7]
RemoveStaleDbEntries: Cleanup of stale DB entries skipped because master db is not memory optimized. DbId: 7.
Parallel redo is started for database 'DevDB' with worker pool size [1].
Parallel redo is shutdown for database 'DevDB' with worker pool size [1].

Applicable Delphix Versions

Click here to view the versions of the Delphix engine to which this article applies

Date	Release
Dec 20, 2023 \| Jan 10, 2024	18.0.0.0 \| 18.0.0.1
Nov 21, 2023	17.0.0.0
Oct 18, 2023	16.0.0.0
Sep 21, 2023	15.0.0.0
Aug 24, 2023	14.0.0.0
Jul 24, 2023	13.0.0.0
Jun 21, 2023	12.0.0.0
May 25, 2023	11.0.0.0
Apr 13, 2023	10.0.0.0 \| 10.0.0.1
Mar 13, 2023 \| Mar 20, 2023	9.0.0.0 \| 9.0.0.1
Feb 13, 2023	8.0.0.0
Jan 12, 2023	7.0.0.0
Releases Prior to 2023
Major Release	All Sub Releases
6.0	6.0.0.0, 6.0.1.0, 6.0.1.1, 6.0.2.0, 6.0.2.1, 6.0.3.0, 6.0.3.1, 6.0.4.0, 6.0.4.1, 6.0.4.2, 6.0.5.0, 6.0.6.0, 6.0.6.1, 6.0.7.0, 6.0.8.0, 6.0.8.1, 6.0.9.0, 6.0.10.0, 6.0.10.1, 6.0.11.0, 6.0.12.0, 6.0.12.1, 6.0.13.0, 6.0.13.1, 6.0.14.0, 6.0.15.0, 6.0.16.0, 6.0.17.0, 6.0.17.1, 6.0.17.2
5.3	5.3.0.0, 5.3.0.1, 5.3.0.2, 5.3.0.3, 5.3.1.0, 5.3.1.1, 5.3.1.2, 5.3.2.0, 5.3.3.0, 5.3.3.1, 5.3.4.0, 5.3.5.0, 5.3.6.0, 5.3.7.0, 5.3.7.1, 5.3.8.0, 5.3.8.1, 5.3.9.0
5.2	5.2.2.0, 5.2.2.1, 5.2.3.0, 5.2.4.0, 5.2.5.0, 5.2.5.1, 5.2.6.0, 5.2.6.1
5.1	5.1.0.0, 5.1.1.0, 5.1.2.0, 5.1.3.0, 5.1.4.0, 5.1.5.0, 5.1.5.1, 5.1.6.0, 5.1.7.0, 5.1.8.0, 5.1.8.1, 5.1.9.0, 5.1.10.0
5.0	5.0.1.0, 5.0.1.1, 5.0.2.0, 5.0.2.1, 5.0.2.2, 5.0.2.3, 5.0.3.0, 5.0.3.1, 5.0.4.0, 5.0.4.1, 5.0.5.0, 5.0.5.1, 5.0.5.2, 5.0.5.3, 5.0.5.4

Resolution

These messages are a normal part of the VDB Provision and Refresh process.

No action is required, and these messages can be ignored if the VDB operation completes successfully.

If a VDB Provision or Refresh operation fails, the ERRORLOG entries described in this article are unlikely to be relevant for troubleshooting, though other log entries may be helpful. Please review any error message shown in the Continuous Data Engine Management interface for further information and recommended actions.

KBA