SCC-00164: Application quiesce for the plug-in [MAXDB] failed with exit code [-1] and with error

[C_Greiner]

Hello Netapp.Community,

we try to backup our first MaxDB-Systems.

We were able to install the maxdb-plugin on our Host (RHEL8).

We get these message when we want to backup the MaxDB:

 SCC-00164: Application quiesce for the plug-in [MAXDB] failed with exit code [-1] and with error : Can't exec "dbmcli": No such file or directory at /IO/CaptureOutput.pm line 74 (#1) (W exec) A system(), exec(), or piped open call could not execute the named program for the indicated reason. Typical reasons include: the permissions were wrong on the file, the file wasn't found in $ENV{PATH}, the executable in question was compiled for another architecture, or the #! line in a script points to an interpreter that can't be run for similar reasons. (Or maybe your system doesn't support #! at all.) SCC-00185: Cleanup for plug-in [MAXDB] failed with exit code [102] and error:

We created a user on the system called snapadm and configured sudo and PATH-variable:

[snapadm@sapaexqv01 ~]$ echo $PATH
/home/snapadm/.local/bin:/home/snapadm/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sapdb/QEX/db/bin

##Sudo-User for SnapCenter
Cmnd_Alias HPPLCMD = sha224:ixqWGFtPO4V8GF2nrHRLGNr77hxudiN3vFhcwQ== /home/snapadm/.sc_netapp/snapcenter_linux_host_plugin.bin, /opt/NetApp/snapcenter/spl/installation/plugins/uninstall, /opt/NetApp/snapcenter/spl/bin/spl
Cmnd_Alias PRECHECKCMD = sha224:sZ/BzfT0pc81O1JeEF7gQA7ykrBrvYKj0L3xLA== /home/snapadm/.sc_netapp/Linux_Prechecks.sh
snapadm ALL=(ALL) NOPASSWD:SETENV: HPPLCMD, PRECHECKCMD
Defaults:snapadm !visiblepw
Defaults:snapadm !requiretty

With snapadm I can check the database like this:

[snapadm@sapaexqv01 ~]$ dbmcli -d QEX -u control,password db_state
OK
State
ONLINE

See also the attached File to see our SnapCenter-Config

I hope I get help here.

Best Regards Christoph Greiner

[darb0505]

Hi Chris,

Sorry to hear that you are having an issue with trying to back up a MaxDB with SnapCenter.  Can you tell me what version of SnapCenter and MaxDB you are running? 

Thanks

[C_Greiner]

Hello Team Netapp,

SnapCenter Server Version 4.4 

Build = 4.4.0.5053

SnapCenter-Plugin Package 1.0 for Linux

MaxDB-Version = 7.9.09.05

Thanx

Best Regards Christoph Greiner

[darb0505]

Hi Chris,

Thanks for getting us this information.  Based on the version of SnapCenter and MaxDB, this issue seems to be related to a known issue with the plugin failing to quiesce. 

You can reference the following KB: Quiesce hangs during SnapCenter MaxDB backup, then times out

Let us know if you have any questions regarding the KB or the solution in the KB.

Thanks

[C_Greiner]

Hello Netapp,

we created 2 scripts

/opt/NetApp/snapcenter/spl/scripts/prequiesce.sh:

 #!/bin/bash
export HOME="/home/snapadm"
/sapdb/DEX/db/bin/dbmcli -d DEX -u control,password background_server_start na_bg_DEX

/opt/NetApp/snapcenter/spl/scripts/postquiesce.sh:

#!/bin/bash
export HOME="/home/snapadm"
/sapdb/DEX/db/bin/dbmcli -d DEX -u control,password background_server_exit na_bg_DEX

The User snapadm can execute this scripts sucessful on OS.

But in the snapcenter we become this error:

SCC-00164: Application quiesce for the plug-in [MAXDB] failed with exit code [-1] and with error : Can't exec "dbmcli": No such file or directory at /IO/CaptureOutput.pm line 74 (#1) (W exec) A system(), exec(), or piped open call could not execute the named program for the indicated reason. Typical reasons include: the permissions were wrong on the file, the file wasn't found in $ENV{PATH}, the executable in question was compiled for another architecture, or the #! line in a script points to an interpreter that can't be run for similar reasons. (Or maybe your system doesn't support #! at all.)

Can anybody help me out?

Best Regards

Christoph Greiner

[RamiB · Accepted solution]

Hi,

Did you specified the DBMCLICMD in the resource parameters(In Snapcenetr)?

the error indicates that this option is not specified.

this should include the path to the dbmcli

you are also welcome to open a case for this issue

Thanks