Guest

Preview Tool

Cisco Bug: CSCvs55123 - After a successful upgrade, SM fails to display chat/email data for sessions from before the upgrade

Last Modified

Jan 08, 2020

Products (1)

  • Cisco SocialMiner

Known Affected Releases

11.6(2)

Description (partial)

Symptom:
In some cases, after a successful upgrade of the SocialMiner node, the SM Admin page does not display any data for the chat/email sessions from before the upgrade.

However, newly created chat/email sessions show up correctly without any issues.

In such cases, the old chat/email sessions' age is NOT older than the configured 'purge older than' setting in the SM Datastore Purge Settings

Conditions:
On SocialMiner, during the switch version, the social contacts' data from Cassandra database is dumped into flat files and then imported back onto new version.

However, in some cases, the re-import of data from the flat file fails and thereby causing SM to not display any chat/email records

Example:
======
Upgrade from 10.5 to 11.6.2

## From the export_ccp_datastore_tables.log, export of data appears to be successful.
- Thu Oct 24 21:50:11 CDT 2019: 10,000 number of social contacts exported successfully to SocialContact-part0 in 3 secs
- Thu Oct 24 21:50:14 CDT 2019: 2,630 number of social contacts exported successfully to SocialContact-part2 in 0 secs
- Thu Oct 24 21:50:14 CDT 2019: 10,000 number of social contacts exported successfully to SocialContact-part1 in 2 secs
- Thu Oct 24 21:50:15 CDT 2019: 10,000 number of social contact links exported successfully to SocialContactLinks-part0 in 0 secs
- Thu Oct 24 21:50:16 CDT 2019: 10,000 number of social contact links exported successfully to SocialContactLinks-part1 in 0 secs
- Thu Oct 24 21:50:16 CDT 2019: 2,630 number of social contact links exported successfully to SocialContactLinks-part2 in 0 secs
- Thu Oct 24 21:50:18 CDT 2019: 10,000 number of social contact report records exported successfully to SocialContactReportRecords-part0 in 0 secs
- Thu Oct 24 21:50:21 CDT 2019: 10,000 number of social contact report records exported successfully to SocialContactReportRecords-part1 in 0 secs
- Thu Oct 24 21:50:21 CDT 2019: 1 number of social contact interval records exported successfully to SocialContactIntervalRecords-part0 in 0 secs
- Thu Oct 24 21:50:21 CDT 2019: 2,638 number of social contact report records exported successfully to SocialContactReportRecords-part2 in 0 secs
- Thu Oct 24 21:50:21 CDT 2019: 5 number of Predefined Response records exported successfully to PredefinedResponse-part0 in 0 secs
- Thu Oct 24 21:50:21 CDT 2019: Total export time 17 secs

## However, during the subsequent import of the backed up data; insertion of every record of every backed up table fails with the following exception:

++ From import_ccp_datastore_tables.log,
- com.datastax.driver.core.exceptions.SyntaxError: line 1:1472 mismatched character '<EOF>' expecting set null
-         at com.datastax.driver.core.exceptions.SyntaxError.copy(SyntaxError.java:66)
-         at com.datastax.driver.core.DriverThrowables.propagateCause(DriverThrowables.java:37)
-         at com.datastax.driver.core.DefaultResultSetFuture.getUninterruptibly(DefaultResultSetFuture.java:214)
-         at com.datastax.driver.core.AbstractSession.execute(AbstractSession.java:52)
-         at com.datastax.driver.core.AbstractSession.execute(AbstractSession.java:36)
-         at com.cisco.ccbu.ccp.datastore.migration.cassandra.CassandraDSImportStep$1.run(CassandraDSImportStep.java:115)
-         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
-         at java.util.concurrent.FutureTask.run(FutureTask.java:262)
-         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
-         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
-         at java.lang.Thread.run(Thread.java:745)
- Caused by: com.datastax.driver.core.exceptions.SyntaxError: line 1:1472 mismatched character '<EOF>' expecting set null
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.