Hi Adam, I am not sure what you mean by “in the same console” but I have both products running at the same time on the same machine but installed into different
Below is an extract from the DB2 Action.log file and the series of events as I remember them. The green-highlighted lines are when I started Toad. To me it seems
that Toad tried to launch the document recovery manager but was not successful. I presume that each time Toad either closes/starts successfully that it deletes any existing .SQL files in the Document Recovery directory?
I ended my day on 4/10 and had several editors open in both Toad for DB2 and SQL.
I remoted in on 4/11 to find both Toad versions shutdown (and also Spotlight for DB2).
I started Toad (line 4) expecting the document recovery to activate (line 5); however, it never did.
I shut down/restarted Toad hoping that document recovery would activate (lines 10-13).
I then decided to test the document recovery process (lines 17-21).
Open an editor
Write some SQL
Wait for document recovery save interval to pass
Kill Toad with task manager
Toad recovered my editor successfully
Action Log Entries
04/10/2014 14:32:39: Editor.Databases
04/10/2014 14:33:03: Editor.Databases
04/10/2014 14:33:15: Editor.Databases
04/11/2014 06:38:35: ApplicationInitializationStarted UAC
04/11/2014 06:38:44: ApplicationRecoverDocuments
04/11/2014 06:39:02: ApplicationInitializationEnded
04/11/2014 06:39:13: NewConnection.DB2 9.7.6
04/11/2014 06:39:14: DatabaseBrowser.ShowDatabaseBrowserEditionDepended
04/11/2014 06:39:31: Preferences.ShowOptionsTools
04/11/2014 06:49:36: ApplicationShutdown
04/11/2014 06:55:09: ApplicationInitializationStarted Administrator
04/11/2014 06:56:11: ApplicationInitializationStarted Administrator
04/11/2014 06:56:34: ApplicationInitializationEnded
04/11/2014 07:06:48: NewConnection.DB2 9.7.6
04/11/2014 07:06:49: DatabaseBrowser.ShowDatabaseBrowserEditionDepended
04/11/2014 07:06:56: Preferences.ShowOptionsTools
04/11/2014 07:08:31: Editor.ShowEditor
04/11/2014 07:41:00: ApplicationInitializationStarted Administrator
04/11/2014 07:41:05: ApplicationRecoverDocuments
04/11/2014 07:41:08: DocumentRecoveryManager.ShowDocumentRecoveryManager
04/11/2014 07:41:26: ApplicationInitializationEnded
Richard Chouanard, analytics consultant
DB2 Database Administrator
*Payment Operations Management/Float Datamart
From: Adam Ririe [mailto:firstname.lastname@example.org]
Sent: Tuesday, April 15, 2014 11:57 AM
Subject: RE: [Toad for IBM DB2 - Beta Discussion Forum] Toad for DB2 v5.6 B2831 - Document Recovery May Not Be Working
RE: Toad for DB2 v5.6 B2831 - Document Recovery May Not Be Working
Reply by Adam Ririe
The only way I’ve been able to reproduce this is to open an editor, not execute, and force shutdown of the machine before the auto recovery period expires. If I run the editor or wait until
the auto recovery period saves the doc, I can pull the plug on the machine, and Toad recovers the editors.
Are you running both Toads in the same console?
If you see this again, please check in your user documents directory …\AppData\Roaming\Quest Software\Toad for DB2 5.6\ for a directory named “Document Recoveryquestdb2”. Maybe somehow this
directory is lost in whatever your company installed software is doing. If you know a restart is coming I’d like to know if the directory exists before the restart, but not after.
To reply, please reply-all to this email.
Stop receiving emails on this subject.
Unsubscribe from Toad for IBM DB2 - Beta notifications altogether.
Toad for IBM DB2 - Beta Discussion Forum
this post as spam/abuse.