Ingres Resource Deadlock

Ingres Resource Deadlock

Post by Jon Nago » Sat, 13 Nov 1999 04:00:00



I'm having problems with the resource deadlock issue with my ingres 6.4/07
installation on the E3500 machine, I'm running Prophecy Billing Suite.  The
ingres engine keeps shutting down by itself when it hit the resource deadlock
issue.  Below is the errlog.log and the current parameters of the dbms.. i
really hope anybody can help me with a correct settings of the dbms parameters
or anything that could resolve the problem.  Thank you very much...i would
really appreciated it.

Regards,
Jon Nagome

errlog.log

      ::[36841           , 00836040]: Fri Oct 29 08:52:53 1999
E_DM9043_LOCK_TIMEOUT
   Timeout occurred during lock request on table TABLE_ID (2749,0)
in database polydb with mode 2.

      ::[36841           , 0056E4E0]: Fri Oct 29 08:52:53 1999
E_DM9043_LOCK_TIMEOUT
   Timeout occurred during lock request on table TABLE_ID (2749,0)
in database polydb                  with mode 2.

      ::[36841           , 00AB2880]: Fri Oct 29 08:53:08 1999
E_DM9043_LOCK_TIMEOUT
   Timeout occurred during lock request on table TABLE_ID (2749,0)
in database polydb                   with mode 2.

      ::[36841           , 00EB9EC0]: Fri Oct 29 08:53:10 1999
E_DM9043_LOCK_TIMEOUT
   Timeout occurred during lock request on table TABLE_ID (2749,0)
in database polydb                   with mode 2.

      ::[36841           , 00F0B1C0]: Fri Oct 29 08:53:30 1999
E_DM9043_LOCK_TIMEOUT
   Timeout occurred during lock request on table TABLE_ID (2749,0)
in database polydb                   with mode 2.

      ::[36841           , 01317800]: Fri Oct 29 09:11:18 1999
E_CLFE06_BS_WRITE_ERR
   Write to peer process failed; it may have exited.

      ::[36839           , 00ED5080]: Fri Oct 29 09:15:03 1999
E_CLFE06_BS_WRITE_ERR
   Write to peer process failed; it may have exited.

      ::[36841           , 00F85520]: Fri Oct 29 09:22:48 1999
E_CLFE07_BS_READ_ERR
    Read from peer process failed; it may have exited.

      ::[36841           , 00F85520]: Fri Oct 29 09:22:48 1999
E_SC022F_BAD_GCA_READ
   SCF was unable to read a GCF block.
      ::[36841           , 00E28A40]: Fri Oct 29 09:26:21 1999
E_DM9044_ESCALATE_DEADLOCK
      Deadlock encountered while escalating to table level locking
on table bitsessround             in database polydb with mode 5.

      ::[36841           , 00E28A40]: Fri Oct 29 09:26:21 1999
E_DM0042_DEADLOCK        Resource deadlock.
      ::[36841           , 00E28A40]: Fri Oct 29 09:26:21 1999
E_QE002A_DEADLOCK        Deadlock detected.
      ::[36841           , 00E28A40]: Fri Oct 29 09:26:27 1999
E_CL1005_LK_NOLOCKS      Out of lock resources

      ::[36841           , 00E28A40]: Fri Oct 29 09:26:27 1999
E_DM004B_LOCK_QUOTA_EXCEEDED     Lock quota exceeded.
      ::[II_RCP          , 00316040]: DMF EXCEPTION: Segmentation
Violation (SIGSEGV) @ PC 19d958 SP efffeb20 PSR fe001003 G1 4 o0 2f3a64
      ::[II_RCP          , 00316040]: Fri Oct 29 09:26:29 1999
E_DM904A_FATAL_EXCEPTION
A Fatal Error has occurred in the DMF Facility.
      ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
E_CL0F04_LG_BADPARAM
    Bad input parameter passed to LG routine

      ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
E_DM900F_BAD_LOG_EVENT
  Error waiting for the logging system event:  0x00010071.

      ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
E_DM9815_ARCH_SHUTDOWN
  The Archiver was told to shutdown.
      ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
E_CL0F04_LG_BADPARAM
    Bad input parameter passed to LG routine

      ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
E_DM900E_BAD_LOG_END
    Error trying to end the transaction:  0x0002000B.

      ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
E_DM9811_ARCH_LOG_END
   The Archiver got an error trying to do an LGend call.
      ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
E_DM9813_ARCH_CLOSE_LOG
 The Archiver got an error trying to close the log file.
      ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
E_DM9815_ARCH_SHUTDOWN
  The Archiver was told to shutdown.

      ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
E_DM9855_ACP_LG_ACCESS_EXIT
     Archive processing cannot continue due an error reading information
