Merge branch 'jfkdev' into bkedev plus final 3.1.2 updates

oracle · Mar 7, 2024 · 4f81c00 · 4f81c00
2 parents a630077 + a897efc
commit 4f81c00
Show file tree

Hide file tree

Showing 126 changed files with 3,558 additions and 2,951 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,6 +1,6 @@
 # RWP\*Load Simulator Release Notes
 
-## 3.1.1
+## 3.1.2
 
 * Bug fixes
 * Statisitcs count only increased when no ORA- error during execution
@@ -11,6 +11,8 @@
 * Changes to repository
 * Full end-to-end tracing (on Linux only)
 
+Note that there was no release 3.1.1
+
 ## 3.1.0
 
 * Bug fixes

diff --git a/admin/rwl311.sql → admin/rwl312.sql b/admin/rwl311.sql → admin/rwl312.sql
diff --git a/docs/INSTALL.md b/docs/INSTALL.md
@@ -8,7 +8,7 @@ There are three types of binary distributions available at github releases:
 
 ### Using complete binaries
 
-Complete binaries distributed in a file such rwloadsim-linux-x86_64-bin-3.1.1.tgz
+Complete binaries distributed in a file such rwloadsim-linux-x86_64-bin-3.1.2.tgz
 can be used as is, i.e. without getting a clone or pull from github.
 It should be used if you simply want a full run time environment
 and it contains the following directories:
@@ -27,7 +27,7 @@ and it contains the following directories:
 If you prefer to have access to source code, but avoid building the executables,
 you can clone or pull from github (which would allow you to potentially compile
 rwloadsim yourself), and then 
-use a file like rwloadsim-linux-x86_64-binonly-3.1.1.tgz.
+use a file like rwloadsim-linux-x86_64-binonly-3.1.2.tgz.
 This file contains little more than the compiled binaries of the rwloadsim program,
 and you can simply un-tar this file
 directly into your cloned or pulled directory; the result will be as if you had
@@ -46,7 +46,7 @@ On the system where you are going to run rwloadsim,
 create a (possibly shared) directory where you simply
 use a command like
 ```
-tar -zxvf rwloadsim-linux-x86_64-bin-3.1.1.tgz
+tar -zxvf rwloadsim-linux-x86_64-bin-3.1.2.tgz
 ```
 One install can be shared between several users as long as all have access to the directory.
 If appropriate, you can put the directory on an NFS (or some other) share and make it available to multiple systems.
@@ -66,7 +66,7 @@ You can use Oracle Instant Client or a full client (or even server) install.
 Start by doing a pull or clone of the sources from github 
 as if you would do your own compile, and then use a command like
 ```
-tar -zxvf rwloadsim-linux-x86_64-binonly-3.1.1.tgz
+tar -zxvf rwloadsim-linux-x86_64-binonly-3.1.2.tgz
 ```
 to extract little more than the compiled rwloadsim binaries into your already existing pull or clone.
 
@@ -157,16 +157,16 @@ If you are sharing the repository between many different users/projects, having
 the grants are set to only allow the needed access to the various repository tables.
 For most tables, this is insert and select.
 
-### Updating the repostitory to version 3.1.1
+### Updating the repostitory to version 3.1.2
 
-In version 3.1.1, there is a new column added to oltpxc and any existing
+In version 3.1.2, there is a new column added to oltpxc and any existing
 repository need to be updated to reflect this.
-If you have an existing repository created earlier than version 3.1.1
+If you have an existing repository created earlier than version 3.1.2
 and you are upgrading to a version
-3.1.1 or later, you must execute the file rwl311.sql 
+3.1.2 or later, you must execute the file rwl312.sql 
 logged in using sqlplus to your primary
 repository schema.
-The rwl311.sql file is found in the admin directory of your distribution.
+The rwl312.sql file is found in the admin directory of your distribution.
 
 There are similarly updates to rwlviews.sql which must be executed against your primary and
 possibly secondary repository schema.
@@ -182,7 +182,7 @@ as you will otherwise get ORA- errors during execution of the oltpworkload.
 
 If you have an existing repository created earlier than version 3.0.6
 and you are upgrading to a version
-3.0.6 or later (including 3.1.1), you must execute the file rwl306.sql (which includes an
+3.0.6 or later (including 3.1.2), you must execute the file rwl306.sql (which includes an
 update to the persec table) logged in using sqlplus to your primary
 repository schema.
 The rwl306.sql file is found in the admin directory of your distribution.
@@ -233,7 +233,7 @@ If your only interest is to use utilities such as ociping or awrreport, you can
 get these completely stand-alone.
 This does _not_ include the complete rwloadsim, and does _not_ allow you
 to create any rwl programs yourself.
-The file such as generated-linux-x86_64-bin-3.1.1.tgz _only_ contains binaries
+The file such as generated-linux-x86_64-bin-3.1.2.tgz _only_ contains binaries
 that you simply put into any directory, typically one in your PATH.
 The only other requirement is an Oracle client environment as explained above.
 

diff --git a/docs/NEWS31.md b/docs/NEWS31.md
@@ -1,6 +1,6 @@
-## News and updates for version 3.1.1 of the RWP\*Load Simulator
+## News and updates for version 3.1.2 of the RWP\*Load Simulator
 
-The most important changes in version 3.1.1 are:
+The most important changes in version 3.1.2 are:
 
 ### Availability on Microsoft Windows
 
@@ -25,6 +25,8 @@ the runres and possibly persec repository tables) you can now also get the
 application time and database time.
 This feature is currently only available on Linux.
 
