DB Link Create table as select

I ve a query which starts with create table as select ..
When I run the select part of the query, it runs in 2 sec.
But the whole query runs in 10min. It is fetching data from dblink.
I think if select can finish in 2 sec. All is left to do is create table and insert.
Why is takin so long?
Oracle DB version 9.2.0.8

When I run the select part of the query, it runs in 2 sec.Does the select finish in 2 seconds or does it start returning rows in 2 seconds?
Big difference.

Similar Messages

Create table as select (CTAS)statement is taking very long time.

Hi All,
One of my procedure run a create table as select statement every month.
Usually it finishes in 20 mins. for 6172063 records and 1 hour in 13699067.
But this time it is taking forever even for 38076 records.
When I checked all it is doing is CPU usage. No I/O.
I did a count(*) using the query it brought results fine.
BUT CTAS keeps going on.
I'm using Oracle 10.2.0.4 .
main table temp_ip has 38076
table nhs_opcs_hier has 26769 records.
and table nhs_icd10_hier has 49551 records.
Query is as follows:
create table analytic_hes.temp_ip_hier as
select b.*, (select nvl(max(hierarchy), 0)
from ref_hd.nhs_opcs_hier a
where fiscal_year = b.hd_spell_fiscal_year
and a.code in
(primary_PROCEDURE, secondary_procedure_1, secondary_procedure_2,
secondary_procedure_3, secondary_procedure_4, secondary_procedure_5,
secondary_procedure_6, secondary_procedure_7, secondary_procedure_8,
secondary_procedure_9, secondary_procedure_10,
secondary_procedure_11, secondary_procedure_12)) as hd_procedure_hierarchy,
(select nvl(max(hierarchy), 0) from ref_hd.nhs_icd10_hier a
where fiscal_year = b.hd_spell_fiscal_year
and a.code in
(primary_diagnosis, secondary_diagnosis_1,
secondary_diagnosis_2, secondary_diagnosis_3,
secondary_diagnosis_4, secondary_diagnosis_5,
secondary_diagnosis_6, secondary_diagnosis_7,
secondary_diagnosis_8, secondary_diagnosis_9,
secondary_diagnosis_10, secondary_diagnosis_11,
secondary_diagnosis_12, secondary_diagnosis_13,
secondary_diagnosis_14)) as hd_diagnosis_hierarchy
from analytic_hes.temp_ip b
Any help would be greatly appreciated

