Resolving Siemens S120 p0103 Database Structure Error

Resolving the Siemens S120 p0103 "Database – Structure Error" on CU320-2DP

The Siemens SINAMICS S120 drive platform occasionally reports fault F0103 / parameter (00) p0103 "Access error: Database – structure error" on the AOP30 advanced operator panel. When this fault appears, the drive reverts to commissioning mode and previously saved parameter sets are deleted from non-volatile memory. This article documents the root cause, the diagnostic parameters that must be inspected, and the field-proven recovery procedure for systems built around two CU320-2DP control units with multiple Sensor Modules (SMM / SMC) and an Active Line Module (ALM).

1. System Topology Affected by the Fault

The reported configuration is typical of a multi-axis S120 line-up:

The drive is a VVVF (Variable Voltage Variable Frequency) arrangement. Both CU320-2DP control units run DRIVE-CLiQ and the parameter set is stored on a CompactFlash (CF) card inserted in each CU.

2. The p0103 Fault – What It Means

Parameter p0103 is the "Application-specific view of an existing drive object, stored in non-volatile memory." In other words, p0103 indexes the view used to display or interpret a drive object. It is a read/write access that must agree with the project structure on the CF card.

When the firmware detects that the stored project on the CF card no longer matches the current drive object layout (an inconsistency between the active firmware view and the database on the non-volatile media), the system raises:

F0103 / A0103
Parameter (00) p0103 Access error
Database – structure error

The drive then automatically transitions to commissioning mode and clears the runtime parameter image, because the integrity of the parameter database can no longer be guaranteed.

3. Root Cause Analysis

For the S120 platform the most common root causes of an F0103 / A0103 after a power cycle are, in order of frequency:

1. Corrupted CF card file system – the FAT/FAT32 structure on the CF card contains a write that was interrupted by the power loss.
2. AOP30 internal battery low / dead – the AOP30 keeps a small parameter copy; if the lithium cell is flat, the panel will boot in commissioning mode and can request an incorrect view of the drive object database.
3. Project – firmware mismatch – the CF card contains a project saved with a different STARTER / SCOUT version or SINAMICS firmware version than the CU is now running.
4. Loose or contaminated CF card contact – vibration in the cabinet can lift the CF card briefly during power restoration, producing partial writes.
5. AOP30 ↔ CU handshake failure – if the AOP30 is plugged in at the moment of boot and the handshake fails, the CU may default to commissioning mode.
6. End-of-life CF card – industrial CF cards have a finite write-cycle count. Once the wear counter is exhausted, sectors fail and the database becomes inconsistent.

4. Diagnostic Parameters to Inspect First

Before touching the hardware, read the following parameters from each affected drive object (Control Unit and every Drive Object):

The rule is simple: CU and every Drive Object must show p0009 = 0 and p0010 = 0. If any drive object is sitting in a commissioning filter (typically 1, 2, 3, 4, 5, 15, 29, 30), the control unit is held in commissioning mode and the parameter image is treated as volatile.

5. Step-by-Step Recovery Procedure

Execute the following sequence in order. Stop after each step and observe whether the fault reappears after the next power cycle.

Step 1 – Isolate the AOP30

1. Power down the cabinet and the drive DC bus.
2. Unplug the AOP30 from the CU320-2DP front port.
3. Power the cabinet back up and observe the RDY and COM LEDs on the CU.
4. If the drive now boots into RUN with no F0103, the AOP30 is the source of the corruption. Replace the AOP30 internal lithium battery (type CR2032, every 3-5 years) and re-evaluate.

Step 2 – Verify the AOP30 / BOP20 Battery

If the AOP30 is older than 3 years, or if the cabinet has been in ambient >40 °C, replace the AOP30 backup battery regardless of the test result. A weak AOP30 will force commissioning mode every time mains returns.

Step 3 – Back Up and Quick-Format the CF Card

1. Power down. Remove the CF card from CU 1 and CU 2.
2. Insert each CF card into a read-only card reader and copy the entire card content (including hidden files and the /OEM, /USER, /SINAMICS, and /SAVE directories) to a PC folder named with the date and CU serial number.
3. Re-insert the CF card and perform a QUICK format (FAT32, default allocation unit size). Do not select "Quick Format" if the option is greyed out – use the Windows / Linux quick format equivalent.
4. Copy the backed-up project files back to the root of the CF card. Verify that the file OEM.SINAMICS (or the project archive) is present at the root.
5. Re-seat the CF card in the CU and power up.

Step 4 – Re-Download the Complete Project

