Re: URGENT 2: LOGGING IN INFORMIX

Aurelio To check for open sessions you need to do a onstat -u and you need to kill sessions using onmode -z session_id. Since you are on NT, I dont really know how you will do it, but that is what I would do on Unix. When you close the SQL Editor window, you have killed the client, but you probably have not killed the session at the server. A probable (far fetched) reason could be that you are running out of locks, because you can do the same thing within a transaction but not outside one. In any case, DDL statements are always logged. It could also be a problem with your SQL editor setup. BTW, how is this urgent? You have obviously been able to create your tables by putitng them within a transaction. Or maybe I am misinterpreting something? HTH Sujit Aurelio <i52sacaa@uco.es> on 04/16/99 08:21:43 AM Please respond to Aurelio <i52sacaa@uco.es> To: informix-list@iiug.org cc: (bcc: Sujit Pal) Subject: URGENT 2: LOGGING IN INFORMIX Sorry, if I am reposting my message, but I haven?t received an answer yet. I have some other questions in this list, and they can wait, but this one is URGENT. Message was: Hello, I am installing Online Dynamic Server 7.3 (NT). Although I have programmed in a Informix enviroment I am newbie on installing it. I have been given only a server, a machine and some pdf manuals (and two weeks). I think that the instalation process is very easy, and it is installed well, and a default server instance too. But the problem raises when I try to create a new database. With SQL editor, what I do is: create database dbname with log; and then I launch the script with tables, constraints, etc. Everything is ok, but when some statements have been executed (not too much) the SQL Editor seems to crash (not respond, a sandclock), so I kill the task. If I init another session, and try to drop the database, I can't because the server returns : SQL Error (-425) : Database is currently opened by another user. [ ISAM error -107 : ISAM error: record is locked. ] and I am sure there isn't another session open. If I launch all the sentences within a transaction, all are executed properly, and SQL Editor doesn?t crash. So I think there's some problem with logging. (If I create the database without log it also fails) Maybe the nunmer of log files, or logsize... This is the part of the file. # Physical Log Configuration PHYSDBS rootdbs # Location (dbspace) of physical log PHYSFILE 2000 # Physical log file size (Kbytes) # Logical Log Configuration LOGFILES 20 # Number of logical log files LOGSIZE 5000 # Logical log size (Kbytes)LOG_BACKUP_MODE MANUAL # Logical log backup mode (MANUAL, CONT) Can anyone tell me what could be wrong? I am lost! Best regards, Aurelio