Truncating table having partitions

Hi,
I have a table haing 10 partitions and 5 subpartitions in each partition. Now i have to truncate that table. please let me know..
1) Can i truncate the table directly?
2) If no then how to truncate the table having partition->sub-partitions....
With Regards,
snp

Hello,
To count your rows on the Truncated Table, you may also execute the following query:
select count(*) from <Table_name>;You should be carefull if you ANALYZE or use DBMS_STATS on your Table just after you
Truncate it.
Because, as the Table is empty, the statistics of the optimizer may be wrong and, it could
affect the performance of your queries on this Table later (when it will be full).
So, you may have to refresh you statistics (with DBMS_STATS) after loading again this Table.
Hope this help.
Best regards,
Jean-Valentin

Similar Messages

Problem in truncate/drop partitions in a table having nested table columns.

Hi,
I have a table that has 2 columns of type nested table. Now in the purge process, when I try to truncate or drop a partition from this table, I get error that I can't do this (because table has nested tables). Can anybody help me telling how I will be able to truncate/drop partition from this table? IF I change column types from nested table to varray type, will it help?
Also, is there any short method of moving existing data from a nested table column to a varray column (having same fields as nested table)?
Thanks in advance.

>
I have a table that has 2 columns of type nested table. Now in the purge process, when I try to truncate or drop a partition from this table, I get error that I can't do this (because table has nested tables). Can anybody help me telling how I will be able to truncate/drop partition from this table?
>
Unfortunately you can't do those operations when a table has a nested table column. No truncate, no drop, no exchange partition at the partition level.
A nested table column is stored as a separate table and acts like a 'child' table with foreign keys to the 'parent' table. It is these 'foreign keys' that prevent the truncation (just like normal foreign keys prevent truncating partions and must be disabled first) but there is no mechanism to 'disable' them.
Just one excellent example (there are many others) of why you should NOT use object columns at all.
>
IF I change column types from nested table to varray type, will it help?
>
Yes but I STRONGLY suggest you take this opportunity to change your data model to a standard relational one and put the 'child' (nested table) data into its own table with a foreign key to the parent. You can create a view on the two tables that can make data appear as if you have a nested table type if you want.
Assuming that you are going to ignore the above advice just create a new VARRAY type and a table with that type as a column. Remember VARRAYs are defined with a maximum size. So the number of nested table records needs to be within the capacity of the VARRAY type for the data to fit.
>
Also, is there any short method of moving existing data from a nested table column to a varray column (having same fields as nested table)?
>
Sure - just CAST the nested table to the VARRAY type. Here is code for a VARRAY type and a new table that shows how to do it.
-- new array type
CREATE OR REPLACE TYPE ARRAY_T AS VARRAY(10) OF VARCHAR2(64)
-- new table using new array type - NOTE there is no nested table storage clause - arrays stored inline
CREATE TABLE partitioned_table_array
     ( ID_ INT,
      arra_col ARRAY_T )
     PARTITION BY RANGE (ID_)
     ( PARTITION p1 VALUES LESS THAN (40)
     , PARTITION p2 VALUES LESS THAN(80)
     , PARTITION p3 VALUES LESS THAN(100)
-- insert the data from the original table converting the nested table data to the varray type
INSERT INTO PARTITIONED_TABLE_ARRAY
SELECT ID_, CAST(NESTED_COL AS ARRAY_T) FROM PARTITIONED_TABLENaturally since there is no more nested table storage you can truncate or drop partitions in the above table
alter table partitioned_table_array truncate partition p1
alter table partitioned_table_array drop partition p1

ORA-01502: Index or Partition is in unusable status. while truncating table

Hi All,
One of our Devlopers compalined that he is getting ORA-01502 : Index or partition is unusable status while truncating the a table in our Dataware house production database. He is using the following commands.
Alter index <index_name> unusable;
Truncate table <table_name> ;
He is running a scripts to truncate each table and ecah time he is passing the table name as an input parameter to script. He is using same method to truncate four tables each having a BITMAP and a REGULAR index. For two tables every thing is working fine, but for other two tables the he is getting ORA-01502 for BITMAP indexes. It a weekly process and every week he is getting the same issue. I checkd the Index status, they are in valid status only.
For a work around I have created a table with BITMAP and regular index in our dev database. made the indexes unusable, checked their status. I truncated the table. Importent thing here is the Indexes are becoming vaild when I truncate the table.
I suspect that my devloper's Indexes were already in unusable status (before he use the command ALTER INDEX), when he truncated the table, oracle trying to validate the index and throwing the error ORA-01502 because the Indexes are in unusabel statsu for a while.
I tried searching for the mechanism of truncate table command and its effect on Indexes. But I did not find any luck, no one is speaking about index when truncating the table. Can any one please help me????
Sorry for lengthy post. Any help is greatly appriciated and I thank every one in advance.

DDL for Indexes getting ORA-01502 error
CREATE BITMAP INDEX DWHMGR.ACT_TXN_LN_STG_01_XN3 ON DWHMGR.ACCT_TXN_LINE_TERM_BAL_STG_01 (TERM_BAL_CD ASC) TABLESPACE "BALFD_INX_04" NOLOGGING PCTFREE 1 INITRANS 2 MAXTRANS 255 STORAGE
( INITIAL 8M NEXT 8M MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 BUFFER_POOL DEFAULT );
CREATE BITMAP INDEX DWHMGR.ACCT_TERM_BAL_STG_01_XN3 ON DWHMGR.ACCT_TERM_BAL_STG_01 TERM_BAL_CD ASC) TABLESPACE "BALFD_INX_04" NOLOGGING PCTFREE 1 INITRANS 2 MAXTRANS 255 STORAGE
( INITIAL 8M NEXT 8M MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 BUFFER_POOL DEFAULT );
Indexes that have no issues.
CREATE INDEX DWHMGR.ACCT_TERM_BAL_STG_01_XN2 ON DWHMGR.ACCT_TERM_BAL_STG_01 (ACCT_REF_NB ASC) TABLESPACE "BALFD_INX_04" NOLOGGING PCTFREE 1 INITRANS 2 MAXTRANS 255 STORAGE (INITIAL 8M
NEXT 8M MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 BUFFER_POOL DEFAULT );
CREATE BITMAP INDEX DWHMGR.ACCT_PRC_STG_01_XN1 ON DWHMGR.ACCT_PRC_STG_01 (ACCT_ORG_CD ASC) TABLESPACE "BALFD_INX_04" NOLOGGING PCTFREE 1 INITRANS 2 MAXTRANS 255 STORAGE ( INITIAL 8M
NEXT 8M MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 BUFFER_POOL DEFAULT );
Please look at the DDL of the indexes and let me know if you need any other information.

