1 Reply Latest reply on Jul 14, 2016 3:30 PM by Gary Graham-Oracle

    CREATE TABLE STATEMENT THROWS WARNING ON COMPLETION, BUT WORKS

    sudiptabhaskar1

      Hello experts,

       

        I have facing one strange problem in sql developer.

       

      *********************************************************************************************************************************************************

        While creating any table with more than 8 columns, it is showing the following warning in sql developer, but the table gets created.

       

      create table dbo.bhaskar_test as select * from dbo.cd_individual where rownum between 1 and 10;

      create table bhaskar_test as select * from cd_individual where rownum between 1 and 10

      Error report -

      SQL Command: table BHASKAR_TEST

      Failed: Warning: execution completed with warning


      The same script runs perfectly fine in sql* plus.

       

      SQL> create table bhaskar_test as select * from cd_individual where rownum between 1 and 10;

       

      Table created.


      *************************************************************************************************************************************************************


      But if the number of columns are less than 8 then no such warning comes.


      create table bhaskar_test as select mem_no from cd_individual where rownum between 1 and 10;

      table BHASKAR_TEST created.


      **********************************************************************************************************************************************


      Kindly suggest.


      Thanks

      Bhaskar


        • 1. Re: CREATE TABLE STATEMENT THROWS WARNING ON COMPLETION, BUT WORKS
          Gary Graham-Oracle

          The following, with 11 columns, works fine using SQL Developer 4.1.3 against an 11g XE database:

          create table hr.employees_dup as select * from hr.employees where rownum between 1 and 10;

          That statement was executed while actually connected as HR.  Please share more details about your test case such as...

          1. SQL Developer version

          2. Whether you connected as DBO (a misleading SQL Server reference?)

          3. Differences in column data types between the 8 vs 8+ column test cases.

          1 person found this helpful