[TD 5.1 SP6] ORA-24324 after fetch a lot of columns

[ILYA]

Hi!

I have a table with many columns (more then 30). I populate it with SalTblPopulate. Data loads normally. Then I wait couple of minutes and populate again - everything is correct again. I wait again, and populating I've got "ORA-24324 - service handle not initialized", and then "ORA-24323 - value not allowed". I tried to use less then 30 columns and with 28 column I don't see ORA-24324 error. What can it be?

[Jeff Luther]

Try adding a COMMIT after the populate is done. Be sure the table window's cache is Discardable=No and Max Rows = 128000 or something large.

[ILYA]

Doesn't work, Jeff. I added COMMIT and Discardable=No and Max Rows = 128000 - no effect. But I can't understand why should I have to use COMMIT after the populate.

[Jeff Luther]

why should I have to use COMMIT after the populate

On the off-chance that there were any locks left on the DB after the populate was done. And if so, that might account for the server error next time you tried to populate.

[Charlie]

Hello,

Just for the heck of it, have you tried calling SalTblReset( hWndTbl ) before each SalTblPopulate( ... ) call ?

[ILYA]

Yes, SalTblReset is calling before SalTblPopulate

[Charlie]

A few questions:

• What version of Oracle (database and client) are you using?
• Native connection or OleDB ?
• Is it the exact same query for each SalTblPopulate?
• Are your table window columns static or dynamically created?
• Between calls to SalTblPopulate and during SalTblPopulate processing (i.e. SAM_Fetch* message processing), do you perform any other database activity?

[ILYA]

• Oracle Dtabase 10g EE 10.2.0.1.0 / Oracle client 10.2.0.1.0
• Native connection (sqlora32.dll 5.1.6.8873)
• I do different queries for SalTblPopulate, but have a bug for just one
• Columns are dynamically created
• No database activity between SalTblPopulate and during SalTblPopulate processing

[Charlie]

G'day,

I'm thinking that you're getting a misleading error (i.e. ORA-24324 has nothing to do with your problem.)

Being a betting man, I'm guessing that the problem has to do with one specific column that works sometimes and doesn't work in one or more other cases because of some db column value.

By trial and error, can you isolate the problem to one or more specific columns? (i.e. by commenting and uncommenting different batches of columns.)