ERROR: Incorrect length in SAS Metadata Repository

[databobjr]

I used an oracle view as my drill thought table. It worked fine in my development server. But when I moved it to the production server, it gave me the following error when I tried to drill to the details:
"
The immediate MDX execution failed select * from ... ERROR: SQL passthru expression contained these errors: ERROR: Incorrect length in SAS Metadata Repository for column xxx.... ERROR: The following columns were not found in the contributing tables: xxx.The immediate MDX execution failedThe server encountered an error accessing a source data table.

"
I used olap cube 4.2 M2 and Metadata server 9200

the database is oracle 11g

Thanks,
Bob Message was edited by: databobjr

[AngelaHall]

Hi Bob,
This could be a problem with the install in Prod (example note: http://support.sas.com/kb/41/025.html).

However the workaround is the same, refresh the metadata in prod for the detail table.

~ Angela

[databobjr]

Thanks Angela!

I did use the management console to update the metadata.(right mouse click and select update metadata). But it still did not work. I also deleted and registered the table again. But it still did not work.

On thing I may need to point out, in development, we use a single server for all the SAS component. In production, we used multi servers. But I don't see this is a problem. Is there a log I can check for more details?

Thanks again,
Bob,

[AngelaHall]

Hi Bob,
Sorry for the delay. Were you able to get any further on this issue? Outside of the metadata server log, you might find some information in the workspace server log files. (\Lev1\SASApp\WorkspaceServer\Logs).

Also, are you able to connect to the table directly using PROC SQL Access to Oracle? http://support.sas.com/documentation/cdl/en/acreldb/63647/HTML/default/viewer.htm#rddptq.htm
http://support.sas.com/kb/41/616.html

If you can, can you then compare the properties of the table here with what was imported from Mgmt Console? There are some issues with pulling DBMS tables into Mgmt Console & this might be what is happening. Here is an example of one: http://support.sas.com/kb/37/118.html

~ Angela

[databobjr]

I just found other error information from the web studio log:

2011-02-21 17:52:09,483 [http-0.0.0.0-8180-7] ERROR [] com.sas.commands.olap.ShowDetailDataCommand - Drill through cannot be performed. No valid OLAP connection to get Show Detail results.Please contact your data administrator.
java.lang.IllegalStateException: Drill through cannot be performed. No valid OLAP connection to get Show Detail results.Please contact your data administrator.


What is a "valid OLAP connection"?

Thanks,
Bob.

[AngelaHall]

The source for the drill-through is Oracle, correct?

http://support.sas.com/kb/12/215.html
"Most connections to the data are performed using the OLAP Server's
process ID. The exception to this is a SAS/ACCESS library against a
third-party RDBMS when the USER option has been specified."


My guess with the error below is that the OLAP Server process id is trying to connect to Oracle and doesn't have access.

~ Angela