UNDOTABLESPACE and TABLESPACE TEMP in cold or hot backup database

Similar Questions

• is it OK to alter tablespace temp SYS of the running production database

  Dear,
  
  is it OK to alter tablespace temp of the user SYS of the running production database
  
  Business database version 10.2.0.5
  single instance on AIX
  
  We have two temp tablespace temp and temp2
  
  I'm trying to rebuild the index by using sys connection but its not working, cannot extend the temp tablepspace
  
  then I checked this system a default temp tablespace is of a size of 2 GB
  
  on the other hand, all other schemas has (including the owner of the index) have the temp of larger size.
  
  
  He suggests to change the tablespace temp of SYS.

  Ok. Then the answer is Yes, change the SYS temp tablespace should not be a problem. If you use SYS to reconstructions of index maintenance is another story. In any case, Yes, change the tablespace temp should not be a problem. Other sessions of this user would continue using the old tablespace until their completed transaction. New transactions will begin using the newly designated temp tablespace.

  Hope that helps,

  -Mark

• HOT backup database 10g express edition

  Dear Sir
  I use oracle database 10g express edition with 3.2.1 apex.
  
  I'm planing to db.here hot backup entire database is 24 x 7 running... fashion archive
  Info
  
  pFile, control, password file
  System datafile
  SYSAUX datafile
  Undo tablespace file
  temporary tablespace file
  redo log files
  application data tablespace file
  application index tablespace file
  
  for backup of the entire database HOT including apex WORKSPACE... which tablespace or files are REQUIRED for backup?
  
  Thank you
  Engr.M.K Chowdhury

  Hello

  To be convinced, you can do the following:

  alter database begin backup;
  

  Then, you check the backup status of your datafilles with the following query:

  select file#, status
  from v$backup
  order by file#;
  

  If the status is ACTIVE, this means that the data files are in backup mode, and you can copy them.

  The redologs online, you can save them but this is not mandatory, because you have logs archived.

  It is important to get all archived logs generated during (and after) the backup.

  To do this, you can run the following right after the hot data files backup:

  alter system archive log current;
  

  It will generate a log archived that you need to include in your backup.

  If you lose all your data (including the redologs online), after you restore the data files, you need to retrieve
  the database. During this operation, you apply all archived logs and then you reset the redologs. It is a
  incomplete recovery.

  However, for the online redo logs, it is important to multiplex to another disk. So, if you lose members on
  a single disk, you can perform a full restore with their copy on the second disc.

  Hope this helps.
  Best regards
  Jean Valentine

• Restored coldbackup and trouble with tablespace TEMP

  Hi, I've successfully restored from a coldbackup on solaris. (oracle 9.2)
  I can connect to databases using toad, query the database, but when I try to take an export or something I got the error
  
  EXP-00056: ORACLE error 1157
  ORA-01157: cannot identify/lock data file 203 - see DBWR trace file
  ORA-01110: data file 203: ' / sun2int1/oracle92/app/oracle/product/9.2.1/oradata/TPRS/temp03.dbf'
  ORA-06512: at "SYS." DBMS_LOB", line 424
  ORA-06512: at "SYS." Dbms_metadata", line 1140
  ORA-06512: at line 1
  EXP-00000: export completed unsuccessfully
  
  
  When I did the restore, I simply rename the data files and redo logs.
  But I was not rename the TEMP data file, as you can rename it with a command 'alter database rename file... ". »
  That's the problem!
  
  I plan to create a new default temp. tablespace and simply do it by default and a drop. but it does not work!
  
  I tried to run:
  
  CREATE a TABLESPACE TEMPORARY TMP4 TEMPFILE ' / oracleAS/TPRS/oradata/TPRS/temp4.dbf' SIZE 5 M REUSE AUTOEXTEND ON NEXT 1 M MAXSIZE unlimited
  EXTENT MANAGEMENT UNIFORM LOCAL 1 M SIZE;
  
  create tablespace temp01 temporary tempfile ' / oracleAS/TPRS/oradata/TPRS/temp01.dbf' size 100M;
  
  but they all hang! I wait, but nothing happens! (and the alert log will not connect anything too)
  
  Finally, I tried to drop the default tablespace and I couldn't let it go as I thought. (ORA-12906: cannot remove the temporary tablespace default)
  )
  
  So, im stuck and I think I should RENAME the data file for the temporary tablespace. How can I do this?
  
  Published by: merope on June 9, 2009 11:32

  I just found this link:
  http://dbaforums.org/Oracle/lofiversion/index.php?t4552.html
  which is something talk no problem of tablespace temp cold backup restore. In the end, it's say that the OP got solution due to the existence of a DDL trigger or something like that.

  HTH
  Girish Sharma

• Question regarding tablespace TEMP and the o/s file associated with.

  Hello
  
  I want to write a simple query that returns the existing storage space and files that are part of each tablespace.
  
  I tried the script / query:
  

  col tablespace_name format a15
  col datafile_name   format a35
  col MB              format 999999
  col "CreateSize MB" format 999999
  
  --
  -- following two queries present only to show the problem I'm running into
  --
  
  select ts#
       , name
    from v$tablespace;
  
  select ts#
       , name
    from v$datafile;
  
  --
  -- this ALMOST works
  --
  
  select t.name tablespace_name
       , t.bigfile
       , d.name datafile_name
       , d.bytes/(1024*1024) MB
       , d.create_bytes/(1024 * 1024) "Create Size MB"
    from v$tablespace t
    join v$datafile   d
   using (ts#)
  ;

  The last query fails to display the files associated with it and the TEMP tablespace.
  
  Question: what tables should I ask to get a complete picture (one that is not lack of TEMP and its files)?
  
  Thank you for your help,
  
  John.

  V$ tempfile

  dba_temp_files

  Here you get a temporary tablespace.

  Concerning
  Asif kabir

• excluding tablespace in the hot backup

  Hi master,
  
  I use oracle 10g on linux. We use the hot backup to date strategy to back up the database.
  
  
  but I think that I support too much data. I now have tablespeces in my database
  
  System
  users
  Temp
  Cancel
  index
  perfstat
  blob1
  tool
  etc. and default tablespace installed by oracle at installation time.
  
  I can I exclude some of the hot backup table spaces so that it consumes less time to back up the database?
  
  
  can I exclude spaces of temp, perstat and tool table?
  
  It will cause no impact on the database and?
  
  Thanks and greetings
  VD

  DON'T think to drop your UNDO tablespace. You use it to save "in front of your block images.
  Re: cancel

• Precisely how to find freespace in tablespace Temp

  DB version: 11.2.0.4

  Platform: Oracle Linux 6.4

  It seems that finding the space left in the temporary tablespace is not simple.

  Question1.

  These are the descriptions of column to see DBA_TEMP_FREE_SPACE

  ALLOCATED_SPACE: Total allocated space, in bytes, including the currently allocated space

  and used and the space that is currently allocated and available for reuse

  Free_space: Total free space available in bytes, including the space which is currently assigned and available for

  reuse and the space that is currently not allocated

  http://docs.Oracle.com/CD/E11882_01/server.112/e40402/statviews_5062.htm#REFRN23627

  I'm not native English, but aren't the words in red above for the column ALLOCATED_SPACE a wrong repetition?

  Question2. In 10g, when you see zero space left in the Temp tablespace, allows us to add more space to the tablespace TEMP immediately to prevent ORA-1652: unable to extend temp segment . 11 g, is there an architectural change by what TEMP segments are recycled internally (like UNDO segments) so that we don't have to worry much when we see the 0 space in tablespace temp?

  Question3. For the same database, the results of two queries are listed below. The news of freespace vary between QueryA and QueryB.

  Which is the correct output; QueryA or QueryB?

  -QueryA using dba_temp_free_space

  Select nom_tablespace,

  totalGB tablespace_size/1024/1024/1024,

  AllocSpaceGB ALLOCATED_SPACE/1024/1024/1024,

  free_space/1024/1024/1024 FreeSpaceGB

  of dba_temp_free_space;

  NOM_TABLESPACE TOTALGB ALLOCSPACEGB FREESPACEGB

  ------------------------------ ---------- ------------ -----------

  TEMP 125.99707 125.748047 69.9150391

  -QueryB using v$ sort_segment

  SELECT A.tablespace_name, D.gb_total, tablespace

  SUM (A.used_blocks * D.block_size)/1024/1024/1024 gb_used,)

  D.gb_total - SUM (A.used_blocks * D.block_size)/1024/1024/1024 gb_free)

  V $ sort_segment A.

  (

  SELECT B.name, C.block_size, SUM (C.bytes)/1024/1024/1024 gb_total

  V $ tablespace B, v$ tempfile C

  WHERE B.ts # = C.ts #.

  B.name GROUP, C.block_size

  ) D

  WHERE

  D.name = A.tablespace_name

  GROUP A.tablespace_name, D.gb_total;

  TABLESPACE GB_TOTAL GB_USED GB_FREE

  ------------------------------- ---------- ---------- ----------

  TEMP 125.99707 22.6992188 103.297852

  So, this could mean that oracle will be reuse TEMP segments internally and Temp space needs to be increased if

  you see errors ORA-1652 in the alerts log. Right?

  
  

  I rarely answer even in this case.  It is usually a transient problem with enriched work.  Only when it becomes quite persistent to impact business operations should I address it.  When I receive an event, the first thing we do is to go to the guy in charge of the related enterprise application and ask if his phone rings.  If this isn't the case, I don't worry about this. And even if it causes a business problem, the solution may be to increase the size of the TS but to identify a particularly evil-wise query.  The last time that I had to deal with this error was due to a broad and complex query generating a large intermediate result set.  The solution should not continue to increase the TEMP TS (which turned out be "whack-a-mole") but to create a materialized view to reduce the amount of data that had to be picked up and joined running.

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

  Hi all

  We receive ora 1652 error because since a few days, I increased the temporary table space for nearly 20 GB, but it still keeps to launch error

  Following errors written to the alert log file. Please check

  **********************************************************************

  Date: 26/12/13 Thursday 22:44:01

  **********************************************************************

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

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

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

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

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

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

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

  After some research, I found that query below is causing such huge operation & the invasion of the temporary space

  Select distinct s.serialnr, s.shipdate, s.cpc, s.country, s.description, s.soldt

  oparty, s.shiptoparty, s.ean_code, registration_crm_serial_n s.shipserialnr

  Join s Pascale registration_crm_serial_number s2 left s.serialnr = s2.shipseria

  NRL where (s2.serialnr =: 1 or s.serialnr =: 2) and s.shipserialnr is null

  I have only 10 GB of space left on my mount point and may not increase any more space for the temporary table space.

  version of database-10 g

  one question und an additional comment:

  1. is the separate necessary? This is the reason for sorting - and when I see a distinct, I always start to think if it is useful...

  2. an outer join with:

  left outer join t2 t1 (t1.col1 = t2.col1) where t2.col2 = 'something '.

  is therefore more an outer join for the t2.col2 condition = 'something' deletes all attachments outside your result NULL values

