GENERATING DOC - sql developer 1.5

hi guys,
i am encountering this problem..
i am only able to get TABLES and VIEWS when generating DB document..
I cant seems to get procedures/functions and stuff like that.
what could be wrong ? is there a log file for me to do some tracing ? where else can i ask except here?
Pls advice
Regards,
Noob

Please do not duplicate threads. You've asked the same thing in sql developer 1.5 - generate db doc
K.

Similar Messages

  • SYS_REFCURSOR in SQL Developer

    Hello! I'm trying to execute function which returns sys_refcursor. Code is generated by Sql Developer Run command
    DECLARE
    P_DATE_FROM DATE;
    P_DATE_TO DATE;
    P_OUT_ERROR_CODE VARCHAR2(200);
    v_Return SYS_REFCURSOR;
    BEGIN
    P_DATE_FROM := SYSDATE - 10;
    P_DATE_TO := SYSDATE;
    v_Return := MONITORING.GET_MONITORING_DATA(
    P_DATE_FROM => P_DATE_FROM,
    P_DATE_TO => P_DATE_TO,
    P_OUT_ERROR_CODE => P_OUT_ERROR_CODE
    :P_OUT_ERROR_CODE := P_OUT_ERROR_CODE;
    :v_Return := v_Return; --<-- Cursor
    END;
    Function body:
    FUNCTION get_monitoring_data
    ( p_date_from IN DATE
    , p_date_to IN DATE
    , p_out_error_code OUT VARCHAR2
    RETURN SYS_REFCURSOR
    IS
    v_cursor SYS_REFCURSOR;
    BEGIN
    OPEN v_cursor FOR
    SELECT * FROM person_case;
    RETURN v_cursor;
    END get_monitoring_data;
    Unfortunately I'm receiving error every time:
    ORA-06550: line 18, column 20:
    PLS-00382: expression is of wrong type
    Line 18 is: :v_Return := v_Return;
    Everything works fine in VS Developer Tools and PL/SQL Developer
    What I'm doing wrong? Thanks in advance!

    I don't use SQL Developer, though I'm sure it must have a way of handling ref cursors.
    In SQL*Plus you would do something like...
    SQL> ed
    Wrote file afiedt.buf
      1  CREATE OR REPLACE
      2  FUNCTION get_monitoring_data(p_date_from IN DATE
      3                              ,p_date_to IN DATE
      4                              ,p_out_error_code OUT VARCHAR2
      5                              ) RETURN SYS_REFCURSOR IS
      6    v_cursor SYS_REFCURSOR;
      7  BEGIN
      8    OPEN v_cursor FOR
      9      SELECT * FROM emp;
    10    RETURN v_cursor;
    11* END get_monitoring_data;
    SQL> /
    Function created.
    SQL> var p_out_error_code varchar2;
    SQL> var v_return refcursor;
    SQL> ed
    Wrote file afiedt.buf
      1  DECLARE
      2    P_DATE_FROM DATE;
      3    P_DATE_TO DATE;
      4    P_OUT_ERROR_CODE VARCHAR2(200);
      5    v_Return SYS_REFCURSOR;
      6  BEGIN
      7    P_DATE_FROM := SYSDATE - 10;
      8    P_DATE_TO := SYSDATE;
      9    v_Return := GET_MONITORING_DATA(
    10                  P_DATE_FROM => P_DATE_FROM,
    11                  P_DATE_TO => P_DATE_TO,
    12                  P_OUT_ERROR_CODE => P_OUT_ERROR_CODE
    13                 );
    14    :P_OUT_ERROR_CODE := P_OUT_ERROR_CODE;
    15    :v_Return := v_Return;
    16* END;
    SQL> /
    PL/SQL procedure successfully completed.
    SQL> print v_return;
         EMPNO ENAME      JOB              MGR HIREDATE                    SAL       COMM     DEPTNO
          7369 SMITH      CLERK           7902 17-DEC-1980 00:00:00        800                    20
          7499 ALLEN      SALESMAN        7698 20-FEB-1981 00:00:00       1600        300         30
          7521 WARD       SALESMAN        7698 22-FEB-1981 00:00:00       1250        500         30
          7566 JONES      MANAGER         7839 02-APR-1981 00:00:00       2975                    20
          7654 MARTIN     SALESMAN        7698 28-SEP-1981 00:00:00       1250       1400         30
          7698 BLAKE      MANAGER         7839 01-MAY-1981 00:00:00       2850                    30
          7782 CLARK      MANAGER         7839 09-JUN-1981 00:00:00       2450                    10
          7788 SCOTT      ANALYST         7566 19-APR-1987 00:00:00       3000                    20
          7839 KING       PRESIDENT            17-NOV-1981 00:00:00       5000                    10
          7844 TURNER     SALESMAN        7698 08-SEP-1981 00:00:00       1500          0         30
          7876 ADAMS      CLERK           7788 23-MAY-1987 00:00:00       1100                    20
          7900 JAMES      CLERK           7698 03-DEC-1981 00:00:00        950                    30
          7902 FORD       ANALYST         7566 03-DEC-1981 00:00:00       3000                    20
          7934 MILLER     CLERK           7782 23-JAN-1982 00:00:00       1300                    10
    14 rows selected.
    SQL>So that SQL*Plus has the variables that the returned values are going to be bound to (the ones signified by the ":")
    SQL Developer should have something similar I would guess to allow the returned values to be bound out so that it can then fetch and display the contents of the ref cursor itself.

  • Generating hourly report from oracle database using sql developer .Help

    I am working on SQL Developer 1.5.1, i need to prepare hourly record of the activity on the database, for that i have a sql query that gives me the report as per selected columns on hourly basis.I need to prepare 24 reports a day.
    Each time i have to go to the query , change the date as per hours like form 22:06:2011 10:00:00 to 22:06:2011 11:00:00 and get the report and export it in excel.
    I want to automate the script so that whenever i run the script , it just asks me the date and runs the script 24 times and fetch me the hourly report of whole day.
    the query syntax is something like this
    Select
    from
    where
    And.......................
    And...................
    And......................
    And req date between to-date( 22:06:2011 10:00:00) And to-date(22:06:2011 11:00:00)
    Order by 7,1,2,3,4,5
    Is there any possibility that i can automate the script to automatically change the hour itself and generate a report in excel 24 times?please share if you have any idea on this.
    Looking forward for a response.

    This gives you data for the whole day and the first column tells you which hour data it is,
    SELECT 'HOUR' || TO_CHAR ( req_date, 'HH24') AS hour_num,
           col1,
           col2,
           col3
      FROM table_name
    WHERE TRUNC (req_date) = TO_DATE ( '22/06/2011', 'DD/MM/YYYY')G.

  • SQL*Developer 2.1 - Not Generating DDL for Different Users

    Using SQL*Developer Version 2.1.0.63 I get an error trying to generate DDL from another user, that has access to many other schemas. It looks to me like Sql Developer is calling the DBMS_METADATA package from within other PL/SQL.
    I am receiving the following error:
    ORA-31603: object "ACCOUNT_TYPE_LKP" of type TABLE not found in schema "POR_OWN"
    ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
    ORA-06512: at "SYS.DBMS_METADATA", line 3241
    ORA-06512: at "SYS.DBMS_METADATA", line 4812
    ORA-06512: at line 1
    I would receive these same errors in SQL Developer 1.5, but the DDL would still generated. It was picking something up, even though it had an error.
    Our DBA has not been able to provided a work around. He says you have to login directly as the owner of the objects to use dbms_metdata in this fashion.
    Is there any work around for this? I really need to be able to get DDL and I do not want to go back to 1.5 (I like the other new features of 2.1).
    Thanks,
    Tom

    We have several users currently using SQL Navigator and/or TOAD. We would like them to switch to SQL developer, but part of their job is to view the source of views in another schema. They have select privileges on the underlying tables and are able to see the source using other tools. Using SQL Developer, they receive on ORA-31603 because it's calling dbms_meta. Note ID 1185443.1 describes the issue and suggests granting the users the SELECT_CATALOG_ROLE.
    We are hesitant about granting this role to these users which allows access to ever 1,700 objects, plus execute privileges to 4 objects.
    Support indicated that Enhancement Request 8498115 addresses this issue.
    Is this something that may be addressed in the next release?
    Thanks,
    Paul

  • BUG in Oracle SQL Developer 3.0.04 on the "generating DLL" with comments?

    I'm newbie on oracle, but I think that I found out a bug in Oracle SQL Developer version 3.0.04 on the "generating DLL" tool using "comments".
    I will describe the steps that I gave:
    I created a view, but after I test it I had to change my “where” condition, so I comment the old code and then I wrote the new “where” condition below. After I done that I tried to look at the sql code of my view using “generating DLL” tool, but oracle sql developer only shown me half of the code, a lot of code were missing. Then I began with some test trying to understand what happen and I notice that if I put an invalid sql code in my comment the generating DLL start working with no problems, for example(pseudo-code):
    (COMMENT WITH VALID SQL CODE the "Generating SQL" don't work:)
    CREATE OR REPLACE VIEW <user>.<view_name> ( <column1>,<column2> )
    AS
    SELECT column1, column2
    FROM table1
    INNER JOIN
    (SELECT
    FROM table2
    INNER JOIN .....
    INNER JOIN ....
    --where time_stamp = (select max(time_stamp) from .....)
    WHERE time_stamp >= TRUNC(sysdate)
    ) t1 ON t1.ID = ....
    AND ..... >= TRUNC(sysdate)
    ORDER BY ....
    Generating DLL returns this(when the error occurs):
    CREATE OR REPLACE VIEW <user>.<view_name> ( <column1>,<column2> )
    AS
    (COMMENT WITH VALID SQL CODE the "Generating SQL" work with no problems:)
    CREATE OR REPLACE VIEW <user>.<view_name> ( <column1>,<column2> )
    AS
    SELECT column1, column2
    FROM table1
    INNER JOIN
    (SELECT
    FROM table2
    INNER JOIN .....
    INNER JOIN ....
    --where
    WHERE time_stamp >= TRUNC(sysdate)
    ) t1 ON t1.ID = ....
    AND ..... >= TRUNC(sysdate)
    ORDER BY ....
    I believe that "Generating DLL" tool have some problem with the comments, I also used /*...*/ to comment but the problem is still active.
    I notice as well that if I started to add some more comments along the code, the conditions migth change, so I think the problem is related with "comments" code.
    Would you mind telling me if this is a real bug or if I'm doing anything wrong.
    Thank you in advance,
    Rodrigo Campos
    Edited by: 894886 on 3/Nov/2011 5:29

    Hi Rodrigo,
    Thank you for reporting this. The only bug I see currently logged on a comment affecting the generated View DDL involves ending the last line of the definition with a comment, which treats the ending semi-colon (even if on a different line) as part of the comment. That is actually related to a low-priority bug against an Oracle database API.
    Unfortunately, your pseudo-code is a bit complex. Trying a few quick, simpler tests against the standard HR schema did not reproduce the issue. I tried INNER JOIN, and nested SELECTs. It would help greatly if you could provide a test case compilable against one of the standard schema, like HR or SCOTT.
    Regards,
    Gary
    SQL Developer Team

  • SQL Developer 1.5.1 - warning messages generated by CREATE TABLE

    Hi,
    Have an issue with a CREATE TABLE statement - it works correctly, but generates a warning message when used in SQL Developer (1.2 or 1.5.1). Full test case below:
    Setup:
    drop table samplenames;
    drop table customers;
    drop table phones;
    drop table customers_phone;
    drop sequence primkey;
    create table samplenames
    (name VARCHAR2(10));
    insert into samplenames values ('dan');
    insert into samplenames values ('joe');
    insert into samplenames values ('bob');
    insert into samplenames values ('sam');
    insert into samplenames values ('weslington');
    insert into samplenames values ('sue');
    insert into samplenames values ('ann');
    insert into samplenames values ('mary');
    insert into samplenames values ('pam');
    insert into samplenames values ('lucy');
    create sequence primkey
    start with 1000000
    increment by 1;
    create table customers as
    select primkey.nextval as cust_id,
    tmp1.name || tmp2.name as first_name,
    tmp3.name || tmp4.name || tmp5.name as last_name
    from samplenames tmp1,
    samplenames tmp2,
    samplenames tmp3,
    samplenames tmp4,
    samplenames tmp5;
    CREATE TABLE PHONES AS
    SELECT cust_id, 'H' as phn_loc, trunc(dbms_random.value(100,999)) as area_cde,
    trunc(dbms_random.value(1000000,9999999)) as phn_num
    FROM customers;
    INSERT INTO PHONES
    SELECT cust_id, 'B' as phn_loc, trunc(dbms_random.value(100,999)) as area_cde,
    trunc(dbms_random.value(1000000,9999999)) as phn_num
    FROM customers;
    --randomly delete ~10% of records to make sure nulls are handled correctly.
    delete from phones
    where MOD(area_cde + phn_num, 10) = 0;
    create table statement (there are legacy reasons for why this is written the way it is):
    CREATE TABLE customers_phone NOLOGGING AS
    SELECT cst.*,
    piv.HOME_PHONE,
    piv.WORK_PHONE
    FROM (SELECT cust_id,
    MAX(decode(phn_loc, 'H', '(' || area_cde || ') ' ||
    substr(phn_num,1,3) || '-' || substr(phn_num,4,4), NULL)) AS HOME_PHONE,
    MAX(decode(phn_loc, 'B', '(' || area_cde || ') ' ||
    substr(phn_num,1,3) || '-' || substr(phn_num,4,4), NULL)) AS WORK_PHONE
    FROM phones phn
    WHERE phn_loc IN ('H', 'B')
    AND cust_id IS NOT NULL
    AND EXISTS (SELECT NULL
    FROM customers
    WHERE cust_id = phn.cust_id)
    GROUP BY cust_id) piv,
    customers cst
    WHERE cst.cust_id = piv.cust_id (+)
    Warning message output:
    "Error starting at line 1 in command:
    CREATE TABLE customers_phone NOLOGGING AS
    SELECT cst.*,
    piv.HOME_PHONE,
    piv.WORK_PHONE
    FROM (SELECT cust_id,
    MAX(decode(phn_loc, 'H', '(' || area_cde || ') ' || substr(phn_num,1,3) || '-' || substr(phn_num,4,4), NULL)) AS HOME_PHONE,
    MAX(decode(phn_loc, 'B', '(' || area_cde || ') ' || substr(phn_num,1,3) || '-' || substr(phn_num,4,4), NULL)) AS WORK_PHONE
    FROM phones phn
    WHERE phn_loc IN ('H', 'B')
    AND cust_id IS NOT NULL
    AND EXISTS (SELECT NULL
    FROM customers
    WHERE cust_id = phn.cust_id)
    GROUP BY cust_id) piv,
    customers cst
    WHERE cst.cust_id = piv.cust_id (+)
    Error report:
    SQL Command: CREATE TABLE
    Failed: Warning: execution completed with warning"
    I am on 10.2.0.3. The CREATE TABLE always completes successfully, but the warning bugs me, and I have had no success tracking it down since there is no associated numberr.
    Anyone have any ideas?

    Hi ,
    The Oracle JDBC driver is returning this warning so I will be logging an issue with them, but for the moment SQL Developer will continue to report the warning as is.
    The reason for the warning is not clear or documented as far as I can tell,
    but I have replicated the issue with a simpler testcase which makes it easier to have a guess about the issue :)
    ----START
    DROP TABLE sourcetable ;
    CREATE TABLE sourcetable(col1 char);
    INSERT INTO sourcetable VALUES('M');
    DROP TABLE customers_phone;
    CREATE TABLE customers_phone AS
    SELECT MAX(decode(col1, 'm','OK' , NULL)) COLALIAS
    FROM sourcetable;
    ----END
    The warning occurs in the above script in SQL Developer , but not in SQL*Plus.
    The warning disappears when we change 'm' to 'M'.
    The warning disappears when we change NULL to 'OK2'
    In all cases the table creates successfully and the appropriate values inserted.
    My gut feeling is ...
    During the definition of customers_phone, Oracle has to work out what the COLALIAS datatype is.
    When it sees NULL as the only alternative (as sourcetable.col1 = 'M' not 'm') it throws up a warning. It then has to rely on the 'OK' value to define the COLALIAS datatype, even though the 'OK' value wont be inserted as sourcetable.col1 = 'M' and not 'm'. So Oracle makes the correct decision to define the COLALIAS as VARCHAR2(2), but the warning is just to say it had to use the alternative value to define the column.
    Why SQL*Plus does not report it and JDBC does, I'm not sure. Either way it doesn't look like a real issue.
    Again, this is just a guess and not a fact.
    Just though an update was in order.
    Regards,
    Dermot.

  • SQL Developer 3.0.04 generated scripts not compatible with Oracle 10g (XE)

    HI,
    I tried to do an export from one XE database (still 10g) to another XE database. (also 10g).
    I tried to do a database copy as well as a separate export and import (by loading the file and running as a script).
    Neither of them work without modifying the files as it seems that SQL Developer generates scripts that are only compatible with Oracle 11g.
    - Create table contains "segment creation automatic"
    - Storage clauses contain parts that are not compatible with 10g
    I ran through the wizard several times but neither can I find an option to choose for compatibility with earlier versions of Oracle.
    Checked the preferences screen as well.
    Is this a well hidden option or is it not possible to make this work for 10g.
    Extra : found workaround by removing the storage clause to the export. Is there another way that does not force me to remove the storage clause?
    Edited by: kcaluwae on 24-jun-2011 6:03

    I'm sure this is far from the supported way to fix this but, seeing that it's apparently an issue with the classpath or something in it, I hacked <sqldeveloper_install>\sqldeveloper\bin\sqldeveloper.bat and added [ORACLE_HOME]\jdbc\lib\ojdbc6.jar to the classpath. At least that gets me started with 3.0 and lets me create TNS connections.
    I'd really appreciate a better solution, if any of you kind folks knows of something.
    Thanks,
    Kelly

  • Generating Entity - RelationShip in Oracle SQL Developer.

    Is it possible to generate an Entity - RelationShip diagram from Oracle SQL Developer?
    Thanks in advance,
    Jaime.

    If you're willing to pay the 3000 quid per seat (+ annual support costs), take a look at [Oracle SQL Developer Data Modeler|http://www.oracle.com/technology/products/database/datamodeler/index.html].
    Have fun,
    K.

  • Generate DDL works in old version of SQL Developer, but not in new versions

    Hello all,
    How to generate DDL in new versions of Oracle SQL Developer for production Oracle database?
    For production database, the generate DDL feature works fine in old versions (version 1.5.5) of Oracle SQL Developer, SQuirrel, Toad and many other similar tools, but not the new versions of Oracle SQL Developer (such as 2.1.1.64.45).
    The SQL tab for a table is blank for me in production databases. Of course, it works fine in development Oracle database.
    I did some research that many articles describe SELECT_CATALOG_ROLE as the required read-only role in production database. Our DBA did a test to grant me this role temporarily, and it worked for me to generate DDL using new Oracle SQL Developer. It is pain for me to ask for this role.
    Is there a plug-in or work-around, so the new versions of Oracle SQL Developer can have this generate DDL feature in production without the mentioned SELECT_CATALOG_ROLE?
    I could not find the answer in older forum threads.
    For now, I will have to install older versions of Oracle SQL Developer.
    Thanks

    I've seen a couple posts about people not being able to generate DDL for other users. To date, I've never seen a anybody post a workaround, nor have I seen one of the developers post a response, nor have I seen anybody say they've submitted a SR.
    I think I remember reading somewhere that the new version of SQL Developer uses dbms_metadata.get_ddl to generate DDLS, rather than some custom query built on top of catalog views...which could explain why it use to work, but no longer does. But whether or not this is true, I don't know.
    You could try submitting a SR and see if Oracle responds saying that it's a known bug and will be fixed in the next release. Until then, unless you get the role, you're stuck using something else for DDL generation.

  • SQL Developer 4.0 - Database Diff - turn off schema name in generated script

    SQL Developer 4 / RDBMS 11GR2
    I know SQL Developer 4 is EA, but maybe the question has the same answer in 3.3.  Also if 4.0 EA questions need to be asked in a different forum, please advise.
    I am new to SQL Developer and I admit to using brand Z (TOAD) for many, many years.
    (1) When using Database Diff, is there a setting to turn off the schema name that is displayed in the scripts that are generated?  I looked in PREFERENCES, but if it is there, I did not see it.
    (2) While I have found good resources on SQL Developer, is there a FAQ on Database DIff that answers a lot of these silly type questions?
    Thanks in advance

    On the first screen of the DIFF wizard there's a check box for 'Schema' - uncheck that.

  • SQL Developer generates strange trace files on server

    Hello out there,
    I observed the generation of some strange trace files on the database server (Oracle 11.0.2.0.2 64bit on Win 2008R2).
    Whenever I start SQL Developer (3.2.20.09.87 64bit with JDK 1.7.0_17 64bit on Win7 64bit) for each connection I defined one trace file like this is generated:
    Trace file C:\ORACLE\diag\rdbms\ora\ora\trace\ora_ora_8500.trc
    Oracle Database 11g Release 11.2.0.2.0 - 64bit Production
    Windows NT Version V6.1 Service Pack 1
    CPU                 : 2 - type 8664, 2 Physical Cores
    Process Affinity    : 0x0x0000000000000000
    Memory (Avail/Total): Ph:990M/3959M, Ph+PgF:3743M/7918M
    Instance name: ora
    Redo thread mounted by this instance: 1
    Oracle process number: 23
    Windows thread id: 8500, image: ORACLE.EXE (SHAD)
    *** 2013-03-06 08:04:13.842
    *** CLIENT ID:() 2013-03-06 08:04:13.842
    *** SERVICE NAME:() 2013-03-06 08:04:13.842
    *** MODULE NAME:() 2013-03-06 08:04:13.842
    *** ACTION NAME:() 2013-03-06 08:04:13.842
    Breaking the connection before proto/dty negotiation, error raised 3113I enabled listener log to find out the origin of this and it contains lines like the following:
    06-MRZ-2013 08:04:13 * (CONNECT_DATA=(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))(SERVICE_NAME=ora.vu)(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.36.143)(PORT=49320)) * establish * ora.vu * 0
    06-MRZ-2013 08:04:13 * (CONNECT_DATA=(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))(SERVICE_NAME=ora.vu)(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.36.143)(PORT=49322)) * establish * ora.vu * 0
    06-MRZ-2013 08:04:13 * (CONNECT_DATA=(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))(SERVICE_NAME=ora.vu)(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.36.143)(PORT=49323)) * establish * ora.vu * 0
    06-MRZ-2013 08:04:13 * (CONNECT_DATA=(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))(SERVICE_NAME=ora.vu)(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.36.143)(PORT=49325)) * establish * ora.vu * 0
    06-MRZ-2013 08:04:14 * (CONNECT_DATA=(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))(SERVICE_NAME=ora.vu)(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.36.143)(PORT=49329)) * establish * ora.vu * 0
    06-MRZ-2013 08:04:14 * (CONNECT_DATA=(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))(SERVICE_NAME=ora.vu)(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.36.143)(PORT=49331)) * establish * ora.vu * 0The IP address is mine and I have excatly 6 connections defined for that server. On other servers, similar trace files are generated, one for each connection in my SQL Developer.
    This also occurred with JDK 1.6 so I don't think it's a Java issue.
    Besides the generation of the trace files there seem to be no other problems.
    Any ideas?

    Hi,
    I think Srini is probably correct. The noted bug applies to 11.2.0.1 and up, is fixed in 12c, and included in an 11.2.0.3 patch. However the version of SQL Developer also affects the creation of trace files on product startup (prior to any user initiated db connect attempts).
    For example,
    A. SQL Developer 3.1.07.42 - no such trace files created.
    B. SQL Developer 3.2.20.09.87 - such trace files created for 11.2.0.1 connections, but not 10g XE or 12c connections.
    So I presume an OCIServerAttach call got added in 3.2.2, not sure in support of which feature, but the bug will only impact users of 11.2.0.1, 11.2.0.2, and unpatched 11.2.0.3 DB releases.
    Regards,
    Gary
    SQL Developer Team

  • SQL Developer Migation Tool - formating generated SQL

    I am using SQL Developer version 2.1.1.64 to migrate MS SQL server to ORACLE via the Migration tool.
    My question is : Is there a way to format the generated ORACLE code?
    The reason I ask, our developmet team has coding standards for creating procedures. For example, use TABs for identation, not spaces.
    I changed the profiles under the SQL formatted (Tools>Preferences>Database>SQL Formatter>ORACLE Formatting) but it does not seam to affect the generation output.
    The code is always generated using spaces.

    Ctrl-shift-f7 invokes the formatter. This can be defaulted to your standards by choosing them from the preferences.
    B

  • REPORT generating dilema SQL plus, SQL worksheet, SQL developer, when to yo

    hi i am always generating report for my company into excel sheet..
    and i encoutner a scenario where by i need to do a
    BREAK ON col skip 1 command.
    now i am wondering..
    1) i am using sql developer to export the report into excel sheet everytime. and ihave tried using the break on col skip 1 command, it will not work on sql developer.
    if i run it in a script [F5] i cannot export the data in excel..
    2) if i use sql*plus to do the report, i wont not be able to see all the columns in 1 straight row..
    even though i have set the linesize to the maximum..my tables has too many columns..
    2nd , can sql*plus generate excel file?
    3) what is the difference between sqlworksheet and sqlplus, does oracle10g still support sqlworksheet? i cant seem to find it in oracle10g
    4) somehow i feel certain mechanism inside sqldeveloper sqlworksheet are the same of sqlplus,
    anybody has a clue?
    thats all 10s

    SQL Worksheet is no longer supported.
    The SQL Developer team are trying to make the worksheet in SQLDeveloper compatible with sqlplus, but they have some way to go.
    SQL*Plus can't generate excel files directly, but you can use 'set colsep ,' to get a comma separated file of sorts.
    The maximum linesize in sqlplus is 32767. Are you sure you need all that information in one line?
    You may need to look at better report writers such as Apex or Oracle reports, or use MSQuery to pull the data directly into Excel.

  • SQL Developer generating an XML Schema for a table

    I hope I've put this question in to correct area of the forum!
    My question is how do you generate an XML schema of a table layout in SQL Developer?
    You can generate an XML schema for the DATA, but I just want to generate one with all the column definitions etc.
    The annoying thing is I managed to do this the other day, but after attempting again for several hours I've forgotten how to do it :-(
    Thanks and regards, Adrian

    A more specific answer, using SqlDeveloper itself, can be found at
    Re: Generating an XML schema for a TABLE

  • Unable to generate insert stmt scripts using sql developer

    We are not able to generate INSERT statement script using SQL Developer. In the INSERT script system is inserting some spaces due to carriage return which we cannot reviewed individually.

    DELETE FROM IM_INSTANCE_EXT_VAL_FRM
    WHERE IEVF_TRG_FLD_NAME = 'PRAI_NUM_03'
    AND IEVF_INST_CODE = 'APV-QQ-03'
    AND IEVF_BLK_NAME = 'PGIT_POL_RISK_ADDL_INFO_01';
    -- INSERTING into IM_INSTANCE_EXT_VAL_FRM
    Insert into IM_INSTANCE_EXT_VAL_FRM (IEVF_SYS_ID,IEVF_INST_CODE,IEVF_PROG_CODE,IEVF_BLK_NAME,IEVF_TRG_FLD_NAME,IEVF_ACT_FLDS,IEVF_ACTION,IEVF_PROC,IEVF_SRNO,IEVF_ERR_NO,IEVF_ERR_YN,IEVF_APP_CODE,IEVF_REMARKS,IEVF_UPD_UID,IEVF_UPD_DT,IEVF_CR_UID,IEVF_CR_DT,IEVF_TRG_NAME,IEVF_CLEAR_FLD_YN,IEVF_VALIDATE_YN) values (IEVF_SYS_ID.NEXTVAL,'APV-QQ-03','PGIT6_03','PGIT_POL_RISK_ADDL_INFO_01','PRAI_NUM_03','PRAI_DATA_15,','ENABLED','VFB_EV_GEN.EXT_VAL_DISABLE_PHY_DAMAGE(:PGIT_POL_RISK_ADDL_INFO_01.PRAI_POL_SYS_ID,
    :PGIT_POL_RISK_ADDL_INFO_01.PRAI_END_NO_IDX,
    :PGIT_POL_RISK_ADDL_INFO_01.PRAI_END_SR_NO,
    :PGIT_POL_RISK_ADDL_INFO_01.PRAI_LVL1_SYS_ID,
    :PGIT_POL_RISK_ADDL_INFO_01.PRAI_CODE_02,
    :PGIT_POL_RISK_ADDL_INFO_01.PRAI_NUM_03,:P_FLAG_OUT)',1,null,'N','01','VALIADTION',null,null,'PREMIA',
    to_date('19-SEP-07','DD-MON-RR'),'WHEN-VALIDATE-ITEM','0','1');
    Insert into IM_INSTANCE_EXT_VAL_FRM (IEVF_SYS_ID,IEVF_INST_CODE,IEVF_PROG_CODE,IEVF_BLK_NAME,IEVF_TRG_FLD_NAME,IEVF_ACT_FLDS,IEVF_ACTION,IEVF_PROC,IEVF_SRNO,IEVF_ERR_NO,IEVF_ERR_YN,IEVF_APP_CODE,IEVF_REMARKS,IEVF_UPD_UID,IEVF_UPD_DT,IEVF_CR_UID,IEVF_CR_DT,IEVF_TRG_NAME,IEVF_CLEAR_FLD_YN,IEVF_VALIDATE_YN) values (IEVF_SYS_ID.NEXTVAL,'APV-QQ-03','PGIT6_03','PGIT_POL_RISK_ADDL_INFO_01','PRAI_NUM_03',null,'VALIDATE','VFB_EV_GEN.EXT_VAL_VEHICLE_AGE(:PGIT_POL_RISK_ADDL_INFO_01.PRAI_POL_SYS_ID,     :PGIT_POL_RISK_ADDL_INFO_01.PRAI_PSEC_SYS_ID,
    ''APV'',
    ''APV'',
    :PGIT_POL_RISK_ADDL_INFO_01.PRAI_NUM_03,
    :PGIT_POL_RISK_ADDL_INFO_01.PRAI_NUM_07,
    :PGIT_POL_RISK_ADDL_INFO_01.PRAI_NUM_08,
    :P_FLAG_OUT,
    :PGIT_POL_RISK_ADDL_INFO_01.PRAI_NUM_35_OUT) ',3,null,'N','01','VALIADTION',null,null,'PREMIA',to_date('19-SEP-07','DD-MON-RR'),'WHEN-VALIDATE-ITEM','1','1');
    Insert into IM_INSTANCE_EXT_VAL_FRM (IEVF_SYS_ID,IEVF_INST_CODE,IEVF_PROG_CODE,IEVF_BLK_NAME,IEVF_TRG_FLD_NAME,IEVF_ACT_FLDS,IEVF_ACTION,IEVF_PROC,IEVF_SRNO,IEVF_ERR_NO,IEVF_ERR_YN,IEVF_APP_CODE,IEVF_REMARKS,IEVF_UPD_UID,IEVF_UPD_DT,IEVF_CR_UID,IEVF_CR_DT,IEVF_TRG_NAME,IEVF_CLEAR_FLD_YN,IEVF_VALIDATE_YN) values (IEVF_SYS_ID.NEXTVAL,'APV-QQ-03','PGIT6_03','PGIT_POL_RISK_ADDL_INFO_01','PRAI_NUM_03','PRAI_DATA_15,','DEFAULT','VFB_EV_GEN.DEFAULT_PHYSICAL_DAMAGE_SYMBOL(:PGIT_POL_RISK_ADDL_INFO_01.PRAI_POL_SYS_ID,
    :PGIT_POL_RISK_ADDL_INFO_01.PRAI_PROD_CODE,
    :PGIT_POL_RISK_ADDL_INFO_01.PRAI_PSEC_SYS_ID,
    ''APV'',
    :PGIT_POL_RISK_ADDL_INFO_01.PRAI_NUM_03,
    :PGIT_POL_RISK_ADDL_INFO_01.PRAI_NUM_07,
    :PGIT_POL_RISK_ADDL_INFO_01.PRAI_CODE_03,
    :PGIT_POL_RISK_ADDL_INFO_01.PRAI_CODE_02,
    :P_FLAG_OUT,
    :PGIT_POL_RISK_ADDL_INFO_01.PRAI_DATA_15_OUT)',2,null,'N','01','DEFAULT',null,null,'PREMIA',to_date('30-AUG-07','DD-MON-RR'),'WHEN-VALIDATE-ITEM','0','1');
    Insert into IM_INSTANCE_EXT_VAL_FRM (IEVF_SYS_ID,IEVF_INST_CODE,IEVF_PROG_CODE,IEVF_BLK_NAME,IEVF_TRG_FLD_NAME,IEVF_ACT_FLDS,IEVF_ACTION,IEVF_PROC,IEVF_SRNO,IEVF_ERR_NO,IEVF_ERR_YN,IEVF_APP_CODE,IEVF_REMARKS,IEVF_UPD_UID,IEVF_UPD_DT,IEVF_CR_UID,IEVF_CR_DT,IEVF_TRG_NAME,IEVF_CLEAR_FLD_YN,IEVF_VALIDATE_YN) values (IEVF_SYS_ID.NEXTVAL,'APV-QQ-03','PGIT6_03','PGIT_POL_RISK_ADDL_INFO_01','PRAI_NUM_03',null,'VALIDATE','VFB_EV_GEN.EXT_VAL_PHY_DAMAGE(:PGIT_POL_RISK_ADDL_INFO_01.PRAI_POL_SYS_ID,
    :PGIT_POL_RISK_ADDL_INFO_01.PRAI_END_NO_IDX,
    :PGIT_POL_RISK_ADDL_INFO_01.PRAI_END_SR_NO,
    :PGIT_POL_RISK_ADDL_INFO_01.PRAI_LVL1_SYS_ID,
    :PGIT_POL_RISK_ADDL_INFO_01.PRAI_CODE_02,
    :PGIT_POL_RISK_ADDL_INFO_01.PRAI_NUM_03,
    :P_FLAG_OUT,
    :PGIT_POL_RISK_ADDL_INFO_01.PRAI_DATA_15_OUT)',9,null,'N','01','VALIADTION',null,null,'PREMIA',
    to_date('19-SEP-07','DD-MON-RR'),'WHEN-VALIDATE-ITEM','1','1');
    script which is taken from Sql Developer and got error while running in SQL* PLUS
    Following error was raised on running the script in SQL * PLUS
    5 rows deleted.
    1 row created.
    1 row created.
    1 row created.
    SP2-0734: unknown command beginning ":P_FLAG_OU..." - rest of line ignored.
    SP2-0734: unknown command beginning ":PGIT_POL_..." - rest of line ignored.
    SP2-0734: unknown command beginning "to_date('1..." - rest of line ignored.

Maybe you are looking for