1008001 to 1008152: System Call Messages

Table 5 lists error and informational messages about system calls.

Table 5. System Call Messages 1008001 to 1008152

Message Number Message Possible Cause Possible Solution

1008001

Unable to Allocate Memory

Essbase cannot allocate enough memory to perform the operation.

Ensure that the virtual memory is two to three times as large as the physical memory.

Ensure that the swap space is two to three times as large as the RAM.

Check the block size of the database. If necessary, reduce the block size.

Check the data cache setting. If necessary, increase the data cache size.

Check the index cache setting. If necessary, increase the index cache size.

If you are on a UNIX computer, check the user limit profile (see Checking the User Limit Profile).

Determine whether the security file is corrupt.

If the server computer is running the HP-UX operating system, increase MAXDSIZE to at least 2 * (data cache size + index cache size).

Determine whether any databases are corrupt (see Checking for Database Corruption).

Restart the server computer.

Ensure that you have enough RAM.

1008006

Unable to Free Memory for memoryToBeFreed in funtionName

 

Contact Oracle Support.

1008009

Pointer is NULL - Free Canceled: variableName in functionName

Essbase cannot free the listed memory.

Contact Oracle Support.

1008010

Read Failed

Essbase cannot read a calculation script located on the client.

  1. Run the calculation script again.

  2. Restart the client and rerun the calculation script.

  3. Copy the calculation script to the server and rerun the calculation script.

1008021

Named Pipe Create Failed

Essbase cannot create the named pipe.

Consult the networking documentation.

1008022

Pipe Create Failed

Essbase cannot create the named pipe.

Consult the networking documentation.

1008023

Named Pipe Connect Failed

Essbase cannot disconnect from the named pipe.

Consult the networking documentation.

1008024

Named Pipe Disconnect Failed

Essbase cannot disconnect from the named pipe.

Consult the networking documentation.

1008025

Named Pipe Peek Failed

Essbase cannot peek to the named pipe.

Consult the networking documentation.

1008028

Pipe Read Error

Essbase cannot read from the named pipe.

Determine whether Essbase Server is running.

  • If Essbase Server is not running, restart Essbase Server.

  • If Essbase Server crashed, follow the procedures for an abnormal shutdown.

  • If Essbase Server has frozen, stop Essbase Server and follow the procedures for an abnormal shutdown. If you cannot stop Essbase Server using the standard methods, end the task (see Ending the Server Task).

1008029

Pipe Write Error

Essbase cannot write to the named pipe.

Consult the networking documentation.

1008030

Pipe Open Failed

Essbase cannot open the named pipe.

Consult the networking documentation.

1008031

Pipe Close Failed

Essbase cannot close the named pipe.

Consult the networking documentation.

1008036

Incorrect # of Bytes Written To Pipe

Essbase cannot finish writing to the named pipe.

Consult the networking documentation.

1008037

Find Next Failed

Essbase cannot find the next file in the sequence.

This might occur if Essbase is processing multiple files, such as during a copy or a load. If you can determine which file is missing, restore it from backups.

1008039

Find Close Failed

Essbase cannot close the next file in the sequence.

This might occur if Essbase is processing multiple files, such as during a copy or a load. If you can determine which file is having problems, restore it from backups.

1008089

Error receiving data from Agent

Essbase cannot receive data from the Agent.

Determine whether Essbase Server is running.

  • If Essbase Server is not running, restart Essbase Server.

  • If Essbase Server crashed, follow the procedures for an abnormal shutdown.

  • If Essbase Server has frozen, stop Essbase Server and follow the procedures for an abnormal shutdown. If you cannot stop Essbase Server using the standard methods, end the task (see Ending the Server Task), and restart Essbase Server.

1008090

Timed out receiving data from Agent

Essbase cannot receive data from the Agent.

Determine whether Essbase Server is running.

  • If Essbase Server is not running, restart Essbase Server.

  • If Essbase Server crashed, follow the procedures for an abnormal shutdown.

  • If Essbase Server has frozen, stop Essbase Server and follow the procedures for an abnormal shutdown. If you cannot stop Essbase Server using the standard methods, end the task (see Ending the Server Task), and restart Essbase Server.

1008091

Error sending data to Agent

Essbase cannot send data to the Agent.

Contact Oracle Support.

