Important notes: NOTE 1: If you just get "command not found" when you run the script this means bash is not located in the right place. Do: locate bash and change the #!...bash line on the first line of the bash script. NOTE 2 : You have to have sqlplus set up before you run these scripts. Normally, setting up the cdf software in any release is enough. But we've had problems with running pl/sql scripts with some setups resulting in the following error: Input truncated to 1 characters ERROR: ORA-06550: line 1, column 29: PLS-00553: character set name is not recognized ORA-06550: line 0, column 0: PL/SQL: Compilation unit analysis terminated ======================================================================= This directory contains scripts for verifying the streams tests The scripts are well commented (mostly!) The idea is that you run this script on the database you ran the sim on, and it generates an output file. Then you re-run the same script on the database the streams output on and it should generate the same file. Here is what the output file contains: - Take a process_run from used_sets - Take all the jobsets associated with that run (1 for the simulation, >1 in real life) - Take all the cids associated with that jobset - Take all the tables associated with those cids (1 per cid) - print out the count(*) for this table - Take the first 10 (or less) rows associated with those cids for each table - Take the first two columns of each row - Print this out. (with interspersed table names and jobsets I guess.) ======================================================================================== There are 4 files in this directory: 1) check_sim_results.sql : This is the sql script which takes a process_run and dumps out information about it from the dbase. 2) run_check_sim_results.bash : This is the parent bash script which runs the sql script for each line of runfile 3) runfile : an example runfile for running with. 4) README : This text! So an example usage would be: ./run_check_sim_results.bash ./runfile '/@cdfonprd' The output is: total_check_compare.log Although the same stuff gets churned out to the screen.