Possible to Exchange temporary table with composite range-hash partitioned table?

Similar Questions

• Rebuild the range-Hash partitioned local index

  Hi all
  
  We have a table with 400 million records in our dataware House environment. It is partitioned using range-Hash Partitioning composit. He used a global Indexes previously. Last month the global indices have been changed to the index the. Since then, Exchange and index rebuild partition takes twice against the take used previously. From my understanding local index should provide availability high and more usable in the warehouse environment. Please correct me if I'm wrong and give me your suggestion. Also, I'm looking for a good material for the exchange of the partition and Index rebild with locally manage the range-hash partitioned index. Let me know if you know a good link for this...
  
  
  Thanks in advance...

  Dear krmreddy,

  Carefully read the following link and I hope this will guide you;

  http://asktom.Oracle.com/pls/asktom/f?p=100:11:0:P11_QUESTION_ID:223318100346512896

  Kind regards.

  Ogan

• Adding a Partition to a range-Hash partitioned Table

  Hello

  I created the composite partition table (RANGE-HASH).  Oracle: 11.2, OS: HP UX

  CREATE TABLE 'XYZ '. "" TABLE_XYZ.

  (

  ----

  VARCHAR2 (54) "PROFILE" DEFAULT "000000000000000000' ENABLE NON-NULL"

  NUMBER (21.7) "CREATED_ON" DEFAULT 0 ENABLE NOT NULL,.

  ----

  )

  PARTITION BY RANGE

  (

  CREATED_ON

  )

  SUBPARTITION BY HASH

  (

  VIEW PROFILE

  )

  SUBPARTITION TEMPLATE

  (

  SUBPARTITION SP1 TABLESPACE PSAPISU,

  SUBPARTITION TABLESPACE PSAPISU SP2,

  SUBPARTITION SP3 TABLESPACE PSAPISU,

  SUBPARTITION SP4 TABLESPACE PSAPISU,

  SUBPARTITION SP5 TABLESPACE PSAPISU,

  SUBPARTITION SP6 TABLESPACE PSAPISU,

  SUBPARTITION SP7 TABLESPACE PSAPISU,

  SUBPARTITION SP8 TABLESPACE PSAPISU,

  SUBPARTITION SP9 TABLESPACE PSAPISU,

  SUBPARTITION SP10 TABLESPACE PSAPISU,

  SUBPARTITION SP11 TABLESPACE PSAPISU,

  SUBPARTITION SP12 TABLESPACE PSAPISU,

  SUBPARTITION SP13 TABLESPACE PSAPISU,

  SUBPARTITION SP14 TABLESPACE PSAPISU,

  SUBPARTITION SP15 TABLESPACE PSAPISU,

  SUBPARTITION SP16 TABLESPACE PSAPISU,

  SUBPARTITION SP17 TABLESPACE PSAPISU,

  SUBPARTITION SP18 TABLESPACE PSAPISU,

  SUBPARTITION SP19 TABLESPACE PSAPISU,

  SUBPARTITION SP20 TABLESPACE PSAPISU,

  SUBPARTITION SP21 TABLESPACE PSAPISU,

  SUBPARTITION SP22 TABLESPACE PSAPISU,

  SUBPARTITION SP23 TABLESPACE PSAPISU,

  SUBPARTITION SP24 TABLESPACE PSAPISU,

  SUBPARTITION SP25 TABLESPACE PSAPISU

  )

  (

  CREATED_ON_OCP01 PARTITION VALUES LESS THAN (20090101000000).

  CREATED_ON_OCP02 PARTITION VALUES LESS THAN (20090401000000).

  CREATED_ON_OCP03 PARTITION VALUES LESS THAN (20090701000000).

  CREATED_ON_OCP04 PARTITION VALUES LESS THAN (20091001000000).

  CREATED_ON_OCP05 PARTITION VALUES LESS THAN (20100101000000).

  CREATED_ON_OCP06 PARTITION VALUES LESS THAN (20100401000000).

  CREATED_ON_OCP07 PARTITION VALUES LESS THAN (20100701000000).

  CREATED_ON_OCP08 PARTITION VALUES LESS THAN (20101001000000).

  CREATED_ON_OCP09 PARTITION VALUES LESS THAN (20110101000000).

  CREATED_ON_OCP10 PARTITION VALUES LESS THAN (20110401000000).

  CREATED_ON_OCP11 PARTITION VALUES LESS THAN (20110701000000).

  CREATED_ON_OCP12 PARTITION VALUES LESS THAN (20111001000000).

  CREATED_ON_OCP13 PARTITION VALUES LESS THAN (20120101000000).

  CREATED_ON_OCP14 PARTITION VALUES LESS THAN (20120401000000).

  CREATED_ON_OCP15 PARTITION VALUES LESS THAN (20120701000000).

  CREATED_ON_OCP16 PARTITION VALUES LESS THAN (20121001000000).

  CREATED_ON_OCP17 PARTITION VALUES LESS THAN (20130101000000).

  CREATED_ON_OCP18 PARTITION VALUES LESS THAN (20130401000000).

  CREATED_ON_OCP19 PARTITION VALUES LESS THAN (20130701000000).

  CREATED_ON_OCP20 PARTITION VALUES LESS THAN (20131001000000).

  CREATED_ON_OCP21 PARTITION VALUES LESS THAN (20140101000000).

  CREATED_ON_OCP22 PARTITION VALUES LESS THAN (20140401000000).

  CREATED_ON_OCP23 PARTITION VALUES LESS THAN (20140701000000).

  CREATED_ON_OCP24 PARTITION VALUES LESS THAN (20141001000000).

  CREATED_ON_OCP25 PARTITION VALUES LESS THAN (20150101000000).

  PARTITION CREATED_ON_OCPMAX VALUES LESS THAN (MAXVALUE)

  )

  TABLESPACE "PSAPISU" ENABLE LINE MOVEMENT;

  Now, I am trying to add the new partition but becomes under errors:

  ALTER TABLE SAPISU. ADD PARTITION VALUES LESS THAN (20150401000000) CREATED_ON_OCP26 ZTMD_300_VERS_MANAGE

  *

  ERROR on line 1:

  ORA-14074: partition bound must gather greater than that of the last partition

  ERROR on line 1:

  ORA-14018: partition bound list contains too few elements

  I tried the SYNTAX mentioned by Oracle DOC, still getting error. Partitioned table and index management

  Could if it you please let me know, what is the exact syntax that I should follow?

  See you soon

  Sameer

  CREATED_ON_OCPMAX PARTITION SPLIT THAN (MAXVALUE)

  That don't mean to 'divide' the MAXVALUE partition.

  You cannot split a partition that contains the values of A, B, C, D, MAXVALUE to MAXVALUE; that makes no sense. ERROR on line 1:

  ORA-14080: partition cannot be split along the specified high limit

  That exception is to say you can't use MAXVALUE upper limit. You must use a value that is actually IN the partition.

  Go back and look at the definition of your partitions:

  CREATED_ON_OCP25 PARTITION VALUES LESS THAN (20150101000000).

  PARTITION CREATED_ON_OCPMAX VALUES LESS THAN (MAXVALUE)

  See which ends with: "VALUES LESS THAN (MAXVALUE)? MAXVALUE is not IN the score; This is the upper limit of the partition.

  Divide certain value > '20150101000000' and LESS THAN MAXVALUE;

  So if you try to create a partition for OCP26 you can use '20160101000000'.

  CREATE TABLE PART_TEST2)
  VARCHAR2 (54) DEFAULT PROFILE "000000000000000000' ENABLE NOT NULL,
  CREATED_ON NUMBER (21.7) DEFAULT 0 ENABLE NOT NULL
  )
  PARTITION BY RANGE (CREATED_ON)
  (
  CREATED_ON_OCP24 PARTITION VALUES LESS THAN (20141001000000).
  CREATED_ON_OCP25 PARTITION VALUES LESS THAN (20150101000000).
  PARTITION CREATED_ON_OCPMAX VALUES LESS THAN (MAXVALUE)
  )

  ALTER table split partition created_on_ocpmax part_test2
  to (20160101000000) into (partition, partition CREATED_ON_OCPMAX created_on_ocp26)