Truncate table and materialized view log

I user oracle 10 R2
I have a table and on that table a materialized view log.
I execute in a pl/sql procedure:
1) execute immediate('drop materialized view log on tab1');
then:
2) execute immediate('truncate table tab1');
3) Now I insert a lot of records in tab1
4) execute immediate('create materialized view log on tab1 WITH rowid INCLUDING NEW VALUES');
When I create the materialized view log I recieved this message:
ora32321: refresh fast on tab2 unsupported after detail table truncate
Why?

Refresh fast after truncate operation on container table is not supported, regardless the container table is or is not partitioned.
Perform a refresh complete.
ORA-32321 :
Cause:     A detail table has been truncated and no materialized view
     supports fast refersh after a detail table has been truncated
Action:     Use REFRESH COMPLETE. Note: you can determine why your
     materialized view does not support fast refresh after TRUNCATE
     using the DBMS_MVIEW.EXPLAIN_MV() API.

Problem with truncate table in procedure ora -00054

hi do anybody know where is mistake ???
the procedure has problem with truncate table
ora - 00054: resource busy and acquire with NOWAIT specified
ora - 06512 at "POVAPSYS.HMAN_P_REFRESH", line 6
ora - 06512 at "POVAPSYS.POVAPSYS", line 6
ora - 06512 at line 1
this is my procedure....
AS
BEGIN
execute immediate 'TRUNCATE TABLE hman_t_max';
INSERT INTO hman_t_max SELECT * FROM hman_v_max;
COMMIT;
END;

