Database Memory & 4030/4031 (MOSC)

MOSC Banner

Oracle temp tablespace filling up fast and observed error ORA-1652 in trace

in Database Memory & 4030/4031 (MOSC) 4 commentsAnswered

Oracle version: Oracle Database 12c Release 12.1.0.1.0 - 64bit Production.

Below error is observed in trace files:

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

Mon Oct 19 00:13:00 2020

Exception [type: ACCESS_VIOLATION, UNABLE_TO_READ] [ADDR:0x0] [PC:0x7FF6FC5DB45A, kdgvsp()+298]

Mon Oct 19 00:13:00 2020

Exception [type: ACCESS_VIOLATION, UNABLE_TO_READ] [ADDR:0x0] [PC:0x7FF6FC5DB45A, kdgvsp()+298]


temp tablesace datafile has reached maximum of 32GB currently and it is giving the above error in trace files.

Is there any way to cleanup unused space in temporary tablespace , please suggest.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center