Hello
This is a bit of a wild card I think because it's going to require 14 fill scans of the temp_ip table to unpivot the diagnosis and procedure codes, so it's lilkely this will run slower than the original. However, as this is a temporary table, I'm guessing you might have some control over its structure, or at least have the ability to sack it and try something else. If you are able to alter this table structure, you could make the query much simpler and most likely much quicker. I think you need to have a list of procedure codes for the fiscal year and a list of diagnosis codes for the fiscal year. I'm doing that through the big list of UNION ALL statements, but you may have a more efficient way to do it based on the core tables you're populating temp_ip from. Anyway, here it is (as far as I can tell this will do the same job)
WITH codes AS
(   SELECT
        bd.primary_key_column_s,
        hd_spell_fiscal_year,
        primary_PROCEDURE       procedure_code,
        primary_diagnosis       diagnosis_code,
    FROM
        temp_ip
    UNION ALL
    SELECT
        bd.primary_key_column_s,
        hd_spell_fiscal_year,
        secondary_procedure_1    procedure_code,
        secondary_diagnosis_1    diagnosis_code
    FROM
        temp_ip
    UNION ALL
    SELECT
        bd.primary_key_column_s,
        hd_spell_fiscal_year,
        secondary_procedure_2    procedure_code ,
        secondary_diagnosis_2    diagnosis_code
    FROM
        temp_ip
    UNION ALL
    SELECT
        bd.primary_key_column_s,
        hd_spell_fiscal_year,
        secondary_procedure_3    procedure_code,
        secondary_diagnosis_3    diagnosis_code
    FROM
        temp_ip
    UNION ALL
    SELECT
        bd.primary_key_column_s,
        hd_spell_fiscal_year,
        secondary_procedure_4    procedure_code,
        secondary_diagnosis_4    diagnosis_code
    FROM
        temp_ip
    UNION ALL
    SELECT
        bd.primary_key_column_s,
        hd_spell_fiscal_year,
        secondary_procedure_5    procedure_code,
        secondary_diagnosis_5    diagnosis_code
    FROM
        temp_ip
    UNION ALL
    SELECT
        bd.primary_key_column_s,
        hd_spell_fiscal_year,
        secondary_procedure_6    procedure_code,
        secondary_diagnosis_6    diagnosis_code
    FROM
        temp_ip
    UNION ALL
    SELECT
        bd.primary_key_column_s,
        hd_spell_fiscal_year,
        secondary_procedure_7    procedure_code,
        secondary_diagnosis_7    diagnosis_code
    FROM
        temp_ip
    UNION ALL
    SELECT
        bd.primary_key_column_s,
        hd_spell_fiscal_year,
        secondary_procedure_8    procedure_code,
        secondary_diagnosis_8    diagnosis_code
    FROM
        temp_ip
    UNION ALL
    SELECT
        bd.primary_key_column_s,
        hd_spell_fiscal_year,
        secondary_procedure_9    procedure_code,
        secondary_diagnosis_9    diagnosis_code
    FROM
        temp_ip
    UNION ALL
    SELECT
        bd.primary_key_column_s,
        hd_spell_fiscal_year,
        secondary_procedure_10 procedure_code,
        secondary_diagnosis_10    diagnosis_code
    FROM
        temp_ip
    UNION ALL
    SELECT
        bd.primary_key_column_s,
        hd_spell_fiscal_year,
        secondary_procedure_11 procedure_code,
        secondary_diagnosis_11    diagnosis_code
    FROM
        temp_ip
    SELECT
        bd.primary_key_column_s,
        hd_spell_fiscal_year,
        secondary_procedure_12 procedure_code,
        secondary_diagnosis_12    diagnosis_code
    FROM
        temp_ip
), hd_procedure_hierarchy AS
(   SELECT
        NVL (MAX (a.hierarchy), 0) hd_procedure_hierarchy,
        a.fiscal_year
    FROM
        ref_hd.nhs_opcs_hier a,
        codes pc
    WHERE
        a.fiscal_year = pc.hd_spell_fiscal_year
    AND
        a.code = pc.procedure_code
    GROUP BY
        a.fiscal_year
),hd_diagnosis_hierarchy AS
(   SELECT
        NVL (MAX (a.hierarchy), 0) hd_diagnosis_hierarchy,
        a.fiscal_year
    FROM
        ref_hd.nhs_icd10_hier a,
        codes pc
    WHERE
        a.fiscal_year = pc.hd_spell_fiscal_year
    AND
        a.code = pc.diagnosis_code
    GROUP BY
        a.fiscal_year
SELECT b.*, a.hd_procedure_hierarchy, c.hd_diagnosis_hierarchy
FROM analytic_hes.temp_ip b,
       LEFT OUTER JOIN hd_procedure_hierarchy a
          ON (a.fiscal_year = b.hd_spell_fiscal_year)
       LEFT OUTER JOIN hd_diagnosis_hierarchy c
          ON (c.fiscal_year = b.hd_spell_fiscal_year)HTH
David

Identify tablspace in create table as select

I am trying to run a create table as select query that specifies which tablspace to create the table in. When I run the query below I get an error, any ideas?
create table roi_call_record_backup as (select * from prod.roi_call_record)
tablespace roi_data01;
null

Try this ...
create table roi_call_record_backup
tablespace roi_data01
as
(select * from prod.roi_call_record)
null

To make the query more efficient (create table wiht select command)

Hi,
I have written this query to create another table, but it takes approx two hours while both tables are indexed with 891353, 769023, i have used the following query.
create table source1 as select a.idx, a.source from tt a where a.idx not in (select b.idx from ttt b)
thanks

Try this one if you're on oracle 8i or older
create table source1 as
select a.idx, a.source
from tt a
where not exists (select null from ttt b where a.idx = b.idx)

CREATE TABLE AS SELECT PROBLEM

Dear members,
I created a table whose definition is a select query.
for ex: I created a table xx_customer as :
create table xx_customer as
select customer_name,customer_number
from xx_ar_customer
where org_id = '87'when i run the query
select count(*)
from xx_customer;The count was 120 records.
This was done as part of performance tunning.
Now few days after the table xx_customer was created few records were inserted into table xx_ar_customer for org_id = '87' .
So ideally the count should be more than 120 but its not.
when i run the same query again
select count(*)
from xx_customer;I get count as 120 Records which is wrong.
It looks like it not refreshing data. If i run the table definition query i am getting count as more than 120 but if i do a select on the table count is still 120.
Any ideas?
Thanks
Sandeep

Hi,
795291 wrote:
I cant create view. I tried that before. If i use view then my query runs for a very long time and if i create a table then the run time is reduced by half :)
So if we create Table as a select statement, then will it give data at the point of time it was created? Exactly!
Will it not give latest data?Not unless the latest data happens to be the same as the data at the time it was created.
CREATE TABLE AS is kind of like putting a photograph of yourself on your web site. If you smile, that doesn't mean the picture smiles.
CREATE VIEW is kind of like hanging a video camea from your hat, and streaming the output to your web page. As soon as you smile, the picture smiles. It's more expensive than a still picture.
A compromise apprioach is a Materialized View , which is really a type of table. Like any other table, it occupies space, and is relatively fast to use. You can define a materialized view to be refreshed at regular intervals (once a day, once an hour, once a week, ...) or whenever there is a change in the base table(s).

Create table as select statement.

Hello Oracle Gurus,
I am trying to create a table using select * from other table.
The procedure that I am following is this:-
I have a temp table whose signature is on commit delete rows.
I insert records in this table.
when I do select * from temp_table,perm_table I get some rows.
then I try to create a result_table using this
CREATE TABLE result_table
AS SELECT * FROM temp_table,perm_table;
I see the table in created but number of records in 0. Can anyone please explain where commit takes place while sequence in this query occurs.
Thanks
Edited by: user10696492 on Nov 10, 2009 8:47 AM

Create table statement is a ddl - so an implicit commit is performed before the create statement begins. The implicit commit will delete all the rows from the temp table. If it is feasible change the definition of the temp table to on commit preserve rows.

"Create Table from select Query" Vs "Insert into"

Hi
Schenaio:
My Select Query returns more than 10 million records, these records needs to be inserted into another table.
Approach 1:
I created table called TABLE1, and inserted the records using INSERT statement as a batch (batch size is 5000).
Approach 2:
I create table like,
CREATE TABLE TABLE1 AS <SELECT QUERY>
Here Apporach-1 took almost 40 minutes to complete the insert but Approach-2 took only 6 minutes.
If anybody knows why it is? And is there any way to improve the performance of Approach-1?.
Thanks
Nidhi

Most "batch" methods execute the same query multiple times. Row filtering is done after the rows are fetched from the source. The process of fetching all the rows could be a FullTableScan.
Therefore, a FullTableScan is executed for each batch of 5000 rows.
However, your query and batch definitions may well be different. We haven't seen the query and the execution plan.
Another point : How are you "filtering" the rows (i.e the second execution inserts rows 5001 to 10000 and does not attempt to reinsert rows 1 to 5000) ?
What is the overhead imposed by the filter ? (does the third execution have to exclude rows 1 to 10000 and inserts rows 10001 to 15000 and so on)
Hemant K Chitale

[Solved]SIMPLE Question ON "CREATE TABLE as SELECT".

Hi there,
I was wondering how to work it out smartly and briefly.
For example, I already have a "tableA" as following.
tableA
id name
1 name1
2 name2
create table tmp as
select id, name from tableA;
It will create the tmp table successfully.
If I want to add a new column 'tel' in tmp table,
I can run as following.
create table tmp as
select id, name, 999 tel, 'aaaaaaaaa' ps from tableA;
It will add 'tel NUMBER' column and 'ps char(9)' in tableA.
If I want to add 'col varchar(50)' in tableA,
I do not want to make a string which contains 50 characters in Select command.
How can I make it work in a smart way?
Thanks.
Phil
Message was edited by:
user615355

Is there a reason that you need this to be in a single statement? You would normally be better served here with a separate CREATE TABLE and INSERT (possibly as a direct path operation).
That said, you could use the CAST operator, i.e.
SCOTT @ jcave102 Local> create table a as select cast('a' as varchar2(50)) col1 from dual;
Table created.
Elapsed: 00:00:00.48
SCOTT @ jcave102 Local> desc a;
Name Null? Type
COL1 VARCHAR2(50)
SCOTT @ jcave102 Local> Justin

Create Table As Select From Select

Table_2
CREATE TABLE TABLE_2
"ID" VARCHAR2(10),
"EXCL" VARCHAR2(10),
"SEQ" NUMBER(10)
Inserts
INSERT INTO TABLE_2 (ID ,EXCL ,SEQ ) VALUES ('123456' ,'' ,1 );
INSERT INTO TABLE_2 (ID ,EXCL ,SEQ ) VALUES ('123456' ,'EX' ,2 );
INSERT INTO TABLE_2 (ID ,EXCL ,SEQ ) VALUES ('123456' ,'' ,3 );
INSERT INTO TABLE_2 (ID ,EXCL ,SEQ ) VALUES ('321654' ,'' ,4 );
INSERT INTO TABLE_2 (ID ,EXCL ,SEQ ) VALUES ('123798' ,'EX' ,5 );
INSERT INTO TABLE_2 (ID ,EXCL ,SEQ ) VALUES ('123785' ,'' ,6 );
INSERT INTO TABLE_2 (ID ,EXCL ,SEQ ) VALUES ('654787' ,'' ,7 );
INSERT INTO TABLE_2 (ID ,EXCL ,SEQ ) VALUES ('654787' ,'' ,8 );
INSERT INTO TABLE_2 (ID ,EXCL ,SEQ ) VALUES ('654787' ,'' ,9 );
INSERT INTO TABLE_2 (ID ,EXCL ,SEQ ) VALUES ('985217' ,'EX' ,10 );
INSERT INTO TABLE_2 (ID ,EXCL ,SEQ ) VALUES ('985217' ,'' ,11 );
INSERT INTO TABLE_2 (ID ,EXCL ,SEQ ) VALUES ('937158' ,'' ,12 );
INSERT INTO TABLE_2 (ID ,EXCL ,SEQ ) VALUES ('937158' ,'' ,13 );
Select *
ID EXCL SEQ
123456 1
123456 EX 2
123456 3
321654 4
123798 EX 5
123785 6
654787 7
654787 8
654787 9
985217 EX 10
985217 11
937158 12
937158 13
I need to create a table based on for all Records which are EXC not null - but I need to bring through all the records which have the same ID as EXC not null field.
Desired output: -
ID EXCL SEQ
123456 1
123456 EX 2
123456 3
123798 EX 5
985217 EX 10
985217 11
Any ideas folks?

