Discussions
Categories
- 385.5K All Categories
- 5.1K Data
- 2.5K Big Data Appliance
- 2.5K Data Science
- 453.4K Databases
- 223.2K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 47 Multilingual Engine
- 606 MySQL Community Space
- 486 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.2K ORDS, SODA & JSON in the Database
- 585 SQLcl
- 4K SQL Developer Data Modeler
- 188K SQL & PL/SQL
- 21.5K SQL Developer
- 46 Data Integration
- 46 GoldenGate
- 298.4K Development
- 4 Application Development
- 20 Developer Projects
- 166 Programming Languages
- 295K Development Tools
- 150 DevOps
- 3.1K QA/Testing
- 646.7K Java
- 37 Java Learning Subscription
- 37.1K Database Connectivity
- 201 Java Community Process
- 108 Java 25
- 22.2K Java APIs
- 138.3K Java Development Tools
- 165.4K Java EE (Java Enterprise Edition)
- 22 Java Essentials
- 176 Java 8 Questions
- 86K Java Programming
- 82 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
- 208 Java User Groups
- 25 JavaScript - Nashorn
- Programs
- 667 LiveLabs
- 41 Workshops
- 10.3K Software
- 6.7K Berkeley DB Family
- 3.6K JHeadstart
- 6K Other Languages
- 2.3K Chinese
- 207 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 474 Portuguese
ORA-00904 invalid identifier when dropping generated column

Hello,
I have a table that was created as
CREATE TABLE xxx (
"SHAPE" "SDO_GEOMETRY",
"X_VALUE" NUMBER GENERATED ALWAYS AS ((("MDSYS"."SDO_GEOM"."SDO_POINTONSURFACE"("SHAPE",0.005))."SDO_POINT")."X") VIRTUAL ,
"Y_VALUE" NUMBER GENERATED ALWAYS AS ((("MDSYS"."SDO_GEOM"."SDO_POINTONSURFACE"("SHAPE",0.005))."SDO_POINT")."Y") VIRTUAL)
Both X_VALUE and Y_VALUE columns are created from the SHAPE (SDO_GEOMETRY) column, but when I want to drop them with:
ALTER TABLE xxx DROP (X_VALUE, Y_VALUE)
I get the error "ORA-00904: "MDSYS"."SDO_GEOM"."SDO_POINTONSURFACE": invalid identifier". Am I doing something wrong?
Best Answer
-
Thanks for supplying a model to test.
I've run it on 19.11.0.0 with a couple of variations. Obviously having the SHAPE column produces a number of virtual columns, but that doesn't seem to be the critical issue.
It looks like an Oracle bug; I've created a version of the table with some other "real" columns, before, after, and in between your columns, and if I include even one column like the X_VALUE or Y_VALUE I get the same error even when I drop a real, simple column.
Regards
Jonathan Lewis
Answers
-
Thanks for supplying a model to test.
I've run it on 19.11.0.0 with a couple of variations. Obviously having the SHAPE column produces a number of virtual columns, but that doesn't seem to be the critical issue.
It looks like an Oracle bug; I've created a version of the table with some other "real" columns, before, after, and in between your columns, and if I include even one column like the X_VALUE or Y_VALUE I get the same error even when I drop a real, simple column.
Regards
Jonathan Lewis
-
I've had another look at this - the only workaround I've found is to create functions that hide the complexity, viz:
create or replace function my_x(inshape mdsys.sdo_geometry) return number deterministic as begin return mdsys.sdo_geom.sdo_pointonsurface(inshape,0.005).sdo_point.x; end; / ... x_value number generated always as (my_x(shape)) virtual, ...
with a similar function and definition for y_value.
Regards
Jonathan Lewis