1. Get rid of all advertisements and get unlimited access to documents by upgrading to Premium Membership. Upgrade to Premium Now and also get a Premium Badge!

Classic Report Query limit

Discussion in 'Oracle Application Express (APEX)' started by Bharat, Jan 8, 2015.

  1. Bharat

    Bharat Community Moderator Forum Guru

    Messages:
    1,747
    Likes Received:
    147
    Trophy Points:
    1,805
    Location:
    Vijayawada, India
    Hi All,

    Is there any limitations on length of the Query need to define in Classic Report ?

    As when we place the query and press Next button following error message is pulling up.

    ORA-01461: can bind a LONG value only for insert into a LONG column
     
  2. DTSIGuy

    DTSIGuy Forum Advisor

    Messages:
    402
    Likes Received:
    58
    Trophy Points:
    410
    Location:
    Texas
    What makes you think the error has anything to do w/ the length of the query?
     
  3. Bharat

    Bharat Community Moderator Forum Guru

    Messages:
    1,747
    Likes Received:
    147
    Trophy Points:
    1,805
    Location:
    Vijayawada, India
    When I decrease the length of query by removing two lines then report region is creating fine, but when adding 1 line to that query is erroring out with the provided error message. So thought like there would be an limitation on the sql portion.
     
  4. DTSIGuy

    DTSIGuy Forum Advisor

    Messages:
    402
    Likes Received:
    58
    Trophy Points:
    410
    Location:
    Texas
  5. Bharat

    Bharat Community Moderator Forum Guru

    Messages:
    1,747
    Likes Received:
    147
    Trophy Points:
    1,805
    Location:
    Vijayawada, India
    So, is there any limitation on report region level for query ?
     
  6. DTSIGuy

    DTSIGuy Forum Advisor

    Messages:
    402
    Likes Received:
    58
    Trophy Points:
    410
    Location:
    Texas
    Of course there are limitations...there are limitations for just about everything. As the link points out, any limit regarding the report looks to be based entirely on how the report is stored in the APEX tables (if I understand it correctly) which you have no control over.

    I suspect all you need to do to fix your report is to alter your approach.

    CJ
     
  7. Bharat

    Bharat Community Moderator Forum Guru

    Messages:
    1,747
    Likes Received:
    147
    Trophy Points:
    1,805
    Location:
    Vijayawada, India
    Yeah... Achieved this by creating a function which returns query and there in report level we have used pl/sql function which returns query to capture the query. By that we can overcome this issue as suggested in the provided URL.