Error when executing Integration Gateway service

Question

Hello,
I created  a service on IGW to expose an oracle db as odata but i'm getting the following error when i call it from the browser:
<error><code/><message xml:lang="en-US">An exception occurred.</message></error>
The service itself is working. Its destination is reachable from the IGW's management cockpit test, and its url returns the service description when executed from the browser. The error happens when i try to access an entity within the service, as in:
https://smp3url:8083/gateway/odata/SIST/ODATATEST;v=1/Solicitacao/
I checked SMP's logs and found two possibly related error entries. The first is from execution of my custom script. I had to create a script to map the entity set names to actual table names in the database (their full name: schema + table name).
2015 04 07 15:41:29#0-300#ERROR#com.sap.gateway.ip.core.customdev.processor.IGWScriptProcessor##anonymous#http-bio-8083-exec-5###[Gateway][TECHNICAL][TechnicalError]:This is first log
2015 04 07 15:41:29#0-300#ERROR#com.sap.gateway.core.odata4sap.ODataErrorCallbackImpl##anonymous#http-bio-8083-exec-5###handleError(): failed to serve request for URI https://smp3url:8083/gateway/odata/SIST/ODATATEST;v=1/Solicitacao, message = An exception occurred.
Thanks,

Answer 1

Thanks for the tips guys.
Jitendra, i can't connect to my database with that string format. I need to use a tns name format, such as:
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=MyHost)(PORT=MyPort))(CONNECT_DATA=(SERVICE_NAME=MyOracleSID)))
I couldn't find a way to define the schema for this. I think i've passed this issue anyway. After the implementation of the custom script i stopped receiving an "Oracle - ORA-00942 : table or view does not exist" error from the service.
Midhun, i increased the log level but i couldn't find anything interesting in SMP's server logs. Still, i found this error message on the troubleshooting session of IGW's cockpit:
com.sap.gateway.core.api.provider.data.GenericODataProcessor: readEntitySet failed: entity set = Solicitacao, content type = application/xml;charset=utf-8, message = org.apache.olingo.odata2.api.ep.EntityProviderException: An exception occurred.
Is it a problem with the service itself then? This is interesting because i'm getting these errors  when generate the integration content on my project. I was actually ingnoring them because the deploy was still successful.