Toad World® Forums

Toad for DB2 v5.6 B2831 - Document Recovery May Not Be Working

In the last 30 days I have come into the office only to find that all of my Quest Software products (Spotlight, Toad for DB2 v5.6, Toad for SQL Server v5.8) have closed down. The assumption is that my company installed software that required a forced restart. However, this is not normally an issue since I have Document Recovery active and set to 3 minute save intervals on both Toad products. I have Toad for DB2 running 5 days a week, 8 hours a day. I have come into the office many times to find that my PC has had a forced reboot, and it has never been an issue since Toad has always recovered my open editors. The Document Recovery feature may not be working in the beta version (or in my Toad for SQL Server).

Richard

Hi Richard,

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.

Regards,

Adam

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
directories.

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).

a.
Open an editor

b.
Write some SQL

c.
Wait for document recovery save interval to pass

d.
Kill Toad with task manager

e.
Restart Toad

f.
Toad recovered my editor successfully

Line

Action Log Entries

1

04/10/2014 14:32:39: Editor.Databases

2

04/10/2014 14:33:03: Editor.Databases

3

04/10/2014 14:33:15: Editor.Databases

4

04/11/2014 06:38:35: ApplicationInitializationStarted UAC

5

04/11/2014 06:38:44: ApplicationRecoverDocuments

6

04/11/2014 06:39:02: ApplicationInitializationEnded

7

04/11/2014 06:39:13: NewConnection.DB2 9.7.6

8

04/11/2014 06:39:14: DatabaseBrowser.ShowDatabaseBrowserEditionDepended

9

04/11/2014 06:39:31: Preferences.ShowOptionsTools

10

04/11/2014 06:49:36: ApplicationShutdown

11

04/11/2014 06:55:09: ApplicationInitializationStarted Administrator

12

04/11/2014 06:56:11: ApplicationInitializationStarted Administrator

13

04/11/2014 06:56:34: ApplicationInitializationEnded

14

04/11/2014 07:06:48: NewConnection.DB2 9.7.6

15

04/11/2014 07:06:49: DatabaseBrowser.ShowDatabaseBrowserEditionDepended

16

04/11/2014 07:06:56: Preferences.ShowOptionsTools

17

04/11/2014 07:08:31: Editor.ShowEditor

18

04/11/2014 07:41:00: ApplicationInitializationStarted Administrator

19

04/11/2014 07:41:05: ApplicationRecoverDocuments

20

04/11/2014 07:41:08: DocumentRecoveryManager.ShowDocumentRecoveryManager

21

04/11/2014 07:41:26: ApplicationInitializationEnded

Richard Chouanard, analytics consultant

DB2 Database Administrator

*Payment Operations Management/Float Datamart

*Ph: 480-724-2142

From: Adam Ririe [mailto:bounce-adamririe_906@toadworld.com]

Sent: Tuesday, April 15, 2014 11:57 AM

To: toaddb2beta@toadworld.com

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

Hi Richard,

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.

Regards,

Adam

To reply, please reply-all to this email.

Stop receiving emails on this subject.

Or
Unsubscribe from Toad for IBM DB2 - Beta
notifications altogether.

Toad for IBM DB2 - Beta Discussion Forum

Flag
this post as spam/abuse.

Hi Richard,

Are the unrecovered editors open on saved files without changes? I know this seems obvious, I'm just eliminating possibilities.

Also, have you changed these Toad Desktop options?

My Desktop options look just like the image other that in addition to Default I also have Administration and Debug. When I look in the Document Recovery folder
the only SQL files I see are from my current open editors. The is one other file and it is Manifest… XML file.

Richard Chouanard, analytics consultant

DB2 Database Administrator

*Payment Operations Management/Float Datamart

*Ph: 480-724-2142

From: Adam Ririe [mailto:bounce-adamririe_906@toadworld.com]

Sent: Wednesday, April 16, 2014 8:32 AM

To: toaddb2beta@toadworld.com

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

Hi Richard,

Are the unrecovered editors open on saved files without changes? I know this seems obvious, I’m just eliminating possibilities.

Also, have you changed these Toad Desktop options?

To reply, please reply-all to this email.

Stop receiving emails on this subject.

Or
Unsubscribe from Toad for IBM DB2 - Beta
notifications altogether.

Toad for IBM DB2 - Beta Discussion Forum

Flag
this post as spam/abuse.

Is normal Windows Update restarting your machine, or is it some other client management tool? What OS are you running?

Adam, Wells uses a software-push type tool. The thing that is different this last month as opposed to before is that my machine was not at the endpoint encryption
logon screen, but was at my desktop with all office products and IE open to basically where I had left them. The endpoint encryption logon occurs prior to Windows loading, so it was really easy to tell when the machine was restarted.

I run Windows 7 SP1.

Richard Chouanard, analytics consultant

DB2 Database Administrator

*Payment Operations Management/Float Datamart

*Ph: 480-724-2142

From: Adam Ririe [mailto:bounce-adamririe_906@toadworld.com]

Sent: Wednesday, April 16, 2014 11:46 AM

To: toaddb2beta@toadworld.com

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

Is normal Windows Update restarting your machine, or is it some other client management tool? What OS are you running?

To reply, please reply-all to this email.

Stop receiving emails on this subject.

Or
Unsubscribe from Toad for IBM DB2 - Beta
notifications altogether.

Toad for IBM DB2 - Beta Discussion Forum

Flag
this post as spam/abuse.