Consultor Eletrônico

Status: Unverified

SYMPTOM(s):

The proshut command is returning with an exit code of 1 during the db shutdown process.

Shutdown is executing. (1613)

<time> processes still connected. (2262)

Begin normal shutdown (2248)

Sending signal <signal number> to <num> connected user(s). (2261)

Sending signal 7 to 1 connected user(s). (2261)

Sending signal 7 to user 61 (-----)

Received signal <sigNum>; handling as SIGHUP. (4375)

Received signal 7; handling as SIGHUP. (4375)

Resending shutdown request to <num> user(s). (2263)

Resending shutdown request to 1 user(s). (2263)

HANGUP signal received. (562)

Disconnecting dead user <number>. (2527)

Disconnecting dead user 61 (2527)

<time><Multi/Single> session end. (334)

FACT(s) (Environment):

Database being shutdown via a script
Command to shutdown the database is: proshut dbname -by
proshut command is listed as SHUT 10 in the database log file.
Database does shutdown successfully after the user associated with the proshut command has exited from the database.
ia64 (Itanium)
HP-UX 11.x
OpenEdge 10.1B
OpenEdge Category: Database

CAUSE:

Bug# OE00179252

FIX:

The exit codes for the proshut command is 0 for successful and 2 which denotes a general purpose bad exit. An exit code of 1 on UNIX is used as a catchall for general errors.

If the proshut command returns with an exit code of anything other than 0, then additional investigation needs to be performed to identify if the database did in fact shutdown or if the process simply exited as a result of handling a signal that the process received while connected to the database.

Modify database shutdown scripts to make use of other commands to validate that the database shutdown instead of relying solely on return codes for the proshut command. Can validate that the database was successfully shutdown by using proutil busy command, checking for .lk file or parsing the log file for the message Multi user session end. (334)