Usage Note 38650: Out of memory, no documents were processed, no terms were generated, and processing error occurred messages appear
 |  |  |  |
When running a Text Miner node within SAS®Enterprise Miner, you might get an error dialog box:
ERROR: Processing error occurred.
The full error in the Text Miner node run log is:
NOTE: Reading variable number 1 as a body of text.
NOTE: The data set EMWS.TEXT2_OUT_T has 0 observations and 0 variables.
WARNING: Data set EMWS.TEXT2_OUT_T was not replaced be because new file is incomplete
ERROR: No documents were processed.
ERROR: No terms were generated.
ERROR: Abnormal Termination parsing the document collection.
ERROR: Out of memory
The following error might also appear:
ERROR: Docparse internal core error: Unable to allocate xxxxxx bytes.
The Text Miner node now requires more system memory than in previous releases. There is no formal recommendation for memory settings. However, if the above problem occurs, then you will need to increase your system memory settings.
If increasing the MEMSIZE option does not solve the problem, then you will need to increase the SAS system option MAXMEMQUERY. To set the MAXMEMQUERY option, refer to "SAS 9.2 Companion for UNIX Environments".
To prevent paging and the associated performance problems, use a MAXMEMQUERY and MEMSIZE system value that is smaller than the amount of real memory.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Text Miner | 64-bit Enabled AIX | 4.2 | 9.2 TS2M2 | ||
| 64-bit Enabled Solaris | 4.2 | 9.2 TS2M2 | ||||
| HP-UX IPF | 4.2 | 9.2 TS2M2 | ||||
| Linux for x64 | 4.2 | 9.2 TS2M2 | ||||
| Solaris for x64 | 4.2 | 9.2 TS2M2 | ||||
| Type: | Usage Note |
| Priority: | alert |
| Date Modified: | 2010-05-25 11:00:44 |
| Date Created: | 2010-02-08 12:39:33 |