Wednesday, December 24, 2014

OATS: All Things about OLT Sessions

Oracle Load Testing(OLT)[1] is a component of Oracle Application Test Suite (OATS), which can simulate hundreds of virtual users accessing the application simultaneously and measures the effect of the load on application performance.

The results of load tests are grouped by sessions which are stored in Oracle database.  Oracle Load Testing then allows you to create customized post-run reports on the results of your load tests.


After you've run many load tests, eventually you could run into:
ORA-01654: unable to extend index OLT.COUNTERRUN_IDX by 1024 in tablespace USERS
OLT comes with a Session Manager which allows you to manage session data in the database:
  • Edit
    • Displays the Edit Session dialog box for changing the name and description of the session.
  • Delete
    • Deletes the entire selected session data from the database.
  • Delete Virtual User Logs
    • Deletes only the VU log data for the selected sessions. 
The easiest solution to the ORA-01654 is to delete old session data as shown below:

On the other hand, if you are using Oracle EE[2,3] and have enough disk space, all you need to do is:
Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.

Note that if you are currently using XE, we would recommend you use a dedicated machine for database and use Oracle EE.

Attach to Session

Read [4] for how to set up autopilot.  After setting up the parameters of autopilot, you can run scenarios from the command line.[4]  Assuming you have done that, then you can monitor load test session by attaching to it in OLT.  This enables a tester to share real-time test results and to collaborate with team members during testing.

From menu Session, select Attach.... The current running session as below should be listed.

You can then select how you want to attach to the session:

No comments: