dbm_getf_error (Tcode DB13)

[Former Member]

Hello!

I have the following error, entering the tcode DB13

Name und Server : <SAPSID> - server1020

DBMRFC Function : DBM_GETF

Command : DBAHIST DATE=20060907

Error : Systemerror

error message : timeout during allocate / CPIC-CALL: 'ThSAPCMRCV' : cmRc=20

dbm_getf_error

Meldungsnr. SADA001

What can be done in order to solve the problem?

Thank you very much!

[roland_mallmann]

Hi,

if you can't find a matching OSS note on the subject (on component BC-DB-SDB*), then please (if not already done) open an OSS ticket. Please mention your exact R/3 and DB version.

One thing which you could do is to check the connection to your MaxDB instance from transaction DB59.

Regards,

Roland

[Former Member]

Thank you Roland,

which FRC-connection in Tcode SM59 do you mention, is that

<b><SID></b>?

If yes, this connection works, although it is the self-generated connection, becausu none data there is maintaned.

Have you other troubleshooting steps?

Thank you!

regards

[roland_mallmann]

Hi again,

I didn't mention transaction SM59, but DB59. Please check the connection there. In SM59 you could check the connections 'SAPDB_DBM' and 'SAPDB_DBM_DAEMON'.

Important: as already stated and if not already done so, please open an official OSS ticket for your issue.

Regards,

Roland

[Former Member]

Hi again,

thank you!

I have executed the Tcode DB59 and executed the test you recommended.

The following result:

SAPDB_DBM was unsuccessful

the other three etries are working fine.

What can be done.

I have patched my kernel and disp+work.

Perhaps some RFC-patches should be executed?

Thank you

[roland_mallmann]

So only the SM59 test of connection SAPDB_DBM was unsuccessful? The connection test in SM59 for 'SAPDB_DBM_DAEMON' went ok?

The connection test in DB59 was ok?

---

I really <b>must</b> urge you to open a ticket for your issue. Any further communicatio should then continue in that ticket.

Please also mention this SDN thread in your ticket.

Regards,

Roland

[Former Member]

Hello!

The check result is of course red, because of unsuccessful SAPDB_DBM..

The SAPDB_DBM_DAEMON is successful.

I will create the OSS message, but I will first try to solve the problem by myself.

Regards

Thom

[Former Member]

Hi!

I have tested tp commando that has been ended also with error:

tp pf=/usr/sap/trans/bin/TP_DOMAIN_<SID>.PFL connect <SID>

tells me missing parameter SAPEVTPATH

Can you help with this issue?

Thank you!

regards

[former_member229109]

Dear Mr. Heinemann,

1)"I have patched my kernel and disp+work."

What version of the SAP kernel do you have on your system?

What versions of the tp tool & sapdbmrfc?

What is OS of the application server?

2) What are the versions of the database software packages installed

on the application server ?

Please update with output of the command 'sdbregview -l'

< see SAP note 822239 >.

3) Please run checks in the transaction /nstms-> Import Overview -> go to the 'Import queue'

-> Check -> Transport tool

< For example, review the SAP notes 47392 & 97993 >

tp pf=/usr/sap/trans/bin/TP_DOMAIN_<SID>.PFL getdbinfo <SID>

4) Please repeat the Connection Test in /ndb59 for selected Database Connection & update with 'Connection Test Log'.

Please also check errors in /nst11 in the logs dev_rd, dev_rfc,dev_w …

Please check in the Connection Test log - General Connection Data :

Connection Name....:

Database Name......:

Database Server....:

tp Profiles .......: no_longer_used < ?? >

And run in /nsm49, using dbmcli tool :

-d <SID-Database Name> -n <Database Server> -tpi <SID-system> -tpc <SID-connection name> -tpp no_longer_used db_state

or

-d <SID-Database Name> -n <Database Server> -tpi <SID-system> -tpc <SID-connection name> -tpp no_longer_used info state

5) Please also check, if you will get errors in /nsm49, using dbmrfc tool -> Execute

6) You reported the error: dbm_getf_error - Meldungsnr. SADA001 above.

Please run the tests in /nsm49, using dbmgetf tool:

-d <SID-Database Name> -n <Database Server> -tpi <SID-system> -tpc <SID-connection name> -tpp no_longer_used -l

< to review the list of the files ID => see if DBAHIST is listed >

-d <SID-Database Name> -n <Database Server> -tpi <SID-system> -tpc <SID-connection name> -tpp no_longer_used -k DBAHIST DATE=20060907

&&

-d <SID-Database Name> -n <Database Server> -u control,<control> -k DBAHIST DATE=20060907

7) Did you already open the OSS message, where you reported this problem?

Thank you and best regards, Natalia Khlopina