SLOB can be obtained at this link: Click here.
This post is just a simple set of screenshots I recently took during a fresh SLOB deployment. There have been a tremendous number of SLOB downloads lately so I thought this might be a helpful addition to go along with the documentation. The examples I show herein are based on a 220.127.116.11 Oracle Database but these principles apply equally to 18.104.22.168 and all Oracle Database 11g releases as well.
- Create a tablespace for SLOB.
- Run setup.sh
- Verify user schemas
- Execute runit.sh. An Example Of Wait Kit Failure and Remedy
- Execute runit.sh Successfully
- Using SLOB With SQL*Net
- Test SQL*Net Configuration
- Execute runit.sh With SQL*Net
- More About Testing Non-Linux Platforms
Create a Tablespace for SLOB
If you already have a tablespace to load SLOB schemas into please see the next step in the sequence.
Provided database connectivity works with ‘/ as sysdba’ this step is quite simple. All you have to do is tell setup.sh which tablespace to use and how many SLOB users (schemas) load. The slob.conf file tells setup.sh how much data to load. This example is 16 SLOB schemas each with 10,000 8K blocks of data. One thing to be careful of is the slob.conf->LOAD_PARALLEL_DEGREE parameter. The name is not exactly perfect since this actually controls concurrent degree of SLOB schema creation/loading. Underneath the concurrency may be parallelism (Oracle Parallel Query) so consider setting this to a rather low value so as to not flood the system until you’ve practiced with setup.sh for a while.
Verify Users’ Schemas
After taking a quick look at cr_tab_and_load.out, as per setup.sh instruction, feel free to count the number of schemas. Remember, there is a “zero” user so setup.sh with 16 will have 17 SLOB schema users.
Execute runit.sh. An Example Of Wait Kit Failure and Remedy
This is an example of what happens if one misses the detail to create the semaphore wait kit as per the documentation. Not to worry, simply do what the output of runit.sh directs you to do. Note, while runit.sh supports just a single argument as shown here, SLOB 2.3 and beyond have additional options to support Multiple Schema Model. Please see the documentation for more information on recently added options to runit.sh.
Execute runit.sh Successfully
The following is an example of a healthy runit.sh test.
Using SLOB with SQL Net
Strictly speaking this is all optional if all you intend to do is test SLOB on your current host. However, if SLOB has been configured in a Windows, AIX, or Solaris box this is how one tests SLOB. Testing these non-Linux platforms merely requires a small Linux box (e.g., a laptop or a VM running on the system you intend to test!) and SQL*Net.
Test SQL*Net Configuration
We don’t care where the SLOB database service is. If you can reach it successfully with tnsping you are mostly there.
Execute runit.sh With SQL*Net
The following is an example of a successful runit.sh test over SQL*Net.
More About Testing Non-Linux Platforms
Please note, loading SLOB over SQL*Net has the same configuration requirements as what I’ve shown for data loading (i.e., running setup.sh). Consider the following screenshot which shows an example of loading SLOB via SQL*Net.
Finally, please see the next screenshot which shows the slob.conf file the corresponds to the proof of loading SLOB via SQL*Net.
This short post shows the simple steps needed to deploy SLOB in both the simple Linux host-only scenario as well as via SQL*Net. Once a SLOB user gains the skills needed to load and use SLOB via SQL*Net there are no barriers to testing SLOB databases running on any platform to include Windows, AIX and Solaris.