In SAS® IT Resource Management, you might find that some files and directories are inadvertently deleted if they reside in a location where an IT data mart resides and you delete that data mart.
When you create an IT data mart, you must specify a default root path. The path is used in the creation of the physical libraries. This path is also used to form the default locations for any subsequent SAS libraries that are automatically created for the IT data mart.
For example, suppose during the creation of an IT data mart that you specify a root path that contains a directory named ClusterXYZ. In Microsoft Windows operating environments, that path is as follows:
C:\datamarts\ClusterXYZ
Upon creation of the IT data mart, an admin directory for miscellaneous content is created automatically under the ClusterXYZ directory.
C:\datamarts\ClusterXYZ\admin
In addition, if you use the Adapter Setup Wizard for this IT data mart, other SAS libraries are created, as shown in this example:
C:\datamarts\ClusterXYZ\staging
If you delete the data mart by selecting the Erase Data Mart action, both the metadata and all of the physical directories under the default root path are physically deleted. For example, in the scenario described above, suppose that the directory C:\datamarts\ClusterXYZ\documents already exists. In that case, that unrelated content and directory might also be deleted.
Note: This topic is relevant to any directory-based file system, including Windows and UNIX operating environments as well as the zFS file system in the z/OS operating environment. It is not relevant to the use and specification of traditional file-system paths under z/OS.
To avoid this problem (and as a best practice), do not create an IT data mart in a physical location where files or subdirectories exist that are unrelated to that IT data mart.
For more information about creating or erasing an IT data mart, see the section "Working with IT data marts" in the SAS® IT Resource Management: Administrator's Guide for your release.
Operating System and Release Information
SAS System | SAS IT Resource Management-Server | Microsoft Windows 8 Enterprise x64 | 3.4 | 3.5 | 9.4 TS1M2 | 9.4 TS1M2 |
Microsoft Windows 8 Pro 32-bit | 3.4 | 3.5 | 9.4 TS1M2 | 9.4 TS1M2 |
Microsoft Windows 8 Enterprise 32-bit | 3.4 | 3.5 | 9.4 TS1M2 | 9.4 TS1M2 |
z/OS | 3.4 | 3.5 | 9.4 TS1M2 | 9.4 TS1M2 |
Microsoft Windows 8 Pro x64 | 3.4 | 3.5 | 9.4 TS1M2 | 9.4 TS1M2 |
Microsoft Windows 8.1 Enterprise 32-bit | 3.4 | 3.5 | 9.4 TS1M2 | 9.4 TS1M2 |
Microsoft Windows 8.1 Enterprise x64 | 3.4 | 3.5 | 9.4 TS1M2 | 9.4 TS1M2 |
Microsoft Windows 8.1 Pro | 3.4 | 3.5 | 9.4 TS1M2 | 9.4 TS1M2 |
Microsoft Windows 8.1 Pro 32-bit | 3.4 | 3.5 | 9.4 TS1M2 | 9.4 TS1M2 |
Microsoft Windows Server 2012 Datacenter | 3.4 | 3.5 | 9.4 TS1M2 | 9.4 TS1M2 |
Microsoft Windows Server 2012 R2 Datacenter | 3.4 | 3.5 | 9.4 TS1M2 | 9.4 TS1M2 |
Microsoft Windows Server 2012 R2 Std | 3.4 | 3.5 | 9.4 TS1M2 | 9.4 TS1M2 |
Microsoft Windows Server 2012 Std | 3.4 | 3.5 | 9.4 TS1M2 | 9.4 TS1M2 |
Windows 7 Enterprise 32 bit | 3.4 | 3.5 | 9.4 TS1M2 | 9.4 TS1M2 |
Windows 7 Enterprise x64 | 3.4 | 3.5 | 9.4 TS1M2 | 9.4 TS1M2 |
Windows 7 Home Premium 32 bit | 3.4 | 3.5 | 9.4 TS1M2 | 9.4 TS1M2 |
Windows 7 Home Premium x64 | 3.4 | 3.5 | 9.4 TS1M2 | 9.4 TS1M2 |
Windows 7 Professional 32 bit | 3.4 | 3.5 | 9.4 TS1M2 | 9.4 TS1M2 |
Windows 7 Professional x64 | 3.4 | 3.5 | 9.4 TS1M2 | 9.4 TS1M2 |
Windows 7 Ultimate 32 bit | 3.4 | 3.5 | 9.4 TS1M2 | 9.4 TS1M2 |
Windows 7 Ultimate x64 | 3.4 | 3.5 | 9.4 TS1M2 | 9.4 TS1M2 |
64-bit Enabled AIX | 3.4 | 3.5 | 9.4 TS1M2 | 9.4 TS1M2 |
64-bit Enabled Solaris | 3.4 | 3.5 | 9.4 TS1M2 | 9.4 TS1M2 |
HP-UX IPF | 3.4 | 3.5 | 9.4 TS1M2 | 9.4 TS1M2 |
Linux for x64 | 3.4 | 3.5 | 9.4 TS1M2 | 9.4 TS1M2 |
Solaris for x64 | 3.4 | 3.5 | 9.4 TS1M2 | 9.4 TS1M2 |
*
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.