Thread: Table locking SC 4.0

Hi what a responce :smile: great.

Well I have a nother problem, we are running on a production system a database from version 3.05 and p4 database.



We did an upgrade to 4.04 client and server, but we are still using the old DB files with less then 2% modifications (only form changes nothing deep). The upgrade was made in October 2001. And everything runs great. But since 2 weeks we have massive problems, with sand clocks, some categories in ICM are not able to view anymore or 10 % of the tickets are not able open or view. IF we are in an in box (sc.manage.problem) you see all tickets listed but if you want to open them nothing happens only "sand clock"! The client will freeze and you have to cancel "click the X" to stop the client. After reboot the client, you see in the system form still the old process running.

If we Kill this process with sucess, nothing happens after log in and try to view other tickets.These tickets are not "locked" from other operators.

All in ICM nothing call or change Mgmnt.



-->Is there an association with DEADLINES ?



-> Is it a bug from Peregrine ? or could it be connected cause of 3.05 DB and 4.04 ?



Kindly regards,



John



Germany

PS: IF I am more trained in this I would give some help if needed in sending Documents or other stuff. :smile: :smile:

I think You should run a LFSCAN on your database.



Be sure to have a backup before you start.



As for the cause, I am not sure it is related to the upgrade. More likely is it that somehow the database is corrupt and this could have been caused by a crash on the server or f.ex. doing dbdict changes with the system client.