ORA-00998 or ORA-932 at imp or impdp for CREATE VIEW Using CURRENT_TIME Column
(Doc ID 2232974.1)
Last updated on APRIL 14, 2023
Applies to:
Oracle Database Cloud Service - Version N/A and laterOracle Database - Enterprise Edition - Version 12.1.0.2 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Information in this document applies to any platform.
Symptoms
Getting ORA-998 at either DataPump import (impdp) or traditional import (imp) when it creates an editionable view which contains current_time in the syntax:
CREATE OR REPLACE EDITIONABLE VIEW test_view as
select comp_ci_obj_nr, current_time,down_days from
(
select
1 comp_ci_obj_nr,
sysdate current_time,
0 down_days
from dual
) incidents
model
dimension by (current_time)
measures(down_days)
rules update (down_days[any]=0)
WITH READ ONLY;
The same syntax is successful in SQL*Plus.
Another possible error is:
ORA-00932: inconsistent datatypes: expected TIME WITH TIME ZONE got NUMBER as explained in Internal bug 30985910
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
ORA-39083: Object type CONSTRAINT failed to create with error:
ORA-00932: inconsistent datatypes: expected TIME WITH TIME ZONE got NUMBER
Changes
NONE
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |