- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: EXP-00014 and EXP-00008
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-23-2003 08:38 PM
тАО12-23-2003 08:38 PM
I have a database of release oracle 7.3.4 installed of UNIX HP 10.20. After having to launch the export of the database this night in mode direct, I come to receive the error messages according to:
EXP-00014: error on row 36342 of table CI_CNTRCT_LGHT
EXP-00008: ORACLE error 600 encountered
ORA-00600: internal error code, arguments: [8103], [], [], [], [], [], [], []
how to make to correct that?.
thank for your assistance.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-23-2003 08:58 PM
тАО12-23-2003 08:58 PM
Re: EXP-00014 and EXP-00008
There are a couple of articles on metalink which may help.
http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=FOR&p_id=54711.999
Basically this one can happen if someone drops the table whilst the export is running. Could this have happened ? Is your table CI_CNTRCT_LGHT still there?
http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=FOR&p_id=73165.996
This one was caused by a bug (no 623287), the fix is in 8.0.5 and not backported to 7.x
Hope this helps, but I fear an urgent upgrade is your best option.
-- Graham
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-23-2003 09:00 PM
тАО12-23-2003 09:00 PM
SolutionYou have encountered bug 430972, which is fixed in version 2.3.4 of SQL*Net. A local export uses the BEQ (bequeath) driver which reads the sqlnet.ora and hence enables dead connection detection (DCD) if sqlnet.expire_time is set.
Above is an extract from metalink note: 1037541.6
regards
and Merry Christmas
Yogeeraj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-23-2003 09:10 PM
тАО12-23-2003 09:10 PM
Re: EXP-00014 and EXP-00008
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-01-2004 10:18 PM
тАО01-01-2004 10:18 PM
Re: EXP-00014 and EXP-00008
It seems me to refer to something different. You have ORA-600; his refers to ORA-1013. Noth the same at all.
Please let us know.
-- Graham