Backups MAXDB7,6 REDHat 5.2 64bits

[Former Member]

Hi guys

We have many problems with the backups to disk (disk USB attach to server)

-24988 SQL error (Backup_save "Data1" DATA RECOVERY); -903, HOST file I/O error

and we tray to confiigure the DB59 or DB13 and the error is

1. Connect. test with "dbmcli db_state" Successful

2. Connect. test with command mode "dbmrfc db_state" Successful

3. Connect. test with session mode "dbmrfc db_state" Unsuccessful

dbm_system_error

Name and Server : UMP - sapprod

DBMRFC Function : DBM_EXECUTE

Command : db_state

Error : DBM Error

Return Code : -16

Error Message : command timeout exceeded

4. Connect. test with "native SQL" ( UMP ) Successful

in these cases what isthe problem?

The version is MAX DB 7.6.03.9

SAP ECC 6.0

LINUX REDHAT 5.2 64 bits

Kernel patch 175

Thanks in advance

Alberto Gil

[roland_mallmann · Accepted solution]

Hi Alberto,

you seem to indicate you've got 2 issues:

1) backups

2) dbmrfc connection in session mode does not work

If not already done so, I highly suggest you open an official OSS message for both of your issues (i.e. two messages in total).

You did not specify enough information regarding the backup issue, but you might want to take a look at SAP note 1128989 regarding the second issue.

Regards,

Roland

[Former Member · Accepted solution]

Hi Rolan Thansk for you post

Yes, are two issues but i think they are interrelated.

In the case for DB50 and DB59 (test connection) the error is

3. Connect. test with session mode "dbmrfc db_state" Unsuccessful

dbm_system_error

Name and Server : UMQ - sapqas

DBMRFC Function : DBM_EXECUTE

Command : db_state

Error : DBM Error

Return Code : -16

Error Message : command timeout exceeded

The server DEV is running fine (this server is 32bits) but in QAS and PRD dont work (both are 64 bits). The notes spoke of this error is corrected with the SPS SAPKB70014, in my case the level is SAPKB70017.

Any idea for this?

Alberto G

[former_member229109 · Accepted solution]

Hello Alberto G,

1. SAP note 1128989 recommended to check the version of the dbmrfc

MAXDB tool installed on the application servers.

You could run 'sdbregview -l' and check the version of the 'Basis' package.

The reported problem could be due the fact that you are using the dbmrfc

version 7.6.03 build lower than 14 or 7.6.04 build lower than 06.

Please login to the application servers of QAS and PRD systems & run:

'sdbregview -l' => post the output.

2. As SAP customer you have option to create the OSS ticket and get SAP support. And the problems on your system could be discussed in more details with SAP support, we could logon via OSS to check your system.

Thank you and best regards, Natalia Khlopina

[Former Member · Accepted solution]

Hi Natalia

This is the print

sapprod:umpadm 2> sdbregview -l

Server Utilities /sapdb/programs 7.6.03.09 64 bit valid

DB Analyzer /sapdb/programs 7.6.03.09 64 bit valid

PCR 7300 /sapdb/programs 7.3.00.58 valid

PCR 7301 /sapdb/programs 7.3.01.22 valid

PCR 7500 /sapdb/programs 7.5.00.46 64 bit valid

SAP Utilities /sapdb/programs 7.6.03.09 64 bit valid

Redist Python /sapdb/programs 7.6.03.09 64 bit valid

Base /sapdb/programs 7.6.03.09 64 bit valid

JDBC /sapdb/programs 7.6.03.03 valid

Messages /sapdb/programs MSG 0.5603 valid

ODBC /sapdb/programs 7.6.03.09 64 bit valid

Database Kernel /sapdb/UMP/db 7.6.03.09 64 bit valid

Loader /sapdb/programs 7.6.03.09 64 bit valid

SQLDBC /sapdb/programs 7.6.03.09 64 bit valid

Fastload API /sapdb/programs 7.6.03.09 64 bit valid

SQLDBC 76 /sapdb/programs 7.6.03.09 64 bit valid

sapprod:umpadm 3>

thanks

Alberto

[former_member229109 · Accepted solution]

Hello Alberto G,

1. As I already wrote you that the dbmrfc problem from SAP note 1128989

fixed as of version 7.6.03 build 14 or 7.6.04 build 06, you have version 7.6.03 build 9.

