Salesforce

Index rebuild stopped by HANGUP Signal.

« Go Back

Information

 
TitleIndex rebuild stopped by HANGUP Signal.
URL Name000055404
Article Number000170750
EnvironmentProduct: Progress
Version: All supported versions
Product: OpenEdge
Version: All supported versions
OS: Unix
Question/Problem Description
Index Rebuild stopped by HANGUP Signal, message 562
Index rebuild did not complete successfully after being interrupted by SIGHUP. 




 
Steps to Reproduce
Clarifying Information
The <dbname>.xb file does not exist in the working directory or the directory where the dbname.db file is located.
Error Message(562) HANGUP signal received.
(13629) Index rebuild utility did not complete successfully.
Index reconstruction utility was aborted. Rerun it to completion. (651)
Defect Number
Enhancement Number
Cause
A hangup signal was sent by the user or by the system.

One potential, but not exclusive, cause of the HANGUP signal can be an inactivity timer closing a terminal session to a machine.
When the operating system perceives the connection to the system has ended, sends a SIGHUP signal to all child processes of the session, thereby terminating the IDXBUILD operation.
Resolution
1.  Use the NOHUP option when performing long duration operations.

NOHUP will inform the Operating System to not allow hangup signals to be transmitted to the process.

Example of nohup for an Index Rebuild:

$   nohup proutil <database name> -C idxbuild all -TB 31 -TM 32 -SG 64 < y.txt

Where:
The content of the text file: "y.txt" is the y for yes, which would be needed to acknowledge that there is space for sorting.

2. A terminated idxbuild against a database leaves the database with an internal flag to indicate a failure has occurred with the idxbuild routine.

The next steps therefore are either:

A.  IF a full IDXBUILD operation was interrupted by the SIGHUP, then re-run a full IDXBUILD, with the NOHUP option outlined above.

B.  If a partial IDXBUILD operation was interrupted by the SIGHUP, then Refer to the Workaround information in Article
Excerpt from Article:

The file needs to have the <dbname>.xb for the file name. Example: sports2000.xb This file must exist in the working directory where the idxbuild command is going to be issued. When the idxbuild utility starts, it looks in the current directory for the <dbname.xb> file for the indexes to build. The contents of the <dbname>.xb file has the format of:

tableowner
tablename
indexname

This format needs to be repeated for all tables and indexes associated with the failed idxbuild. The file also needs to have an "!" exclamation point for the final entry and a new line following. Example <dbname>.xb file in the format: tableowner, tablename, indexname

PUB
customer
name
!
 
Workaround
Notes
Keyword Phrase
Last Modified Date11/20/2020 7:30 AM

Powered by