2.MAKE SURE THAT OTHER THAN YOU ANYBODY IS TRYING TO
COMPILE AND RUN THE PROCEDUREShould he make sure that anybody is running the procedure?
3.MAKE SURE THAT ANY PARALLEL QUERY IS RUNNING IN THE
SERVER SIDE,THATS KEEPS THE RESOURCE BUSYShould he make sure any parallel query is running in the server side to keep the resource busy?
Gita,
I COULDN'T RESIST HAVING ONE SUGGESTION FOR YOU. Please look at the impact of your English in the reply before posting. Check if that sends reverse message!
Cheers
Sarma.

How to handle tables having volatile data

Hi,
We have a table in which we load millions of data and after validation a huge amount of data is deleted. After that the select statements (performing FTS) becomes slow. If we shrink the space, the queries becomes faster. But shrinking space requires additional time. We can consider creating index on the table. But the indexes will slow down the inserts.
I wanted to know, how do we handle such tables containing data which has volitile nature.
The database version is 10.2.0.5 and platform Windows server 2008.
Regards,

Thanks Justin,
We can't truncate the table.
Basically, the application is for a credit card payment gateway. A credit card transaction may be a successful or unsuccessful transaction. All the data is pushed in flat file. The application loads the data(using SQL loader) in a temporary table and if the merchant_id is correct then the data is pushed in permanent table(say T1). The table T1 may contain successful as well as unsuccessful transations (The unsuccessful transactions have to be maintained for 30 days because of business compulsions). Once the validation is done, the successful transations are moved to different table and are deleted from T1.
Here I have referred T1 as a table having volatile data. We can't truncate it as it has still data which is required by business.
Hope I am clear.
Regards,

Interrupted TRUNCATE TABLE command

Hello,
I've made very dangerous mistake today: TRUNCATE TABLE on production database. :-(
But in several seconds (2 or 3), I managed to break the operation (Before the execution ended).
It was quite a big table, now (after the accident) there are more then 32 million records.
We need to know, are there any records deleted?
We have no proper backup, to compare the records with it.
And I could not find any in-depth description of how TRUNCATE works.
Please can you:
1. Tell, about any method to check if there are deleted records?
2. Link, to any resource, where I can read in details, about how TRUNCATE TABLE works.
Thanks, in advance, for help

My understanding is that the TRUNCATE TABLE table statement is atomic. It either fails or succeeds. Truncates all rows or no rows at all. Therefore if you interrupt a TRUNCATE TABLE statement your table should remain in its original state.
This can be shown below:
SQL > CREATE TABLE TEST AS SELECT * FROM ALL_OBJECTS;
Table created.
SQL > INSERT INTO TEST SELECT * FROM TEST;
12421 rows created.
SQL > INSERT INTO TEST SELECT * FROM TEST;
24842 rows created.
SQL > INSERT INTO TEST SELECT * FROM TEST;
49684 rows created.
SQL > INSERT INTO TEST SELECT * FROM TEST;
99368 rows created.
SQL > INSERT INTO TEST SELECT * FROM TEST;
198736 rows created.
SQL > INSERT INTO TEST SELECT * FROM TEST;
397472 rows created.
SQL > INSERT INTO TEST SELECT * FROM TEST;
794944 rows created.
SQL > INSERT INTO TEST SELECT * FROM TEST;
1589888 rows created.
SQL > SELECT COUNT(*) FROM TEST;
COUNT(*)
3179776
SQL > TRUNCATE TABLE TEST;
^C
H:\>sqlplus /@testdb
SQL*Plus: Release 10.2.0.4.0 - Production on Mon Aug 3 08:20:11 2009
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Enter password:
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL > SELECT COUNT(*) FROM TEST;
COUNT(*)
3179776HTH!

Truncate Tables

Is it possible to truncate tables or table partitions in a physical standby database using dataguard.
The reason behind this is we do not need to carry forward data into the standby more than a certain period. The table is more of a datawarehouse table.
Is this possible on dataguard 11g R1.
Thanks,

