How to Solve :
Oracle database error code ORA-06807 – TLI Driver: could not open ethernet device driver file
Oracle Database Error Code ORA-6807 Description :
TLI Driver: could not open ethernet device driver file
Error Cause:
The file /dev/eth does not exist, or the driver it references could not be opened.
How to Solve :
The systems real ethernet device file, for example /dev/wd, for the Western Digital ethernet driver, should be linked to the file /dev/eth. If this has been done, insure that the ethernet driver has been installed by completing the TCP/IP installation on your system, and testing a connection. If problem continues, contact your customer support representative for a list of supported ethernet drivers.
Filed under: How to Solve, Oracle 10g, Oracle 11g, Oracle 9i, Oracle Error Codes Etiketler: ora - 6807, 06807, 6807, about oracle ORA-06807 error, help ORA-06807 about, How to Solve Oracle Database Error ORA-06807, ORA-06807 error code, ORA-06807 problem, Oracle 9i 10g 11g, Oracle Database Server Error Messages, Oracle Error Codes, oracle number 6807 error code, oracle ORA-06807 example, TLI Driver: could not open ethernet device driver file
No Comment Yet
No Comment Yet
Recent Entries
- Oracle database error code ORA-29959 – error in the execution of the string routine for one or more of the index partitions
- Oracle database error code ORA-31601 – Function string cannot be called now that fetch has begun.
- Oracle database error code ORA-29958 – fatal error occurred in the execution of ODCIINDEXCREATE routine
- Oracle database error code ORA-31600 – invalid input value string for parameter string in function string
- Oracle database error code ORA-29957 – cannot create a function-based domain index on a string table
- Oracle database error code ORA-31604 – invalid string parameter “string” for object type string in function string
- Oracle database error code ORA-29961 – too many warnings occurred in the execution of ODCIIndex DDL routine
Search Oracle Error Codes and Descriptions:
Be The First To Comment
Similar Errors
Please Leave Your Comments Below