Error creating Good/Bad/Marginal incoming status rule.

Technote (troubleshooting)


Problem(Abstract)

When creating a Good, Bad, Marginal incoming status rule with a large filter, the following error is received:

Exception occurred while inserting an OrgNode into DataType

Symptom

When creating a Good, Bad, Marginal incoming status rule with a large filter, the following error is recieved:

Exception occured while inserting an OrgNode into
DataType: EventMappingFilterGUI. Exception:
com.micromuse.response.common.RespException:
Could not create SQL statement

The following error found in the logs:
Target exception: com.micromuse.sla.soap.RADSoapException: Exception
occurred while inserting an OrgNode into DataType:
EventMappingFilterGUI. Exception:
com.micromuse.response.common.RespException: com.ibm.db2.jcc.am.co: DB2
SQL Error: SQLCODE=-302, SQLSTATE=22001, SQLERRMC=null, DRIVER=3.57.82


Cause

The size of the SERVICEFILTER column in the EVENTMAPPINGFILTER table is exceeded. It is possible to increase the value, but not possible to make it limitless.


Any filter that exceeds this value is likely to be very inefficient, so that size will not be increased further.

Resolving the problem

Reduce the size of the filter. Large filters can be very inefficient, change your TBSM solution design to use a smaller filter in the rule.

Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Business Service Manager

Software version:

6.1

Operating system(s):

AIX, Linux, Linux zSeries, Solaris, Windows

Reference #:

1615581

Modified date:

2014-09-02

Translate my page

Machine Translation

Content navigation