• Tablespace Temp created primary not replicated to standby mode

  Hello
  
  I configured Oracle 9i data guard recently, while doing, that I was forced to restructure primary db since maxlog files was 5, so I used backup controlfile to trace and changed the maxlogfiles to 6 and then transported the remaining steps. While I was using the trace file and restructuring of the Db, I did not notice that I missed to add the temporary file and moving it in standby mode. Yest.Day once get a team request error, that I created a new tablespace temp and logs switch made, however this tablespace temp tempfile was not copied to the standby server. Does this cause anything serious or can I do now to copy it in standby? Only the manual copy with primary db shutdown or any other means?

  standby
  SQL > SELECT NAME FROM V$ TEMPFILE;

  no selected line

  Use the commands below

  SQL > alter tablespace add tempfile ' D:\ORACLE\ORADATA\CTSOC\TEMPNEW01. DBF' size 31457280;

  If you take controlfile trace (or) metadata, you can see command DDL that too.
  Thank you.

• create tablespace temp with parameters

  It's recommended to create tablespace temp with parameter (autoextend, maxbytes, maxblock and increment_by). ?
  
  If Yes, please help me with the syntax of the command.
  
  Kind regards.

  Please read the documentation before posting similar questions.

  CREATE TABLESPACE
  http://download.Oracle.com/docs/CD/E11882_01/server.112/e17118/statements_7003.htm#SQLRF01403

  CREATE TABLESPACE: examples
  http://download.Oracle.com/docs/CD/E11882_01/server.112/e17120/omf003.htm#ADMIN11501

  Thank you
  Hussein

