Small but important fixes to allow for further review and testing. (#25)

* TimesTen: Initial population

* Work in progress

* Finalising workshop instructions etc.

* QA fixes #1

* QA fixes #2

* Typo and grammar corrections

* URL fixup, additional minor tweaks.

* Minor updates and fixes.

* Improve connection instructions.

* cleanup migration

cleanup migration

* clean up after migration

clean up after migration

* Update to README file

* Various improvements based on feedback.

* URL corrections

* Correcting e-mail address for 'help'

* Tiny changes

* Urgent fixes from first round review

Co-authored-by: Kevin Lazarz <kevin.lazarz@oracle.com>

Author: ChrisJ60

timesten/cache-introduction/10-oltp-performance/oltp-performance.md

@@ -50,7 +50,7 @@ select directory_nb, last_calling_party, descr from vpn_users where vpn_id = :id
 
 The input values, *id* and *nb*, are randomly generated for each execution such that they fall within the range of the values in the table, so each execution of the statement retrieves a randomly chosen row.
 
-You will run the benchmark using the script **~/bin/runBenchmark**:
+You will run the benchmark using the script **/tt/livelab/bin/runBenchmark**:
 
 ```
 #!/bin/bash
@@ -149,7 +149,7 @@ Run the program against the Oracle database and note the results:
 
 ```
 <copy>
-~/bin/runBenchmark -oracle
+/tt/livelab/bin/runBenchmark -oracle
 </copy>
 ```
 
@@ -170,7 +170,7 @@ Run the program against the TimesTen cache and note the results:
 
 ```
 <copy>
-~/bin/runBenchmark -timesten
+/tt/livelab/bin/runBenchmark -timesten
 </copy>
 ```
 

timesten/cache-introduction/11-query-performance/query-performance.md

@@ -46,7 +46,9 @@ A much better way to time queries, with any database, is to use a program writte
 
 `usage: timeQueries { -oracle | -timesten } <filename>`
 
-where ‘filename’ is the name of a file containing the query text. The source code for the queryTimer utility is available in the main VM in the directory **~/lab/src**. Here is the timeQueries script:
+where ‘filename’ is the name of a file containing the query text. The source code for the queryTimer utility is available in the main VM in the directory **~/lab/src**. 
+
+Here is the **/tt/livelab/bin/timeQueries** script:
 
 ```
 #!/bin/bash
@@ -110,7 +112,7 @@ Examine the three queries that we will use for this exercise:
 
 ```
 <copy>
-cat ~/queries/query_1.sql
+cat /tt/livelab/queries/query_1.sql
 </copy>
 ```
 
@@ -133,7 +135,7 @@ ORDER BY 6;
 
 ```
 <copy>
-cat ~queries/query_2.sql
+cat /tt/livelab/queries/query_2.sql
 </copy>
 ```
 
@@ -160,7 +162,7 @@ SELECT
 
 ```
 <copy>
-cat ~queries/query_3.sql
+cat /tt/livelab/queries/query_3.sql
 </copy>
 ```
 
@@ -180,15 +182,15 @@ SELECT
  ORDER BY 1, 3 DESC;
 ```
 
-There is also a file, **queries/query_all.sql**, that contains all three queries.
+There is also a file, **/tt/livelab/queries/query_all.sql**, that contains all three queries.
 
 ## Task 3: Run the queries against the Oracle database
 
 First run the queries against the Oracle database:
 
 ```
 <copy>
-~/bin/timeQueries -oracle queries/query_all.sql
+/tt/livelab/bin/timeQueries -oracle queries/query_all.sql
 </copy>
 ```
 
@@ -265,7 +267,7 @@ Now run the queries against the TimesTen cache:
 
 ```
 <copy>
-~/bin/timeQueries -timesten queries/query_all.sql
+/tt/livelab/bin/timeQueries -timesten queries/query_all.sql
 </copy>
 ```
 

timesten/cache-introduction/12-dynamic-caching/dynamic-caching.md

@@ -114,7 +114,7 @@ This is because you do not need to perform an initial load for a dynamic cache g
 Check the state of the tables:
 
 ```
-<count>
+<copy>
 select count(*) from appuser.parent;
 </copy>
 ```