Answer / guest

Cause: Either records_per_block has been minimized for one
of the tables to be exchanged, but not the other, or the
hakan factors for the tables to be exchanged are not equal.

Action: If records_per_block has been minimized for one of
the tables, but not the other, either perform alter table
with the NOMINIMIZE RECORDS_PER_BLOCK option for both
tables, or perform alter table with the MINIMIZE
RECORDS_PER_BLOCK for both tables. If the hakan factors do
not match perform alter table with the NOMINIMIZE
RECORDS_PER_BLOCK option for both tables.

Please add more information about this Error

ORA-29501: invalid or missing Java source, class, or resource name

1 Answers  

---

ORA-25329: AQ array operations not allowed on 8.0 queues

1 Answers  

---

ORA-32741: Hang analysis already going on

1 Answers  

---

ORA-22913: must specify table name for nested table column or attribute

1 Answers   ABC,

---

ORA-22339: cannot alter to not final since its attribute column is substitutable

1 Answers  

---

ORA-30121: 'string' is not an allowable value for 'string'

1 Answers   CTS,

---

ORA-14192: cannot modify physical index attributes of a Hash index partition

1 Answers  

---

ORA-23375: feature is incompatible with database version at string

1 Answers  

---

ORA-25353: branch marked for deletion

1 Answers  

---

QSM-00788: the table string is invalid for directive string

1 Answers  

---

NNO-00622: warning: too many auto-refresh failures for name "string", query expired

1 Answers  

---

ORA-16641: failure to acquire broker configuration metadata lock

1 Answers  

---