Can't free logical logs

Can't free logical logs

Post by Diane Housto » Sun, 31 Dec 1899 09:00:00



I am running OnLine 5.01 UDS on HP-UX 9.04.

I had a problem with all logical logs full due to long transaction. I
was unable to resolve problem by methods from manual and unable take
off-line so I rebooted the system. OnLine now stuck in Recovery mode
although log shows:

Tue May 19 17:43:17 1998

17:43:17  INFORMIX-OnLine Initialized -- Shared Memory Initialized
17:43:18  Physical Recovery Started
17:43:18  Checkpoint Completed
17:43:18  Physical Recovery Complete: 0 Pages Restored
17:43:18  Logical Log Files are Full -- Backup is Needed

17:43:19  Logical Log Files are Full -- Backup is Needed

17:43:20  Logical Log Files are Full -- Backup is Needed

17:43:21  Logical Log Files are Full -- Backup is Needed

OnLine seems to think user dianeh still logged in

                          USER INFORMATION

                        Locks        Disk               Disk        User
 PID            User           Held         Reads      Writes
Status

 383            root               0                    6
2               ------D
   0            root               0            0               0
------D
   0            dianeh         0            0                   0
--T----
 595            root               0            0               0
------M
 571            root               0            0               0
------M

I have tried tbmode -c since status of log was U-B-L.

Any other suggestions before I restore.

Thanks in Advance

Regards
Diane Houston
MedAS
OASIS Application Support
Villiers House, Room 135
Tel: 19575

 
 
 

Can't free logical logs

Post by Ivan Lopes Junio » Sun, 31 Dec 1899 09:00:00


Hi Diane,