1008092

Timed out sending data to Agent

Essbase cannot send data to the Agent.

Contact Oracle Support.

1008093

Invalid data type for conversion

 

Contact Oracle Support.

1008099

HALLOC: Possible duplicate memory allocation! variableName in functionName

 

Contact Oracle Support.

1008100

HFREE: Pointer already freed! variableName in functionName

 

Contact Oracle Support.

1008101

HFREE: Likely memory overwrite! variableName in functionName

The original memory allocation was overwritten by a newer allocation to the same pointer.

Contact Oracle Support.

1008106

Exception error log errorLogName.XCP is being created

Essbase is generating an exception log just before it shuts down abnormally.

Search the exception log for information about what caused the shut down.

  • If the server crashes, the log is written to HYPERION_HOME/logs/essbase; for example, log00001.xcp.

  • If the application crashes and the application name is unknown, the log is written to HYPERION_HOME/logs/essbase/app; for example, log00001.xcp.

  • If the application crashes and the application name is known, the log is written to HYPERION_HOME/logs/essbase/app/appName; for example, sample/log00001.xcp.

  • If the database crashes and the database name is unknown, the log is written to HYPERION_HOME/logs/essbase/app/appName/; for example, app/sample/log00001.xcp.

  • If the database crashes and the database name is known, the log is written to HYPERION_HOME/logs/essbase/app/appName/databasename; for example, app/sample/basic/log00001.xcp.

Determine whether the database is corrupt (see Checking for Database Corruption).

Contact Oracle Support.

1008107

Exception error log completed -- please contact technical support and provide them with this file

Essbase finished generating the error log and shuts down.

Search the exception log for information about what caused the shut down.

  • If the server crashes, the log is written to HYPERION_HOME/logs/essbase; for example, log00001.xcp.

  • If the application crashes and the application name is unknown, the log is written to HYPERION_HOME/logs/essbase/app/; for example, app/log00001.xcp.

  • If the application crashes and the application name is known, the log is written to HYPERION_HOME/logs/essbase/app/appName/; for example, app/sample/log00001.xcp.

  • If the database crashes and the database name is unknown, the log is written to HYPERION_HOME/logs/essbase/app/appName/; for example, app/sample/log00001.xcp.

  • If the database crashes and the database name is known, the log is written to HYPERION_HOME/logs/essbase/app/appName/databasename; for example, app/sample/basic/log00001.xcp.

Determine whether the database is corrupt (see Checking for Database Corruption).

Contact Oracle Support.

1008108

Essbase Internal Logic Error logicErrorNumber

Essbase encountered a logic error and shut down abnormally.

Ensure that Essbase Server is running.

  • If Essbase Server is not running, restart Essbase Server.

  • If Essbase Server crashed, follow the procedures for an abnormal shutdown.

  • If Essbase Server has frozen, stop Essbase Server and follow the procedures for an abnormal shutdown. If you cannot stop Essbase Server using the standard methods, end the task (see Ending the Server Task).

Determine whether the database is corrupt (see Checking for Database Corruption).

Ensure that the networking and computer hardware are running correctly.

Ensure that the virtual memory is two to three times as large as the physical memory. If that is still not large enough, increase the memory of the server computer.

Check the block size.

Ensure that the data cache can hold at least 100 blocks.

Ensure that the index cache size is within the recommended range.

1008109

Unable to Reallocate Memory for pointerName in functionName

Essbase cannot reallocate memory to the listed function.

Ensure that you have enough memory.

1008110

Unable to Allocate Memory. Refer to the Application Log for details.

Essbase cannot allocate memory.

Ensure that the Essbase computer has enough resources. Consult the Oracle Hyperion Enterprise Performance Management System Installation Start Here for system requirements. If a resource-intensive application, such as a relational database, is running on the same computer, the resource-intensive application may be using the resources that Essbase needs.

Ensure that you have enough memory.

Do not close the Essbase Server window by clicking the "X" in the title bar.

After you restart Essbase Server, determine whether the database is corrupt (see Checking for Database Corruption).

See appName.log.

1008111

Unable to Reallocate Memory for pointerName in functionName. Refer to the Application Log for details.

Essbase cannot reallocate memory.

Ensure that the Essbase computer has enough resources. Consult the Oracle Hyperion Enterprise Performance Management System Installation Start Here for system requirements. If a resource-intensive application, such as a relational database, is running on the same computer, the resource-intensive application may be using the resources that Essbase needs.

Ensure that you have enough memory.

Do not close the Essbase Server window by clicking the "X" in the title bar.

After you restart Essbase Server, determine whether the database is corrupt (see Checking for Database Corruption).

See appName.log.

1008112

Memory Allocation error codes: O/S error = errorCode, O/S return code = errorNumber

Essbase could not allocate memory.

Ensure that you have enough memory.

Look up the operating system error code and the operating system return code in the operating system documentation.

1008113

Memory Reallocation error codes: O/S error = errorCode, O/S return code = errorNumber

Essbase could not reallocate memory.

Ensure that you have enough memory.

Look up the operating system error code and the operating system return code in the operating system documentation.

1008114

Allocation request for number bytes of virtual memory. Percentage of memory in use is number %.

Bytes of virtual memory requested and the percentage of virtual memory currently being used by Essbase.

Not applicable

1008115

Total physical memory is number bytes. Available physical memory is number bytes.

Total bytes of physical memory and bytes of available physical memory.

Not applicable

1008116

Total swap space is number bytes. Available swap space is number bytes.

Total bytes of swap space and bytes of available swap space.

Not applicable

1008117

Total virtual memory is number bytes. Available virtual memory is number bytes.

Total bytes of virtual memory and bytes of available virtual memory.

Not applicable

1008118

Memory page size is number bytes. Allocation granularity is number bytes.

Total bytes of memory page size and the size that memory is allocated in.

Not applicable

1008119

Memory page size is number bytes

Total bytes of memory page size.

Not applicable

1008120

Unable to Allocate Physical Memory for pointerName in functionName

Essbase cannot allocate physical memory to the listed function.

Ensure that you have enough physical memory.

1008121

Unable to Allocate Physical Memory for pointerName in functionName for reallocation

Essbase cannot reallocate physical memory to the listed function.

Ensure that you have enough physical memory.

1008122

Unable to Lock the Allocated Memory for pointerName in functionName

Essbase cannot lock the needed memory.

Ensure that the Agent is assigned the correct operating system privileges (see Determining Operating System Privileges).

Ensure that the Essbase computer has enough resources. Consult the Oracle Hyperion Enterprise Performance Management System Installation Start Here for system requirements. If a resource-intensive application, such as a relational database, is running on the same computer, the resource-intensive application may be using the resources that Essbase needs.

Ensure that the memory to be locked is valid. Consult the operating system documentation.

1008123

Unable to Lock the Allocated Memory for pointerName in functionName for reallocation

Essbase cannot lock the needed memory.

Ensure that the Agent is assigned the correct operating system privileges (see Determining Operating System Privileges).

Ensure that the Essbase computer has enough resources. Consult the Oracle Hyperion Enterprise Performance Management System Installation Start Here for system requirements. If a resource-intensive application, such as a relational database, is running on the same computer, the resource-intensive application may be using the resources that Essbase needs.

Ensure that the memory to be locked is valid. See the operating system documentation.

1008124

Unable to Lock the Allocated Memory pointerName in functionName, because of insufficient quota

Essbase does not have enough physical memory to lock the memory.

Check the Essbase Server memory requirements. If necessary, increase the physical memory.

1008125

Unable to Lock the Allocated Memory pointerName in functionName, because of insufficient privilege

Essbase is not assigned the correct operating system privileges to lock the memory.

Ensure that the Agent is assigned the correct operating system privileges (see Determining Operating System Privileges).

1008126

Unable to Lock the Allocated Memory pointerName in functionName for reallocation, because of insufficient quota

Essbase does not have enough physical memory to lock the memory.

Check the Essbase Server memory requirements. If necessary, increase the physical memory.

1008127

Unable to Lock the Allocated Memory pointerName in functionName for reallocation, because of insufficient privilege

Essbase is not assigned the correct operating system privileges to lock the memory.

Ensure that the Agent is assigned the correct operating system privileges (see Determining Operating System Privileges).

1008128

Unable to Allocate Physical Memory for pointerName in functionName. Refer to the Application Log for details.

Essbase does not have enough physical memory to lock the memory.