• alter tablespace temp failed

  C:\Documents and Settings\Administrateur > sqlplus
  
  SQL * more: Release 8.1.7.0.0 - Production on Mon Dec 13 12:56:25 2010
  
  (c) Copyright 2000 Oracle Corporation. All rights reserved.
  
  Enter the user name: sys as sysdba
  Enter the password:
  
  Connected to:
  Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
  With the partitioning option
  Release 8.1.7.0.0 - Production jserver
  
  SQL > set linesize 3333
  SQL > select * from dba_tablespaces;
  
  NOM_TABLESPACE INITIAL_EXTENT NEXT_EXTENT MIN_EXTENTS MAX_EXTENTS PCT_INCREASE MIN_EXTLEN STATUS LOGGING EXTENT_MAN DISTRIBUTION CONTENT PLU
  ------------------------------ -------------- ----------- ----------- ----------- ------------ ---------- --------- --------- --------- ---------- --------- ---
  RECORD PERMANENT ONLINE SYSTEM 65536 65536 1 2147483645 50 65536 DICTIONARY USER NO.
  RECORD PERMANENT 524288 524288 8 4096 50 524288 DICTIONARY USER NO. RBS ONLINE
  RECORD PERMANENT 131072 131072 1 4096 0 131072 DICTIONARY USER NO. USERS ONLINE
  TEMP 65536 65536 1 0 65536 TEMPORARY USER NO. DICTIONARY ONLINE REGISTRATION
  TOOLS 32768 32768 1 4096 0 32768 CONSIGNMENT PERMANENT ONLINE DICTIONARY USER NO.
  RECORD PERMANENT ONLINE 131072 131072 1 4096 0 131072 DICTIONARY USER NO. INDX
  RECORD PERMANENT DRSYS 65536 65536 1 2147483645 50 65536 USER NO. DICTIONARY ONLINE
  
  7 selected lines.
  
  SQL > alter tablespace temp add tempfile 'E:\oracle\product\10.2.0\oradata\temp03.dbf' size 12 M;
  alter tablespace temp add tempfile 'E:\oracle\product\10.2.0\oradata\temp03.dbf' size 12 M
  *
  ERROR on line 1:
  ORA-03217: invalid option to alter the TEMPORARY TABLESPACE
  
  
  SQL >

  oracleRaj wrote:
  any solution... ??

  You must upgrade the database 11g, Execute following and post result it

  alter tablespace temp add datafile 'E:\oracle\product\10.2.0\oradata\temp03.dbf' size 12M;
  