Hi,
Here's one way:
CREATE     TABLE     table_x
AS
SELECT     *
FROM     table_2
WHERE     id     IN (
                 SELECT id
                 FROM    table_2
                 WHERE   excl     IS NOT NULL
;By the way, whenever you post formatted text (such as query results) on this site, type these 6 characters:
\(small letters only, inside curly brackets) before and after each section of formatted text, to preserve spacing.
You'll get better answers quicker if people can read:ID EXCL SEQ
123456 1
123456 EX 2
123456 3
123798 EX 5
985217 EX 10
985217 11
(for example) rather than
Deeds_2001 wrote:
ID EXCL SEQ
123456 1
123456 EX 2
123456 3
123798 EX 5
985217 EX 10
985217 11

Performance issue Create table as select BLOB

Hi!
I have a performance issue when moving BLOB´s between tables. (The size of images files are from 2MB to 10MB).
I'm using follwing statement for example,
"Create table tmp_blob as select * from table_blob
where blob_id = 333;"
Is there any hints that I can give when moving data like this or is Oracle10g better with BLOB's?

Did you find a resolution to this issue?
We are also having the same issue and wondering if there is a faster mechanism to copy LOBs between two table.

Sync with manually created tables or selected publication items

HI
I have the following situation :
Server side:
Table1, Table2,Table3,Table4,Table5,Table6
Client type1 :
Table1, Table2,Table3,Table4
Client type2:
Table3,Table4,Table5,Table6
so i cant create two different publications for clients.
I have 1 publication with Table1, Table2,Table3,Table4,Table5,Table6
In this situation, is it possible to synchronize with manually created lite database and tables, or mobile server knows how to sync only with snapshots created by his own ?
Sync process reports "sync ok" but nothing happens
And one more question is :
can i use some sync api to create database with snapshots
1,2,3,4 for client1 and snapshots 3,4,5,6 for client2?
Today it works in following way:
1)install mobile client on mobile devices
2)install mobile application type 1 and 2 on mobile devices
3)call msync to create database with snapshots 1-6 on all devices
4)client type 1 do not use tables 5,6 sync only tables 1,2,3,4
5)client type 2 do not use tables 1,2, sync only tables 3,4,5,6

only tables defined in the application and synchronised down to the client will be synchronised - manually created tables on the client are ignored (list of tables to be synchronised is controlled by the table c$table_list in the concli database)
for your requirement, either
use one application for both client types, but ignore the 'unused' tables in the client software - advantage=easy, disadvantage overhead in synchronising and composing data not needed
or
create two seperate applications .no problem about using the same table in multiple applications, we do that for reference data all of the time, sequences cannot be shared (but there is a work around for that), and then associate each client user to one or the other application - advantage=better meets the requirement, disadvantage=maintenance and different database names in the client configuration

Proble creating Table Type = Select in 10gR3

In a very simple example case I have a customers table that I am trying to create a Table Type of Select in the physical layer.
Using the Admin tool I create "New Physical tabe" and enter select * from customer where region = 'East'
If I "Update All Row Counts" it now shows 56 rows - which is correct
If I try and "view data" I get an error
[nQSError: 17001] Oracle Error Code: 936, messgae: ORA-00936: missing expression at OCI cal OCIStmtExecute.
[nQSError: 17010] SQL Statement preparation failed.
If I deploy the view I can go to sqlplus and select from it.
I have tried qualifying table name and selecting specific columns - I know its not a permission issue and presumably the fact that it counted rows correctly confirms it must have generated correct SQL.
I'm puzzled - what am I missing here?

This is standard behavior..Update Row Count work fine since SELECT COUNT (*) FROM (select * from customer where region = 'East') is a valid SQL, View Data doesn't work since your columns aren't named, so OBI cant select col1, col2, etc.
Hope this explains.
Michael
Edited by: mkooloos on Jan 17, 2011 3:48 PM

Insert, select and create table as give different results

