Insert, append and alter truncate partition table

Similar Questions

• Insert / * + Append * / and direct-path INSERT

  Hi guys
  
  Insert / * + Append * / hint cause Oracle 10 G using direct-path INSERT?
  and so insert / * + Append * / suspicion causes an Oracle of using direct-path INSERT, insert / * + Append * / is subject to the same restrictions as direct-path, such as "the target table cannot have any triggers or referential integrity constraints defined on it.»
  
  
  
  Thank you

  How it would be difficult for you to look for the answer in the documentation and do not abuse this forum asking questions doc and flaming posters colleagues?

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

• Insert, Update, Delete on a partition table not even at a time

  Hello
  I have a non-partitioned table on which inserts, updates and deletes come at the same time due to which I am facing problem of contention.
  What would be the ideal solutions to solve my problem (deletion conflict.)
  
  Thank you
  Badin

  Can you give us more details on the "problem of contention"? This could mean a very large number of different things.

  You have different sessions simultaneously update the same row in the table, for example? If so, you probably need to look at the architecture of the application to avoid multiple sessions to the same line at the same time setting, or you would need to look at the data model to avoid multiple sessions to update the same line at the same time setting.

  But there could be dozens of other kinds of claim that you could talk.

  Justin

• Need help and suggestions for partitioned tables

  Hello

  We have a table and it is partitioned and partitioned with datetime column, IE... partition by range.

  I tried to run the query in the form below and it runs 1 HR and did not get the result and I kill the query.

  Select min (datetime) max (datetime) < big_table > maxdate, mindate; -2203M data in this table

  index also in place on these columns as a composite index (code, datetime, status, po_num)

  < big_table > - having columns like code, datetime, status, po_num, creation_date

  Here is the plan of the explain command:

  Hash value of plan: 228211001

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

  | ID | Operation | Name | Lines | Bytes | Cost (% CPU). Time | Pstart. Pstop |

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

  |   0 | SELECT STATEMENT |                   |     1.     8.  4009K (2) | 04:41:57 |       |       |

  |   1.  GLOBAL TRI |                   |     1.     8.            |          |       |       |

  |   2.   RANGE OF PARTITION ALL THE |                   |  2163M |    16G |  4009K (2) | 04:41:57 |     1. 1048575.

  |   3.    FULL RESTRICTED INDEX SCAN FAST | POSTATUSINDEX |  2163M |    16G |  4009K (2) | 04:41:57 |     1. 1048575.

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

  Please give me any suggestions how to get the query faster.

  THX in advance

  You need to know which column mainly used in queries?

  If most of the request uses ID column, then partition of hash on ID will be beneficial.

