uniCenta oPOS upgrade

uniCenta oPOS have so far released quite a few versions from 3.56 that I am using. They are 3.60, 3.70, 3.80/3.81, 3.90. The upgrade cannot be straight from 3.56 to 3.90. As per the release notes, it goes this way: 3.56 -> 3.60, 3.60 -> 3.70, 3.70 -> 3.90.

3.80/3.81 can be skipped. Version 3.80 is deprecated since it introduced some error to the database, 3.81 was released to address this issue.

All of the version so far seem to need the JRE 1.7. The latest JRE 1.8 is not compatible, using it with uniCenta oPOS will result in errors when running some reports (I only tested the “top 10 sales” report).

If the installer throws in an error saying JRE is not installed, it is possible that you don’t have JRE 1.7 installed. The uniCenta oPOS installer doesn’t recognise JRE 1.8 even it is installed.

Installer issue on old PCs

I discovered that since uniCenta oPOS 3.70, the installer cannot start on older PCs that appear to have CPU that doesn’t support SSE2. The installer will throw an error then quit. So far I haven’t been able to find a solution to this.

PostgresSQL database rollback

Since I encountered issue (mentioned above) when attemping to upgrade the uniCenta oPOS from 3.60 to 3.70 on an old touch screen PC. I had to roll back the database version. Below are the commands that I used for doing these. Note that pg_restore command gave me lots of error when directly restoring backup into the existing databse, I decided to drop the live database, created it again from template0 to ensure it is empty, then restore backup into the empty database.

Below restores the database backup file “unicenta.bak” into a database named “unicenta_test”. The restore command askes for password when starting.

cd "C:\Program Files\PostgreSQL\9.3\bin\"
pg_restore.exe -U username -d unicenta_test 'E:\DB backup\unicenta.bak'

Below creates an empty database named “unicenta_test”

cd "C:\Program Files\PostgreSQL\9.3\bin\"
createdb.exe -U username -T template0 unicenta_test

I didn’t find the command to change database owner to be the right one, therefore using the pgadmin GUI tool to do this. Ensure the database owner is the right one instead of the default Postgres one.