Once I entered in a situation exactly like that and I was able to perform
an emergencial logical log back-up using ondatartr utility (But my version
is 7.x and I don't know if it exists in version 5).

I was told that Informix Support has a utility to "bypass" the logical logs
and resolve problems like that.

If none of the above options resolve, you can always restore your last
back-up. :-(

Regards,

Ivan
----------

Sent:   Terca-feira, 19 de Maio de 1998 14:41

Subject:        Can't free logical logs

I am running OnLine 5.01 UDS on HP-UX 9.04.

I had a problem with all logical logs full due to long transaction. I
was unable to resolve problem by methods from manual and unable take
off-line so I rebooted the system. OnLine now stuck in Recovery mode
although log shows:

Tue May 19 17:43:17 1998

17:43:17  INFORMIX-OnLine Initialized -- Shared Memory Initialized
17:43:18  Physical Recovery Started
17:43:18  Checkpoint Completed
17:43:18  Physical Recovery Complete: 0 Pages Restored
17:43:18  Logical Log Files are Full -- Backup is Needed

17:43:19  Logical Log Files are Full -- Backup is Needed

17:43:20  Logical Log Files are Full -- Backup is Needed

17:43:21  Logical Log Files are Full -- Backup is Needed

OnLine seems to think user dianeh still logged in

                          USER INFORMATION

                        Locks        Disk               Disk        User
 PID            User           Held         Reads      Writes
Status

 383            root               0                    6
2               ------D
   0            root               0            0               0
------D
   0            dianeh         0            0                   0
--T----
 595            root               0            0               0
------M
 571            root               0            0               0
------M

I have tried tbmode -c since status of log was U-B-L.

Any other suggestions before I restore.

Thanks in Advance

Regards
Diane Houston
MedAS
OASIS Application Support
Villiers House, Room 135
Tel: 19575

 
 
 

Can't free logical logs

Post by Soporte Tecnico de Informi » Sun, 31 Dec 1899 09:00:00


        In my personal experience:

        For other time, never reboot the machine or the Online, first backup
the logs!  This is posibly in Online .03 and the next engines, i don't know
in 5.01.

        Now only restore!! :-(

        In this  version of the online, long transaction is very dangerous!,
before of realize this, I set the continous backup of logical logs or set
the database to no-transactions.  Other idea??

        Along time ago, with Online 4.xx, fix the problem by this: (Only=
 luck!)

        1. First try restore the database, but, the Online say: logical logs
full wish backup?
        2. And think this the solution, say yes, and push other data-tape,
and the Online backup some percent of the logs!
        3. I repeat the first step and the second, until the logs are=
 empty!!!
        4. I don't needed restore the Database.  Eureka!! Lucky!!

        I don't try after of this time this experience, and know what this
is not correct!!

        If you try, set to don't write mode the data-tape of the restore!!!
Take care of this!!! =20

Thanks. Gustavo

Note: Excuse the bad english!! :-)


Quote:>I am running OnLine 5.01 UDS on HP-UX 9.04.

>I had a problem with all logical logs full due to long transaction. I
>was unable to resolve problem by methods from manual and unable take
>off-line so I rebooted the system. OnLine now stuck in Recovery mode
>although log shows:=20

>Tue May 19 17:43:17 1998

>17:43:17  INFORMIX-OnLine Initialized -- Shared Memory Initialized
>17:43:18  Physical Recovery Started
>17:43:18  Checkpoint Completed
>17:43:18  Physical Recovery Complete: 0 Pages Restored
>17:43:18  Logical Log Files are Full -- Backup is Needed

>17:43:19  Logical Log Files are Full -- Backup is Needed

>17:43:20  Logical Log Files are Full -- Backup is Needed

>17:43:21  Logical Log Files are Full -- Backup is Needed

>OnLine seems to think user dianeh still logged in

>                          USER INFORMATION

>                            Locks        Disk               Disk        User
> PID        User           Held         Reads      Writes
>Status

> 383        root               0                    6
>2           ------D
>   0        root               0            0               0
>------D
>   0        dianeh         0            0                   0
>--T----
> 595        root               0            0               0
>------M
> 571        root               0            0               0
>------M

>I have tried tbmode -c since status of log was U-B-L.

>Any other suggestions before I restore.

>Thanks in Advance

>Regards
>Diane Houston
>MedAS
>OASIS Application Support
>Villiers House, Room 135
>Tel: 19575

Informix Costa Rica
Soporte T=E9cnico
Sistemas Integrales de Computaci=F3n
 
 
 

Can't free logical logs

Post by Sanjit Chakrabort » Sun, 31 Dec 1899 09:00:00


Hi Diane,

Try the following steps -
1.  Login as 'informix' and Set proper TBCONFIG.

2.  tbstat -u
    take all 'PID' for all users other than root and informix users.

3.  tbmode -z PID
    use this individually for all the PIDs.

4.  Login as 'root' and kill and PIDs with -15 option.
    kill -15 PIDs

5.  Login as informix , set your TBCONFIG and increase the 'Logical
    Log number' with some handful number from 'tbmonitor' for time
    being.

6.  tbtape -a
    take logical log backup.

7.  tbmode -ky
    stop your informix

8.  tbinit
    restart informix

9.  Change the logical log number to the previous status.

Bye,
Sanjit.
20/05/1998.

************************ START OF FORWARDED MESSAGE **********************


Subject        : Can't free logical logs
Date           : 19/05/98 23:44

I am running OnLine 5.01 UDS on HP-UX 9.04.

I had a problem with all logical logs full due to long transaction. I
was unable to resolve problem by methods from manual and unable take
off-line so I rebooted the system. OnLine now stuck in Recovery mode
although log shows:

Tue May 19 17:43:17 1998

17:43:17  INFORMIX-OnLine Initialized -- Shared Memory Initialized
17:43:18  Physical Recovery Started
17:43:18  Checkpoint Completed
17:43:18  Physical Recovery Complete: 0 Pages Restored
17:43:18  Logical Log Files are Full -- Backup is Needed

17:43:19  Logical Log Files are Full -- Backup is Needed

17:43:20  Logical Log Files are Full -- Backup is Needed

17:43:21  Logical Log Files are Full -- Backup is Needed

OnLine seems to think user dianeh still logged in

                          USER INFORMATION

                        Locks        Disk               Disk        User
 PID            User           Held         Reads      Writes
Status

 383            root               0                    6
2               ------D
   0            root               0            0               0
------D
   0            dianeh         0            0                   0
--T----
 595            root               0            0               0
------M
 571            root               0            0               0
------M

I have tried tbmode -c since status of log was U-B-L.

Any other suggestions before I restore.

Thanks in Advance

Regards
Diane Houston
MedAS
OASIS Application Support
Villiers House, Room 135
Tel: 19575

 
 
 

Can't free logical logs

Post by Volker Fraenkl » Sun, 31 Dec 1899 09:00:00


Your problem is,
INFORMIX needs free logical logs to do it's recovery. Some INFORMIX
ports have a tbinit flag, called "-F". This flag forces online to forget
the recovery.

But, with this flag your database may be inconsistent, after init.

Yours Volker

Diane Houston schrieb:

Quote:

> I am running OnLine 5.01 UDS on HP-UX 9.04.

> I had a problem with all logical logs full due to long transaction. I
> was unable to resolve problem by methods from manual and unable take
> off-line so I rebooted the system. OnLine now stuck in Recovery mode
> although log shows:

--

CS Controlling                  Phone:  +49 7144 8144-0
Software Systeme GmbH           Fax:    +49 7144 8144-10
Riedbachstrasse 5                              
74385 Pleidelsheim
 
 
 

Can't free logical logs

Post by Sunil Thakka » Sun, 31 Dec 1899 09:00:00


Sanjit,

I dont think this will work.  

Once the system is in long transaction - recovery mode then it will
never complete the recovery as there are no free logs to log the
recovery, and till the system completes the recovery we cannot do
anything like this.

The only alternative is to get the informix tech support to help us out.  
I had faced it twice before and both the times they had helped me out in
about 30 minutes.
(this goes against all the theories about informix tech supprt not
providing any support).

Thanks,
Sunil.


Date: Wed, 20 May 98 10:48:35 +0530

Subject: Can't free logical logs

Hi Diane,

Try the following steps -
1.  Login as 'informix' and Set proper TBCONFIG.

2.  tbstat -u
    take all 'PID' for all users other than root and informix users.

3.  tbmode -z PID
    use this individually for all the PIDs.

4.  Login as 'root' and kill and PIDs with -15 option.
    kill -15 PIDs

5.  Login as informix , set your TBCONFIG and increase the 'Logical
    Log number' with some handful number from 'tbmonitor' for time
    being.

6.  tbtape -a
    take logical log backup.

7.  tbmode -ky
    stop your informix

8.  tbinit
    restart informix

9.  Change the logical log number to the previous status.

Bye,
Sanjit.
20/05/1998.

************************ START OF FORWARDED MESSAGE
**********************


Subject        : Can't free logical logs
Date           : 19/05/98 23:44

I am running OnLine 5.01 UDS on HP-UX 9.04.

I had a problem with all logical logs full due to long transaction. I
was unable to resolve problem by methods from manual and unable take
off-line so I rebooted the system. OnLine now stuck in Recovery mode
although log shows:

Tue May 19 17:43:17 1998

17:43:17  INFORMIX-OnLine Initialized -- Shared Memory Initialized
17:43:18  Physical Recovery Started
17:43:18  Checkpoint Completed
17:43:18  Physical Recovery Complete: 0 Pages Restored
17:43:18  Logical Log Files are Full -- Backup is Needed

17:43:19  Logical Log Files are Full -- Backup is Needed

17:43:20  Logical Log Files are Full -- Backup is Needed

17:43:21  Logical Log Files are Full -- Backup is Needed

OnLine seems to think user dianeh still logged in

                          USER INFORMATION

                        Locks        Disk               Disk        User
 PID            User           Held         Reads      Writes
Status

 383            root               0                    6
2               ------D
   0            root               0            0               0
------D
   0            dianeh         0            0                   0
--T----
 595            root               0            0               0
------M
 571            root               0            0               0
------M

I have tried tbmode -c since status of log was U-B-L.

Any other suggestions before I restore.

Thanks in Advance

Regards
Diane Houston
MedAS
OASIS Application Support
Villiers House, Room 135
Tel: 19575

______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com

 
 
 

Can't free logical logs

Post by Glyn_Balmer_at_ERI.. » Sun, 31 Dec 1899 09:00:00


     In response to Diane Houston, Sanjit wrote on 20 May 1998 :-

     > Hi Diane,
     > Try the following steps -
     > 1.  Login as 'informix' and Set proper TBCONFIG.
     >
     > 2.  tbstat -u
     > take all 'PID' for all users other than root and informix users.

     Agreed. But note the following extract from OnLine Administrator's
     Guide v5.0 :-

     Check that the process is not in a critical section. Look at the
     third-position flag of the tbstat -u output. If the process flag is X,
     DO NOT KILL THE PROCESS. If you do, OnLine aborts with an immediate
     shutdown.

     Check that the process is not holding a latch. Obtain the address of
     the process from the tbstat -u output. Execute tbstat -s to look at a
     summary of latch information. Verify that the address of this process
     is not listed as the owner of any latch. If the process address is
     associated with a latch, DO NOT KILL THE PROCESS. If you do, OnLine
     aborts with an immediate shutdown.

     > 3.  tbmode -z PID
     > use this individually for all the PIDs.
     >> 4.  Login as 'root' and kill and PIDs with -15 option.
     >> kill -15 PIDs

     It may just be me being twitchy, having suffered from OnLine aborts
     and the subsequent late nights restoring, but I don't like "kill"-ing
     any Informix processes. I appreciate -15 is less severe than -9 (a
     definite no-no!!).

     >> 5.  Login as informix , set your TBCONFIG and increase the 'Logical
     >> Log number' with some handful number from 'tbmonitor' for time
     >> being.
     >> 6.  tbtape -a
     >> take logical log backup.
     >> 7.  tbmode -ky
     >> stop your informix
     >> 8.  tbinit
     >> restart informix
     >> 9.  Change the logical log number to the previous status.

     Regards

     Glyn Balmer
     I.T. Consultant
     BICC Cables Limited
     Erith  Kent  UK
     Tel: 0181 225-2281
     Fax: 0181 311-3300

 
 
 

Can't free logical logs

Post by David William » Sun, 31 Dec 1899 09:00:00




Quote:

>Sanjit,

>I dont think this will work.  

>Once the system is in long transaction - recovery mode then it will
>never complete the recovery as there are no free logs to log the
>recovery, and till the system completes the recovery we cannot do
>anything like this.

>The only alternative is to get the informix tech support to help us out.  
>I had faced it twice before and both the times they had helped me out in
>about 30 minutes.
>(this goes against all the theories about informix tech supprt not
>providing any support).

>Thanks,
>Sunil.

 Yep! they compile a tool to add logical logs WITHOUT logging the
 addition!! I have a lot of respect for these boys and girls! They are
 one of the few people apart from Art Kagel (who has an unfair advantage
 with access to Informix developers) who beat me at Informix...

- Show quoted text -


>Date: Wed, 20 May 98 10:48:35 +0530

>Subject: Can't free logical logs

>Hi Diane,

>Try the following steps -
>1.  Login as 'informix' and Set proper TBCONFIG.

>2.  tbstat -u
>    take all 'PID' for all users other than root and informix users.

>3.  tbmode -z PID
>    use this individually for all the PIDs.

>4.  Login as 'root' and kill and PIDs with -15 option.
>    kill -15 PIDs

>5.  Login as informix , set your TBCONFIG and increase the 'Logical
>    Log number' with some handful number from 'tbmonitor' for time
>    being.

>6.  tbtape -a
>    take logical log backup.

>7.  tbmode -ky
>    stop your informix

>8.  tbinit
>    restart informix

>9.  Change the logical log number to the previous status.

>Bye,
>Sanjit.
>20/05/1998.

>************************ START OF FORWARDED MESSAGE
>**********************



>Subject        : Can't free logical logs
>Date           : 19/05/98 23:44

>I am running OnLine 5.01 UDS on HP-UX 9.04.

>I had a problem with all logical logs full due to long transaction. I
>was unable to resolve problem by methods from manual and unable take
>off-line so I rebooted the system. OnLine now stuck in Recovery mode
>although log shows:

>Tue May 19 17:43:17 1998

>17:43:17  INFORMIX-OnLine Initialized -- Shared Memory Initialized
>17:43:18  Physical Recovery Started
>17:43:18  Checkpoint Completed
>17:43:18  Physical Recovery Complete: 0 Pages Restored
>17:43:18  Logical Log Files are Full -- Backup is Needed

>17:43:19  Logical Log Files are Full -- Backup is Needed

>17:43:20  Logical Log Files are Full -- Backup is Needed

>17:43:21  Logical Log Files are Full -- Backup is Needed

>OnLine seems to think user dianeh still logged in

>                          USER INFORMATION

>                               Locks        Disk               Disk        User
> PID           User           Held         Reads      Writes
>Status

> 383           root               0                    6
>2              ------D
>   0           root               0            0               0
>------D
>   0           dianeh         0            0                   0
>--T----
> 595           root               0            0               0
>------M
> 571           root               0            0               0
>------M

>I have tried tbmode -c since status of log was U-B-L.

>Any other suggestions before I restore.

>Thanks in Advance

>Regards
>Diane Houston
>MedAS
>OASIS Application Support
>Villiers House, Room 135
>Tel: 19575

>______________________________________________________
>Get Your Private, Free Email at http://www.hotmail.com

--
David Williams

Maintainer of the Informix FAQ
 Primary site (Beta Version)  http://www.smooth1.demon.co.uk
 Official site                http://www.iiug.org/techinfo/faq/faq_top.html

I see you standin', Standin' on your own, It's such a lonely place for you, For
you to be If you need a shoulder, Or if you need a friend, I'll be here
standing, Until the bitter end...
So don't chastise me Or think I, I mean you harm...
All I ever wanted Was for you To know that I care

 
 
 

Can't free logical logs

Post by Peter Tashkof » Sun, 31 Dec 1899 09:00:00


Sorry but I can't agree with this.
Why is the instance down in the first place?  Because the DBA did not =
configure the system right, or did not keep an eye on it.  High water mark =
was set too high else the system would have rolled back nicely.
It is *not* informix's fault that this has happened.

The tbzero facility is a ambulance that Informix has devised simply =
because people are always getting themselves into this state.  It dives =
beneath the covers and directly writes to the underlying system, so there =
is no QA, anything could happen, which is why there is no warranty for =
it's use and they won't leave it on a client machine, or publish it.

But it is *not* informix's problem.  It is a DBA issue.  If this is =
happening often to a production server, then the server is underconfigured,=
 or incorrectly configured.
rgds


Zespri International Limited      Std Disclaimers Apply
All rights reserved.  No party may use this document to vilify another.

Zespri New Zealand Kiwifruit, The World's Finest

This can happen so often that Informix should publish the "tbzero" or =
other
utility required to terminate the offending transaction and bring up the
instance.

If a production server is down, 30+ minutes for tech support to fix the
problem is too long.

...Terry.

-----Original Message-----



Date: May 20, 1998 10:33
Subject: Re: Can't free logical logs

>Sanjit,

>I dont think this will work.

>Once the system is in long transaction - recovery mode then it will
>never complete the recovery as there are no free logs to log the
>recovery, and till the system completes the recovery we cannot do
>anything like this.

>The only alternative is to get the informix tech support to help us out.
>I had faced it twice before and both the times they had helped me out in
>about 30 minutes.
>(this goes against all the theories about informix tech supprt not
>providing any support).

>Thanks,
>Sunil.


>Date: Wed, 20 May 98 10:48:35 +0530

>Subject: Can't free logical logs

>Hi Diane,

>Try the following steps -
>1.  Login as 'informix' and Set proper TBCONFIG.

>2.  tbstat -u
>    take all 'PID' for all users other than root and informix users.

>3.  tbmode -z PID
>    use this individually for all the PIDs.

>4.  Login as 'root' and kill and PIDs with -15 option.
>    kill -15 PIDs

>5.  Login as informix , set your TBCONFIG and increase the 'Logical
>    Log number' with some handful number from 'tbmonitor' for time
>    being.

>6.  tbtape -a
>    take logical log backup.

>7.  tbmode -ky
>    stop your informix

>8.  tbinit
>    restart informix

>9.  Change the logical log number to the previous status.

>Bye,
>Sanjit.
>20/05/1998.

>************************ START OF FORWARDED MESSAGE
>**********************



>Subject        : Can't free logical logs
>Date           : 19/05/98 23:44

>I am running OnLine 5.01 UDS on HP-UX 9.04.

>I had a problem with all logical logs full due to long transaction. I
>was unable to resolve problem by methods from manual and unable take
>off-line so I rebooted the system. OnLine now stuck in Recovery mode
>although log shows:

>Tue May 19 17:43:17 1998

>17:43:17  INFORMIX-OnLine Initialized -- Shared Memory Initialized
>17:43:18  Physical Recovery Started
>17:43:18  Checkpoint Completed
>17:43:18  Physical Recovery Complete: 0 Pages Restored
>17:43:18  Logical Log Files are Full -- Backup is Needed

>17:43:19  Logical Log Files are Full -- Backup is Needed

>17:43:20  Logical Log Files are Full -- Backup is Needed

>17:43:21  Logical Log Files are Full -- Backup is Needed

>OnLine seems to think user dianeh still logged in

>                          USER INFORMATION

>                       Locks        Disk       Disk        User
> PID    User           Held         Reads      Writes
>Status

> 383    root               0            6
>2       ------D
>   0    root               0            0           0
>------D
>   0    dianeh         0            0           0
>--T----
> 595    root               0            0           0
>------M
> 571    root               0            0          0
>------M

>I have tried tbmode -c since status of log was U-B-L.

>Any other suggestions before I restore.

>Thanks in Advance

>Regards
>Diane Houston
>MedAS
>OASIS Application Support
>Villiers House, Room 135
>Tel: 19575

>______________________________________________________
>Get Your Private, Free Email at http://www.hotmail.com=20