If necessary, decrease the cache sizes.

Ensure that the Essbase computer has enough resources. Consult the Oracle Hyperion Enterprise Performance Management System Installation Start Here for system requirements. If a resource-intensive application, such as a relational database, is running on the same computer, the resource-intensive application may be using the resources that Essbase needs.

Restart the server computer.

Check the Essbase Server physical memory requirements. If necessary, increase the physical memory.

See appName.log.

1008129

Unable to Allocate Physical Memory for pointerName in functionName for reallocation. Refer to the Application Log for details.

Essbase does not have enough physical memory to lock the memory.

If necessary, decrease the cache sizes.

Ensure that the Essbase computer has enough resources. Consult the Oracle Hyperion Enterprise Performance Management System Installation Start Here for system requirements. If a resource-intensive application, such as a relational database, is running on the same computer, the resource-intensive application may be using the resources that Essbase needs.

Restart the server computer.

Check the Essbase Server physical memory requirements. If necessary, increase the physical memory.

See appName.log.

1008130

Unable to Lock the Allocated Memory for pointerName. Refer to the Application Log for details.

Essbase cannot lock the needed memory.

Ensure that the Agent is assigned the correct operating system privileges (see Determining Operating System Privileges).

Ensure that the Essbase computer has enough resources. Consult the Oracle Hyperion Enterprise Performance Management System Installation Start Here for system requirements. If a resource-intensive application, such as a relational database, is running on the same computer, the resource-intensive application may be using the resources that Essbase needs.

Ensure that the memory to be locked is valid.

See appName.log.

1008131

Unable to Lock the Allocated Memory for pointerName in functionName for reallocation. Refer to the Application Log for details.

Essbase cannot lock the needed memory.

Ensure that the Agent is assigned the correct operating system privileges (see Determining Operating System Privileges).

Ensure that the Essbase computer has enough resources. Consult the Oracle Hyperion Enterprise Performance Management System Installation Start Here for system requirements. If a resource-intensive application, such as a relational database, is running on the same computer, the resource-intensive application may be using the resources that Essbase needs.

Ensure that the memory to be locked is valid.

See appName.log.

1008132

Unable to Lock the Allocated Memory pointerName in functionName, because of insufficient quota. Refer to the Application Log for details.

Essbase does not have enough physical memory to lock the memory.

Check the Essbase Server memory requirements. If necessary, increase the physical memory.

See appName.log.

1008133

Unable to Lock the Allocated Memory pointerName in functionName, because of insufficient privilege. Refer to the Application Log for details.

Essbase is not assigned the correct operating system privileges to lock the needed memory.

Ensure that the Agent is assigned the correct operating system privileges (see Determining Operating System Privileges).

Ensure that the Essbase computer has enough resources. Consult the Oracle Hyperion Enterprise Performance Management System Installation Start Here for system requirements. If a resource-intensive application, such as a relational database, is running on the same computer, the resource-intensive application may be using the resources that Essbase needs.

See appName.log.

1008134

Unable to Lock the Allocated Memory pointerName in funtionName for reallocation, because of insufficient quota. Refer to the Application Log for details.

Essbase does not have enough physical memory to lock the memory.

If necessary, decrease the cache sizes.

Ensure that the Essbase computer has enough resources. Consult the Oracle Hyperion Enterprise Performance Management System Installation Start Here for system requirements. If a resource-intensive application, such as a relational database, is running on the same computer, the resource-intensive application may be using the resources that Essbase needs.

Restart the server computer.

Check the Essbase Server physical memory requirements. If necessary, increase the physical memory.

See appName.log.

1008135

Unable to Lock the Allocated Memory pointerName in functionName for reallocation, because of insufficient privilege. Refer to the Application Log for details.

Essbase is not assigned the correct operating system privileges to lock the needed memory.

Ensure that the Agent is assigned the correct operating system privileges (see Determining Operating System Privileges).

Ensure that the Essbase computer has enough resources. Consult the Oracle Hyperion Enterprise Performance Management System Installation Start Here for system requirements. If a resource-intensive application, such as a relational database, is running on the same computer, the resource-intensive application may be using the resources that Essbase needs.

See appName.log.

1008136

Unable to Free Locked Memory for pointerName in functionName

