Process won’t start

I noticed the following in your process log….

[dbi :dbi :ERR /0:

A little late here but you could try ‘hcilmclear’.

When I run it I get:

c:temp>hcilmclear -p obhboc -v

Clearing db user “obhboc_cmd”

Clearing db user “obhboc_xlate”

I hate to ressurect old threads like this, but this is the exact same thing happening to us right now. Messages had been processing fine for weeks without issue and then suddenly stopped. Below is a copy of the output. Almost exactly the same as the one above.

Any ideas?

[prod:prod:INFO/0:

Did you try Greg Day’s suggestion?

The information I have is for windows to shutdown the process, daemons and restart QDX service.

Hello All,

I’ve run through all of the suggested solutions, with no success yet. We’ve even bounced the server to make sure we’ve covered all of our bases. It only seems to be occurring with this one process.

Additionally, I’ve dug a bit deeper and have found the following that might be of use as well…

Reported at: Fri Oct 12 09:26:32 CDT 2007

Status

Are all of those failed messages really in your error database?

Do you ever purge your error database?

I’d shut down, do an hcidbinit -AC, then hcimsiutil -Z and start again.

Eureka! That did the trick. However, I feel that I’ve found the root culprit in the following error.

Proto Err: Fri Oct 12 12:07:35 CDT 2007

Error Msg: cannot open ……datainbound/OBGYN_CAD_db_20071004.BAK for reading: No

This error (and others similar to it) have cropped up before during testing and development of this interface in particular, but they haven’t blocked the flow of data into Xlates. Now though, the process is back up and running, but the inbound thread is still showing the preceding error.

We’re still pretty new at trying to troubleshoot these issues, so we haven’t really gotten our “sea legs” yet.

Thank you all, again, for your input and suggestions. They are greatly appreciated.

Posting to this older thread because someone saw this and thought they were having same problem.  I wanted to clarify some things.  The relevant error for the original poster is this one.

[dbi :dbi :ERR /0:       obhboc] Db_Vista database error -921: ‘SYSTEM/OS error: -921

Now the following error message “EXCEPTION_ACCESS_VIOLATION” was in the log but was simply a consequence of the 921.  There are many things that can cause an EXCEPTION_ACCESS_VIOLATION that have nothing to do with a 921.  Usually that is either bad data or permissions caused by some other software or program accessing the cloverleaf files while cloverleaf is writing to them.  

For the 921 what you do depends on your OS.  First we will assume this was on a unix box.  We look and see what the duplicate user was.

[dbi :dbi :ERR /0:       obhboc] Duplicate DB_VISTA user id: ‘testobhboc’

The following command could have been used.

lmclear -u testobhboc -mp

Alternatively if this does not work the following command could be used

hcilmclear -p processname

where processname is the name of the process that is having a problem.  

Now if you are on windows the lmclear command will not work because there is no lock manager to process the command.  So when you get the dbvista -921 on windows you have to stop all engines on all sites and all daemons on all sites and then bounce the cloverleaf service.  I usually hit task manager and go to the processes tab to verify there is nothing hci still left running.  If possible the service should not be stopped while any engines or daemons are running.  The exact name of the service varies slightly on each cloverleaf version so if in doubt you may need to call support to be certain.  

So in summary the EXCEPTION_ACCESS_VIOLATION may be very important when not preceded by the 921 but when the two are found together deal with the 921 and the EXCEPTION_ACCESS_VIOLATION should disappear since it is 99% probably caused by the real 921 problem.

Hopefully this clears this up a little and does not confuse anyone more.

Try stopping the lock monitor and monitor deamon, and rebooted the server. Also if this doesn’t work you can do clover leaf cleanup .

1.shutdown the site – hcisitectl -K -f

2. Remove the CMD and PID file in