Highlighted
Honored Contributor.
Honored Contributor.
1441 views

Undisplayed message:Value for Subcategory field is not valid.

Jump to solution

Hi,

I am working on integration OMi-SM, I already have opened related case 5314098965 where I was able to create an incident in SM, now I have made modification to mapping on SM side and incident does not open. Need to know why, because I set $defaultValueOfCreate("x") for category, subcategoy and product.type, but error in log keeps returning Undisplayed message:Value for Subcategory field is not valid.
Do I need to change script on OMi side or how to convince SM to open a incident? I have checked the PD workflow and I do not have any validation set, is this anywhere in background still present and it is causing me problems?

Please also review attached files

Regards

2936( 5500) 10/21/2016 16:14:19 RTE I User OMiSMIntegrUser has logged in and is using a Named license ( 2 out of a maximum 5 )
2936( 5500) 10/21/2016 16:14:19 RTE I Base login Response: 0.234 -- RAD: 0.000 JS: 0.140 Log:0.000 Database: 0.094(00524) LDAP: 0.000 (CPU 0.155) application:login,cleanup
2936( 5500) 10/21/2016 16:14:19 RTE I -Memory : S(4297800) O(1032244) MAX(5330044) - MALLOC's Total(318379)
2936( 5500) 10/21/2016 16:14:20 RTE A Mapping-3-SMISConfiguration,paramInfo,paramName, SQL Query incomplete because field (paramInfo,paramName) not mapped in file (SMISConfiguration) ; application(Unknown), panel(Unknown)
2936( 5500) 10/21/2016 16:14:20 RTE A Mapping-3-SMISConfiguration,paramInfo,paramValue, SQL Query incomplete because field (paramInfo,paramValue) not mapped in file (SMISConfiguration) ; application(Unknown), panel(Unknown)
2936( 5500) 10/21/2016 16:14:20 RTE A Performance-2-SMISConfiguration, Partial File Scan for query involving fields {intId, template, paramInfo,paramName, paramInfo,paramValue} ; application(Unknown), panel(Unknown)
2936( 5500) 10/21/2016 16:14:20 RTE E Script failed: Error in executing script BDM_SM.processRequestError in executing script 'BDM_SM.processRequest'Error in executing script BDM_SM.processRequest: ValidationFailedException: Validation failed for probsummary - failed to add record
2936( 4716) 10/21/2016 16:14:20 JRTE E Caught exception:
com.hp.ov.sm.common.core.DAOValidationFailedException: : Validation failed for probsummary - failed to add record
at com.hp.ov.sm.server.utility.DAOThread.handleRequest(Native Method)
at com.hp.ov.sm.server.utility.DAOThread.processRequest(DAOThread.java:308)
at com.hp.ov.sm.server.utility.DAOThread.processRequest(DAOThread.java:201)
at com.hp.ov.sm.server.utility.DAOThread.process(DAOThread.java:167)
at com.hp.ov.sm.server.utility.DAOThread.run(DAOThread.java:96)
2936( 4716) 10/21/2016 16:14:20 JRTE E RESTful service exception:
com.hp.ov.sm.common.core.DAOValidationFailedException: : Validation failed for probsummary - failed to add record
at com.hp.ov.sm.server.utility.DAOThread.handleRequest(Native Method)
at com.hp.ov.sm.server.utility.DAOThread.processRequest(DAOThread.java:308)
at com.hp.ov.sm.server.utility.DAOThread.processRequest(DAOThread.java:201)
at com.hp.ov.sm.server.utility.DAOThread.process(DAOThread.java:167)
at com.hp.ov.sm.server.utility.DAOThread.run(DAOThread.java:96)
2936( 5500) 10/21/2016 16:14:35 JRTE I DAOThread exits after idle for (sec): dao_sessiontimeout=15
2936( 5500) 10/21/2016 16:14:35 JRTE I Termination signal: 0
2936( 5500) 10/21/2016 16:14:35 RTE D Destroying DAOThread ed1c610
2936( 5500) 10/21/2016 16:14:35 RTE I -Memory : S(7221704) O(2353540) MAX(10070988) - MALLOC's Total(637962)
2936( 5500) 10/21/2016 16:14:35 RTE I Thread termination in progress
2936( 5500) 10/21/2016 16:14:35 RTE A SUMMARY-1 The following event has been reported 1 times in the last 0 minute(s)
2936( 5500) 10/21/2016 16:14:35 RTE A Mapping-3-SMISConfiguration,paramInfo,paramName, SQL Query incomplete because field (paramInfo,paramName) not mapped in file (SMISConfiguration)
2936( 5500) 10/21/2016 16:14:35 RTE A SUMMARY-1 The following event has been reported 1 times in the last 0 minute(s)
2936( 5500) 10/21/2016 16:14:35 RTE A Mapping-3-SMISConfiguration,paramInfo,paramValue, SQL Query incomplete because field (paramInfo,paramValue) not mapped in file (SMISConfiguration)
2936( 5500) 10/21/2016 16:14:35 RTE A SUMMARY-1 The following event has been reported 1 times in the last 0 minute(s)
2936( 5500) 10/21/2016 16:14:35 RTE A Performance-2-SMISConfiguration, Partial File Scan for query involving fields {intId, template, paramInfo,paramName, paramInfo,paramValue}
2936( 5500) 10/21/2016 16:14:35 RTE I User OMiSMIntegrUser has logged out and freed a Named license ( 1 out of a maximum 5 )
2936( 5500) 10/21/2016 16:14:35 RTE I Undisplayed message:Script line 0: ERROR uncaught exception: ValidationFailedException: Validation failed for probsummary - failed to add record at char 1
2936( 5500) 10/21/2016 16:14:35 RTE I Undisplayed message:Value for Subcategory field is not valid.
2936( 5500) 10/21/2016 16:14:35 RTE I Undisplayed message:[INFO][BDM_Mapping_Config]: load smFieldTypes, fileName = probsummary
2936( 5500) 10/21/2016 16:14:35 RTE I Undisplayed message:[INFO][BDM_Mapping_Config]: init __bdm_sm_field_types ...
2936( 5500) 10/21/2016 16:14:35 RTE I Undisplayed message:[INFO][BDM_Mapping_Config]: load mapping config: incident, version = 1.1
2936( 5500) 10/21/2016 16:14:35 RTE I Undisplayed message:[INFO][BDM_Mapping_Config]: -> __createSMBDMMappingConfig ...
2936( 5500) 10/21/2016 16:14:35 RTE I Thread termination cleanup complete. Thread was active for 0 days,00:00:16. Threads remaining: 2 of 50

0 Likes
1 Solution

Accepted Solutions
Highlighted
Honored Contributor.
Honored Contributor.

Re: Undisplayed message:Value for Subcategory field is not valid.

Jump to solution

Hi,

just to update you, issue was resolved. What I needed to do is:

- change parameter in groovy script INCIDENT_TYPE = 'incident'

- change BDM mapping for category and direction

- comment the IncidentDAO the part:
if( obj.category != "incident" )
throw new lib.BasicDAO.ValidationFailedException(this.tableName, "The BDM incident_type (Category field of probsummary) has to be \"incident\" while creating a new incident in SM.");

Regards

View solution in original post

22 Replies
Highlighted
Super Contributor.
Super Contributor.

Re: Undisplayed message:Value for Subcategory field is not valid.

Jump to solution

Hello Wboy,

It seems the validation failed. If you create a ticket in SM itself with the subcategory you defined in the mapping, will the ticket be created?

Estelle

0 Likes
Highlighted
Honored Contributor.
Honored Contributor.

Re: Undisplayed message:Value for Subcategory field is not valid.

Jump to solution

Hi,

If I open incident manually it is opened. Also subcategory is not mandatory in logging phase at all and I am not sure why is insisting as mandatory. Does SM has this validation checking somewhere else defined? On PD or FC nothing is present.

Regards

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Undisplayed message:Value for Subcategory field is not valid.

Jump to solution

Hi,

I haved worked on similar issue before.

let me explain you how I fixed that issue and you can verify the same steps on your box.

/////////////////////////////////

SM logs of my customer have "Validation failed for probsummary - failed to add record” is coming so many times and the reason for it is

 16440( 21328) 07/08/2016 03:15:37  RAD W Value for Subcategory field is not valid.

So subcategory is not valid which my customer was passing.

You should check your OMI logs also.

The OMI logs of my customer shows the same error i.e.

2016-07-08 12:46:53,893 [pool-4041-thread-1] DEBUG ExternalProcessAdapter.invoke(?) - forwardEvent() for event: c4da8280-44db-71e6-151c-0a3b7b560000 
2016-07-08 12:46:53,896 [pool-4041-thread-1] DEBUG ExternalProcessAdapter.invoke(?) - Creating request for: http://HPOMI001.INDIA.SBIUNIVERSAL.com:80/topaz/dash/nodeDetails.do?cmdbId=929715407eafa506988ef4824a1639d3
Hosted on: NCAST002
 
[Category]
Performance
 
[Application]
alarmgen
 
[Object]
Memory
 
[Original Data]
Node:         
Message group: Performance
Application:   alarmgen
Object:        Memory
Severity:      Critical
Text:          "Memory Bottleneck probability=   100.00%" START: 07/08/2016 12:40:00 (-b 1467961800 -e 1467961800)
 
 
[Title]
"Memory Bottleneck probability=   100.00%" START: 07/08/2016 12:40:00 (-b 1467961800 -e 1467961800)
 
[Assigned User]
<unassigned>
 
[Assigned Group]
<unassigned>
 
[State]
open
 
[Severity]
critical
 
[Priority]
medium
 
[Initiated by]
BSM forwarding rule: Critical
 
[OMi Hostname]
HPOMI001.INDIA.SBIUNIVERSAL.com
</description>
  </activity_log>
</incident> 
2016-07-08 12:46:54,085 [pool-4041-thread-1] DEBUG ExternalProcessAdapter.invoke(?) - Getting Cookies 
2016-07-08 12:46:54,085 [pool-4041-thread-1] DEBUG ExternalProcessAdapter.invoke(?) - HTTP Header count: 6 
2016-07-08 12:46:54,085 [pool-4041-thread-1] DEBUG ExternalProcessAdapter.invoke(?) - Header: Connection: [close] 
2016-07-08 12:46:54,086 [pool-4041-thread-1] DEBUG ExternalProcessAdapter.invoke(?) - Header: Content-Length: [58] 
2016-07-08 12:46:54,086 [pool-4041-thread-1] DEBUG ExternalProcessAdapter.invoke(?) - Header: Content-Type: [application/atom+xml] 
2016-07-08 12:46:54,087 [pool-4041-thread-1] DEBUG ExternalProcessAdapter.invoke(?) - Header: Date: [Fri, 08 Jul 2016 07:15:37 GMT] 
2016-07-08 12:46:54,087 [pool-4041-thread-1] DEBUG ExternalProcessAdapter.invoke(?) - Header: Server: [Apache-Coyote/1.1] 
2016-07-08 12:46:54,088 [pool-4041-thread-1] ERROR ExternalProcessAdapter.invoke(?) - HTTP error response - Bad Request (400): : Validation failed for probsummary - failed to add record 
2016-07-08 12:46:54,088 [pool-4041-thread-1] ERROR ExternalProcessAdapter.invoke(?) - Node: HPSM001.INDIA.SBIUNIVERSAL.com, Port: 13082, ClientWebException encountered: (400) Bad Request 
org.apache.wink.client.ClientWebException

So the delivery failed error is coming.

The sub category customer was passing is Performance.

So the suggestion given was

1 Please note that Category field in OMI is mapped to Subcategory field in SM.

2 When OMI is passing category Performance for critical alert to SM,  it is failing and SM ticket are not creating.

This is because we saw that the category incident which is used for IM ticket do not have Subcategory Performance

So please go to windows client

Go to db->imSubcatgeroy table and check that and add that category

/////////////////////////////////

I hope this helps.

Thanks & Regards
Animesh

0 Likes
Highlighted
Super Contributor.
Super Contributor.

Re: Undisplayed message:Value for Subcategory field is not valid.

Jump to solution

Hi Wboy,

Please help verify Animesh's comments.

If you still see the problem after checking all above, it's better to open a support case to collect debug log for further analysis.

Estelle

0 Likes
Highlighted
Honored Contributor.
Honored Contributor.

Re: Undisplayed message:Value for Subcategory field is not valid.

Jump to solution

Hi,

thank you for reply. In my case I want to hardcode this to be always the same, since I do not need different values based on event, how can I achieve this? Do I need to modify script on OMi side? Like I said in first post, I have defined SM Callback on mapping $defaultValueOfCreate("OMi alert") but it does not work. There is no details in documentation, so I need someone with experience to tell me more.

Regards

0 Likes
Highlighted
Super Contributor.
Super Contributor.

Re: Undisplayed message:Value for Subcategory field is not valid.

Jump to solution

Hi Wboy,

I tested OMI-SM integration early this year. This function "$defaultValueOfCreate()" did work at that time.

May I know if you have a support case opened for this issue?

A debug trace of related port would help to identify where this validation came from.

Estelle

0 Likes
Highlighted
Honored Contributor.
Honored Contributor.

Re: Undisplayed message:Value for Subcategory field is not valid.

Jump to solution

Hi,

I have opened a support case but this things go slow since L1 does not have knowledge, seniors are not included soon and last case I resolved myself since in 1 week it did not move case anywhere. Which debug parameter should I use and what to search for? I should probably use separated servlet to only focus on the integration?

Regards

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Undisplayed message:Value for Subcategory field is not valid.

Jump to solution

Hi,

we can do some query on BDM mapping SM Callback Script and meet your requirement. if you see the attached screen the if loop is getting called when category is empty or NULL.

you can check if category field empty or not empty when OMI is passing it and then change the if loop condition and code inside that to meet your requirement.

I hope this helps.Thanks & Regards

Animesh

Highlighted
Honored Contributor.
Honored Contributor.

Re: Undisplayed message:Value for Subcategory field is not valid.

Jump to solution

I have been modifying this script, but validation fails, so I am not sure with what values/parameters incident is being opened and how does the bdm mapping affecting. Integration manager is set to debug, but nothing useful is written to log. SOAP webservice integrations was a lot easier to debug.

Regards

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Undisplayed message:Value for Subcategory field is not valid.

Jump to solution

Hi ,

Thanks for the reply.

We need a debug trace to narrow down this issue as without that we can not tell where exactly is the issue.

STEPS

1 open a debug port on SM with below parameter

-RTM:3 -debugdbquery:999 -debugnode:1 -numberoflogfiles:10 -maxlogsize:30480000 -log:../logs/SMOMI.log

2 Replicate the issue i.e. sent us one event from OMI TO SM. Incident will not open in SM as you told.

Then provide us

3 All the log file starting from with "opr-event-sync-adapter" from OMI end

4 event id which you sent from OMI + screen shot of the event

5 All the SMOMI.log from SM end.

6 Unload of BDM mapping.

Thanks & Regards

Animesh

Animesh

0 Likes
Highlighted
Honored Contributor.
Honored Contributor.

Re: Undisplayed message:Value for Subcategory field is not valid.

Jump to solution

Hi,

I assume it is forcing an OMi event category to incident and this why it failes. Is it possible to set default values in mapping at SM default value column? I can not attach zip file, so I will send you link to FTP.

Regards

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.