Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-24049: invalid agent name string, names with AQ$_ prefix
are not valid
- 1 Answers
- 3427 Views
- I also Faced
- E-Mail Answers
Answer Posted / guest
Cause: An attempt was made to use a reserved prefix in the
agent name.
Action: Enter a different value for the agent name. Then,
retry the operation.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
NZE-28890: Entrust Login Failed
IMP-00064: Definition of LOB was truncated by export
ORA-16627: No standby databases support the overall protection mode.
ORA-16626: failed to enable specified object
NZE-28868: Peer certificate chain check failed.
ORA-26076: cannot set or reset value after direct path structure is allocated
ORA-26082: load of overlapping segments on table string.string is not allowed
IMP-00096: Warning: Skipping table "string"."string" because type synonym "string"."string" cannot be created
Hi guys, I have four tables those are emp,dept,eliminate and uneliminate. i wrote small cursor..when i run, it display one error (ORA-01403 nodata found)... The query is: Declare cursor c1 is select e.ename emp_name from emp e,dept d where e.deptno=d.deptno group by deptno; r1 c1%rowtype; test_emp varchar2(200); begin for r1 in c1 loop begin select eliminate_emp into test_emp from eliminate t,uneliminate ut where t.number=ut.number and t.deptno=e.deptno and rownum<1; end; dbms_output.put_line(r1.emp_name); end loop; end; Thanks...
IMP-00070: Lob definitions in dump file are inconsistent with database.
ORA-26095: unprocessed stream data exists
ORA-07497: sdpri: cannot create trace file 'string'; errno = string.
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
IMP-00060: Warning: Skipping table "string"."string" because object type "string"."string" does not exist or has different identifier