• Range of partitioning of the interval

  Hello
  
  
  Using Oracle 11.20.3
  We want to have a table partitioned composite range-hash, a partition for each month.
  
  However, want to esnure are still a tehrfore partition would use range interval partitioning.
  
  Have a few questions, if I say 201301 to 201312 but get intellectualization rosw partition with a value date in June 2014 it create
  a new partition for each month IE 201401, 201402 etc. or just a 201406?
  
  Wanyt esnure system can automatically dial with a scenario
  
  Daty1 have partitions 201301 to 201312
  
  Day 2 get record for 201406 (June 2014)
  
  Day 3 get record for 201403 (March 2014)
  
  
  We have no control over the date range, we were able to get but don't want to tpo have to manually create partitions BOF tehse all dates in advance - want system she managed automatically.
  
  Also you can just rename it the names of system partition generated to something more useful later.

  Yes, the creation of partitions of the interval is 'rare' - a given partition will be created only when necessary. (This should be easy to try, by the way).

• Range-Hash verssu Hash Partitioning purely report performance

  Hello
  
  We evaluate different strategies and whereas hash and range-hash partitioning.
  
  While the range would give us additional cleaning options, is by far out up to priority for the reports to run as fast as possible.
  
  Central Oraxcle 11.2.0.3 in fact warehouse using large table estaimte will be 500 GB, surrogarte key star schema and the key to the substitution of the largest dimesnion partioned-hash with the surrogate key.
  
  According to your experience, the side purley perfomance queruy someone found the hash is significantly greater than parrtition by range of dates, then under hash partition.
  
  Queries do not use partition size.
  
  Greater hope of qwe benfit to win partitioning uses a parallel query + score-recognition of join between columns of hash-partitioedn (on the facts and the great dimesnion table.
  
  Thank you

  >
  We evaluate different strategies and whereas hash and range-hash partitioning.

  While the range would give us additional cleaning options, is by far out up to priority for the reports to run as fast as possible.

  Central Oraxcle 11.2.0.3 in fact warehouse using large table estaimte will be 500 GB, surrogarte key star schema and the key to the substitution of the largest dimesnion partioned-hash with the surrogate key.

  According to your experience, the side purley perfomance queruy someone found the hash is significantly greater than parrtition by range of dates, then under hash partition.

  Queries do not use partition size.

  Greater hope of qwe benfit to win partitioning uses a parallel query + score-recognition of join between columns of hash-partitioedn (on the facts and the great dimesnion table.
  >
  Objectives statements in this thread have some of the same problems and missing information that was your other thread.
  Re: Compress all the existing table ain dat

  So I would say the same thing, that I suggested it with minor changes.

  You give us your preferred solution instead of us giving that information about the PROBLEM you're trying to solve.

  You must first focus on the problem:

  1. define the problem - indicate the desired objectives
  2. identify the options and resources available to address the problem
  3. Select one or several small, these options for assessment earn and tests.
  4 testing of possible solutions
  5. Select and implement what you consider the "best" solution
  6. monitor the results
  >
  We evaluate different strategies and whereas hash and range-hash partitioning.
  >
  Why? 1. What is the problem that you are trying to address and what are your desired goals? Partitioning is a solution - what's the problem?
  >
  While the range would give us additional cleaning options, is by far out up to priority for the reports to run as fast as possible.
  >
  Great! Do you really need or even want options housekeeping? If so, which? Don't you bulk loads? Down periodically the data? How many times? Monthly? Every year?

  What is the relationship, in your analysis between partitioning and your reports running "as fast as possible? Give us some details. Why do you partitioning in general (range or range-hash in particular) will somehow make your reports run faster? What kind of reports? The amount of data they have access to produce? The amount of data returned in fact? How many times reports do work? How much of a problem reports are now? Generally meet their SLA? Or they RARELY meet their SLA?

  Partitioning is not a remedy of performance for badly written queries. Often the most effective way to improve the performance of reports is to resolve any issues the queries themselves may have or add appropriate indexes. You have exhausted these possibilities? Have you created and examined the execution plans for your key reports? That shows this analysis?
  >
  According to your experience, the side purley perfomance queruy someone found the hash is significantly greater than parrtition by range of dates, then under hash partition.
  >
  For a partitioned table, all data are stored in individual segments; a segment for each partition.

  For a partitioned table Sub all data are stored in the individual segments; a segment for each subpartition. There is NO data stored at the partition level.

  The type of partitioning (versus range-hash hash) and the type of data (partition versus subpartion) logic has no relevance in terms of performance.

  Performance of the queries are directly proportional the number of segments that should be available, the type of access (via the index or full scan) and the size of the segment (including the amount of data).

  The number of segments that should be available depends on the ability of the Oracle to prune partitions during the analysis statically or dynamically at run time.
  >
  Queries do not use partition size.
  >
  Partitioning then generally won't be valuable performance but only for maintenance operations.
  >
  Greater hope of qwe benfit to win partitioning uses a parallel query + score-recognition of join between columns of hash-partitioedn (on the facts and the great dimesnion table.
  >
  Please explain why you think that partitioning will provide this benefit.

  Oracle PARALLEL query very well on non-partitioned tables without using partition-wise joins. The latest version of Oracle also has a DBMS_PARALLEL_EXECUTE package that provides additional features for the realization of PARALLEL operations for many of the use cases more.

  Partitioning lends itself to a natural method of CHUNKing based on the scores/subparts, but that is not necessary to get the benefit of the PARALLEL use. The exception would be if provided partitioning segments that are on different axes or decrease disk IO conflicts.

  Another missing piece of key information are the number and the type of index that needs your reports. Will you be able to use mainly LOCAL partitioned indexes? Global index tend to destroy any maintenance performance that can be learned from partitioning.

• Temporary table with dates

  I try to explain my problem:
  
  I have a query that lists sales grouped by day like this:
  
  SELECT S.DAY, SUM (S.AMOUNT)
  SALES S
  WHERE S.DAY BETWEEN SYSDATE-100 AND SYSDATE
  S.DAY GROUP
  
  I need the query also lists the days that were not given.
  I think the solution is to use a temporary table using subquery that has a list of values of days:
  
  SELECT D.DAY, SUM (S.AMOUNT)
  S (*) D, SALES
  WHERE S.DAY (+) = D.DAY
  GROUP OF D.DAY
  
  Anyone know how to create the subquery (*) with the list of all the days, from the range (for example, SYSDATE-100 to SYSDATE)?
  Thank you.

  Hello

  You'd have to utilze a little thing called a generator of line:

  SQL> select trunc(sysdate) -level your_date
    from dual connect by level < 10
  
  YOUR_DATE
  ---------
  16-FEB-11
  15-FEB-11
  14-FEB-11
  13-FEB-11
  12-FEB-11
  11-FEB-11
  10-FEB-11
  09-FEB-11
  08-FEB-11
  
  9 rows selected.
  

  Use it in your query in the form of conduct table and outer join to the table sales.

  Concerning
  Peter

• Doesn't work with temporary tables

  I try to make 'between' select server-side:
  
  < cfquery name = "issueList" datasource = "HOTLINE" >
  CREATE TABLE ##tmpIssues (ROWNUM INT IDENTITY (1, 1) INT ISSUE_ID);
  INSERT INTO ##tmpIssues (ISSUE_ID)
  SELECT dbo. QUESTIONS. ISSUE_ID
  FROM dbo. QUESTIONS
  WHERE THE...
  SELECT...
  INNER JOIN ##tmpIssues AS TI on dbo. QUESTIONS. ISSUE_ID = TI. ISSUE_ID
  WHERE TI. ROWNUM BETWEEN #Evaluate (displayRows * (StartRowOptional - 1) + 1) # #Evaluate(displayRows * startRow) AND #;
  DROP TABLE ##tmpIssues;
  
  and receive:
  
  Execution of the SQL statement is not allowed.
  
  When I delete all of the code except for create temporary table - error remains. I can't believe that it is not possible to create a temporary table inside cfquery!
  
  That is what it is? How to handle this?

  Thanks for the reply.

  I replaced the temporary table with the table variable, and it works properly now. Yes, I feel that this temporary table could lead to disorders... If I used it in a stored procedure, called from this request - it would work okay maybe... But if I want to do is universal - I need to pass parameters to query inside? Hell...: \
  I know that table variables have their own drawbacks. But at least I can guarantee you that there is no conflict between users. I use about 50 records per page - I guess it's ok for var table.

  I wish I went back any recordset object and managed beaches via StartRowOptional & LignesMax... But the problem is that any recordset returns records too and I want limit on serverside also...

• Global temporary table in PL/SQL with XML

  Hello

  I have the impression that it is something strange or maybe I'm missing something basic.

  Step 1: Create a global Temp table that should not be specific transaction.

  create a global temporary table Temp01

  (

  NUMBER OF TICKET_ID

  , Varchar2 (10) of the REGION

  NUMBER OF THE YEAR

  , CO_ID VARCHAR2 (10)

  ) ON COMMIT DELETE ROWS.

  Step 2:

  My XML that goes as a parameter to a new function.

  < TICKET >

  < TICKET_ID > 38498051 < / TICKET_ID >

  the USA < REGION > < / REGION >

  < YEAR > 2014 < / YEAR >

  XYZ123 < CO_ID > < / CO_ID >

  < / TICKET >

  Step 3: Create a Stand Alone function:

  -drop function aagarwal.wr_creation;

  create or replace FUNCTION XML_FUNC

  (

  ret_msg out varchar2,.

  p_xmlval IN varchar2

  )

  RETURN varchar2

  is

  l_xmlval varchar2 (4000): = p_xmlval;

  V_CO_ID VARCHAR2 (10);

  V_CODE VARCHAR2 (10);

  BEGIN

  BEGIN

  INSERT INTO Temp01

  (

  TICKET_ID,

  REGION,

  BLEACHED,

  CO_ID

  )

  SELECT

  EXTRACTVALUE (XmlType (p_xmlval), "/ TICKET/TICKET_ID ') ID,.

  EXTRACTVALUE (XmlType (p_xmlval), "/ TICKET/REGION") REGION.

  EXTRACTVALUE (XmlType (p_xmlval), "/ TICKET per YEAR"),.

  EXTRACTVALUE (XmlType (p_xmlval), "/ TICKET/CO_ID ') CO_ID

  FROM DUAL;

  ret_msg: = 'SUCCESS';

  -SELECT CO_ID IN V_CO_ID of aagarwal. TEMP_STAGE_WR;

  -return ret_msg;

  EXCEPTION

  WHILE OTHERS THEN

  ret_msg: = sqlerrm;

  Return ret_msg;

  END;

  BEGIN

  SELECT CO_ID INTO V_CO_ID FROM Temp01;

  / * MERGE IN the site is

  With the HELP of aagarwal. TEMP01 T

  WE (T.co_id = se.code AND se.type_nm = ' TYPE' and se.src_nm = T.region)

  WHEN NOT MATCHED THEN

  INSERT (ID, SRCNM, CODE, TYPENM)

  VALUES (SHARED_SEQ. NEXTVAL, T.region, T.co_id, 'TYPE');

  -commit; */

  return ret_msg | "ACE" | v_co_id;

  END;

  END;

  /

  Fact - created function.

  NOTE: MERGE statement is blocked and if the function was created in sweetness.

  Step 4: Call the function

  declare

  l_out varchar2 (50);

  l_outr varchar2 (50);

  p_xml XMLTYPE.

  Start

  l_outr: = XML_FUNC (l_out, ' < TICKET >)

  < TICKET_ID > 38498051 < / TICKET_ID >

  the USA < REGION > < / REGION >

  < YEAR > 2014 < / YEAR >

  XYZ123 < CO_ID > < / CO_ID >

  (< / TICKET > ');

  dbms_output.put_line (l_outr);

  end;

  /

  
  

  Step 5: Check the value being inserted into the temporary Table:

  
  Select * from temp01;

  
  

  So far so good.

  THE PROBLEM:

  Now I want to tweek the XML_FUNC function above by uncommenting MERGE statement, which brings me to an error that is not differentiable:

  I.e. PL/SQL: ORA-00942: table or view does not exist in line on MERGE pointing to Temp01 statement.

  NOTE: I tested this Merge statement explicitly (as long as the execution of Stand Alone and also by calling via anonymous block PLSQL) and its absolutely perfect work. And SITE table exist.

  PS: I would be grateful, if there is a better way to write this code? I'm not a regular PLSQL developer and so badly can write the code of practice.

  Kind regards

  AAG.

  Using 11.2.0.3:

  Owner of all these three objects is DBA.

  Are you sure?

  After the release of:

  Select object_name, object_type

  of object

  where object_name in ('TEMP01', 'SITE', 'XML_FUNC');

  You must grant the explicit right to select on the table for the owner of the function if the owners are different.

  This works as expected for me (user DEV has all 3 items):

  Connected to Oracle Database 11g Enterprise Edition Release 11.2.0.3.0

  Logged in as dev

  SQL >

  SQL > create a global temporary table Temp01)

  NUMBER OF TICKET_ID 2

  3, Varchar2 (10) of the REGION

  4, NUMBER OF THE YEAR

  5, CO_ID VARCHAR2 (10)

  6)

  7. ON COMMIT DELETE ROWS.

  Table created

  SQL >

  SQL > create table site)

  Identification number 2

  3, srcnm varchar2 (10)

  4, code varchar2 (10)

  5, typenm varchar2 (10)

  6  );

  Table created

  SQL > create the sequence shared_seq;

  Order of creation

  SQL >

  SQL >

  SQL > create or replace FUNCTION XML_FUNC)

  2 p_xmlval IN varchar2

  3)

  4 RETURN varchar2

  5 is

  6 l_xmlval xmltype: = xmltype (p_xmlval);

  7. START

  8

  9 INSERT INTO Temp01

  (10)

  TICKET_ID 11,

  REGION 12,

  13 YEARS,

  CO_ID 14

  15)

  16. SELECT ID EXTRACTVALUE(l_xmlval, '/TICKET/TICKET_ID'),

  17 EXTRACTVALUE(l_xmlval, '/TICKET/REGION') REGION,

  18 EXTRACTVALUE (l_xmlval, ' / TICKET per YEAR ') YEAR.

  19 EXTRACTVALUE(l_xmlval, '/TICKET/CO_ID') CO_ID

  20 FROM DUAL;

  21

  22. MERGE IN site

  23. WITH THE HELP OF TEMP01 T

  (24)

  25 T.co_id = se.code

  26 AND se.typenm = 'TYPE '.

  27 and se.srcnm = T.region

  28)

  29 WHEN NOT MATCHED THEN

  30 INSERT (ID, SRCNM, CODE, TYPENM)

  31 VALUES (SHARED_SEQ. NEXTVAL, T.region, T.co_id, 'TYPE');

  32

  33 return "SUCCESS";

  34

  35 END;

  36.

  Feature created

  SQL >

  SQL >

  SQL > set serveroutput on

  SQL >

  SQL >

  SQL > declare

  2

  3 l_outr varchar2 (50);

  4

  5. start

  6

  7 l_outr: = XML_FUNC (')

  8 38498051

  9 USA

  10 2014

  11 XYZ123

  12    ');

  13

  14 dbms_output.put_line (l_outr);

  15

  16 end;

  17.

  SUCCESS

  PL/SQL procedure successfully completed

  SQL > select * from site;

  ID CODE TYPENM SRCNM

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

  TYPE 1 USA XYZ123

• Working with temporary tables in PL/SQL processes

  So I'm trying to write a PL/SQL process and I have some difficulty. Here's what I do:
  
  -Create temporary tables
  -Put the data in them
  -Use the data in temporary tables to fill the main status table
  -Remove temporary tables
  
  I'm running into some problems when I try to create the tables. If I do as I would in SQL Server:
  
  SELECT field1, Field2
  IN TempTable1
  Of
  …
  
  Then, I get an error saying that there is no such thing as TempTable1. If I say:
  
  CREATE TABLE TempTable1 AS
  SELECT field1, Field2
  Of
  …
  
  Then I get "found CREATE, Expecting CASE or another statement." I know that to truncate or remove tables in a PL/SQL, I use EXECUTE IMMEDIATE. I do the same thing for the creation of a table? If this is the case, how can I use run immediately on a query with apostrophe inside multi-line?
  
  Thank you!

  Use of temporary tables in Oracle is different from MS Sql Server.
  In Oracle, you create tables Temp the same way you would normally create a permanent table.
  Search syntax "create a global temporary table.
  Oracle global temporary tables are visible to all connections, but don't share all the data.
  The data are visible only for connections that introduced the data and are removed on commit / rollback, or when the connection ends.
  So Structure is permanent, data is temporary and exclusive to a single connection.

  If your process should look like this:

  Create global temporary tables - once - at the same time, you create all of the other tables in your system.

  -Fill the temporary tables.
  -use the data in temporary tables to fill the main report table
  -remove the data from the temporary tables.

  Information on the Temp in Oracle tables:
  http://download.Oracle.com/docs/CD/B19306_01/server.102/b14231/tables.htm#sthref2213

  HTH
  Thomas

• Temporary tables are themselves created, name starting with BIN$...

  Hello
  
  I use Oracle 10.2 and a problem that make certain operations on existing tables, some temporary tables to develop starting with BIN$.
  
  For ex: BIN$ HULdSlmnRZmbCXAl/pkA9w == $0
  
  But I do not see these tables in the database after two or three days. I found that these temporary tables are a replica of the existing tables and these contain only the structure of the table, but not the data. I couldn't even drop database.
  
  Can someone throw some tips on this?
  
  Thank you and best regards,
  Siva

  These paintings are in the trash of Oracle. When you delete a table, Oracle renames just for BIN$ xxx so that you can undrop table if you made a mistake.

  -You can ignore tables in the trash if you wish. Oracle purge them automatically when it needs the space.
  -You can prevent a table goes the trash by adding the command serve down, i.e.

  DROP TABLE table_name PURGE
  

  -You can empty the trash using the command

  SQL> purge dba_recyclebin
  

  (or just recyclebin if you do wish to erase objects you own to the recyclebin).

  Justin

• Is a database table that is required for the temporary interfaces with the data flat file source?

  People, this is the situation I ODI 11.1.1.7

  1. I have an interface temporary (yellow), called MJ_TEMP_INT, which uses data from TWO sets of data from the source in a temporary target (TEMP_TARG). Wrestling is a shot of a data set from a table while the other set of data extracted from a flat file.  A union is made on data sets.
  2. I then create another interface, called MJ_INT, which uses the MJ_TEMP_INT as the source and the target is a real database. table called "REAL_TARGET".

  Two questions:

  1. When I run my second interface (MJ_INT), I get a message "ORA-00942: table or view does not exist" because it is looking for a real TEMP_TARG db table. Why I have to have one? because I am pulling a flat file?
  2. On my second interface (MJ_INT) when I look at the interface of my source MJ_TEMP_INT (yellow) property sheet, the box 'Use the temporary interface as a Derived table' is DISABLED.  Why? Is also because my temporary interface is pulling from a flat file?

  I am attaching a file that shows a screenshot of my studio ODI.

  Furthermore, IF my temporary source interface has only a single set of data by pulling from a database. Table to table in a temporary target, called MJ_TEMP2_TARG, and then when I use this temporary interface as a source to the other another real db. target table (REAL2_TARGET), THEN everything works.  ODI requires me to have a real database. Table MJ_TEMP2_TARG and the checkbox for "interface temporary use as a Derived table" is NOT DISABLED and my REAL2_TARGET table gets filled.

  Thank you in advance.

  Mr. Jamal.

  You quite rightly assume the reasons that you have questions is because you try to attach a file. A file I always have to be materialized in the transit zone, as a temporary table and then have the data loaded in it.

• GeoRasters mosaicing with global temporary tables

  Mosaicing function requires that all individual images (there is a picture in each record) be in their own table before can be mosaiced, that there is no way to predict that some of the images in a table should be used.
  
  So, the best idea I've had so far is to use a global temporary table where the images I need can be selected and put in the temporary table - then mosaiced. It is important that the temporary table contain only the images necessary to a mosaic of data. However, I'll be at performs the operation of mosaic several times in a given session (perhaps even more 1 mosaic at the same time) and worry that there will be documents unrelated to the temporary table or former.
  
  Does this mean that I have to do a new session every time I need a picture of the mosaic? It seems not very effective. Can I have just one session, but a 'new' table temp every time?
  
  Thank you
  HD

  MH, creating an oracle georaster objects "VIEW", no matter where they are actually stored, would suit your needs. The mosaic georaster works on georaster views, which are treated as regular georaster tables.

  Jeffrey

• Need help with a global temporary table

  Can someone please help, the following line of code:
  
  CREATE TEMPORARY TABLE global tbl_bulknodes_temp (obt_uuid VARCHAR2) ON COMMIT DELETE ROWS
  
  Yeilds the following error running in SQL and PL/SQL
  
  Error from the 1 in the command line:
  CREATE TEMPORARY TABLE global tbl_bulknodes_temp (obt_uuid VARCHAR2) ON COMMIT DELETE ROWS
  Error report:
  SQL error: ORA-00906: lack of left parenthesis

  Hello

  You need the length of varchar2 column...

  SQL> CREATE GLOBAL TEMPORARY TABLE tbl_bulknodes_temp ( obt_uuid VARCHAR2(30) ) ON COMMIT DELETE ROWS;
  
  Table created
  
  SQL> CREATE GLOBAL TEMPORARY TABLE tbl_bulknodes_temp2 ( obt_uuid VARCHAR2 ) ON COMMIT DELETE ROWS;
  
  CREATE GLOBAL TEMPORARY TABLE tbl_bulknodes_temp2 ( obt_uuid VARCHAR2 ) ON COMMIT DELETE ROWS
  
  ORA-00906: missing left parenthesis
  
  SQL> 
  

  Kind regards

• Is it possible to copy a table partitioned to another different partitioned table statistics?

  Hello

  Using oracle 11.2.0.3 and study the possibility to copy his stats of a hash range partitioned table to another partitioned table range-hash.

  New table is based on the old table with the same structure, about right. of lines.

  estimate_percent auto not practical sample - size took 10 hours in tests and careful to just down for example 1% percent estimate.

  Is it possible to simply copy the stats on our old table

  Thank you

  Mismatch / typo in statid?

  statid-online "CURRENT_STATS."

  statid => ' CURRENT_STATUS

• Global temporary Table problem in ADF

  Hello
  
  I have an application where I need to use a TWG (on the ranks of commit preserve) DB and try to insert data to TWG of screw ADF.
  But the table does not store data even after the Commit command. [Even I tried with permament DB table, and it worked.]
  
  Could someone help me find the problem with inserting data TWG.
  
  
  Kind regards
  Manju

  It is not a good idea to use a global temporary Table in an ADF application. The problem is that all web applications are really stateless. ADF maintains the State of a session data backup or reload it when necessary. Regarding the database, ADF can disconnect a session from the database at any time and connect to another session. This means that you do not necessarily have a continuous database session, then the lines you wrote to a TWG may well gone with the following query. There are ways to tell ADF not to do, but they have a considerable performance drop.

  Therefore, rethinking how you will save temporary information for the duration of a user session. You can do it in an object view ADF BC (VO) - interviewed by VO data carried session - if ADF needs to share a user session to load the data of another user (this is called "passivation") it will save these data. Then when ADF 'active' session, he'll find the saved data and reload it. Or you can use a permanent table with your name or session id - a little more complicated, but possible.

  If you want to tell us a little bit your use case - you need your application to do so, we may have other alternatives.