yeah, i've read that and saw this in a lot of other SQL DB, but when it comes to reality with a large amount of insert/delete made to the table the index is corrupted and there's the need to rebuild it like once a week.

Have you got any experiece like this? I need to create an index and use it on a table that will costantly have insert and delete (transactional data, a list/queue of transactions that needs to be processed)


Hi, to examine and kill a job i'll go via terminal in iris session, zn to %SYS and execute ^JOBEXAM that is a sort of "top" for linux.

in the process list you can push (or keep pushed) spacebar to update the screen and keep an eye on the column "globals" and "lines", the ones that will grow really fast are probably the jobs that you are looking for.

Using "n" and "p" you can go to "Next" or "Previous" page.

When you fins the process that in your opinion is the one that needs to be killed you can examine what it's doing pushing "E" to "Examine" and give the job number (the first column). Also in this case pressing spacebar will update the screen.

When you are sure that you want to kill that process proceed with "t" to "Terminate" the job followed by the number.

Doing so, you can easily find all the jobs that needs to be killed

Hi, you simply got an information (0 in the log), these are system db so you can choose to not backup them (they are included in the installation) and running the task as another use won't solve the problem (that is not a problem).

Also mounting them as rw is a bad bad thing because you can end up in modifying the DB (Andi you don't want this).

You should simply ignore the message and if it's a monitoring system that warns you, set it to check for 1 or above severity (I'll go for 2 or more).

If you really really want to get rid of it and still backup every db, write a custom backup routine tanto mounts the db row, backup them, get them ro again. But this would be a waste of time because it's just an info