PowerBuilder · Database exception

SQLDBCode 24333 (Oracle ORA-24333 Zero Iteration Count)

What does SQLDBCode 24333 (Oracle ORA-24333 Zero Iteration Count) mean in PowerBuilder?

SQLCA.SQLDBCode returns 24333, Oracle's ORA-24333 'zero iteration count' error, when a simple embedded SQL SELECT executes through an EAServer/Jaguar component's datasource (CacheName) connection but the underlying OCI fetch context was never given an iteration count, even though the initial CONNECT succeeded (SQLCode = 0). The same statement run over a direct hardcoded PowerBuilder connection (LogId/LogPass/ServerName) instead of the EAServer datasource typically does not fail.

SQLDBCode 24333 (Oracle ORA-24333 Zero Iteration Count)PowerBuilder Classic · Appeon PowerBuilder

Condition

SQLCA.SQLDBCode returns 24333, Oracle's ORA-24333 'zero iteration count' error, when a simple embedded SQL SELECT executes through an EAServer/Jaguar component's datasource (CacheName) connection but the underlying OCI fetch context was never given an iteration count, even though the initial CONNECT succeeded (SQLCode = 0). The same statement run over a direct hardcoded PowerBuilder connection (LogId/LogPass/ServerName) instead of the EAServer datasource typically does not fail.

Fix

If the failure only occurs through an EAServer-managed datasource connection, update the Oracle OCI client/driver and EAServer to a build where this connection-pooling defect is fixed rather than changing the SQL, since a direct PowerBuilder connection with the same statement works. As a workaround, route the affected retrieve through a direct transaction object instead of the CacheName-based pooled connection.

Pending source verification. Not yet checked against official documentation.

Related database exception