Showing posts with label ssas. Show all posts
Showing posts with label ssas. Show all posts

Thursday, March 22, 2012

can't add a new measure after the column is added in the DSV ?!?!

Just found one more nice error in SSAS :-)

If i add a column in my facttable, refresh the DSV and drag the new meassure into my meassuregroup i get an error when processing.

"Errors in the high-level relational engine. The data source view does not contain a definition for the 'MEA_BeregnetErhverv' column in the 'dbo_Fakt_Measures' table or view."

Well this is nice, since i just dragged it from that view :-)

Anyone got a workaround for this, except building the DSV and Cube structure from scrap each time ?

I've tried this exact scenario using Adventure Works sample database on a SQL Server AS 2005 SP1 box and it worked just fine, no errors. What version of the product are you using? Have you applied the latest service pack?

--Artur

|||

I've had this problem and after much trail fixed it by reviewing each of the Relationships in the Cube's Dimension Usage.

The problem turned out to be that one of the Measure Group Columns had a caps change since the last time I defined the relationship and AS couldn't match that column to the column in the Data Source View.

You couldn't see that it was invalid until you clicked on the dropdown list and the column name disappeared. (were as normally it would highlight the current selected column from the available columns).

can't add a new measure after the column is added in the DSV ?!?!

Just found one more nice error in SSAS :-)

If i add a column in my facttable, refresh the DSV and drag the new meassure into my meassuregroup i get an error when processing.

"Errors in the high-level relational engine. The data source view does not contain a definition for the 'MEA_BeregnetErhverv' column in the 'dbo_Fakt_Measures' table or view."

Well this is nice, since i just dragged it from that view :-)

Anyone got a workaround for this, except building the DSV and Cube structure from scrap each time ?

I've tried this exact scenario using Adventure Works sample database on a SQL Server AS 2005 SP1 box and it worked just fine, no errors. What version of the product are you using? Have you applied the latest service pack?

--Artur

|||

I've had this problem and after much trail fixed it by reviewing each of the Relationships in the Cube's Dimension Usage.

The problem turned out to be that one of the Measure Group Columns had a caps change since the last time I defined the relationship and AS couldn't match that column to the column in the Data Source View.

You couldn't see that it was invalid until you clicked on the dropdown list and the column name disappeared. (were as normally it would highlight the current selected column from the available columns).

Sunday, March 11, 2012

cannot use datasource column twice in ssas - IBMDB2

We develop ontop of IBMDB2 and cannot use a column twice in the model.

To work arround we have to add for every usage of the column and additional column with new name to an DB2 view and use the new column in the olap model - thats really annoying.

Does someone know a solution to solve this? because ontop of sql server you could use a column N times (for example for: name, key and some other attributes - in with DB2 we have to add 3 columns.) The Error Message we got is "Error in Backend Relational Model - OLEDB Reported unknown Status ' ' for column.".

Our System:

Analysis Services 2005 SP1 ENTERPRISE 64 Bit on Windows 2003 64 Bit connection with the IBMDADB2.1 64Bit OLEDB Provider from the IBM Client Version 8.2.4 to an IBM DB2 Database Version 8.2.4 running on LINUX 64 Bit.

Thanks for your help

HANNES

When do you get the error? Is it at processing time? You can see the query that Analysis Services sends to the Relational system and determine if the query is not formed correctly. This may give you clue to what is wrong.

Are you working around it in the DSV or in an actual DB2 view? An easier workaround would be to use the DSV and add the columns there.

David Botzenhart

|||

we get the error at processing time. see below for the full processing response. If we run the query at db2 directly its correct and working - so it must have something todo with anaylsis services or the oledb provider.

Mostly we work arround with the DB2 view..

This is the server processing state information

Thanks HANNES

====================

