Error message
"Failure in allocating information storage area." |
Applicable versions and levels
Windows versions: V5.0L10 or later
Solaris versions: 5.0 or later
Linux versions: 5.2, V10.0L10 or later
Linux for Itanium versions: V12.0L10 or later
HP-UX versions: 5.1 or later
AIX versions: 5.1 or later
DS versions: V20L10
Action
Cause
The Systemwalker Operation Manager client receives the data that was sent from the Systemwalker Operation Manager server in the dynamically obtained memory when displaying the job properties. This problem may occur at this time, because the dynamic memory could not be obtained from the system.
The Systemwalker Operation Manager server creates the data to be sent to the Systemwalker Operation Manager client based on the files that store the output content from the jobs shown below. This file size is always extremely large, therefore the amount of data that is sent to the Systemwalker Operation Manager client may be large, which may cause the memory of the Systemwalker Operation Manager client that receives it to be depleted.
[Windows versions]
<Jobscheduler database directory>\<project name>_<job net name>_<nnn>.log (nnn is a 3-digit integer) (*1)
*1: In V13.3.0 or later, this is <project name>_<job net name>_<cccccccccccccccc>.log (cccccccccccccccc can be any character)
[UNIX versions]
<jobscheduler database directory>/<project name>_<job net name>.log (*1)
*1: In V13.3.0 or later, this is <project name>_<job net name>_<nn>.log (nn can be any number)
The Jobscheduler database directory can be checked on the Database tab in the Define Jobscheduler Startup Parameters window, displayed when Startup parameter is clicked in the Systemwalker Operation Manager Environment Setup window.
Action method
Delete the above file that stores the output content from the applicable job.
Then, on the Standard information tab in the Monitor - Job window, select the Do not save standard/error output check box, or review the output content of the job, and consider an operation that reduces the output amount.
If all output content is required, ensuring that the job properties window is not used, use a text editor, for example, to back up the file that stores the output content from the above job directly, so that this file can be referenced.
