This chapter describes the how to work with Oracle Load Testing session data. The following session actions are available:
Attach to and detach from sessions that are running on the Oracle Load Testing server. This enables a tester to share real-time test results and to collaborate with team members during testing.
Export specific session data from and import session data to any Oracle Load Testing instance. This enable users to share session data stored on one instance of Oracle Load Testing with other users running another instance of Oracle Load testing without having to export and import an entire Oracle Load Testing database. The user importing the session data can then generate reports for the data using their own Oracle Load Testing instance.
You can attach to another running session on the Oracle Load Testing Server. To attach to a session:
Select Attach from the Sessions menu.
<session list> - lists all sessions that are running on the Oracle Load Testing Server. Select a session and click OK.
Attach mode - select how you want to attach to the session:
View Only - select this option to attach to the session in view only mode. This mode allows you access to graphs.
Full Control - select this option to attach to the session with full control. This option allows you to control tests.
Select the session to which you want to attach.
Select the mode in which you want to attach.
Click OK.
If you have attached to a session, you will need to detach from it to run a separate test.
To detach from a session, select Detach from the Sessions menu.
You can export Oracle Load Testing session data to an external file which can than be imported into another instance of Oracle Load Testing installed elsewhere.
To export Oracle Load Testing session data:
Select Export from the Tools menu.
Select OLT Session Data as the Type. The Source list shows the list of sessions stored in the Oracle Load Testing database. The Source list uses the following markers to indicate if a session can be exported or not:
Check mark: indicates the session can be exported.
X-mark: indicates the session cannot be exported. Sessions that cannot be exported include running sessions, sessions currently being imported, and sessions in a Reservation status.
Select the session to export and click Export. You can also double-click a session name to start the export.
Click Save when the File Download dialog box appears.
Specify the location and file name and click Save.
The default name of the file is the same as the session name. The filename can be changed to any other name. The data is not affected.
The exported file has a .osd (OLT Session Data) file extension. The file is in .zip compression format. You can change the extension to .zip and open the file in any ZIP utility to access the raw data. However, the file extension must be .osd to import the file into another Oracle Load Testing instance. The file structure is as follows:
Session Data\
db\
sessionRun.csv
scenarioReports.csv
counterHDR.csv
counterRun.csv
awrInfo.csv
vulog.csv
metadata.csv
All the Database related data is stored in /Session Data/db/. The db folder contains comma-separated-value (.csv) files which represent corresponding tables and their session related data in the database. Each .csv file contains the column names as their first row and the values on subsequent lines. All the .csv files are encoded in UTF-8 format.
You can import Oracle Load Testing session data that has been previously exported from another Oracle Load Testing instance as an Oracel Session Data (.osd) file.
To import Oracle Load Testing session data:
Select Import from the Tools menu.
Select OLT Session Data as the Type. The File To Import list shows the list of sessions stored in the current Oracle Load Testing instance database.
Click Browse in the File To Import section and select the session .osd file to import and click Open.
Click Import. The Session Import Wizard shows the session details.
Session Details - shows the details for the data included in the .osd file being imported, as follows:
Name - shows the name of the load testing session.
Start Time - shows the date and time the session started.
End Time - shows the date and time the session ended.
Machine - shows the name of the machine on which the session ran.
VUDisplay Data - shows if Oracle Load Testing virtual user logs data is included in the session data.osd file being imported or not. Yes indicates the .osd file includes virtual user logs data. No indicates the .osd file does not include virtual user logs data.
ADDM/AWR Data - shows if Automatic Database Diagnostic Monitor (ADDM) Report and Automatic Workload Repository (AWR) Report data is included in the session data.osd file being imported or not. Yes indicates the .osd file includes ADDM/AWR data. No indicates the .osd file does not include ADDM/AWR data.
Counter Definitions - shows the number of counter definitions included in the in the session data.
Counter Values - shows the number of counter values included in the session data.
Click Next. The Session Import Wizard shows the session name details.
Original Session Name - shows the name of the session that was exported from the original Oracle L.oad Testing instance. This session name will be the name of the session as it was exported from the original Oracle Load Testing instance regardless of the .osd file name.
New Session Name - provides a text box for renaming the session being imported (optional). The default is the original session name.
<Session List> - shows the sessions already in the current Oracle Load Testing instance.
Optionally specify a new session name and click Import. If you attempt to import a session with the same name as a session that already exists in the Session List, a Confirm message appears asking if you wish to overwrite the existing session. Select Yes to import and overwrite or No to cancel.
Click OK when the Info box appears indicating the import was successful. The imported session will now appear in the Session Lists of the current Oracle Load Testing instance.
Click the Create Reports tab and select the imported session name to generate reports from the session data.