Hi,
aprarently this is not possible. A physical data guard configuration is marked by the fact that primary and standby database are bitwise identical (spreaking from the data files here).
So it is not possible - even in 11g. In 11g you can open the standby database, modify data and flashback the database to the point you started modifying the standby and continue apply
the redo log data.
If you want a solution: You can use streams to replicate the data to another database. In this "another" database you are free to truncate the data. Or you can use
a logical standby database where you can truncate the table as well.
Ronny Egner
My blog: http://ronnyegner.wordpress.com

How to get the rows from a table having some column has any letter

Hi All,
suppose i have a table having columns id(number), code(varchar).
code has alphanumeric characters (ex. ABC123, 67B56 etc).
some codes are only numbers (2344, 7898 etc).
how can i get the rows which have alphabets in the code.
ex:
id code
1 AB45
2 456
3 890
4 67B7
how can i write a query such that it should give me the ids 1 and 4 (as they have alphabets in code)
thanks in advance to all

Thanks to one and all.
i am gettig my required output.
But i have a doubt in the operator.
If i add or remove '[]' in the operator, i am getting different ouputs.
There is a count difference in the result of the operators used.
REGEXP_LIKE(<column>,'[[:lower:]]')
REGEXP_LIKE(<column>,'[[[:lower:]]]')
REGEXP_LIKE(<column>,'[:lower:]')
Can anybody please explain what is the difference in using '[]', in the operator?
What is the correct syntax, whether i have to use two '[]'s or one '[]'.
Also, can i use REGEXP_LIKE() in oracle 8i version.( I am unable to use the operator in 8i)?
Any query to get the required output in 8i version?
Thanks in advance to all.

Full Load: Error while executing :TRUNCATE TABLE: S_ETL_PARAM

Hi All,
We are using Bi Apps 7.9.6.1. Full Load was running fine. But Now we are facing a problem with truncating a table "S_ETL_PARAM".
I have restart informatica Server And also DAC Srever. But still I am getting the same in the DAC Log as, *"NOMALY INFO::: Error while executing : TRUNCATE TABLE:S_ETL_PARAM*
*MESSAGE:::com.siebel.etl.database.IllegalSQLQueryException: DBConnection_OLTP:SIEBTRUN ('siebel.S_ETL_PARAM')*
*Values :*
*Null Map*
*EXCEPTION CLASS::: java.lang.Exception"*
Any Suggestion.....
Thanks in Advance,
Deepak

are you trying to run incremental load when you get this truncate error? can you re-run full load and see that still runs ok? pls also check your DW side database logs like alert lor any DB level issue. such errors do not throw friendly messages in DAC/Informatica side.

Need help for SQL SELECT query to fetch XML records from Oracle tables having CLOB field

