@@ -8,7 +8,7 @@ There are three types of binary distributions available at github releases:
8
8
9
9
### Using complete binaries
10
10
11
- Complete binaries distributed in a file such rwloadsim-linux-x86_64-bin-3.1.0 .tgz
11
+ Complete binaries distributed in a file such rwloadsim-linux-x86_64-bin-3.1.1 .tgz
12
12
can be used as is, i.e. without getting a clone or pull from github.
13
13
It should be used if you simply want a full run time environment
14
14
and it contains the following directories:
@@ -27,7 +27,7 @@ and it contains the following directories:
27
27
If you prefer to have access to source code, but avoid building the executables,
28
28
you can clone or pull from github (which would allow you to potentially compile
29
29
rwloadsim yourself), and then
30
- use a file like rwloadsim-linux-x86_64-binonly-3.1.0 .tgz.
30
+ use a file like rwloadsim-linux-x86_64-binonly-3.1.1 .tgz.
31
31
This file contains little more than the compiled binaries of the rwloadsim program,
32
32
and you can simply un-tar this file
33
33
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,
46
46
create a (possibly shared) directory where you simply
47
47
use a command like
48
48
```
49
- tar -zxvf rwloadsim-linux-x86_64-bin-3.1.0 .tgz
49
+ tar -zxvf rwloadsim-linux-x86_64-bin-3.1.1 .tgz
50
50
```
51
51
One install can be shared between several users as long as all have access to the directory.
52
52
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.
66
66
Start by doing a pull or clone of the sources from github
67
67
as if you would do your own compile, and then use a command like
68
68
```
69
- tar -zxvf rwloadsim-linux-x86_64-binonly-3.1.0 .tgz
69
+ tar -zxvf rwloadsim-linux-x86_64-binonly-3.1.1 .tgz
70
70
```
71
71
to extract little more than the compiled rwloadsim binaries into your already existing pull or clone.
72
72
@@ -182,7 +182,7 @@ as you will otherwise get ORA- errors during execution of the oltpworkload.
182
182
183
183
If you have an existing repository created earlier than version 3.0.6
184
184
and you are upgrading to a version
185
- 3.0.6 or later (including 3.1.0 ), you must execute the file rwl306.sql (which includes an
185
+ 3.0.6 or later (including 3.1.1 ), you must execute the file rwl306.sql (which includes an
186
186
update to the persec table) logged in using sqlplus to your primary
187
187
repository schema.
188
188
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
233
233
get these completely stand-alone.
234
234
This does _ not_ include the complete rwloadsim, and does _ not_ allow you
235
235
to create any rwl programs yourself.
236
- The file such as generated-linux-x86_64-bin-3.1.0 .tgz _ only_ contains binaries
236
+ The file such as generated-linux-x86_64-bin-3.1.1 .tgz _ only_ contains binaries
237
237
that you simply put into any directory, typically one in your PATH.
238
238
The only other requirement is an Oracle client environment as explained above.
239
239
0 commit comments