Answer Posted / guest
Cause: The number specified on the OPEN_MOUNTS parameter in
the parameter file exceeds the maximum allowed (255).
Action: Change the value of this parameter so that it
reflects the actual number of possible open mounts to
secondary databases. This must be less than 255.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
[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
IMP-00096: Warning: Skipping table "string"."string" because type synonym "string"."string" cannot be created
ORA-26084: direct path context already finished
ORA-26028: index string.string initially in unusable state
ORA-26095: unprocessed stream data exists
NZE-28890: Entrust Login Failed
if the lengths of two wires are same and the area of cross sections is 4:7 then what will be the ratio of current passing through these wires
IMP-00063: Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier
RMAN-05017: no copy of datafile number found to recover
In my project I am using star schema and only diimension tables are loaded and not fact tables any one can help me why it is happening? Plase guide me.
ORA-26029: index string.string partition string initially in unusable state
IMP-00064: Definition of LOB was truncated by export
ORA-16627: No standby databases support the overall protection mode.
ORA-26094: stream format error: input column overflow
How to resolve QSM-01108 error. I have no OR conditions in my query, but do have 9 IN conditions. The error says the max limit is 2 while I have 257 number of disjuncts. However, if I remove even a single IN condition, the query is rewritten. I cannot change my query. How can I resolve this issue?