Skip to main content

Recreating Temporary Tablespace: The Proper Way !!!

Create a new temporary tablespace to be default:

CREATE TEMPORARY TABLESPACE temp2 TEMPFILE 'DATAFILE_LOCATION/temp2_01.dbf' SIZE 500M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE unlimited EXTENT MANAGEMENT LOCAL;

ALTER DATABASE DEFAULT TEMPORARY TABLESPACE temp2;


Drop the previously default tablespace:

DROP TABLESPACE temp INCLUDING CONTENTS AND DATAFILES;


Create previous tablespace again:

CREATE TEMPORARY TABLESPACE temp TEMPFILE ' DATAFILE_LOCATION /temp_01.dbf' SIZE 500M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE unlimited EXTENT MANAGEMENT LOCAL;


Make it default tablespace:

ALTER DATABASE DEFAULT TEMPORARY TABLESPACE temp;


Drop the temporary tablespace created for swapping:

DROP TABLESPACE temp2 INCLUDING CONTENTS AND DATAFILES;


SELECT tablespace_name, file_name, bytes FROM dba_temp_files WHERE tablespace_name = 'TEMP';


Adding Datafile to a Temporary Tablespace:
ALTER TABLESPACE temp ADD TEMPFILE ' DATAFILE_LOCATION /temp_02.dbf' SIZE 512m AUTOEXTEND ON NEXT 500M MAXSIZE UNLIMITED;


--------------------------------------------------------
Happy to Help

Comments

Popular posts from this blog

ORACLE FLASH RECOVERY AREA USAGE QUERY

FINDING ORACLE FLASH RECOVERY AREA USAGE SELECT NAME,        (SPACE_LIMIT / 1024 / 1024 / 1024) SPACE_LIMIT_GB,          ((SPACE_LIMIT - SPACE_USED + SPACE_RECLAIMABLE) / 1024 / 1024 / 1024) AS SPACE_AVAILABLE_GB,        ROUND((SPACE_USED - SPACE_RECLAIMABLE) / SPACE_LIMIT * 100, 1) AS PERCENT_FULL   FROM V$RECOVERY_FILE_DEST;

Shared Pool Tuning: Cursor Tuning (Tuning Open_Cursors, Session_Cached_Cursors, Cursor_Space_For_Time)

Shared Pool Tuning: Cursor Tuning The three most important parameter for shared pool tuning are OPEN_CURSORS , SESSION_CACHED_CURSORS and CURSOR_SPACE_FOR_TIME. But most of the time we see that these two parameters SESSION_CACHED_CURSORS and CURSOR_SPACE_FOR_TIME are ignored or unused . OPEN CURSORS Open cursors take up space in the shared pool, in the library cache. OPEN_CURSORS sets the maximum number of cursors each session can have open, per session. For example, if OPEN_CURSORS is set to 1000, then each session can have up to 1000 cursors open at one time. V$open_cursor shows cached cursors, not currently open cursors, by session. If you’re wondering how many cursors a session has open, don’t look in v$open_cursor. It shows the cursors in the session cursor cache for each session, not cursors that are actually open.  To monitor open cursors, query v$sesstat where name= ’opened cursors current’ . This will give the number of currently opened cursors, by session:

How to delete/remove Management Agent from Oracle Enterprise Manager 12C

  1. Before you deinstall a Management Agent, do the following:     a. Stop the Agent using command from Management Agent home:                 cd /u01/oemcc_latest/core/12.1.0.2.0/bin/                 $ emctl stop agent     b. Wait for the Management Agent to go to the unreachable state in the Cloud Control console.     c. It is mandatory to delete the Management Agent and their monitored targets using any of the following methods: Remove the Agent target manually from the console: 1. Login to 12C Cloud Control 2. Navigate to Setup => Manage Cloud Control => Agents 3. Go to the Home page of the Agent that you want to remove 4. Expand the drop-down menu near the " Agent " 5. Expand the " Target Setup " option 6. Select " Remove Target "            In Cloud Control Release 12.1.0.2, the following dialog box will be displayed if the Agent is still monitoring targets. Click Continue. You can then remove all targets (usin