---
oid: "1.3.6.1.4.1.1206.4.2.9.8.3"
short-description: "dcmErrCodeTable OBJECT-TYPE"
last-modified: "2025-06-28"
parent-oid: "1.3.6.1.4.1.1206.4.2.9.8"
---

## OID: `1.3.6.1.4.1.1206.4.2.9.8.3`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 1206 transportation(4) devices(2) dcm(9) dcmErrors(8) dcmErrCodeTable(3)}
```

### Description

```asn1
dcmErrCodeTable OBJECT-TYPE
SYNTAX SEQUENCE OF DcmErrCodeEntry
ACCESS not-accessible
STATUS optional
DESCRIPTION
"This table is a read-only table that is updated by the device after each setoperation. This table has a single general index. The index must be assignedsequentially by the device. The number of rows present are dependent on theresults of the previous operation. If the last set operation resulted in no
errors, then there shall be no rows configured in this table. There can be
multiple rows set (one for each item in error) or there may only be one rowset which would contain the OID of the first object that was in error, thischoice is implementation-specific. Each row identifies the type of error andlinks it to the OID of the object that caused the dcm error. This table is NOTused to report communications protocol errors, those are handled as part ofthe communications protocols. All existing rows shall be cleared out eachtime the device updates this table. The rows shall always indicate errorsbased on the last time this table was updated and not show historical errors."
```

**Classification:** MIB object for network management

### Child OIDs

- `1.3.6.1.4.1.1206.4.2.9.8.3.1`: `dcmErrCodeEntry(1)`

### Terms of Use

[Terms of use](https://oid-base.com/disclaimer.htm.md)

**Note to implementers:**: The OID repository is constantly updated but does not necessarily store the latest (or most accurate) version of this formal description. For an implementation, it is recommended to search the web for a more recent description. If this is the case, please update the above description.