Jive Content does not have Impact Metrics - all values are zero or information is not populating.
- All content is affected - including previously created content and newly created content.
- You recently upgraded the database of the analytics server
- E.g. From Postgres 9.2 to 12.8 or Postgres 9.2 to 11.
- You have an On-Premise instance of Jive
- Your version of Jive does not officially support the new version of Postgres that you upgraded to.
- ETL Jobs have run successfully.
You need to have root user access to the Jive servers (webapp nodes and Analytics servers). You should be comfortable with database administration and the Linux command line.
Check Analytics database settings - particularly the authentication settings.
Ensure you enter the correct username and password for the database and Test Connection again.
After an hour, data should populate in Views, Viewers, Global Reach, along with a graph.
If this does not happen, check if you are seeing this error in SBS logs:
“ERROR com.jivesoftware.community.analytics.impact.task.impl.SpringBatchJobTask - org.springframework.transaction.CannotCreateTransactionException: Could not open JDBC Connection for transaction; nested exception is org.postgresql.util.PSQLException: This ResultSet is closed.”
If you are seeing it, this is because the Postgres drivers installed on your webnodes do not match the version of Postgres you upgraded to. You have 3 options at this point (listed in the preferred order):
- Upgrade Jive to the latest version (on which your Postgres version is supported).
- Downgrade Postgres to an older version (which is supported for your version of Jive).
- Upgrade the Postgres drivers to those of the version that you installed. Note - if the Postgres version is not officially supported by Jive, you may run into further errors.
Steps to upgrade the JDBC driver for Postgres.
- Download the latest Postgres JDBC driver version and transfer it to the webapp nodes.
- On each webapp node, as Jive user, create the
/usr/local/jive/postgresdirectory and copy the
postgresql-42.3.1.jarfile to the directory. Ensure the file owner is the jive user.
- On the first webapp node, set the following startup property:
jive set webapp.custom_classpath_additions /usr/lib/oracle/11.2/client64/lib/ojdbc6.jar:/usr/local/jive/postgres/postgresql-42.3.1.jar
- Confirm it by running a
jive listcommand and checking the value of the webapp.custom_classpath_additions property.
Also, check if there are password-related errors in the logs:
ERROR com.jivesoftware.community.analytics.AnalyticsUpgradeUtils - Analytics
database is enabled but a connection could not be established. Analytics upgrade
will not continue.org.postgresql.util.PSQLException: FATAL: password authentication
failed for user "username"
If yes, then:
- Disable Analytics
- Configure the analytics DB password in the system property “jive.analytics.database.password”
- Enable Analytics back.