Hi,

I've done a vbs program that generates an as database
(using metadata scripter subroutines), where measures and
dimensions are created from metadata in a SQL table. No
errors when running the script, the database looks ok in
AM, and processes ok.

After several weeks I get an database processing error
that a member is in the fact table (optimized schema), but
not in the dimension table. BUT IT IS ! After having
deleted and regenerated the database (or saved it without
really changing anything) the errors disappears. I can't
repeat the error.

This has happened on two different servers (different
facttables and dimensions) after some time.

Questions:
Any idea, anyone?
When using DSO, is it easy to create instable or corrupt
databases, ie what you see in AM is not whats in the
repository?
Is there a control program to verify/repair an AS database
when having problems?

We use ASY2K and SP3.

/Jerome

Did you also process your dimensions before you process cubes?



Originally posted by Jerome

/Jerome


--
Posted via http://dbforums.com

Yes, I have seen this error. Atleast in my case it was
actually a "true" error message.

The way to fix this is to set the different components of
the cube/dimensions in the VB program, explicitly. What I
mean is: SourceTable, FromClause, Join conditions etc.

Hope this helps.

Sunil.

yes, both separately and as a part of db processing

/J

- How did you notice it was "true" ? The sql code when
processing ? For me, it was only one product among 1000
that was rejected, and it worked ok when I first generated
the cube.
- Any idea about a verify/repair program ?

/J

Not too sure, exactly when, its been a while. One of the
things that made my DSO module work was to initialize
the "structure" so to speak. Almost like going back to
programming fundamentals, initialize the values:
SourceTable, JoinClause, FromClause etc. This ensures that
none of these are wrongly allocated by the DSO module.

Hope this helps.

Sunil