imp 导入报错
IMP-00058: 遇到 ORACLE 错误 12571
ORA-12571: TNS: 包写入程序失败
IMP-00058: 遇到 ORACLE 错误 3114
ORA-03114: 未连接到 ORALCE
IMP-00000: 未成功终止导入
imp 语句为
imp aa/bb@cc file=F:/test.dmp tables=test log=F:/test.log buffer=31200000 indexes=n feedback=10000 ignore=y commit=y analyze=n grants=y
是数据库的问题还是网络的问题啊
谢谢大家啊
------解决方案--------------------
tnsping cc如果不通说明监听未启或监听名错误，如果通的话检查oracle服务端的服务是否都已经开启。
------解决方案--------------------
6. TCP/IP timeouts on Windows 95/98
The same parameter may also be used under Windows 95. It performs the same
functionality, however only the location of the parameter is different.
HKEY_LOCAL_MACHINE
System
CurrentControlSet
Services
Winsock
Parameters
TcpMaxDataRetransmissions REG_DWORD "number"
Again, the parameter is not present in the registry by default. This means
the parameter must be added to the registry the first time it is modified.
7. SDU & TDU parameters
Part of the problem may be the sequence of information that is transmitted.
If there are disruptions in the sequence, errors ORA-12151 and ORA-12571 can
also appear, alerting the application that not all information has been sent
across the network succesfully.
The sequence of information is determined by the amount of data the program
is sending and the actual size the protocol can send across the network
at a time.
The more data the program wants to send in one 'go', the more sequences and
transport packets will have to be made.
By default, SQL*Net uses a Session Data Unit SDU) of 2048 bytes (2Kb)
and a Transport Data Unit (TDU) of 32768 (32Kb) bytes. On standard Ethernet
connections, without modification, the SDU is 1500 bytes and TDU 8760 bytes.
With these values, each data request made by SQL*Net must be split into
several smaller packets to be able to be transmitted.
Therefore, where errors occur, it is recommended to minimise the creation of
unecessary additional packets by synchronising the SDU and TDU parameters at
the SQL*Net level with those of the actual network topology/protocol in use.
To use non-default SDU/TDU values, the parameters must be configured within
both client and server SQL*Net configuration files as follows:
TNSNAMES.ORA:
-------------
ORCL.WORLD =
(DESCRIPTION =
(SDU=1500)
(TDU=8760)
(ADDRESS_LIST =
(ADDRESS =(PROTOCOL=TCP)(HOST=foobar)(PORT=1521))
)
(CONNECT_DATA =
(SID = ORCL)
)
)
LISTENER.ORA:
-------------
...
SID_DESC_LISTENER =
(SID_LIST =
(SID_DESC =
(SDU = 1500)
(TDU = 8760)
(SID_NAME = ORCL)
)
)
For additional information regarding SDU and TDU parameters, refer to
Note 44694.1: SQL*Net Packet Sizes (SDU & TDU Parameters).
8. Setting a new TDU size on Windows NT
You can modify the TDU size on Windows NT, via the TcpWindowSize parameter:
HKEY_LOCAL_MACHINE
System
CurrentControlSet
Services
Tcpip
Parameters
TcpWindowSize REG_DWORD "number"
Additional information about Windows NT network parameters:
-----------------------
Q120642: TCP/IP & NBT Configuration Parameters for Windows NT