Hi

We use AS 2000 SP3. We pump data from a DB2 database and create MOLAP
cubes. When we create a partiton AS is creating an aggregation prefix
for it. The problem is when we process the cube it goes to the DB2
catalog to find the aggregation. Is the a way to tell AS not to go to
DB2 catalog for the aggregation ????


Thanks

What do you mean by this? What symptoms are you seeing?

--
Dean Adam
Magenic Technologies


"gag12" wrote:

Hi

When we process the cube AS is making a lot of reques to DB2. Here is
an exemple of one request.

SELECT TBCREATOR , TBNAME , NAME , COLTYPE , CASE COLTYPE WHEN 'BLOB'


THEN LENGTH2 WHEN 'CLOB' THEN LENGTH2 WHEN 'DBCLOB' THEN LENGTH2


WHEN 'ROWID' THEN LENGTH2 ELSE LENGTH END AS LENGTH , SCALE ,


NULLS , REMARKS , FOREIGNKEY , COLNO , DEFAULT , DEFAULTVALUE ,


TYPESCHEMA , TYPENAME


FROM "SYSIBM".SYSCOLUMNS


WHERE RTRIM ( TBCREATOR ) = 'DADD0' AND


TBNAME =


'Indemnisationbase_Indemnisationbase_1U'


ORDER BY TBCREATOR , TBNAME , COLNO


FOR FETCH ONLY

Indemnisationbase_Indemnisationbase_1U is the name you have in the
advanced panel of the partition wizard. I don't know why it goes to
DB2. And the RTRIM clause in the select causes a full table scan of the
system table.