ORA-32400: cannot use object id columns from materialized
view log on "string"."string"
- 1 Answers
- 2489 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: The materialized view log either does not have object
id columns logged, or the timestamp associated with the
object id columns is more recent than the last refresh time.
Action: A complete refresh is required before the next fast
refresh. Add object id columns to the materialized view log,
if required.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
PROT-00010: Failed to open the specified source cluster registry
ORA-17610: file 'string' does not exist and no size specified
ORA-39056: invalid log file specification.
ORA-07279: spcre: semget error, unable to get first semaphore set.
KUP-04051: error processing column string in row number for datafile string
TNS-03504: Service name too long
TNS-00246: Connection Manager: Failed to start tracing
ORA-12843: pdml lock not held properly on the table
QSM-02178: MV has a view with UNION ALL that is not fast refreshable
QSM-00770: the specified workload string is already referenced by task string
ORA-39304: during sync/swap, object "string" conflicts: "string"
LPX-00659: Output write failed.
Oracle Errors 