• Assistance button works do not (= does ' t start VAIO Care Rescue) after having lost and recover the partition table / MBR

  Hello

  For some reason that I lost my patition table but I was able to get it back and I'm rewriting MBR. I'll be back all my partition and files contain the VAIO recovery partition except files on the operating system partition ("C:\ »). It's an unformatted partition. VAIO Care rescue didn't work so I had to format "C:\". "and reinstall windows 7 and now all is good.

  I have VAIO Care Rescue. I think that it is enough to change the partition table / MBR. What exactly is the problem and is it possible to fix the problem of button Assist?

  
  And if one removes all xxxx (include VAIO Recovery) and creates new ones, is it possible, software or image of the recovery restore partition and Assist button start VAIO Care Rescue?

  My laptop model: VPCEA25FG

  Thank you

  You can restore your computer back to factory with all the pre program and software installed by using recovery discs. For further assistance, please recommend contacting Sony's Support Center in your area at http://www.sony-asia.com/support/product/VPCEA25FGfor your model of Asia-Pacific computer. Thank you.

  If my post answered your question, please mark it as "accept as a Solution.

• ALTER drop partition table for ORA-01031: insufficient privileges

  Hello
  
  Select * from version of v$.
  BANNER
  --------------------------------------------------------------------------------
  Oracle Database 11 g Enterprise Edition Release 11.2.0.2.0 - 64 bit Production
  PL/SQL Release 11.2.0.2.0 - Production
  CORE Production 11.2.0.2.0
  AMT for Linux: Version 11.2.0.2.0 - Production
  NLSRTL Version 11.2.0.2.0 - Production
  
  
  I have a table in the schema Y whose partition based on the value should be removed from schema X.
  
  For example, ALTER TABLE DROP PARTITION Y.TAB_NAME FOR (4853);
  
  I guess I gave almost all the privileges. Any thoughts?
  
  Select * from DBA_TAB_PRIVS where table_name = 'Table_name' and recipient = 'X '.
  
  DEALERSHIP OWNER TABLE_NAME GRANTOR PRIVILEGE HIERARCHY
  ------------------------------ ------------------------------ ------------------------------ ------------------------------ ---------------------------------------- --------- --------------------- --------- ---------------------
  X Y TABLE_NAME Y ALTER YES NO
  X Y TABLE_NAME DELETE YES NO
  X Y TABLE_NAME Y INSERT YES NO
  X Y TABLE_NAME SELECT YES NO
  UPDATE TABLE_NAME Y Y X YES NO
  INDEX OF TABLE_NAME Y Y X YES NO
  
  6 selected lines

  Additional Prerequisites for Partitioning Operations
  If you are not the owner of the table, then you need the DROP ANY TABLE privilege in order to use the drop_table_partition or truncate_table_partition clause.
  

  reference - http://download.oracle.com/docs/cd/B28359_01/server.111/b28286/statements_3001.htm

  * That said I think seriously to give such a privilege [DROP ANY TABLE] to another schema.*

  I hope this helps!

  Published by: Sri on April 6, 2011 14:12

• Partition table with null column

  Friends,

  DB: 11 GR 2

  OS: Linux

  I'm conversion from table to table of partition and try to understand the to do.

  Table has a date column that can have null values and I am partitioning table to date.

  I creates interval partitioning and also want to use MAXVALUE so that all dates go null.

  Somehow below syntax does not work, tried to read the manual, but not able to set below.

  CREATE TABLE EMP

  (DATE_ENTERED DATE default sysdate,

  ID NUMBER (10) NULL NOT ACTIVATE.

  ACTIVATE THE FIRST NAME VARCHAR2 (200) NOT NULL,

  TURN ON LAS_NAME VARHCAR2 (200) NOT NULL

  CONSTRAINT PK_ID PRIMARY KEY (ID)

  )

  PARTITION BY RANGE (DATE_ENTERED)

  INTERVAL (NUMTODSINTERVAL(1,'day'))

  (

  partition values P_NOT_USE less (to_date ('2015-01-01', 'yyyy-mm-dd'));

  values p_max_value score less than (MAXVALUE)

  );

  Receive the error message:

  ORA-14761 maxvalue partition cannot be specified for interval partitioned objects.

  Advice to solve this problem?

  I think the problem is using the function of the interval but then how can we partition a day?

  Also is there any way/script available to find all the permissions/privileges table before a fall?

  Manual: maintenance of Partitions

  The error is pretty clear to me. You can't have a partition of maxvalue for objects partitioned interval, only beach.

  There is no logical sense to have a for range partitioning's maxvalue partition, because the whole point is to have the Oracle to create new partitions automatically when you insert something above the transition point.

  SQL> desc dba_tab_privs
  Name                                      Null?    Type
  ----------------------------------------- -------- --------------
  GRANTEE                                            VARCHAR2(128)
  OWNER                                              VARCHAR2(128)
  TABLE_NAME                                        VARCHAR2(128)
  GRANTOR                                            VARCHAR2(128)
  PRIVILEGE                                          VARCHAR2(40)
  GRANTABLE                                          VARCHAR2(3)
  HIERARCHY                                          VARCHAR2(3)
  COMMON                                            VARCHAR2(3)
  TYPE                                              VARCHAR2(24)
  

• Partitioned table

  I modified a table and actually list partitioned table. The partition is on col1 column which is used in the select clause when retrieving data. Do I need to make changes to the code? I use 10.2 g.
  If no change then please don't let me know if there is any difference in the time taken by
  SELECT * FROM partitioned_table PARTITION (p1);
  
  and
  
  SELECT * FROM partitioned_table where col1 = 'list value corresponding to p1;
  
  Published by: user637544 on August 3, 2009 06:51

  Do I need to make changes to the code?

  One of the nice things about the partitions is that their use requires no code changes.

  (when it is implemented correctly, in other words)

• Invalid option to TRUNCATE PARTITION in ALTER TABLE

  Below edit sql works fine when I run this one.

  ALTER TABLE table_name TRUNCATE partition partition_nm UPDATE GLOBAL INDEXES;

  But if I run this procedure I get the error message "14054. 00000 - option ALTER TABLE TRUNCATE PARTITION invalid"

  create or replace PROCEDURE TRUNCATE_WS_CLAIMS_REPORT

  as

  whole crsor;

  rval around edge;

  Start

  crsor: = dbms_sql.open_cursor;

  DBMS_SQL. Parse (crsor, ALTER TABLE table_name TRUNCATED partition partition_nm INDEXES', dbms_sql.v7 GLOBAL UPDATE);

  rval Tip: = dbms_sql.execute (crsor);

  DBMS_SQL.close_cursor (crsor);

  end;

  Can you guide me how to solve this error?

  Have you tried to run immediately instead of dbms_sql?

  Start

  run immediately "ALTER TABLE table_name partition TRUNCATE partition_nm UPDATE GLOBAL INDEXES";

  end;

• Difference in performance between the CTA and INSERT / * + APPEND * / IN

  Hi all

  I have a question about the ETG and "Insert / * + Append * / Into" statements.

  Suite deal, I have a question that I did not understand the difference in operating times EXADATA.

  The two tables of selection (g02_f01 and g02_f02) have not any partition. But I could partition tables with the method of partition by column "ip_id" hash and I tried to run the same query with partition tables. Change anything in execution times.

  I executed plan gather statistics for all tables. The two paintings were 13.176.888 records. The two arrays have same "ip_id' unique columns. I want to combine these tables into a single table.

  First request:

  Insert / * + append parallel (a, 16) * / in dg.tiz_irdm_g02_cc one

  (ip_id, process_date,...)

  Select / * + parallel (a, 16) parallel (16B) * / *.

  tgarstg.tst_irdm_g02_f01 a.,

  tgarstg.tst_irdm_g02_f02 b

  where a.ip_id = b.ip_id

  
  

  Elapsed = > 45: 00 minutes
  

  
  

  Second request:

  create table dg.tiz_irdm_g02_cc nologging parallel 16 compress for than query

  Select / * + parallel (a, 16) (b, 16) parallel * / *.

  tgarstg.tst_irdm_g02_f01 a.,

  tgarstg.tst_irdm_g02_f02 b

  where a.ip_id = b.ip_id

  Elapsed = > 04:00 minutes

  
  

  Execution plans are:

  
  

  1. Enter the statement execution Plan:

  Hash value of plan: 3814019933

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

  | ID | Operation | Name | Lines | Bytes | TempSpc | Cost (% CPU). Time |    TQ | IN-OUT | PQ Distrib.

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

  |   0 | INSERT STATEMENT.                  |    13 M |    36G |       |   127K (1) | 00:00:05 |        |      |            |

  |   1.  LOAD SELECT ACE | TIZ_IRDM_G02_CC |       |       |       |            |          |        |      |            |

  |   2.   COORDINATOR OF PX |                  |       |       |       |            |          |        |      |            |

  |   5:    PX SEND QC (RANDOM). : TQ10002 |    13 M |    36G |       |   127K (1) | 00:00:05 |  Q1, 02 | P > S | QC (RAND) |

  |*  4 |     IN THE BUFFER HASH JOIN |                  |    13 M |    36G |   921 M |   127K (1) | 00:00:05 |  Q1, 02 | SVCP |            |

  |   3:      RECEIVE PX |                  |    13 M |    14G |       |  5732 (5) | 00:00:01 |  Q1, 02 | SVCP |            |

  |   6.       PX SEND HASH | : TQ10000 |    13 M |    14G |       |  5732 (5) | 00:00:01 |  Q1 00 | P > P | HASH |

  |   7.        ITERATOR BLOCK PX |                  |    13 M |    14G |       |  5732 (5) | 00:00:01 |  Q1 00 | ISSUE |            |

  |   8.         STORE TABLE FULL ACCESS | TST_IRDM_G02_F02 |    13 M |    14G |       |  5732 (5) | 00:00:01 |  Q1 00 | SVCP |            |

  |   9.      RECEIVE PX |                  |    13 M |    21G |       | 18353 (3) | 00:00:01 |  Q1, 02 | SVCP |            |

  |  10.       PX SEND HASH | : TQ10001 |    13 M |    21G |       | 18353 (3) | 00:00:01 |  Q1, 01 | P > P | HASH |

  |  11.        ITERATOR BLOCK PX |                  |    13 M |    21G |       | 18353 (3) | 00:00:01 |  Q1, 01 | ISSUE |            |

  |  12.         STORE TABLE FULL ACCESS | TST_IRDM_G02_F01 |    13 M |    21G |       | 18353 (3) | 00:00:01 |  Q1, 01 | SVCP |            |

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

  Information of predicates (identified by the operation identity card):

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

  4 - access("AIRDM_G02_F01".") IP_ID '= 'AIRDM_G02_F02'.' IP_ID")

  2 - DEC execution Plan:

  Hash value of plan: 3613570869

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

  | ID | Operation | Name | Lines | Bytes | TempSpc | Cost (% CPU). Time |    TQ | IN-OUT | PQ Distrib.

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

  |   0 | CREATE TABLE STATEMENT.                  |    13 M |    36G |       |   397K (1) | 00:00:14 |        |      |            |

  |   1.  COORDINATOR OF PX |                  |       |       |       |            |          |        |      |            |

  |   2.   PX SEND QC (RANDOM). : TQ10002 |    13 M |    36G |       |   255K (1) | 00:00:09 |  Q1, 02 | P > S | QC (RAND) |

  |   3.    LOAD SELECT ACE | TIZ_IRDM_G02_CC |       |       |       |            |          |  Q1, 02 | SVCP |            |

  |*  4 |     HASH JOIN |                  |    13 M |    36G |  1842M |   255K (1) | 00:00:09 |  Q1, 02 | SVCP |            |

  |   5.      RECEIVE PX |                  |    13 M |    14G |       | 11465 (5) | 00:00:01 |  Q1, 02 | SVCP |            |

  |   6.       PX SEND HASH | : TQ10000 |    13 M |    14G |       | 11465 (5) | 00:00:01 |  Q1 00 | P > P | HASH |

  |   7.        ITERATOR BLOCK PX |                  |    13 M |    14G |       | 11465 (5) | 00:00:01 |  Q1 00 | ISSUE |            |

  |   8.         STORE TABLE FULL ACCESS | TST_IRDM_G02_F02 |    13 M |    14G |       | 11465 (5) | 00:00:01 |  Q1 00 | SVCP |            |

  |   9.      RECEIVE PX |                  |    13 M |    21G |       | 36706 (3) | 00:00:02 |  Q1, 02 | SVCP |            |

  |  10.       PX SEND HASH | : TQ10001 |    13 M |    21G |       | 36706 (3) | 00:00:02 |  Q1, 01 | P > P | HASH |

  |  11.        ITERATOR BLOCK PX |                  |    13 M |    21G |       | 36706 (3) | 00:00:02 |  Q1, 01 | ISSUE |            |

  |  12.         STORE TABLE FULL ACCESS | TST_IRDM_G02_F01 |    13 M |    21G |       | 36706 (3) | 00:00:02 |  Q1, 01 | SVCP |            |

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

  Information of predicates (identified by the operation identity card):

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

  4 - access("AIRDM_G02_F01".") IP_ID '= 'AIRDM_G02_F02'.' IP_ID")

  Oracle version:

  Oracle Database 11 g Enterprise Edition Release 11.2.0.4.0 - 64 bit Production

  PL/SQL Release 11.2.0.4.0 - Production

  CORE Production 11.2.0.4.0

  AMT for Linux: Version 11.2.0.4.0 - Production

  NLSRTL Version 11.2.0.4.0 - Production

  Notice how this additional distribution has disappeared from the non-partitioned table.

  I think that with the partitioned table that oracle has tried to balance the number of slaves against the number of scores he expected to use and decided to distribute the data to get a 'fair sharing' workload, but had not authorized for the side effects of the buffer hash join which was to appear and extra messaging for distribution.

  You could try the indicator pq_distribute() for the insert to tell Oracle that he should not disrtibute like that. for example, based on your original code:

  Insert / * + append pq_distribute parallel (a, 16) (a zero) * / in dg.tiz_irdm_g02_cc one...

  This can give you the performance you want with the partitioned table, but check what it does to the space allocation that it can introduce a large number (16) of extensions by segment that are not completely filled and therefore be rather waste of space.

  Concerning

  Jonathan Lewis

• Question about parallel hint and 'alter table enable parallel DML'

  Hi all
  
  I have a DML as follows:
  
  Insert / * + append * / into table1
  Select *.
  of COMPLEX_VIEW;
  
  Here complex_view contains a very complicated SQL, in which there is some heavy tables joins, subqueries, and aggregations.
  
  Question 1:
  
  Let's assume that the underlying tables have no attribute "parallel." Where should I add "parallel index" to force it to be run in parallel and can get better performance?
  
  Some members think that what follows is good.
  
  Insert / * + append * / into table1
  Select / * + parallel (a 4) * / *.
  of COMPLEX_VIEW;
  
  But I think that indicators must be put in the defintion of the complex view where they should be and do not put advice to the main insert DML, like this:
  
  Insert / * + append * / into table1
  Select *.
  of COMPLEX_VIEW; -I added the indicators in the COMPLEX_VIEW.
  
  What is your opinion?
  
  Quesion2:
  Without ' alter session enable parallel DML ", I can see the parallel session in v$ px_session thus." And the execution time has been shortened. This proves without this statement, the DML is also run in parallel.
  
  So, what is the effect of this statement?
  
  Best regards
  Leon

  I prefer the suspicion out of the COMPLEX_VIEW. This way, only this application forces the suspicion. If you put the indicator in the COMPLEX_VIEW, any other query on COMPLEX_VIEW (or Assembly of COMPLEX_VIEW to another view or a table) would also "encode" indicator in its execution. You don't then isolation parallel query to only where it is needed.

  If you put the parallel indicator in SELECT it (or view), the query is parallelized. This does not necessarily mean that the INSERT is parallelized. What you see v$ px_session are only slaves to PQ to SELECT.
  You must ALTER SESSION ACTIVATE PARALLEL DML and add the PARALLEL indicator in the INSERT.

  Hemant K Collette

• Insert / * + append * / into TableName Select / * + parallel (t, 4, 1) * / * from Tabl

  Hello
  
  I use
  

  Insert  /*+ append */   into TableNew select  /*+ parallel( t,4,1) */  * from TableOld t

  to load data into a table through TableNew
  another table of the same structure - TableOld
  
  More than 4-5 hours it takes me to do this for about 1.5 million lines with a column defined as XMLType as well.
  
  -Are there any rules to determine the degree of parallelism, or is he just hit and a trial?
  - Or set none and let the optimizer?
  -Any other rule, I keep in mind to try to optimize this operation?
  
  Thank you...
  
  Published by: BluShadow on December 6, 2012 11:20
  addition of {noformat}

  {noformat} tags for readability.  Read: {message:id=9360002} and learn to do this yourself                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    

  Ben hassen says:

  user8941550 wrote:
  So I tried,

  Insert / * + append * / into TableNew select * from TableOld t
  and it is now running in an hour.

  No explanation for this.

  I don't recommend this way (insert into... Select..) for large tables.
  Because you have no ability to run a commit when inserting (first at the end of the insertion process that you can commit).
  It takes much more space-cancellation (if you run rollback after the insert statement).

  But, principal in blocks or pieces is not a transactional point of view and can cause more problems later if there is an error in one of the blocks of inserts, because you will not be able to easily restore data that has already been posted.
  I highly recommend to use a single INSERT. SELECT... statement in most cases (it's always going to be rare exceptions), simply to maintain transactional integrity.

  A better way is, define a cursor, read for blocked lines (e.g. 1000 lines), after every 1000 lines run a commit.

  That's a great way to a) slow down the process and b) make it difficult to restore it if a problem occurs.
  Whenever you issue a commit, it tells Oracle to write the data in the data files. Which is performed by the writer processes. By default, the database starts with N number of processes of writer ("N" depends on the configuration of database, so let's assume 4 processes of writer for example). Whenever a commit is issued, a writer process gets allocated to the task of writing the data to the data files as defined. The workload is shared between these processes, so if a further validation is issued and a single process for writer is already busy, then another process will consider this request. If the database starts to do a lot of approvals issued, and concludes that all the existing processes of the writer are busy, it will generate new writer processes to process new requests, taking up more resources (memory, files, and processes handles etc.) server and the writer process more, there is more chance they have of creating States of waiting between them as they all try and write to the data files (same) especially if the data is committed are closely for example same table and associated tablespace etc.). These resources are not released again when the tasks are complete, until the server is restarted or the stop of the Oracle, Oracle keeps them there in waiting, it will get the same kind of workload once again. Oracle is perfectly capable of treating millions of lines, suggesting that it is 'better' to insert into pieces of 1,000 records at a time, having committed after each, not only slows down the process of pl/sql code perspective, but also slows down things from a server resources point of view, as well as causing potential claim to IO file issues... including the possibility of having some i/o contention problems with disks. It is certainly NOT "a better way".

  These suggestions are usually given by people who do not understand the underlying architecture of databases Oracle, something which is taught on the Oracle DBA courses, and it's a course I would recommend that any so-called professional developer attends, even if they did not intend to be a DBA. How works the architecture of a database is probably useful to know how to write good code... not only in the Oracle, but some other RDBMS establishments (when I was a developer of Ingres database, I have followed the courses of Ingres DBA and it was also valuable to understand how to write good code).

• Doubt by inserting the Date and time in the table

  Hi I created a table with two columns "Order_ID" and "Order_date" as
  
  create table test
  (
  whole order_id,
  ORDER_DATE date default sysdate
  );
  
  Now, I insert a line in the
  insert into test (order_id) values (1);
  
  now, I get the result as
  ORDER_ID ORDER_DAT
  ------------- --------------
  1 JUNE 5, 12
  
  But I need to insert the time current system also in the Order_date column.
  How can I achieve this?

  It works well for me!

  bcm@bcm-laptop:~$ sqlplus user2/user2
  
  SQL*Plus: Release 11.2.0.1.0 Production on Mon Jun 4 20:19:57 2012
  
  Copyright (c) 1982, 2009, Oracle.  All rights reserved.
  
  Connected to:
  Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
  With the Partitioning, OLAP, Data Mining and Real Application Testing options
  
  20:19:58 SQL> @test1
  20:20:01 SQL> create table test1
  20:20:01   2  (
  20:20:01   3  order_id integer,
  20:20:01   4  order_date date default sysdate
  20:20:01   5  );
  
  Table created.
  
  20:20:01 SQL>
  20:20:01 SQL> insert into test1(order_id) values(1);
  
  1 row created.
  
  20:20:01 SQL> select * from test1;
  
    ORDER_ID ORDER_DATE
  ---------- -------------------
        1 2012-06-04 20:20:01
  
  20:20:01 SQL> 
  

• How can I insert a number to a specific index (row and column) to a table

  I had the most with function 'insert into array' problem because of its counter-intuitiveness. I want to insert a number I got inside a loop IN a table. The ROW and COLUMN of this table I want enter the number is specified by the number of loops of two loops FOR. It did not work.

  So, I have isolated and tested this function further. Frankly, I initialized a table 2D with ZEROS and plugged into the "insert into array" function (on top of entry). I then put the number '1' for the index (line) and the number "2" for the index (column) and then put the entry number "6" for the "new item/sub-table. Then, I hung a picture of 2-D (indicator) output to the output of the function "insert into array. When I did all that, it means I want to just put the number '6' in line '1' and the column '2'... This isn't letting me do it.

  How can I do this SIMPLE?

  Hi Darrell h...,

  Looks like you can use the function "autoindexing. Take your value and connect it to your loop, it will be a default autoindexing. Right-click on the last tunnel of output and select Create indicator, the result is your table.

  It will be useful.

  Mike

• How to use several adf 12 shape and insert the form data in to table during the click on "submit" button

  How to use several adf 12 shape and insert the form data in to table during the click on "submit" button. Can we use several form from adf or not?

  Make sure that you dragged the VO based EO.

  Also make sure that the VO attributes based EO Updatable property.

  The query according to VO is used only to add LOV to the column of the original VO ModelId.

  See you soon

  AJ