ORA-00089: invalid instance number in ORADEBUG command

Answer Posted / guest

Cause: An invalid instance number was specified in a cluster
database ORADEBUG command.

Action: Reissue the command with valid instance numbers.

Please add more information about this Error

Is This Answer Correct ?    0 Yes 0 No



Post New Answer       View All Answers


Please Help Members By Posting Answers For Below Questions

ORA-26082: load of overlapping segments on table string.string is not allowed

1369


IMP-00096: Warning: Skipping table "string"."string" because type synonym "string"."string" cannot be created

1233


IMG-02003: 2FF03 - incorrect color histogram feature specification

1196


when i ran any workflow or session, getting below error: seesion task instance[s_xxx]: Execution terminated unexpecterdly

1746


ORA-16626: failed to enable specified object

1767






IMP-00070: Lob definitions in dump file are inconsistent with database.

1283


ORA-26095: unprocessed stream data exists

2794


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

2228


ORA-26076: cannot set or reset value after direct path structure is allocated

1469


[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

2282


IMP-00064: Definition of LOB was truncated by export

5879


IMP-00060: Warning: Skipping table "string"."string" because object type "string"."string" does not exist or has different identifier

2614


ORA-26094: stream format error: input column overflow

2245


RMAN-05017: no copy of datafile number found to recover

1878


ORA-16627: No standby databases support the overall protection mode.

3548