Topic
  • 1 reply
  • Latest Post - ‏2010-07-09T13:23:37Z by SystemAdmin
NareshKKhurana
NareshKKhurana
3 Posts

Pinned topic Problem with DB schedular

‏2010-05-06T05:50:43Z |
I am facing the following error in Message log file. we have schedule some task via db scheduler.

06:42:28 SCHAPI: thread dbWorker2 task post_alarm_message(15-16900541) shutting down
06:42:29 Logical Log 8849233 Complete, timestamp: 0x362bc4d8.
06:42:29 SCHAPI: Re-starting 1 dbWorker threads.
06:42:29 SCHAPI: Started 1 dbWorker threads.
06:42:29 SCHAPI: Error -271 Could not insert new row into the table.
06:42:29 SCHAPI: Type: TASK, Name: post_alarm_message, Location: NULL.
06:42:29 SCHAPI: Error -136 ISAM error: no more extents
06:42:29 SCHAPI: Type: TASK, Name: post_alarm_message, Location: NULL.
06:42:29 SCHAPI: Type: TASK, Name: post_alarm_message, Error Message: Unable to execute function http:// ph_dbs_alert(integer,integer,informix.pointer ) .
06:42:29 SCHAPI: thread dbWorker1 task post_alarm_message(15-16900542) shutting down
06:42:30 SCHAPI: Re-starting 1 dbWorker threads.
06:42:30 SCHAPI: Started 1 dbWorker threads.
06:42:30 Logical Log 8849234 - Backup Started
06:42:30 Logical Log 8849234 - Backup Completed
06:42:30 SCHAPI: Error -271 Could not insert new row into the table.
06:42:30 SCHAPI: Type: TASK, Name: post_alarm_message, Location: NULL.
06:42:30 SCHAPI: Error -136 ISAM error: no more extents
06:42:30 SCHAPI: Type: TASK, Name: post_alarm_message, Location: NULL.
06:42:30 SCHAPI: Type: TASK, Name: post_alarm_message, Error Message: Unable to execute function http:// ph_dbs_alert(integer,integer,informix.pointer ) .
06:42:30 SCHAPI: thread dbWorker1 task post_alarm_message(15-16900543) shutting down

Kindly do the needful.
Updated on 2010-07-09T13:23:37Z at 2010-07-09T13:23:37Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    228 Posts

    Re: Problem with DB schedular

    ‏2010-07-09T13:23:37Z  
    It seems that engine is unable to add a new row into table on task execution because there is no space left. Here is finderr output:

    
    -136      ISAM error: no more extents.   The database server needs to add an extent to a table but cannot 
    
    do so. Either not enough disk space is available in the dbspace, or the table has been given the maximum number of extents that is allowed, or the maximum number of pages has been reached. The database server administrator can determine the cause as follows:   1.  Determine the tblspace number 
    
    for the table. It is the value in the partnum column of the systables table 
    
    for 
    
    this table.   2.  Convert the tblspace number to hexadecimal and extract its most-significant 2 digits (the high-order 
    
    byte). This chunk number indicates where the table resides.   3.  Use the onstat utility -t option to find out disk usage 
    
    for 
    
    this table. Note particularly the values reported 
    
    for npages (disk pages available), nused (disk pages used), and nextns (number of extents).   If nused is less than npages, and nextns is large, the table may have too many extents. The upper limit of extents per table depends on the page size of the dbspace it is in, as well as how much space is consumed by other entries on its tblspace page. An estimate of the maximum allowed number of extents is the page size in bytes, minus 150 bytes of overhead, divided by eight. Thus a table in a 2K page size dbspace is limited to roughly (2,048 - 150) / 8 = 237 extents, but the actual limit may be lower 
    
    if other entries on its tblspace page reduce the space available 
    
    for extent entries. Larger page sizes allow correspondingly higher numbers of extents.