 |
|
ORA-02068: following severe error tips
Oracle Error Tips by Donald Burleson(S. Karam)
|
The Oracle docs note this on the
ora-02068 error:
-
ORA-02068: following severe
error from string string
-
-
Cause: A severe
error (disconnect, fatal Oracle error) received from the
indicated database link. See following error text.
-
Action: Contact the remote
system administrator.
MOSC documents offer information on
ORA-02068, On Enterprise Edition of Oracle Server; Version 9207 (occurring on
any platform). This ORA-02068 documents includes actions as follows:
Symptoms: Via Oracle Warehouse Builder, a package performs dml operations
via
db link on remote tables, for example truncate and insert. At the end, the
package executes dbms_stats.gather_schema_stats on that remote
schema. It
returns the following errors:
ORA-20999: odb_rep_interface.repli_contract: ORA-2068: following
severe
error
from ODB_DBLN
ORA-3113: end-of-file on communication channel
ORA-2068: following severe error from ODB_DBLN
ORA-3113: end-of-file on communication channel
ORA-6512: at ""DWRSOURCE.ODB_REP_INTERFACE"", line 446
ORA-6512: at line 2
The remote alert log shows ORA-7445 (null parameters) on an internal select
as shown in the Diagnostics section below.
Intermittently a ora-600[qks3tAssert:1][2304][][] also shows in alert log
The errors (including ORA-02068) begin after
patchset 9.2.0.7 on top of release 9.2.0.4 has been applied. The cause is
reported as follows:
Cause: The problem is caused by Bug 4439739 Base Bug 3494626 (as confirmed
by Bug Diagnostics and Escalations team in Bug 4773592).
The solution is in regards to many errors in
addition to ORA-02068 in cluding
ORA-600[QKS3TASSERT:1]
ORA-7445 NULL PARAMETERS
ORA-7445 "exception encountered: core dump [%s] [%s]"
ORA-20999
ORA-6512 "at %sline %s"
ORA-2068 following severe error from
ORA-3113 "end-of-file on communication channel"
And should be resolved as follows:
Solution: Do not run gather_schema_stats
within the same package. Run the DMLs within the package. Then, when the
package execution is done, execute gather_schema_stats.
Alternarively, upgrade to 10.1.0.5 (the bug is fixed in this release).
For further information, you are suggested to
view Bug Reference 4773592
