MaxDB - R3load Import Task failed with error: DBSL error 26 (db code 0):

[michael4sap]

Hello community,

we are executing an import with R3load. It´s a homogenous systemcopy with no changes except SLES Version.

During the import we always face this error in several packages:

Task failed with error: DBSL error 26 (db code 0):
A1 EGEN 002 ====================================================
A1 EDMP 010 Resource usage: GENERAL times: 1.421/ 0.824/ 0.037 1.4%/ 3.7%/ 1.9% real/usr/sys
A1 EDMP 010 Resource usage: DATABASE times: 76.502/ 3.595/ 0.332 74.4%/16.2%/17.3% real/usr/sys
A1 EDMP 010 Resource usage: FILE times: 24.912/ 17.832/ 1.552 24.2%/80.1%/80.8% real/usr/sys
A1 EDMP 009 Memory usage: 33/0 MB buffer/disk (1 reused buffers)

Our parameters during the copy are these one:

SLES 12 SP04 - Server has 80 GB RAM and 16 CPU´s (4 Sapdatas á 350GB with separate Filesystem)

SLES12 is running on ESXHost.

MaxDB: 7.9.09.05 Databasesize is 1,2 TB

36 Datafiles á 32GB

CacheMemorySize: 8019680 8k Pages (ca. 60GB)

MaxCPU: 14

MaxSQLLocks: 50.000.000

RequestTimeout: 28800 (8h)

MaxUserTaks: 250

Does anyone know what these exit code means ? We can´t find any information about this one.

Is there maybe a MaxDB Parameter which should increase also ?

I´m looking forward to your suggestions and the possible solution.

Thanks to everybody

Best regards

Michael

[michael4sap · Accepted solution]

The solution was found in the R3load parameters. To execute the import sucessfully we added these options:

"-nolog -c 50000 -force_repeat"

[michael4sap]

env-sidadm.txt

Hi Kaushik,

thanks for your response even it is saturday evening 🙂

Well until now there where some changes but let me answer your suggestions:

DBSL Version ist the newest one : DBSL: version 753 - So i think changing the version isn´t the right way, or ?

I uploaded the env of sidadm. As this is a new installation there is only the default.pfl which standard profiles provided by SWPM.

So the situation has changed now. After 450 Jobs were failed with DBSL 26 error the SWPM went into an error. So i retried the import step and gave the R3load option "-loadprocedure fast" so actually the SWPM is running and there are more completed jobs than failed but it is running very slow because R3load first deletes all entries of failed packages which were already done - this is a mechanism of the R3load.

And thats the point why i don´t want the execute the provided command of you to clean up memory

So thanks to your support - may you have a further suggestion ?

Best regards

Michael

[kaus19d]

Hi Michael Amrehn,

Could you please provide us your env values & DEFAULT.PFL values.

Next approach would be to update the DBSL library & clearing temporary cache memory by using below command,

echo 1 > /proc/sys/vm/drop_caches

Also please check the SAP Note 822271 & below,

https://help.sap.com/doc/saphelp_snc_uiaddon_10/1.0/en-US/4a/1df9315c171b40e10000000a42189c/content....

Thanks,

Kaushik