Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If the columns are different between DB1.table_name and DB2.table_name then you're going to have to specify a column list in the insert statement. Unfortunately, there's not really a "magic bullet" here.</p> <p>With that said, to speed up the process you could write some PL/SQL to generate the insert statements, and then you could fix those by hand. Here's a sample PL/SQL code to do this. In this example, l_src_table would be your source table and l_target_table would be your target table. Obviously, you'll still have to manually fix the SQL statement this code generates, but this will at least generate a template SQL which should save you a lot of time.</p> <pre><code>DECLARE l_insert_stmt VARCHAR2(4000); l_comma VARCHAR2(1) DEFAULT ' '; l_src_table VARCHAR2(500) := 'TABLE1'; l_src_table_owner VARCHAR2(500) := 'DB1'; l_target_table VARCHAR2(500) := 'TABLE2'; l_target_table_owner VARCHAR2(500) := 'DB2'; BEGIN l_insert_stmt := 'INSERT INTO ' || l_target_table || ' ( '; FOR rec IN (SELECT column_name FROM all_tab_columns WHERE TABLE_name = l_target_table AND owner = l_target_table_owner) LOOP l_insert_stmt := l_insert_stmt || l_comma || rec.column_name; l_comma := ','; END LOOP; l_insert_stmt := l_insert_stmt || ' ) '; l_insert_stmt := l_insert_stmt || ' SELECT '; l_comma := ' '; FOR rec IN (SELECT column_name FROM all_tab_columns WHERE TABLE_name = l_src_table AND owner = l_src_table_owner) LOOP l_insert_stmt := l_insert_stmt || l_comma || rec.column_name; l_comma := ','; END LOOP; l_insert_stmt := l_insert_stmt || ' FROM ' || l_src_table; dbms_output.put_line(l_insert_stmt); END; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. PODoes anyone have a sample data migration script (Oracle 10g to Oracle 10g, but different schemas)?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USdcp
    1. USdcp
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI tried the part to output just the Insert into (without the select). All I get output for each table is "Insert into table_name ( )" ... none of the column names are output.
      singulars
      1. PO
      1. USTheresa
    2. COOn the right track, but you aren't accounting for the ordering of the columns or that the column lists are different.
      singulars
      1. PO
      1. USAdam Hawkes
    3. COYou need to make sure to set the l_src_table, l_src_table_owner, l_target_table VARCHAR2(500), l_target_table_owner variables properly or it won't work. For example, you could try setting the values to this: l_src_table VARCHAR2(500) := 'ALL_OBJECTS'; l_src_table_owner VARCHAR2(500) := 'SYS'; l_target_table VARCHAR2(500) := 'ALL_TABLES'; l_target_table_owner VARCHAR2(500) := 'SYS'; This should at least give you a SQL statement with columns in it. Then you can just tweak the values to whatever's proper for your environment.
      singulars
      1. PO
      1. USdcp
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload