And now a fix to the fixes...

Just realised I uploaded the last build with Oracle Database 12c Release 1 ( jdbc drivers. I’ve fixed that (now drivers) and so feel free to download again.



Fixes to swingbench

Happy new year….

I’ve updated swingbench with some fixes. Most of these are to do with the new results to pdf functionality. But at this point I’m giving fair warning that the following releases will be available on Java 8 only.

I’m also removing the “3d” charts from swingbench and replacing them with a richer selection of charts build using JavaFX.

Also I’ve added some simple code to the jar file to tell you which version it is… You can run this with the command

$ java -jar swingbench.jar
Swingbench Version 2.5.955

As always you can download it here. Please leave comments below if you run into any problems.

PDF Generation of report files

I finally got round to adding some code that creates pdf files such that you can convert the “XML” result files into something more readable. However this new functionality requires a Java8 VM to work. You can download the latest build here.

All you need to do is to run swingbench and from the menu save the summary results.


Minibench and charbench will automatically create a results config file in the local directory after a benchmark run. The file that’s created will typically start with “result” and it should look something like this.

[bin]$ ls
                    ccwizard.xml        coordinator         oewizard            shwizard.xml
bmcompare           charbench           data                oewizard.xml        swingbench
ccconfig.xml        clusteroverview     debug.log           results.xml         swingconfig.xml
ccwizard            clusteroverview.xml minibench           shwizard

All you need to do after this is to run the “results2pdf command

[bin]$ ./results2pdf -c results2pdf

There’s really only 2 command line options

[bin]$ ./results2pdf -h
usage: parameters:
-c <filename>   the config file to convert from xml to pdf
-debug          send debug information to stdout
-h,--help       print this message
-o              output filename

They are for the input file (-c) and the output file (-o).

The resultant file will contain tables and graphs. The type of data will depend heavily on the type of stats collected in the benchmark. For the richest collection you should enable

  • Full stats collection
  • Database statistics collection
  • CPU collection

An example of the output can be found here.


I plan to try and have the resultant pdf generated and displayed at the end of every bench mark. I’ll include this functionality in a future build.

Application Continuity in Oracle Database 12c (

In this entry I’ll try and detail the steps required to get application continuity working with swingbench. I’ll create a video with a complete walk through of the build. It’s also possible this blog is likely to be updated regularly as I get feedback


The following assumptions are made

  • You have a working Oracle RAC Database 12c ideally running at version (Database and Clusterware)
  • You have downloaded the very latest version of swingbench
  • You’ve installed the SOE benchmark using the oewizard
  • You’re running on a Physical or Virtual Machine (Virtual Box)
  • You are using the thin jdbc driver with swingbench

My configuration

In this example I’m using a 2 node RAC cluster for simplicity but I’ve validated the configuration on an 8 node cluster as well. My configuration

OS : Linux 6
Nodes : RAC1, RAC2
SCAN : racscan
CDB : orcl
PDB : soe
schema : soe

So after you’ve confirmed that the soe benchmark has been installed correctly the next step is to define the services. I created two new ones to show the difference between Application Continuity and standard Fast Application Failover. First a non Application Continuity Service

srvctl add service -d orcl -s soepdb -pdb soe -preferred orcl1,orcl2
srvctl modify service -db orcl -service soepdb -failoverdelay 5
srvctl modify service -db orcl -service soepdb -failoverretry  60
srvctl modify service -db orcl -service soepdb -clbgoal SHORT
srvctl modify service -db orcl -service soepdb -rlbgoal SERVICE_TIME

Now a service defined for Application Continuity

srvctl add service -db orcl -service soepdb_ac -commit_outcome TRUE -retention 86400 -preferred orcl1,orcl2
srvctl modify service -db orcl -service soepdb_ac -failovertype TRANSACTION
srvctl modify service -db orcl -service soepdb_ac -failoverdelay 5
srvctl modify service -db orcl -service soepdb_ac -failoverretry  60
srvctl modify service -db orcl -service soepdb_ac -session_state STATIC
srvctl modify service -db orcl -service soepdb_ac -clbgoal SHORT
srvctl modify service -db orcl -service soepdb_ac -rlbgoal SERVICE_TIME

Then grant access to the Application Continuity package to the SOE use


And thats it for the database/grid. All we need to do now is to configure swingbench to connect to the services. You can do this either in the command line, swingbench GUI or by editing the config file. The connect string should look similar to this (for application continuity)

    (HOST = racscan)
    (PORT = 1521)
    (SERVICE_NAME = soepdb_ac)

NOTE : EZConnect strings won’t work for this.

We’ll also need to use connection pooling. The pool definition is only example and should reflect the total number of threads you plan to run with. If you’ve edited the definition in the config file you should end up with something similar to


Or if you modify it via the GUI.


The final step is to enable the application continuity driver and FAN you can again do this in the config file with the following settings

            <Property Key="StatementCaching">50</Property>
            <Property Key="FastFailover">true</Property>
            <Property Key="FetchSize">20</Property>
            <Property Key="OnsConfiguration">nodes=rac1:6200,rac2:6200</Property>
            <Property Key="AppContinuityDriver">true</Property>

or via the GUI


For my test I used the following Load configuration


Or via the GUI


My complete config file is available here for reference

I’d initially suggest running with swingbench to enable the monitoring of errors. Start swingbench


You should see a balanced number of users logged on across your instances. Although though may fluctuate depending on a number of factors.


The next step is to cause an unexpected termination of one of the resources. I’d suggest killing PMON i.e.

[oracle@rac2 ~]$ ps -def | grep pmon
oracle    4345     1  0 05:00 ?        00:00:00 asm_pmon_+ASM2
oracle   18093     1  0 08:11 ?        00:00:00 ora_pmon_orcl2
oracle   25847  6655  0 08:37 pts/1    00:00:00 grep pmon
[oracle@rac2 ~]$ kill -9 18093

You should see a little disruption in the TPS as you kill the instance. How long will depend on your RAC configuration and power of machine. The following screen shot is from 2 VMs running on my mac. But the important point is that swingbench won’t get any errors.


To try and see what happens without application continuity try changing the connect string to point at the non application continuity service.


Then delete the property that forces swingbench to use the Application Continuity Driver.


Rerunning and terminating the instance should result in something like this.


The important point here is the errors which normally an application developer would need to handle without the guarantee of transactions not being applied more than once.


On the subject of donations

Some of you may have noticed that on the side of the page I ask for donations. I haven’t been totally open about where that money goes to, so let me clear that up now. Over the years, like many people, I’ve seen the terrible pain and suffering cancer can inflict on friends and family. So all the donations that I receive via PayPal are given straight to Cancer Research UK and the British Red Cross. Clearly there’s no need to make it directly to me, you can pass it onto your local organisations.

So once again thank you to everybody that makes a donation.