Hi all
I have a strange situation with this three cases:
1) select statement: SELECT (...)
2) insert statement with that same select as above: INSERT INTO SELECT (...)
3) create table statement again with that same select: CREATE TABLE AS SELECT (...)
Each of these cases produce different number of rows (first one 24, second 108 and third 58). What's more the data for second and third case doesn't have any sense with what they should return. The first case returns good results.
One interesting thing is that select uses "UNION ALL" between 2 queries. When simple UNION is used, everything works fine and all three cases return 24 rows. Also if each query is run seaprately, they work fine.
Anyone encountered something like this? (before i create an SR :)
Database is 10.2.0.2 on AIX 5.3. It's a data warehouse.
Edited by: dsmoljanovic on Dec 10, 2008 3:57 PM

I understand UNION vs UNION ALL. But that doesn't change the fact that same SELECT should return same set of rows wether in INSERT, CREATE TABLE AS or a simple SELECT.
DB version is 10.2.0.2.
Here is the SQL:
INSERT INTO TMP_TRADING_PROM_BM_OSTALO
select
5 AS VRSTA_PLANIRANJA_KLJUC, u1.UNOS_KLJUC, t1.TRADING_TIP_KLJUC, i1.IZVOR_KLJUC, m1.ITEMNAME AS MJESEC,
l1.PLAN AS IZNOS, l1.TEKUA AS TEKUCA, l1.PROLA AS PROSLA, l1.PLANTEKUA_ AS IZNOS_TEKUCA, l1.PLANPROLA_ AS IZNOS_PROSLA, l1.TEKUAPROLA_ AS TEKUCA_PROSLA, l1.DATUM_UCITAVANJA
from
HR_SP_PLAN.L_12_ET_PROMETI_I_BRUTO_MARZA l1,
select
m1.ITEMIID, m1.ITEMNAME
from
HR_SP_PLAN.L_12_IT_4_MJESECI m1
where
UPPER (m1.ITEMNAME) NOT LIKE '%KVARTAL%' AND UPPER (m1.ITEMNAME) NOT LIKE '%GODINA%' AND UPPER (m1.ITEMNAME) NOT LIKE '%PROC%' and
m1.DATUM_UCITAVANJA = to_date('24.11.2008','dd.mm.yyyy')
union all
select -99, null from dual
) m1,
HR_SP_PLAN.L_12_IT_5_SEKTORI l2,
HR_SP_PLAN.L_12_IT_2_TIPOVI_OSTALO l3, HR_SP_PLAN.D_UNOS u1, HR_SP_PLAN.D_TRADING_TIP t1, HR_SP_PLAN.L_12_IT_1_PROMET_I_BM_OSTALO p1, HR_SP_PLAN.D_IZVOR i1
where
l1.ELIST = l2.ITEMIID and
l2.ITEMNAME = u1.UNOS_NAZIV and u1.USER_KLJUC = 12 and l2.DATUM_UCITAVANJA = to_date('24.11.2008','dd.mm.yyyy') and
l1.DIMENSION_1_PROMET = p1.ITEMIID and
p1.ITEMNAME = i1.IZVOR_NAZIV and i1.USER_KLJUC = 12 and p1.DATUM_UCITAVANJA = to_date('24.11.2008','dd.mm.yyyy') and
nvl(l1.DIMENSION_4_MJESEC , -99) = m1.ITEMIID and
l1.DIMENSION_2_TIPOVI = l3.ITEMIID and
l3.ITEMNAME = t1.TRADING_TIP_NAZIV and l3.DATUM_UCITAVANJA = to_date('24.11.2008','dd.mm.yyyy') and
l1.DATUM_UCITAVANJA = to_date('24.11.2008','dd.mm.yyyy') and
'PROC' = 'PLAN'
union all
select
4 AS VRSTA_PLANIRANJA_KLJUC, u1.UNOS_KLJUC, t1.TRADING_TIP_KLJUC, i1.IZVOR_KLJUC, m1.ITEMNAME AS MJESEC,
l1.PROCJENA AS IZNOS, l1.TEKUA AS TEKUCA, l1.PROLA AS PROSLA, l1.PROCJENATEKUA_ AS IZNOS_TEKUCA, l1.PROCJENAPROLA_ AS IZNOS_PROSLA, l1.TEKUAPROLA_ AS TEKUCA_PROSLA, l1.DATUM_UCITAVANJA
from
HR_SP_PLAN.L_13_ET_PROMETI_I_BRUTO_MARZA l1,
select
m1.ITEMIID, m1.ITEMNAME
from
HR_SP_PLAN.L_13_IT_4_MJESECI m1
where
UPPER (m1.ITEMNAME) NOT LIKE '%KVARTAL%' AND UPPER (m1.ITEMNAME) NOT LIKE '%GODINA%' AND UPPER (m1.ITEMNAME) NOT LIKE '%PROC%' and
nvl(ceil(to_number(m1.ITEMNAME)/3), mod(4, 5)) = mod(4, 5) and m1.DATUM_UCITAVANJA = to_date('24.11.2008','dd.mm.yyyy')
union all
select -99, null from dual
) m1,
HR_SP_PLAN.L_13_IT_5_SEKTORI l2, HR_SP_PLAN.L_13_IT_2_TIPOVI_OSTALO l3,
HR_SP_PLAN.D_UNOS u1, HR_SP_PLAN.D_TRADING_TIP t1,
HR_SP_PLAN.L_13_IT_1_PROMET_I_BM_OSTALO p1, HR_SP_PLAN.D_IZVOR i1
where
l1.ELIST = l2.ITEMIID and
l2.ITEMNAME = u1.UNOS_NAZIV and u1.USER_KLJUC = 13 and l2.DATUM_UCITAVANJA = to_date('24.11.2008','dd.mm.yyyy') and
l1.DIMENSION_1_PROMET = p1.ITEMIID and
p1.ITEMNAME = i1.IZVOR_NAZIV and i1.USER_KLJUC = 13 and p1.DATUM_UCITAVANJA = to_date('24.11.2008','dd.mm.yyyy') and
nvl(l1.DIMENSION_4_MJESEC , -99) = m1.ITEMIID and
l1.DIMENSION_2_TIPOVI = l3.ITEMIID and
l3.ITEMNAME = t1.TRADING_TIP_NAZIV and l3.DATUM_UCITAVANJA = to_date('24.11.2008','dd.mm.yyyy') and
l1.DATUM_UCITAVANJA = to_date('24.11.2008','dd.mm.yyyy') and
'PROC' = 'PROC';

