Error while importing and publishing from 5.8 to 6.0

[himanshu]

Hi,

I am importing BSV from a lower version of AwareIM 5.9 & MySQL 5.6.16 database to version 6.0 and 5.6.26 version of MySQL too.
I also try 5.6.17 MySQL version too but awareim is having some exception.

Below are the snapshots and logs i got. Please any suggestion or help.

java.lang.Exception: Aware IM server encountered the following error .Error creating data base tables You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'POSITION(ID INT NOT NULL PRIMARY KEY, BASVERSION int, BASTIMESTAMP datetime, Pos' at line 1
at com.bas.uiconfiguration.model.D.A(Unknown Source)
at com.bas.uiconfiguration.model.D.B(Unknown Source)
at com.bas.uiconfiguration.command.DomainVersionPublishCommand.D(Unknown Source)
at com.bas.uiconfiguration.command.B.actionPerformed(Unknown Source)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:2018)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2341)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:402)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:259)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:252)
at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:290)
at java.awt.Component.processMouseEvent(Component.java:6505)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3320)
at java.awt.Component.processEvent(Component.java:6270)
at java.awt.Container.processEvent(Container.java:2229)
at java.awt.Component.dispatchEventImpl(Component.java:4861)
at java.awt.Container.dispatchEventImpl(Container.java:2287)
at java.awt.Component.dispatchEvent(Component.java:4687)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4832)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4492)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4422)
at java.awt.Container.dispatchEventImpl(Container.java:2273)
at java.awt.Window.dispatchEventImpl(Window.java:2719)
at java.awt.Component.dispatchEvent(Component.java:4687)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:735)
at java.awt.EventQueue.access$200(EventQueue.java:103)
at java.awt.EventQueue$3.run(EventQueue.java:694)
at java.awt.EventQueue$3.run(EventQueue.java:692)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:87)
at java.awt.EventQueue$4.run(EventQueue.java:708)
at java.awt.EventQueue$4.run(EventQueue.java:706)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:705)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:146)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:91)

[aware_support]

Do you have an object or attribute named Position? If so, try renaming it - it is possible that the new version of MySQL has introduced new keywords that clash with the names of the objects/attributes

[himanshu]

Tons of Thanks Support,

There was a Business Object which was named as Position in my space and after updating problem solved.

It was being last 6-7 days I struggling with the issue. I had tried on 4-5 machine with different version of MySQL and even with previous version of AIM but not able to troubleshoot the root cause.

I am surprised too with following results :

1. As you suggest POSITION is the MySQL keyword but it was present since version 5.0 which was never notified before in the development process or updating the BSV versions.
2. I have tested on multiple terminals and found on 2 terminal out of 5 BSV got published without any issue.

At last you save my life, thanks a lot again for the great support. !!!!