If a STEP 7 / TIA Portal / STARTER project archive is available, perform a complete download to the CU via PROFIBUS (DP), PROFINET, or Ethernet:

1. Open the original STARTER / SCOUT project that matches the SINAMICS firmware version stamped on the CU320-2DP label (the firmware version is also readable in parameter r0018 on a healthy CU).
2. Connect to the CU with the correct PG/PC interface.
3. Right-click the drive and select Download → Download to target device. Tick Download with consistency check and select Download after assembling the project (incl. DCC charts).
4. Save the project to the CF card (Copy RAM to ROM equivalent in STARTER, or Save to non-volatile memory from the AOP30 menu).
5. Perform a POWER ON of the CU. The CF card now contains a freshly written, consistent project.

Step 5 – Verify the Commissioning State

After the download, check on every drive object:

// STARTER / SCOUT expert list
p0009 = 0
p0010 = 0
p0103 = 
r0002 = "Operation – ready to run" (typical code "S2")
r3996 = 0

If all DO show p0009 = 0 and p0010 = 0, the drive will leave commissioning mode and the F0103 / A0103 will clear.

Step 6 – Replace the CF Card (if the Fault Recurs)

If the F0103 returns within two further power cycles, the CF card has exhausted its write-cycle budget or has a bad block. Order a replacement of the same Siemens part number (typical S120 CF card PNs: 6SL3054-0xx00-1BA0 family). Write the latest project image to the new card, then install.

6. Verification Checklist After Recovery

7. Preventive Measures

1. Always execute "Copy RAM to ROM" before power-down. A pending volatile write that is interrupted is the single most common cause of database corruption on S120.
2. Maintain a versioned backup of every CU's CF card image. A monthly image to an external PC and a project archive to the engineering server is the recommended minimum.
3. Lock the CF card in the CU with the captive screw to prevent vibration-induced partial contact.
4. Replace the AOP30 battery on a fixed schedule (3 years maximum, 2 years in hot cabinets).
5. Keep STARTER / SCOUT and the SINAMICS firmware version in lockstep. Mixing firmware versions across the project, the CF card image, and the CU's installed firmware is a frequent source of p0103 mismatches.
6. Avoid the AOP30 during power-up if the panel is in poor condition. Boot the CU first, then connect the AOP30.
7. Cap the number of power cycles. Each power cycle stresses the CF card's flash. If the application cycles daily, plan to replace the CF card every 3-5 years.

8. Related Fault Codes and Parameters

9. Hardware-Only Quick Reference

10. Commissioning-Mode Re-Entry – What Not to Do

When the drive reverts to commissioning mode after F0103, the temptation is to immediately run a factory reset. Avoid the following operations until the database integrity is restored:

• Do not execute p0010 = 30 (parameter reset) on the CU. This will wipe the project before you have a backup of the corrupted state.
• Do not run a full format of the CF card. The license key and the SINAMICS boot image are stored in reserved sectors that are visible only to the CU.
• Do not unplug the DRIVE-CLiQ cables while the CU is powered. The topology is written to the CF card on every successful boot.
• Do not perform a firmware update on a CU that is in F0103. The update requires a consistent parameter database to succeed.

11. Field-Commissioning Notes for the Reported Topology

For the specific configuration (2x CU320-2DP, ALM + 5 SMM, AOP30), the post-recovery steps should be executed in the following order to avoid additional faults:

1. Power up CU 1 alone with the AOP30 disconnected. Verify the ALM and the 2 SMM are visible in STARTER.
2. Power up CU 2 alone. Verify the 3 SMM are visible.
3. Connect the AOP30 to CU 1 and verify the menu hierarchy shows the ALM and the 2 SMM.
4. Move the AOP30 to CU 2 and verify the 3 SMM are visible.
5. Issue a single Save to non-volatile memory on each CU from the AOP30 menu or via STARTER.
6. Perform the 3-cycle power-on soak test from the verification checklist.

This staged power-up isolates any single-CU or single-DO issue before both CU320-2DP units are exercised together.

12. Summary

The "p0103 Access error: Database – structure error" on a CU320-2DP-based SINAMICS S120 system is almost always a sign of CF card file system corruption, a flat AOP30 battery, or a project / firmware mismatch. The diagnostic centre of gravity is the trio p0009, p0010, r0002: if these are 0 / "Ready" on every drive object, the database is consistent and the drive will leave commissioning mode. If any drive object is still in commissioning, the project must be re-loaded and saved. Use a QUICK format only on the CF card, and replace the card entirely if the fault recurs after the project has been re-loaded.