Skip to main content

TEMP Tablespace Usages and Monitoring


<<Back to DB Administration Main Page

What is TEMP Tablespace?

A temporary tablespace contains transient data that persists only for the duration of a
session. No permanent schema objects can reside in a temporary tablespace. A temp
file stores temporary tablespace data.

Types of Temp Tablespace

Starting from 12.2 Temporary tablespaces can be shared or local.

How to Find if a Tablespace is shared or local

SQL>select TABLESPACE_NAME,SHARED from DBA_TEMP_FILES where upper (TABLESPACE_NAME)=upper('&TABLESPACE_NAME');

What is Default Temporary Tablespaces

Every database user account is assigned a default shared temporary tablespace. If the
database contains local temporary tablespaces, then every user account is also
assigned default local temporary tablespace. A user query can access either shared or local temporary tablespace.
After the database accesses a temporary tablespace for a query, it does not switch to a different one.

How to find the default global temporary tablespace for the database

SQL>select PROPERTY_NAME,PROPERTY_VALUE from database_properties where PROPERTY_NAME like '%TEMP%';

How to find the temporary tablespaces assigned to an User

SQL> select USERNAME,TEMPORARY_TABLESPACE,LOCAL_TEMP_TABLESPACE from dba_users where upper(username) = upper('&Username');

How to create a Temporary tablespace

By default shared Temporary tablespace is created
SQL>  create temporary tablespace TEMP_TEST  tempfile '+DATA' size 10M;

Tablespace created.

How to Change Default Temporary Tablespace of the database

SQL> ALTER DATABASE DEFAULT TEMPORARY TABLESPACE TEMP_TEST;

How to Increase TEMP tablespace size

SQL> alter tablespace TEMP_TEST add tempfile '+DATA' size 200M;
Tablespace altered.

Changing the default behavior of TABLESPACE

You can change the default behavior of temp tablespace by changing the following hidden parameters.

Parameter Name   Default Value    Description
_force_local_temp  FALSE     for testing only   Forces temporary tablespaces to be LOCAL
_prefer_local_temp  FALSE     Use Local Temp as preferred default tablespace


NOTE: oracle does not recommend to change any hidden parameter until it recommends to do so.

How to drop the tempfile from temp tablespace

Find the Tempfile name to be dropped
SQL>  select TABLESPACE_NAME,FILE_NAME,STATUS from dba_temp_files where TABLESPACE_NAME='TEMP_TEST';
TABLESPACE_NAME                FILE_NAME                                                    STATUS
------------------------------ ------------------------------------------------------------ -------
TEMP_TEST                      +DATA/TST1TP/TEMPFILE/temp_test.600.1004622233               ONLINE
TEMP_TEST                      +DATA/TST1TP/TEMPFILE/temp_test.607.1004616665               ONLINE


drop the tempfile

SQL> alter database tempfile '+DATA/TST1TP/TEMPFILE/temp_test.607.1004616665' drop including datafiles;
Database altered.

How to Drop the temp tablespace

SQL> drop tablespace TEMP_TEST;
or
SQL> drop tablespace TEMP_TEST including contents and datafiles;
Tablespace dropped.

How to Monitor the Utilization of TEMP Tablespace

Check Current Utilization of TEMP Tablespace
SQL>   SELECT TABLESPACE_NAME,
         CON_ID,
         ROUND (SUM (BYTES) / 1048576, 1)                 SIZE_MB,
         ROUND (SUM (MAXBYTES) / 1048576, 1)              MAXSIZE_MB,
         ROUND (SUM (USER_BYTES) / 1048576, 0)            USED_MB,
         ROUND (SUM (USER_BYTES) / SUM (MAXBYTES) * 100, 1) USED_PCT
    FROM CDB_TEMP_FILES
GROUP BY TABLESPACE_NAME, CON_ID
ORDER BY 1;

Check Which User is Consuming Space of TEMP Tablespace
SQL>   SELECT USERNAME,
         SQL_ID,
         SEGTYPE,
         EXTENTS,
         BLOCKS
    FROM V$TEMPSEG_USAGE
