Usage Note 39437: Directory might be retained after cube fails to build
When a cube build fails, the OLAP procedure attempts to remove the directories that it created. If the process fails in such a way that this is not possible, rebuilding the cube might cause a new directory to be created with a numeric suffix appended to the end of the directory name, for example:
PATH/CubeName
PATH/CubeName1
PATH/CubeName2
...
PATH/CubeNameN
If a cube build fails, before rebuilding the cube, you should use either operating system utilities or SAS programs to remove any directories created by the process. Taking this action will prevent the query process from trying to retrieve data from the original directory if it exists. Another side effect of the extra directories is that they could eventually use up the available disk space and result in insufficient disk space errors.
This problem is more likely to happen on a UNIX environment where the UNIX permissions do not allow the current user to delete the existing cube files that might have been created by a different user. You can consider using the UMASK feature to have each cube developer start the workspace server with the same permissions pattern. This should allow each cube developer the ability to delete the existing cube files, even if they were created by a different user. For more information on creating a UMASK definition in the workspace server, please refer to SAS Note 38040.
Another situation that can cause this issue is when a cube is imported to an environment in the same metadata folder using the same cube name. If you are importing a cube that already exists in a particular folder, you should use a PROC OLAP DELETE_PHYSICAL statement in order to remove the physcial files from the operating system before importing the cube. For information about the DELETE_PHYSICAL option, read the documentation for the PROC OLAP Statement
in the OLAP Server User's Guide.
Operating System and Release Information
| SAS System | SAS OLAP Server | z/OS | 9.2 TS2M0 | |
| Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.2 TS2M0 | |
| Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.2 TS2M0 | |
| Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.2 TS2M0 | |
| Microsoft Windows XP 64-bit Edition | 9.2 TS2M0 | |
| Microsoft® Windows® for x64 | 9.2 TS2M0 | |
| Microsoft Windows Server 2003 Datacenter Edition | 9.2 TS2M0 | |
| Microsoft Windows Server 2003 Enterprise Edition | 9.2 TS2M0 | |
| Microsoft Windows Server 2003 Standard Edition | 9.2 TS2M0 | |
| Microsoft Windows XP Professional | 9.2 TS2M0 | |
| Windows Vista | 9.2 TS2M0 | |
| 64-bit Enabled AIX | 9.2 TS2M0 | |
| 64-bit Enabled HP-UX | 9.2 TS2M0 | |
| 64-bit Enabled Solaris | 9.2 TS2M0 | |
| HP-UX IPF | 9.2 TS2M0 | |
| Linux | 9.2 TS2M0 | |
| Linux for x64 | 9.2 TS2M0 | |
| OpenVMS on HP Integrity | 9.2 TS2M0 | |
| Solaris for x64 | 9.2 TS2M0 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
| Type: | Usage Note |
| Priority: | |
| Topic: | Query and Reporting ==> OLAP (Online Analytical Processing)
|
| Date Modified: | 2010-06-28 15:25:58 |
| Date Created: | 2010-04-26 10:53:13 |