Guest

Preview Tool

Cisco Bug: CSCuq46674 - Logs of Sysagent task fill up DynDb DBSpace and are never cleaned up

Last Modified

May 03, 2018

Products (1)

  • Cisco Unity Connection

Known Affected Releases

10.5(1)ES41

Description (partial)

The logs of sysagent tasks containing reports and failure or success reasons are never cleaned up from the DynDB tables causing an outrageous number of rows to deposit over a period of time. This figure can be so overwhelming that it can certainly consume the entire DynDb space and pose a threat to the normal functioning of Unity Connection. Below is an example of such scenario :


admin:  run cuc dbquery unitydyndb select * from vw_tableinformation order by actualrowcount

name                                                    actualrowcount  estimatedrowcount  pagesused  pagesallocated  pagesunused  dbspacepagesfree  totalpagesavailable  dbspace
----------------------                           --------------  -----------------  ---------  --------------  -----------  ----------------  -------------------  -------
tbl_taskparameter                          3675489         3675463.0          229008     229065          57           3                 60                   dyn
tbl_taskalert                                      1848780         1848728.0          462007     467414          5407         3                 5410                 dyn
tbl_objectchange                            923358          921829.0           92344      92424           80           3                 83                   dyn
tbl_feederobjectchange              297881          297630.0           20337      23465           3128         3                 3131                 dyn
tbl_taskresult                                    26734           25242.0            1910       1911            1            3                 4                    dyn

Majorly Affected Tables :
tbl_taskparameter                         
tbl_taskalert                                     
tbl_taskresult

There could be other tables in the Dynamic database that need attention too for an efficient data storage mechanism.

Symptom:
Error reported in DIGINET ( DIGITAL REPLICATION )
07:21:29.688 |20297,NodeChangeReplicator,,-1,-1,Database unitydyndb access error: Error executing csp_ObjectChangeStamp. ({ call csp_ObjectChangeStampUSN (pObjectId=?, pUsn=?)}, pObjectId=4b2256fc-9ecb-42d2-9c21-60f110fab265, pUsn=1096095 4b2256fc-9ecb-42d2-9c21-60f110fab265, 1096095). TECHNICAL DETAILS: java.sql.SQLException: Could not update a row in the table.

Sql Errors while updating or inserting a row in Dyndb Database :
SQLCODE -346 in EXECUTE:                                                                                                  
IX000: Could not update a row in the table. ()                                                                            
IX000: ISAM error: no free disk space ()

Maxed out DynDB space
address  chunk/dbs     offset     size       free       bpages     flags pathname                                            
57c00988 1      1      0          200000     140875                PO-B-- /var/opt/cisco/connection/db/root_dbspace          
59819a28 2      2      0          1408000    1217946    1217947    POSB-- /var/opt/cisco/connection/db/cuc_er_sbspace        
                         Metadata 190000     167504     190000                                                               
59819c10 3      3      0          128000     122716                PO-B-- /var/opt/cisco/connection/db/cuc_er_dbspace        
59819df8 4      4      0          307200     0                     PO-B-- /var/opt/cisco/connection/db/phys_dbs              
5981a018 5      5      0          1792000    1449432               PO-B-- /var/opt/cisco/connection/db/rpt_dbs               
5981a200 6      6      0          512000     511597                PO-B-- /var/opt/cisco/connection/db/temp2_dbs             
5981a3e8 7      7      0          1268000    3                     PO-B-- /var/opt/cisco/connection/db/dyn_dbs               
5981a5d0 8      8      0          128000     96963                 PO-B-- /usr/local/cm/db/informix/data/mbx_dbs             
5981a7b8 9      9      0          44800      32894                 PO-B-- /var/opt/cisco/connection/db/dir16_dbs             
5981a9a0 10     10     0          327733     0                     PO-B-- /var/opt/cisco/connection/db/log_dbs               
5981ab88 11     11     0          512000     511597                PO-B-- /var/opt/cisco/connection/db/temp_dbs              
5981ad70 12     12     0          64000      46724                 PO-B-- /usr/local/cm/db/informix/data/mbx16_dbs           
5981b018 13     13     0          2804000    1736075               PO-B-- /var/opt/cisco/connection/db/dir_dbs               
5981b200 14     14     0          51200      46421                 PO-B-- /var/opt/cisco/connection/db/sadmin_dbs            
5981b3e8 15     15     0          491520     458363     458363     POSB-- /var/opt/cisco/connection/db/ciscounity_sbspacetemp
                         Metadata 33104      24633      33104                                                                
5981b5d0 16     16     0          10000      9250       9250       POSB-- /var/opt/cisco/connection/db/ciscounity_sbspace    
                         Metadata 697        518        697                                                                  
 16 active, 32766 maximum

Conditions:
Too many rows of logs from sysagent tasks over time can cause this issue . It is seen that the rows in the tables go past 37 Million in some cases.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.