Ok, so from what I found in the files and from the file sizes I reconstructed a possible snapshot chain.
The chain is: 5 -> 4 ->1 -> 14 -> 2 -> 6 -> db1.vmdk
I had to edit two of the .vmdk files (see attachment). The first fix was on No. 14 which pointed to a non-existing snapshot No. 13. The only (next) parent that makes sense here is No. 2, so I chained No. 14 to No. 2. The second fix was to edit the parrentCID in No. 6 to match the base disk's CID. The reason for this mismatch is most likely, because you powered on the VM with db1.vmdk used as the VM's virtual disk.
What I recommend you do now, is to replace the two .vmdk files (12 and 6) with the ones I attached to this post, and then clone the virtual disk from the command line by running vmkfstools -i db1-000005.vmdk db1-clone.vmdk
The next step is to either attach the newly created clone as an additional virtual disk to a helper VM, or - if you want to see whether the VM is able to boot - attach the db1-clone.vmdk directly to the db1 VM. In the second case, please create a new snapshot prior to powering on the VM with the cloned virtual disk. This way the db1-clone.vmdk will not be modified.
In any case be prepared that there might be corruption in the guest's file system!
André