Conference orarep::nomahs::rdbexpert

	Hi Peter,

	Typically you will see Missing BLR statements when
	you start the Collection after a transaction was
	started. Then the program doesn't get the initial
	information and the transaction is missing the BLR.

	If you get a representative workload by gathering
	multiple collections you would capture the transactions
	at other times. Usually you get multiple occurances
	of the transactions so you would be missing only 
	that one instance of a transaction that happened
	to be in mid process in that collection. 

	It generally isn't anything to be concerned about.

	Check to see if you can find that transaction elsewhere
	in your workload. If you can't there is a possibility
	that there is another problem. Let me know if this is
	the case and we can work it further.

	Best regards,
	Sheri

    Thanks Sheri,
    
    I think thats explains the errors I got in the log file. But I think
    there must be some other problem to, because the operation in .0
    will stall or loop. This has happen with several collections (almost
    all)
    
    I think this could come from the usage of stored procedures, in note
    668 you said that stored procedures was not supported, how is it with
    Oracle Expert 3.1.
    
    (This customer knows they are using stored procedures)
    
    
    If you would like to have a try you can find them at:
    
    Directory KALLE::KALLE$DKA100:[PLINDGRE.KUNDER.TELIA]
    
    FENNA_DAG_1.DAT;1       6343  13-MAR-1997 19:51:09.00 
    (RWED,RWED,RWE,RWE)
    FENNA_DAG_10.DAT;1     26379  12-MAR-1997 20:07:31.00 
    (RWED,RWED,RWE,RWE)
    FENNA_DAG_11.DAT;1     26379  12-MAR-1997 20:07:37.00 
    (RWED,RWED,RWE,RWE)
    FENNA_DAG_12.DAT;1     26379  12-MAR-1997 20:07:45.00 
    (RWED,RWED,RWE,RWE)
    FENNA_DAG_2.DAT;1       6343  13-MAR-1997 19:51:20.00 
    (RWED,RWED,RWE,RWE)
    FENNA_DAG_3.DAT;1       6343  13-MAR-1997 19:51:32.00 
    (RWED,RWED,RWE,RWE)
    FENNA_DAG_4.DAT;1       6984  13-MAR-1997 19:51:46.00 
    (RWED,RWED,RWE,RWE)
    FENNA_DAG_5.DAT;1      26379  12-MAR-1997 20:06:47.00 
    (RWED,RWED,RWE,RWE)
    FENNA_DAG_6.DAT;1      55377  12-MAR-1997 20:06:59.00 
    (RWED,RWED,RWE,RWE)
    FENNA_DAG_7.DAT;1      26379  12-MAR-1997 20:07:08.00 
    (RWED,RWED,RWE,RWE)
    FENNA_DAG_8.DAT;1      16713  12-MAR-1997 20:07:17.00 
    (RWED,RWED,RWE,RWE)
    FENNA_DAG_9.DAT;1      45711  12-MAR-1997 20:07:24.00 
    (RWED,RWED,RWE,RWE)
    
     
    If Rdb expert dosen't support stored procedures how should you
    import a workload collected by trace from a database that uses
    stored procedures? Are all collections useles?
    
    
	Regards
    
    	Peter

	Hi Peter,

	I've sent you mail and will post an update here also.

	Stored Procedures are still not supported in the latest
	Expert. The next major release (which I am not sure of
	the schedule) should address this problem. That release
	will be a total rewrite of the product.

	Please send me your schema for your repository in the
	form of a SQL file so that I can do some testing.

	Can you specify one .DAT file that you know
	has the problem. I'll use it in my testing.

	What do you mean when you say that the operation stalls
	or loops? The processing of the requests will loop 
	from n to total number of requests until it reaches
	the end. If it is getting stuck during this loop then
	that typically indicates the processing does have a
	problem. With the number of requests that you were
	processing (15018 and 49819 it would tend to take a 
	very long time. If it stalls, is it reproducible at
	the same number everytime?

	Thanks,

	Sheri

    	Sheri
    
    
    >        Stored Procedures are still not supported in the latest
    >        Expert. 
    
    Does this mean that the whole collection is useless or just the
    processing done by stored procedures?
    
    >        Please send me your schema for your repository in the
    >        form of a SQL file so that I can do some testing.
    
    Files have been made available for copying:
    
    KALLE::USR:[PLINDGRE.KUNDER.TELIA]FENNA_DAG_5.RBR;1
    
    >        Can you specify one .DAT file that you know
    >        has the problem. I'll use it in my testing.
    
    KALLE::USR:[PLINDGRE.KUNDER.TELIA]FENNA_DAG_5.DAT;1
    
    >        What do you mean when you say that the operation stalls
    >        or loops? 
    
    The processing runs ok for some request when is suddenly
    stops, no more I/O just consuming CPU. This is repruduceable
    with the same file, it will always stop on the same request.
   
    I have tested this under Rdb 7.0-01 and 6.1-11
    
    Have found errors in the log created when processing the .DAT file
    with Rdb 6.1-11 
    
    KALLE>SEA FENNA_DAG_5.LOG_KEEP_THIS "-E-"
    
        %RDBX-E-PARSESYNTAX, found ';' at or near line 10
        %RDBX-E-PARSESYNTAX, found ';' at or near line 10
        %RDBX-E-PARSESYNTAX, found ';' at or near line 10
        %RDBX-E-PARSESYNTAX, found ';' at or near line 10
        %RDBX-E-PARSESYNTAX, found ';' at or near line 10
        %RDBX-E-PARSESYNTAX, found ';' at or near line 10
    
    It is available for copying at:
    
    KALLE::USR:[PLINDGRE.KUNDER.TELIA]FENNA_DAG_5.LOG_KEEP_THIS
    
    
    	Peter
                 

>        Stored Procedures are still not supported in the latest
    >        Expert. 
    
    Does this mean that the whole collection is useless or just the
    processing done by stored procedures?
    

>>  Some stored procedures may process fine, depending on what they
>>  are doing.  The problem is that we don't currently support all 
>>  the BLR available via a stored procedure, and when we hit something
>>  we don't recognize, we throw out the whole procedure.

>>  The problem described earlier was caused by a stored procedure
>>  and some new BLR in it sending our BLR decoder into a loop.
>>  I have a new image which will correct the problem.  Please contact
>>  Sheri if you run into this and need the new image.
>>
>>  thanks,
>>  todd