Hello,
I have a scenario wherein i need to fetch records from several oracle tables having CLOB fields(which is holding XML) and then merge them logically to form a hierarchy XML. All these tables are related with PK-FK relationship. This XML hierarchy is having 'OP' as top-most root node and ‘DE’ as it’s bottom-most node with One-To-Many relationship. Hence, Each OP can have multiple GM, Each GM can have multiple DM and so on.
Table structures are mentioned below:
OP:
Name                             Null                    Type
OP_NBR                    NOT NULL      NUMBER(4)    (Primary Key)
OP_DESC                                        VARCHAR2(50)
OP_PAYLOD_XML                           CLOB
GM:
Name                          Null                   Type
GM_NBR                  NOT NULL       NUMBER(4)    (Primary Key)
GM_DESC                                       VARCHAR2(40)
OP_NBR               NOT NULL          NUMBER(4)    (Foreign Key)
GM_PAYLOD_XML                          CLOB
DM:
Name                          Null                    Type
DM_NBR                  NOT NULL         NUMBER(4)    (Primary Key)
DM_DESC                                         VARCHAR2(40)
GM_NBR                  NOT NULL         NUMBER(4)    (Foreign Key)
DM_PAYLOD_XML                            CLOB
DE:
Name                          Null                    Type
DE_NBR                     NOT NULL           NUMBER(4)    (Primary Key)
DE_DESC                   NOT NULL           VARCHAR2(40)
DM_NBR                    NOT NULL           NUMBER(4)    (Foreign Key)
DE_PAYLOD_XML                                CLOB
+++++++++++++++++++++++++++++++++++++++++++++++++++++
SELECT
j.op_nbr||'||'||j.op_desc||'||'||j.op_paylod_xml AS op_paylod_xml,
i.gm_nbr||'||'||i.gm_desc||'||'||i.gm_paylod_xml AS gm_paylod_xml,
h.dm_nbr||'||'||h.dm_desc||'||'||h.dm_paylod_xml AS dm_paylod_xml,
g.de_nbr||'||'||g.de_desc||'||'||g.de_paylod_xml AS de_paylod_xml,
FROM
DE g, DM h, GM i, OP j
WHERE
h.dm_nbr = g.dm_nbr(+) and
i.gm_nbr = h.gm_nbr(+) and
j.op_nbr = i.op_nbr(+)
+++++++++++++++++++++++++++++++++++++++++++++++++++++
I am using above SQL select statement for fetching the XML records and this gives me all related xmls for each entity in a single record(OP, GM, DM. DE). Output of this SQL query is as below:
Current O/P:
<resultSet>
     <Record1>
          <OP_PAYLOD_XML1>
          <GM_PAYLOD_XML1>
          <DM_PAYLOD_XML1>
          <DE_PAYLOD_XML1>
     </Record1>
     <Record2>
          <OP_PAYLOD_XML2>
          <GM_PAYLOD_XML2>
          <DM_PAYLOD_XML2>
          <DE_PAYLOD_XML2>
     </Record2>
     <RecordN>
          <OP_PAYLOD_XMLN>
          <GM_PAYLOD_XMLN>
          <DM_PAYLOD_XMLN>
          <DE_PAYLOD_XMLN>
     </RecordN>
</resultSet>
Now i want to change my SQL query so that i get following output structure:
<resultSet>
     <Record>
          <OP_PAYLOD_XML1>
          <GM_PAYLOD_XML1>
          <GM_PAYLOD_XML2> .......
          <GM_PAYLOD_XMLN>
          <DM_PAYLOD_XML1>
          <DM_PAYLOD_XML2> .......
          <DM_PAYLOD_XMLN>
          <DE_PAYLOD_XML1>
          <DE_PAYLOD_XML2> .......
          <DE_PAYLOD_XMLN>
     </Record>
     <Record>
          <OP_PAYLOD_XML2>
          <GM_PAYLOD_XML1'>
          <GM_PAYLOD_XML2'> .......
          <GM_PAYLOD_XMLN'>
          <DM_PAYLOD_XML1'>
          <DM_PAYLOD_XML2'> .......
          <DM_PAYLOD_XMLN'>
          <DE_PAYLOD_XML1'>
          <DE_PAYLOD_XML2'> .......
          <DE_PAYLOD_XMLN'>
     </Record>
<resultSet>
Appreciate your help in this regard!

Hi,
A few questions :
How's your first query supposed to give you an XML output like you show ?
Is there something you're not telling us?
What's the content of, for example, <OP_PAYLOD_XML1> ?
I don't think it's a good idea to embed the node level in the tag name, it would make much sense to expose that as an attribute.
What's the db version BTW?

Release of space after delete/truncate table

Hello,
How does release of space after delete/truncate table works? Is the space used before deletion released once delete is complete or not? Will I see the space occupied by deleted table as free in dba_segments or will I need to reorganize the table (drop and recreate again?). Reason why I am asking is that I can see table with 0 rows, but in dba_segment I can see it is occupying few gigabytes....
Thank you

Here is a little illustration for you;
SQL> conn ogan/password
Connected.
SQL> create table ogan_deneme as select * from all_objects;
Table created.
SQL> select count(*) from ogan_deneme;
COUNT(*)
    228470
