[ Oracle 10g ] - XMLDB dans un trigger ORA-00600

:alerte: bonjour à tous !! :alerte:

voila un problème etrange que je n'arrive pas a expliquer... si quelqu'un a une idée...

Code:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
 
CREATE TABLE FIELDS (	
   	ID 		NUMBER, 
	NOM 	VARCHAR2(25 CHAR), 
	ACL_DEF XMLTYPE, 
	COD_HOP VARCHAR2(5 CHAR))
	XMLTYPE ACL_DEF STORE AS OBJECT RELATIONAL
		XMLSCHEMA "http://XXXX/projet/YYY/schema/aclfields.xsd"
		ELEMENT "FIELDS"
/
 
ALTER TABLE FIELDS ADD constraint VALIDATE_FIELDS CHECK (XMLIsValid(ACL_DEF)=1)
/
 
 
 
 
-- trigger
create or replace trigger TG_INITFIELDS
before insert on "FIELDS"
for each row 
declare
	template CLOB ;
begin
	SELECT extract(res, '/Resource/Contents/*').getclobval()   INTO template FROM RESOURCE_VIEW WHERE EQUALS_PATH(res,'/home/D47/xml_templates/xml_templates_fields.xml') > 0 ;
	if inserting then
		if :NEW."ID" is null then
			select SQ_FIELDS.nextval INTO :NEW."ID" from dual;
			select xmltype(template) INTO :NEW."ACL_DEF" from dual ;
		end if;
	end if;
end;
/
SHOW ERRORS;
/
 
 
SQL> insert into fields values(null,'sample',null,'00087') ;
insert into fields values(null,'sample',null,'00087')
                    *
ERREUR a la ligne 1 :
ORA-00600: code d'erreur interne, arguments : [qmxtcUMkProcessImage:invtype],
[], [], [], [], [], [], []
ORA-04088: erreur lors d'execution du declencheur 'D47.TG_INITFIELDS'

quelqu'un a t il déjà vu cela....

merci d'avance.

D'emblée rien que le fait que vous ayez nommé votre table avec un mot clé du langage SQL (FIELDS) ne doit pas aider :roll:
Modifiez le nom de votre table, cela éliminera déjà cette hypothèse et vous évitera des ennuis inimaginables.

bonne remarque...:oops:
pas fais gaffe avec toutes les complications XMLDB :D

mais ca ne resoud pas le problème... toujours ora-00600.....

en faite j'ai trouver cela

Code:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
 
Bug No. 	4532970
Filed 	03-AUG-2005 	Updated 	15-SEP-2006
Product 	Oracle Server - Enterprise Edition 	Product Version 	10.1.0.4
Platform 	Microsoft Windows (32-bit) 	Platform Version 	No Data
Database Version 	10.1.0.4 	Affects Platforms 	Generic
Severity 	Minimal Loss of Service 	Status 	Code Bug (Response/Resolution)
Base Bug 	N/A 	Fixed in Product Version 	No Data
 
Problem statement:
 
ORA-600:[QMXTCFLUSHTRXOB:HSH] BY DBMS_XDB.CREATERESOURCE()
 
 
 
*** 08/03/05 01:30 am ***
 
.
 
.
 
=========================
 
PROBLEM:
 
.
 
1. Clear description of the problem encountered:
 
When a trigger exists on a schema based table then the
 
procedure DBMS_XDB.CreateResource() fails with error
 
ORA-00600: internal error code, arguments: [qmxtcFlushTrxob:hsh]
 
when trying to upload an XML file
 
.
 
2. Pertinent configuration information (MTS/OPS/distributed/etc)
 
no MTS, RAC
 
.
 
3. Indication of the frequency and predictability of the problem
 
Problem is reproducable
 
.
 
4. Technical impact on the customer. Include persistent after effects.
 
Functionality is needed for application development
 
.
 
=========================
 
DIAGNOSTIC ANALYSIS:
 
.
 
- XML schemas, XML file is valid, verifyed in XMLspy
 
- table is created during schema registration
 
- before insert trigger on table for validating the XML file
 
.
 
declare
 
b boolean;
 
begin
 
b := DBMS_XDB.CreateResource ('/public/xml/PROBEReport-01.xml',
 
bfilename(directory => 'DIR_TEMP', filename => 'PROBEReport-01.xml'));
 
end;
 
/
 
.
 
declare
 
*
 
ERROR at line 1:
 
ORA-00600: internal error code, arguments: [qmxtcFlushTrxob:hsh], [], [], [],
 
