TCP read error 57

Hi, everyone:
In my graduation design, I need to acquire the data of biscuits from a video and then send it to a VC program. I've achieved the sending process correctly and the program can receive the data. But when I wanted to send a message from the VC program to LabVIEW, the TCP read error 57 occurred.
The TCP write VI and the TCP read VI are in different loops, and they use the same refnum. In the picture, the case structure in top while loop is the data acquiring program so I don't show them.
Can anybody teach me how to correct this program so it can receive data from the VC program? Thanks and forgive my poor English!

Hi,
Today i haven't any problem on the connection. The file is not changed. I think the system held some processes those use the tcp connection. I didn't think to watch in the task manager. It is the only explanation that I can pop out. Anyway I put above the program that gave me that problem. Please, check if the application is bad-built and suggest to me an alternative. Thanks
The block linked over is send-receive packet, opened above. In the first frame the block above send a message on the tcp connection, then it waits 1 second, finally it waits for the answer on the same connection (8 seconds).
The tcp reading block returns error 57. No other request on the same connection is active. I let the timeout of the block to end every 50 ms, I ignore error 56 (timeout) end I terminate the loop execution if:
- a message of a least 5 character is received (application protocol specification).
- the timeout of the receiving block ends (8 seconds)
- a tcp error different from 56 turns out.

Similar Messages

TCP Read Error Code 1

I met a problem in using "TCP Read" in LabView;
First I use "TCP Open Connection" building connection successful with a instrument; and seem the connection ID as the global,equal to a "TCP Network Connection Refnum";
Then I use the global as the connection ID,and use "TCP Write" send a command to a instrument;and use "TCP Read" Receive the instrument return message;this time a 56 error occurs,it is normal.
But after I use this method Send/Receive two times successfully,when i use "TCP Read" receive message, the error 1 occurs,and nothing received.
In each TCP operation,use the global "TCP Network Connection Refnum" as the "Connection ID" input.
someone can tell me,why does it occur?

JiangYu wrote:
> I met a problem in using "TCP Read" in LabView; First I use
> "TCP Open Connection" building connection successful with a instrument;
> and seem the connection ID as the global,equal to a "TCP Network
> Connection Refnum"; Then I use the global as the connection ID,
> and use "TCP Write" send a command to a instrument;and use "TCP Read"
> Receive the instrument return message;this time a 56 error occurs,it is
> normal. But after I use this method Send/Receive two times successfully,
> when i use "TCP Read" receive message, the error 1 occurs,and nothing received.
> In each TCP operation,use the global "TCP Network Connection Refnum"
> as the "Connection ID" input. someone can tell me,why does it occur?
Ouch, globals! That is usually the first sign of a bad application design.
For the rest just watch out. LabVIEW refnums are garbage collected
whenever the VI hierarchy which opened them goes idle (stops executing).
So Executing a VI which Opens the TCP refnum and writes it into a global
and then quits and then executing another VI which tries to use that
refnum from the global will simply fail with error 1 as the refnum has
been already automagically closed and is therefore invalid.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

TCP Read Error 1