SQL> set line 1000
SQL> set pagesize 1000
SQL> select * from dba_segments where owner='OGAN';
OWNER    SEGMENT_NAME        PARTITION_NAME           SEGMENT_TYPE       TABLESPACE_NAME                HEADER_FILE HEADER_BLOCK      BYTES     BLOCKS    EXTENTS INITIAL_EXTENT NEXT_EXTENT MIN_EXTENTS MAX_EXTENTS PCT_INCREASE FREELISTS FREELIST_GROUPS RELATIVE_FNO BUFFER_
OGAN      OGAN_DENEME          TABLE              SYSTEM                                 854       319981   *30408704*       *1856*         *44*          65536                       1 2147483645                       1               1          854 DEFAULT
SQL> truncate table ogan_deneme;
Table truncated.
SQL> select * from dba_segments where owner='OGAN';
OWNER    SEGMENT_NAME        PARTITION_NAME           SEGMENT_TYPE       TABLESPACE_NAME                HEADER_FILE HEADER_BLOCK      BYTES     BLOCKS    EXTENTS INITIAL_EXTENT NEXT_EXTENT MIN_EXTENTS MAX_EXTENTS PCT_INCREASE FREELISTS FREELIST_GROUPS RELATIVE_FNO BUFFER_
OGAN      OGAN_DENEME           TABLE              SYSTEM                                 854       319981      *65536*          *4*          *1*          65536                       1 2147483645                       1               1          854 DEFAULT
SQL>Hope it Helps,
Ogan

Dropping multiple tables having common prefix in SQL Server 2000/2005

Hi
I used the below to drop tables having common prefix like 'GPN'
DECLARE @id varchar(255) DECLARE @dropCommand varchar(255) DECLARE tableCursor CURSOR FOR SELECT name FROM sys.tables WHERE NAME LIKE 'GPN%' OPEN tableCursor FETCH next FROM tableCursor INTO @id WHILE @@fetch_status=0 BEGIN SET @dropcommand = N'drop table ' + @id EXECUTE(@dropcommand) FETCH next FROM tableCursor INTO @id END CLOSE tableCursor DEALLOCATE tableCursor
The point is this works in SQL2005 but not in SQL2000
In SQL 2000 we get errors like
Server: Msg 137, Level 15, State 1, Line 2
Must declare the variable '@dropcommand'.
Server: Msg 137, Level 15, State 1, Line 2
Must declare the variable '@dropcommand'.
Tried the following as well : SELECT table_name FROM Information_Schema.TABLES WHERE table_name LIKE
but ended up with the same error.
Please let me know where i am going wrong and how i can correct it
Purushothama

Hi.
As far as I know SQLS2000 uses syntax:
EXEC sp_executesql @dropcommand
Isn't this a problem?
Talerod

What is the recommended way to truncate tables in ODI?

I want to create a separate step to truncate the result tables, before the start of the actual job. What is the recommended way of doing this?
I am currently putting the truncate statements in the ODI procedure, but that has a lot of typing. Is there a odi command in the toolbox that I can use?
Thanks.

Ok,
If the table will be loaded by interfaces, you have the "Truncate" option at the IKM's, just change it to "Yes".
If you need to Truncate but they won't be loaded by Interfaces a possible way is:
- requirements: it will be necessary to have some common "string" at tables names.
1) create a procedure
2) create an step
3) at source tab put:
Select table_name from user_tables where table_name in '%THE_STRING%'
4) at target tab put:
Truncate table #table_name
If you don't have a common "string" you, instead, can create a table with all table names that you need to truncate and change the select command at 3).
Does it help you?
Message was edited by:
Cezar_Santos

Truncate Table before Insert--Performance

HI All,
This post is in focus of special requirement where a table is truncated before inserting records in the table.
Now, when a table is truncated the High Water Mark(HWK) is reset to lowest memory allocated for table in tablespace. After this, would insert with append can boost the performance of the insert query?
In simple insert query, the oracle engine consults the free list to look for free spaces.
But in insert with apppend, the engine starts above the HWM. And the argument is when truncate has been executes on table, would the freelist be used in simple insert.
I just need to know if there are any benefits of using append insert on truncated table or simple insert would be same in term of performance with respect to insert with append.
Regards
Nits

Hi,
if you don't need the data truncate the table. There is no negativ impact whether you are using an conventional path or a direct path insert.
If you use append less redo is written for the table if the table is in NOLOGGING mode, but redo is written for all indexes. I would recommand to create a full backup after that (if needed), because your table will not be recoverable after that (no REDO Information).
Dim

Truncating table having partitions

Similar Messages

Maybe you are looking for