cancel
Showing results for 
Search instead for 
Did you mean: 

SYSERROR -9042 BD Append not allowed

Former Member
0 Kudos

Hi

We installed a MaxDB Database Version 7.6.4.7 on AIX 5.3. for a non _SAP application

I found the following message in the file knldiag.

2008-07-16 14:20:02 6940 11007 COMMUNIC wait for connection T261

2008-07-16 14:20:02 6940 11561 COMMUNIC Connected T261 dehanu33 162842

2008-07-16 14:20:02 6940 11560 COMMUNIC Releasing T211

2008-07-16 14:20:02 2314 11561 COMMUNIC Connecting T239 dehanu33 222848

2008-07-16 14:20:02 6940 12929 TASKING Task T239 started

2008-07-16 14:20:02 6940 11007 COMMUNIC wait for connection T239

2008-07-16 14:20:02 6940 11561 COMMUNIC Connected T239 dehanu33 222848

2008-07-16 14:20:03 7197 11560 COMMUNIC Releasing T316

2008-07-16 14:20:03 2314 11561 COMMUNIC Connecting T292 dehanu33 284338

2008-07-16 14:20:03 7197 12929 TASKING Task T292 started

2008-07-16 14:20:03 7197 11007 COMMUNIC wait for connection T292

2008-07-16 14:20:03 7197 11561 COMMUNIC Connected T292 dehanu33 284338

2008-07-16 14:20:03 6940 12827 COMMUNIC wait for connection T209

2008-07-16 14:20:03 6940 12827 COMMUNIC wait for connection T235

2008-07-16 14:20:05 7197 ERR 51080 SYSERROR -9042 BD Append not allowed

2008-07-16 14:20:06 7197 ERR 51080 SYSERROR -9042 BD Append not allowed

2008-07-16 14:20:06 7197 ERR 51080 SYSERROR -9042 BD Append not allowed

2008-07-16 14:20:06 7197 ERR 51080 SYSERROR -9042 BD Append not allowed

2008-07-16 14:20:06 7197 ERR 51080 SYSERROR -9042 BD Append not allowed

2008-07-16 14:20:06 7197 ERR 51080 SYSERROR -9042 BD Append not allowed

2008-07-16 14:20:06 7197 ERR 51080 SYSERROR -9042 BD Append not allowed

2008-07-16 14:20:06 7197 ERR 51080 SYSERROR -9042 BD Append not allowed

2008-07-16 14:20:06 7197 ERR 51080 SYSERROR -9042 BD Append not allowed

2008-07-16 14:20:06 7197 ERR 51080 SYSERROR -9042 BD Append not allowed

2008-07-16 14:20:06 7197 ERR 51080 SYSERROR -9042 BD Append not allowed

2008-07-16 14:20:06 7197 ERR 51080 SYSERROR -9042 BD Append not allowed

2008-07-16 14:20:07 6940 WNG 11824 COMMUNIC Releasing T233 command timeout

2008-07-16 14:20:07 6940 12827 COMMUNIC wait for connection T233

2008-07-16 14:20:09 2314 11561 COMMUNIC Connecting T246 dehanu33 151936

2008-07-16 14:20:09 6940 12929 TASKING Task T246 started

2008-07-16 14:20:09 6940 11007 COMMUNIC wait for connection T246

2008-07-16 14:20:09 6940 11561 COMMUNIC Connected T246 dehanu33 151936

2008-07-16 14:20:09 2057 WNG 11840 COMMUNIC Killing T309 for died apid 326254

2008-07-16 14:20:09 7197 WNG 11804 COMMUNIC application dead for T309

2008-07-16 14:20:09 7197 WNG 11824 COMMUNIC Releasing T309 connection aborted

2008-07-16 14:20:09 7197 12827 COMMUNIC wait for connection T309

2008-07-16 14:20:10 6940 11560 COMMUNIC Releasing T226

2008-07-16 14:20:10 2314 11561 COMMUNIC Connecting T206 dehanu33 282008

2008-07-16 14:20:10 6940 12929 TASKING Task T206 started

2008-07-16 14:20:10 6940 11007 COMMUNIC wait for connection T206

2008-07-16 14:20:10 6940 11561 COMMUNIC Connected T206 dehanu33 282008

2008-07-16 14:20:11 6940 11560 COMMUNIC Releasing T206

2008-07-16 14:20:11 6940 12929 TASKING Task T216 started

