from the error message it looks like you are running into an endianness problem. SPARC is big-endian and linux X86 is little endian. We do not support the case where the same set of database and log files are accessed by machines of 2 different endianness. You take a db that is on a little endian machine, move it to a big endian machine, start it up and access it from just the big endian machine .
In our scenario, moving it may not be a suitable solution in a sense that others may want to access that at original location.
Let me give little bit more details...
If I am not doing any in memory write or reads (i.e. directly accessing db file) would it be OK to remove journals when db is being updated?
I thought of removing the journals....
Log files are for recovery. If you are not concerned with recovering transactions then you can remove them. If you are not concerned with transaction recovery, then maybe you can run without transactions all together. This change would be made by changing the flags on the db open.