CAST Imaging System - Database - Neo4j - Error on Documentation - V2

CAST Imaging System - Database - Neo4j - Error - Server error - Java heap space

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This section provides assistance when there is aMemory error while Importing into Imaging.

Memory error can result in a warning and an error in imaging system while importing which maybe seen as one of the following:

WARN run: unable getting transactionObjects cypher summary for x_complete error=database returned error[Neo.TransientError.General.OutOfMemoryError]
ERROR Import: error while remodeling the graph, aborting import error=subobjectswithgraphrefactor: failed to run queries to import sub-objects and refactor the graph: run: error fetching cypher summary for Removal of .NET Instantiated nodes

Imaging Version

CAST Imaging System - Database - Neo4j - Error - Super Admin not accessible anymore

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This section provides assistance when Super Admin is not accessible in Imaging. The Super Admin user account may have been removed or is no longer active.

Imaging Version

Release	Yes/No
2.x	✅

Details

Please select the ‘imaging’ database and run the following:. For using this refer CAST Imaging System - Information - How to access Neo4j

MATCH (r:Role {Name: ‘Super Admin’})<-[:HAS_ROLE]-(k) RETURN k.Name, labels(k)

 2. ```java
MATCH (r:Role {Name: 'Super Admin'})<-[:HAS_ROLE]-(k:User)<-[:CONTAINS_USER]-(sm:SecurityMode) RETURN k.Name, sm.Name

The first query returns the user name and role. The second query returns the user name and type of access they are authorized for (such as ‘LDAP’)

CAST Imaging System - Database - Neo4j - Error - Database not starting results in errors like applications not loading or internal server error

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

When the Neo4j database is not up, you may face several problems such as ‘Internal server error’ when applying a key, applications not loading, errors like ‘Index clean jobs can’t be added after collector start’.

Imaging Version

Release	Yes/No
2.x	✅

Details

When the Neo4j database is not up, you can have several problems such as ‘Internal server error’ when applying a key, applications not loading, and errors like ‘Index clean jobs can’t be added after collector start’.

CAST Imaging System - Database - Neo4j - Error - Failed to apply transaction

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

When starting imaging the applications are not loading. The following Error is seen in the neo4j debug.log file : “org.neo4j.internal.kernel.api.exceptions.TransactionApplyKernelException: Failed to apply transaction: Transaction #594571 at log position”

Because of this error, database recovery was failing and going to offline state.

Imaging Version

Release	Yes/No
2.x	✅

Details

Define the following parameter in neo4j.conf file.

unsupported.dbms.tx_log.fail_on_corrupted_log_files=false

2. Restart the neo4j service after adding this parameter
3. If you do not find the information you are looking for or solution for your problem, please contact [CAST Technical Support](https://help.castsoftware.com/hc/en-us/articles/204189137-How-to-contact-CAST-Technical-Support)

**Notes/comments**

**Related Pages**

CAST Imaging System - Database - Neo4j - Error - Fail to read transaction log version

Mon, 01 Jan 0001 00:00:00 +0000

Purpose (problem description)

The neo4j database is not changing its state from offline to online even after using the CALL dbms.quarantineDatabase(“neo4j”,false) query to un quarantine it.

Found Fail to read transaction log version xxxx error in debug log

Observed in CAST Version, CAST Extension Version, CAST Component Version

Release	Yes/No
>2.x	✅

Step by Step scenario

Ran command CALL dbms.quarantineDatabase(“neo4j”,false) query to un quarantine the noe4j database
neo4j remains in the quarantine (offline) state.
Checked the debug log.
Found the error Fail to read transaction log version xxxx,

Action Plan

CAST Imaging System - Database - Neo4j - Error - Transaction logs are missing and recovery is not possible

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

When starting imaging, neo4j does not start and the debug.log shows the error: ‘Transaction logs are missing and recovery is not possible’

Imaging Version

Release	Yes/No
2.x	✅

Details

This happens if something has happened to the transaction logs, such as they were moved or removed due to space issues.

However deleting/moving them is not permitted as per neo4j: https://neo4j.com/docs/operations-manual/current/configuration/transaction-logs

Since the transaction logs were missing,

Add below parameter to the neo4j.conf file which forces database to start without recovery in case of missing transaction logs.