2008-07-16 14:20:11 2314 11561 COMMUNIC Connecting T216 dehanu33 282008

2008-07-16 14:20:11 6940 11007 COMMUNIC wait for connection T216

2008-07-16 14:20:11 6940 11561 COMMUNIC Connected T216 dehanu33 282008

2008-07-16 14:20:11 6940 11560 COMMUNIC Releasing T216

2008-07-16 14:20:11 2314 11561 COMMUNIC Connecting T338 dehanu33 282008

2008-07-16 14:20:11 7197 12929 TASKING Task T338 started

I found no explanation for this message.

Thank you

Harald

Accepted Solutions (0)

Answers (1)

Answers (1)

roland_mallmann
Advisor
Advisor
0 Kudos

Hi,

can you maybe find out which exact (incl. variables) SQL statement leads to this -9042 error?

If possible, please also show us an explain of the SQL statement, so we can see what kind of strategy the Optimizer is trying to use.

Edit: is it reproducable?

Regards,

Roland

Former Member
0 Kudos

Hi Roland,

how can I discover the SQL statement? Which trace database trace is possible? We got the error again and again.

Regards

Harald

roland_mallmann
Advisor
Advisor
0 Kudos

Hi,

so I take you don't have any SQL logging from the application side, so you're bound to two options:

a) database trace (also called vtrace) and

