OEM 10g - reorganize tablespace error on invalid sort area size

Hi all,
When I try to reorganize a tablespace with OEM 10g, I get an error in the 3rd step (options) saying :
Invalid value for sort area size. The minimum value is 96 KB. My SGA management is set to AUTO.
Why this error on sort size area ?
Thanks for your help.

Found a workaround. ( Not a real answer to the "why" )
My settings were : pga_aggregate_target : 400 MB
work_area_policy : AUTO
Following the documentation the sort_area_size should then default to 20% of SGA ( which is 1200MB ), and should thus be 240 MB, largely sufficient I would think ...
I now changed the work_area_policy to MANUAL, and the sort_area_size to 100MB, and then it works fine.
If anyone would have an explanation for this, it is still most welcome !
Linde

Similar Messages

Pga and sort area size both are set in parameter file

Hello,
Both the pga and sort area size are set in the parameter file. Is this an issue? Are there conflicts? Can both be set and only pga will take effect? Db is 10.1.0.5.

hi,
might also be worth looking at metalink note Note:223730.1
rgds
Alan

Problem with 10G R2 installation (OUI - 10133 Invalid Staging Area) on W2K3

I'm getting a strange error installing 10G R2 Database on a Windows 2003 server. I get "OUI - 10133 Invalid Staging Area. There are no top level components for Windows NT, Windows 2000 available for installation in this staging area." This happens when I choose an Advanced installation or when I choose a starter database.
The funny thing is that I've performed this installation with this exact installation disk on a virtual server on my laptop with Windows 2003.
Also, I ran a quick test with the 10G R1 installation files and I don't get the error. I want to run tests on case insensitivity with LIKE searches (a new feature enabled in 10G R2) so I can't use 10G R1.

I have seen that problem frequently and it is because for some reason the installer doesn't like burned CD's. Copy all the staging files over to disk. I usually download the zip files onto a staging drive on the server, unzip, install, then delete the install files when I'm done if I need the space.
This has two major benefits: I don't run into the "staging area" error and the install only takes about 30 minutes compared to about 3 hours when installing from CD.

SORT ARE SIZE

SORT operations are performed in temporary segments, then why SORT_AREA_SIZE is required?
regards
wire

i've checked log files, they do not contain information in this concern, i think i've made a mess by asking lot of questions. i just want to know what exactly redo log files contain, do they contain all sql statements? and how can i view redo log files contents?
regards
wire

Sort Area Size in Automatic memory management

Hello All
I am aware that the AREASIZE is ignored of the PGA_AGGREGATE_TARGET is set.
So how is it possible that if we incrase the SORT_AREA_SIZE, the performance improves?
does this necessarily mean that the PGA_AGGREGATE_TARGET was not set to a proper value that it instead used the SORT_AREA_SIZE instead?
thanks

Hi,
If you have set workarea_size_policy=auto then under the automatic PGA memory management mode, sizing of work
areas for all sessions becomes automatic and the AREASIZE parameters are
ignored by all sessions running in that mode.
In auto mode if you change any AREASIZE parameters will be ignored.
If you want to manually handle ARASIZE then turnoff the Automatic pga memory by setting workarea_size_policy=MANUAL and then your changes to parameter will take effect but it's advisable to set pga to automatic.
To check whether your pga is set proper or not check v$pga_target_advice view
SELECT round(PGA_TARGET_FOR_ESTIMATE/1024/1024) target_mb,
ESTD_PGA_CACHE_HIT_PERCENTAGE cache_hit_perc,
ESTD_OVERALLOC_COUNT
FROM V$PGA_TARGET_ADVICE;
This will give you how your pga is set.
chirag

Table View : Sort='server' : Error=Invalid sort field type in "SORT ... AS

Hi ,
The Sort button does not work for GUID and it shows the error,
<b>Invalid sort field type in "SORT ... AS TEXT"</b>
How do I solve this problem?
Thanks and Best Regards,
Bindiya

Hi ,
Below is the code :
IF_HTMLB_TABLEVIEW_ITERATOR~GET_COLUMN_DEFINITIONS
==================================================
        ls_coldef-columnname              = 'PBI_C_VALUE_ID1'.
        ls_coldef-width                         = '150'.
        ls_coldef-title                           = 'Category I '.
        ls_coldef-tooltipheader              = 'Category I '.
        ls_coldef-wrapping                   = zcl_zsc_co=>sc_true.
        ls_coldef-edit                          = zcl_zsc_co=>sc_true.
        ls_coldef-sort                          = zcl_zsc_co=>sc_true.
        APPEND ls_coldef TO p_column_definitions.
        CLEAR ls_coldef.
==================================================
IF_HTMLB_TABLEVIEW_ITERATOR~RENDER_CELL_START
==================================================
    WHEN 'PBI_C_VALUE_ID1'.
      CREATE OBJECT lr_dropdown.
      lr_dropdown->id                 = p_cell_id.
      lr_dropdown->nameofkeycolumn    = 'PBI_C_VALUE_ID'.
      lr_dropdown->nameofvaluecolumn = 'SHORT_NAME'.
      lr_dropdown->selection          = <fs_row>-pbi_c_value_id1.
      lr_dropdown->disabled           = lv_disable.
      lr_dropdown->width              = '170'.
      GET REFERENCE OF mr_model_assign_sb_list->mr_model_pb_item_list->mr_model_def_category->mt_dropdown_cat_1_val INTO lr_dropdown->table.
      p_replacement_bee = lr_dropdown.
==================================================
NOTE: the data element of 'PBI_C_VALUE_ID' is RAW 16.
Thanks and Best Regards,
Bindiya

Oracle 8.1.5 Invalid Staging Area Error

I get an error message: Invalid staging area. There is no top level components for Windows NT available for installing
from this staging area. I installed this version successfully running win98, but i get this error with XP. I tried renaming the symcjit.dll
as suggested in some of the earlier posting with no success. Any help is appreciated.
Thanks,
Will

copy disk to hardrive in a temporary directory. go to properties for setup.exe (right click on file used to install oracle). Select the compatiblity tab. make sure the check box "run this program in compatibility mode" is checked. In combo box select windows 98.

Invalid initial heap size Problem with sdk1.4.2_03

Hi,
ich habe a troubling error with the java version 1.4.2_03.
I use an Ant Task to start a Weblogic Server (J2EE Server). For this, I use the following Ant code :
-----ANT CODE------------------------------------------------------------------------------------------------------------------------
<java classname="weblogic.Server" fork="true" failonerror="true" dir="${weblogic.domain.dir}">
<sysproperty key="bea.home" value="${bea.home.dir}"/>
<sysproperty key="weblogic.Name" value="${weblogic.admin.server.name}"/>
<sysproperty key="weblogic.management.username" value="${weblogic.user.name}"/>
<sysproperty key="weblogic.management.password" value="${weblogic.user.password}"/>
<sysproperty key="weblogic.ProductionModeEnabled" value="false"/>
<sysproperty key="java.security.policy" value="${weblogic.home.dir}\server\lib\weblogic.policy"/>
<sysproperty key="weblogic.security.SSL.trustedCAKeyStore" value="${weblogic.home.dir}\server\lib\cacerts"/>
<jvmarg value="-Xms32m -Xmx200m"/>
<classpath>
<pathelement path="${windows.classpath.wls}"/>
</classpath>
</java>
-----/ANT CODE------------------------------------------------------------------------------------------------------------------------
This Task perfectly works with the sdk java version 1.4.1_05, but I have the following message with the sdk java version 1.4.2_03 :
-----ERROR MESSAGE---------------------------------------------------
Invalid initial heap size: -Xms32m -Xmx200m
Could not create the Java virtual machine.
-----/ERROR MESSAGE---------------------------------------------------
The following parameter is anymore correct : <jvmarg value="-Xms32m -Xmx200m"/>
I have tried with a lot of possibilty, 64-200, 128-200, 128-128, 256-256, 512-512, nothing works.
I have tried without this parameter, this works fine.
I have tried with the weblogic server without the Ant Task, and this works fine too.
I think this is a bug in the JVM 1.4.2_03.
What do you think about this problem ??? Do you have some solution ???
I have also tried with another version of ant, I have the same problem. This works with JVM 1.4.1_05 and not with JVM 1.4.2_03.
If you have an idea, please, help.
Thanks

If you can start a 1.4.2 JVM with all these parameters independently (i.e. not from Ant) and it works, but from Ant it doesn't work, it's more likely that the problem is somehow related to interaction between Ant and the JVM, rather than the JVM itself. So I would suggest trying some Ant forum first - I think it would also work faster than if you try to submit this bug to Sun.

Invalid Business Area in combination with company code

Dear Expert,
I have just created a new business area, however, when doing a posting against the new business area I got prompted an error message "Invalid Business Area 7000 with combination of company code 0001". Could anyone tell me what setting did I miss?
Thank you

Hi...
As per your issue..i think your company is using validation for your business area avoiding miss usage.
In this case once created new business area you have to update new business area in GGB0 T.code at company code level
So go to GGB0 and click on Financial accounting -> line item -> here select your company code and click on business area here enter your new business area and save it after that come back one step and select your company code go to Validation at menu bar select transport.
I hope it will helps you and let me know if you have any doubts
Regards
vamsi

'Error: Invalid Staging Area' while installing Developer Studio 10g

Dear All,
I am trying to install Oracle Developer Studio 10g on Windows 2000 SP4 machine having 512 MB RAM.
All the installer requirements are met.
After that Oracle Universal Installer displays the error:
Invalid Staging Area. There are no top level components for Windows NT, Windows 2000 available for installation in this staging area.
Please explain me this error. I am not getting any references about the same on Internet.
Do i able to install Oracle Developer Suite on my machine?
-Sameer

"Invalid Staging Area. There are no top level components for Windows NT available for install from this staging area."
This is Oracle's way of saying nothing on this CD can be installed on Windows NT (or Windows 2000)
Also see
http://www.orafaq.com/forum/?t=msg&th=46751/0/
Google on "There are no top level components"

OEM 10g OBE file download URL error

goto Oracle By Example for OEM 10g :
http://www.oracle.com/technology/obe/obe10gem/index.html
on the right-side, click "Oracle By Example Files" under "Downloads" :
http://www.oracle.com/technology/obe/obe10gem/download/download.zip
I get :
Sorry, this page was not found. (ErrorDocument 404)
could someone let me know how to report this ?
thanks

My System Administrator declined my request telling
me to tell Oracle to fix their code. I did open an SR
and since my initial contact - I have not gotten an
update. Maybe someone went on vacation?even if your SR is accepted as a bug i'm certain a patch would take a few weeks if not months, because there's an easy workaround. i reported a similar issue with 10.1.0.4 and it was fixed in 10.2.0.1.
it seems your sysadmin doesn't know how long oracle needs to solve such trivial problems.
regards,
-ap

OEM 10g OracleByExample files URL error ?

not sure whom to contact about this :
goto Oracle By Example for OEM 10g :
http://www.oracle.com/technology/obe/obe10gem/index.html
on the right-side, click "Oracle By Example Files" under "Downloads" :
http://www.oracle.com/technology/obe/obe10gem/download/download.zip
I get :
Sorry, this page was not found. (ErrorDocument 404)
could someone let me know how to report this ?
thanks

Failed to contact the OMS at the HTTP URL set in /apps/apsp1/oracle/emhome/agent10g/sysman/config/emd.propertiesDid you check that? It seems configuration file 'emd.properties' points to a URL, which cannot be resolved.
Werner

Creating Standby database in OEM 10g

DB = Oracle 10.2.0.4
OS = Solaris 10 Sparc
I am trying to create a physical standby database using the add standby database option within OEM 10g. This is something we have done numerous times before on 10g and 11g db's without a single issue, but for some reason, this time after selecting my RMAN backup location and staging area location , I am getting the following error when I click Next:
RMAN Backup Location - The specified RMAN backup is invalid. Could not identify controlfile from the backup
It is the latest backup (using RMAN catalog) from the previous evening and includes datafiles and control file.
Here is the output for List backup:
BS Key Size Device Type Elapsed Time Completion Time
1741586 7.70G DISK 00:03:26 06-DEC-12
BP Key: 1741590 Status: AVAILABLE Compressed: NO Tag: TAG20121206T220033
Piece Name: /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4811_1.bus
List of Archived Logs in backup set 1741586
Thrd Seq Low SCN Low Time Next SCN Next Time
1 20013 7974703107 04-DEC-12 7974865046 04-DEC-12
1 20014 7974865046 04-DEC-12 7975209322 05-DEC-12
1 20015 7975209322 05-DEC-12 7975792781 05-DEC-12
1 20016 7975792781 05-DEC-12 7975841363 05-DEC-12
1 20017 7975841363 05-DEC-12 7976016507 05-DEC-12
1 20018 7976016507 05-DEC-12 7976577946 06-DEC-12
1 20019 7976577946 06-DEC-12 7976685352 06-DEC-12
1 20020 7976685352 06-DEC-12 7976816259 06-DEC-12
1 20021 7976816259 06-DEC-12 7976884597 06-DEC-12
1 20022 7976884597 06-DEC-12 7977236969 06-DEC-12
1 20023 7977236969 06-DEC-12 7978009499 06-DEC-12
1 20024 7978009499 06-DEC-12 7978784609 06-DEC-12
1 20025 7978784609 06-DEC-12 7979558556 06-DEC-12
1 20026 7979558556 06-DEC-12 7980614921 06-DEC-12
1 20027 7980614921 06-DEC-12 7981238045 06-DEC-12
1 20028 7981238045 06-DEC-12 7981890156 06-DEC-12
1 20029 7981890156 06-DEC-12 7982119933 06-DEC-12
1 20030 7982119933 06-DEC-12 7982775834 06-DEC-12
1 20031 7982775834 06-DEC-12 7983388279 06-DEC-12
BS Key Type LV Size Device Type Elapsed Time Completion Time
1741587 Full 214.09G DISK 01:15:15 06-DEC-12
List of Datafiles in backup set 1741587
File LV Type Ckp SCN Ckp Time Name
1 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/system01.dbf
2 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/undotbs01.dbf
3 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/sysaux01.dbf
4 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/large_indexes01.dbf
5 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/large_indexes02.dbf
6 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/large_indexes03.dbf
7 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/large_tables01.dbf
8 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/large_tables02.dbf
9 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/large_tables03.dbf
10 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/small_tables01.dbf
11 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/small_tables02.dbf
12 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/small_tables03.dbf
13 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/small_tables04.dbf
14 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/medium_tables01.dbf
15 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/medium_tables02.dbf
16 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/medium_tables03.dbf
17 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/small_indexes01.dbf
18 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/medium_indexes01.dbf
19 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/tools01.dbf
20 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/small_indexes02.dbf
Backup Set Copy #1 of backup set 1741587
Device Type Elapsed Time Completion Time Compressed Tag
DISK 01:15:15 06-DEC-12 NO TAG20121206T220415
List of Backup Pieces for backup set 1741587 Copy #1
BP Key Pc# Status Piece Name
1741591 1 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_1.bus
1741592 2 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_2.bus
1741593 3 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_3.bus
1741594 4 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_4.bus
1741595 5 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_5.bus
1741596 6 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_6.bus
1741597 7 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_7.bus
1741598 8 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_8.bus
1741599 9 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_9.bus
1741600 10 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_10.bus
1741601 11 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_11.bus
1741602 12 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_12.bus
1741603 13 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_13.bus
1741604 14 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_14.bus
1741605 15 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_15.bus
1741606 16 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_16.bus
1741607 17 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_17.bus
1741608 18 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_18.bus
1741609 19 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_19.bus
1741610 20 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_20.bus
1741611 21 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_21.bus
1741612 22 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_22.bus
BS Key Size Device Type Elapsed Time Completion Time
1741658 104.19M DISK 00:00:04 06-DEC-12
BP Key: 1741679 Status: AVAILABLE Compressed: NO Tag: TAG20121206T231939
Piece Name: /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4813_1.bus
List of Archived Logs in backup set 1741658
Thrd Seq Low SCN Low Time Next SCN Next Time
1 20032 7983388279 06-DEC-12 7983637536 06-DEC-12
BS Key Type LV Size Device Type Elapsed Time Completion Time
1741702 Full 7.33M DISK 00:00:02 06-DEC-12
BP Key: 1741704 Status: AVAILABLE Compressed: NO Tag: TAG20121206T231950
Piece Name: /carebackup/oradata/CARELIVE/carelive/backup/ctlc-3640364239-20121206-00
Control File Included: Ckp SCN: 7983638867 Ckp time: 06-DEC-12
SPFILE Included: Modification time: 06-DEC-12
The only difference between creating a standby for this db and others we have created is that the file system the backups are stored on is on a non-global zone shared via nfs mount.
I know that when I try and share that filesystem with other servers I get the message:
share_nfs: Cannot share filesystems in non-global zones
If the /backup filesystem is not shared with any other servers would OEM be able to read from that NGZ? The filesystem is available to connect to using ssh from other locations, but not sure how OEM handles this part of the process.
Any advice would be great.
Regards,
JP

Thanks for the reply. I thought that is what I would need to do. However this link is very useful and could resolve the issue. I have yet to raise it with the system admin guys here yet but will do and will report back on outcome.
http://faizsulaiman.com/mount-nfs-solaris-non-global-zone/

10G: TEMPORARY TABLESPACES GROUP

제품 : ORACLE SERVER
작성날짜 : 2004-05-25
10G: TEMPORARY TABLESPACES GROUP
==================================
PURPOSE
이 문서에서는 10g New Feature 인 Temporary tablespace 의 group 에 대해 알아 보도록 한다.
Explanation
10g 에서는 temporary tablespaces 에 대해 group 을 지정하여 생성할 수 있고
consumer group 을 지정하여 resource manager 와 함께 적용하여 사용이 가능하다.
다음은 Temporary tablespace group 지정을 위한 기본적이 사항이다.
1. 하나의 temporary tablespace group 은 적어도 하나의 tablespace 가 존재해야 하고
maximum number tablespace 에 대한 limit 은 정해져 있지 않다.
2. Ttemporary tablespace 와 group name 을 동일하게 지정할 수 없다.
3. Temporary tablespace group 은
     1) 한 group 에서 다른 group 으로 move 가 가능하고
     2) Group 내에서 삭제 될 수 있으며
     3) 추가적으로 add 가 가능하다.
4. Temporary tablespace group 사용으로 인해
     1) Sort 결과를 유지하여 space 낭비를 막을 수 있고
     2) 동시에 여러개의 session connect 시에도 서로 다른 temporary tablespaces 를 사용함으로써
     temporary tablespaces 의 사용을 분산 시킬 수 있다.
     3) Parallel operation 시에도 multiple temporary tablespaces 사용이 가능하다.
Example
1. GROUP1 을 지정하고 GROUP1 에 속하는 temporary tablespace LMTEMP 1 를 생성한다.
이 때 GROUP 1 을 따로 생성할 필요 없고 temporary tablespace 생성시에 지정하도록 한다.
SQL> create temporary tablespace LMTEMP 1
tempfile 'D:\ORACLE10\ORCL\temp1_01.dbf' size 50M
tablespace group GROUP1;
SQL> select * from dba_tablespace_groups;
GROUP_NAME TABLESPACE_NAME
GROUP1 LMTEMP1
2. LMTEMP2 를 GROUP1 에 새로 추가한다.
SQL> create temporary tablespace lmtemp2
tempfile 'D:\ORACLE10\ORCL\temp1_02.dbf' size 2M
tablespace group group1;
Tablespace created.
SQL> select * from dba_tablespace_groups;
GROUP_NAME TABLESPACE_NAME
GROUP1 LMTEMP1
GROUP1 LMTEMP2
3. 기존에 존재하는 LMTEMP1 를 GROUP2 로 move 한다.
SQL> alter tablespace LMTEMP1 tablespace group GROUP2 ;
Tablespace altered.
SQL> select * from dba_tablespace_groups;
GROUP_NAME TABLESPACE_NAME
GROUP2 LMTEMP1
GROUP1 LMTEMP2
4. LMTEMP1 이 속해 있던 GROUP2 에서 LMTEMP1 를 제외 시키고 다시 포함시킬 수 있다.
SQL> alter tablespace LMTEMP1 tablespace group '';
Tablespace altered.
SQL> select * from dba_tablespace_groups;
GROUP_NAME TABLESPACE_NAME
GROUP1 LMTEMP2
SQL> select tablespace_name from dba_tablespaces where contents='TEMPORARY';
TABLESPACE_NAME
TEMP
LMTEMP1
LMTEMP2
SQL> alter tablespace LMTEMP1 tablespace group GROUP1;
Tablespace altered.
5. Temporary tablespace 와 group name 을 동일하게 지정할 경우 ORA-10918 에러가 발생한다.
즉, temporary tablespace 와 group name 을 동일하게 지정이 불가능하다.
SQL> create temporary tablespace lmtemp5
tempfile 'D:\ORACLE10\ORCL\temp1_05.dbf' size 50M
tablespace group lmtemp5;
create temporary tablespace lmtemp5
ERROR at line 1:
ORA-10918: TABLESPACE GROUP name cannot be the same as tablespace name
6. 존재하던 모든 temporary tablespaces 를 drop 하게 되면 group 은 자동으로 remove 된다.
SQL> create temporary tablespace LMTEMP3
tempfile 'D:\ORACLE10\ORCL\temp1_03.dbf' size 2M
tablespace group GROUP2;
Tablespace created.
SQL> create temporary tablespace LMTEMP4
tempfile 'D:\ORACLE10\ORCL\temp1_04.dbf' size 2M
tablespace group GROUP2;
Tablespace created.
SQL> select * from dba_tablespace_groups;
GROUP_NAME TABLESPACE_NAME
GROUP1 LMTEMP1
GROUP1 LMTEMP2
GROUP2 LMTEMP3
GROUP2 LMTEMP4
SQL> drop tablespace lmtemp3 including contents and datafiles;
Tablespace dropped.
SQL> drop tablespace lmtemp4 including contents and datafiles;
Tablespace dropped.
SQL> select * from dba_tablespace_groups;
GROUP_NAME TABLESPACE_NAME
GROUP1 LMTEMP1
GROUP1 LMTEMP2
7. Group 에 user 사용이 가능하도록 지정할 수 있다.
SQL> alter user scott temporary tablespace GROUP1;
User altered.
8. Temporary tablespace group 을 database level 의 default temporary tablespace 로도 지정할 수 있다.
SQL> alter database <db_name> default temporary tablespace GROUP1;
Database altered.
만약, temporary tablespaces 가 default database temporary tablespace group 에 속해 있는경우
drop 시 ORA-10921 에러가 발생하게 된다. 즉, default temporary tablespace group 에 속해 있는 경우
drop 할 수 없다.
SQL> drop tablespace LMTEMP2 including contents and datafiles;
drop tablespace lmtemp2 including contents and datafiles
ERROR at line 1:
ORA-10921: Cannot drop tablespace belonging to default temporary tablespace
group
Reference Documents
<NOTE. 245645.1>

Hi,
Take a look in
1 - DBA_TEMP_FILES :http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96536/ch2398.htm
2 - V$TEMPFILE: http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96536/ch3225.htm
Cheers,
Marcello M.

OEM alert: temporary tablespace more than 100% full

Hi,
I created an event in OEM which checks tablespaces. Once in a while I'm having an alerts like:
Tablespace TEMP is 102.08% full. -339968.0 KBytes of free space remain
What to do ?

Did you do the calc yourself?
Ideally a temporary tablespace will show roughly 100% full (95-105%) at all times, using standard extent calculations. Any small amount over 100% is usually the result of rounding error, or using several independent queries and catching the reuse and realloc of segments.
The only time a temporary tablespace should show nearly empty is shortly affter restarting the instance. Once it starts getting used, the temp tablespace should get blocks used by active sessions. When a session needs an empty block, it formats that block for the purpose (sort, global tempo table, hash area, etc.) Once sessions are finished with them, the blocks are reused - for performance, blocks are not cleared (reformatted to 'empty') and therefore simply show 'being used' in a typical dba_segments/dba_extents select.
The only time to worry about it is when a session (or the system) compains about being out of temp space. In which case, make it bigger ... or figger why it needs the extra space and fiux that.

OEM 10g - reorganize tablespace error on invalid sort area size

Similar Messages

Maybe you are looking for