And the solution to the dbmrfc issue is to update the database to the version MAXDB 7.6.05.12 ,

Latest released version, follow the SAP note 0735598 for the database update.

The independent database software will be updated to the version 7.6.05.12 too.

2. Second problem:

"We have many problems with the backups to disk (disk USB attach to server)

-24988 SQL error (Backup_save "Data1" DATA RECOVERY); -903, HOST file I/O error"

I could create the complete databackup to USB disk attached to server without any problems.

To get clear on your issue, so far I don't think that the second problem related to the first one,

Please update with additional information:

• Post the errors you see in the knldiag file + additional lines before the error.

• The dbm.prt lines with the errors + dbm command, which was executed.

*According the posted info you run dbm command : Backup_save "Data1" DATA RECOVERY

Please post the output of the dbm command 'medium_getall' to see the medium defenition.

3. As SAP customer you have option to create the OSS ticket and get SAP support. And the problems on your system could be discussed in more details with SAP support, we could logon via OSS to check your system.

Thank you and best regards, Natalia Khlopina

[Former Member · Accepted solution]

Hi Natalia, The mentioned noted helped, updating the client software fix the problem.

In the second case, defining a backup template, the command use:

dmbcli -u superdba,pass -d UMD medium_put DemoDataCompl /mnt/Disco2/completoEnero FILE DATA 0 8

But this is the output

ERR

-24994,ERR_RTE: Runtime environment error

1,OS error: 'No space left on device'

I can verify the disk space:

Filesystem 1K-blocks Used Available Use% Mounted on

/dev/md0 2972144 2889300 0 100% /

/dev/md13 267757856 166241940 87695204 66% /sapdb/UMD/sapdata

/dev/md9 13888536 166300 13005344 2% /tmp

/dev/md8 11904496 723276 10566740 7% /home

/dev/md7 6940392 146968 6435184 3% /opt

/dev/md6 11904496 766048 10523968 7% /sapmnt/UMD

/dev/md5 29753468 21441144 6776516 76% /instaladores

/dev/md4 19840804 16576224 2240444 89% /sapdb/UMD/saplog

/dev/md3 24797260 176200 23341092 1% /sapdb/UMD/sapdb

/dev/md2 9920468 2622756 6785648 28% /usr

/dev/md11 24797324 8687288 14830064 37% /usr/sap/trans

/dev/md10 24797260 2001188 21516104 9% /usr/sap/UMD

/dev/md1 7936416 204588 7322180 3% /var

tmpfs 4155300 1445468 2709832 35% /dev/shm

/dev/sdb1 961432072 188260056 724334016 21% /mnt/Disco2

I don´t understand what is my mistake

Thanks for your help

[markus_doehr2 · Accepted solution]

> ERR

> -24994,ERR_RTE: Runtime environment error

> 1,OS error: 'No space left on device'

This is an IPC shared memory (mmap()ed file) error - not a filesystem error.

Did you adapt the IPC shared memory parameters in /etc/sysctl.conf?

Markus

[Former Member · Accepted solution]

Hi Markus, that is the error. I change the sysctl.conf and works the definition backup template, but now with the command backup_start DemoDataCompl obtain this error:

dbmcli on UMQ>backup_start DemoDataCompl

ERR

-24988,ERR_SQL: SQL error

-903,Host file I/O error

3,Data backup failed

1,Backupmedium #1 (/mnt/DiscoTMP2/completo) Could not open volume

6,Backup error occured, Error code 3700 "hostfile_error"

17,Servertask Info: because Error in backup task occured

10,Job 1 (Backup / Restore Medium Task) [executing] WaitingT120 Result=3700

6,Error in backup task occured, Error code 3700 "hostfile_error"

the command for template:

dbmcli -u superdba,pass -d UMQ medium_put DemoDataInc /mnt/DiscoTMP2/incremental FILE DATA 0 8 NO

OK

I very much appreciate any cooperation

[former_member229109 · Accepted solution]

-> Please check if you could create the file in /mnt/DiscoTMP2 as sdb user or user in the sdba group.

-> Please update with output of the commands:

df -k /mnt/DiscoTMP2

ls -l /mnt

mount

&& dbm command 'medium_get DemoDataCompl'.

Thank you & best regards, Natalia Khlopina