Re: monitorring number of records processed by AS
- From: "Jeje" <willgart@xxxxxxxxxxx>
- Date: Sun, 20 Aug 2006 12:13:02 -0400
you can verify how many rows has been really read if you have a count
measure in the cube.
execute an MDX query which return this measure and compare to the expected
rows. (and restart a new process)
another option is to create your own processing utility.
call the DSO objects to execute the process and intercept the processing
events.
1 of these event return the current number of rows read, keep this value
into a variable and when you'll receive the event which is "read step
finish" (I don't know what is this event exactly, but you'll found one event
which can do this job) compare the number rows read (your variable) to the
expected result.
if its not equal, then cancel the process (so you can cancel before the
server calculate the aggregations)
this option required more code compared to the first one.
but its strange to hear that the reading step stops without further errors.
How do you know that the connection break?
Have you take a look at the query executed by AS against your oracle
database and verify that this query return the right number of rows?
remember that AS do some inner joins, so the resulting number of rows can be
less then the real number of rows in the database.
So you expect 1 million of rows, but the result of the join can return only
0.5million of rows, so you think there is a problem, but in fact its a cube
design issue.
"Rea" <Rea@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7685B719-F7BC-4E52-8ECE-BBC1402C5682@xxxxxxxxxxxxxxxx
Hello eb
Is there a way to monitor, while partition is being processed or right
after
its process is complete, the number of source data records that had been
processed?
I need to know no late than process end, whether all records had been
returned
to AS from facts or just a partial select results..
From some reson,when select from facts breaks in the middle of cube's
process
, AS does not identify that as an error end finishes the process
successfully.
Data source is ORACLE.
Data provider is ORACLE PROVIDER for OLEDB.
AS 2K SP4.
Do you think changing data provider to Microsoft OLE DB provider for
Oracle
should help AS identify the problem in select results??
Thanks for your attention
Rea
.
- Follow-Ups:
- Prev by Date: Re: MDX statement
- Next by Date: Re: MDX statement
- Previous by thread: create local cube and ignore errors
- Next by thread: Re: monitorring number of records processed by AS
- Index(es):
Relevant Pages
|