ORDER BY USERNAME

Top 5 TEMP TABLESPACE Consumer Over Laster 7 Days 
SQL>   SELECT T.SAMPLE_TIME,
         T.SQL_ID,
         T.TEMP_MB,
         T.TEMP_DIFF,
         S.SQL_TEXT
    FROM (  SELECT
                   TRUNC (SAMPLE_TIME) SAMPLE_TIME,
                   SQL_ID,
                   SUM (TEMP_MB) TEMP_MB,
                   SUM (TEMP_DIFF) TEMP_DIFF,
                   ROW_NUMBER ()
                   OVER (PARTITION BY TRUNC (SAMPLE_TIME)
                         ORDER BY SUM (TEMP_MB) DESC NULLS LAST)
                       AS RN
              FROM (SELECT SAMPLE_TIME,
                           SESSION_ID,
                           SESSION_SERIAL#,
                           SQL_ID,
                           TEMP_SPACE_ALLOCATED / 1024 / 1024 TEMP_MB,
                             TEMP_SPACE_ALLOCATED / 1024 / 1024
                           - LAG (TEMP_SPACE_ALLOCATED / 1024 / 1024, 1, 0)
                                 OVER (ORDER BY SAMPLE_TIME)
                               AS TEMP_DIFF
                      FROM DBA_HIST_ACTIVE_SESS_HISTORY
                     WHERE 1 = 1
                                )
          GROUP BY
                  TRUNC (SAMPLE_TIME), SQL_ID) T
         LEFT JOIN V$SQLAREA S ON S.SQL_ID = T.SQL_ID
   WHERE 1 = 1 AND RN <= 1 AND SAMPLE_TIME >= TRUNC (SYSDATE) - 7
ORDER BY SAMPLE_TIME DESC, TEMP_MB DESC

How to Shrink TEMP tablespace

SQL> alter tablespace LOCAL_TEMP_TEST shrink space keep 100m;
Tablespace altered.

How to Shrink Tempfile

SQL> ALTER TABLESPACE LOCAL_TEMP_TEST SHRINK TEMPFILE '+DATA/TST1TP/822B1C132B1804A6E0530601A8C00CF1/TEMPFILE/local_temp_test.603.1004621635' KEEP 30M;
Tablespace altered.

Comments

Popular posts from this blog

DataPump Import Of Object Types Fails With Errors ORA-39083 ORA-2304 Or ORA-39117 ORA-39779

