Problem Note 14717: CPDBCOPY fails to copy views created in older PDBs
Using %CPDBCOPY in IT Resource Management 2.7 to copy a an older version
PDB into a SAS 9 PDB may fail with the following error messages:
ERROR: DATA Step View xxx.xxx could not be processed. There is no
source code stored with this view.
ERROR: File xxx.xxx.xxx has not been saved because copy could not be
completed.
Due to the variety and complexity of changes (generation/storage/usage)
that were made to views during the lifetime of Version 8 of the SAS
System, a specific release level that defines an "older PDB" has not
been determined.
To circumvent this problem, follow the steps below:
1. Make a backup of the CPDBCOPY member located in your
prefix.AUTOLIB library.
2. Locate the following source in CPDBCOPY:
PROC COPY IN=&cprefix.&level OUT=T&level
%if &cpfeng=6 and &cpteng=7 %then %do;
MEMTYPE=(CATALOG DATA ACCESS)
%end;
%else %do;
MEMTYPE=ALL
%end;
; RUN;
3. Change this code (above) to the following:
PROC COPY IN=&cprefix.&level OUT=T&level
MEMTYPE=(CATALOG DATA ACCESS)
; RUN;
A fix for this problem is being considered for a future software release.
Operating System and Release Information
SAS System | SAS IT Resource Management-Server | Microsoft Windows 2000 Server | 2.7 | | 9.1 TS1M3 SP4 | |
z/OS | 2.7 | 3.1 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Microsoft® Windows® for 64-Bit Itanium-based Systems | 2.7 | 3.1 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Microsoft Windows Server 2003 Datacenter 64-bit Edition | 2.7 | 3.1 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Microsoft Windows Server 2003 Enterprise 64-bit Edition | 2.7 | 3.1 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Microsoft Windows XP 64-bit Edition | 2.7 | 3.1 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Microsoft® Windows® for x64 | 2.7 | 3.1 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Microsoft Windows 2000 Advanced Server | 2.7 | | 9.1 TS1M3 SP4 | |
Microsoft Windows 2000 Datacenter Server | 2.7 | | 9.1 TS1M3 SP4 | |
Microsoft Windows 2000 Professional | 2.7 | | 9.1 TS1M3 SP4 | |
Microsoft Windows NT Workstation | 2.7 | | 9.1 TS1M3 SP4 | |
Microsoft Windows Server 2003 Datacenter Edition | 2.7 | 3.1 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Microsoft Windows Server 2003 Enterprise Edition | 2.7 | 3.1 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Microsoft Windows Server 2003 Standard Edition | 2.7 | 3.1 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Microsoft Windows XP Professional | 2.7 | 3.1 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Windows Vista | 2.7 | 3.1 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
64-bit Enabled AIX | 2.7 | 3.1 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
64-bit Enabled HP-UX | 2.7 | 3.1 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
64-bit Enabled Solaris | 2.7 | 3.1 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
HP-UX IPF | 2.7 | 3.1 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Linux | 2.7 | 3.1 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Tru64 UNIX | 2.7 | 3.1 | 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.
Type: | Problem Note |
Priority: | high |
Topic: | System Administration ==> Servers
|
Date Modified: | 2005-12-02 10:34:48 |
Date Created: | 2005-03-07 11:40:07 |