ORA-21500: internal error code, arguments: [% s], [% s], [% s], [% s], [% s], [% s], [% s], [% s]
I searched a lot but none of the links helped me in solving this problem. I get
ORA-21500: internal error code, arguments: [% s], [% s], [% s], [% s], [% s], [% s], [% s], [% s] for using OracleDataAdapter.
I am using 11.2.0 Oracle client and oracle dataset is 11.1.0.7.0. Can anyone help me on why I am getting this error? Some of the links I was looking for say it has to do with an incompatible client and oracle database. This error is intermittent and debugging the problem did not provide many clues.
StackTrace result:
at Oracle.DataAccess.Client.OracleException.HandleErrorHelper(Int32 errCode, OracleConnection conn, IntPtr opsErrCtx, OpoSqlValCtx* pOpoSqlValCtx, Object src, String procedure, Boolean bCheck)
at Oracle.DataAccess.Client.OracleDataReader.Read()
at System.Data.Common.DataAdapter.FillLoadDataRow(SchemaMapping mapping)
at System.Data.Common.DataAdapter.FillFromReader(DataSet dataset, DataTable datatable, String srcTable, DataReaderContainer dataReader, Int32 startRecord, Int32 maxRecords, DataColumn parentChapterColumn, Object parentChapterValue)
at System.Data.Common.DataAdapter.Fill(DataTable[] dataTables, IDataReader dataReader, Int32 startRecord, Int32 maxRecords)
at Oracle.DataAccess.Client.OracleDataAdapter.Fill(DataTable[] dataTables, Int32 startRecord, Int32 maxRecords, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
Thanks for the comment. I just found this issue to be related to the fetch size that I am setting on the Oracle command object from which I am creating the Oracle Data Adapter. As soon as I stopped setting the command fetch size it started working fine without any problem.
From here :
Cause
The error is caused by an internal Oracle error that ArcGIS and ArcSDE cannot control. The error occurs when the application generates an SQL statement using an asterisk in SELECT (SELECT * FROM ...).
For more information on the Oracle error, see Oracle Metalink Note: 49375.1.
Bypass
There are two possible workarounds for this problem. Make sure there is a spatial index present for the feature class and / or adding an extra attribute after the ST_Geometry attribute.
To check for a spatial index using ArcCatalog, connect to an ArcSDE instance as a class owner. Select the function class. Open the properties dialog. Select the Indexes tab and make sure a spatial index is available.
To add a new attribute to a feature class in ArcCatalog, open the properties for the feature class. Select the fields tab and add a new attribute.
As soon as the ST_Geometry attribute is no longer in the last SELECT * position, the ORA-21500 internal error is no longer encountered.
source to share