from the Logging System. Please check the Archiver Log (II_ACP.LOG)
for the specific operation which failed and more detailed messages
describing the error.  Verify that the Ingres Installation is currently
running. It is possible that failures attempting to read the Ingres
Log File could be caused by process quota limitations; if so, this
should be reflected in the error log.  If the cause of the error
is not apparent, try restarting archive processing via the Ingres
command 'iiarchive'.  If the same error is encountered, try stopping
and restarting the Ingres installation.

logstat

======================Fri Oct 29 10:49:30 1999 Logging System
Summary======================
    Database add              190        Database removes          176
    Transaction begins     137587        Transaction ends       137555
    Log read i/o's             55        Log write i/o's         67586
    Log writes             502126        Log forces              38365
    Log waits               41070        Log split waits         16899
    Log free waits            199        Log stall waits             4
    Log BCP waits               4        Logfull stall waits         0
    Log group commit        20920        Log group count         22274
    Check commit timer      22169        Timer write             19457
    Inconsistent db             0        Kbytes written         465911
----Current log file
header---------------------------------------------------------------
    Block size: 8192    Block count: 131292    Buffer count: 12
    CP interval: 6564   Logfull interval: 124727   Abort interval: 105033
    Last Transaction Id:    000038106FE00247
    Begin: <940601276:33061:6920>    CP: <940601276:46211:6488>    End:
<940601276:47942:1432>
    Percentage of log file in use: 11
    Journal Window: <0,0,0>..<0,0,0>
    Dump Window: <0,0,0>..<0,0,0>
    Status:         ONLINE,ECPDONE
----List of active
processes--------------------------------------------------------------
    ID        PID      TYPE    OPEN_DB   WRITE   FORCE    WAIT   BEGIN    
END

--------------------------------------------------------------------------------------
    0001000A  00004378 FCT,SBM        6  441748    1698   32626  100736
100722
    0001000D  00004359 ARCHIV        1       0       0     395       2      
1
    00010010  00004355 MASTER        1      46       0     405       1      
0
    0001001F  0000441C FCT,SBM        6   60332     584    7644   36848  
36833
----List of active
databases-------------------------------------------------------

iibuild.log

The number of log buffers in the memory : 12
The maximum number of transactions in the logging system : 400
The maximum number of databases in the logging system: 48
The maximum consistency point interval for invoking archiver : 1
The block size of the log file : 8 Kbytes
The log-full-limit in percentage : 95
The percentage of log file for each consistency point : 5
The force-abort-limit in percentage : 87
The size of the lock hash table : 13001
The size of the resource hash table : 13001
The maximum number of locks in the locking system : 65000
The maximum number of lock lists in the locking system : 400
The maximum number of locks allowed per transaction : 800

____________________________________________________________________
Get free email and a permanent address at http://www.netaddress.com/?N=1

 
 
 

Ingres Resource Deadlock

Post by Reid, Ste » Sat, 13 Nov 1999 04:00:00


F.Y.I.,
                We are running the same release 6.4/07
        on Solaris 2.6 running Prophecy Billing Suite also
        We have crashed twice in the last 2 days also.
        Any info would be helpful.

Regards

Steve Reid.

> -----Original Message-----
> From:      Jon Nagome [SMTP:jon_nag...@usa.net]
> Sent:      Friday, 12 November 1999 15:51
> To:        info-ing...@ams.org
> Subject:   Ingres Resource Deadlock

> I'm having problems with the resource deadlock issue with my ingres 6.4/07
> installation on the E3500 machine, I'm running Prophecy Billing Suite.
> The
> ingres engine keeps shutting down by itself when it hit the resource
> deadlock
> issue.  Below is the errlog.log and the current parameters of the dbms.. i
> really hope anybody can help me with a correct settings of the dbms
> parameters
> or anything that could resolve the problem.  Thank you very much...i would
> really appreciated it.

> Regards,
> Jon Nagome

> errlog.log

>       ::[36841           , 00836040]: Fri Oct 29 08:52:53 1999
> E_DM9043_LOCK_TIMEOUT
>    Timeout occurred during lock request on table TABLE_ID (2749,0)
> in database polydb with mode 2.

>       ::[36841           , 0056E4E0]: Fri Oct 29 08:52:53 1999
> E_DM9043_LOCK_TIMEOUT
>    Timeout occurred during lock request on table TABLE_ID (2749,0)
> in database polydb                  with mode 2.

>       ::[36841           , 00AB2880]: Fri Oct 29 08:53:08 1999
> E_DM9043_LOCK_TIMEOUT
>    Timeout occurred during lock request on table TABLE_ID (2749,0)
> in database polydb                   with mode 2.

