ORA-01652:unable to extend temp segment by 128 in tablespace TEMP | Community
Skip to main content
O
Ofattah
Level 2
June 2, 2021
Solved

ORA-01652:unable to extend temp segment by 128 in tablespace TEMP

  • June 2, 2021
  • 2 replies
  • 24394 views

Hello everyone,
I hope you can help me solve this issue.
We launched a workflow with a query-->enrichment box-->change dimension box...
The workflow stops just when it reaches the change dimension box because of the following error: ORA-01652:unable to extend temp segment by 128 in tablespace TEMP.

We already extended the temp tablespace in the database, but it didn't resolve the problem.
Do you have an idea please? because we had the same error with the same workflow in the query box too before. 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by venkatesanj1458

Hi @ofattah 

This could be because the resulting data set fetched by the query is exceeding the temp tablespace in oracle DB. Please have a DBA involved and extend the temp tablespace in the database.

 

2 replies

venkatesanj1458
venkatesanj1458Accepted solution
Level 2
June 2, 2021

Hi @ofattah 

This could be because the resulting data set fetched by the query is exceeding the temp tablespace in oracle DB. Please have a DBA involved and extend the temp tablespace in the database.

 

O
OfattahAuthor
Level 2
June 2, 2021

Hi @venkatesanj1458 

Thank you for your response.

We already extended the temp tablespace in the database but it didn't solve the problem.

Thanks

LaurentLam
LaurentLam
Level 5
June 2, 2021

Hi @ofattah 
Does the neolane DB user has the right to extend the temp segment:

I'm not DBA at all but it seems that, due to the request, the user is trying to do it by itself, and that's the result

if not possible, I would then try to

1- try to reproduce the issue with the less sample data as possible in order to know if this is a structural issue in the generated SQL queries or not

2- if this is a structural issue then simplify the enrichment and trying to reproduce the problem by adding more and more links/fields in order to understand which field or link create the issue

    O
    OfattahAuthor
    Level 2
    June 3, 2021

    Hi @laurentlam 

    Thank you for your response,

    I just tried to reduce the fields of the enrichment box (from around 10 to only 2) and it went well. The problem is that we use the same workflow with another account and it works just fine.

    Thanks

    Terms & ConditionsAccessibility statement

    Loading footer...