Question Re: Assertion Faileure 201503 in Technology Q&A

Assertion Faileure 201503

iamdna — Thu, 27 Mar 2025 14:51:35 GMT

Hi,

We have a database that is failing to start with Assertion Failed: 201503.
Record 0x1 not present on page.

We are unable to unload the database excluding any corrupted table as the database will not even initialise.

Unfortunately despite running validation checks each evening the corruption has only revealed itself on startup therefore previous backup now also fail to start.

Do you know if there any tools that would allow us to rebuild this database?

Thanks in advance

Damian

Re: Assertion Faileure 201503

chris_keating — Fri, 28 Mar 2025 01:38:52 GMT

Please provide the full Assertion message specifically the value that follows "on page". This will contain info about the page type.

Re: Assertion Faileure 201503

iamdna — Fri, 28 Mar 2025 07:43:10 GMT

Record 0x1 not present on page 0x0:0x50475

Re: Assertion Faileure 201503

iamdna — Fri, 28 Mar 2025 08:23:39 GMT

Starting database "TEST" (C:\Temp\TEST.db) at Fri Mar 28 2025 08:21
Database recovery in progress
Last checkpoint at Tue Mar 18 2025 19:49
Checkpoint log...
Opening dbspace 'TEST' in file 'TEST.DBS' for database 'TEST'
Transaction log: TEST.log...
*** ERROR *** Assertion failed: 201503 (17.0.9.4913)[TEST]
Record 0x1 not present on page 0x0:0x50475

Re: Assertion Faileure 201503

chris_keating — Fri, 28 Mar 2025 14:43:54 GMT

Just to confirm, there are no backups that are healthy that can be used as a starting point for a recovery? Are you able to restart the database without the transaction log (try starting with -f on a copy of the database)?

Re: Assertion Faileure 201503

iamdna — Fri, 28 Mar 2025 16:21:48 GMT

There are no recent backups and we are looking to see if we have any older backups that are archived that don't have the corruption.
We have tried the -f but the issue still persists unfortunately.

Re: Assertion Faileure 201503

johnsmirnios — Fri, 29 Aug 2025 12:33:20 GMT

If you are using '-f', you must also move the TEST.log file out of the way. '-f' means it's okay not to apply the redo log during recover if the redo log cannot be found.

Re: Assertion Faileure 201503

johnsmirnios — Fri, 29 Aug 2025 12:35:52 GMT

If you can get the database started (see my comment about -f and renaming the .log file), try an unordered unload (dbunload -u) which will prevent the usages of key indexes. Failing that, we have been able to recover some databases if you send it to support.