Top 7 Tips for Navigating NexusDB DataBase Structure Viewer Efficiently

Troubleshooting Common Issues in NexusDB DataBase Structure Viewer

1) Structure Viewer doesn’t display schema objects

• Cause: Insufficient permissions or wrong database selected.
• Fix: Ensure you’re connected with a user that has schema-read privileges and confirm the correct database file/alias is open. Refresh the viewer or reconnect.

2) Viewer shows outdated schema after changes

• Cause: Cached metadata or no auto-refresh.
• Fix: Use the viewer’s refresh/reload command or close and reopen the connection. If changes were made externally, restart the client application.

3) Slow loading or timeouts when opening large schemas

• Cause: Large number of tables/indexes, network latency, or limited client resources.
• Fix: Open on a machine with more memory/CPU, increase client-side timeouts if configurable, or view subsets (filter by schema/table name) rather than full tree.

4) Errors when expanding specific nodes (tables, indexes, fields)

• Cause: Corrupted metadata or incompatible NexusDB version differences.
• Fix: Verify NexusDB server and client versions match; run metadata validation/repair utilities included with NexusDB; restore metadata from backup if corruption found.

5) Connection fails or viewer reports authentication errors

• Cause: Wrong credentials, network blocking, or server not running.
• Fix: Check server status, confirm host/port and credentials, test connectivity with a basic client (ping/tns test), and ensure firewall allows the NexusDB service.

6) Missing relationships/foreign keys in the viewer

• Cause: Relationships not defined in DB or viewer’s filter hides them.
• Fix: Confirm foreign keys exist in the schema (query system tables) and remove filters or enable relationship display options in the viewer.

7) Incorrect column types or lengths shown

• Cause: Viewer misreading metadata due to version mismatch or corrupted system tables.
• Fix: Compare results with direct SQL queries against system tables; update client to match server version; repair system tables if needed.

8) Exporting schema fails or produces incomplete output

• Cause: Bug, insufficient permissions, or unsupported objects in export.
• Fix: Check error logs for details, run export as an elevated user, split export into smaller parts, or use SQL scripts to extract schema definitions manually.

9) UI glitches or crashes in Structure Viewer

• Cause: Client-side bugs, incompatible OS components, or corrupted settings.
• Fix: Update to latest NexusDB tools, reset viewer settings/preferences, or reinstall the client. Check application logs and Windows Event Viewer for crash details.

Quick diagnostic checklist

1. Confirm NexusDB client/server versions match.
2. Test connectivity and credentials separately.
3. Refresh viewer and clear any caches.
4. Query system tables directly to compare metadata.
5. Check logs (client, server, OS) for error specifics.
6. Run metadata validation/repair tools and restore backups if necessary.

If you want, I can provide example SQL queries to inspect NexusDB system tables or a step-by-step repair checklist based on a specific error message.