Spectrus DB Enterprise: Troubleshooting "Scheduled for Reindexing" persistent status

Description

The yellow status message “Scheduled for Reindexing” remains continuously displayed in the Spectrus DB client bottom status bar or under the Index State column in the Record Sets panel of ESMC (Enterprise Server Management Console).

Impact on Search

While a Record Set is in the Scheduled for Reindexing or Reindexing state:

• Newly Added Data is Incompletely Searchable: Substructure, similarity, spectral queries, and spectrum previews will not return or display newly added or modified records until indexing completes.

• Previously Indexed Data Remains Searchable: Existing records indexed prior to the latest import/update are unaffected.

• Basic Metadata Searches: Direct field searches (e.g., Record ID, batch number) continue to function.

Overview (Normal Behavior)

What Does "Scheduled for Reindexing" Mean?

In Spectrus DB Enterprise (Remote), background indexes enable rapid chemical structure searches (exact, substructure, similarity) and analytical peak queries. When records with chemical structures or spectral/chromatographic data are imported, created, or updated:

1. The Spectrus DB Server automatically queues the Record Set for background index regeneration.

2. In the Spectrus DB client, a yellow status message appears in the bottom status bar:
   Scheduled for reindexing (or Scheduled for reindexing (SubStructure, Similarity), etc.).

3. In ESMC (Enterprise Server Management Console) under the Record Sets panel, the Index State column displays Scheduled for Reindexing.

Normal Indexing Lifecycle

Under healthy system operations, the dedicated background process (cbookreindexer.exe) automatically picks up the queued task and progresses through the stages:

1. Scheduled for Reindexing

2. Reindexing ( Processing Spectra, Processing SubStructure/Similarity, Processing Spectra  Previews and Tables, etc.)

3. Valid  as shown in ESMC (the yellow status bar message in the Spectrus DB client disappears).

Expected Completion Time

• Data Volume: A few records take seconds to minutes; bulk imports (thousands of records) can take several hours.

• Data Complexity: Complex data (2D NMR, hyphenated chromatograms, Markush structures) takes longer than simple 1D spectra or basic chemical structures.

• Server Performance: Available CPU, memory, and disk I/O on the database server.

Troubleshooting (When Status Persists)

1. Check Scope — Single vs. Multiple Record Sets

-  Open ESMC.exe (located in <ACD_Installation_Dir>\SPECTRUSDB.SRV) and navigate to the Record Sets panel, check Index State column:

• Only One Record Set is Stuck

• Multiple or All Record Sets are Stuck

2. Inspect Machine and System Resources

On the SDBES server:

- Verify CPU/memory/disk are healthy and sufficient on the server.
- Check SDBES processes in Task Manager: ensure CBOOKSERVER.EXE and CBOOKREINDEXER.EXE are running.

3. Check & Toggle "Allow Database Reindexing" in ESMC

1. Open ESMC.exe (located in <ACD_Installation_Dir>\SPECTRUSDB.SRV) and log in as an administrator.

2. In the left tree, locate your database schema (e.g., PostgreSQL DB or Oracle DB).

3. Right-click the database node:

   • Verify whether Allow Database Reindexing has a checkmark.

   • If it is unchecked, click it to enable reindexing.

4. Toggle Reindexing:

   • If already checked, right-click and uncheck Allow Database Reindexing.

   • Wait 30 seconds.

   • Right-click and check Allow Database Reindexing again.

5. In the Record Sets panel, right-click the affected record set and select Reindex. 

6. Wait 5–10 minutes, then Refresh and verify Index State.

4: Restart Spectrus DB Enterprise Server

Restarting the SDBES service resets connections, clears transient deadlocks, and relaunches the reindexer process:

1. Launch SMC.exe (Server Management Console) from <ACD_Installation_Dir>\SERVICES.SRV

2. Locate Spectrus DB Enterprise Server (SDBES).

3. Right-click and select Stop.

4. Open Windows Task Manager to ensure both cbookserver.exe and cbookreindexer.exe have cleanly exited. If an orphaned process is hanging, manually terminate it via End Task.

5. Start the Spectrus DB Enterprise Server.

6. Return to ESMC or the Spectrus DB client and verify if the status begins processing or clears to Valid.

5. Validate environment versions and state:

- Note SDBES and PostgreSQL/ Oracle DB versions; confirm no recent upgrades/changes coincide with the issue.
- Confirm disk thresholds for database and temp tables are not exceeded.

Escalation / Diagnostics Collection

If the status remains stuck, collect the following diagnostics and contact Technical Support:

• Logs & Crash Dumps: Gather cbookserver_errors.log, cbookreindexer_errors.log, cbookserver_scripts.log, and the entire \bug_reports\ folder from <ACD_Installation_Dir>\SPECTRUSDB.SRV\.

• Timestamps: Note approximate time the issue began and any recent service restarts.

• Screenshots:

  • ESMC Record Sets showing the Index State column.

  • ESMC Database Properties showing the database schema and SDBES build versions.

• Scope Details: Affected record set names, approximate record counts, and whether large volumes of spectra or structures were recently imported.