The following checks need to be performed to troubleshoot an EDM connection issue to ensure the configuration is correct:

• Check the connection by ensuring that you can ping the database server from the Breeze cluster node.

• Verify the database user specified in the attribute EDM: Username in System Manager has read/write access to the CS_OPERATION table and the CS_PROVISION table.

• Verify the specified database name matches with the database name specified for the associated attribute in System Manager.

• The database may have a provision enabled which locks the db user account if incorrect login credentials are used. This will require the db user's account to be specifically unlocked. This should be done after the credentials have been updated in System Manager as the system will consistently attempt retries with the incorrect details otherwise. The system will continue to retry the connection even if the db user account is locked.

• Check that the JDBC driver in System Manager is under JDBC providers. Postgres does not require a driver to be loaded in System Manager. For Oracle or MS SQL server verify that the driver is compatible with the version of the database.

• Verify the following System Manager attributes are set for ContextStoreManager:

  Attribute name	Required Value/Format	Sample value	Notes
  EDM: Enable Persistence to database	True or False	True	This must be set to true to enable EDM
  EDM: Database type	PostgreSQL Oracle Microsoft SQL Server	PostgreSQL	The type selected must match the database.
  EDM: Database host	Host address for External Data Mart database.	10.20.30.40
  EDM: Database port	Port for External Data Mart database.	5432
  EDM: Database Name	Name of the database used as External Data Mart.	csedm	Ensure that the configured database name matches the actual name of the created database.
  EDM: Username	Username for the External Data Mart database connection	edm_user
  EDM: Password	Username for the External Data Mart database connection	edm_password	Verify in DB admin tool that the DB user has access to the CS_OPERATION table
  EDM: Mirror Service container size	Memory required for the External Data Mart Mirror Service deployment. Numeric value only is interpreted as GB. MB can be specified with an ‘m’ or ‘mb’ after the number. Example, 128m	128m	If this allocation is invalid then the EDM PU will not deploy.

• Verify the following System Manager attributes are set for ContextStoreQuery:

  Attribute name	Value	Sample value	Notes
  EDM: Username	<db_username>	edm_user	This is the same value set in ContextStoreManager attributes
  EDM: Password	<db_user-password>	edm_password	This is the same value set in ContextStoreManager attributes

• Debugging

  1. Verify that the EDM PU is deployed in Gigaspaces.

  2. Check the logs located at /var/log/Avaya/services/ContextStoreManager/ContextStoreManager.log.

     Error	Cause	Solution
     org.jini.rio.core.JSBInstantiationException: org.hibernate.HibernateException: Missing column: touchpoint in public.cs_provision	The schema in the table is incorrect and is missing the field specified in the error message (in this case the 'touchpoint' field)	Verify that both table schemas match the schemas in the Context Store documentation. Different release versions of the software have different schemas. Ensure the documentation you use is the same version as the Context Store running on the system.
     2018-08-15 15:14:47,905 GSC SEVERE [com.gigaspaces.grid.gsc] - Failed to instantiate ContextStoreSpace.5 [1]; Caused by: org.jini.rio.core.JSBInstantiationException: org.hibernate.HibernateException: Missing table: CS_PROVISION	The system is trying to run an SQL command against a table that does not exist in the database or does not have read/write permissions.	Verify that the table exists in the database specified in the SMGR attributes. Verify that the dbuser does not have the required permissions to view the table. Double check that the attributes in the SMGR are not being pointed to the wrong database. Changing the db password on the database server and also in the SMGR attributes and rebooting will result in a connection error if it is the wrong database.

• Specific Database Issues

  If you are using Microsoft SQL server DB user:

  • The db user configured for the EDM feature must have database ownership or the system administrator privileges for this connection to be successful.

  • From the security profile of the database user, you must set the Context Store database as the default database for this user.

  If you are using the Oracle Analytics Database for your EDM then verify that the database account is accessible.

  Test out the database user login via sqlplus on the console or via Oracle SQL Developer (or another DB Admin Tool) to ensure that the user account can access the database. The default database details for Oracle DB in Analytics are:

  username*	context_store
  password*	ContextStoreAv33
  database name / SID	orcl
  port	1521

  Note:

  These are the default values in the base_install.sql and may have been updated prior to installation.

  Use Case	Error	Cause	Solution
  Logging in to the database directly as Context Store user.	ORA-28000	Context Store has made multiple attempts to open a DB connection with invalid credentials and the database has locked the accout as a result.	Login in to sqlplus as sysdba. Run the query ALTER USER <<user_name>> identified by <<user_password>> ACCOUNT UNLOCK;
  Logging in to the database directly as Context Store user.	IO Error: The Network Adapter could not establish the connection	Unknown	Reboot the node because there are issues with the database.
  Logging in to the database directly as sysdba user.	ERROR: ORA-09817: Write to audit file failed. Linux-x86_64 Error: 28: No space left on device. Additional information: 12 ORA-09945: Unable to initialize the audit trail file Linux-x86_64 Error: 28: No space left on device.	Disk is full. Check if /var/log/audit is full.	Check log files.
  ContextStoreManager is able to connect to the database. ContextStoreQuery is able to connect to the database. The EDM PU is not able to persist context to the database.	ORA -01005: null password given; logon denied.	The oracle driver used is incompatible.	The tested and supported Oracle driver versions for Context Store are : Context Store 3.4 and above - ojdbc6 driver version 11.2.0.4 ONLY Context Store 3.5 and above - ojdbc6 driver version 11.2.0.4, 12.1.0.1, 12.1.0.2

• API Validation

  1. Download and install the POSTMAN web client using the Chrome browser.

  2. Download the Context Store Postman Request Collection on DevConnect.

  3. Import the ContextStore3.5.postman_collection.json file into the POSTMAN client.

  4. Within ContextStore3.5.postman_collection.json, run Create Persisted Context

     This runs using the ContextStoreRest interface.

  5. Verify that the context is persisted to the database.

  6. Use the ContextStore3.5.postman_collection.json to check that the context can be retrieved through the ContextStoreQuery interface.

• MIcrosoft SQL Server DB User

  If you are using Microsoft SQL Server:

  • The db user configured for the EDM feature must have database ownership or the system administrator privileges for this connection to be successful.

  • From the security profile of the database user, you must set the Context Store database as the default database for this user.

• Oracle Database

  If you are using an Oracle Database:

  • The Oracle driver being used must be compatible with the version of the Oracle database.

  • From Context Store 3.5 onwards, the tested and supported Oracle driver version for Context Store is ojdbc6 driver version 11.2.0.4, 12.1.0.1, 12.1.0.2 which are all available in Oracle Database JDBC Downloads webpage.

  • There should only be one Oracle driver installed on the cluster, if the driver has been changed, the nodes must be rebooted.