Receive "ORA-01652: unable to extend temp segment by 128 in tablespace TEMP" error on query after upgrading to MetaMatrix 5.5.4

Solution Verified - Updated -

Issue

  • This is our first issue identified post-upgrade of 5.5.4 in Production.   The same report using attached query from Business Objects was running fine before upgrade and now after the upgrade,  it is not taking forever and throws an error "ORA-01652: unable to extend temp segment by 128 in tablespace TEMP"
  • For some reason,  the MetaMatrix query engine is sending incorrect statement to cache database which is causing cartesian join when we use FormatDate.
  • If we use ParseDate the correct query is sent to the database.

Environment

  • MetaMatrix Enterprise Server 5.5.4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content