<Batch xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">
<Parallel>
<Process xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Object>
<DatabaseID>DWH_AT</DatabaseID>
<DimensionID>LU AGMT REQUEST SPEC</DimensionID>
</Object>
<Type>ProcessUpdate</Type>
<WriteBackTableCreation>UseExisting</WriteBackTableCreation>
</Process>
</Parallel>
</Batch>
Processing Dimension 'Agreement request profile' failed.
Start time: 30.11.2006 09:44:25; End time: 30.11.2006 09:45:21; Duration: 0:00:56
Processing Dimension Attribute '(All)' completed successfully.
Start time: 30.11.2006 09:44:25; End time: 30.11.2006 09:44:25; Duration: 0:00:00
Processing Dimension Attribute 'Longname' completed successfully. 573 rows have been read.
Start time: 30.11.2006 09:44:25; End time: 30.11.2006 09:45:21; Duration: 0:00:56
SQL queries 1
SELECT
DISTINCT
"PIPE01_LU_AGMT_REQUEST_SPEC"."NAME" AS "IPE01_LU_AGMT_REQUEST_SPEC0_0"
FROM "PIPE01"."LU_AGMT_REQUEST_PROFILE" AS "PIPE01_LU_AGMT_REQUEST_SPEC"
Processing Dimension Attribute 'Product group' completed successfully. 19 rows have been read.
Start time: 30.11.2006 09:44:25; End time: 30.11.2006 09:45:21; Duration: 0:00:56
SQL queries 1
SELECT
DISTINCT
"PIPE01_LU_AGMT_REQUEST_SPEC"."SPARTE" AS "IPE01_LU_AGMT_REQUEST_SPEC0_0"
FROM "PIPE01"."LU_AGMT_REQUEST_PROFILE" AS "PIPE01_LU_AGMT_REQUEST_SPEC"
Processing Dimension Attribute 'Asset category' completed successfully. 6 rows have been read.
Start time: 30.11.2006 09:44:25; End time: 30.11.2006 09:45:21; Duration: 0:00:56
SQL queries 1
SELECT
DISTINCT
"PIPE01_LU_AGMT_REQUEST_SPEC"."CODE_GROUP_VALUE" AS "IPE01_LU_AGMT_REQUEST_SPEC0_0"
FROM "PIPE01"."LU_AGMT_REQUEST_PROFILE" AS "PIPE01_LU_AGMT_REQUEST_SPEC"
Processing Dimension Attribute 'Request reason code' completed successfully. 1698 rows have been read.
Start time: 30.11.2006 09:45:21; End time: 30.11.2006 09:45:21; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
"PIPE01_LU_AGMT_REQUEST_SPEC"."EXTERNAL_REFERENCE" AS "IPE01_LU_AGMT_REQUEST_SPEC0_0","PIPE01_LU_AGMT_REQUEST_SPEC"."EXTERNE_DARSTELLUNG" AS "IPE01_LU_AGMT_REQUEST_SPEC0_1","PIPE01_LU_AGMT_REQUEST_SPEC"."NAME" AS "IPE01_LU_AGMT_REQUEST_SPEC0_2"
FROM "PIPE01"."LU_AGMT_REQUEST_PROFILE" AS "PIPE01_LU_AGMT_REQUEST_SPEC"
Processing Dimension Attribute 'Request reason' failed.
Start time: 30.11.2006 09:45:21; End time: 30.11.2006 09:45:21; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
"PIPE01_LU_AGMT_REQUEST_SPEC"."EXTERNAL_REFERENCE" AS "IPE01_LU_AGMT_REQUEST_SPEC0_0","PIPE01_LU_AGMT_REQUEST_SPEC"."EXTERNE_DARSTELLUNG" AS "IPE01_LU_AGMT_REQUEST_SPEC0_1","PIPE01_LU_AGMT_REQUEST_SPEC"."NAME" AS "IPE01_LU_AGMT_REQUEST_SPEC0_2","PIPE01_LU_AGMT_REQUEST_SPEC"."CODE_GROUP_VALUE" AS "IPE01_LU_AGMT_REQUEST_SPEC0_3","PIPE01_LU_AGMT_REQUEST_SPEC"."SPARTE" AS "IPE01_LU_AGMT_REQUEST_SPEC0_4"
FROM "PIPE01"."LU_AGMT_REQUEST_PROFILE" AS "PIPE01_LU_AGMT_REQUEST_SPEC"
Error Messages 1
Fehler im Back-End-Datenbankzugriffsmodul. OLE DB hat den unbekannten Status '' für die 1-Spalte gemeldet. Fehler im OLAP-Speichermodul: Fehler beim Verarbeiten des Request reason-Attributs der Agreement request profile-Dimension aus der DWH_AT-Datenbank.
Errors and Warnings from Response
Fehler im Back-End-Datenbankzugriffsmodul. OLE DB hat den unbekannten Status '' für die 1-Spalte gemeldet.
Fehler im OLAP-Speichermodul: Fehler beim Verarbeiten des Request reason-Attributs der Agreement request profile-Dimension aus der DWH_AT-Datenbank.
Fehler im OLAP-Speichermodul: Der Verarbeitungsvorgang wurde beendet, da die Anzahl von Fehlern, die w?hrend der Verarbeitung ermittelt wurden, die für den Vorgang maximal zul?ssige Anzahl von Fehlern erreicht hat.

