logging change error

[h***@gmail.com]

Hi
I am a new Informix DBA - and have never use Informix before :) (I have an
Oracle background)
Yesterday I dbimported a database (ausatst -thank god it is a test database,
but still v. important at this stage of the project). I had not set logging
on (didn't know I had to) and had to go to a meeting. The PeopleSoft
administrator (my backup) attempted to set logging on with "ontape -s -U
ausatst" and encountered some sort of error. I think he may have done a
level 2 ontape.
Anyway the present situation is that onmonitor reports a logging status of
N. Any attempt to alter the logging status results in the following error
Error changing logging status - 'aufstst'. iserrno 107.
I have attempted to do "ontape -s -N ausatst" with the same result.
ontape -s -B ausatst gives the result "invalid logging change" or some very
similar error. I have dropped and reimported the database. I have stopped
and resarted the instance. The docos refer to an onarchive command that
stops a partly completed logging change but we don't use onarchive and it
doesn't run - I tried it.
Any help greatfull appreciated. As I do not have newsgroup access at work
Karl Hewlett
PeopleSoft DBA
University of Auckland
New Zealand

ejecutar dbimport con -l buffered
la solucion funciona:

server:informix/home/informix > ontape -s -L 0 -B database

Please mount tape 1 on /work/tape_serverinformix and press Return to continue ...
10 percent done.
20 percent done.
30 percent done.
100 percent done.
Read/Write End Of Medium enabled: blocks = 61441

Please label this tape as number 1 in the arc tape sequence.
This tape contains the following logical logs:

20542

Program over.

[Mike Walker]

I think that this might be as simple as making sure that there is NOBODY in the database when you try and change the logging mode.

The 107 is a locking error.

Run "onstat -g sql" and there should be NO connections referencing the ausatst database.

I don't know what version of Informix you are on, but you may find the ondblog command (if available) more friendly than using ontape.

-----Original Message-----
From: informix-list-***@iiug.org [mailto:informix-list-***@iiug.org] On Behalf Of ***@gmail.com
Sent: Friday, March 22, 2019 12:08 PM
To: informix-***@iiug.org
Subject: Re: logging change error

Hi
I am a new Informix DBA - and have never use Informix before :) (I
have an Oracle background)
Yesterday I dbimported a database (ausatst -thank god it is a test
database, but still v. important at this stage of the project). I had
not set logging on (didn't know I had to) and had to go to a meeting.
The PeopleSoft administrator (my backup) attempted to set logging on
with "ontape -s -U ausatst" and encountered some sort of error. I
think he may have done a level 2 ontape.
Anyway the present situation is that onmonitor reports a logging
status of N. Any attempt to alter the logging status results in the
following error
status - 'aufstst'. iserrno 107.
I have attempted to do "ontape -s -N ausatst" with the same result.
ontape -s -B ausatst gives the result "invalid logging change" or
some very similar error. I have dropped and reimported the database.
I have stopped and resarted the instance. The docos refer to an
onarchive command that stops a partly completed logging change but we
don't use onarchive and it doesn't run - I tried it.
Any help greatfull appreciated. As I do not have newsgroup access at
Karl Hewlett
PeopleSoft DBA
University of Auckland
New Zealand

ejecutar dbimport con -l buffered
la solucion funciona:

server:informix/home/informix > ontape -s -L 0 -B database

Please mount tape 1 on /work/tape_serverinformix and press Return to continue ...
10 percent done.
20 percent done.
30 percent done.
100 percent done.
Read/Write End Of Medium enabled: blocks = 61441

Please label this tape as number 1 in the arc tape sequence.
This tape contains the following logical logs:

20542

Program over.