How To Resize Temp-tablespace In Active Data Guard Scenario
Last updated on DECEMBER 25, 2017
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 and later
Information in this document applies to any platform.
Management of TEMP TABLESPACE in ADG is very important from 12c because DML on TEMP is allowed in ADG.
DML changes to TEMP doesn't generate REDo because it is TEMP tablespace. However undo generated for the changes does in turn generate REDO. Due to this reason GLOBAL TEMP Tablespace is not allowed in ADG. However from 12c onwards UNDO for global TEMP tablespace is stored in TEMP itself unlike UNDO tablespace.Due to the above reason it is very much important to look for an option to resize the TEMP properly.
++ Read mostly application can redirect their table sorting with GLOBAL TEMP TABLES on ADG.
++ Use TEMP_UNDO_ENABLED to TRUE to enable TEMP UNDO on primary. However in ADG it is default enabled.
++ We can use this TEMP_UNDO_ENABLED on primary to reduce the REDO generation for TEMP operation
Resize Temp on ADG failing with ORA-16000
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms