Trouble with ASA9 database

[Former Member]

Hi,

We've got an ASA9 database that started causing us some trouble yesterday. It appears to not allow any connections to be made to it. Doesn't give any return messages, it just hangs at the client level and never does anything. The service window looks normal. Says the server is started normally, as well as the sharedmemory link, namedpipes link and TCPIP link. Starts on the port and says that it is now accepting requests. Try to connect through our application, scjview, dbisql, dbvalid, etc. all just hang with no response. Go to stop the service, and it just hangs as well. Have to kill all of the processes.

Had IT get me the backup, and it had the same problem. Had to go back 3 days to get a backup that would actually start and allow connections. I ended up translating the log and applying the sql to the last good backup in order to get us running again. Ran dbvalid against the database and nothing was found to be wrong.

I'm concerned that there is something else going on. Has anyone seen anything similar? Any thoughts on what the issue could be?

Thanks!

John

[former_member244518 · Accepted solution]

Hi John,

Assuming you still have a copy of the database that hangs, could you try starting it with request level logging enabled?

dbsrv9 -z -zr ALL -zo C:\path\to\file.txt database.db

As well as connecting with a client log:

dbisql -c "UID=DBA;PWD=sql;ENG=database;LOG=C:\path\to\file2.txt"

Which operating system are you running the server on?

Thanks,

Mikel

[Former Member · Accepted solution]

Yes I still have the suspect database. Ran both commands. Waited several minutes before ending task on both processes.

I believe the server is Windows Server 2008. I am also attempting to run these locally with a Windows 7 Pro

Files attached.

John

file2.txt.zip

file.txt.zip

[former_member244518 · Accepted solution]

Hi John,

Does the database contain sensitive information?

If not, could you obtain a dump file of the process while it is hung? You can do this using the procdump utility ("procdump.exe dbsrv9"). The resulting file should be small enough to compress and upload.

Be aware that the memory dump could contain any information from within the database in an unencrypted format (including passwords). If you have a support contract, your best option would be to open an incident.

Thanks,
Mikel