function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
kbkb 

oracle errors coming back in faultstring from QUERY call

our application queries the Organization entity to get the org name and id of the current user.
it used to work fine, but we are now getting ORA-XXX oracle errors in the fault string.
Note that it still works if the current user has admin privs; this error only happens when a non-admin user is issuing the sforce call...but this used to work..

is there a better (w/o using the 2.0 undocumented api call) to get the org id?

sent:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <soapenv:Header>
  <ns1:SessionHeader soapenv:mustUnderstand="0" xmlns:ns1="SoapService">
   <ns2:sessionId xmlns:ns2="urn:partner.soap.sforce.com">[omit]</ns2:sessionId>
  </ns1:SessionHeader>
  <ns3:QueryOptions soapenv:mustUnderstand="0" xmlns:ns3="SoapService">
   <ns4:batchSize xmlns:ns4="urn:partner.soap.sforce.com">500</ns4:batchSize>
  </ns3:QueryOptions>
 </soapenv:Header>
 <soapenv:Body>
  <query xmlns="urn:partner.soap.sforce.com">
   <queryString>SELECT Name,Id FROM Organization</queryString>
  </query>
 </soapenv:Body>
</soapenv:Envelope>

received:
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <soapenv:Body>
  <soapenv:Fault>
   <faultcode>soapenv:Server.userException</faultcode>
   <faultstring>java.sql.SQLException: ORA-20000:
ORA-06512: at &quot;BUILD132R5A.CPERMISSIONS&quot;, line 46
ORA-06512: at &quot;BUILD132R5A.CORGANIZATION&quot;, line 2382
ORA-06512: at line 1
</faultstring>
   <detail/>
  </soapenv:Fault>
 </soapenv:Body>
</soapenv:Envelope>

DevAngelDevAngel

Hi kb,

This looks like a bug, and I have filed one on your behalf.  Expect resolution in next release at latest.