Conference orarep::nomahs::dectrace_v20

    
    What ever happened to this?  

	Hi,

	Sorry that I had to rush out Friday when you called.

	This is the error that this customer was seeing:

   Error: The DECTrace database <filename> is not a valid RDB collection.
           The following tables were not found :

           EPC$1_221_REQUEST_BLR
  
	What version of Rdb, Trace, and Expert is the customer running?

	This problem had to do with the customers selection
	being defined as using a CLASS other than ALL or 
	RDBEXPERT.

        When DECTrace sets up the repostitory that it uses to capture the
        data from the Collection it creates the Tables based upon what the
        customer has defined. If something in the customers
        definition is not set up properly the table will not be
        created during the collection.
 
	Have the customer send a log (set host 0 )of what they are 
	seeing and the exact error along with the information on
	their collection, selection, facility definitions, etc.

	Some information that is helpful in determining the problem
	would be to have the customer provide the following information:

	SHOW COLLECTION:
	Look and see what Selection that they are using.

	SHOW SELECTION:

	 DECtrace> show selection customer_selection_name  

   Selection Name        Facility         Version     Class
   --------------------  ---------------  ----------  --------------------
   customer_selection_name  RDBVMS           V6.0-04     PERFORMANCE

     If the customers CLASS is not ALL or RDBEXPERT, have them add a qualifier 
     to their selection definition to make the class be ALL.

	SHOW DEFINITION:

               $ COLLECT SHOW DEFINITION RDBVMS/VERSION = "V6.0-04"
 
       They would need to use a statement such as follows to create a Facility
        selection to include any other products or their application for
        which they want to collect:

                $ COLLECT CREATE SELECTION SELECTION_1 -
                _$ OPTIONS

                Option> FACILITY RDBVMS /VERSION = "V6.0-04" /CLASS = ALL
                Option> FACILITY there_application_name /VERSION = "Vxxxx"
                Option> ctrl z

	Be sure to verify that they have the correct facility file for 
	the version of RDB that they are running. 

	After the customer verifies everything, if they need to redefine the 
	SELECTION, first have them delete the previous one,
	$COLLECT DELETE SELECTION selection_name. Then they need to rerun 
	the collection and then reformat the .DAT file:

        Then they would need to reschedule and run their collection:

        $ COLLECT SCHEDULE COLLECTION customer_selection_file -
        _$ output_name.DAT -
        -$ /DURATION = :30
        _$ /COLLECTION_FILES = (PROTECTION = (W:RW)
        ...

        Then he needs to REFORMAT his .DAT file to an .RDB file and
        Import the workload to his Expert repository.
 

	Hope that this information is helpful to track down this problem.

	Let me know what you find and I'll help track this down.

	Sheri

    
    Thank you Sheri...
    
    Your last utterance about the RDBex... class:-) on Friday was the fix.  
    I had the CT add the RDBEXPERT class to the selection and this worked.
    CT is on 2.2, rdb6.0 (will be upgrading to 7 soon).
    
    CT had been using ALL and/or PERFORMANCE only.