Problem Note 7563: Restart of failed CPREDUCE results in lost data
In IT Service Vision, if CPREDUCE fails due to insufficient space for
the DAY summary level, and you rerun the CPREDUCE job after increasing
the space allocation for the DAY level, data is lost, and the following
note may be generated in the SAS Log:
NOTE: the REDUCE2 file in PDBWORK is not found
Although the job completes with a return code 0, the information in the
PDB is different than if they restore to before the failure and rerun.
Also, %CPREDUCE may fail to write observations to MONTH.tablenmP but
before having written new observations to MONTH.tablenmD if a timeout
occurs. The restart attempt appears to succeed but clears out all
observations from MONTH.tablenmD and MONTH.tablenmP, and fails to add
observations from staged data in PDBWORK .
The PDB will need to be restored and the CxPROCES and CPREDUCE jobs
rerun.
A Technical Support hot fix for SAS IT Service Vision Release 2.5 for
this issue is available at:
http://www.sas.com/techsup/download/hotfix/itsv25.html
Operating System and Release Information
| SAS System | SAS IT Resource Management-Server | Microsoft Windows NT Workstation | 2.5 | 2.6 | 8.2 TS2M0 | 8.2 TS2M0 |
| Microsoft Windows 95/98 | 2.4 | 2.6 | 8.2 TS2M0 | 8.2 TS2M0 |
| Microsoft Windows 2000 Server | 2.3 | 2.6 | 8 TS M0 | 8.2 TS2M0 |
| Microsoft Windows 2000 Professional | 2.3 | 2.6 | 8 TS M0 | 8.2 TS2M0 |
| Microsoft Windows 2000 Datacenter Server | 2.3 | 2.6 | 8 TS M0 | 8.2 TS2M0 |
| Microsoft Windows 2000 Advanced Server | 2.3 | 2.6 | 8 TS M0 | 8.2 TS2M0 |
| Solaris | 2.5 | 2.6 | 8.2 TS2M0 | 8.2 TS2M0 |
| 64-bit Enabled Solaris | 2.3 | 2.6 | 8 TS M0 | 8.2 TS2M0 |
| z/OS | 2.3 | 2.6 | 8 TS M0 | 8.2 TS2M0 |
| OS/2 | 2.3 | 2.6 | 8 TS M0 | 8.2 TS2M0 |
| HP-UX | 2.3 | 2.6 | 8 TS M0 | 8.2 TS2M0 |
| 64-bit Enabled HP-UX | 2.4 | 2.6 | 8.2 TS2M0 | 8.2 TS2M0 |
| 64-bit Enabled AIX | 2.3 | 2.6 | 8 TS M0 | 8.2 TS2M0 |
| Tru64 UNIX | 2.4 | 2.6 | 8.2 TS2M0 | 8.2 TS2M0 |
| AIX | 2.3 | 2.6 | 8 TS M0 | 8.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: | alert |
| Topic: | System Administration ==> Servers
|
| Date Modified: | 2003-09-08 12:36:54 |
| Date Created: | 2002-05-20 11:39:29 |