Essbase cannot free the memory, probably because an invalid pointer was passed to the function that frees the memory.

Contact Oracle Support.

1008137

Unable to Free Memory for pointerName in functionName in reallocation

Essbase cannot free the memory, probably because an invalid pointer was passed to the function that frees the memory.

Contact Oracle Support.

1008138

Unable to Free Memory for pointerName in functionName in reallocation. Refer to the Application Log for details.

Essbase cannot free the memory, probably because an invalid pointer was passed to the function that frees the memory.

See appName.log.

Contact Oracle Support.

1008139

Unable to Allocate Aligned Memory for pointerName in functionName

Essbase does not have enough virtual memory to allocate the memory to the listed pointer.

Check the Essbase Server virtual memory requirements. If necessary, increase the virtual memory and restart Essbase Server.

1008140

Unable to Free Aligned Memory for pointerName in functionName

Essbase cannot free the memory, probably because an invalid pointer was passed to the function that frees the memory.

Contact Oracle Support.

1008141

Unable to Allocate Aligned Memory for pointerName in functionName for reallocation

Essbase does not have enough virtual memory to allocate the memory to the listed pointer.

Check the Essbase Server virtual memory requirements. If necessary, increase the virtual memory and restart Essbase Server.

1008142

Unable to Free Aligned Memory for pointerName in functionName in reallocation

Essbase cannot free the memory, probably because an invalid pointer was passed to the function that frees the memory.

Contact Oracle Support.

1008143

Unable to Allocate Aligned Memory for pointerName in functionName. Refer to the Application Log for details.

Essbase does not have enough virtual memory to allocate the memory to the listed pointer.

Check the Essbase Server virtual memory requirements. If necessary, increase the virtual memory and restart Essbase Server.

See appName.log.

1008144

Check the Essbase Server virtual memory requirements. If necessary, increase the virtual memory and restart Essbase Server.

Essbase does not have enough virtual memory to allocate the memory to the listed pointer.

Check the Essbase Server virtual memory requirements. If necessary, increase the virtual memory and restart Essbase Server.

See appName.log.

1008145

Unable to Free Aligned Memory for pointerName in functionName in reallocation. Refer to the Application Log for details.

Essbase cannot free the memory, probably because an invalid pointer was passed to the function that frees the memory.

See appName.log.

Contact Oracle Support.

1008146

Unable to Unlock the Allocated Memory pointerName in functionName

Essbase cannot free the memory, probably because an invalid pointer was passed to the function that frees the memory.

Contact Oracle Support.

1008147

Unable to Allocate Memory for pointerName in functionName

Essbase does not have enough virtual memory to allocate the memory to the listed pointer.

Check the Essbase Server virtual memory requirements. If necessary, increase the virtual memory and restart Essbase Server.

1008148

Unable to Allocate Memory for pointerName in functionName. Refer to the Application Log for details.

Essbase does not have enough virtual memory to allocate the memory to the listed pointer.

Check the Essbase Server virtual memory requirements. If necessary, increase the virtual memory and restart Essbase Server.

See appName.log.

1008149

Abnormal shutdown request entered Are you sure you want to forcibly shutdown the application [1-yes,2-no]?

You are trying to shut down Essbase Server incorrectly.

If possible, stop Essbase Server correctly.

  1. Enter 2 and try to stop Essbase Server correctly.

  2. If you cannot stop Essbase Server correctly, enter 1 to stop Essbase Server.

  3. If this does not work, end the task (see Ending the Server Task).

  4. After you stop Essbase Server, follow the procedures for an abnormal shutdown.

1008150

The abnormal shutdown request is aborted, the application will continue processing

The administrator aborted an abnormal shutdown request, probably by answering no to message 1008149.

 

1008151

System is busy. The application will re-attempt the abnormal shutdown request.

Essbase Server is performing an important task, such as writing to the index.

When the task is complete, Essbase Server tries to shut down again.

1008152

System is still busy. The abnormal shutdown request is aborted, try again later.

Essbase Server is performing an important task, such as writing to the index. Essbase Server aborted the abnormal shutdown request to finish this task.

If possible, wait a few minutes and stop Essbase Server correctly. If you cannot stop Essbase Server correctly, end the task (see Ending the Server Task).

After you stop Essbase Server, follow the procedures for an abnormal shutdown.