go to post Pietro Montorfano · May 25 Hi,i'll try a copy after join the mirror (step 11 before step 9) so that mirror knows that there's a new member. So basically shut down both iris, copy the files from TEST_NODE1 to TEST_NODE2 and start them again (first TEST_NODE1 and the TEST_NODE2) Pietro
go to post Pietro Montorfano · May 24 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) Thanks
go to post Pietro Montorfano · May 23 I think that it depends on the filters in studio. You should be looking for a "class definition CLS". Try to check it with the web portal. System explorer > classes, choose the namespace (should be "monitor"), look at the classes
go to post Pietro Montorfano · May 19 You can became iris owner with su - iris owner Via sudo or via root user Moreover you can run iris list To see where iris is installed. Other "funny" ways can be lsof | grep iris ps ef | grep iris
go to post Pietro Montorfano · May 19 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
go to post Pietro Montorfano · May 17 yes if you have the global mapped in some different db, GOF will tell you so you need to go first with ^%GD to display the mapping, zn to that db and use ^%GOF. ^%GIF can be used anywhere inside the Namespace.
go to post Pietro Montorfano · May 15 Ok, if we are talking about code in deployed mode you simply can't do this. You must get a code compiled for your actual version. You can try with $SYSTEM.OBJ.Export which export the obj, but you will probably get the same error.
go to post Pietro Montorfano · May 14 Hi, you could check what's happening using Wireshark to analyze the TCP traffic and the request that you are doing. Are you getting this error on the server side, what you got on client side? Seems that they are not communicating or the server is getting something wrong
go to post Pietro Montorfano · May 14 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