Regarding sql error

[gaurav.shetti]

I had written a query within the sql block a simple fetch.
I had written the same logic on 2 pages(test and search). 1 which only contained the query (test) and the other which contains other logic in addition to this query logic(search).

In test, it fetches the result perfectly fine.
But in search, these are the parameters that were set after the sql was fired to the oracle database from vortex page


$ret :
QUERY: select case_url,title from t_case_detail_url where rownum<6 and case_element_id in(select case_element_id from t_Case_Detail_New where case_id='535798') ERROR: command sh returned exit code 1 - CASE_URL|TITLE/attachments/scmail/57493/case_535798_2967433_1.jpg|4thumbnail.jpg -


$ret.err :
nothing was returned here

$ret.stderr :
nothing was returned here

$err :
1

[gaurav.shetti]

a few more to add
$errnum :
118

$errmsg :
command sh returned exit code 1

$errfunc:
returned nothing

$errvfunc:
buildSqlClauses

[mark]

Hard to say without seeing the code, but basically the shell command you ran returned a 1 for exit code which usually indicates some kind of problem while running the script. Confirm the operation of the script you're calling.

[gaurav.shetti]

when i ran the script from unix i got the results without any issues. I also noticed that the errornum was returning a warning and not an error and the data was being fetched.
Can you tell me what 118 warning corresponds to ?

[gaurav.shetti]

errornum 118 corresponds to ? *

[mark]

118 is a warning level. Specifically regarding exec.
errmsg gives the details.

http://www.thunderstone.com/site/vortex ... rrors.html

[gaurav.shetti]

Well from the data given above .. particularly from no2. Can you tell me what can be the possible issues ?

[gaurav.shetti]

sorry i got it ... i was assuming buildSqlClauses was a standard warning from vortex. Its a module written by us. Got it