SQL Developer 3.2 - Export DDL challenge

Hi,
I would like to Export DDL for approximately 300 of 1000 objects in a schema.  I have the names of all required tables for which I'd like to get the DDL in a table in my personal schema.  Is there a way that I can use this table as a driver for the built-in Export DDL utility or will I need to either go to the schema browser and hand-pick each of the 300 tables and/or from the Tools-Export DDL "Specify Objects" window?
I would like to make this more automated so that I dont have to keep clicking, scrolling, clicking my way through the list of required objects.  Any thoughts are appreciated, thanks.

1008686 wrote:
Hi,
I would like to Export DDL for approximately 300 of 1000 objects in a schema.  I have the names of all required tables for which I'd like to get the DDL in a table in my personal schema.  Is there a way that I can use this table as a driver for the built-in Export DDL utility or will I need to either go to the schema browser and hand-pick each of the 300 tables and/or from the Tools-Export DDL "Specify Objects" window?
I would like to make this more automated so that I dont have to keep clicking, scrolling, clicking my way through the list of required objects.  Any thoughts are appreciated, thanks.
There is no way to use sql developer to do that.
You can:
1. do it manually as you suggest
2. do it manually by writing a script that makes the appropriate DBMS_METADATA calls
3. use expdp to extract the metadata and create a DDL file.
The full DDL for a table will include a lot of components that many people don't even want, for example storage clauses.
The bigger issue you should address is why you don't already have the DDL to begin with. Best practices are to create the DDL and keep it in a version control system; not extract it after the fact.
I suggest you use the EXPDP utility to extract the DDL into a file so that you have it for future use.
If you plan to write a script there are plenty of examples on the web that show how to do that. Here is one:
http://www.colestock.com/blogs/2008/02/extracting-ddl-from-oracle-2-approaches.html

