search cancel

Chorus DBID table full message

book

Article ID: 237798

calendar_today

Updated On:

Products

CHORUS SOFTWARE MANAGER

Issue/Introduction

Applying maintenance through Chorus gives the warning message

A database error has occurred. Consult the CSM logs for further information.
Error message: PreparedStatementCallback; SQL [insert into filteritem (filter_id, item)values (?, ?)]; ca.datacom.db.DBSQLException: ca.datacom.db.DBSQLException: TABLE FULL - DBID=4000 INTERNAL NAME FII in Session(Exception executeImmediate)in Query(execparameterized); nested exception is java.sql.SQLException: ca.datacom.db.DBSQLException: ca.datacom.db.DBSQLException: TABLE FULL - DBID=4000 INTERNAL NAME FII in Session(Exception executeImmediate)in Query(execparameterized) 

Cause

The disk holding the CSM database tables is out of space

Environment

Release : 6.0

Component : Chorus Software Manager

Resolution

Enlarge CSM DB table
 
Follow the instructions on this page of the manual:
 
In STEP 2 of the manual change some SYSIN in backup  job CSMBK4K

// SYSIN DD*
 COMM OPTION=STATS                                  
 COMM OPTION=CLOSE,DBID=4000    
 ACCESS STATUS=UTLTY,DBID=4000,USERS=FAIL                     
 BACKUP DBID=4000,DDNAME=DB4000BK,SEQ=NAT 
/*
 
In STEP 3 please run the DBUTILTY with the control statement :

  REPORT AREA=CXX,DBID=4000,TYPE=A   
 
In this sample it shows the INV file ran out of space,
 Or isn’t able to add more extends to the datasets because the volume it’s allocated on is full..
 
0DATACOM/AD                   DATA AREA SPACE UTILIZATION REPORT                                                                    
-AREA DATA       TOTAL           TOTAL       TOTAL       USED    PERCENT    PARTIALLY  AREA REUSE
 NAME BASE      TRACKS         RECORDS      BLOCKS      BLOCKS  FULL   MAX  EMPTY BLKS    OPTION
                                                                                                                                    
0CXX               525           N/A         6,300         398     6     6         N/A  N/A  
0IXX  4000       1,800           N/A        21,600       8,189    37    37         N/A  N/A
  AUD 4000       7,500           6,419      15,000         129     0     0           4  RANDOM
  INV 4000      10,500         793,297      63,000      63,000   100   100           0  RANDOM
  JNL 4000       1,800         104,702      10,800       6,802    62    62          10  RANDOM
  PCY 4000         525           1,906       6,300         145     2     2          39  RANDOM 
  SCS 4000       1,950           4,241      11,700          68     0     1          34  RANDOM
  SDS 4000       2,700           8,520      16,200       1,642    10    10          11  RANDOM
  SRG 4000         900             771       5,400          98     1     1           1  RANDOM 
  XML 4000      13,500          20,342      27,000      20,908    77    77           1  RANDOM                                     
 
And in the CSMMUF joblog it says:

 08.14.39 STC20614  MSMMUF:DB01705I - DYNAMIC EXTEND START INV4000 TRK 10,500                                       SYS2.CSM60.INV4000
 08.14.39 STC20614  IEC030I B37-04,IFG0554A,MSMMUF,MSMMUF,INV4000,2949,DSK300,0427041D,  909
    909             SYS2.CSM60.INV4000
 
In STEP 4 of the manual..
Instead of deleting the current DB index or Area dataset, rename the current INV4000 data set to <dataset name>.OLD and allocate a new INV4000 data set with the same dsn as before , with larger primary allocation and secondary allocation space.
Use below JCL as sample. Change the table name and dataset name

//*                                   
//ALCCSM  EXEC PGM=IEFBR14              
//*                                     
//*       ALLOCATE CSM DATABASE DATASETS
//*                                           
//INV4000  DD DSN=SYS2.CSM60.INV4000,  
//         SPACE=(CYL,(600,100)),               
//         UNIT=&AXUNI1,                        
//         DSNTYPE=BASIC,                       
//         &VOL1,                               
//         DISP=(NEW,CATLG,DELETE)  
            
In STEP 5 of the manual, the restore job CSMLD4K.
Use these statements as input for the STEP01 SYSIN:
 
//SYSIN DD *
  INIT DBID=4000,AREA=IXX  
  INIT AREA=INV,DBID=4000 
  LOAD DBID=4000,FORMAT=BACKUP,DDNAME=DB4000BK,SORT=10000,SORTDFLT=YES 
  ACCESS STATUS=WRITE,DBID=4000
/*
 
And leave the STEP02 and STEP03 in the job as is…