ORA-25201: invalid value, VISIBILITY should be ON_COMMIT or
IMMEDIATE
Answer Posted / guest
Cause: An invalid value specified for parameter VISIBILITY.
Action: Specify either ON_COMMIT or IMMEDIATE.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
ORA-26032: index string.string loading aborted after string keys
ORA-26029: index string.string partition string initially in unusable state
ORA-26027: unique index string.string partition string initially in unusable state
NZE-28890: Entrust Login Failed
IMG-02003: 2FF03 - incorrect color histogram feature specification
ORA-16627: No standby databases support the overall protection mode.
When i am connect database through toad,one error occured. ORA-12514: TNS:listener does not currently know of service requested in connect descriptor. plz help me thanks advance.............
invalid quantity specification negative quantity are not allowed for this item please check this item definition quantity
IMP-00063: Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier
IMP-00070: Lob definitions in dump file are inconsistent with database.
IMP-00096: Warning: Skipping table "string"."string" because type synonym "string"."string" cannot be created
RMAN-05017: no copy of datafile number found to recover
IMP-00060: Warning: Skipping table "string"."string" because object type "string"."string" does not exist or has different identifier
ORA-26028: index string.string initially in unusable state
[ERROR] [main 11:01:20] (JCLLoggerAdapter.java:error:454) Unsuccessful: alter table user.CEN_USER_MASTER add constraint FKF4EDEDC3D0BAAE75 foreign key (ROLE_ID) references user.CEN_ROLE_MASTER [ERROR] [main 11:01:20] (JCLLoggerAdapter.java:error:454) ORA-02275: such a referential constraint already exists in the table