Problem Reading data from server - java.io.UTFDataFormatException

[Former Member]

I have done a SQL Query with row count as 10,000.

I have some 9500 records(rows of data) in my database.

When populating those data through a grid in portal an error is coming in java console:

<b>Problem Reading data from server - Java.io.UTFDataFormatException.</b>

Because of this error ,data is not populated in the grid, empty grid is displayed.

Is 10,000 is the maximum no of rows which can be displayed in a grid ?

Is this error because of data volume?

Please provide your inputs.

[Former Member]

If you test the query template, do you get data back or do you get this error?

What other data columns are being returned from the query? Are there any "funky" characters in the result set?

[Former Member]

Ryan,

Through Query Template I dont get the error and Query runs successfully

If I use dynamic page generator it throws the same error.

There are no Funky characters but "/" is there in the data.

Is this error due to SQL Server Memory size used for Querying?

[jcgood25]

Raman,

What are the project requirements that would need an iGrid showing 10,000 records!? I would imagine that the user patience to wait for this resultset will not match up very well against the time it takes to return that volume of data, especially if this is the default behavior of the page when it loads. I can only speculate that there would be a better way to give the users access to filter the specific data they really need, not just all the records in the database table itself. This would reduce the excessive strain on many of the components: client browser, xMII server, SQLServer...

Run the same query in Query Analyzer (or whatever native query tool you would typically use) and see if it warns you of non-unicode characters in the dataset, maybe you'll get information telling you which record or what character it is. We have seen this a few times recently with Oracle tables having invalid characters. If it is a particular record(s) you could reduce your RowCount and adjust your query to filter certain ranges of the data to see if you can pinpoint the set of data that is causing the problem. Enterprise Manager and/or Query Analyzer will probably be your best help in narrowing down this problem.

Regards,

Jeremy

[Former Member]

Jeremy,

This was the project requirement.Anyways we have changed the solution and now we are fetching 500 records at one time.

This has solved the problem.

Thanks for the input.I will analyze the problem using SQL Query analyzer and share the results.

Regards

Raman