RMAN-06182: archive log larger than MAXSETSIZE: thread
string seq string string
Answer Posted / guest
Cause: A BACKUP ARCHIVELOG command specified the MAXSETSIZE
operand too low. The specified archive log is larger than
MAXSETSIZE will allow.
Action: Increase MAXSETSIZE limit.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 1 No |
Post New Answer View All Answers
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
NZE-28868: Peer certificate chain check failed.
ORA-26029: index string.string partition string initially in unusable state
IMP-00096: Warning: Skipping table "string"."string" because type synonym "string"."string" cannot be created
IMP-00064: Definition of LOB was truncated by export
IMG-02003: 2FF03 - incorrect color histogram feature specification
[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
ORA-26032: index string.string loading aborted after string keys
ORA-26027: unique index string.string partition string initially in unusable state
ORA-26082: load of overlapping segments on table string.string is not allowed
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...
ORA-26084: direct path context already finished
IMP-00063: Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier
invalid quantity specification negative quantity are not allowed for this item please check this item definition quantity
ORA-26030: index string.string had string partitions made unusable due to: