Hi,
Thanks to LJ and Jose for the replies! As suggested I looked at the logs.
The output seems to support the idea that there is a bug in
parseQualification:
When called on a field that works as expected ('Summary' in the example
below) the result is:
SELECT T852.C1,C536870989 FROM T852 WHERE (T852.C8 = 'atl01a') ORDER
BY C536870944 DESC, 1 ASC
When called on a field that causes an exception ('Associated Asset' in the
example below) the result is:
SELECT T852.C1,C536870989 FROM T852 WHERE (T852.C536870989 ORDER BY
C536870944 DESC, 1 ASC
When called using LIKE instead of = on the 'Associated Asset' the result
is:
SELECT T852.C1,C536870989 FROM T852 WHERE (dbms_lob.instr
(T852.C536870989, 'atl01a') > 0) ORDER BY C536870944 DESC, 1 ASC
Unfortunately, while this runs without an error, it does return any
results.
Maybe I'm missing something, but it seems to me that parseQualification is
not generating a working sql statement in the example that causes an
exception. Note that there is no comparison operator or RHS value between
T852.C536870989 and ORDER BY.
Further, the sql statement that is generated when LIKE is used doesn't
result in the correct results.
thanks again,
Tony
-----Original Message-----
Date: Thu, 15 Mar 2012 09:34:09 -0600
From: LJ LongWing <lj.longw...@gmail.com>
Subject: Re: invalid relational operator exception from QualifierInfo
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:arslist@ARSLIST.ORG] On Behalf Of Anthony Jurado Jr
Sent: Wednesday, March 14, 2012 2:13 PM
To: arslist@ARSLIST.ORG
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
(UnknownSource)
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
(UnknownSource)
at com.bmc.arsys.api.ARServerUser.getListEntry
(UnknownSource)
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"
