[ZBX-26118] Zabbix Agent 2 v7.0.10 - RHEL v8 -- Next: ORA-40478: output value too large (maximum: 4000) Created: 2025 Mar 01  Updated: 2025 Mar 27  Resolved: 2025 Mar 02

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Incident report Priority: Trivial
Reporter: Brian Smith Assignee: Zabbix Support Team
Resolution: False Positive Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2025-03-02-15-11-42-051.png    

 Description   

Steps to reproduce:

  1. Install Zabbix Agent 2 v7.0.10 for RHEL v8
  2. Install oracle-instantclient19.26-basic-19.26.0.0.0-1.x86_64.rpm
  3. Configure Oracle Plugin based (https://www.zabbix.com/integrations/oracle)
  4.  

Result:

2025/03/01 15:26:27.776634 [Oracle] Cannot fetch data.: Next: ORA-40478: output value too large (maximum: 4000).
2025/03/01 15:26:27.776703 failed to execute direct exporter task for key 'oracle.ts.stats[[tcp://<hostname>:1521 sys as sysdba <mypassword> <service>]]' error: 'Cannot fetch data.: Next: ORA-40478: output value too large (maximum: 4000).'
2025/03/01 15:26:27.776882 sending passive check response: '{"version":"7.0.10","variant":2,"data":[

{"error":"Cannot fetch data.: Next: ORA-40478: output value too large (maximum: 4000)."}

]}' to '<zabbix server>'

All discovery table spaces, in latest data, show "Cannot fetch data ...".

Expected:
Values to be populated during discovery

 Comments   
Comment by Brian Smith [ 2025 Mar 02 ]

I think this was caused by upgrading Zabbix from v5 to v7, and I forgot to upgrade my templates apparently.

I wiped updated the templates for Oracle by Zabbix agent 2, and my errors are gone (after deleting my asset).

Comment by Brian Smith [ 2025 Mar 02 ]

Issue was "upgraded induced" by not following full upgrade procedures.

Comment by Antons Sincovs [ 2025 Mar 27 ]

brian.smith  thank you for sharing the solution, yesterday stumbled upon the same issue and updating the template to the current (7.0) version did help.
The difference is that instead of one master item which might return > 4000 bytes

oracle.ts.discovery["{$ORACLE.CONNSTRING}","{$ORACLE.USER}","{$ORACLE.PASSWORD}","{$ORACLE.SERVICE}"]

Now oracle.ts.discovery item is used for each tablespace separately with additional parameters  "TABLESPACE","CONTENTS","CON_NAME" with the full syntax:

oracle.ts.stats["{$ORACLE.CONNSTRING}","{$ORACLE.USER}","{$ORACLE.PASSWORD}","{$ORACLE.SERVICE}","{#TABLESPACE}","{#CONTENTS}","{#CON_NAME}"]

This limits the returned output size to under 4000 bytes

Generated at Wed Jul 16 11:11:18 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.