ontape & database logging modes

I am using Informix Dynamic Server 7.23 running on AIX (IBM RS/6000). The problem I have is that I occasionally have to use dbexport to get data from one Informix server, and then use dbimport to get the data onto a development area. The only difference between the servers is that one uses raw disk access and the other uses cooked space. When taking data from the raw area to the cooked area I do not use the -ss option on the dbexport command as this would cause the dbimport routine to fail on loading. The biggest problem is that once the data is loaded it is necessary to change the logging mode on the database from Not logged "N" status to Unbuffered logging ("U" status), this is normally achieved by typing : ontape -s -U <database name> However, sometimes this command fails to change the logging mode on the database, and only with repeated attempts does the system finally give in and change the logging mode, sometimes it can take many attempts and hours of frustration. If anyone else has had this problem, or knows how to fix it I would love to hear from you. Kind Regards Callum Reply by email to : callum@online-home.freeserve.co.uk PS Is there another method of changing the logging mode on a database other than using onmonitor or ontape ?

Callum wrote: > I am using Informix Dynamic Server 7.23 running on AIX (IBM RS/6000). The > problem I have is that I occasionally have to use dbexport to get data from > one Informix server, and then use dbimport to get the data onto a > development area. The only difference between the servers is that one uses > raw disk access and the other uses cooked space. When taking data from the > raw area to the cooked area I do not use the -ss option on the dbexport > command as this would cause the dbimport routine to fail on loading. > The biggest problem is that once the data is loaded it is necessary to > change the logging mode on the database from Not logged "N" status to [SNIP] > If anyone else has had this problem, or knows how to fix it I would love to > hear from you. OK you can fix the dbspace problem by editing the schema file. You can fix the logging problem by including the '-l' logging flag in the dbimport commandline.