最近在oracle9.2.0.6上对业务数据表进行export（参数中带了direct=Y)导出的时候，数据库提示 ORA-600 [6191] or ORA-600 [6193]错误，不能导出，到metalink上进行搜寻，原因是oracle的一个bug，并说原因是：table contains a column with datatype LONG or LONG RAW and database block size is 8k or larger: DB_BLOCK_SIZE = 8192 (or higher)解决方法是升级oracle到更高版本或者将导出脚本中使用了direct=y修改未direct=N；
－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－参考metalink文章如下：ORA-600 [6191] or ORA-600 [6193] on DIRECT Mode Export
文档 ID: 注释:239965.1 类型: BULLETIN
上次修订日期: 06-MAY-2005 状态: PUBLISHED The information in this article applies to:- Oracle Server 8i - Release 2 - 8.1.6.0 up to 8.1.6.3
- Oracle Server 8i - Release 3 - 8.1.7.0 up to 8.1.7.4
- Oracle Server 9i - Release 1 - 9.0.1.1 up to 9.0.1.5
- Oracle Server 9i - Release 2 - 9.2.0.1 up to 9.2.0.6
- Oracle Server 10g - Release 1 - 10.1.0.1 up to 10.1.0.3
- Export Utility (EXP)
- Export is done in Direct Path mode: using parameter DIRECT=Y
- on all supported platforms
PURPOSE
-------
This document provides information about the known problems with a DIRECT
path export, that can result in internal errors like ORA-600 [6191] and
ORA-600 [6193].
SCOPE & APPLICATION
-------------------
The article is intended for users of the Oracle8i, Oracle9i and Oracle10g
databases who run a DIRECT path export and experience an internal error:
ORA-600 [6191] or ORA-600 [6193]. These errors may also reproduce when
exporting from older releases, such as from Oracle8 and Oracle7. As those
older releases have been de-supported, they are not listed in this docuement.
For details about the DIRECT path export see:
Note 155477.1 "Parameter DIRECT - Conventional Path Export Versus Direct
Path Export"
ORA-600 [6191] OR ORA-600 [6193] ON DIRECT MODE EXPORT
=========================================================
Bug 1477959
-------------
Details : A direct path export may fail with internal errors ORA-600 [6193]
if the table contains ROWID columns.
Releases: 8.1.6.0 and 8.1.6.1 and 8.1.6.2 and 8.1.6.3
8.1.7.0 and 8.1.7.1 and 8.1.7.2 and 8.1.7.3
9.0.1.1 and 9.0.1.2
Symptoms: EXP-00008: ORACLE error 600 encountered
ORA-00600: internal error code, arguments: [6193], [1], [579], [6],
[], [], [], []
Solution: Apply patchset and re-run the export:
- For Oracle8i 8.1.7.x: apply 8.1.7.4 patchset
- For Oracle9i 9.0.1.x: apply 9.0.1.3 patchset or any higher patchset
or: Upgrade and re-run the export:
- Upgrade to Oracle9i Release 2 (9.2.0.x)
- Upgrade to Oracle10g Release 1 (10.1.0.x)
or: Use the workaround:
- re-run the export in conventional path mode (DIRECT=N).
Bug 1686987 (not a public bug)
--------------------------------
Details : A direct path export may fail with internal errors ORA-600 [6191]
if the row data contains trailing null columns.
Releases: 8.1.6.0 and 8.1.6.1 and 8.1.6.2 and 8.1.6.3
8.1.7.0 and 8.1.7.1 and 8.1.7.2 and 8.1.7.3
9.0.1.1 and 9.0.1.2
Symptoms: EXP-00008: ORACLE error 600 encountered
ORA-00600: internal error code, arguments: [6191], [3], [3], [8], [],
[], [], []
Solution: Apply patchset and re-run the export:
- For Oracle8i 8.1.7.x: apply 8.1.7.4 patchset
- For Oracle9i 9.0.1.x: apply 9.0.1.3 patchset or any higher patchset
or: Upgrade and re-run the export:
- Upgrade to Oracle9i Release 2 (9.2.0.x)
- Upgrade to Oracle10g Release 1 (10.1.0.x)
or: Use the workaround:
- re-run the export in conventional path mode (DIRECT=N).
Bug 2308033
-------------
Details : A direct path export may fail with internal errors ORA-600 [6191]
or ORA-600 [6193] if the table contains a column with datatype
LONG or LONG RAW and database block size is 8k or larger:
DB_BLOCK_SIZE = 8192 (or higher)
Releases: 9.0.1.1 and 9.0.1.2 and 9.0.1.3
9.2.0.1
Symptoms: EXP-00008: ORACLE error 600 encountered
ORA-00600: internal error code, arguments: [6191], [3], [3937],
[3957], [], [], [], []
or:
EXP-00008: ORACLE error 600 encountered
ORA-00600: internal error code, arguments: [6193], [4], [44], [4000],
[4175], [], [], []
Ignoring these errors and trying to import from this corrupted export
dump file can produce several errors upon import, such as:
IMP-00020: long column too large for column buffer size (8)
IMP-00018: partial import of previous table completed: 50230 rows
imported
IMP-00008: unrecognized statement in the export file: ?
Solution: Apply patchset and re-run the export:
- For Oracle9i 9.0.1.x: apply 9.0.1.4 patchset or any higher patchset
- For Oracle9i 9.2.0.x: apply 9.2.0.2 patchset or any higher patchset
or: Upgrade and re-run the export:
- Upgrade to Oracle10g Release 1 (10.1.0.x)
or: Use the workaround:
- re-run the export in conventional path mode (DIRECT=N).
Bug 3230116
-------------
Details : A direct path export may fail with internal errors ORA-600 [6191]
or ORA-600 [6193] if the table or partition is compressed.
Releases: 9.0.1.1 and 9.0.1.2 and 9.0.1.3 and 9.0.1.4 and 9.0.1.5
9.2.0.1 and 9.2.0.2 and 9.2.0.3 and 9.2.0.4
Symptoms: EXP-00008: ORACLE error 600 encountered
ORA-00600: internal error code, arguments: [6193], [4], [494],
[20360], [64256], [], [], []
or:
EXP-00008: ORACLE error 600 encountered
ORA-00600: internal error code, arguments: [6191], [3], [6985],
[7156], [], [], [], []
Solution: Apply patchset and re-run the export:
- For Oracle9i 9.2.0.x: apply 9.2.0.5 patchset or any higher patchset
or: Upgrade and re-run the export:
- Upgrade to Oracle10g Release 1 (10.1.0.x)
or: Use the workaround:
- re-run the export in conventional path mode (DIRECT=N).
Bug 4085785
-------------
Details : A direct path export may fail with internal errors ORA-600 [6191]
if the partition is compressed.
This defect was introduced with the fix for Bug 3579567 "Corrupt
export exporting a compressed table with direct=y (IMP-9)"
Releases: 9.2.0.6
10.1.0.4 and 10.1.0.5
Symptoms: EXP-00008: ORACLE error 600 encountered
ORA-00600: internal error code, arguments: [6191], [3], [19058],
[51456], [], [], [], []
Solution: Apply patchset and re-run the export:
- For Oracle9i 9.2.0.6: apply 9.2.0.7 patchset (when available)
- For Oracle10g 10.1.0.4+: apply 10.1.0.6 patchset (when available)
or: Use the workaround:
- re-run the export in conventional path mode (DIRECT=N).RELATED DOCUMENTS
-----------------
Note 155477.1 "Parameter DIRECT - Conventional Path Export Versus
Direct Path Export"Bug 1477959 "OERI:6193 possible from DIRECT EXPORT of tables containing ROWID
columns"
Bug 1686987 "OERI:6191 possible from direct path export (with trailing NULL
columns)"
Bug 2308033 "OERI:6191 / OERI:6193 possible on DIRECT mode EXPORT of long
row with >=8k DB_BLOCK_SIZE"
Bug 3230116 "Direct export of a compressed table fails with OERI[6193]"
Bug 4085785 "ORA-600 [6191] on compressed partition export on version which
includes 3230116"
－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－参考metalink文章如下：ORA-600 [6191] or ORA-600 [6193] on DIRECT Mode Export
文档 ID: 注释:239965.1 类型: BULLETIN
上次修订日期: 06-MAY-2005 状态: PUBLISHED The information in this article applies to:- Oracle Server 8i - Release 2 - 8.1.6.0 up to 8.1.6.3
- Oracle Server 8i - Release 3 - 8.1.7.0 up to 8.1.7.4
- Oracle Server 9i - Release 1 - 9.0.1.1 up to 9.0.1.5
- Oracle Server 9i - Release 2 - 9.2.0.1 up to 9.2.0.6
- Oracle Server 10g - Release 1 - 10.1.0.1 up to 10.1.0.3
- Export Utility (EXP)
- Export is done in Direct Path mode: using parameter DIRECT=Y
- on all supported platforms
PURPOSE
-------
This document provides information about the known problems with a DIRECT
path export, that can result in internal errors like ORA-600 [6191] and
ORA-600 [6193].
SCOPE & APPLICATION
-------------------
The article is intended for users of the Oracle8i, Oracle9i and Oracle10g
databases who run a DIRECT path export and experience an internal error:
ORA-600 [6191] or ORA-600 [6193]. These errors may also reproduce when
exporting from older releases, such as from Oracle8 and Oracle7. As those
older releases have been de-supported, they are not listed in this docuement.
For details about the DIRECT path export see:
Note 155477.1 "Parameter DIRECT - Conventional Path Export Versus Direct
Path Export"
ORA-600 [6191] OR ORA-600 [6193] ON DIRECT MODE EXPORT
=========================================================
Bug 1477959
-------------
Details : A direct path export may fail with internal errors ORA-600 [6193]
if the table contains ROWID columns.
Releases: 8.1.6.0 and 8.1.6.1 and 8.1.6.2 and 8.1.6.3
8.1.7.0 and 8.1.7.1 and 8.1.7.2 and 8.1.7.3
9.0.1.1 and 9.0.1.2
Symptoms: EXP-00008: ORACLE error 600 encountered
ORA-00600: internal error code, arguments: [6193], [1], [579], [6],
[], [], [], []
Solution: Apply patchset and re-run the export:
- For Oracle8i 8.1.7.x: apply 8.1.7.4 patchset
- For Oracle9i 9.0.1.x: apply 9.0.1.3 patchset or any higher patchset
or: Upgrade and re-run the export:
- Upgrade to Oracle9i Release 2 (9.2.0.x)
- Upgrade to Oracle10g Release 1 (10.1.0.x)
or: Use the workaround:
- re-run the export in conventional path mode (DIRECT=N).
Bug 1686987 (not a public bug)
--------------------------------
Details : A direct path export may fail with internal errors ORA-600 [6191]
if the row data contains trailing null columns.
Releases: 8.1.6.0 and 8.1.6.1 and 8.1.6.2 and 8.1.6.3
8.1.7.0 and 8.1.7.1 and 8.1.7.2 and 8.1.7.3
9.0.1.1 and 9.0.1.2
Symptoms: EXP-00008: ORACLE error 600 encountered
ORA-00600: internal error code, arguments: [6191], [3], [3], [8], [],
[], [], []
Solution: Apply patchset and re-run the export:
- For Oracle8i 8.1.7.x: apply 8.1.7.4 patchset
- For Oracle9i 9.0.1.x: apply 9.0.1.3 patchset or any higher patchset
or: Upgrade and re-run the export:
- Upgrade to Oracle9i Release 2 (9.2.0.x)
- Upgrade to Oracle10g Release 1 (10.1.0.x)
or: Use the workaround:
- re-run the export in conventional path mode (DIRECT=N).
Bug 2308033
-------------
Details : A direct path export may fail with internal errors ORA-600 [6191]
or ORA-600 [6193] if the table contains a column with datatype
LONG or LONG RAW and database block size is 8k or larger:
DB_BLOCK_SIZE = 8192 (or higher)
Releases: 9.0.1.1 and 9.0.1.2 and 9.0.1.3
9.2.0.1
Symptoms: EXP-00008: ORACLE error 600 encountered
ORA-00600: internal error code, arguments: [6191], [3], [3937],
[3957], [], [], [], []
or:
EXP-00008: ORACLE error 600 encountered
ORA-00600: internal error code, arguments: [6193], [4], [44], [4000],
[4175], [], [], []
Ignoring these errors and trying to import from this corrupted export
dump file can produce several errors upon import, such as:
IMP-00020: long column too large for column buffer size (8)
IMP-00018: partial import of previous table completed: 50230 rows
imported
IMP-00008: unrecognized statement in the export file: ?
Solution: Apply patchset and re-run the export:
- For Oracle9i 9.0.1.x: apply 9.0.1.4 patchset or any higher patchset
- For Oracle9i 9.2.0.x: apply 9.2.0.2 patchset or any higher patchset
or: Upgrade and re-run the export:
- Upgrade to Oracle10g Release 1 (10.1.0.x)
or: Use the workaround:
- re-run the export in conventional path mode (DIRECT=N).
Bug 3230116
-------------
Details : A direct path export may fail with internal errors ORA-600 [6191]
or ORA-600 [6193] if the table or partition is compressed.
Releases: 9.0.1.1 and 9.0.1.2 and 9.0.1.3 and 9.0.1.4 and 9.0.1.5
9.2.0.1 and 9.2.0.2 and 9.2.0.3 and 9.2.0.4
Symptoms: EXP-00008: ORACLE error 600 encountered
ORA-00600: internal error code, arguments: [6193], [4], [494],
[20360], [64256], [], [], []
or:
EXP-00008: ORACLE error 600 encountered
ORA-00600: internal error code, arguments: [6191], [3], [6985],
[7156], [], [], [], []
Solution: Apply patchset and re-run the export:
- For Oracle9i 9.2.0.x: apply 9.2.0.5 patchset or any higher patchset
or: Upgrade and re-run the export:
- Upgrade to Oracle10g Release 1 (10.1.0.x)
or: Use the workaround:
- re-run the export in conventional path mode (DIRECT=N).
Bug 4085785
-------------
Details : A direct path export may fail with internal errors ORA-600 [6191]
if the partition is compressed.
This defect was introduced with the fix for Bug 3579567 "Corrupt
export exporting a compressed table with direct=y (IMP-9)"
Releases: 9.2.0.6
10.1.0.4 and 10.1.0.5
Symptoms: EXP-00008: ORACLE error 600 encountered
ORA-00600: internal error code, arguments: [6191], [3], [19058],
[51456], [], [], [], []
Solution: Apply patchset and re-run the export:
- For Oracle9i 9.2.0.6: apply 9.2.0.7 patchset (when available)
- For Oracle10g 10.1.0.4+: apply 10.1.0.6 patchset (when available)
or: Use the workaround:
- re-run the export in conventional path mode (DIRECT=N).RELATED DOCUMENTS
-----------------
Note 155477.1 "Parameter DIRECT - Conventional Path Export Versus
Direct Path Export"Bug 1477959 "OERI:6193 possible from DIRECT EXPORT of tables containing ROWID
columns"
Bug 1686987 "OERI:6191 possible from direct path export (with trailing NULL
columns)"
Bug 2308033 "OERI:6191 / OERI:6193 possible on DIRECT mode EXPORT of long
row with >=8k DB_BLOCK_SIZE"
Bug 3230116 "Direct export of a compressed table fails with OERI[6193]"
Bug 4085785 "ORA-600 [6191] on compressed partition export on version which
includes 3230116"
解决方案 »
免费领取超大流量手机卡，每月29元包185G流量+100分钟通话, 中国电信官方发货