HPE EVA Storage

RSM 5.1 PSQLException

New Member

RSM 5.1 PSQLException

Hi everyone,
Having this issue with RSM 5.1 when I try run any jobs
"psqlexception :error:invalid input syntax for type timestamp:"somedate""

It doesnt matter which job I try
* trying to add a vmserver
* trying to create a drgroup

Any Ideas ?
Occasional Advisor

Re: RSM 5.1 PSQLException

I have the same error with RSM 5.1.70.

Are there any solutions???
Ralf Gerresheim
Frequent Advisor

Re: RSM 5.1 PSQLException

Hello sagie

I have the same problem:
It doesn't work on a W2k3 server in our lab, but it works absolutely without any problem on a W2k3 R2 server!

Maybe that will help you.

New Member

Re: RSM 5.1 PSQLException


we had the same Problem after updating to RSM 5.1.70.

org.postgresl.util.PSQLException:ERROR: invalid input syntax for type timestamp: "2010-07-06 09:10:57 MESZ"

After I was reading a lot of Postgresql manuals, I figured out how the postgresql 8.3 insallation is working with timezones etc...

The timezonesets that are valid are stored in the following folder:
C:\Program Files (x86)\PostgreSQL\8.3\share\timezonesets\

If nothing else is configured in the postgresql.conf, the "Default" file is used.

As I was checking the "Default" file, I was recognizing that "MESZ"(Mitteleuropaeische Sommerzeit) was not listed under "EUROPE". That is quiet strange, because MEZ (Mitteleuropaeische Zeit) is listed! And also "MEST" (Middle Europe Summer Time) is also listed... I don't know why MESZ isn't but I thougt lets give it a try and edit the file. I added the following row:

MESZ 7200 D # Mitteleuropaeische Sommerzeit (German) (not in zic)

After that I restarted the RSM Services and everythin is workin fine now.

I'm not saying this is a supported solution for that problem, I just say it works for us.
I'm not a postgresql or hp engineer so please use this information on your own risk.

Under the follwoing link you find the porstgresql manual, have a look under Appendix B.




New Member

Re: RSM 5.1 PSQLException

This problem is still present in the most recent version of RSM. 


@HP: you might want to fix this ... ?