[], [], [], []
 
ORA-04088: error during execution of trigger
 
'SR4549419_992.VALIDATE_PROBE_REPORT'
 
ORA-06512: at "XDB.DBMS_XDB", line 145
 
ORA-06512: at "XDB.DBMS_XDB", line 186
 
ORA-06512: at line 4
 
.
 
When connected as sysdba or no trigger is defined the procedure will be
 
successfully completed.
 
.
 
=========================
 
WORKAROUND:
 
Allways upload XML resources as sysdba is not a workaround
 
.
 
=========================
 
RELATED BUGS:
 
10.1.0.2)
 
.
 
=========================
 
REPRODUCIBILITY:
 
.
 
1. State if the problem is reproducible; indicate where and predictability
 
Error is reproducable
 
.
 
2. List the versions in which the problem has reproduced
 
10.1.0.4 at SUN Solaris 64-bit
 
10.1.0.4 at MS Windows 2000
 
.
 
3. List any versions in which the problem has not reproduced
 
none
 
.
 
=========================
 
TESTCASE:
 
.
 
- Register XML schemas Metadata.xsd, Persistence.xsd and PROBEReport.xsd
 
.
 
begin
 
dbms_xmlschema.registerSchema(schemaURL
 
schemaDoc => xdbURIType('/public/schemas/Persistence.xsd').getclob(),
 
local => TRUE,genTypes => TRUE,genBean => FALSE,genTables => TRUE);
 
dbms_xmlschema.registerSchema(schemaURL
 
schemaDoc => xdbURIType('/public/schemas/Metadata.xsd').getclob(),
 
local => TRUE,genTypes => TRUE,genBean => FALSE,genTables => TRUE);
 
dbms_xmlschema.registerSchema(schemaURL
 
schemaDoc => xdbURIType('/public/schemas/PROBEReport.xsd').getclob(),
 
local => TRUE,genTypes => TRUE,genBean => FALSE,genTables => TRUE);
 
end;
 
/
 
.
 
.
 
- Create directory 'DIR_TEMP' where XML file PROBEReport-01.xml is located
 
.
 
.
 
- Create trigger
 
.
 
create or replace trigger VALIDATE_PROBE_REPORT
 
before insert on PROBE_REPORT
 
for each row
 
begin
 
if (:new.object_value is not null)
 
then :new.object_value.schemavalidate();
 
end if;
 
end;
 
/
 
.
 
.
 
- Run procedure
 
.
 
declare
 
b boolean;
 
begin
 
b := DBMS_XDB.CreateResource ('/public/xml/PROBEReport-01.xml',
 
bfilename(directory => 'DIR_TEMP', filename => 'PROBEReport-01.xml'));
 
end;
 
/
 
.
 
.
 
========================
 
STACK TRACE:
 
.
 
Summary Stack:
 
~~~~~~~~~~~~~~
 
ksedmp
 
kgerinv
 
kgeasnmierr
 
qmxtcFlushTransientXob
 
qmxiStoreOutLineXob
 
qmxiCreateCollImg
 
qmxiCreateCollImage
 
qmxiStoreArrayImage
 
qmxiWriteXobToImageInternal
 
qmxiCreateCollImg
 
qmxiCreateCollImage
 
qmxiStoreArrayImage
 
qmxiWriteXobToImageInternal
 
qmxiCreateCollImg
 
qmxiCreateCollImage
 
qmxiStoreArrayImage
 
qmxiWriteXobToImageInternal
 
qmxiStoreXobElement
 
qmxiStoreElement
 
qmxiWriteXobToImageInternal
 
qmxiStoreXobElement
 
qmxiStoreElement
 
qmxiWriteXobToImageInternal
 
qmxiWriteXobToImageWithHeap
 
qmxiWriteXobToImage
 
qmxtcUMkProcessImage
 
qmxtcUnEvalMkXML
 
kxtosba
 
psdsbat
 
pevm_SBVAR
 
pfrinstr_SBVAR
 
pfrrun_no_tool
 
pfrrun
 
plsql_run
 
peicnt
 
kkxtexe
 
kxtex1
 
rpiswu2
 
kxtexe
 
insbrp
 
insrow
 
insdrv
 
inscovexe
 
insExecStmtExecIniEngine
 
insexe
 
ngine
 
opiexe
 
opiall0
 
opikpr
 
opiodr
 
rpidrus
 
skgmstack
 
rpidru
 
rpiswu2
 
