Oracle Error Code 17144
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the internalqueryexecmaxblockingsortbytes workings and policies of this site About Us Learn more about Stack mongodb create index for sorting Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs
Mongodb Add Index
Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join
Mongoose Index
them; it only takes a minute: Sign up My Mongo query is too large and I'm reaching a memory issue up vote 0 down vote favorite I'm reaching some sort of RAM limit when doing this query, here's the error: The operation: #
can return. The appendix is organized as follows: General Structure of JDBC Error Messages General JDBC Messages Native XA
Mongodb Sort By Date
Messages TTC Messages Each of the message lists is first sorted bytes to mb by ORA number, and then alphabetically. See Also: "Processing SQL Exceptions" General Structure of JDBC Error Messages The general JDBC error message structure allows run-time information to be appended to the end of a message, following a colon, as follows:
Previous TicketNext Ticket → Opened 5 years ago Closed 4 years ago Last modified 3 years ago #17144 closed Bug (fixed) Excessive GROUP BY clauses during aggregations. Reported by: christian_oudard Owned by: Anssi Kääriäinen https://code.djangoproject.com/ticket/17144 Component: Database layer (models, ORM) Version: 1.3 Severity: Normal Keywords: Cc: Michael Curry, kmike84@…, YenTheFirst, baryshev@…, anssi.kaariainen@…, hcarvalhoalves@…, dev@… Triage Stage: Accepted Has patch: yes Needs documentation: no Needs tests: http://www.dbforums.com/showthread.php?717167-ORA-24338-statement-handle-not-executed no Patch needs improvement: no Easy pickings: no UI/UX: no Description Doing a simple aggregation using the Django ORM on MySQL, it is producing a GROUP BY clause that oracle error includes an unnecessary field. In the particular case where I discovered this, the unnecessary field is very large, and was slowing down the query by 100-fold. Here is a simplified version of the model: class Document(models.Model): data = models.TextField() # Very large field class Attachment(models.Model): document = models.ForeignKey(Document) And the query I am running: Document.objects.annotate(num_attachments=Count('attachment')) And the SQL output: SELECT oracle error code `document_document`.`id`, `document_document`.`data`, COUNT(`document_attachment`.`id`) AS `num_attachments` FROM `document_document` LEFT OUTER JOIN `document_attachment` ON (`document_document`.`id` = `document_attachment`.`document_id`) GROUP BY `document_document`.`id`, `document_document`.`id`, `document_document`.`data` ORDER BY NULL Doing GROUP BY on the data field is unnecessary, and it did not do this in Django 1.2. From the Django mailing list: Karen Tracey On Tue, Nov 1, 2011 at 6:19 PM The SQL generated by the ORM for this query changed between Django version 1.2 and 1.3. The 1.2 SQL did a group by only on the id field. With 1.3 we're getting id twice and then all other fields in the model. Bisection shows the change was made with r14715: https://code.djangoproject.com/changeset/14715 It certainly looks to me like the old SQL was correct and preferable for this particular case. In a brief search I did not find a ticket reporting this issue -- could you open one? Attachments (2) group_by_bug_regressiontest.patch (1.6 KB) - added by christian_oudard 5 years ago. Regression test for the issue 17144.diff (8.1 KB) - added by Anssi Kääriäinen 5 years ago. Download all attachments as: .zip Oldes
be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Page 1 of 2 12 Last Jump to page: Results 1 to 15 of 17 Thread: ORA-24338: statement handle not executed Tweet Thread Tools Show Printable Version Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 03-11-03,10:21 #1 johnstv3 View Profile View Forum Posts Registered User Join Date Mar 2003 Posts 20 Unanswered: ORA-24338: statement handle not executed Hi everyone, I currently have a stored procedure that takes two input parameters and one REF CURSOR output parameter which I am calling from ASP. Depending upon the values of the two input parameters a REF CURSOR can either be returned or nor returned. I.e. IF param1 = 2 /* do something */ ELSE IF param2 = 4 /* Open REF CURSOR for return parameter */ OPEN curs FOR SELECT * FROM temp; END IF; When a REF CURSOR is returned the ASP code is fine and I can display all the records it has within it. The trouble starts when param1 is 2 and therefore no REF CURSOR is returned. At this point I am greeted with the error: OraOLEDB error '80004005' ORA-24338: statement handle not executed Does anyone know how I can deal with this situation. A REF CURSOR must only be returned under a specific condition (i.e. param2 = 4). Thanks. Regards, John Last edited by johnstv3; 03-11-03 at 10:25. Reply With Quote 03-11-03,10:40 #2 andrewst View Profile View Forum Posts Visit Homepage Moderator. Join Date Sep 2002 Location UK Posts 5,171 Provided Answers: 1 Re: ORA-24338: statement handle not executed Your ASP program needs to take into account whether