Resolving Inspection Form Revision Errors in Maximo

A field-tested troubleshooting guide for the -803 database error and inconsistent revision behavior in Maximo Inspection Forms.

Best for: Maximo administrators, EAM technical leads, implementation teams

The Problem

When attempting to create a new revision of an Inspection Form, Maximo returns the following error:

Database error number -803 has occurred when operating on APPDOCTYPE... BMXAA4211E

At the same time, the inspection form behavior becomes inconsistent — visible in some contexts but failing to function correctly during revision attempts.

What Actually Happened

The error traces back to a missing record in the APPDOCTYPE table:

• Missing CONTMASTER entry
• DOCTYPE = CONTADM

This creates a mismatch between application logic and database state.

Two compounding factors make it worse:

• The inspection form update process failed mid-transaction, leaving the system in an inconsistent state
• The active form incorrectly had HASREVISION = 0, which prevented proper revision handling and caused erratic UI behavior

Key insight: The -803 error points to a constraint issue, but the root cause is missing configuration data — not a duplication problem. Treat database errors as symptoms, not conclusions.

Resolution

Step 1 — Restore Application Visibility

Reset the revision flag to stabilize the form and restore visibility in the application:

UPDATE INSPECTIONFORM
SET HASREVISION = 0
WHERE INSPFORMNUM = '1055'
AND STATUS = 'ACTIVE';

Note: Replace 1055 with your actual inspection form number.

This resets the revision flag after the failed mid-transaction update and allows the form to appear and behave correctly again.

Step 2 — Recreate the Missing System Record

Rather than inserting directly into APPDOCTYPE — which risks missing dependent relationships — use Maximo to rebuild the record automatically:

1. Create a dummy inspection form in the Inspection Forms application
2. Add a question that references document attachments in folder CONTADM
3. Save the form

Maximo will automatically:

• Generate the missing APPDOCTYPE record
• Re-establish the required CONTMASTER relationship

Best Practice: Always let Maximo rebuild system records through application-driven actions where possible. Direct database inserts bypass the logic that establishes dependent relationships — and can leave the system in a harder-to-diagnose state than before.

Validation Checklist

After completing both steps, confirm the following before closing out:

• Inspection form is visible and accessible in the application
• New revision can be initiated without error
• APPDOCTYPE contains a CONTMASTER entry with DOCTYPE = CONTADM
• HASREVISION flag reflects accurate revision state
• Dummy inspection form is inactivated or removed after system record is confirmed

Key Lessons Learned

1. APPDOCTYPE integrity is critical for Inspection Forms

Inspection Forms that reference attachments depend on proper document type configuration. Missing entries in APPDOCTYPE can surface as seemingly unrelated application errors — including constraint violations that look like duplication issues.

2. Mid-transaction failures leave residual state

When Maximo operations fail during a save or revision action, flags like HASREVISION may not reflect reality. Always validate backend state when errors occur — don’t assume a visible form is a correctly configured one.

3. Let Maximo rebuild system records when possible

Application-driven record creation ensures all dependent relationships are properly established. Direct inserts into system tables skip that logic and create new risk.

4. Database error codes point to symptoms, not root causes

A -803 constraint error suggests duplication — but the actual problem here was missing data. Diagnose before acting on the error message alone.

Quick Reference

Back to Field Kits