{"id":147,"date":"2018-10-27T17:13:04","date_gmt":"2018-10-27T17:13:04","guid":{"rendered":"http:\/\/www.hammerdb.com\/blog\/?p=147"},"modified":"2019-08-15T17:30:06","modified_gmt":"2019-08-15T17:30:06","slug":"driving-hammerdbcli-from-a-bash-script","status":"publish","type":"post","link":"https:\/\/www.hammerdb.com\/blog\/uncategorized\/driving-hammerdbcli-from-a-bash-script\/","title":{"rendered":"Driving hammerdbcli from a bash script"},"content":{"rendered":"

Update:<\/strong> There is considerably more efficient method of running HammerDB through a bash script described in a more recent post here: \u00a0Running hammerdbcli from a bash or batch script updated for v3.2<\/a> It is strongly recommended to move to this method described for v3.2 rather than the method described in this post which can have a greater overhead and a potential impact on performance imposed by bash.<\/p>\n

A current FAQ is how to drive the command line hammerdbcli from an external bash script. <\/span>This post gives an example of one way which this can be done. <\/span><\/p>\n

For an example we will run a bash script that prints output and then runs hammerdbcli to build an Oracle schema before wating for this to finish and printing more output.\u00a0 Firstly we need the hammerdbcli script.\u00a0 Note that as HammerDB is multithreaded, adding exit to the end of a script will cause that script to terminate before virtual users are complete. This is unlikely to be the desired outcome. Therefore you need a function that will wait for the script to complete before issuing the exit. The important command here is vucomplete and you need to wait until the condition of this is “true”. An example of this is as follows: <\/span><\/p>\n

#!\/bin\/tclsh\nputs \"SETTING CONFIGURATION\"\nglobal complete\nproc wait_to_complete {} {\nglobal complete\nset complete [vucomplete]\nif {!$complete} {after 5000 wait_to_complete} else { exit }\n}\ndbset db ora\ndiset connection system_password oracle\ndiset connection instance vulpdb1 \ndiset tpcc count_ware 4\ndiset tpcc num_vu 4\ndiset tpcc tpcc_def_tab users\nprint dict\nbuildschema\nwait_to_complete<\/pre>\n
This script has been saved as buildora.tcl.\u00a0 Now we want the driving bash script that looks as follows: <\/span><\/p>\n
#!\/bin\/bash\necho \"BASH SCRIPT BEFORE BUILD..\"\n.\/hammerdbcli <<!\nsource buildora.tcl\n!\necho \"BASH SCRIPT AFTER BUILD..\"<\/pre>\n
if you want to redirect your output to a file it can look like the following:<\/p>\n
#!\/bin\/bash\necho \"BASH SCRIPT BEFORE BUILD..\"\n.\/hammerdbcli <<!>> buildora.output 2>&1\nsource buildora.tcl\n!\necho \"BASH SCRIPT AFTER BUILD..\"<\/pre>\n
If you run the bash script it will now call hammerdbcli that will run buildora.tcl, this will wait until complete to call exit before returning control back to the bash script. This is just one example of many ways in which hammerdbcli can be blended with Tcl, bash or even Python<\/a> to automate HammerDB functionality.<\/p>\n
If it is needed to strip the control characters from the output this can be done using sed. The stdbuf command can also be used to write the output line by line to the output file.<\/p>\n
#!\/bin\/bash\necho \"BASH SCRIPT BEFORE BUILD..\"\n.\/hammerdbcli <<! 2>&1 | stdbuf -oL -eL sed -e \"s,\\x1B\\[[0-9;]*[a-zA-Z],,g\" -e \"s,\\r,,g\" -e \"s,hammerdb>,,g\" -e \"s,after\\#[0-9]*,,g\" >> buildora.output\nsource buildora.tcl\n!\necho \"BASH SCRIPT AFTER BUILD..\"<\/pre>\n