b) interface trace (you're probably using JDBC)

Option a - vtrace

Easiest tool to use would be either Database Manager GUI (DBMGUI) or Database Studio. Switch on the database trace with the following options: Default + Order and make sure you also specify to stop the vtrace at error nr. -9042.

Option b - JDBC trace

read [this|http://maxdb.sap.com/doc/7_7/46/7bc392e97150d1e10000000a155369/content.htm] and use the same stop on error functionality here.

If you need more specifics, let me know.

Regards,

Roland

Former Member
0 Kudos

Hi Roland,

I create a trace with the Error 9042 and with me colleague we found only one join between the table wb and Tranziel .

Here is a part of the kerneltrace.

1544.2027 page 1545)

PACKET: ascii, normal_swap, 70500-CPC (1 segment, len: 40)

ok / RETURN SEGMENT 1 (0 parts, len: 40)

commit_fc, sqlstate: '00000'

(2889.7714 page 2890)

PACKET: ascii, normal_swap, 70500-CPC (1 segment, len: 120)

execute SEGMENT 1 (2 parts, len: 120)

internal, user_cmd

parsid PART (1 argument, size: 126760)

mess_type: sharedSQLParseid

partbuf

pos: 1 2 3 4 5 6 7 8 9 10 11 12

dec: 0 46 61232 0 0 25 1 84 0 0 0

hex: 00 2E 3D E8 00 00 19 01 54 00 00 00

chr: . = T

data PART (1 argument, size: 126728)

partbuf BUFFER FROM 1 TO 25

pos: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

dec: 0194 82 32 85 76 32 48 56 51 57 49 53 54 53 51 54 0128 0

hex: 00 C2 52 20 55 4C 20 30 38 33 39 31 35 36 35 33 36 00 80 00

chr: R U L 0 8 3 9 1 5 6 5 3 6

pos: 21 22 23 24 25

dec: 0 0 0193 48

hex: 00 00 00 C1 30

chr: 0

>AccessOp idnil/18219 select last_join_op TABID 0-0648 TabNo 002

>AccessOp idnil/18219 select frst_join_op TABID 0-065D TabNo 001

>AccessOp Open() TabNo 001

>b02first_ql key(22):

20554C20 30383339 31353635 33360080 00000000 C252

' UL 0839156536.......R'

b02first_ql root 13930; *** no_next_record ***

>AccessOp Open( keys ) TabNo 002

>b02first_ql key(6): ' N8110'

b02first_ql root 87995; ok

>AccessOp Close() TabNo 002

>AccessOp Close() TabNo 001

>b07cappend key(60):

00C25220 554C00C1 30203038 33393135 36353336 20303020

20FF0000 00000000 00000000 FF000000 20493030 3130204E

38313130 00C48110 00000001

'..R UL..0 0839156536 00 ............... I0010 N8110......'

'..'

b07cappend root 104461; *** append_not_allowed ***

AccessOp idnil/18219 *** append_not_allowed *** TabNo 002

AccessOp idnil/18219 *** append_not_allowed *** TabNo 002

AccessOp idnil/18219 *** append_not_allowed *** TabNo 001

AccessOp idnil/18219 *** append_not_allowed *** TabNo 001

KB05 idnil/18219 *** no_next_record ***

>b01empty Temp; fileTfnNo = 0; ttfnInto

session: 0; fid = 8

fn: 1A00 8000000000000677 000000000008

b01empty root 104461; ok

TOO MANY PACKETS

UNKNOWN: 17 1

UNKNOWN: 17 1

00000100 00000000 00000000 00006000 00000000 01000102 53393034

32DCAE00 00000100 00000000 F4000000 00000000 00000006 00000100

00000000 00002300 01FE9053 79737465 6D206572 726F723A 20424420

41707065 6E64206E 6F742061 6C6C6F77 6564FFFF FFFFFFFF 2E2E2E2E

2E2E2E2E 2E2E2E2E 2E2E2E2E 2E2E2E2E 2E2E2E

'..............`.........S9042.................................#..'

'..System error: BD Append not allowed............................'

'.'

===== T212 ===== idnil =============================2890.628 page 2891

(2890.628 page 2891)

PACKET: ascii, normal_swap, 70500-CPC (1 segment, len: 536)

execute SEGMENT 1 (2 parts, len: 536)

internal, user_cmd

parsid PART (1 argument, size: 126760)

mess_type: sharedSQLParseid

partbuf

pos: 1 2 3 4 5 6 7 8 9 10 11 12

dec: 0 46110118 0 0 58 1 84 0 0 0

hex: 00 2E 6E 76 00 00 3A 01 54 00 00 00

chr: . n v : T

data PART (1 argument, size: 126728)

partbuf BUFFER FROM 1 TO 444

pos: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

dec: 32 85 76 32 48 56 51 57 49 53 54 53 51 55 0128 0 0 0 0

hex: 20 55 4C 20 30 38 33 39 31 35 36 35 33 37 00 80 00 00 00 00

chr: U L 0 8 3 9 1 5 6 5 3 7

pos: 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40

dec:194 82 0193 48 32 50 32 49 48 32 85 76 32 48 56 51 57 49 53

hex: C2 52 00 C1 30 20 32 20 31 30 20 55 4C 20 30 38 33 39 31 35

chr: R 0 2 1 0 U L 0 8 3 9 1 5

pos: 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60

dec: 54 53 51 55 32 48 48 32 32 32 54 54 56 53 55255 0194 82 32

hex: 36 35 33 37 20 30 30 20 20 20 36 36 38 35 37 FF 00 C2 52 20

chr: 6 5 3 7 0 0 6 6 8 5 7 R

pos: 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80

dec: 49 32 48 32 32 32255 0128 0255 32 32 48255 49 32 32 32 32

hex: 31 20 30 20 20 20 FF 00 80 00 FF 20 20 30 FF 31 20 20 20 20

chr: 1 0 0 1

pos: 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99

dec: 50 48 48 56 48 57 50 50 49 52 50 55 52 55255 32255 32 32 32

hex: 32 30 30 38 30 39 32 32 31 34 32 37 34 37 FF 20 FF 20 20 20

chr: 2 0 0 8 0 9 2 2 1 4 2 7 4 7

pos:101 103 105 107 109 111 113 115 117 119

dec: 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32

hex: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20

chr:

... 121 TO 140

pos:141 143 145 147 149 151 153 155 157 159

dec: 32 32 32 32 32 32 32255 48 49 32255 32 32 32 32 73 48 48 49

hex: 20 20 20 20 20 20 20 FF 30 31 20 FF 20 20 20 20 49 30 30 31

chr: 0 1 I 0 0 1

pos:161 163 165 167 169 171 173 175 177 179

dec: 48 32 48 49 84 76 66 48 51 48 50 48 32 78 56 49 49 48 32 48

hex: 30 20 30 31 54 4C 42 30 33 30 32 30 20 4E 38 31 31 30 20 30

chr: 0 0 1 T L B 0 3 0 2 0 N 8 1 1 0 0

pos:181 183 185 187 189 191 193 195 197 199

dec: 49 75 82 87 87 48 54 52 67 0128 0 0 0 0 0 0128 0 0

hex: 31 4B 52 57 57 30 36 34 43 00 80 00 00 00 00 00 00 80 00 00

chr: 1 K R W W 0 6 4 C

pos:201 203 205 207 209 211 213 215 217 219

dec: 0 0 0 0128 0 0 0 0 0 0193 64 0 0 0 0 0128 0

hex: 00 00 00 00 80 00 00 00 00 00 00 C1 40 00 00 00 00 00 80 00

chr: @

pos:221 223 225 227 229 231 233 235 237 239

dec: 0 0 0 0 0128 0 0 0 0 0 0194 32 0 0193 64 0 32

hex: 00 00 00 00 00 80 00 00 00 00 00 00 C2 20 00 00 C1 40 00 20

chr: @

pos:241 243 245 247 249 251 253 255 257 259

dec: 48 49 32 32 32 32 48 54 48 50 53 32 49 55 54 55 5

We assume that these statements create the error BD append not allowed. Is this possible? the tableid 0648 is tranziel and 65D is WB.

EXEC SQL DECLARE curWbTz CURSOR for

SELECT wb.mandant,

wb.wb_status,

wb.wb_art,

wb.lb_nummer,

wb.lb_nummer_fa,

wb.ls_nr,

wb.pa_nr,

wb.sektion_quelle,

wb.sektion_ziel,

tz.t_ziel,

MAX(wb.prioritaet),

MIN(wb.time_neuanlage),

SUM(menge2_soll - menge2_ist),

SUM((menge2_soll - menge2_ist) / anz_box_stp )

FROM wb, tranziel tz

WHERE mandant = :Mandant

AND wb.wb_status >= :wbStatusVon

AND wb.wb_status <= :wbStatusBis

AND tz.sektion = wb.sektion_ziel

AND wb.wb_art not like 'E%'

AND ( ( wb_art = 'WA' AND

TIMESTAMP < ( :jh & abfahrttag & abfahrtzeit ) ) OR

wb_art <> 'WA'

)

GROUP BY wb.mandant, wb.wb_status, wb.wb_art, wb.lb_nummer, wb.lb_nummer_fa,

wb.ls_nr, wb.pa_nr, wb.sektion_quelle, wb.sektion_ziel, tz.t_ziel

ORDER BY MAX(wb.prioritaet) desc, MIN(abfahrttag), MIN(abfahrtzeit), MIN(wb.time_neuanlage),

wb.ls_nr, wb.lb_nummer;

bzw. als Single Select:

EXEC SQL

SELECT wb.mandant,

wb.wb_status,

wb.wb_art,

wb.lb_nummer,

wb.lb_nummer_fa,

wb.ls_nr,

wb.pa_nr,

wb.sektion_quelle,

wb.sektion_ziel,

tz.t_ziel,

max(wb.prioritaet),

min(wb.time_neuanlage),

sum(menge2_soll - menge2_ist),

sum((menge2_soll - menge2_ist) / anz_box_stp )

INTO :wbtz :iwbtz

FROM wb, tranziel tz

WHERE mandant = :wb.MANDANT

AND wb.wb_art = :wb.WB_ART

AND wb.wb_nummer = :wb.WB_NUMMER

AND wb.wb_nummer_fa= :wb.WB_NUMMER_FA

AND wb.wb_status = :wbStatusLesen

AND tz.sektion = wb.sektion_ziel

GROUP BY wb.mandant, wb.wb_art, wb.wb_status, wb.lb_nummer, wb.lb_nummer_fa,

wb.ls_nr, wb.pa_nr, wb.sektion_quelle, wb.sektion_ziel, tz.t_ziel;

Best regards

Harald Kühne

roland_mallmann
Advisor
Advisor
0 Kudos

Hi Harald,

can you reproduce the error using SQL Studio or DB Studio (by issueing the SQL statements from your last answer against the DB)?

Kind regards,

Roland

Former Member
0 Kudos

Hi Roland,

we couldn't reproduce the error by starting the SQL statement with the SQl-Studio.

And now? I have no idea.

Best Regards

Harald

roland_mallmann
Advisor
Advisor
0 Kudos

Hi Harald,

I'll discuss your issue with the relevant developer and report back to you.

Regards,

Roland

roland_mallmann
Advisor
Advisor
0 Kudos

Hi Harald,

I just tried to send you a mail, but it bounced.

We need the full binary vtrace file of the reproduction of the error to be able to retrieve more information.

Please upload it to the following container:

[SAPMats upload container|https://sapmats-de.sap-ag.de/upload/index.cgi?id=VUDSFI3PBTJ10VDR1VUBXEFDJ3GDHPUFN3V7WJLSU5BFBDWPGV]

Thanks & regards,

Roland