>       ::[36841           , 00EB9EC0]: Fri Oct 29 08:53:10 1999
> E_DM9043_LOCK_TIMEOUT
>    Timeout occurred during lock request on table TABLE_ID (2749,0)
> in database polydb                   with mode 2.

>       ::[36841           , 00F0B1C0]: Fri Oct 29 08:53:30 1999
> E_DM9043_LOCK_TIMEOUT
>    Timeout occurred during lock request on table TABLE_ID (2749,0)
> in database polydb                   with mode 2.

>       ::[36841           , 01317800]: Fri Oct 29 09:11:18 1999
> E_CLFE06_BS_WRITE_ERR
>    Write to peer process failed; it may have exited.

>       ::[36839           , 00ED5080]: Fri Oct 29 09:15:03 1999
> E_CLFE06_BS_WRITE_ERR
>    Write to peer process failed; it may have exited.

>       ::[36841           , 00F85520]: Fri Oct 29 09:22:48 1999
> E_CLFE07_BS_READ_ERR
>     Read from peer process failed; it may have exited.

>       ::[36841           , 00F85520]: Fri Oct 29 09:22:48 1999
> E_SC022F_BAD_GCA_READ
>    SCF was unable to read a GCF block.
>       ::[36841           , 00E28A40]: Fri Oct 29 09:26:21 1999
> E_DM9044_ESCALATE_DEADLOCK
>       Deadlock encountered while escalating to table level locking
> on table bitsessround             in database polydb with mode 5.

>       ::[36841           , 00E28A40]: Fri Oct 29 09:26:21 1999
> E_DM0042_DEADLOCK        Resource deadlock.
>       ::[36841           , 00E28A40]: Fri Oct 29 09:26:21 1999
> E_QE002A_DEADLOCK        Deadlock detected.
>       ::[36841           , 00E28A40]: Fri Oct 29 09:26:27 1999
> E_CL1005_LK_NOLOCKS      Out of lock resources

>       ::[36841           , 00E28A40]: Fri Oct 29 09:26:27 1999
> E_DM004B_LOCK_QUOTA_EXCEEDED     Lock quota exceeded.
>       ::[II_RCP          , 00316040]: DMF EXCEPTION: Segmentation
> Violation (SIGSEGV) @ PC 19d958 SP efffeb20 PSR fe001003 G1 4 o0 2f3a64
>       ::[II_RCP          , 00316040]: Fri Oct 29 09:26:29 1999
> E_DM904A_FATAL_EXCEPTION
> A Fatal Error has occurred in the DMF Facility.
>       ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
> E_CL0F04_LG_BADPARAM
>     Bad input parameter passed to LG routine

>       ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
> E_DM900F_BAD_LOG_EVENT
>   Error waiting for the logging system event:  0x00010071.

>       ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
> E_DM9815_ARCH_SHUTDOWN
>   The Archiver was told to shutdown.
>       ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
> E_CL0F04_LG_BADPARAM
>     Bad input parameter passed to LG routine

>       ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
> E_DM900E_BAD_LOG_END
>     Error trying to end the transaction:  0x0002000B.

>       ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
> E_DM9811_ARCH_LOG_END
>    The Archiver got an error trying to do an LGend call.
>       ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
> E_DM9813_ARCH_CLOSE_LOG
>  The Archiver got an error trying to close the log file.
>       ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
> E_DM9815_ARCH_SHUTDOWN
>   The Archiver was told to shutdown.

>       ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
> E_DM9855_ACP_LG_ACCESS_EXIT
>      Archive processing cannot continue due an error reading information
> from the Logging System. Please check the Archiver Log (II_ACP.LOG)
> for the specific operation which failed and more detailed messages
> describing the error.  Verify that the Ingres Installation is currently
> running. It is possible that failures attempting to read the Ingres
> Log File could be caused by process quota limitations; if so, this
> should be reflected in the error log.  If the cause of the error
> is not apparent, try restarting archive processing via the Ingres
> command 'iiarchive'.  If the same error is encountered, try stopping
> and restarting the Ingres installation.

> logstat

> ======================Fri Oct 29 10:49:30 1999 Logging System
> Summary======================
>     Database add              190        Database removes          176
>     Transaction begins     137587        Transaction ends       137555
>     Log read i/o's             55        Log write i/o's         67586
>     Log writes             502126        Log forces              38365
>     Log waits               41070        Log split waits         16899
>     Log free waits            199        Log stall waits             4
>     Log BCP waits               4        Logfull stall waits         0
>     Log group commit        20920        Log group count         22274
>     Check commit timer      22169        Timer write             19457
>     Inconsistent db             0        Kbytes written         465911
> ----Current log file
> header---------------------------------------------------------------
>     Block size: 8192    Block count: 131292    Buffer count: 12
>     CP interval: 6564   Logfull interval: 124727   Abort interval: 105033
>     Last Transaction Id:    000038106FE00247
>     Begin: <940601276:33061:6920>    CP: <940601276:46211:6488>    End:
> <940601276:47942:1432>
>     Percentage of log file in use: 11
>     Journal Window: <0,0,0>..<0,0,0>
>     Dump Window: <0,0,0>..<0,0,0>
>     Status:         ONLINE,ECPDONE
> ----List of active
> processes--------------------------------------------------------------
>     ID        PID      TYPE    OPEN_DB   WRITE   FORCE    WAIT   BEGIN    
> END