• Question of Tablespace Temp datafile.

  Hi Oracle gurus,
  
  the problem occurred when my file temp01.dbf to increase the size of certain MBs to 30 GB! (Within weeks)
  without doing RnD on advice, datafile temp01.dbf has been deleted! ,
  now a text file has been created, I renamed it with the same name 'temp01.dbf '!
  
  now my tasks fail with the error:
  
  1157: 64000: java.sql.SQLException: ORA-01157: cannot identify/lock data file 201 - see DBWR trace file
  ORA-01110: data file 201: ' C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\TEMP01. DBF'
  
  I tried to add a data file over to the storage space according to the steps below:
  1. connect to sqlplus DBA (user sys)
  2. stop; -Removed database and Oracle Instance will stop.
  3. start; -Oracle instance started.
  4 run this query
  alter tablespace temp add datafile
  ' C:\oracle\product\10.2.0\oradata\orcl\TEMP02. DBF' SIZE 32 M;
  
  but still the error points to Temp01.
  
  The funny part, I wrote here that I don't get the name of the data file anywhere in the comic book.
  
  I've run this query below
  
  SELECT FILE_NAME IN DBA_DATA_FILES;
  
  and there is no name of data file with "Temp01" or "Temp02".
  
  I get the name 'TEMP' Tablespace when performing "SELECT TABLESPACE_NAME FROM DBA_TABLESPACES";
  
  to add more of what the above
  
  I tried to delete the file with the name 'TEMP01. DBF. "
  by running
  
  alter tablespace temp drop datafile
  ' C:\oracle\product\10.2.0\oradata\orcl\TEMP01. DBF';
  
  I get the following error:
  ORA-03219: Tablespace 'TEMP' is managed by dictionary, offline or temporary
  
  This storage space (TEMP) is temporary (Default) and his allocation_type is uniform
  
  
  I'm looking for
  
  1 remove the Temp01 data file and rename the temp02 with her.
  2 allow the name of auto extension datafile renamed as well as default data temp file features.
  
  I'm at the point of no return?..... .i am new to this level of work... I tried to solve the problem by taking the forumns References... somwhr but still missing...
  
  Need help to solve this problem.

  Hello

  4 run this query
  alter tablespace temp add datafile
  ' C:\oracle\product\10.2.0\oradata\orcl\TEMP02. DBF' SIZE 32 M;

  but still the error points to Temp01.

  the query should be as below

  ALTER TABLESPACE
  Add TEMPFILE '' SIZE M;
  example:
  ALTER TABLESPACE temp_new
  Add TEMPFILE ' / u02/oradata/tempnew02.dbf' SIZE 200 M;

  >

  The part funny, I noted here that I don't get the name of the file of data anywhere in the DB.

  I've run this query below

  SELECT FILE_NAME IN DBA_DATA_FILES;

  and there is no name of data file with "Temp01" or "Temp02".

  We are unable to display a temporary file in dba_data_files... It's funny...

  Use tempfile $ v and v$ temp_space_header to view a temporary file...

  to make offline / online
  ALTER DATABASE TEMPFILE '' offline / online;

  MAKE USE OF THE TEMPORARY TABLESPACE DEFAULT

  ALTER TABLESPACE TEMPORARY for executives from the DATABASE default;

  the use of thiese views

  SELECT *.
  FROM database_properties
  Property_name WHERE = 'DEFAULT_TEMP_TABLESPACE ';

  SELECT file_name, nom_tablespace
  FROM dba_temp_files;

  Kind regards
  Deepak