Similar Messages

  • SQL Developer is not exporting the time part of date data types.

    I need to export data from a table using sql developer. The column is a date data type but when I export the data to a csv, xls or an sql file with insert statements, sql developer only includes the date part without the time.
    Please kindly advise.
    Thanks,
    Erika

    What is your 4 digits Oracle version ?
    What is your SQL Developer version ?
    With Oracle XE and a schema named TEST I have:
    select * from t
    X                        
    04-FÉVR.-2010 21:24:40  If I use Tools/Database Export with all default settings with SQL Developer 2.1.0.63 I get following SQL file:
    --  Fichier créé - jeudi-février-04-2010  
    --  DDL for Table T
      CREATE TABLE "T"
       (     "X" DATE
    --   DATA FOR TABLE T
    --   FILTER = none used
    REM INSERTING into T
    Insert into T (X) values (to_timestamp('04/02/10 21:24:40,000000000','DD/MM/RR HH24:MI:SS,FF'));
    --   END DATA FOR TABLE T
    ---------------------------------------------------Edited by: P. Forstmann on 4 févr. 2010 21:26

  • SQL Developer objects not showing DDL

    Greetings! First time posting here on the Oracle forums, so hopefully I can be as specific as possible :)
    I'm having an issue with displaying the SQL that makes up an object, specifically a VIEW.
    Here is the scenario:
    I log on as an IT user - WDSQUERY (this account can be used my multiple folks for querying in different schemas). I navigate down to other users and expand that node. I find the schema I want to use, ALCHEMY, and expand that node.
    It now places me in the ALCHEMY realm we'll call it. I should be able to see all the different objects owned by this schema (assuming permissions are set up). I click on the 'VIEWS' node to expand all the view objects. I can see the data and columns. What I cannot see is the SQL that generates that view, and I have no idea why.
    Co-worker of mine uses Toad, and he can do the exact same scenario (same user id, goes to same schema, etc.), however when he clicks on the 'Script' tab, it will generate the SQL that builds that view. Which leads me to believe this isn't a permission issue, because he's on the exact same user_ID.
    Is there some option I don't have checked somewhere in SQL Developer? The current work around for this is that I simply query the DBA_VIEWS where owner = 'ALCHEMY', and then pull out the name/text of the view I want. But....still this is just one of those things I want to know why it isn't working.
    Here are the little ORA codes I'm getting when trying to view the SQL code of the VIEW:
    ORA-31603: object "PO_LINE" of type VIEW not found in schema "ALCHEMY"
    ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
    ORA-06512: at "SYS.DBMS_METADATA", line 2806
    ORA-06512: at "SYS.DBMS_METADATA", line 4333
    ORA-06512: at line 1
    Any help would be GREATYLY appreciated!

    Hi,
    If you can see the objects in the 'Other Users' schema, then I would imagine your user_ID has the SELECT ANY DICTIONARY system privilege. Seeing the data and DDL requires additional privileges, however. I haven't looked deeply enough to be absolutely sure, but there are two or three methods that SQL Developer uses:
    1) If you have SELECT ON <other user_ID>.<viewname> object privilege, then you can see both data and DDL.
    2) Otherwise if you have EXECUTE ON DBMS_METADATA you can see the DDL (except it may depend on other privileges too(?)).
    Sorry I don't have time to dig deeper into DBMS_METADATA. It works on some of my connection users but not others. And, of course, privileges like SELECT ON DBA_VIEWS always give one an unfair advantage.
    Hope this helps,
    Gary Graham
    SQL Developer Team

  • SQL Developer 3.2 - Exporting data with TIMESTAMP datatype

    Hi,
    We have users that are attempting to export data with the Timestamp format to Excel (xls format) using SQL Developer 3.2.  When attempting to sort the Timestamp in either asc or desc order, Excel is having issues sorting correctly.  I suggested that the user just do all the sorting within their SQL Developer session but they require the ability to slice and dice in Excel.
    This is definitely not an issue with Excel as the users have previously exported Timestamp data from Toad and been able to sort without issue.  Any thoughts as to what might resolve this issue? 
    Thanks.

    We're not formatting timestamps in Oracle as numbers/dates in Excel. They'll need to properly format the Excel column/cells to get it to sort the way they want vs being treated as simple strings.

  • SQL Developer Hangs on Export

    SQL Developer version 1.0.0.14.67
    The application immediately freezes (so quickly, in fact, that it doesn’t even remove the context menu from which I have selected “Text” or “CSV”). I can still utilize the general windows controls (minimize/maximize, restore, etc). If I minimize and then restore the application it doesn’t redraw anything bit the title bar. The entire application window is system gray.
    The data set I retrieved included 2,208 records with 14 elements each.
    I tested it again with a slightly smaller data set (1,982 records) and this time I selected “Text” as the export format. Same result.
    The application still shows as “Running” in Task Manager, but the process “sqldeveloperW.exe” shows “00” under CPU activity and never moves. I am experiencing nominal Memory and CPU utilization (other programs are still open). Nothing is pegged @ 100%.
    I’ve let the application sit in this state for 10+ minutes with no change.

    There have been several updates since 1.0.0.14.67. Could you upgrade to the latest version?

  • Sql developer: question about exporting data

    Hi,
    we're recently working with sql-developer. i've got a question about how we can export query results to txt/csv files for use in other applications.
    First a problem: if we start a query that looks like this:
    select * from
    select * from A where start_date = &date
    ) a,
    select * from B where start_date = &date
    ) b
    where a.name = b.name
    Sql-developer asks twice to input a value for the variable 'date', although it's the same variable and it's supposed to have the same value.
    We solve this by making a script:
    first we define the variable, then we put the query.
    When we start the script, the query runs ok and sql developer asks to input the value for the variable once.
    But now the result of the query is shown in the script output. The script output seems to be limited in number of lines and difficult to export.
    So my question is: what's the best way to export query results to txt/csv files, avoiding the problem mentioned above?
    i hope there is a solution where we can use a single query or script.
    Thanks in advance!

    Using bind variables like ":date" should solve the problem of being asked twice for the same thing.
    Executing the query normally (F9), gives you the export options you require through the context menu inside the Results grid.
    Regards,
    K.

  • Sql Developer 3.1 - Exporting a result set in xls generates and empty file

    Ever since upgrading to the Production version SQL Developer 3.1 (3.1.07) it appears that there is an issue when attempting to export a result set as a .xls format.
    If I attempt to export in .xls format, the exported file is an empty file (i,e no output). When I change the export type to txt, csv or xlsx the results are exported as expected.
    This appears to be a bug introduced in the Production version as I was successfully able to perform these tasks on the various 3.1 EA releases.
    Am I alone in this, have I misconfigured something or is this a bug?

    I keep having problems exporting to XLSX - mostly in cases where the data is voluminous and the format would be preferable over plain XLS as it does not have the 65krows limit ;-{ The data is read to the data grid (sometimes fast, sometimes much slower and "in chunks"), then the "task progress" won't move anymore, and the export file remains empty; If I cancel the task, trying to export again results in a message stating that sqldeveloper still has the output file locked.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • SQL Developer 1.5 - Exporting Data

    Hi,
    I am using SQL Developer 1.5 and trying to run query and asving the data to to file but having following problems.
    1) How to save data as pipe or other delimitted data in text file?
    2) when i am saving as text file, its taking longer but when its done, it shows 0 kb.
    Appreciated your help!
    Thanks,
    poratips

    This issue has been fix in version 2.1 that is YET TO BE RELEASED. There are no known work arounds for this issue in 1.5.

  • BUG: SQL Developer 1.5.3 CSV export column order broken

    There's a bug in the 1.5.3 release of SQL Developer regarding data export. This bug re-orders the column order in the data export to be alphabetically sorted. This produces mangled CSV files if used on a table or a view.
    This is a critical bug to me since I need to produce lots of ad-hoc data CSV export files. I'm staying with SQL Developer 1.5.0.53 (53.38) for now as it doesn't have this problem.
    This is the same bug as present in Jdeveloper 11.1 as described in my post here: BUG: Jdev 11.1.1.0.0 -- DB table data export column order is not preserved
    Quoted from that post:
    When I connect to Oracle database, get the table list, right click on the table and select 'Export Data'->csv. The dialog box opens with three tabs: Format, Columns, Where. The column order displayed in both tabs Columns and Where is alphabetic. Because alphabetic ordering re-arranges columns from their initial ordering in the table, this screws up CSV export because columns are not in their intended order. This same problem occurs when I try to export data from views to generate a CSV file with a particular column order.
    Please open/check bug report if it's already open.
    Thanks!

    This happens with all of the export options for tables or views if you right click from the connections tab table list. If I pull it up in the main window and go to the data tab, I can then right click and it will keep the column id order for some of the views and tables. But not all.
    I am running 1.5.3 Build Main 5783 on a Windows XP Professional Service Pack 3 platform

  • How to see data modeller reports in sql developer?

    How to see data modeller reports in sql developer?

    1) export your design to existing schema in Oracle database
    2) define connection to that schema in SQL Developer
    3) find "Data Modeler Reports" in reports window of SQL Developer - probably "design rules" are more interesting here
    Philip

  • Just downloaded SQL Developer today, need help copy data

    How do I import data from Oracle XE to an Oracle server by using SQL Developer?

    Probably a better option would be use the export and import utilities provided with the database.
    From within SQL*Developer you can export data as either a csv file (and then use sql*loader to load it), or as insert statements which you can run in in either sql*developer or sql*plus.
    To export data in sql*developer, right-click on a table or a result set.
    Search for Export Table Data in the help system

  • SQL Developer export forgot to check to include semicolons in DDL

    Hi,
    I used the SQL Developers Export-function (select tables and right click on them, then select export) to backup tables.
    However, I forgot to set the 'Abschlusszeichen' (sorry for the german). That apparently means my create table statements are not finished by an ';', and they sinmply don't execute using the @script.sql method, or the sql developers import-function.
    One sql-file is 2 GB in size, so I currently have no idea how to edit it and add the semicolons manually. Is there any hope to rescue the data?
    I'm running sql developer 3.2.20.09, oracle Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production as well as Windows 8.1
    For clarification, this is how the create table part looks:
    --  Datei erstellt -Montag-September-30-2013  
    --  DDL for Table ZZ_BEN_0
      CREATE TABLE "PIERUSCHM"."ZZ_BEN_0"
       (    "BENUTZER_ID" NVARCHAR2(30),
        "NAME" NVARCHAR2(30),
        "GUELT_VON" NVARCHAR2(30),
        "GUELT_BIS" NVARCHAR2(30),
        "IST_KORREKTUR" NVARCHAR2(30),
        "IST_HALBTAGSKRAFT" NVARCHAR2(30),
        "LADE_DAT" DATE
    --  DDL for Table ZZ_BEN_1
      CREATE TABLE "PIERUSCHM"."ZZ_BEN_1"
       (    "BENUTZER_ID" NVARCHAR2(30),
        "NAME" NVARCHAR2(30),
        "GUELT_VON" NVARCHAR2(30),
        "GUELT_BIS" NVARCHAR2(30),
        "IST_KORREKTUR" NVARCHAR2(30),
        "IST_HALBTAGSKRAFT" NVARCHAR2(30),
        "LADE_DAT" DATE
    --  DDL for Table ZZ_BEN_10

    Also i'd like to add that the file begins with table definitions but then contains the actual (and randomly generated) data as well.
    You still need to have the file regenerated or you should expect to have problems with ANY method you use to try to automatically 'fix' the problem.
    1. No experienced developer that I have worked with would EVER try to execute such a monolithic script because there is virtually NO chance that a 2 GB script will EVER run successfully without an error of some sort. Objects have to be created in the proper order when dependencies exist between them. For example, you can't create an index if the table hasn't been created yet. There can even be circular references that will prevent all objects from being VALID even if they are created.
    2. There is virtually NO chance that ANY method you use will put terminators in EXACTLY the right place without causing a problem of some sort.
    3. When there is an error the script may continue to try to executed and that usually causes further errors. It also creates garbage objects that are not valid but will keep the script from working correctly the next time since the objects will already exist.
    You need to create a SET of scripts that are of manageable size so that you can control the process of executing them in the proper order.
    If you don't take the time to do that, up front, you are going to wasted a tremendous amount of time when the script fails trying to cut and paste the pieces you need out of that 'master' script.
    There are NO SHORTCUTS: take the time to do it right the first time.

  • SQL Developer - Database Export - Constraints not included in DDL

    I have used the Database Export function available in the Tools menu but have been unsuccessful in getting the referential integrety and check contraints to export. These are the steps I take:
    Environment: Windows XP Professional.
    SQL Developer 1.5.1
    Tools>Database Export
    In Source/Destination I select the filename and the database source and check:
    Show Schema
    Terminator
    Pretty Print
    Add Force to Views
    Include Grants
    In Types to Export I check all except Data.
    In Specify Objects I select the Schema I want to export.
    None of the foreign_key or check constraints are shown but I select all of the objects.
    Export Summary
    File:C:\Documents and Settings\richardk.asbury\My Documents\EER\eer3.sql
    Connection:ENVD
    DDL Options
         Show Schema
         Terminator
         Pretty Print
         Add Force to Views
         Necessary object dependencies will be included in export.
    Tables
         A_EMIS_TOXIC_DTL
         A_EMIS_TOXIC_HDR
         DSK_BLOB
         PORTAL_AI_PROFILE
         PORTAL_AI_XREF
         PORTAL_USER
         SUBJECT_ITEM_PARENT
         SUBJ_ITEM_ATTRIBUTE
         SUBJ_ITEM_COMMENTS
         SUBJ_ITEM_QUANTITIES
         SUBJ_ITEM_RELATED
    Views
         ACTIVITY_TASK_LIST_VW
         AGENCY_INTEREST_ORG_XREF_VW
         AGENCY_INTEREST_VW
         A_EMIS_TOXIC_DTL_VW
         A_EMIS_TOXIC_HDR_VW
         DSK_CENTRAL_VW
         MTB_ATTRIBUTE_DESC_VW
         MTB_ATTRIB_ATTR_DESC_XREF_VW
         MTB_MUNICIPALITY_VW
         MTB_PARAMETER_VW
         MTB_PERSON_TITLE_VW
         MTB_PORTAL_SUBMITTAL_STATUS_VW
         MTB_QUANTITY_TYPE_VW
         MTB_QUANT_METHOD_VW
         MTB_STATE_VW
         MTB_SUBJECT_ITEM_ATTRIBUTE_VW
         MTB_SUBJECT_ITEM_TYPE_VW
         MTB_UNITS_VW
         ORGANIZATION_VW
         PERSON_VW
         PORTAL_AI_PROFILE_VW
         PORTAL_AI_XREF_VW
         PORTAL_EMAIL_QUEUE_VW
         PORTAL_USER_VW
         SUBJECT_ITEM_VW
         SUBJ_ITEM_COMMENTS_VW
         SUBJ_ITEM_GENERAL_VW
         SUBJ_ITEM_LOC_LAT_LONG_VW
    Indexes
         INDX_DSK_BLOB_BLOB_TITLE
         PK_A_EMIS_TOXIC_DTL_ID
         PK_A_EMIS_TOXIC_HDR_ID
         PK_DSK_BLOB
         PK_PORTAL_USER_ID
         PK_SUBJECT_ITEM_PARENT
         PK_SUBJECT_ITEM_RELATED
         PK_SUBJ_ITEM_ATTRIB_ID
         PK_SUBJ_ITEM_COMMENTS_ID
         PK_SUBJ_ITEM_QUANT_ID
         SYS_C0017821
    Package Spec
         MNG_DATA
         MNG_USER
    Package Body
         MNG_DATA
         MNG_USER
    Procedures
    All procedures will be exported.
    Functions
    All functions will be exported.
    Triggers
         A_EMIS_TOXIC_DTL_BEFINSUPD
         A_EMIS_TOXIC_HDR_BEFINSUPD
         PORTAL_AI_PROFILE_BEFINS
         PORTAL_AI_XREF_BEFINS
         PORTAL_USER_BEFINS
         SUBJECT_ITEM_PARENT_BEFINSUPD
         SUBJ_ITEM_ATTRIBUTE_BEFINSUPD
         SUBJ_ITEM_COMMENTS_BEFINSUPD
         SUBJ_ITEM_QUANTITIES_BEFINSUPD
         SUBJ_ITEM_RELATED_BEFINSUPD
    Types
    All types will be exported.
    Sequences
         A_EMIS_TOXIC_DTL_SEQ
         A_EMIS_TOXIC_HDR_SEQ
         DSK_BLOB_SEQ
         PORTAL_AI_PROFILE_SEQ
         PORTAL_AI_XREF_SEQ
         PORTAL_USER_SEQ
         SUBJECT_ITEM_PARENT_SEQ
         SUBJ_ITEM_ATTRIBUTE_SEQ
         SUBJ_ITEM_COMMENTS_SEQ
         SUBJ_ITEM_QUANTITIES_SEQ
         SUBJ_ITEM_RELATED_SEQ
    Materialized Views
    All materialized views will be exported.
    Materialized View Logs
    All materialized view logs will be exported.
    Synonymns
    All synonyms will be exported.
    Queues
    All queues will be exported.
    Queue Tables
    All queue tables will be exported.
    Database Links
    All data base links will be exported.
    There are numerous Check and Foreign_key constraints missing in created DDL.
    Im I missing a step?
    rasberry

    Actually all tables were included and the Automatically Include Dependent Objects option was checked.
    For an example, the first table exported A_EMIS_TOXIC_DTL had the following constraints:
    FK_A_EMIS_TOXIC_DTL2HDR     Foreign_Key
    NN_A_EMIS_TOXIC_DTL_ID     Check
    PK_A_EMIS_TOXIC_DTL_ID     Primary_Key
    The primary key constraint was included in the DDL but none of the others.

  • Statement terminator problems when exporting data with SQL Developer 3.2

    I've ran across what appears to be a bug with SQL Developer 3.2.20.09. If someone can let me know if this is indeed a bug, or just something I need to configure differently, please let me know.
    The problem is related to exporting a database as a SQL script, and terminator characters at the end of "create" statements, especially when columns have comments, and problems that occur when using SQLPlus to run the export script to create the tables. With the old SQL Developer 1.5.4, with the "Terminator" and "Pretty Print" options checked, statements like the following are generated:
    -- DDL for Type NUM_ARRAY
    CREATE OR REPLACE TYPE "NUM_ARRAY"
    IS TABLE OF NUMBER(20)
    -- DDL for Sequence MYTABLE_SEQ
    CREATE SEQUENCE "MYTABLE_SEQ" MINVALUE 1 MAXVALUE 999999999999999999999999999 INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE ;
    -- DDL for Table MYTABLE
    CREATE TABLE "MYTABLE"
    (     "MYTABLE_ID" NUMBER,
         "COL2" NUMBER,
         "COL3" NUMBER
    -- DDL for Table ANOTHERTABLE
    CREATE TABLE "ANOTHERTABLE"
    (     "ANOTHERTABLE_ID" NUMBER,
         "COL2" VARCHAR2(1024),
         "COL3" VARCHAR2(1024)
    COMMENT ON COLUMN "ANOTHERTABLE"."ANOTHERTABLE_ID" IS 'This is a comment.';
    When I then run the script using SQLPlus, everything works fine. However, with SQL Developer 3.2.20.09, with the same options enabled, the same statements are generated like this:
    -- DDL for Type NUM_ARRAY
    CREATE OR REPLACE TYPE "NUM_ARRAY"
    IS TABLE OF NUMBER(20)
    -- DDL for Sequence MYTABLE_SEQ
    CREATE SEQUENCE "MYTABLE_SEQ" MINVALUE 1 MAXVALUE 999999999999999999999999999 INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE ;
    -- DDL for Table MYTABLE
    CREATE TABLE "MYTABLE"
    (     "MYTABLE_ID" NUMBER,
         "COL2" NUMBER,
         "COL3" NUMBER
    -- DDL for Table ANOTHERTABLE
    CREATE TABLE "ANOTHERTABLE"
    (     "ANOTHERTABLE_ID" NUMBER,
         "COL2" VARCHAR2(1024),
         "COL3" VARCHAR2(1024)
    COMMENT ON COLUMN "ANOTHERTABLE"."ANOTHERTABLE_ID" IS 'This is a comment.';
    Notice all of the extra slashes in there. If a slash is not used as a statement terminator, SQLPlus treats slashes as a command to repeat the last SQL statement, which causes many errors about tables or sequences already existing. So, I tried removing the "Terminator" flag from the export options. This lead to statements that looked a bit more promising:
    -- DDL for Type NUM_ARRAY
    CREATE OR REPLACE TYPE "NUM_ARRAY"
    IS TABLE OF NUMBER(20)
    -- DDL for Sequence MYTABLE_SEQ
    CREATE SEQUENCE "MYTABLE_SEQ" MINVALUE 1 MAXVALUE 999999999999999999999999999 INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE
    -- DDL for Table MYTABLE
    CREATE TABLE "MYTABLE"
    (     "MYTABLE_ID" NUMBER,
         "COL2" NUMBER,
         "COL3" NUMBER
    -- DDL for Table ANOTHERTABLE
    CREATE TABLE "ANOTHERTABLE"
    (     "ANOTHERTABLE_ID" NUMBER,
         "COL2" VARCHAR2(1024),
         "COL3" VARCHAR2(1024)
    COMMENT ON COLUMN "ANOTHERTABLE"."ANOTHERTABLE_ID" IS 'This is a comment.'
    The big problem, though, is in the statement for the table with a comment. Notice that there are two statements, but there is not a semicolon after either of them. This unfortunately causes the "COMMENT" statement to be appended to the "CREATE TABLE" statement before being executed, which causes the table to not be created (which causes even more errors later on when the script attempts to populate the table with data).
    So, it would appear that this is a bug, but I'm not sure. Is there a way I can configure the export options to make SQL Developer export these statements like it used to in older versions?
    Thanks,
    -Bill

    >
    So, it would appear that this is a bug, but I'm not sure.
    >
    That would be a bug. Thanks for reporting it and providing the detailed example.
    >
    Is there a way I can configure the export options to make SQL Developer export these statements like it used to in older versions?
    >
    No.
    Leave the thread open. One of the developers for sql developer should be monitoring the forum and can provide more information.

  • Import / Export MySQL database in SQL Developer

    Hello,
    I have version 3.1.2.704 of SQL Developer Data Modeler and version 3.2.09 of SQL Developer installed.
    When I´m adding a new connection in SQL Developer, I can choose the MySQL tab an create a connection to a MySQL database.
    The connection test was successful and I can see all tables.
    I use the same JDBC driver for SQL Developer and SQL Developer Data Modeler (mysql-connector-java-5.0.4-bin.jar).
    But there are two problems.
    1. First there is an problem when I want to import from a MySQL database (SQL Developer -> File -> DataModeler -> Import -> DataDictionary).
    After choosing the MySQL connection and pressing the next button an error occurs: CONNECTION_TYPE
    What is the reason?
    2. In SQL Developer Data Modeler I have not the CONNECTION_TYPE problem. But when I want to export DDL, there is no MySQL type selectable, although there is working connection to the MySQL Database. It´s the same in SQL Developer.
    What is the reason?

    Hi,
    Please be aware that a separate forum for SQL Developer Data Modeler is available:
    SQL Developer Data Modeler
    You will likely get a more rapid response if you mark this thread as answered and re-post your question over there.
    Regards,
    Gary

Maybe you are looking for

  • Need some help in collection initiallization

    Hi i am facing some problem with collection intiallization.we have 10g db.it is throwing 'ORA-06531: Reference to uninitialized collection' error.i tried out the same procedure with emp table.it is not throwing any error.i am pasting both codes here.

  • Upgrading Mac Pro 3,1 for CS5

    We have 2 2008 Mac Pro 3,1 need to update to use Adobe CS5, and I think we may need some hardware/software upgrade to boost the performance and would like to have some suggestion. Here is the list of hardware:   Model Name:          Mac Pro   Model I

  • How do I update my iOS 4.2.8 software to 4.3?

    How do I update my iOS 4.2.8 software to 4.3?

  • Cross-references in Pages?

    This is one of those "In Word I could do ____, how do I do it in Pages?" questions. Word has a cross-reference feature where, for example, you could insert a statement such as: "See footnote __, above." The blank line would actually be text field tha

  • Placing properties file

    wls 6.1sp4 WebApp in WAR format contains a servlet which loads on startup. This servlets has to load some properties file. Currently if i have this properties file in system classpath. Servlet is able to find. I dont want to place my properties file