> --------------------------------------------------------------------------
> ------------
>     0001000A  00004378 FCT,SBM        6  441748    1698   32626  100736
> 100722
>     0001000D  00004359 ARCHIV        1       0       0     395       2

> 1
>     00010010  00004355 MASTER        1      46       0     405       1

> 0
>     0001001F  0000441C FCT,SBM        6   60332     584    7644   36848  
> 36833
> ----List of active
> databases-------------------------------------------------------

> iibuild.log

> The number of log buffers in the memory : 12
> The maximum number of transactions in the logging system : 400
> The maximum number of databases in the logging system: 48
> The maximum consistency point interval for invoking archiver : 1
> The block size of the log file : 8 Kbytes
> The log-full-limit in percentage : 95
> The percentage of log file for each consistency point : 5
> The force-abort-limit in percentage : 87
> The size of the lock hash table : 13001
> The size of the resource hash table : 13001
> The maximum number of locks in the locking system : 65000
> The maximum number of lock lists in the locking system : 400
> The maximum number of locks allowed per transaction : 800

> ____________________________________________________________________
> Get free email and a permanent address at http://www.netaddress.com/?N=1

_________________________________________________________________________
CAUTION - This message may contain privileged and confidential
information intended only for the use of the addressee named above.
If you are not the intended recipient of this message you are hereby
notified that any use, dissemination, distribution or reproduction of
this message is prohibited. If you have received this message in error
please notify Yarra Valley Water immediately. Any views expressed in
this message are those of the individual sender and may not necessarily
reflect the views of Yarra Valley Water.
__________________________________________________________________________

 
 
 

Ingres Resource Deadlock

Post by Kent Smi » Fri, 19 Nov 1999 04:00:00


When I upgraded from 6.4/06 to 6.4/07 under Solarin 2.6 I had some
severe problems running the Prophecy bill printing program.  The batch
job would run for a while then crash without explanation.  After a bit
of digging, it became clear that Ingres was not escalating locks
properly.  I watched the process in IPM and determined which tables
were being used, then set ING_SET to include a SET LOCKMODE statement
that set the level to exclusive for those tables.  Then I ended up
with a 7 line lock list and everything ran fine.

I don't know if this is the same problem, but it was *a* problem.

--Kent Smith
  IPSO Incorporated
  Business * Technology * Solutions
  ksm...@ipsoinc.com

On 12 Nov 1999 00:56:18 -0600, sr...@yvw.com.au (Reid, Steve) wrote:

>F.Y.I.,
>            We are running the same release 6.4/07
>    on Solaris 2.6 running Prophecy Billing Suite also
>    We have crashed twice in the last 2 days also.
>    Any info would be helpful.

>Regards

>Steve Reid.

>> -----Original Message-----
>> From:  Jon Nagome [SMTP:jon_nag...@usa.net]
>> Sent:  Friday, 12 November 1999 15:51
>> To:    info-ing...@ams.org
>> Subject:       Ingres Resource Deadlock

>> I'm having problems with the resource deadlock issue with my ingres 6.4/07
>> installation on the E3500 machine, I'm running Prophecy Billing Suite.
>> The
>> ingres engine keeps shutting down by itself when it hit the resource
>> deadlock
>> issue.  Below is the errlog.log and the current parameters of the dbms.. i
>> really hope anybody can help me with a correct settings of the dbms
>> parameters
>> or anything that could resolve the problem.  Thank you very much...i would
>> really appreciated it.

>> Regards,
>> Jon Nagome

>> errlog.log

>>       ::[36841           , 00836040]: Fri Oct 29 08:52:53 1999
>> E_DM9043_LOCK_TIMEOUT
>>    Timeout occurred during lock request on table TABLE_ID (2749,0)
>> in database polydb with mode 2.

>>       ::[36841           , 0056E4E0]: Fri Oct 29 08:52:53 1999
>> E_DM9043_LOCK_TIMEOUT
>>    Timeout occurred during lock request on table TABLE_ID (2749,0)
>> in database polydb                  with mode 2.

>>       ::[36841           , 00AB2880]: Fri Oct 29 08:53:08 1999
>> E_DM9043_LOCK_TIMEOUT
>>    Timeout occurred during lock request on table TABLE_ID (2749,0)
>> in database polydb                   with mode 2.

