bdadiag Script Fails When Running on BDA 4.11 X7-2 Servers (Doc ID 2441439.1)

Last updated on APRIL 17, 2023

Applies to:

Symptoms

When running the bdadiag script on an X7-2, BDA 4.11 cluster, the script completes but reports many errors and does not create the output file. Some of these errors are:

...
/opt/oracle/bda/bin/bdadiag: line 1069: $outdir/messages/"ilom-console-history.out": ambiguous redirect
/opt/oracle/bda/bin/bdadiag: line 1077: $outdir/raid/"megacli64-AdpAllInfo.out": ambiguous redirect
/opt/oracle/bda/bin/bdadiag: line 1079: $outdir/raid/"megacli64-FwTermLog.out": ambiguous redirect
/opt/oracle/bda/bin/bdadiag: line 1080: $outdir/raid/"megacli64-CfgDsply.out": ambiguous redirect
/opt/oracle/bda/bin/bdadiag: line 1081: $outdir/raid/"megacli64-BbuCmd.out": ambiguous redirect
/opt/oracle/bda/bin/bdadiag: line 1082: $outdir/raid/"megacli64-LdPdInfo.out": ambiguous redirect
/opt/oracle/bda/bin/bdadiag: line 1083: $outdir/raid/"megacli64-PdList_long.out": ambiguous redirect
/opt/oracle/bda/bin/bdadiag: line 1084: $outdir/raid/"megacli64-LdInfo.out": ambiguous redirect

syntax error, unexpected TOKEN_UNKNOWN, expecting $end
...
cp: omitting directory `#'
/opt/oracle/bda/bin/bdadiag: line 1286: $outdir/asr/$devicename"_ps_ef_bda_mon": ambiguous redirect
Generating diagnostics tarball and removing temp directory
/bin/tar: <BDA_SerialNumber>_2018_08_23_09_24.tar.bz2: Cannot stat: No such file or directory
/bin/tar: bdadiag_<bdahost>_#: Cannot stat: No such file or directory
/bin/tar: Exiting with failure status due to previous errors

==============================================================================
Done. The report files are bzip2 compressed in /tmp/bdadiag_<bdahost>_#/bdadiag_<bdahost>_#
#
<BDA_SerialNumber>_2018_08_23_09_24.tar.bz2

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.