SQL statement history storage

Hitting the wrong button in iSeries can cause a serious headache. If you have exited an STRSQL session without saving and want to retrieve your lost information, you may be out of luck. But Scott Ingvaldson explains where SQL statement history is stored, and how it can be retrieved.

Scott Ingvaldson

Published: 28 Apr 2008

I was using the standard STRSQL command and exited after use. When I exited I chose option 2=Exit without saving...

Step 2 of 2:

You forgot to provide an Email Address.

This email address doesn’t appear to be valid.

This email address is already registered. Please login.

You have exceeded the maximum character limit.

Please provide a Corporate E-mail Address.
- I agree to TechTarget’s Terms of Use, Privacy Policy, and the transfer of my information to the United States for processing to provide me with relevant information as described in our Privacy Policy.
Please check the box if you want to proceed.
- I agree to my information being processed by TechTarget and its Partners to contact me via phone, email, or other means regarding information relevant to my professional interests. I may unsubscribe at any time.
Please check the box if you want to proceed.

session, instead of option 1=Save and exit session. Now I have lost all my cumulative SQL history. Do you know where this data was kept? I may be able to restore it from my last backup. I have been unable to locate where the SQL statement history is kept.

Interactive SQL statement history is kept in an object named ISQLST-usrprf-devicename in the library QRECOVERY.

You can display the statement history with this command:
DMPSYSOBJ ISQLSTuuuuuddddd QRECOVERY TYPE(19) SUBTYPE(EE)

Unfortunately, Qrecovery does not get saved with the standard save commands. Unless you have explicitly saved objects from Qrecovery, I don't think you'll have anything to restore. If you had lost your SQL statement history due to changing your device name you might be able to retrieve it with the above command.

A more permanent way to save your statement history when exiting SQL is to use option 4=Save session in source file.

Dig Deeper on iSeries SQL commands and statements

Microsoft SQL Operations Studio eases SQL Server admin tasks SQL Operations Studio simplifies routine administration of SQL Server and Azure SQL databases, making database development and management easier for users who aren't full-time DBAs.

Mastering the Linux history command Learning how to take advantage of the Linux history command, as well as the Bash variant, can save Linux admins a lot of time. Discover how the command works, including shortcuts, searching and settings.

Detecting system changes made by outside IP address If you suspect that changes are being made by an external source, you can use an exit point program to monitor the activity and trace the IP address.

Insert not showing in v$sqlarea If a stored PL/SQL procedure is executed, all the DML in the procedure should show up in v$sqlarea, right? My test case shows it's not there. Why don't I see the insert?

Updating rows with a cursor is slow

How to stop scripts when error condition occurs

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

Meet all of our AS/400 experts

View all AS/400 questions and answers

Please create a username to comment.

Understand top public cloud repatriation use cases

Microsoft quantum development turns toward hardware

Top 5 options for Linux certifications

Dig Deeper on iSeries SQL commands and statements

Related Q&A from Scott Ingvaldson

Have a question for an expert?

Start the conversation

0 comments

Register

Login

Forgot your password?

Your password has been sent to:

Please create a username to comment.