<<Back to Oracle DATAPUMP Main Page ORA-39083: Object type TYPE:"TEST_QA01"."LOG_RECORD" failed to create with error: ORA-02304: invalid object identifier literal Import: Release 12.1.0.2.0 - Production on Tue May 29 07:59:12 2018 Copyright (c) 1982, 2014, Oracle and/or its affiliates.  All rights reserved. Connected to: Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production With the Partitioning, Real Application Clusters, Automatic Storage Management, Oracle Label Security, OLAP, Advanced Analytics and Real Application Testing options Master table "SYSTEM"."SYS_IMPORT_FULL_01" successfully loaded/unloaded Starting "SYSTEM"."SYS_IMPORT_FULL_01":  system/********@TEST_QA parfile=import_TEST.par Processing object type SCHEMA_EXPORT/USER Processing object type SCHEMA_EXPORT/SYSTEM_GRANT Processing object type SCHEMA_EXPORT/ROLE_GRANT Processing object type SCHEMA_EXPORT/DEFAULT_ROLE Pr

ORA-28374: typed master key not found in wallet

<<Back to Oracle DB Security Main Page ORA-46665: master keys not activated for all PDBs during REKEY SQL> ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL ; ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL * ERROR at line 1: ORA-46665: master keys not activated for all PDBs during REKEY I found following in the trace file REKEY: Create Key in PDB 3 resulted in error 46658 *** 2019-02-06T15:27:04.667485+01:00 (CDB$ROOT(1)) REKEY: Activation of Key AdnU5OzNP08Qv1mIyXhP/64AAAAAAAAAAAAAAAAAAAAAAAAAAAAA in PDB 3 resulted in error 28374 REKEY: Keystore needs to be restored from the REKEY backup.Aborting REKEY! Cause: All this hassle started because I accidently deleted the wallet and all wallet backup files too and also forgot the keystore password. There was no way to restore the wallet back. Fortunately in my case the PDB which had encrypted data was supposed to be deco

How to Find VIP of an Oracle RAC Cluster

<<Back to Oracle RAC Main Page How to Find Out VIP of an Oracle RAC Cluster Login clusterware owner (oracle) and execute the below command to find out the VIP hostname used in Oracle RAC $ olsnodes -i node1     node1-vip node2     node2-vip OR $ srvctl config nodeapps -viponly Network 1 exists Subnet IPv4: 10.0.0.0/255.255.0.0/bondeth0, static Subnet IPv6: Ping Targets: Network is enabled Network is individually enabled on nodes: Network is individually disabled on nodes: VIP exists: network number 1, hosting node node1 VIP Name: node1-vip VIP IPv4 Address: 10.0.0.1 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes: VIP exists: network number 1, hosting node node2 VIP Name: node2-vip VIP IPv4 Address: 10.0.0.2 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes:

How to Power On/off Oracle Exadata Machine

<<Back to Exadata Main Page How to Power On/off Oracle Exadata Machine Oracle Exadata machines can be powered on/off either by pressing the power button on front of the server or by logging in to the ILOM interface. Powering on servers using  button on front of the server The power on sequence is as follows. 1. Start Rack, including switches  Note:- Ensure the switches have had power applied for a few minutes to complete power on  configuration before starting Exadata Storage Servers 2.Start Exadata Storage Servers  Note:- Ensure all Exadata Storage Servers complete the boot process before starting the   database servers 3. Start Database Servers Powering On Servers Remotely using ILOM The ILOM can be accessed using the Web console, the command-line interface (CLI), IPMI, or SNMP. For example, to apply power to server dm01cel01 using IPMI, where dm01cel01-ilom is the host name of the ILOM for the server to be powered on, run the

How to Attach to a Datapump Job and Check Status of Export or Import

<<Back to Oracle DATAPUMP Main Page How to check the progress of  export or import Jobs You can attach to the export/import  job using ATTACH parameter of oracle datapump utility. Once you are attached to the job you check its status by typing STATUS command. Let us see how Step1>  Find the Export/Import Job Name You can find the datapump job information from  DBA_DATAPUMP_JOBS or  USER_DATAPUMP_JOBS view. SQL> SELECT OWNER_NAME,JOB_NAME,OPERATION,JOB_MODE,STATE from DBA_DATAPUMP_JOBS; OWNER_NAME JOB_NAME                       OPERATION            JOB_MODE   STATE ---------- ------------------------------ -------------------- ---------- ---------- SYSTEM     SYS_EXPORT_FULL_02             EXPORT               FULL       EXECUTING OR You can also find the job name for export/import in logfile in beginning itself. Step2>Attach to the Job and check status One you get the Export/Import Job Name attach the job and check its status. You can attach or det

How to Create Pfile from Spfile and Vice Versa

<<Back to DB Administration Main Page There are instances when a DBA need to start the database using pfile, for example to trouble an instance startup error or to validate init file post parameter changes etc. In such situations you can create a pfile from spfile and once you are done with your changes you can create spfile from updated/modified pfile to start the database. How to Create Pfile from Spfile As sysdba execute following command  SQL> create pfile='/tmp/initOrcl.ora' from spfile; How to Create SPfile from Pfile As sysdba execute following command  SQL> create spfile from  pfile='/tmp/initOrcl.ora'; You can also create the pfile directly from memory How to Create Pfile from Memory As sysdba execute following command  SQL> create  pfile='/tmp/initOrcl.ora' from memory;

How to export only data or only metadata using expdp

<<Back to Oracle DATAPUMP Main Page CONTENT parameter of expdp let you select whether you want to export only data or only metadata or both Default : ALL Syntax and Description CONTENT=[ALL | DATA_ONLY | METADATA_ONLY] DATA_ONLY exports only table row data; no database object definitions are exported. METADATA_ONLY exports only database object definitions; no table row data is exported. Exporting metadata only  $ cat exp_full_pdb01.par directory=dump dumpfile=EXP_PDB01_FULL%U.dmp logfile=EXP_PDB01_FULL.log full=y CONTENT=METADATA_ONLY $ expdp system@PDB01 parfile=exp_full_pdb01.par Exporting data only directory=dump dumpfile=EXP_PDB01_FULL%U.dmp logfile=EXP_PDB01_FULL.log full=y CONTENT=DATA_ONLY $ expdp system@PDB01 parfile=exp_full_pdb01.par

Step by Step How to Configure Software Keystore/ Oracle Wallet

<<Back to Oracle DB Security Main Page How to Configure a Software Keystore A software keystore is a container that stores the Transparent Data Encryption master encryption key. To configure a software Keystore follow the steps below. Step 1: Set the Keystore Location in the sqlnet.ora File You can store the software keystore (also known as wallet) in file system or in ASM Diskgroup. Does not matter where you want to store the keystore you have modify the sqlnet.ora and make an entry accordingly Make an entry as shown below in $ORACLE_HOME/network/admin/sqlnet.ora file Example1: If Storing the Wallet in ASM ENCRYPTION_WALLET_LOCATION=  (SOURCE=(METHOD=FILE)    (METHOD_DATA=     (DIRECTORY= +DG_TST_DATA/$ORACLE_SID/wallet )    )  )   Example2: If Storing the Wallet in File System ENCRYPTION_WALLET_LOCATION=  (SOURCE=(METHOD=FILE)    (METHOD_DATA=     (DIRECTORY= /u01/dbatst1/admin/wallet/$ORACLE_SID)    )  ) NOTE: Ensure that the path you entered in  DIREC

ORA-15040: diskgroup is incomplete

<<Back to Oracle ASM Main Page ORA-15040: diskgroup is incomplete SQL> startup ORA-00099: warning: no parameter file specified for ASM instance ASM instance started Total System Global Area 1140850688 bytes Fixed Size                  8629704 bytes Variable Size            1107055160 bytes ASM Cache                  25165824 bytes ORA-15110: no diskgroups mounted Reason: The reason of this error is simply the ASM is not able to find the some or all the disks. Solution: Investigate and make all the disks available to ASM to mount the disk group. Make sure the disks has proper permissions. If you are using AFD check following services are online oracleacfs oracleadvm oracleoks  oracleafd   Source of Problem : Issue started after restart of the server After restarting the server when I tried to start the ASM instance its started throwing error.  ORA-15110: no diskgroups mounted Investigation in my Case Step1> ASM Logfile Scanning  Looked i

ORA-28365: wallet is not open while starting the database

<<Back to DB Administration Main Page ORA-28365: wallet is not open Encountered while Starting the Database $ srvctl start instance -d CDB001 -i CDB0011 PRCR-1013 : Failed to start resource ora.cdb001.db PRCR-1064 : Failed to start resource ora.cdb001.db on node node1.oracle.com CRS-5017: The resource action "ora.cdb001.db start" encountered the following error: ORA-28365: wallet is not open . For details refer to "(:CLSN00107:)" in "/u01/app/oracle/diag/crs/node1.oracle.com/crs/trace/crsd_oraagent_oracle.trc". CRS-2674: Start of 'ora.cdb001.db' on 'node1.oracle.com' failed Solution : Start the instance in mount mode SQL> startup mount; ORACLE instance started. Total System Global Area 2147483648 bytes Fixed Size                  2926472 bytes Variable Size            1392511096 bytes Database Buffers          738197504 bytes Redo Buffers               13848576 bytes Database mounted. Check Wallet status set linesiz