Hi,

I am trying to turn transaction support ON for my databases. I have
been able to turn transactions on for the sysmaster and sysutils
database, but I can't turn it on for my user created databases.

I turned on the transactions for sysmaster and sysutils by adding
"TAPEDEV /dev/null" to the onconfig file, and issued "ontape -s -L 0
-B sysmaster". I tried issuing "ontape -s -L 0 -B newdb", but the
transactions support for the "newdb" database is not turned on.

I make a jdbc connection to the Informix server using the sysmaster
database and I can start a transaction, but if I change the database
to "newdb", I can't start a transaction.

Am I doing something wrong? Does anyone have any ideas on how I can
turn ON transactions for my databases?

thanks in advance
-John

Hi John,

You won't be able to alter the transaction status of a database if any user
is connected to it.

Make sure nobody is using newdb and try again.

HTH

--
Phil@oninit.com

JohnLH wrote:

>"Phil Rule" <phil.rule@ntlworld.com> wrote in message news:<7jTLa.146$oB5.53@newsfep3-gui.server.ntli.net>...
>
>
>>Hi John,
>>
>>You won't be able to alter the transaction status of a database if any user
>>is connected to it.
>>
>>Make sure nobody is using newdb and try again.
>>
>>HTH
>>
>>
>
>I did a query on the sysdatabases and got what shows the logging
>status ...
>
> name partnum owner created is_logging
> ------------ ---------- -------- ---------- -------------
> sysmaster 1048579 informix 2003-02-03 1
> sysutils 1048742 informix 2003-02-03 1
> example_data 1048626 informix 2003-02-27 0
> contact_data 2097154 informix 2003-02-27 0
> newdb 1048688 informix 2003-06-30 0
> newdb_log 1048798 informix 2003-06-30 1
>
> 6 record(s) selected [Fetch MetaData: 0/ms] [Fetch Data: 0/ms]
>
> [Executed: 6/30/03 12:19:09 PM PDT ] [Execution: 0/ms]
>
>
>I still couldn't change the transactions on the databases with no
>connections. I also used ondblog without success, but I was able to
>create a database with transaction support with "CREATE DATABASE
>newdb_log WITH BUFFERED LOG" ...
>
>So, that should be enough to solve my problem.
>
>thanks
>John
>
>
This may or may not help you, but some time ago I was unable
to turn Buffered log mode on, however Unbuffered worked. No idea why.

Michael