Applies to:
Gupta Team Developer (TD) 6.1, 6.2, 6.3, 7.0
Summary:
In Team Developer, when connecting to Oracle using native router and fetching Oracle CLOB data, you might receive error 146 “Input message buffer set too small” or experience an application hang with 100% CPU usage depending on the size of the CLOB data fetched.
This issue occurs in (but may not be limited to): 6.3 SP2 Update 2, 7.0 Update 1
Resolution:
The current status of this issue is Open. Please check this article later for status updates.
Tracking Number:
TD-23468
TD-23468: Error 146 “Input message buffer set too small” or hang with 100% CPU usage fetching Oracle CLOB
-
- Founder/Site Admin
- Posts: 3321
- Joined: 24 Feb 2017, 09:12
- Location: Gouda, The Netherlands
TD-23468: Error 146 “Input message buffer set too small” or hang with 100% CPU usage fetching Oracle CLOB
Regards,
Dave Rabelink

Articles and information on Team Developer Tips & Tricks Wiki
Download samples, documents and resources from TD Sample Vault
Videos on TDWiki YouTube Channel
Dave Rabelink

Articles and information on Team Developer Tips & Tricks Wiki
Download samples, documents and resources from TD Sample Vault
Videos on TDWiki YouTube Channel
Re: TD-23468: Error 146 “Input message buffer set too small” or hang with 100% CPU usage fetching Oracle CLOB
Hello Dave,
we did come into this too.
For us this issue appears only at 64k. Depending on the type of data, we add a comment or some byte of NULL data ( in Insert/Update-Trigger) to jump over 64k...
The error appears first some bytes before 64k, I made some test runs adding one byte from cycle to cycle, it seems that the calculation for the needed buffersize fails at 64k.
Also the point where the error occurs depends on the additional data size your are fetching with the CLOB
Did you already test this with TD7?
Best regards
Henning
we did come into this too.
For us this issue appears only at 64k. Depending on the type of data, we add a comment or some byte of NULL data ( in Insert/Update-Trigger) to jump over 64k...
The error appears first some bytes before 64k, I made some test runs adding one byte from cycle to cycle, it seems that the calculation for the needed buffersize fails at 64k.
Also the point where the error occurs depends on the additional data size your are fetching with the CLOB
Did you already test this with TD7?
Best regards
Henning
-
- Founder/Site Admin
- Posts: 3321
- Joined: 24 Feb 2017, 09:12
- Location: Gouda, The Netherlands
Re: TD-23468: Error 146 “Input message buffer set too small” or hang with 100% CPU usage fetching Oracle CLOB
This defect has been fixed in TD 6.3.9
Regards,
Dave Rabelink

Articles and information on Team Developer Tips & Tricks Wiki
Download samples, documents and resources from TD Sample Vault
Videos on TDWiki YouTube Channel
Dave Rabelink

Articles and information on Team Developer Tips & Tricks Wiki
Download samples, documents and resources from TD Sample Vault
Videos on TDWiki YouTube Channel
Re: TD-23468: Error 146 “Input message buffer set too small” or hang with 100% CPU usage fetching Oracle CLOB
THX Dave,
that will be a great help with upgrading to TD 7.
Best regards
Henning
that will be a great help with upgrading to TD 7.
Best regards
Henning
Who is online
Users browsing this forum: [Ccbot] and 1 guest