Tony, I have tried doing searches (via the user tool) on 0 length fields and received errors (I believe it stores them in clob in the db)...but I'm on SQL, and my error was different...but I suspect that the problem is a DB problem, not a Remedy problem....can you issue the same query in the user tool...and then maybe get an sql log of the request and try it directly at the DB?...I fully suspect you will find that it's a db problem and not an api issue.
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Anthony Jurado Jr Sent: Wednesday, March 14, 2012 2:13 PM To: [email protected] Subject: invalid relational operator exception from QualifierInfo Hi, I have a Java program which uses getListEntry(). I use a QualifierInfo object to create the qualification for getListEntry. The qualification looks like this: QualifierInfo qualifier = remedyConn.parseQualification(arForm, "'Associated Asset' = \"atl01a\""); Which results in this exception: CreateRemedyTicket.getSchema ARExceptionERROR (552): Failure during SQL operation to the database; ORA-00920: invalid relational operator ERROR (552): Failure during SQL operation to the database; ORA-00920: invalid relational operator at com.bmc.arsys.api.ProxyJRpcBase.verifyStatus(Unknown Source) at com.bmc.arsys.api.ProxyJRpcBase.a(Unknown Source) at com.bmc.arsys.api.ProxyJRpcBase.arCall(Unknown Source) at com.bmc.arsys.api.ProxyJRpc.ARGetListEntry(Unknown Source) at com.bmc.arsys.api.ARServerUser.getListEntry(Unknown Source) at CreateRemedyTicket.<init>(CreateRemedyTicket.java:42) at CreateRemedyTicket.main(CreateRemedyTicket.java:94) Oddly, if I change the equal sign to LIKE the query works: QualifierInfo qualifier = remedyConn.parseQualification(arForm, "'Associated Asset' LIKE \"atl01a\""); // works I have other qualifiers for different fields on the same form in which use the equal sign with no problem. E.g.: QualifierInfo qualifier = remedyConn.parseQualification(arForm, "'Summary' = \"System Down\""); // works The properties for the Summary and Associated Asset are the same with the following two exceptions: Entry Mode is Required for the Summary field (which works as expected) and optional for the Associated Asset (which doesn't work). Input Length is 254 for the Summary field and 0 for the Associated Asset field. I would appreciate any suggestions! thanks in advance, Tony Jurado Release Manager, Services Engineering IBM Security Services ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
