When using the BI Manager in the SAS® Management Console to import a SAS
package file that contains stored processes, if the package contains a
stored process that already exists in the metadata (and was created
in SAS 9.1.3 Service Pack 4) and this stored process contains
parameters, then the metadata might be destroyed for all stored processes
that contain parameters. This problem occurs in SAS 9.1.3 Service
Pack 4.
For example, suppose the SAS Package file (spk file) contains
a stored process called "test123" that contains a parameter
called "parm1". If this "test123" stored process already
exists in your metadata and was created in SAS 9.1.3 SP4, then
when you import the SAS Package file, the existing "test123" stored
process will be overwritten. In addition, the metadata will be destroyed
for all stored processes that contain parameters of the same type as
"parm1" (for example, String, Date, Float, Integer, Boolean, and so on). So, if
"parm1" has a type of "string", then the metadata will be destroyed
for all stored processes that contain a parameter of type "string".
The problem is most likely to occur if the same SAS package file is
imported two times. The second import will cause the existing stored
processes to be overwritten.
When an attempt is made to import a stored process that already exists
within a repository, the first step performed is that the existing
stored process definition, along with all its associated metadata
objects, gets deleted before the new version is imported.
In SAS 9.1.3 Service Pack 4, a change was made such that all parameters
share a single set of 9 global property-type objects in order to reduce
redundancy and conserve space within metadata.
The behavior documented in the first paragraph, in conjunction with the
change outlined above, means that all parameter definitions within the
Foundation repository that have property types in common with those
defined in the stored process that is being re-imported will be deleted!
If the reimport of the stored process occurs while working in a
repository other than Foundation, the user will receive the following
error because the code is unable to delete all the associated objects
that reside in Foundation, and the import will fail.
ERROR - Error importing metadata. Reason:
com.sas.iom.SASIOMDefs.GenericError: This transaction failed because it
attempts to implicitly update an associated object in repository
XXXXXXXX and this repository does not have a dependency defined to the
repository identified in the XML request.
Select the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| SAS System | SAS Management Console | OpenVMS Alpha | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| Microsoft Windows NT Workstation | 9.1 TS1M3 SP4 | |
| Microsoft Windows XP Professional | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| Microsoft Windows XP 64-bit Edition | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| Microsoft Windows Server 2003 Standard Edition | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| Microsoft Windows Server 2003 Datacenter Edition | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| Microsoft Windows Server 2003 Enterprise Edition | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| Microsoft Windows 2000 Professional | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| Microsoft Windows 2000 Server | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| Microsoft Windows 2000 Datacenter Server | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| Microsoft Windows 2000 Advanced Server | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| 64-bit Enabled Solaris | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| z/OS | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| 64-bit Enabled HP-UX | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| HP-UX IPF | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| Linux on Itanium | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| Linux | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| 64-bit Enabled AIX | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| Tru64 UNIX | 9.1 TS1M3 SP4 | 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.