Problems with the BD in the Dcm4chee

[Ramses Martinez Muñoz]

Good morning, I would like to ask you about a series of problems that have been presented to me with version 2.17-psql of the dcm4chee.

Firstly, I would like to know if it is possible that a study which was sent the previous day in this case of a Multicort TAC team is displayed well on the same day it was sent and is not displayed the next day. (This is the first problem).

The second problem is that the specialists have sent studies to the server with strange characters (*,;, ñ) and apparently the coding of the DB does not allow them to be sent in this way, but the strange thing about this problem is that when they send from the team nothing happens.

Now I had the need to reinstall the Operating System in this case Debian 7 v64 bits and to rebuild the BD I used the storescu.

But the same to send a series of studies and find a study that contains a special character there for the transfer process, blocks the BD and can not communicate any station with the server. (Problem 2)


And my question is this:

1- Is there any way to change the coding of the Bone BD UTF-8 to another similar one that allows me to re-index the cases that have this problem?

2- Is there another program that is not the storescu that allows me to index more than 2TB of images?

3- What tool in Postgresql allows me to identify faults in the BD?

I await your prompt reply.
Thank you very much in advance.
Ramses