There are multiple reasons why you might not be able to view a SAS OLAP cube. This SAS note is a guide to diagnosing the cause of your particular problem. For example, review this note if you see the message "View Cube results are not available" in SAS OLAP Cube Studio 4.2 or later. Another common error is "Metadata error - The specified metadata repository or schema does not define any cubes."
Each section includes information on where to look and which items you should investigate.
Verify that the cube files exist in the directory specified by the PATH option in the PROC OLAP code or in the Cube Designer wizard in SAS OLAP Cube Studio.
Verify that the OLAP Server process ID has read and execute permission to the directory and the files that make up the cube by navigating to the directory specified by the PATH option in the PROC OLAP code or in the Cube Designer wizard in SAS OLAP Cube Studio. To do this, log into your operating system environment using the same account that you used to start the SAS OLAP Server.
Verify that the SAS Trusted User account is being used to connect from the SAS OLAP Server to the SAS® Metadata Server. The SAS OLAP Server log should have a line similar to the following at or near the beginning of a newly started server:
New out call client connection (1) from sastrust.
Verify that the SAS OLAP Server was started after the SAS Metadata Server had completed its own start-up routine.
Verify that there are no errors in either the OLAP server log or the metadata server log that indicate a problem.
Verify that the OLAP schema is assigned to the application server.
Note: This verification can also be done in SAS OLAP Cube Studio by right-clicking on the OLAP Schema in the metadata folder, selecting the Server Assignment tab and making certain that the schema is correctly associated with the application server.
Verify that the OLAP Schema is correctly associated to the application server. In some cases, the application server can lose its association to the SAS OLAP Schema even though the schema appears to be correctly assigned. In order to reassociate the schema to the application server, follow these steps:
Verify that the ID of the user who is attempting to view the cube has Read and ReadMetadata granted to the OLAP cube, and ReadMetadata granted to the application server and the OLAP Schema.
Verify that the Read and ReadMetadata permissions are not denied on any of the components that make up the cube. For example, a user can have problems viewing a cube if the user is denied ReadMetadata on the directory object.
Using either an interactive Base SAS® session or SAS® Enterprise Guide®, submit the following PROC SQL passthru to capture a more descriptive error. Replace the macro values in the code below with the correct information for your environment.
/* The machine name or IP address for the OLAP server */ %let host=server.domain.com; /* The port number for the OLAP server */ %let port=5451; /* A User ID with access to the cube */ %let user=sasdemo; /* The User's password */ %let pass=sasdemo1; /* The OLAP cube name */ %let cube=Example; proc sql; connect to olap (host="&host" port=&port user="&user" pass="&pass"); select * from connection to olap ( select [Measures].defaultmember on columns from [&cube] ); disconnect from olap; quit;
Errors that contain "Access Denied" or "User does not have privileges" typically indicate a problem at the operating system level.
Errors that the word "permission" usually indicate that the problem is due to metadata permissions.
If the error indicates that the repository or schema does not contain cubes, see the next section.
In SAS 9.1.3 Service Pack 3 and earlier, it is possible to create multiple schemas that have the same name. This will cause the OLAP server to lose the reference to the cube object. You can remove duplicate schemas in SAS OLAP Cube Studio if the schema is empty. To empty a schema, recreate the cubes in that schema using the Edit Cube Structure option in the context menu of the cube. Make sure to change the schema name before completing the wizard.
If the -METAREPOSITORY option has not been specified in the OLAP server's configuration, the server will be unable to locate the schema or cubes. The preferred location for this option is the sasv9.cfg file located in the home directory of the application server. For example, the directory might be Lev1\SASMain or Lev1\SASApp. The option can also be specified directly in the OLAP Server's configuration file or shell script if necessary.
Make sure that the -METASERVER option is pointing to the correct SAS Metadata Server.
|Product Family||Product||System||SAS Release|
|SAS System||SAS OLAP Server||Tru64 UNIX||9.1 TS1M0|
|64-bit Enabled AIX||9.1 TS1M0|
|OpenVMS Alpha||9.1 TS1M0|
|64-bit Enabled HP-UX||9.1 TS1M0|
|HP-UX IPF||9.1 TS1M0|
|64-bit Enabled Solaris||9.1 TS1M0|
|Microsoft Windows 2000 Advanced Server||9.1 TS1M0|
|Microsoft Windows 2000 Datacenter Server||9.1 TS1M0|
|Microsoft Windows 2000 Professional||9.1 TS1M0|
|Microsoft Windows 2000 Server||9.1 TS1M0|
|Microsoft Windows Server 2003 Datacenter Edition||9.1 TS1M0|
|Microsoft Windows Server 2003 Enterprise Edition||9.1 TS1M0|
|Microsoft Windows Server 2003 Standard Edition||9.1 TS1M0|
|Microsoft® Windows® for 64-Bit Itanium-based Systems||9.1 TS1M0|
|Microsoft Windows NT Workstation||9.1 TS1M0|
|Microsoft Windows XP Professional||9.1 TS1M0|
|Topic:||System Administration ==> Servers ==> OLAP|
Query and Reporting ==> OLAP (Online Analytical Processing)
|Date Modified:||2008-11-14 12:38:14|
|Date Created:||2006-09-01 12:07:10|