AnalyticsPlus Startup issue

AnalyticsPlus Startup issue

Issue:

Unable to start the services when there is a formula column created with static data

Cause:

When a formula column holds static data static data (like 123 or 1*24)  then those data types are stored as INT4 or INT8 or float8 because which the service doesn't start.

Error trace:

[23:43:32:811]|[06-18-2020]|[SYSERR]|[INFO]|[28]: java.lang.Exception: Module Loading Failed : ZohoUserDB|
[23:43:32:811]|[06-18-2020]|[SYSERR]|[INFO]|[28]: at com.zoho.mickey.startup.MEServer.populateModules(MEServer.java:835)|
[23:43:32:811]|[06-18-2020]|[SYSERR]|[INFO]|[28]: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)|
[23:43:32:811]|[06-18-2020]|[SYSERR]|[INFO]|[28]: at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)|
[23:43:32:811]|[06-18-2020]|[SYSERR]|[INFO]|[28]: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)|
[23:43:32:811]|[06-18-2020]|[SYSERR]|[INFO]|[28]: at java.lang.reflect.Method.invoke(Method.java:497)|
[23:43:32:811]|[06-18-2020]|[SYSERR]|[INFO]|[28]: at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:349)|
[23:43:32:811]|[06-18-2020]|[SYSERR]|[INFO]|[28]: at java.lang.Thread.run(Thread.java:745)|[23:43:32:811]|[06-18-2020]|[SYSERR]|[INFO]|[28]: Caused by: java.lang.IllegalArgumentException: Unknown data type:INT4|


Solution:

  1. Start the DB from <AnalyticsPlus home>/bin.
  2. Connect to the AnalyticsPlus database and execute the below query (add the datatype found the error trace - like'INT4' or 'INT8')
    UPDATE columndetails set data_type='BIGINT' where data_type in ('INT4','INT');
    or
UPDATE columndetails set data_type='DOUBLE' where data_type='float8';
  1. Stop the db.
  2. Place this patch in <AnalyticsPlus home>/fixes folder.
  3. Start the services.

Note: The given patch is compatible with 4500 and 4510 as the issue is experienced only from 4500 build (will be fixed in the future release), 

                  New to ADSelfService Plus?

                    • Related Articles

                    • Upgrade to AnalyticsPlus 5400 Fails for Users with Missing zsoid Values

                      Issue Upgrading from builds between 5301 and 5360 to build 5400 fails because the zsoid field for some users is null. Error Trace java.sql.SQLException: This column [ZSOID] has some null values, hence it cannot be modified as not-null. Cause The ...
                    • Initial Sync Failed Between ServiceDesk Plus Cloud and AnalyticsPlus Cloud due to Custom Field Names

                      Issue The initial synchronization between ServiceDesk Plus Cloud and AnalyticsPlus Cloud failed because custom field names in ServiceDesk Plus contained backslashes (\). Error screenshot for reference Cause This is due to a limitation in the SDPOD ...
                    • Sync issue between SDP MSP and Aplus

                      Issue: Sync fails between ServiceDesk Plus MSP and AnalyticsPlus, after upgrading the SDP to 14730. Cause: An example of a case mismatch issue is when Analytics Plus seeks column alias names such as BillID, but MSP returns BILLID instead. This is a ...
                    • Upgrade issue in build 3200

                      Upgrade issue in build 3200 The below cases were identified in local system and couple of customer's system during 3200 upgrade. Issue 1: PGSQL migration fails: Since this upgrade will upgrade pgsql version, pgsql has its own upgrade prior to ...
                    • MSSQL DB Connection Password Special character issue

                      Please find the steps below to resolve the issue 1. Download the patch from here 2. Stop Analytics Plus services and make sure all the related processes are terminated. 3. Extract the patch.zip file under ManageEngine/AnalyticsPlus/, the patch will ...