Hi Marco,

i have a question, i don't know if this is the correct place to ask it.

We have several programs writen in delphi using DOA. In the last year we discovered that if the program crashes due to the fact that there is a field missing. The program starts to generate "minidump" files. They have names like:

H_minidump_default_pid_8784_tid_x1BBC_2012_12_27_13_41_38.dmp

the fist character is often a strange ascii, not a normal character.

The problem is that the program does not end. It disappears from the taskbar. Taskmanger shows it in memory. The program keeps on generating minidump files every second until the process is killed in memory.

I can't discover what causes this. We had this in our delphi7 versions last year. That disapeared when we upgraded to a newer doa version 4.1. Know we have te same problem in delphixe2 using the 4.1 doa version. This is probably an coincedence.

Do you have any idea? Can you point me in the right direction?

Kind regards

Ruud

Extra info:

It happens when a dataset is activated that contains en sql where a field is missing. It results in an ora-00904 invalid id. It happens before "application.run" in the project file. If the same happens after application.run during normal program execution than the error is handled correct.

It has something to do with some windows proces. Before our application shows its (doa)error dialog. Windows shows a dialog. With the choice to close the program or to debug. If i choose close then the normal dialog is shown het the ora error.

The solution in this case is of cours ad the field, but we already had thousends of minidump file because a customer dit not run as script during an update....

Hope you can help.

Kind regards

Ruud

My guess is that you have a data module or auto-created form with a TOracleDataSet instance with Active = True. The missing field will lead to an exception when Active is set to True when instantiating the form/data module. To prevent this you can perhaps activate the dataset in a more controlled manner, after the application is completely initialized.

You can set TOracleDataSet.DesignActivation to True to enable active datasets at design-time, but disable implicit activation at run-time.

Hi Marco

thanks for looking in to this. I am setting the dataset active to true myself. And you are right, i can do this later.... But sometimes the same happens after a long time of inactivity. An oracle error occurs and the generations of minidump files starts.

I don't understand what mechanisme causes the generation of these files. Is it a feature comming with delphi? Is it doa? Is it oracle? Windows? Do you have any idea?

More important can i turn it off? I don't want to fill the harddisk at a customer site with these files.

any help is apreciated,

thanks in advance.

Ruud

Unfortunately I have no real clue what could cause the minidump.

Hi Marco,

i scanned some dlls en found in orageneric11.dll':

"MiniDumpWriteDump Error orrured %d %s_%s_pid_%d_tid_x%X_%d_%d_%d_%d_%d_%d_"

This is the exact patern as found in the the minidump file name.
We communicate thrue doa to oracle. Can you help me?
Or should i contact oracle to ask what could cause this?

Kind Regards

Ruud

The orageneric11.dll is a library from your Oracle Client installation, so you could contact Oracle Support, but the error message does not seem very useful.

Hi Ruudbern,

I have the same problem as you have.
Did you find the solution of your problem ?
How to disabled the generation of these minidump on Oracle ?

Regards,

Chareon.

Hi,

upgrade oracle client to 11.2.0.3 fixed the problem.

Regards

Ruud