Hello!
I would like to create a server - multi clients program. When i want to run that, the second iteration (top while loop, when listen a client) give the Error 1 error in the TCP Read.vi.
Somebody could help me?
(Sorry about my english, it isn't the best)
Thanks
Attachments:
MCP.zip ‏54 KB

Dear tibtobi!
Welcome on NI Discussion Forums!
In my opinion for such kind of projects it is better to use an already working solution.
Please allow me to recommend You a woking Multiple TCP Clients to One Server implementation:
Managing Multiple Clients from One Server Using TCP/IP in LabVIEW
There are also some articles about this topic like this:
Connecting Multiple TCP Clients to One Server in LabVIEW
There is also a reference library made by NI:
LabVIEW Simple Messaging Reference Library (STM)
In my opinion You could save a lot of time by using these already existing resources an implementations.
Please let me know, if my suggestion helped, or if You have any other questions.
Best Regards,
Balazs Nagy

Getting tcp/ip read errors when I receive an email

Hi
I have been having problems with a copier that scans to email. My production GWIA is too busy to monitor so I brought up another gwia to test with the copier. Its across a wan and used to work just fine. If they scan 1-6 pages it sends just fine. If they scan 9 or more it connects, stays connected for quite awhile and then disconnects with out a file getting sent. The TCP/ip read err incriments. We took the 12 pages and sent to a desktop to see how big the file was it its 400kb. I can copy a file over the wan in ~30 sec. The connection for email stays up for much longer than that.
I checked the nic on the server and its clean.
Very curious why I get the read error when its trying to write the file.
Thanks,
Will

Hi,
391783263 wrote:
> Very curious why I get the read error when its trying to write the
> file.
SMTP is a chain of commands and responses, alternating between sender
and receipient.
Example:
GWIA: Hi, I'm here.
Sender: Hello, I'm scanner.
GWIA: Hey, that's cool, how can I help.
Sender: Please accept MAIL FROM: [email protected]
GWIA: Will do, go ahead.
Sender: And please send that mail to RCPT TO: [email protected]
GWIA: I know that one, so I'll happily take it.
Sender: So here comes the DATA
GWIA: Ok, go ahead and send it, line by line. Once you're done, please
send me a single dot on it's own line so I know you're doe with it all.
Sender: Blabla, blabla.....
more blablalala
and even more blablaba
Gwia: Cool, I have that.
Sender: Cool, we're done. So I QUIT.
Gwia: Bye-Bye.
So now, if for some reason that nice little chat gets interrupted for
whatever reason, and at *whatever* stage, it simply depends on whose
turn it was to talk. If it was GWIA's turn to talk, and it found the
connection broken, you will get a TCP write error (because GWIA was
attempting to "write" something. If however it was the senders turn to
"talk", and it simply never did, or the connection broke down, you'll
receive a tcp read error, because GWIA was expecting to "read" something
from the other end, but nothing ever reached it.
In 99,999% of all cases, this is a low-lever TCP/IP communication
problem, regardless if it's a read or write error. Do *NOT* look at your
GWIA, you'll find nothing. Look at TCP/IP.
CU,
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
http://www.cfc-it.de

Error 56 Occurs When Using TCP Read.vi

TCP Read gives Error 56: The network operation exceeded the user-specified or system time
limit?
TCP Read in my application in not reliable. It works sometime, but it fails some other time. I tried to read just 1 byte, and set time out to be 1 min, I still get error code 56. What could cause this problem?

Most of the time it is due to a poor implementation of TCP-IP and the protocol implementation ontop of that.
There can be several causes.
Once the device we talked to could not handle the network traffic, resulting in several TCP-IP retries (part of TCP-IP) and showing the result only after minutes. There was loads of traffic on the network and the device was overloaded with traffic it shouldn't even been listing to. Solution was a router.
It could just as easily be something else.
Please post a screenshot or code snippet that shows your implementation and we can give you pointers.
André
Regards,
André
Using whatever version of LV the customer requires. (LV5.1-LV2012) (www.carya.nl)

Detecting Error #59 while using TCP Read.vi

I am using the TCP Read.vi to read data from a TCP connection. However, I need to know from the vi when the connection is lost, dropped, or reset. According to LabVIEW help, this should return back to me as Error #59. However, when I purposefully drop the connection on the server side, the TCP Read.vi does not return any errors.

Here is my example. Its a small vi that simulates what I am trying to do. Let me know if you have questions.
Attachments:
TCP_Example.llb ‏159 KB

Error 56 tcp read

Hi,
I'm having trouble with the TCP connection. My computer I am working on will be the server, or the listener, which is trying to connect with a linux based computer. I am able to successfully create a connection using TCP listen. When I am trying the TCP read, I am getting an error 56. I understand it is with the timing. I also tried to run the program with an unlimited amount of time (-1), but this did not seem to resolve the issue. I've attached the screen shots of the code. Server_Listen is the connection to initiate the listening, and Server_Read illustrates how my read is implemented.
Help? :-)
Thanks,
Andrea
Attachments:
Server_Listen.gif ‏5 KB
Server_Read.gif ‏4 KB

More likely than not you are not receiving 20 bytes of data. Your read is expecting to receive 20 bytes. If you don't you will get a timeout error and the whatever data that you did read will be returned. If you set the timeout to -1 you will read forever until 20 bytes are received. It is quite common in network applications to get a timeout when you don't know how much data you will be receiving. You use this timeout to determine if you did receive a block of data. Further processing can determine if you received the complete data or not. In cases where you have a protocol you need to read data according to the defined protocol. A very common and simple protocol would send a 4 byte value indicating the amount of data to follow. In a case like this read 4 bytes, convert it to an integer and use this as the amount of data for the next read.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

Error 56 in TCP Read

Hi,
I have TCP Read in a loop expecting data from some Micropchip boards connected to it. The problem I have is the boards do not send data all the time, hence I cannot wire in a specific constant to the number of bytes to read in, in the TCP read block.
Am I right in saying the only option is to clear the error 56 when it occurs?
Thanks,
Harshil

That should solve the problem. See this post...
There is a VI that you can use to clear this error. look fo rexamples\comm\UDP.llb\no timeout error.vi
The VI is located in an LLB named UDP, but the function only checks the error code, it has nothing to do with the connection.
Now is the right time to use %^<%Y-%m-%dT%H:%M:%S%3uZ>T
If you don't hate time zones, you're not a real programmer.
"You are what you don't automate"
Inplaceness is synonymous with insidiousness

TCP Read does not detect network conncetion closed error (66)

Hi Dear all,
Instead of LAN i am using WLAN to connect PC and mobile. All communication read and write operations are performing ok. But the only problem i am facing is that once i disconnect network connection from mobile my labview TCP read operation does not detect it and only timesout at its specified interval. Although for Bluetooth network connection if i disconnect from mobile then BT read detects it as network conncetion closed by peer error (66).
Can someone help me on this.
Thanks & Regards
awais qureshi
Solved!
Go to Solution.

Awais Qureshi wrote:
Hi Dear Norbert,
I am still waiting for your reply. Whats error you get once you unplug LAN cable? i am unable to understand how to detect Disconnection during Read Time out. Kindly help me in this.Thanks
Dear VT Kim,
I studied your recommended article but which way Labview handles TCP close connection then. i am unable to understand how to detect Disconnection during Read Time out. Kindly help me in this.
Regards
awais qureshi
I have not tested it but more likely than not you would get an error 59 when the network cable is unplugged. Error 66 is for when the network is still up and you attempt to communicate on an established connection that has been closed by the other side. This is not an error that you will se from a TCP read very often.
Also, please keep you related question in a single thread rather than starting multiple threads for the same topic.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

Error 56 occurred at TCP Read in MB Ethernet Receive.vi

My sensor uses MODBUS TCP and operates as a slave device. Currently I'm using Labview 7.1 on my PC and would like to communicate w/ sensor as a Master. I downloaded MODBUS library from ni developer zone. I want to read 14 discrete outputs (coils). I believe MB Ethernet Master Query.vi is most appropriate to use for my application. I put this block into my *.vi inside of a while loop, hooked up the connection ID, configured it with address start/quantity, and ran. The error I got says: "Error 56 occurred at TCP Read in MB Ethernet Receive.vi->MB Ethernet Master Query.vi->...*.vi". I have confirmed that TCP is working with Labview because I can receive other non-MODBUS sensor data from my device via TCP/IP using a different *.vi I created. However this data is received though a different port than the typical 502 MODBUS port. I have also confirmed MODBUS is working on my device using a 3rd party Polling Utility that reports register status.
I currently do not have NI-VISA 3.0.1, VISA Server 3.0.0, or Measurement & Automation Explorer (MAX) version 3.1.1 installed on my PC. Do I absolutely need these products to do what I need to do?
Any thoughts why I am not able to get this setup working?
Also, I am embarking on developing several MODBUS applications after this. Would it be a good idea to upgrade my version of Labview to gain more MODBUS functionality w/ Labview? I'm somewhat new to Labview and am a little confused on which products would really help me for working on MODBUS applications and if those products are compatible with my 7.1 version.

Hi cwallis2,
If you can use TCP/IP in Labview then you should be okay as far as that is concerned. The Ethernet Modbus VIs use LabVIEW TCP VIs underneath; the Serial Modbus VIs use VISA underneath. So unless you want to try the serial VIs if that's a possibility, then you should be okay without VISA.
The error 56 is a time-out error and is generated when an operation
exceeds the user-specified time limit. This error is caused by the
LabVIEW code not receiving a network response in the defined time
limit. The default time-out limit is 5 seconds, which should be enough,
although you can increase this time-out value as an input for the MB
Ethernet Master Query.vi. Since you get the time-out when you are
reading instead of the initialization lets us know that you are able to
open the TCP port correctly.
What is the address you entering into the MB Ethernet Master Query.vi in the Modbus Command constant? You may need to use relative addressing instead of absolute addressing, or vice versa.
Hope this helps!
Adam W
Applications Engineering
National Instruments

Socket read error: connection reset by peer

Hi.
Has anybody experienced the error message �Socket read error: connection reset by peer�
Please see below for detailed information.
Appreciate your help
Regards
RT
Enviroment specification
Server: HP/UX 11.00 64-bit, Oracle RDBMS 8.1.6.0.0 64-bit
2 firewalls between client and db.
Client:
Win 2000,
SP3,
Oracle Client 8.1.7.0.0 ,JDBC OCI (thin JDBC driver,class12.zip)
JDK 1.3
JRUN3.0
The TCP protocol is being used in the communication
Error messages
Web Users receive: Socket read error: connection reset by peer
Trace files on the sever: Read unexpected EOF ERROR on 18.
Explanation: The error in the server sqlnet trace file, suggests that a client connection has terminated abnormally, i.e. client machine powered off, a cable removed or a network connection aborted without warning. No user has complained of such a problem and there is no client trace with an error.
The problem
The users of the java web application, experiencing an exception almost once or twice a day.
The JRUN web-server reports broken connections to the db and client are receiving "connection reset by peer".
At the moment when the errors occurs the users just have to wait a while(2-10 min) and then they can use the web application again.(no action is taken)
This problem can not be reproduced. The problem happens only occasionally when the network is under heavy load and new DB connection is being created.
The application
The java web-application uses a customized connection pooling against the database. This pool is shared among all the users of the website. whenever a user process needs to fetch data from the database, a free connection from this pool is allocated. The application is testing if the connection is valid before making a transaction (select '1' from dual). When the error occurs a ORA-3113 end-of-file on communication channel is returned to the application.
The path between the client and db involves at least two firewalls. The firewalls are opened for sql*net traffic. The network group can tell that enquiries from the app.server is not getting feedback from the db. They have not however, identified if the enquiries are reaching the db-srever, or if they are stopped earlier in the network.
Around 1000 users, are using other applications which uses dedicated sqlnet connections against the db and they have not experienced any problems.
Issues considered
Connection pooling
It is a customized connection pooling, developed by Lindorff developers.
I have read through the source code for the connection pooling and it does the job as it should, and in case of bad connection, it tries to create a new connection.
The log file shows that the call to the method DriverManager.getConnection() hangs until the server goes down, which is probably because of the fact that the method DriverManager.setLoginTimeout(), does not take effect and timeout value is Zero. ( According to oracle , Oracle JDBC does not support login timeouts and calling the static DriverManager.setLoginTimeout() method will have no effect).
Firewall
One thing to consider is when the firewall may decide to shut down the socket due to long inactivity of a connection. This will cause problems to JDBC Connection Pool because the pool is not aware of this disconnection at the TCP/IP level; until someone checks out the connection from the pool and tries to use it. The user will get a Socket read error: connection reset by peer.
Jrun timeout paramter is less than the firewall�s timeout so the firewall will not close a connection before Jrun does.
Number of processes the DB can handle
Processes parameter is 1300, , they have not experienced the Oracle error msg �max # of processes reached�.
Port redirection through a firewall:
Since the firewall has a sql net proxy Port redirection through a firewall is not a problem. Problems with port redirection only appear at connect time, but in this situation the connections fail long after the connection is established.
The network group
The network people who investigaged the problem at Lindorff report that there are a significant amount of "dropped packages" between the database server and the jdbc client (web-application) 24 hrs. The reason for this is "unknown established TCP packet" which means that the firewall does not consider these packages to be part of an already established session. The network group believes this happen because one of the hosts send a RESET or FIN signal which the firewall have noticed but are not received by the other host.
It seems like the firewall are dropping packages bacause of "Unknown
established TCP packet" from both the JDBC client and the TNSLISTENER on the database server. The dropped packages are SQL*Net v2 traffic so clearly Oracle products are involved

Presumably something is working.
Thus the problem is not with your code. At least not the database part that you have control over.
That error occurs when the other side closes the socket. Presumably you are catching lost connection exceptions and trying to restore it.

TCP connection error when sending MODBUS commands to WAGO 750-881 controller after 113655 bytes of data have been sent

Hi all,
I am new to the world of labview and am attempting to build a VI which sends commands to a 750-881 WAGO controller at periodic intervals of 10ms.
To set each of the DO's of the WAGO at once I therefore attempt to send the Modbus fc15 command every 10ms using the standard Labview TCP write module.
When I run the VI it works for about a minute before I recieve an Error 56 message telling me the TCP connection has timed out. Thinking this strange, I decided to record the number of bytes sent via the TCP connection whilst running the program. In doing so I noticed that the connection broke after exactly 113655 Bytes of data had been sent each time.
Thinking that I may have been sending too many messages I increased the While-loop delay from 10ms to 20, 100 and 200 ms but the error remained. I also tried playing with the TCP connection timeout and the TCP write timeout but neither of these had any effect on the problem.
I cannot see why this error is occuring, as the program works perfectly up untill the 113655 Bytes mark.
I have attached a screenshot of the basic VI (simply showing a MODBUS command being sent every second) and of a more advanced VI (where I am able to control each DO of the WAGO manually by setting a frequency at which the DO should switch between ON and OFF).
If anybody has any ideas on where the problems lie, or what I could do to further debug the program this would be greatly appreciated.
Solved!
Go to Solution.
Attachments:
Basic_VI.png ‏84 KB
Expanded_VI.png ‏89 KB

AvdLinden wrote:
Hi ThiCop,
Yes the error occurs after exactly 113655 bytes every time. The timeout control I would like to use is 10ms, however even increasing this to 1s or 10s does not remove the error, which leads me to believe that this is not the issue (furthermore, not adding any delay to the while loop, thus letting it run at maximum speed, has shown that the TCP connection is able to send all 113655 bytes in under 3 seconds again pointing towards the timeout control not being the issue here).
I attempted Marco's suggestion but an having difficulty translating the string returned into a readable string, (rightnow the response given is " -# + ").
As to your second suggestion, I implemented something similar where I created a sub VI to build a TCP connection, send a message and then close the connection. I now build each message and then send the string to this subVI which successfully sends the command to my application. Whilst not being the most elegant method of solving the issue, it has resolved the timeout problem meaning I am able to send as many commands as I want. So in that sense the problem has been solved.
If you still have tips on how to correctly read the TCP read output, I would however like to see if I could not get my first program to work as it is slightly more robust in terms of timing.
Modbus TCP RTU is a binary protocol, as you show in your Basic VI, where you format the data stream using byte values. So you have to interprete the returned answer accordingly with the Modbus RTU spec in hand. Now what is most likely happening is that the connection gets hung after a while since you do NOT read the data the device sends as response to your commands. The TCP/IP stack buffers those bytes and at some point the internal buffers overflow and the connection is blocked by the stack. So adding the TCP Read at strategic places (usually after each write) is the proper solution for this. Is there any reason that you didn't use the NI provided Modbus TCP library?
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

ORA-00333: redo log read error block

ORA-01033: ORACLE initialization or shutdown in progress ...
/ as sysdba
SQL> shutdown immediate;
SQL> startup nomount;
SQL> alter database mount;
SQL> alter database open;
ORA-00333: redo log read error block 8299 count 8192
SQL> SELECT * FROM V$VERSION;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Product
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for 32-bit Windows: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
SQL> select group#,members,THREAD, STATUS,ARCHIVED,BYTES,FIRST_TIME,FIRST_CHAGE#,SEQUENCE# from v$log;
GROUP# MEMBERS,THREAD,STATUS,ARCHIVED,BYTES,FIRST_TIME,FIRST_CHAGE#,SEQUENCE#
1 1 1 CURRENT NO 52428800 29-FEB-12 1597643 57
2 1 1 INACTIVE NO 52428800 29-FEB-12 1573462 56
Dump file c:\oraclexe\app\oracle\admin\xe\bdump\alert_xe.log
Wed Feb 29 19:46:38 2012
Recovery of Online Redo Log: Thread 1 Group 1 Seq 56 Reading mem 0
Mem# 0 errs 0: C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_1_7LZYZK8S_.LOG
Wed Feb 29 19:46:40 2012
Completed redo application
Wed Feb 29 19:46:40 2012
Completed crash recovery at
Thread 1: logseq 56, block 6568, scn 1597642
270 data blocks read, 270 data blocks written, 1460 redo blocks read
Wed Feb 29 19:46:43 2012
Thread 1 advanced to log sequence 57
Thread 1 opened at log sequence 57
Current log# 2 seq# 57 mem# 0: C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_7LZYZL5V_.LOG
Successful open of redo thread 1
Wed Feb 29 19:46:43 2012
SMON: enabling cache recovery
Wed Feb 29 19:46:55 2012
Successfully onlined Undo Tablespace 1.
Wed Feb 29 19:46:55 2012
SMON: enabling tx recovery
Wed Feb 29 19:46:56 2012
Database Characterset is AL32UTF8
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=19, OS id=3024
Wed Feb 29 19:47:09 2012
Completed: alter database open
Wed Feb 29 19:47:14 2012
db_recovery_file_dest_size of 10240 MB is 0.98% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Wed Feb 29 20:33:30 2012
MMNL absent for 1537 secs; Foregrounds taking over
Wed Feb 29 20:33:31 2012
MMNL absent for 1540 secs; Foregrounds taking over
Wed Feb 29 20:33:31 2012
MMNL absent for 1540 secs; Foregrounds taking over
MMNL absent for 1540 secs; Foregrounds taking over
Wed Feb 29 20:33:32 2012
MMNL absent for 1540 secs; Foregrounds taking over
Wed Feb 29 20:33:33 2012
MMNL absent for 1540 secs; Foregrounds taking over
Wed Feb 29 21:45:24 2012
MMNL absent for 4318 secs; Foregrounds taking over
MMNL absent for 4318 secs; Foregrounds taking over
MMNL absent for 4322 secs; Foregrounds taking over
Dump file c:\oraclexe\app\oracle\admin\xe\bdump\alert_xe.log
Wed Feb 29 22:30:01 2012
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows XP Version V5.1 Service Pack 3, v.3244
CPU : 2 - type 586, 2 Physical Cores
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:3097M/3546M, Ph+PgF:5143M/5429M, VA:1943M/2047M
Wed Feb 29 22:30:01 2012
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =10
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
sessions = 49
__shared_pool_size = 201326592
__large_pool_size = 8388608
__java_pool_size = 4194304
__streams_pool_size = 0
spfile = C:\ORACLEXE\APP\ORACLE\PRODUCT\10.2.0\SERVER\DBS\SPFILEXE.ORA
sga_target = 805306368
control_files = C:\ORACLEXE\ORADATA\XE\CONTROL.DBF
__db_cache_size = 587202560
compatible = 10.2.0.1.0
db_recovery_file_dest = C:\oraclexe\app\oracle\flash_recovery_area
db_recovery_file_dest_size= 10737418240
undo_management = AUTO
undo_tablespace = UNDO
remote_login_passwordfile= EXCLUSIVE
dispatchers = (PROTOCOL=TCP) (SERVICE=XEXDB)
shared_servers = 4
local_listener = (ADDRESS=(PROTOCOL=TCP)(HOST=winsp3ue)(PORT=1522))
job_queue_processes = 4
audit_file_dest = C:\ORACLEXE\APP\ORACLE\ADMIN\XE\ADUMP
background_dump_dest = C:\ORACLEXE\APP\ORACLE\ADMIN\XE\BDUMP
user_dump_dest = C:\ORACLEXE\APP\ORACLE\ADMIN\XE\UDUMP
core_dump_dest = C:\ORACLEXE\APP\ORACLE\ADMIN\XE\CDUMP
db_name = XE
open_cursors = 300
os_authent_prefix =
pga_aggregate_target = 268435456
PMON started with pid=2, OS id=2176
PSP0 started with pid=3, OS id=2204
MMAN started with pid=4, OS id=2208
DBW0 started with pid=5, OS id=2212
LGWR started with pid=6, OS id=2220
CKPT started with pid=7, OS id=2240
SMON started with pid=8, OS id=2460
RECO started with pid=9, OS id=2464
CJQ0 started with pid=10, OS id=2480
MMON started with pid=11, OS id=2484
Wed Feb 29 22:30:02 2012
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=12, OS id=2492
Wed Feb 29 22:30:02 2012
starting up 4 shared server(s) ...
Oracle Data Guard is not available in this edition of Oracle.
Wed Feb 29 22:30:02 2012
alter database mount exclusive
Wed Feb 29 22:30:06 2012
Setting recovery target incarnation to 2
Wed Feb 29 22:30:06 2012
Successful mount of redo thread 1, with mount id 2657657770
Wed Feb 29 22:30:06 2012
Database mounted in Exclusive Mode
Completed: alter database mount exclusive
Wed Feb 29 22:30:07 2012
alter database open
Wed Feb 29 22:30:07 2012
Beginning crash recovery of 1 threads
Wed Feb 29 22:30:07 2012
Started redo scan
Wed Feb 29 22:30:15 2012
Errors in file c:\oraclexe\app\oracle\admin\xe\udump\xe_ora_2544.trc:
ORA-00333: redo log read error block 10347 count 6144
ORA-00312: online log 2 thread 1: 'C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_7LZYZL5V_.LOG'
ORA-27070: async read/write failed
OSD-04016: Error queuing an asynchronous I/O request.
O/S-Error: (OS 23) Data error (cyclic redundancy check).
Waiting for Help
Regards

Errors in file c:\oraclexe\app\oracle\admin\xe\udump\xe_ora_2544.trc:
ORA-00333: redo log read error block 10347 count 6144
ORA-00312: online log 2 thread 1: 'C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_7LZYZL5V_.LOG'
ORA-27070: async read/write failed
OSD-04016: Error queuing an asynchronous I/O request.
O/S-Error: (OS 23) Data error (cyclic redundancy check).Might your redo log file is corrupted or not exist, check physically. -> C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_7LZYZL5V_.LOG
is it archivelog mode?
perform fake recovery and open resetlogs.

TCP/IP error 111 (connection refused)

I encountered TCP/IP error 111 (connection refused) in my source DB. I ran view ggsevt.
Source
2013-09-06 17:47:41 INFO    OGG-00987 Oracle GoldenGate Command Interpreter for Oracle: GGSCI c
ommand (oracle): edit params mgr.
2013-09-06 17:48:00 INFO    OGG-00987 Oracle GoldenGate Command Interpreter for Oracle: GGSCI c
ommand (oracle): stop extract ext1.
2013-09-06 17:48:05 WARNING OGG-01223 Oracle GoldenGate Capture for Oracle, ext1.prm: TCP/IP er
ror 111 (Connection refused).
Target
2013-09-06 17:49:38 INFO    OGG-01677 Oracle GoldenGate Collector for Oracle: Waiting fo
r connection (started dynamically).
2013-09-06 17:49:54 ERROR   OGG-01224 Oracle GoldenGate Collector for Oracle: opening po
rt to MGR from SERVER failed with 2:Could not establish host TCP/IP address.
2013-09-06 17:49:54 ERROR   OGG-01668 Oracle GoldenGate Collector for Oracle: PROCESS AB
ENDING.
Firewall is cleared, I can telnet from source to target with port 7809. Not an issue. Checked in another post where a user encountered error in /etc/hosts. My settings are perfect right.
[oracle@db1 dirdat]$ telnet db4 7809
Trying 192.168.56.101...
Connected to db4.localdomain (192.168.56.101).
Escape character is '^]'.
Connection closed by foreign host.
Source:
> edit params mgr
DYNAMICPORTLIST 7000-9000
PORT 7809
Any help is much appreciated.

HI I have the same problem
PLZ tell me the solution！
$ telnet 10.80.16.214 7809
Trying 10.80.16.214...
Connected to 10.80.16.214.
Escape character is '^]'.
Connection to 192.168.0.178 closed by foreign host.
2013-09-13 10:21:42 WARNING OGG-01223 Oracle GoldenGate Capture for Oracle, pum_2.prm: TCP/IP error 111 (Connection refused).
2013-09-13 10:21:54 WARNING OGG-01223 Oracle GoldenGate Capture for Oracle, pum_2.prm: TCP/IP error 111 (Connection refused).
2013-09-13 10:22:05 WARNING OGG-01223 Oracle GoldenGate Capture for Oracle, pum_2.prm: TCP/IP error 111 (Connection refused).
2013-09-13 10:22:16 WARNING OGG-01223 Oracle GoldenGate Capture for Oracle, pum_2.prm: TCP/IP error 111 (Connection refused).
2013-09-13 10:22:27 WARNING OGG-01223 Oracle GoldenGate Capture for Oracle, pum_2.prm: TCP/IP error 111 (Connection refused).
2013-09-13 10:22:38 WARNING OGG-01223 Oracle GoldenGate Capture for Oracle, pum_2.prm: TCP/IP error 111 (Connection refused).
2013-09-13 10:22:49 WARNING OGG-01223 Oracle GoldenGate Capture for Oracle, pum_2.prm: TCP/IP error 111 (Connection refused).
2013-09-13 10:23:00 WARNING OGG-01223 Oracle GoldenGate Capture for Oracle, pum_2.prm: TCP/IP error 111 (Connection refused).
2013-09-13 10:23:11 WARNING OGG-01223 Oracle GoldenGate Capture for Oracle, pum_2.prm: TCP/IP error 111 (Connection refused).
2013-09-13 10:23:22 ERROR   OGG-01224 Oracle GoldenGate Capture for Oracle, pum_2.prm: TCP/IP error 111 (Connection refused); retries exceeded.
2013-09-13 10:23:22 ERROR   OGG-01668 Oracle GoldenGate Capture for Oracle, pum_2.prm: PROCESS ABENDING.

Setting TCP Read timeout value?

How do I choose a timeout value for a TCP read function?
I'm receiving data from a server at a rate which varies between 40 and 140 Hz (normally 120 Hz), there is no handshaking and at any set transmission rate it appears that the network load causes the rate to fluctuate slightly.
All I have been able to do so far is plot a frame number that is received in my data and fiddle with the buffer mode and timeout until I get the least dropouts. At 120Hz 5ms works best with a standard buffer, surprisingly 8ms is poorer.
I am using a producer consumer loop with a queue and some interpolation to make up for the loss of data.
This is very hit and miss so I'm sure there's a proper / better way to do this!

If you are using standard mode, then the read function should return any partial data, but will report an error out.
You may want to look at the functions that you call after the TCP read. I think that the enqueue function will NOT enqueue data if there is an error in.
There is a function you can use to clear TCP timeout errors. You could use this to allow you to enqueue partial data to your consumer loop.
vi.lib\addons\internet\utils\tcputil.llb\No Time Out Error.vi
Note that it will be up to your consumer code to identify your 'frames' for proper decoding.
Now is the right time to use %^<%Y-%m-%dT%H:%M:%S%3uZ>T
If you don't hate time zones, you're not a real programmer.
"You are what you don't automate"
Inplaceness is synonymous with insidiousness

TCP read error 57

Similar Messages

Maybe you are looking for