kprball
 
qmskInsertXmlType
 
qmskStoreXobWithImage
 
qmskStoreXob
 
qmeSaveContents
 
qmePreSave
 
qmtEventFire
 
qmxiWriteXobToImageInternal
 
qmxiWriteXobToImageWithHeap
 
qmxtgGetOpqImageFromXob
 
qmskStoreXobWithImage
 
qmskStoreXob
 
qmeInsertResRow
 
qmeInsertRes
 
qmeLinkInternal
 
qmeCreOrBindRes
 
qmeCreateRes
 
qm_create_res_and_cts
 
qmpxCreateFromBlob
 
spefcifa
 
spefmccallstd
 
peftrusted
 
psdexsp
 
rpiswu2
 
psdextp
 
pefccal
 
pefcal
 
pevm_FCAL
 
pfrinstr_FCAL
 
pfrrun_no_tool
 
pfrrun
 
plsql_run
 
peicnt
 
kkxexe
 
opiexe
 
kpoal8
 
opiodr
 
ttcpip
 
opitsk
 
opiino
 
opiodr
 
opidrv
 
sou2o
 
main
 
start
 
*** 08/03/05 01:38 am ***
 
*** 08/03/05 01:38 am *** (CHG: Sta-&gt;16)
 
*** 08/03/05 03:38 am *** (CHG: Asg-&gt;NEW OWNER)
 
*** 08/03/05 03:38 am ***
 
*** 08/03/05 04:25 am ***
 
.
 
if I use the following code to create the trigger
 
then it works OK:
 
create or replace trigger validate_probe_report
 
before insert on probe_report
 
for each row
 
declare
 
newxml xmltype;
 
begin
 
-- if (:new.object_value is not null)
 
-- then :new.object_value.schemavalidate();
 
-- end if;
 
newxml := :new.sys_nc_rowinfo$;
 
xmltype.schemavalidate(newxml);
 
end;
 
/
 
.
 
*** 08/03/05 04:26 am *** (CHG: Sta-&gt;11)
 
*** 08/03/05 04:26 am ***
 
*** 08/03/05 05:47 am *** (CHG: Asg-&gt;NEW OWNER)
 
*** 08/09/05 11:16 pm *** (CHG: Asg-&gt;NEW OWNER)
 
*** 08/09/05 11:16 pm ***
 
via the ST Bug Assignment Tool
 
*** 08/09/05 11:52 pm *** (CHG: DevPri-&gt;2)
 
*** 08/23/05 11:34 pm *** (CHG: Confirmed Flag-&gt;Y)
 
*** 08/23/05 11:34 pm ***
 
*** 08/23/05 11:57 pm ***
 
*** 09/21/05 09:54 am *** (CHG: Sta-&gt;16 Asg-&gt;NEW OWNER)
 
*** 09/21/05 09:54 am ***
 
*** 09/22/05 04:17 am *** (CHG: Sta-&gt;11 Asg-&gt;NEW OWNER)
 
*** 09/22/05 04:17 am ***
 
*** 11/08/05 05:25 am *** (CHG: Pri-&gt;3)
 
*** 11/08/05 05:25 am ***
 
*** 04/27/06 01:27 pm *** (CHG: SubComp-&gt;RVIEW)
 
*** 09/15/06 03:01 am *** (CHG: Asg-&gt;NEW OWNER)
 
.

un titre plus parlant serait le bien venu :)

bon c'est résolu !!

Citation:

METALINK dit : I'll keep you informed, as soon as I have filed the bug. Can you please let me know, if the explicitly inserting the value from the xml_file in to the ACL_DEF column is a workaround for you.

la solution proposé en attendant la résolution du bug coté oracle

Enregistrer tous les schemas (noeud) en MAJUSCULE
Modification du trigger (voir plus bas)
Code:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 create or replace trigger TG_INITFIELDS before insert on D47FIELDS for each row declare template CLOB ; begin SELECT extract(res, '/Resource/Contents/*').getclobval() INTO template FROM RESOURCE_VIEW WHERE EQUALS_PATH(res,'/home/D47/xml_templates/xml_templates_fields.xml') > 0 ; if inserting then if :NEW.ID is null then select SQ_FIELDS.nextval INTO :NEW.ID from dual; end if ; if :NEW.ACL_DEF is null then select xmltype(template).createschemabasedxml('http://XXX/projet/YYY/schema/aclfields.xsd') INTO :NEW.ACL_DEF from dual ; end if; end if; end; /