Re: change logging

Benno - Change TAPEDEV and LTAPEDEV temporarily to /dev/null in your $ONCONFIG file. - Execute the following command from your Unix prompt: ontape -s -L 0 -U your_db_name. - Change TAPEDEV and LTAPEDEV back to what they were. The reason onmonitor and ontape are (apparently) taking you on a circular trip is because when you make a change from unlogged to a logged database, it needs to take a before-image of your database to start with, thats why you need the -s -L 0 in the ontape command. Strictly you should be backing up your initial image of the database to offline storage, but thats something you would need to decide based on how important the data is to you. As for the second problem, are you saying that SE will behave any differently in the case you mention? I dont know SE all that well, but WADR, I would be surprised if it did. Again the indexes you want to put into your database depend on your application, but to solve the problem you mention, I would put in an additional index on the second column, so now we have 2 indexes, the first is used by the SELECT and the second by the ORDER BY. HTH Sujit Benno Eiwen <benno.eiwen@cubeware.de> on 05/08/99 11:06:03 AM Please respond to Benno Eiwen <benno.eiwen@cubeware.de> To: informix-list@iiug.org cc: (bcc: Sujit Pal) Subject: change logging 2 questions regarding IDS: 1) how can I change a database from no logging to unbuffered logging? When I use onmonitor it tells me to use ontape. If I use ontape it tells me that I'm trying an invalid logging change. 2) I used to work with Informix SE. I have switched to IDS and it is way slower. Especially index handling is not clear to me. I have a compound index on two attributes. If I make a select on the first, order by on the second it takes forever. If I order on the first and the second it's fast. How can I tell the optimizer to always use the compound index= Your help is very much appreciated. Benno