• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1341
  • Last Modified:

SQL0913 - Row or object CCMPBDIH in COMPANYDAT10 type *FILE in use

I am getting this error when I am trying to add a record to a table thru Microsoft Query to iSeries.
Insert into COMPANYDAT10.CCMPBDIH (CHCMPN, CHCMPS, CHCO, CHSLWH, CHBTCN, CHRSCD, CHACDT, CHPON, CHSON) Values ('AD-0036-2008','A','572','81919','819839','MM','20090513','3432','234532')

Open in new window

0
muralibmk
Asked:
muralibmk
1 Solution
 
Gary PattersonVP Technology / Senior Consultant Commented:
A good place to start is always the extended message description.  On the AS/400, use the DSPMSGD command (SQL messages are stored in message file QSQLMSG).

                         Display Formatted Message Text                        
                                                                 
 Message ID . . . . . . . . . :   SQL0913                                      
 Message file . . . . . . . . :   QSQLMSG                                      
   Library  . . . . . . . . . :     QSYS                                      
                                                                               
 Message . . . . :   Row or object &1 in &2 type *&3 in use.
                   
 Cause . . . . . :   The requested object &1 in &2 type *&3 is either in use by
   another application process or a row in the object is in use by either      
   another application process or another cursor in this application process.  

 Recovery  . . . :   Look at the previously listed messages in the job log    
   (DSPJOBLOG command) or from interactive SQL press F10 (Display messages in  
   job log) on this display to determine if this is an object or record lock  
   wait time out.                                                              
     Do one of the following:                                                  
     -- If the object is locked by another application process, try the        
   Structured Query Language (SQL) statement again when the object is not in  
   use. Use the Work with Object Locks (WRKOBJLCK) command to determine who is
   currently using the object.                                                
     -- If the object is a schema and an attempt was made to create a table,  
   view, or index into this schema under commitment control, a                
   save-while-active operation may be in progress on the same schema by another
   job in the system. Try the request again when the save-while-active        
   processing is complete.                                                    
     -- If a record is locked by another application process, try the SQL      
   statement again when the record is not in use.  The Display Record Locks    
   (DSPRCDLCK) command will determine who is currently using the record.      
     -- If this is a record lock held by another cursor in the same application
   process, you must issue a COMMIT, ROLLBACK, or another FETCH statement on  
   the cursor that is holding the lock before issuing this SQL statement.      
     If this error occurs frequently, use the Change Physical File (CHGPF),    
   Change Logical File (CHGLF), or Override Data Base File (OVRDBF) command to
   change the object or record wait time out.

- Gary Patterson
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now