+Note that release 3.1.1 was skipped.
+
 ## News and updates for version 3.1.0 of the RWP\*Load Simulator
 
 Version 3.1 has particular focus on making rwloadsim more versatile as a scripting tool.

diff --git a/docs/ORACLENET.md b/docs/ORACLENET.md
@@ -52,7 +52,7 @@ or ```rwlman nettest```.
 
 In addition to being part of the full rwloadsim distribution,
 the three utilities are distributed together with other as completely stand-alone
-executables in the file generated-linux-x86_64-bin-3.1.1.tgz.
+executables in the file generated-linux-x86_64-bin-3.1.2.tgz.
 It only contains the executable files, and they can be used without a complete installation
 of rwloadsim, as long as there is an Oracle client environment that can be an ordinary
 installation or an Instant Client installation.
@@ -63,7 +63,7 @@ with Instant Client it is the top directory of the installation.
 
 After download, simply execute
 ```
-tar -zxvf generated-linux-x86_64-bin-3.1.1.tgz
+tar -zxvf generated-linux-x86_64-bin-3.1.2.tgz
 ```
 and possibly move the executables to one of the directories in your PATH.
 To get help for either, call it with the -h option.

diff --git a/docs/README.md b/docs/README.md
@@ -4,12 +4,12 @@ An introduction and the users guide to the RWP\*Load Simulator is available at
 [index.md](index.md) for your actual branch or
 [https://oracle.github.io/rwloadsim/](https://oracle.github.io/rwloadsim/)
 for the current
-[binary release 3.1.1](https://github.com/oracle/rwloadsim/releases).
+[binary release 3.1.2](https://github.com/oracle/rwloadsim/releases).
 
 ## RWP\*Load Simulator reference manual
 
 The reference manual is available after installation by typing
 ```
 rwlman
 ```
-or online (for release 3.1.1) in [refman/README.md](refman/README.md)
+or online (for release 3.1.2) in [refman/README.md](refman/README.md)
diff --git a/docs/WINDOWS.md b/docs/WINDOWS.md
@@ -24,12 +24,12 @@ As for Linux, there are two different downloads available:
 A full installation to be used if you want to run your own rwl programs, and a version that only
 contains a set of generated executables such as ociping.
 
-The full installation is named something like rwloadsim-Windows-x86\_64-bin-3.1.1.zip,
+The full installation is named something like rwloadsim-Windows-x86\_64-bin-3.1.2.zip,
 which you should unzip it into an empty directory.
 You subsequently need to set PATH to contain the expanded \\bin directory.
 
 If you only are interested in the generated execuables,
-the download is named something like generated-Windows-x86\_64-bin-3.1.1.zip,
+the download is named something like generated-Windows-x86\_64-bin-3.1.2.zip,
 which you can unzip to any directory you prefer.
 The exectables can be called directly from the directory or you can decide to include the directory in PATH.
 

diff --git a/docs/refman/ashdata.html b/docs/refman/ashdata.html
diff --git a/docs/refman/ashplot.html b/docs/refman/ashplot.html
diff --git a/docs/refman/atclause.html b/docs/refman/atclause.html
diff --git a/docs/refman/awrdump.html b/docs/refman/awrdump.html
diff --git a/docs/refman/awrreport.html b/docs/refman/awrreport.html
diff --git a/docs/refman/compoundstatement.html b/docs/refman/compoundstatement.html
diff --git a/docs/refman/concatenation.html b/docs/refman/concatenation.html
diff --git a/docs/refman/conditional.html b/docs/refman/conditional.html
diff --git a/docs/refman/connping.html b/docs/refman/connping.html
diff --git a/docs/refman/constant.html b/docs/refman/constant.html
diff --git a/docs/refman/controlloop.html b/docs/refman/controlloop.html
diff --git a/docs/refman/cqnthread.html b/docs/refman/cqnthread.html
diff --git a/docs/refman/cursor.html b/docs/refman/cursor.html
diff --git a/docs/refman/cursorloop.html b/docs/refman/cursorloop.html
diff --git a/docs/refman/databasedeclaration.html b/docs/refman/databasedeclaration.html
diff --git a/docs/refman/databasestatement.html b/docs/refman/databasestatement.html
diff --git a/docs/refman/declaration.html b/docs/refman/declaration.html
diff --git a/docs/refman/directive.html b/docs/refman/directive.html
diff --git a/docs/refman/directives.html b/docs/refman/directives.html
diff --git a/docs/refman/double.html b/docs/refman/double.html
diff --git a/docs/refman/executionblock.html b/docs/refman/executionblock.html
diff --git a/docs/refman/expression.html b/docs/refman/expression.html
diff --git a/docs/refman/file.html b/docs/refman/file.html
diff --git a/docs/refman/filecommands.html b/docs/refman/filecommands.html
diff --git a/docs/refman/filestatement.html b/docs/refman/filestatement.html
diff --git a/docs/refman/forloop.html b/docs/refman/forloop.html
diff --git a/docs/refman/fractiles.html b/docs/refman/fractiles.html