Problem Note 47947: %DI_MAINTAIN_JOB generates error: "ERROR: Indexed data set cannot be sorted in place unless the FORCE option is used"
The SAS® Size Profiling %DI_MAINTAIN_JOB might generate an error when you purge the PRF_GEO_PROD_STATUS_PARTIAL, PRF_SALES_FACT_PARTIAL, or PRF_GEO_PROD_STATUS_PARTIAL tables. The following error might be generated in the szpf_purge_table.log file:
ERROR: Indexed data set cannot be sorted in place unless the FORCE option is used.
NOTE: The SAS System stopped processing this step because of errors.
NOTE: PROCEDURE SORT used (Total process time):
real time 0.00 seconds
user cpu time 0.00 seconds
system cpu time 0.00 seconds
memory nk
OS Memory nk
Timestamp mm/dd/yyyy hh:mm:ss
Page Faults 0
Page Reclaims 0
Page Swaps 0
Voluntary Context Switches 0
Involuntary Context Switches 0
Block Input Operations 0
Block Output Operations 0
This issue occurs because the corresponding DI_DM.table_name_META table has an INDEX on PROD_HIER_SK. It should have a PRIMARY KEY constraint on PROD_HIER_SK. Use PROC CONTENTS to confirm that the DI_DM.table_name_META table has an INDEX but not a PRIMARY KEY constraint.
To work around this issue, perform the following steps:
- Drop the index on PROD_HIER_SK for the corresponding DI_DM.table_name_META table.
- Use PROC SQL to add CONSTRAINT PRIM_KEY PRIMARY KEY (PROD_HIER_SK) to DI_DM.table_name_META
- Run %DI_MAINTAIN_JOB for table_name. Even though no rows are purged, DI_DM.table_name_META is rebuilt.
Operating System and Release Information
| SAS System | SAS Size Profiling | 64-bit Enabled AIX | 3.2 | 4.2 | 9.3 TS1M1 | 9.3 TS1M2 |
| Microsoft® Windows® for x64 | 3.2 | 4.2 | 9.3 TS1M1 | 9.3 TS1M2 |
| Linux for x64 | 3.2 | 4.2 | 9.3 TS1M1 | 9.3 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.
| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2012-09-21 11:46:21 |
| Date Created: | 2012-09-20 16:11:49 |