CREATE TABLE A AS SELECT * FROM B WHERE 1 = 2'-Queries

Guys,
I request your guidance in the effect of Create table statement below:
CREATE TABLE A AS SELECT * FROM B WHERE 1 = 2';
Question:
1)What would be the PCTFREE value for table A-Would it inherit PCTFREE from table B?
2) Will table A be created with LOGGING or NO LOGGING?-Will it iinhert the same from table B?
3) What would be the degree of parallelism of table A?-Will it inherit the DOP from B?
Thank you very much for your guidance in advance..
Regards,
Bhagat

1 => it will inherit from the default value
2 => same thing
3 => same thing
The create table as select will only copy the structure of the source table and can copy the datas too. That is all.

Database link create but not fatch data from link database give me this err

Sir I create database link with this command system create link
but when I user query then system give me this error you see in blow
SQL> create database link xyz connect to mfatest identified by mfa786 using 'aamir';
Database link created.
SQL> select * from accbal@xyz;
select * from accbal@xyz
ERROR at line 1:
ORA-28546: connection initialization failed, probable Net8 admin error
ORA-02068: following severe error from XYZ
ORA-03113: end-of-file on communication channel
this is same database but diffrent user
scott user
mfatest user
please give me idea how i fatch data from link database/link other user
thank
aamir

On the machine where you get that error does this work ?
SQL> connect mfatest/mfa786@aamir
SQL> select count(*) from accbal;
If it doesn't, please post tnsnames.ora and sqlnet.ora from local machine, and the result, on remote machine, of
C:\> lsnrctl services

DB Link Create table as select

Similar Messages

Maybe you are looking for