Interesting problem with trigger

[Norman Biggar]

We are experiencing an unusual problem with a trigger.

Version 9.1C on UNIX box.
Occasionally, when updating our database, the update fails and multiple copies of the following message appear in the appbroker log file:

 11:28:44 10 Jun 2005 Application Server 16936 Procedure: '/hsmsV9/software/trigs/c_jobhis.p' Line:3
[size=2]Database hsmsrep does not exist or is not open. (3141)[/size]
[size=2]11:28:44 10 Jun 2005 Application Server 16936 Procedure: '/hsmsV9/software/trigs/c_jobhis.p' Line:3[/size]
[size=2]Database hsmsrep does not exist or is not open. (3141)[/size]
[size=2]11:28:44 10 Jun 2005 Application Server 16936 Procedure: '/hsmsV9/software/trigs/c_jobhis.p' Line:3[/size]
[size=2]Database hsmsrep does not exist or is not open. (3141)[/size]
[size=2](Repeated - all for same server)[/size]

Program c_jobhis.p is a create trigger for table Job_History on hsmsrep. The fact it is the trigger is stored on the hsmsrep schema.

Here is the code

TRIGGER PROCEDURE FOR CREATE OF Job_History.
ASSIGN Job_History.History_No = NEXT-VALUE(sJob_History)
Job_History.Job_Status_Date = TODAY
Job_History.Job_Status_Time = TIME.

Sequence sJob_History is also on hsmsrep and has a value of about 15,000,000.

How could Progress identify from the schema of hsmsrep that c_jobhis.p was the trigger to be run if hsmsrep was not connected?
Surely the program that tried to create the Job_History record would never have run if hsmsrep was not connected.
There were no error messages on the database log file.
Hope you can help.