search cancel

ERRORS in ARCHMGR.OUT "Maximum vardata  string length exceeded"

book

Article ID: 189546

calendar_today

Updated On:

Products

CA Spectrum

Issue/Introduction

We are seeing these errors in the ARCHMGR.OUT log file


SPC-SHD-29021:

**************************************************************************

The following output is intended to facilitate debugging, please forward

to CA technical support.  The files listed are not part of the customer

installation of SPECTRUM.

**************************************************************************


Apr 16 19:07:14 ERROR TRACE at ModelArchDBImp.cc(1572): ModelArchDBImp::submitEvent ( model_h=0x3ea56d04, type=0x82105a, utime: 1587056834 ): Maximum vardata

 string length exceeded

Apr 16 20:20:18 ERROR TRACE at ModelArchDBImp.cc(1572): ModelArchDBImp::submitEvent ( model_h=0x3eac7752, type=0x82105a, utime: 1587061218 ): Maximum vardata

 string length exceeded

Apr 16 20:35:21 ERROR TRACE at ModelArchDBImp.cc(1572): ModelArchDBImp::submitEvent ( model_h=0x3ea56e15, type=0x82105a, utime: 1587062121 ): Maximum vardata

 string length exceeded

Apr 16 21:35:02 ERROR TRACE at ModelArchDBImp.cc(1572): ModelArchDBImp::submitEvent ( model_h=0x3eac7706, type=0x82105a, utime: 1587065702 ): Maximum vardata

 string length exceeded

 

 

Cause

The default database storage for vardata_string for text (65k) was not large enough to accommodate large changes in device configuration (event type 0x82105a).

Environment

Release : 10.3.x, 10.4.x

Spectrum Archive Manager

 

Resolution

Changes were made back in Spectrum 10.2 to increase the default database storage for default vardata_string from text (65k) to mediumtext (16M).
If the ddmdb database was not initialized, then this field has not changed and must be done manually,

This can be verified by performing the following query on the ddmdb database from mysql and checking that the vardata_string is set to mediumtext.

mysql> desc event;
+----------------+----------------------+------+-----+---------+-------+
| Field          | Type                 | Null | Key | Default | Extra |
+----------------+----------------------+------+-----+---------+-------+
| model_h        | int(10) unsigned     | NO   | PRI | NULL    |       |
| utime          | int(11)              | NO   | PRI | NULL    |       |
| counter        | int(10) unsigned     | NO   | PRI | NULL    |       |
| clk_seq        | smallint(5) unsigned | NO   | PRI | NULL    |       |
| version        | tinyint(4)           | NO   | PRI | NULL    |       |
| node_id        | char(6)              | NO   | PRI | NULL    |       |
| user_key       | int(10) unsigned     | NO   |     | NULL    |       |
| type           | int(10) unsigned     | NO   | MUL | NULL    |       |
| severity       | int(10) unsigned     | NO   |     | NULL    |       |
| vardata_string | mediumtext           | YES  |     | NULL    |       |             <<<<<----  Needs to be set to "mediumtext" and not "text"
+----------------+----------------------+------+-----+---------+-------+
10 rows in set (0.00 sec)


If the DDMDB was not reinitialized then the change to perform this manually with Archive Manager stopped  is:

Linux:

$SPECROOT/mysql/bin/mysql --defaults-file=$SPECROOT/mysql/my-spectrum.cnf -uroot -
proot -Dddmdb --execute "ALTER table event MODIFY vardata_string MEDIUMTEXT;"

Windows:

$SPECROOT/mysql/bin/mysql -uroot -proot -Dddmdb --execute "ALTER table event MODIFY vardata_string MEDIUMTEXT;"

Additional Information

If performing the steps manually please plan appropriate ArchMgr downtime.  In our test environment, a 6GB database took over an hour to modify.