Kbase P3529: Error 52 is returned when updating record using Oracle DataS
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
05/08/2003 |
|
Status: Unverified
FACT(s) (Environment):
Progress 9.1C
FACT(s) (Environment):
Progress 9.1D
FACT(s) (Environment):
Windows NT 32 Intel/Windows 2000
SYMPTOM(s):
Error 52 is returned when updating record
using Oracle DataServer
SYSTEM ERROR : fmx -- bad data type.(52)
Dr Watson is generated
The Stack Trace Generated :
Exception code: E0000003
Fault address: 77E8F142 01:0000E142 C:\WINNT\system32\KERNEL32.dll
Registers:
EAX:0012F810
EBX:00000000
ECX:00000000
EDX:77B33488
ESI:00000000
EDI:00000000
CS:EIP:001B:77E8F142
SS:ESP:0023:0012F808 EBP:0012F860
DS:0023 ES:0023 FS:0038 GS:0000
Flags:00000246
Call Stack:
Address Frame
77E8F142 0012F860 RaiseException+51
103924D3 0012F88C utcore+43
1000BEB7 0012F8A0 drexit+3B6
10009AB8 0012F8C8 msgout+2E0
1000965E 0012FC7C msgn+A2
10068A8C 0012FCDC orafldx+36B
1000E28B 0012FCFC fdfldx+31
10181629 0012FD1C fmfldx+98
101B3FA2 0012FD48 rnSchAsgTrig+91
101B3C16 0012FD84 rnAsgTrigLoop+318
101B382C 0012FDB4 rnSetupAsgTrigs+263
1031B1A5 0012FDD4 rnupd_2+DD
10188BCB 0012FDE0 rninterpret+30
101F3CF8 0012FE64 umeDispatchEvent+125E
1010B5B9 0012FEC0 wwRunDispatcher+CD
102F966A 0012FECC iodispatch+87
1001A483 0012FED8 rnrq+C8
100063E5 0012FF08 drmain+20F
1004C6EB 0012FF1C ProStartup+5F
00401008 0012FF24 WinMain+8
00401148 0012FFC0 WinMainCRTStartup+134
77E97D08 0012FFF0 CreateProcessW+DA8
//=====================================================
PROGRESS stack trace as of Mon Jun 17 12:27:37 2002
//=====================================================
Exception code: E0000003
Fault address: 77E8F142 01:0000E142 C:\WINNT\system32\KERNEL32.dll
Registers:
EAX:0012F810
EBX:00000000
ECX:00000000
EDX:77B33488
ESI:00000000
EDI:00000000
CS:EIP:001B:77E8F142
SS:ESP:0023:0012F808 EBP:0012F860
DS:0023 ES:0023 FS:0038 GS:0000
Flags:00000246
Call Stack:
Address Frame
77E8F142 0012F860 RaiseException+51
103924D3 0012F88C utcore+43
1000BEB7 0012F8A0 drexit+3B6
10009AB8 0012F8C8 msgout+2E0
1000965E 0012FC7C msgn+A2
10068A8C 0012FCDC orafldx+36B
1000E28B 0012FCFC fdfldx+31
10181629 0012FD1C fmfldx+98
101B3FA2 0012FD48 rnSchAsgTrig+91
101B3C16 0012FD84 rnAsgTrigLoop+318
101B382C 0012FDB4 rnSetupAsgTrigs+263
1031B1A5 0012FDD4 rnupd_2+DD
10188BCB 0012FDE0 rninterpret+30
101F3CF8 0012FE64 umeDispatchEvent+125E
1010B5B9 0012FEC0 wwRunDispatcher+CD
102F966A 0012FECC iodispatch+87
1001A483 0012FED8 rnrq+C8
100063E5 0012FF08 drmain+20F
1004C6EB 0012FF1C ProStartup+5F
00401008 0012FF24 WinMain+8
00401148 0012FFC0 WinMainCRTStartup+134
77E97D08 0012FFF0 CreateProcessW+DA8
CAUSE:
Bug #20020622-001
FIX:
Upgrade to 9.1D and apply the latest Service Pack
FIX:
If upgrading to 9.1D is not an option, the following workaround can be used :
- Dump the related table using Data Administration
- Delete the Table from the Schema Holder
- Replad the .df into the Schema Holder