Exachk Reporting An Error..awk: record ` 0000500 26178 26164...' too long

Asset ID:	1-72-2290860.1
Update Date:	2017-08-24
Keywords:

Solution Type Problem Resolution Sure

Solution 2290860.1 : Exachk Reporting An Error..awk: record ` 0000500 26178 26164...' too long

Applies to:

Oracle Exadata Storage Server Software - Version 12.1.2.1.3 and later
Exalogic Elastic Cloud X3-2 Hardware - Version X3 and later
Oracle Solaris on x86-64 (64-bit)

Symptoms

Problem Summary
---------------------------------------------------
exachk reporting an error.

Problem Description
---------------------------------------------------
./exachk -v
EXACHK VERSION: 12.2.0.1.3_20170331

./exachk -a

awk: record ` 0000500 26178 26164...' too long
record number 79

Cause

Solaris has multiple awks installed by default.

  /usr/gnu/bin/awk
  /usr/bin/awk
  /usr/xpg4/bin/awk

There are also similar tooks nawk and gawk installed.

The first two have a issues with command strings that exceed a certain character limit. Hence the error seen by the customer. The other tools, /usr/xpg4/bin/awk, nawk and gawk, don't have this problem.

Bug 23717220 [https://bug.oraclecorp.com/pls/bug/webbug_edit.edit_info_top?rptno=23717220] [https://bug.oraclecorp.com/pls/bug/webbug_edit.edit_info_top?rptno=23717220] - /usr/bin/awk fails with awk: record ` ...' too long

===Version Info from the SR===

X3-2 . 2 Nodes

Exalogic statck

Os version: Solaris 11.3

Is this failing only on this node? All nodes

complete error message while running the exacheck

awk: record ' 0000500 26178 26164...' too long
record number 79

Please note.

The problem is with awk use in Solaris. It has limitation.

To test.

perl -e 'print "a"x2569' | awk '{print length}'
awk: record 'aaaaaaaaaaaaaaaaaaaa...' too long

perl -e 'print "a"x2569' | nawk '{print length}'
2569

Solution

Bug 23717220 - /usr/bin/awk fails with awk: record ' ...' too long

Patch not been released yet,its under development working,it will take some time to release patch under testing and all.

---Action Plan /Workaround-----

1. Check if /usr/xpg4/bin/awk exists.

If it exists, go to #2.

If it does not exist, stop here and update the SR with this information.

2. Modify your PATH to place the path to /usr/xpg4/bin/awk or /usr/bin/nawk (which ever you found) before all other items in your PATH. For example:

export PATH=/usr/xpg4/bin:$PATH

3. Run the latest version of Exachk.

If Exachk runs successfully, the issue is resolved.

References

<NOTE:1543820.1> - Availability Machine - Exachk
<BUG:18788862> - SOLSP-12.1-UTL-ORACHK: 'AWK...TOO LONG' WARNING MESSAGE FROM ORACHK CHECK OUTPUT
<BUG:23717220> - /USR/BIN/AWK FAILS WITH AWK: RECORD ` ...' TOO LONG
<NOTE:1070954.1> - Oracle Exadata Database Machine exachk or HealthCheck
<NOTE:1478378.1> - Exalogic Exachk Health-Check Tool Known Issues

Attachments

This solution has no attachment