Marcus,
 
    You might check the table ids on the temp table in both environments.  I have run into problems when importing cubes where it doesn't verify the table ids in the new environment and tries to use the table id from the table in the old environment.  This would cause similar errors to what you are receiving.  To correct this problem do the following:
 
1.    Login to you database (the following is for an Oracle database, you may need to make some minor modifications to make it work in SQL Server
2.    select table_,levTableId,LEVNAME,LEVELTYPE,DIMNAME from olaplev where upper(trim(table_))='CUBENAME'
 
    This will give you what table id your cube is expecting, if it is not correct do the following:
 
3.    update olaplev set levTableId=[Correct Table ID] where upper(trim(table_))='CubeName'
 
Good luck,
 
Rich
-----Original Message-----
From: Marcus Sudarmadji [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 17, 2004 9:23 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: [development-axapta] Export-Import OLAP development got problem

Hi,
I had problem with export-import OLAP self development.
I had created some OLAP on environment A. These OLAP were OK and results the report. I would like to install on environment 'production'. What I did was export-import the Cube Definition, Query and temporary table used by the OLAP.
I had created the database (and procedure to create OLAP) then export-import the Cube.
When I run 'transfer' from the Cube Definition, I got message as below
'Methode 'Process in COM object of Class '_Cube' return code 0x8004000F (unknown) which mean a table was detected in the scheme that is not joined to any other table'
 
Is there familiar with OLAP,  thanks,
 
SQL2000 and Analysis is SP3,  AXAPTA v3 SP1.
 
regards,
 
Marcus sudarmadji


Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online
Yahoo! Groups Sponsor
ADVERTISEMENT


Yahoo! Groups Links

Reply via email to