Running the report, gives me the following error:-
Exception: DBD, ORA-01652: unable to extend temp segment by 128 in tablespace TEMP
State: N/A
Any resolution or ideas?
BO_Stuffed (BOB member since 2008-03-29)
Running the report, gives me the following error:-
Exception: DBD, ORA-01652: unable to extend temp segment by 128 in tablespace TEMP
State: N/A
Any resolution or ideas?
BO_Stuffed (BOB member since 2008-03-29)
I am guessing you are using oracle. It looks to me that the temp file cannot grow due to lack of tablespace resources. You would have to send this to a dba to sort out for you unless you know how to allocate segments and extents etc…
jonathanstokes (BOB member since 2004-09-17)
Thank you… I will wake up my sleeping DBA’s . Get UP!!!
BO_Stuffed (BOB member since 2008-03-29)
Although it is a clue for you that your report might be generating too many lines or it doesn’t group like you thought it would …
HenkK
HenkK (BOB member since 2004-03-02)
Hi All,
i am also getting the same error for few of my reports. I have few questions:
The query when run in toad give me results in just 16 seconds… then why does this throw an error in BO
These reports are scheduled to reach a particular destination in excel format at runtime. The schedule is successful but a blank excel is saved at the destination. Is there a possibility that the mentioned error is causing this to happen.
Thanks…
shiky (BOB member since 2007-07-11)
Toad is very smart: is displays the first 20 or so rows in the screen as soon as they are received from the database. Then the other zillion rows are still en route to Toad …
DeskI on the other hand keeps waiting for the database until the very last row of data is in. Then and only then DeskI starts its own formatting and sorting process. After that is finished, your report is displayed!
So it is difficult to compare Toad and BO on speed!
HenkK
HenkK (BOB member since 2004-03-02)
Hi BO_Stuffed,
Please run the query in the BO and check with your DBA that how much data it generates which causes the TEMP table space to go full.
Is your query having group functions which groups a large volume of data into small number of group by values?
Your DBA would be the best person to tell you to how to fine tune your query.
Omkar Paranjpe (BOB member since 2006-02-13)