>>       ::[36841           , 00EB9EC0]: Fri Oct 29 08:53:10 1999
>> E_DM9043_LOCK_TIMEOUT
>>    Timeout occurred during lock request on table TABLE_ID (2749,0)
>> in database polydb                   with mode 2.

>>       ::[36841           , 00F0B1C0]: Fri Oct 29 08:53:30 1999
>> E_DM9043_LOCK_TIMEOUT
>>    Timeout occurred during lock request on table TABLE_ID (2749,0)
>> in database polydb                   with mode 2.

>>       ::[36841           , 01317800]: Fri Oct 29 09:11:18 1999
>> E_CLFE06_BS_WRITE_ERR
>>    Write to peer process failed; it may have exited.

>>       ::[36839           , 00ED5080]: Fri Oct 29 09:15:03 1999
>> E_CLFE06_BS_WRITE_ERR
>>    Write to peer process failed; it may have exited.

>>       ::[36841           , 00F85520]: Fri Oct 29 09:22:48 1999
>> E_CLFE07_BS_READ_ERR
>>     Read from peer process failed; it may have exited.

>>       ::[36841           , 00F85520]: Fri Oct 29 09:22:48 1999
>> E_SC022F_BAD_GCA_READ
>>    SCF was unable to read a GCF block.
>>       ::[36841           , 00E28A40]: Fri Oct 29 09:26:21 1999
>> E_DM9044_ESCALATE_DEADLOCK
>>       Deadlock encountered while escalating to table level locking
>> on table bitsessround             in database polydb with mode 5.

>>       ::[36841           , 00E28A40]: Fri Oct 29 09:26:21 1999
>> E_DM0042_DEADLOCK        Resource deadlock.
>>       ::[36841           , 00E28A40]: Fri Oct 29 09:26:21 1999
>> E_QE002A_DEADLOCK        Deadlock detected.
>>       ::[36841           , 00E28A40]: Fri Oct 29 09:26:27 1999
>> E_CL1005_LK_NOLOCKS      Out of lock resources

>>       ::[36841           , 00E28A40]: Fri Oct 29 09:26:27 1999
>> E_DM004B_LOCK_QUOTA_EXCEEDED     Lock quota exceeded.
>>       ::[II_RCP          , 00316040]: DMF EXCEPTION: Segmentation
>> Violation (SIGSEGV) @ PC 19d958 SP efffeb20 PSR fe001003 G1 4 o0 2f3a64
>>       ::[II_RCP          , 00316040]: Fri Oct 29 09:26:29 1999
>> E_DM904A_FATAL_EXCEPTION
>> A Fatal Error has occurred in the DMF Facility.
>>       ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
>> E_CL0F04_LG_BADPARAM
>>     Bad input parameter passed to LG routine

>>       ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
>> E_DM900F_BAD_LOG_EVENT
>>   Error waiting for the logging system event:  0x00010071.

>>       ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
>> E_DM9815_ARCH_SHUTDOWN
>>   The Archiver was told to shutdown.
>>       ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
>> E_CL0F04_LG_BADPARAM
>>     Bad input parameter passed to LG routine

>>       ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
>> E_DM900E_BAD_LOG_END
>>     Error trying to end the transaction:  0x0002000B.

>>       ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
>> E_DM9811_ARCH_LOG_END
>>    The Archiver got an error trying to do an LGend call.
>>       ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
>> E_DM9813_ARCH_CLOSE_LOG
>>  The Archiver got an error trying to close the log file.
>>       ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
>> E_DM9815_ARCH_SHUTDOWN
>>   The Archiver was told to shutdown.

>>       ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
>> E_DM9855_ACP_LG_ACCESS_EXIT
>>      Archive processing cannot continue due an error reading information
>> from the Logging System. Please check the Archiver Log (II_ACP.LOG)
>> for the specific operation which failed and more detailed messages
>> describing the error.  Verify that the Ingres Installation is currently
>> running. It is possible that failures attempting to read the Ingres
>> Log File could be caused by process quota limitations; if so, this
>> should be reflected in the error log.  If the cause of the error
>> is not apparent, try restarting archive processing via the Ingres
>> command 'iiarchive'.  If the same error is encountered, try stopping
>> and restarting the Ingres installation.

>> logstat

>> ======================Fri Oct 29 10:49:30 1999 Logging System
>> Summary======================
>>     Database add              190        Database removes          176
>>     Transaction begins     137587        Transaction ends       137555
>>     Log read i/o's             55        Log write i/o's         67586
>>     Log writes             502126        Log forces              38365
>>     Log waits               41070        Log split waits         16899
>>     Log free waits            199        Log stall waits             4
>>     Log BCP waits               4        Logfull stall waits         0
>>     Log group commit        20920        Log group count         22274
>>     Check commit timer      22169        Timer write             19457
>>     Inconsistent db             0        Kbytes written         465911
>> ----Current log file
>> header---------------------------------------------------------------
>>     Block size: 8192    Block count: 131292    Buffer count: 12
>>     CP interval: 6564   Logfull interval: 124727   Abort interval: 105033
>>     Last Transaction Id:    000038106FE00247
>>     Begin: <940601276:33061:6920>    CP: <940601276:46211:6488>    End:
>> <940601276:47942:1432>
>>     Percentage of log file in use: 11
>>     Journal Window: <0,0,0>..<0,0,0>
>>     Dump Window: <0,0,0>..<0,0,0>
>>     Status:         ONLINE,ECPDONE
>> ----List of active
>> processes--------------------------------------------------------------
>>     ID        PID      TYPE    OPEN_DB   WRITE   FORCE    WAIT   BEGIN    
>> END

>> --------------------------------------------------------------------------
>> ------------
>>     0001000A  00004378 FCT,SBM        6  441748    1698   32626  100736
>> 100722
>>     0001000D  00004359 ARCHIV        1       0       0     395       2

>> 1
>>     00010010  00004355 MASTER        1      46       0     405       1

>> 0
>>     0001001F  0000441C FCT,SBM        6   60332     584    7644   36848  
>> 36833
>> ----List of active
>> databases-------------------------------------------------------

>> iibuild.log

>> The number of log buffers in the memory : 12
>> The maximum number of transactions in the logging system : 400
>> The maximum number of databases in the logging system: 48
>> The maximum consistency point interval for invoking archiver : 1
>> The block size of the log file : 8 Kbytes
>> The log-full-limit in percentage : 95
>> The percentage of log file for each consistency point : 5
>> The force-abort-limit in percentage : 87
>> The size of the lock hash table : 13001
>> The size of the resource hash table : 13001
>> The maximum number of locks in the locking system : 65000
>> The maximum number of lock lists in the locking system : 400
>> The maximum number of locks allowed per transaction : 800

>> ____________________________________________________________________
>> Get free email and a permanent address at http://www.netaddress.com/?N=1
>_________________________________________________________________________
>CAUTION - This message may contain privileged and confidential
>information intended only for the use of the addressee named above.
>If you are not the intended recipient of this message you are hereby
>notified that any use, dissemination, distribution or reproduction of
>this message is prohibited. If you have received this message in error
>please notify Yarra Valley Water immediately. Any views expressed in
>this message are those of the individual sender and may not necessarily
>reflect the views of Yarra Valley Water.

...

read more »

 
 
 

Ingres Resource Deadlock

Post by Beavis, Richard non Unis » Fri, 19 Nov 1999 04:00:00


Kent,
We have had a similar problem here on 6.4/07. The solution recommended by CA
came in 2 parts :-

"After studying and researching your errlog, I think that this may a
complication of Bug 96165 - which relates to lock escalations. As a possible
workaround please add the following lines to rundbms.opt and restart the
servers.
-dmf.log_esc_lpr_sc  on
-dmf.log_esc_lpr_ut  on
-dmf.log_esc_lpt_sc  on
-dmf.log_esc_lpt_ut  on
This causes more detailed lock escalation messages to be written to the
errlog but it should also avoid the bug."

In the long run, move to 6.4/07 (su4.us5/01) - otherwise known as GenLevel
649901.

We did the first step and it reduced the problem - but the users still
complained about the intermittent crashes - users have little sense of
humour!! Since we applied the upgrade about a month ago, there have been no
further incidents in any of our 6 production installations.

Cheers
Richard Beavis

-----Original Message-----
From: i...@sprynet.com [mailto:i...@sprynet.com]
Sent: Friday, 19 November 1999 8:29
To: info-ing...@ams.org
Subject: Re: Ingres Resource Deadlock

When I upgraded from 6.4/06 to 6.4/07 under Solarin 2.6 I had some
severe problems running the Prophecy bill printing program.  The batch
job would run for a while then crash without explanation.  After a bit
of digging, it became clear that Ingres was not escalating locks
properly.  I watched the process in IPM and determined which tables
were being used, then set ING_SET to include a SET LOCKMODE statement
that set the level to exclusive for those tables.  Then I ended up
with a 7 line lock list and everything ran fine.

I don't know if this is the same problem, but it was *a* problem.

--Kent Smith
  IPSO Incorporated
  Business * Technology * Solutions
  ksm...@ipsoinc.com

On 12 Nov 1999 00:56:18 -0600, sr...@yvw.com.au (Reid, Steve) wrote:

>F.Y.I.,
>            We are running the same release 6.4/07
>    on Solaris 2.6 running Prophecy Billing Suite also
>    We have crashed twice in the last 2 days also.
>    Any info would be helpful.