|||

Hi Hannes,

I believe that developers in our area recently tested the DB2 v9.1 client driver (IBM OLE DB Provider for DB2, using IBM DB2 ODBC Driver version 9.01.00356), and it resolved this issue.

|||

We will test later on and I reply then

thanks Hannes

Friday, February 10, 2012

Cannot restore / Create Analysis Database

Hi everybody,

I've installed SSAS 2008.

When I try to create a new database or to restore a database, I've many errors :

Create Database :

Either the 'TLS\christophe.laporte' user does not have permission to create a new object in 'PC-LAPORTE', or the object does not exist.
(Microsoft.AnalysisServices)


Program Location:

at Microsoft.AnalysisServices.AnalysisServicesClient.SendExecuteAndReadResponse(ImpactDetailCollection impacts, Boolean expectEmptyResults, Boolean throwIfError)
at Microsoft.AnalysisServices.AnalysisServicesClient.Alter(IMajorObject obj, ObjectExpansion expansion, ImpactDetailCollection impact, Boolean allowCreate)
at Microsoft.AnalysisServices.Server.Update(IMajorObject obj, UpdateOptions options, UpdateMode mode, XmlaWarningCollection warnings, ImpactDetailCollection impactResult)
at Microsoft.AnalysisServices.Server.SendUpdate(IMajorObject obj, UpdateOptions options, UpdateMode mode, XmlaWarningCollection warnings, ImpactDetailCollection impactResult)
at Microsoft.AnalysisServices.MajorObject.Update(UpdateOptions options, UpdateMode mode, XmlaWarningCollection warnings)
at Microsoft.AnalysisServices.MajorObject.Update()
at Microsoft.AnalysisServices.ManagementDialogs.OlapCreateDB.SendDataToServer()

Restore Database when I click on browse button:

Database administrator or server administrator permissions are required to execute SystemGetLogicalDrives command. (Microsoft SQL Server code name "Katmai" Analysis Services)


Program Location:

at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Microsoft.AnalysisServices.AdomdClient.IExecuteProvider.ExecuteTabular(CommandBehavior behavior, ICommandContentProvider contentProvider, AdomdPropertyCollection commandProperties, IDataParameterCollection parameters)
at Microsoft.AnalysisServices.AdomdClient.AdomdCommand.ExecuteReader(CommandBehavior behavior)
at Microsoft.AnalysisServices.AdomdClient.AdomdCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet)
at Microsoft.AnalysisServices.Controls.FileSystemBrowser.Call(String function)
at

Any idea ?

I've installed Katmai on Vista. My account is in the administrators group on the computer. All services are started with a domain admin account ( and I'am too).

Maybe I've te setup katmai again ?

Thanks.

Christophe.

France.

Oups, sorry,

SSMS launched with administrator privileges is OK.

But why I get this error ? MMy account is administrator ...

And why SSMS don't query about privilege elevation when browsing for files or creating a database ?

Chrisstophe.

France.

|||

Chris,

I am not surprised that you have issues with SSAS on Vista PC. Actually on CTP download page Microsoft has a note regarding this:

The SQL Server 2008 June CTP has known compatibility issues with Windows Vista and Windows Server 2008 Beta. We do not recommend testing this CTP on this configuration. Instead, test this CTP on Windows Server 2003 Enterprise Edition with SP1 installed for 32-bit x86 and 64-bit x64 editions, and Windows XP Professional Edition with SP2 installed for 32-bit x86 and 64-bit x64 editions.

So I think you just will have to wait for future CTPs and see if they fixed issues on Vista.

Vidas Matelis

http://www.ssas2008-info.com