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

Starting and Stopping the Oracle Enterprise Manager Console

Starting and Stopping the Oracle Enterprise Manager Console To access the Oracle Enterprise  Manager Console from a client browser, the  dbconsole  process needs to be running on the server. The dbconsole process is automatically started after installation. However, in the event of a system restart,change in IP, or other changes, you can start it manually at the command line. To start the  dbconsole  process from the command line: Navigate into your  ORACLE_HOME/bin  directory. Run the following statement: ./emctl start dbconsole Additionally, you can stop the process and view its status. To stop the  dbconsole  process:          ./emctl stop dbconsole To view the status of the  dbconsole  process:         ./emctl status dbconsole -------------------------------------------------------------------------------------------------------

Query to check the OPTIMAL UNDO RETENTION

Query to check the OPTIMAL UNDO RETENTION _____________________________________________________________________________ SELECT d.undo_size / (1024 * 1024) "ACTUAL UNDO SIZE [MByte]",        SUBSTR(e.value, 1, 25) "UNDO RETENTION [Sec]",        ROUND((d.undo_size / (to_number(f.value) * g.undo_block_per_sec))) "OPTIMAL UNDO RETENTION [Sec]"   FROM (SELECT SUM(a.bytes) undo_size           FROM v$datafile a, v$tablespace b, dba_tablespaces c          WHERE c.contents = 'UNDO'            AND c.STATUS = 'ONLINE'            AND b.name = c.tablespace_name            AND a.ts# = b.ts#) d,        v$parameter e,        v$parameter f,        (SELECT MAX(undoblks / ((end_time - begin_time) * 3600 * 24)) undo_block_per_sec  ...

Solution of problem: Resultset Exceeds the Maximum Size (100 MB)

Solution of problem: Resultset Exceeds the Maximum Size (100 MB) I was running a select statement in PL/SQL Developer. it was a short query but the data volume that the query was fetching was huge. But when ever i Click the button Fetch Last Page or press 'ALT+End' button a message box comes after a while saying: Then I started looking for the exact reason of this sort of problem in Google. When I realized there was no direct solution in the web, I started looking the PL/SQL Developer Software menu and found the ultimate solution. The reason of this problem is there is a parameter of maximum result set size in PL/SQL Developer Software which is by default set to 100 MB. To change this parameter you have to go to the following location: 1. Goto Edit Menu and click ' PL/SQL Beautifier Options '. A new window will open. 2. Click SQL Window of " Window Types ". 3. Now Change the value of "Maximum Result Set Size( 0 is unlimited)"  ...