>Regards

>Steve Reid.

>> -----Original Message-----
>> From:  Jon Nagome [SMTP:jon_nag...@usa.net]
>> Sent:  Friday, 12 November 1999 15:51
>> To:    info-ing...@ams.org
>> Subject:       Ingres Resource Deadlock

>> I'm having problems with the resource deadlock issue with my ingres
6.4/07
>> installation on the E3500 machine, I'm running Prophecy Billing Suite.
>> The
>> ingres engine keeps shutting down by itself when it hit the resource
>> deadlock
>> issue.  Below is the errlog.log and the current parameters of the dbms..
i
>> really hope anybody can help me with a correct settings of the dbms
>> parameters
>> or anything that could resolve the problem.  Thank you very much...i
would
>> really appreciated it.

>> Regards,
>> Jon Nagome

>> errlog.log

>>       ::[36841           , 00836040]: Fri Oct 29 08:52:53 1999
>> E_DM9043_LOCK_TIMEOUT
>>    Timeout occurred during lock request on table TABLE_ID (2749,0)
>> in database polydb with mode 2.

>>       ::[36841           , 0056E4E0]: Fri Oct 29 08:52:53 1999
>> E_DM9043_LOCK_TIMEOUT
>>    Timeout occurred during lock request on table TABLE_ID (2749,0)
>> in database polydb                  with mode 2.

>>       ::[36841           , 00AB2880]: Fri Oct 29 08:53:08 1999
>> E_DM9043_LOCK_TIMEOUT
>>    Timeout occurred during lock request on table TABLE_ID (2749,0)
>> in database polydb                   with mode 2.

>>       ::[36841           , 00EB9EC0]: Fri Oct 29 08:53:10 1999
>> E_DM9043_LOCK_TIMEOUT
>>    Timeout occurred during lock request on table TABLE_ID (2749,0)
>> in database polydb                   with mode 2.

>>       ::[36841           , 00F0B1C0]: Fri Oct 29 08:53:30 1999
>> E_DM9043_LOCK_TIMEOUT
>>    Timeout occurred during lock request on table TABLE_ID (2749,0)
>> in database polydb                   with mode 2.

>>       ::[36841           , 01317800]: Fri Oct 29 09:11:18 1999
>> E_CLFE06_BS_WRITE_ERR
>>    Write to peer process failed; it may have exited.

>>       ::[36839           , 00ED5080]: Fri Oct 29 09:15:03 1999
>> E_CLFE06_BS_WRITE_ERR
>>    Write to peer process failed; it may have exited.

>>       ::[36841           , 00F85520]: Fri Oct 29 09:22:48 1999
>> E_CLFE07_BS_READ_ERR
>>     Read from peer process failed; it may have exited.

>>       ::[36841           , 00F85520]: Fri Oct 29 09:22:48 1999
>> E_SC022F_BAD_GCA_READ
>>    SCF was unable to read a GCF block.
>>       ::[36841           , 00E28A40]: Fri Oct 29 09:26:21 1999
>> E_DM9044_ESCALATE_DEADLOCK
>>       Deadlock encountered while escalating to table level locking
>> on table bitsessround             in database polydb with mode 5.

>>       ::[36841           , 00E28A40]: Fri Oct 29 09:26:21 1999
>> E_DM0042_DEADLOCK        Resource deadlock.
>>       ::[36841           , 00E28A40]: Fri Oct 29 09:26:21 1999
>> E_QE002A_DEADLOCK        Deadlock detected.
>>       ::[36841           , 00E28A40]: Fri Oct 29 09:26:27 1999
>> E_CL1005_LK_NOLOCKS      Out of lock resources

>>       ::[36841           , 00E28A40]: Fri Oct 29 09:26:27 1999
>> E_DM004B_LOCK_QUOTA_EXCEEDED     Lock quota exceeded.
>>       ::[II_RCP          , 00316040]: DMF EXCEPTION: Segmentation
>> Violation (SIGSEGV) @ PC 19d958 SP efffeb20 PSR fe001003 G1 4 o0 2f3a64
>>       ::[II_RCP          , 00316040]: Fri Oct 29 09:26:29 1999
>> E_DM904A_FATAL_EXCEPTION
>> A Fatal Error has occurred in the DMF Facility.
>>       ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
>> E_CL0F04_LG_BADPARAM
>>     Bad input parameter passed to LG routine

>>       ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
>> E_DM900F_BAD_LOG_EVENT
>>   Error waiting for the logging system event:  0x00010071.

>>       ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
>> E_DM9815_ARCH_SHUTDOWN
>>   The Archiver was told to shutdown.
>>       ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
>> E_CL0F04_LG_BADPARAM
>>     Bad input parameter passed to LG routine

>>       ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
>> E_DM900E_BAD_LOG_END
>>     Error trying to end the transaction:  0x0002000B.

>>       ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
>> E_DM9811_ARCH_LOG_END
>>    The Archiver got an error trying to do an LGend call.
>>       ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
>> E_DM9813_ARCH_CLOSE_LOG
>>  The Archiver got an error trying to close the log file.
>>       ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
>> E_DM9815_ARCH_SHUTDOWN
>>   The Archiver was told to shutdown.

>>       ::[II_ACP          , 00312040]: Fri Oct 29 09:26:29 1999
>> E_DM9855_ACP_LG_ACCESS_EXIT
>>      Archive processing cannot continue due an error reading information
>> from the Logging System. Please check the Archiver Log (II_ACP.LOG)
>> for the specific operation which failed and more detailed messages
>> describing the error.  Verify that the Ingres Installation is currently
>> running. It is possible that failures attempting to read the Ingres
>> Log File could be caused by process quota limitations; if so, this
>> should be reflected in the error log.  If the cause of the error
>> is not apparent, try restarting archive processing via the Ingres
>> command 'iiarchive'.  If the same error is encountered, try stopping
>> and restarting the Ingres installation.

>> logstat

>> ======================Fri Oct 29 10:49:30 1999 Logging System
>> Summary======================
>>     Database add              190        Database removes          176
>>     Transaction begins     137587        Transaction ends       137555
>>     Log read i/o's             55        Log write i/o's         67586
>>     Log writes             502126        Log forces              38365
>>     Log waits               41070        Log split waits         16899
>>     Log free waits            199        Log stall waits             4
>>     Log BCP waits               4        Logfull stall waits         0
>>     Log group commit        20920        Log group count         22274
>>     Check commit timer      22169        Timer write             19457
>>     Inconsistent db             0        Kbytes written         465911
>> ----Current log file
>> header---------------------------------------------------------------
>>     Block size: 8192    Block count: 131292    Buffer count: 12
>>     CP interval: 6564   Logfull interval: 124727   Abort interval: 105033
>>     Last Transaction Id:    000038106FE00247
>>     Begin: <940601276:33061:6920>    CP: <940601276:46211:6488>    End:
>> <940601276:47942:1432>
>>     Percentage of log file in use: 11
>>     Journal Window: <0,0,0>..<0,0,0>
>>     Dump Window: <0,0,0>..<0,0,0>
>>     Status:         ONLINE,ECPDONE
>> ----List of active
>> processes--------------------------------------------------------------
>>     ID        PID      TYPE    OPEN_DB   WRITE   FORCE    WAIT   BEGIN

>> END

--------------------------------------------------------------------------
>> ------------
>>     0001000A  00004378 FCT,SBM        6  441748    1698   32626  100736
>> 100722
>>     0001000D  00004359 ARCHIV        1       0       0     395       2

>> 1
>>     00010010  00004355 MASTER        1      46       0     405       1

>> 0
>>     0001001F  0000441C FCT,SBM        6   60332     584    7644   36848  
>> 36833
>> ----List of active
>> databases-------------------------------------------------------

>> iibuild.log

>> The number of log buffers in the memory : 12
>> The maximum number of transactions in the logging system : 400
>> The maximum number of databases in the logging system: 48
>> The maximum consistency point interval for invoking archiver : 1
>> The block size of the log file : 8 Kbytes
>> The log-full-limit in percentage : 95
>> The percentage of log file for each consistency point : 5
>> The

...

read more »

 
 
 

1. Deadlock on Thread | Communication buffer resources

Running SQL Server 2000, I'm periodically getting this error executing a select
statement that joins 5 tables.  

"Error","TID=200","06/21/02","16:54:10","ODBC Error Code = 40001 (Serialization
failure)<P> [Microsoft][ODBC SQL Server Driver][SQL Server]Transaction (Process
ID 55) was deadlocked on thread | communication buffer resources with another
process and has been chosen as the deadlock victim. Rerun the transaction.

Since this is a select only, I don't quite understand how there could be
deadlock issues.

I've searched Microsoft and other sites and don't see a lot of discussion about
deadlocks on thread | communication buffer resources.

Any help would be greatly appreciated.

Doug

2. Help needed in setting up a network printer in d3/linux

3. Help: Oralce on Unix ORA 00060: deadlock detected while waiting for resource

4. sybase

5. Resource deadlock problems

6. ANSI/ISO SQL1998 specifications document - Must read this!!

7. Resource Deadlock

8. Help needed( ingres error 2173..related to deadlocks?)

9. ingres deadlock error

10. Solaris Resource Manager and Ingres

11. Ingres Resources

12. New INGRES Related Links Resource