Index build fails with a Killed message on screen

"idxbuild all" command fails with a "Killed" message on screen.
IDXBUILD fails with "Command terminated by signal 9"
No error messages in database log file, as index build just stops.
There are no procore or protrace files created.
There is sufficient disk space available.

Linux system log file "/var/log/messages" contains the following: 

<process_name> invoked oom-killer:
Out of memory: Kill process <PID> (_dbutil) score 316 or sacrifice child
Killed process <PID> (_dbutil) total-vm:3117988kB, anon-rss:2957708kB, file-rss:368kB
 

Linux "oom-killer" process sacrificed the index rebuild when the server has ran out of memory and another process started requesting more memory.

There are several ways how to avoid this Linux "oom-killer" process stopping Progress index rebuild, for example:

• allocate more available RAM memory to the server or run idxbuild at another time when more memory is available when there is less demand from other processes 
• instead of "idxbuld all" run "idxbuild" at the area / table level 
• reconfigure or disable Linux "oom-killer" process in consulation with Linux support
• Review IDXBUILD parameters used to use less RAM memory:  For example specify  -TF <n> memory usage factor, with a smaller percentage (default 50) 

Progress Articles:

 What is the OOM Killer (Out of Memory Killer)?
 What are the new Index Rebuild parameters that were introduced in 10.2B06?
 How much memory will the 10.2B07 11.2 enhanced IDXBUILD allocate initially ?
 Would consuming all memory bring other databases down?