Avoid shared-memory collision

Both the database server and onpload allocate shared memory. When onpload starts up, the database server allocates shared memory for buffers for onpload processes. The onpload utility also allocates shared memory for its internal use. Because of the dynamic nature of shared-memory allocations, shared-memory collisions can occur between onpload and the database server. If this collision occurs, the onpload job can also fail and error messages are sent to the onpload log file or the database server log file.

To verify if a collision has occurred, use the onstat -g seg option. Check for overlap between the shared-memory segments that the database server is using and the SHMBASE reported in the onpload log file.

Copyright© 2019 HCL Technologies Limited