MAG Manager login fails with an unknown error after installation

Document ID : KB000046817
Last Modified Date : 14/02/2018
Show Technical Document Details

Symptoms: 

MAG Manager login fails with the below:

mag_manager_error.png

The SSG logs will show JDBC errors such as the following:

WARNING 500 com.l7tech.server.jdbc.JdbcQueryingManagerImpl: Failed to perform querying since Table 'mag_db.oauth_token' doesn't exist

WARNING 500 com.l7tech.external.assertions.jdbcquery.server.ServerJdbcQueryAssertion: 9104: "Perform JDBC Query" assertion failed due to: Bad SQL Grammar: Table 'mag_db.oauth_token' doesn't exist

Environment:  

 Mobile API Gateway

Cause: 

 This is commonly seen when you have separated the OTK and MAG databases on Oracle or MySQL.

Resolution:

To allow for the installation of the MAG database schema on a different database than the OTK:

1. Locate the OTK Storage Configuration encapsulated assertion in:

OTK-version/PolicyFragments/configuration/

2. Open the encapsulated assertion and set the separate_schemas variable on line 15 to true.

By default, separate_schemas on line 15 is set to false as shown below.

separateSchemas.png

 

Note: Do not modify the separate_schemas variable on line 14 which applies to Cassandra database installations.