1st: search folders for ilnk*.dbf to find all database files. http://www.orafaq.com/faqdba.htm http://www.google.com/search?as_q=sql+alter+database+resize&num=10&hl=en&btnG=Google+Search&as_epq=&as_oq=&as_eq=&lr=&as_ft=i&as_filetype=&as_qdr=all&as_nlo=&as_nhi=&as_occt=any&as_dt=i&as_sitesearch=&as_rights=&safe=images sql alter database resize ========================= Has any one had any luck importing an Ilink 3.2 dump file into 3.3. I can migrate my database just fine. But if I try to import a 3.2 dump file into a new 3.3 empty or existing installation I get errors indicating the overflow of the TEMP tablespace. I have set my tables to auto-extend but that didn't help as this TEMP space in 3.3 is not a normal table that can be listed and modified. Typical error below: Importing contents of "F:ptcbackups1METADATA.DMP" ... List of error messages: IMP-00017: following statement failed with ORACLE error 1652: IMP-00003: ORACLE error 1652 encountered ORA-01652: unable to extend temp segment by 128 in tablespace TEMP IMP-00017: following statement failed with ORACLE error 1652: IMP-00003: ORACLE error 1652 encountered ORA-01652: unable to extend temp segment by 128 in tablespace TEMP IMP-00017: following statement failed with ORACLE error 1652: IMP-00003: ORACLE error 1652 encountered ORA-01652: unable to extend temp segment by 128 in tablespace TEMP IMP-00017: following statement failed with ORACLE error 1652: IMP-00003: ORACLE error 1652 encountered ORA-01652: unable to extend temp segment by 128 in tablespace TEMP IMP-00017: following statement failed with ORACLE error 1652: IMP-00003: ORACLE error 1652 encountered ORA-01652: unable to extend temp segment by 128 in tablespace TEMP IMP-00017: following statement failed with ORACLE error 2430: I also tried migrating a 3.2 installation to 3.3, which worked fine, then a few weeks later import a newer dump file from our production system into the converted 3.3 installation. Same errors. If you try to increase the TEMP tablespace via the DSMU, you get an error message indicating that table doesn't exist. Because that table is now located elsewhere. Customer service indicates they have not seen this error before and are investigating it for me. Any insights????? Bill Kunz MCAD Specialist > Alcon Laboratories, Inc. > (949) 753-6709 > william.kunz@alconlabs.com > > ========================= PTC Customer support came through again. Also heard the solution from Ray Stewart, an independent consultant. So thanks Lori and Ray. The solution was a special sql command for the temp table that is now created and managed locally. See Below: The command to resize the TEMP tablespace is as follows: alter database tempfile '' resize M; You can also use the same syntax to autoextend: alter database tempfile '' autoextend on; After turning auto extend on for this table the import worked perfectly. Thanks again, Bill Kunz MCAD Specialist > Alcon Laboratories, Inc. > (949) 753-6709 > william.kunz@alconlabs.com > > ========================= http://www.idevelopment.info/data/Oracle/DBA_tips/Tablespaces/TBS_3.shtml Resizing Temporary Tablespace by Jeff Hunter, Sr. Database Administrator -------------------------------------------------------------------------------- Contents Overview Dropping / Recreating Temporary Tablespace Method Drop Tempfile Command Method - (Oracle9i and higher) -------------------------------------------------------------------------------- Overview In many database configurations, the DBA will choose to allow their temporary tablespace (actually the tempfile(s) for the temporary tablespace) to autoextend. A runaway query or sort can easily chew up valuable space on the disk as the tempfiles(s) extends to accommodate the request for space. If the increase in size of the temporary tablespace (the tempfiles) gets exceedingly large because of a particular anomaly, the DBA will often want to resize the temporary tablespace to a more reasonable size in order to reclaim that extra space. The obvious action would be to resize the tempfiles using the following statement: SQL> alter database tempfile '/u02/oradata/TESTDB/temp01.dbf' resize 250M; alter database tempfile '/u02/oradata/TESTDB/temp01.dbf' resize 250M * ERROR at line 1: ORA-03297: file contains used data beyond requested RESIZE value Ouch. You next bounce the database and attempt the same statement only to be greeted with the same error! Several methods exist to reclaim the used space used for a larger than normal temporary tablespace depending on which release of Oracle you are running. The method that exists for all releases of Oracle is to simply drop and recreate the temporary tablespace back to its original (or another reasonable) size. If you are using Oracle9i or higher, you can apply another method which is to drop the large tempfile (which will drop the tempfile from the data dictionary AND the O/S file system) using the alter database tempfile '' drop including datafiles; command. Each method is explained below. -------------------------------------------------------------------------------- Dropping / Recreating Temporary Tablespace Method Keep in mind that the procedures documented here for dropping and recreating your temporary tablespace should be performed during off hours with no users logged on performing work. If you are working with a temporary tablespace in Oracle8i or a temporary tablespace in Oracle9i that is NOT the default temporary tablespace for the database, this process is straight forward. Simply drop and recreate the temporary tablespace: SQL> DROP TABLESPACE temp; Tablespace dropped. SQL> CREATE TEMPORARY TABLESPACE TEMP 2 TEMPFILE '/u02/oradata/TESTDB/temp01.dbf' SIZE 500M REUSE 3 AUTOEXTEND ON NEXT 100M MAXSIZE unlimited 4 EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M; Tablespace created. Oracle9i Default Temporary Tablespace The procedures above document how to drop a temporary tablespace that is not the default temporary tablespace for the database. You will know fairly quickly if the tablespace is a default temporary tablespace when you are greeted with the following exception: SQL> DROP TABLESPACE temp; drop tablespace temp * ERROR at line 1: ORA-12906: cannot drop default temporary tablespace In cases where the temporary tablespace you want to resize (using the drop/recreate method) is the default temporary tablespace for the database, you have several more steps to perform, all documented below. The first step you need to perform is create another temporary tablespace (lets call it TEMP2). The next step would be to remove the temporary tablespace you want to resize from being the default temporary tablespace (in our example, this will be a tablespace named TEMP) by making TEMP2 the default. Drop / recreate the TEMP tablespace to the size you want. Finally, make the newly created TEMP tablespace your default temporary tablespace for the database and drop the TEMP2 tablespace. A full example session is provided below: SQL> CREATE TEMPORARY TABLESPACE temp2 2 TEMPFILE '/u02/oradata/TESTDB/temp2_01.dbf' SIZE 5M REUSE 3 AUTOEXTEND ON NEXT 1M MAXSIZE unlimited 4 EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M; Tablespace created. SQL> ALTER DATABASE DEFAULT TEMPORARY TABLESPACE temp2; Database altered. SQL> DROP TABLESPACE temp INCLUDING CONTENTS AND DATAFILES; Tablespace dropped. SQL> CREATE TEMPORARY TABLESPACE temp 2 TEMPFILE '/u02/oradata/TESTDB/temp01.dbf' SIZE 500M REUSE 3 AUTOEXTEND ON NEXT 100M MAXSIZE unlimited 4 EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M; Tablespace created. SQL> ALTER DATABASE DEFAULT TEMPORARY TABLESPACE temp; Database altered. SQL> DROP TABLESPACE temp2 INCLUDING CONTENTS AND DATAFILES; Tablespace dropped. -------------------------------------------------------------------------------- Drop Tempfile Command Method - (Oracle9i and higher) If you are using Oracle9i or higher, another method exists that allows you to simply drop a tempfile. As with the above method, this should be performed during off hours with no users logged on performing work. The first step is to obtain the name of the tempfile to drop. For this example, my temporary tablespace name is TEMP and the name of the tempfile is /u02/oradata/TESTDB/temp2_01.dbf: SQL> SELECT tablespace_name, file_name, bytes 2 FROM dba_temp_files WHERE tablespace_name = 'TEMP'; TABLESPACE_NAME FILE_NAME BYTES ----------------- -------------------------------- -------------- TEMP /u02/oradata/TESTDB/temp01.dbf 13,107,200,000 The normal size of my temporary tablespace is 512MB which has always been more than adequate for this environment. A bad query, however, increased the size of this tablespace (my tempfile) to over 13GB and I would like to reclaim that space. In the example below, I simply drop and recreate the tempfile: SQL> ALTER DATABASE TEMPFILE '/u02/oradata/TESTDB/temp01.dbf' DROP INCLUDING DATAFILES; Database altered. SQL> ALTER TABLESPACE temp ADD TEMPFILE '/u02/oradata/TESTDB/temp01.dbf' SIZE 512m 2 AUTOEXTEND ON NEXT 250m MAXSIZE UNLIMITED; Tablespace altered. On some platforms (i.e. Windows 2000), it is possible for the tempfile to be deleted from DBA_TEMP_FILES but not from the hard drive of the server. If this occurs, simply delete the file using regular O/S commands. SQL> SELECT tablespace_name, file_name, bytes 2 FROM dba_temp_files WHERE tablespace_name = 'TEMP'; TABLESPACE_NAME FILE_NAME BYTES ----------------- -------------------------------- -------------- TEMP /u02/oradata/TESTDB/temp01.dbf 536,870,912 If users are currently accessing the tempfile you are attempting to drop, you may receive the following error: SQL> ALTER DATABASE TEMPFILE '/u02/oradata/TESTDB/temp01.dbf' DROP INCLUDING DATAFILES; ALTER DATABASE TEMPFILE '/u02/oradata/TESTDB/temp01.dbf' DROP INCLUDING DATAFILES * ERROR at line 1: ORA-25152: TEMPFILE cannot be dropped at this time As for the poor users who were using the tempfile, their transaction will end and will be greeted with the following error message: SQL> @testTemp.sql join dba_extents c on (b.segment_name = c.segment_name) * ERROR at line 4: ORA-00372: file 601 cannot be modified at this time ORA-01110: data file 601: '/u02/oradata/TESTDB/temp01.dbf' ORA-00372: file 601 cannot be modified at this time ORA-01110: data file 601: '/u02/oradata/TESTDB/temp01.dbf' If this happens, you should attempt to drop the tempfile again so the operation is successful: SQL> ALTER DATABASE TEMPFILE '/u02/oradata/TESTDB/temp01.dbf' DROP INCLUDING DATAFILES; Database altered. ========================= http://searchoracle.techtarget.com/tip/1,289483,sid41_gci1057867,00.html oracle basics http://searchoracle.techtarget.com/content/0,290959,sid41_gci1186587,00.html?int=off&Offer=ggcont8583&CMP=KNC-GoogleAdwords&HBX_PK=P_oracle+database+tutorial&HBX_OU=50 ilink error: http://www.dbforums.com/t977873.html C:\ptc\dataserver\intralink\bin\proimgr.bat