Discussions
Categories
- 197K All Categories
- 2.5K Data
- 546 Big Data Appliance
- 1.9K Data Science
- 450.8K Databases
- 221.9K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 552 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 556 SQLcl
- 4K SQL Developer Data Modeler
- 187.2K SQL & PL/SQL
- 21.4K SQL Developer
- 296.4K Development
- 17 Developer Projects
- 139 Programming Languages
- 293.1K Development Tools
- 110 DevOps
- 3.1K QA/Testing
- 646.1K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 161 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.2K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 19 Java Essentials
- 162 Java 8 Questions
- 86K Java Programming
- 81 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 205 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 475 LiveLabs
- 39 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 175 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 233 Portuguese
Isn't DESCRIBE supposed to work in Oracle Developer Tools for VS Code 21.4.0?

Just starting to use Oracle Developer Tools for VS Code as of today (05-Apr-2022). When attempting to do a DESCRIBE on a table you receive the following:
SQL> DESCRIBE CUST_MM_CENSUS;
ERROR at line 1: ORA-00904: "USER_GENERATED": invalid identifier
The exact same command works perfectly fine in Oracle SQL Developer.
Answers
-
Yes it is supposed to work. Maybe there's a bug with one of the column types.
Could you please paste the results of the describe command from SQL Developer here so I can try to create a similar table and reproduce it?
-
Having created the table I know is doesn't have anything unique about the table, so its unlikely there's an issue with a column type per se. This is in a Cerner-based Oracle Database which, knowing that Oracle is purchasing them means this might be something that will come up more often as more developers migrate to using true Oracle tools.
DESCRIBE in SQL Developer and SQLPlus provides the following:
Name Null? Type
-------------- -------- --------------
CENSUS_DATE NOT NULL VARCHAR2(10)
CENSUS_TIME NOT NULL VARCHAR2(8)
REPORT_DATE NOT NULL VARCHAR2(10)
MRN_NUMBER NOT NULL VARCHAR2(200)
ACCOUNT_NUMBER NOT NULL VARCHAR2(200)
ADMISSION_DATE NOT NULL VARCHAR2(10)
LOCATION NOT NULL VARCHAR2(2000)
ROOM_BED NOT NULL VARCHAR2(2000)
PATIENT_NAME NOT NULL VARCHAR2(100)
PATIENT_DOB NOT NULL VARCHAR2(10)
PATIENT_AGE CHAR(1)
DIAGNOSIS VARCHAR2(255)
MD VARCHAR2(100)
PROCESSED_IND NUMBER
SQL for table creation is as follows:
CREATE TABLE CUST_MM_CENSUS (
CENSUS_DATE VARCHAR2( 10 BYTE ) CONSTRAINT CUST_MM_CENSUS_NN01 NOT NULL
, CENSUS_TIME VARCHAR2( 8 BYTE ) CONSTRAINT CUST_MM_CENSUS_NN02 NOT NULL
, REPORT_DATE VARCHAR2( 10 BYTE ) CONSTRAINT CUST_MM_CENSUS_NN03 NOT NULL
, MRN_NUMBER VARCHAR2( 200 BYTE ) CONSTRAINT CUST_MM_CENSUS_NN04 NOT NULL
, ACCOUNT_NUMBER VARCHAR2( 200 BYTE ) CONSTRAINT CUST_MM_CENSUS_NN05 NOT NULL
, ADMISSION_DATE VARCHAR2( 10 BYTE ) CONSTRAINT CUST_MM_CENSUS_NN06 NOT NULL
, LOCATION VARCHAR2( 2000 BYTE ) CONSTRAINT CUST_MM_CENSUS_NN07 NOT NULL
, ROOM_BED VARCHAR2( 2000 BYTE ) CONSTRAINT CUST_MM_CENSUS_NN08 NOT NULL
, PATIENT_NAME VARCHAR2( 100 BYTE ) CONSTRAINT CUST_MM_CENSUS_NN09 NOT NULL
, PATIENT_DOB VARCHAR2( 10 BYTE ) CONSTRAINT CUST_MM_CENSUS_NN10 NOT NULL
, PATIENT_AGE CHAR( 1 BYTE )
, DIAGNOSIS VARCHAR2( 255 BYTE )
, MD VARCHAR2( 100 BYTE )
, PROCESSED_IND NUMBER DEFAULT 0
, CONSTRAINT CUST_MM_CENSUS_PK PRIMARY KEY ( CENSUS_DATE, CENSUS_TIME, LOCATION, ROOM_BED )
USING INDEX
TABLESPACE D_CUST
STORAGE ( INITIAL 1048576 NEXT 1048576 PCTINCREASE 0 MINEXTENTS 1 MAXEXTENTS UNLIMITED )
) TABLESPACE D_CUST
STORAGE ( INITIAL 1048576 NEXT 1048576 PCTINCREASE 0 MINEXTENTS 1 MAXEXTENTS UNLIMITED );
-
That works for me.
What version of the database are you using? I suspect that this error means you are using version 11 or earlier.
-
That is correct, Cerner uses 11g (11.2.0.4)
-
I will double check, but I think this is a bug in that we are issuing a query that uses the USER_GENERATED keyword which was only introduced in Oracle 12.
-
Thank you, most appreciated.