[ZBX-6197] Data not imported correctly in IBM DB2 Created: 2013 Jan 31 Updated: 2017 May 30 Resolved: 2013 Feb 05 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Installation (I) |
| Affects Version/s: | 2.0.5rc1, 2.1.0 |
| Fix Version/s: | 2.0.5rc1, 2.1.0 |
| Type: | Incident report | Priority: | Critical |
| Reporter: | Pavels Jelisejevs (Inactive) | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | db2, images, installation | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
When importing images.sql, the image 41 (IP_PBX_(128)) is not imported. It seems it's too large for DB2. Because of that, the data in data.sql after sysmaps_elements is not imported: it references an unexisting icon. |
| Comments |
| Comment by Andris Zeila [ 2013 Feb 04 ] |
While we are trying to insert 36410 hexadecimal digits. And apparently that limit can't be increased. Copying images to server and importing from stored procedure also is not trivial, as the DB2 SQL stored procedures don't support file operations. The only way is to create C/Java user defined procedure. |
| Comment by Andris Zeila [ 2013 Feb 05 ] |
|
Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-6197 A workaround was found to split larger images in smaller blobs and concatenate those blobs when inserting image. |
| Comment by Alexander Vladishev [ 2013 Feb 05 ] |
|
Successfully tested! |
| Comment by Andris Zeila [ 2013 Feb 06 ] |
|
Fixed in: |