RTC Checkin a large files result into CRJAZ0265E The database resource or the virtual storage is not available
You're trying to attach a large SINGLE file (about 800 MBs) to RTC SCM and it fails due to size of the file. Attaching a small file works.
The error message in the RTC log (either ccm or jazz depends on the root context)
The question, how do you prevent this is from happening so that can attach a large file?
2016-07-26 13:54:54,118 [WebContainer : 8 @@ 13:53 nattu@nomail.com <Mozilla/5.0 (Windows NT 6.1; WOW64; rv:47.0) Gecko/20100101 Firefox/47.0@172.17.45.64> /ccm/service/com.ibm.team.filesystem.service.internal.rest.IFilesystemContentService] ERROR sqlExceptionLogger - CRJAZ1318E The server could not connect to the database. Try the operation again. CRJAZ0265E The database resource or the virtual storage is not available. SQL: INSERT INTO SCM.CONTENT(HASH_CODE, SEQUENCE_COL, STORED_SIZE, EXPANDED_SIZE, STORAGE_METHOD, DELTA_PREDECESSOR, DELETED, CONTENT_BYTES) VALUES (?, ?, ?, ?, ?, ?, ?, ?) SQL Exception #1 SQL Message: DB2 SQL Error: SQLCODE=-964, SQLSTATE=57011, SQLERRMC=null, DRIVER=4.17.28 SQL State: 57011 Error Code: -964 com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-964, SQLSTATE=57011, SQLERRMC=null, DRIVER=4.17.28 at com.ibm.db2.jcc.am.fd.a(fd.java:752) at com.ibm.db2.jcc.am.fd.a(fd.java:66) at com.ibm.db2.jcc.am.fd.a(fd.java:135) at com.ibm.db2.jcc.am.uo.b(uo.java:2422) at com.ibm.db2.jcc.am.uo.c(uo.java:2405) at com.ibm.db2.jcc.t4.ab.l(ab.java:408) at com.ibm.db2.jcc.t4.ab.a(ab.java:62) at com.ibm.db2.jcc.t4.o.a(o.java:50) at com.ibm.db2.jcc.t4.ub.b(ub.java:220) at com.ibm.db2.jcc.am.vo.sc(vo.java:3526) at com.ibm.db2.jcc.am.vo.b(vo.java:4489) at com.ibm.db2.jcc.am.vo.kc(vo.java:807) at com.ibm.db2.jcc.am.vo.executeUpdate(vo.java:781)
2 answers
Although is not suggested to store a such large file into SCM database, try uploading the large file into file server, append the link into RTC WI.
However if you business requirement is to attach a large file, then you can workaround this issue by tuning DB2 database file sizes. The suggested values to check in about 800 + MB file is below.
Logfilsiz=12288
Logprimary=128
Logsecond=128
You need to restart DB2 server for this changes to take effect (in some case it does no required, but its safe to restart). Run
>db2 get db cfg for <dbname>
the cfg file should list configration of your DB, including the log changes you've made. Ensure the changes is picked up.
You're good to go to attach a large file. As always, please avoid attaching a large files into SCM database.
However if you business requirement is to attach a large file, then you can workaround this issue by tuning DB2 database file sizes. The suggested values to check in about 800 + MB file is below.
Logfilsiz=12288
Logprimary=128
Logsecond=128
You need to restart DB2 server for this changes to take effect (in some case it does no required, but its safe to restart). Run
>db2 get db cfg for <dbname>
the cfg file should list configration of your DB, including the log changes you've made. Ensure the changes is picked up.
You're good to go to attach a large file. As always, please avoid attaching a large files into SCM database.
Hi Nattu,
I guess you have already looked at increasing the transaction log space, if not, below is a DB2 Troubleshooting technote, which suggests increasing transaction log space could help :
http://www.ibm.com/support/knowledgecenter/SSATW2_7.3.0/com.ibm.ituam.doc_7.3/troubleshooting/t_exception_db2_sql_error_sqlcode_-964.html
Regards,
Dinesh
I guess you have already looked at increasing the transaction log space, if not, below is a DB2 Troubleshooting technote, which suggests increasing transaction log space could help :
http://www.ibm.com/support/knowledgecenter/SSATW2_7.3.0/com.ibm.ituam.doc_7.3/troubleshooting/t_exception_db2_sql_error_sqlcode_-964.html
Regards,
Dinesh