• Tablespace TEMP too small

  Hi all
  
  
  We have a database Oracle 10.2.0.4 Reporting, each batch of al night data is refreshed from production databases.
  For this update this database uses complex Materialized View definitions.
  
  We continue to recently short TEMP tablespace during the updating of these MV. The TEMP tablespace has recently increased several times (in the past months 15 GB to 25 GB total).
  The great MV is only 3 GB big. Especially one that has lacked tablespace TEMP last night is only 1 GB big.
  The error message:
  
  ORA-12008: error path refresh materialized view
  ORA-12801: error reported in the parallel query P002 Server
  ORA-01652: unable to extend temp segment of 64 in tablespace TEMP
  
  Can someone tell me what could cause this behavior?
  
  Some features:
  
  Oracle 10.2.0.4
  Platform: AIX 5.3 TL06
  
  SGA_TARGET = 3504M
  PARALLEL_MAX_SERVERS = 8
  temp_tablespace_size = 25600 MB
  
  Thanks in advance

  It seems that it is just the pure-grunt that are necessary to update this particular MV which is the single drain on the space. Of the top line of the PLAN to EXPLAIN:

  SELECT STATEMENT SELECT cost: * 278 496 * bytes: * 13,752,541,260 * cardinality: * 18,864,940 *.

  The statistics are up-to-date, and these estimates are reasonably accurate, more than 13 billion bytes of data are involved and close to 19 million lines. And from him alone, it seems that the temp space required is not particularly excessive.

  Are the statistics on the base to update tables (dwh_products_dim, dwh_months_dim, dwh_customers_dim, dwh_financial_fct)? And have you tried to run it manually with parallelism turned off?

  And, have you ever tried to set up a quick refresh?

  Either way, I wouldn't be too concerned with the size of the end of the MV and how this could be a determinant of temporary space in the materialization of this one, which will be generally the smallest to the largest being the amount of aggregation in the source query.

  Published by: Seanmacgc on April 15, 2009 03:01

• Doubt about tablespace temp

  Hi all
  
  DB version: 9.2.0.4.1
  version of the operating system: windows 2003 server sp2 (64-bit)
  
  the application team runs a job of loading each month which requires more temp tablespace.
  so every time my colleague will create new tablespace temp with 30 GB in size and makes it as default.
  He will be too old (old temp is also 30 GB).
  
  (1) if we do not create a new, old temp will be reused?
  (2) is it a bug in this version so that temp is not re-used? (unfortunately, my colleague don't know the answers for these)
  
  also, according to my understanding, oracle will not release tablespace temp paques1861 once the work is completed. Instead it is attributed to another transaction when required.
  Please correct if I am wrong.
  
  Thanks in advance.

  Glance,

  It's pretty simple: just as it is easy to become addicted to alcohol and hard to get rid of him, it is easy to increase a tablespace and hard to reduce its size.
  When you have
  -SQL with the runaway temporary use
  AND
  -you are convinced Oracle must release tablespace temp (which it doesn't)
  you use measures like your colleague has set up.

  Apart from wasting your time (you'd better give that SQL), you do nothing.

  Oracle does not release space for some reason:
  outside the allocation and release of the extents over and over again are very expensive.
  You want to avoid that.

  --------
  Sybrand Bakker
  Senior Oracle DBA

• ORA-01652 in Tablespace TEMP

  Hello
  
  We get the following errors:
  
  RMAN > overlap archivelog all;
  
  
  
  from full resynchronization of the recovery catalog
  
  RMAN-00571: ===========================================================
  
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  
  RMAN-00571: ===========================================================
  
  RMAN-03002: failure of command of overlap at 2009-01-07 14:26:10
  
  RMAN-03014: implicit recovery catalog Resync failed
  
  RMAN-03009: resync command failed complete default channel at 2009-01-07 14:26:10
  
  ORA-01652: unable to extend segment in tablespace temp
  
  
  
  RMAN >
  
  We tried to increase the size of the TEMP tablespace, but this operation keeps using the set temp tablespace. It's the temp tablespace in the target database that fills.
  We cannot continue to increase the size of the ts TEMP to fill the disk.
  We also tried to create a new repository, but it had the same result.
  
  I think that there is something in the database tables, as one of our backups used the control target as its repository file. Should I remove the entries in these tables in the tablespace target to make the repository think that there is no re-synchronization to do?
  
  Kind regards
  Tim.

  See this metalink note:

  Record from database in RMAN fails with RMAN-03002, RMAN-03014 and ORA-01652
  DOC - ID: 469327.1

  Even if you run another command, the error of the battery is exactly the same.

  Werner