- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-27-2018 01:13 PM
Regarding Servicenow and ODBC ServiceNow Driver error message
We recently had some users install the ODBC driver, but they get they got the message error below and a screenshot of is attached.
ERROR [HY000] [SN][ODBC ServiceNow driver][OpenAccess SDK SQL Engine]Cannot create schema.Cannot retrieve a DB schema. Please run <instance>?SCHEMA in your browser and try again. Also make sure that the table descriptor cache can hold all your tables and DB views. You can check the table descriptor stats runing <instance>/xmlstats.do in your browser.[1050]
For the resolve it had a KB article from 2016. However the property glide name looks to have changed or i can't locate it from the KB link below.
Does any one know how to get to this property so I can increase the value of the property glide.cache.size.syscache_table_descriptor to a value greater than the number of tables + the number of database views??
https://hi.service-now.com/kb_view.do?sysparm_article=KB0595630
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-04-2018 09:48 AM
OK, so these resolves were not necessary. What was necessary in this case was that I had to create a local ODBC usernane and password. As ODBC driver does not use SSO. Once I created a local user account for ODBC and gave it the ODBC role which includes the soap_query and itil roles, then we were able to sign on successfully. However, you all are correct that new properties can be created.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-27-2018 01:41 PM
Please follow below steps to create this system property
https://docs.servicenow.com/bundle/jakarta-platform-administration/page/administer/reference-pages/task/t_AddAPropertyUsingSysPropsList.html
Regards,
Sachin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-27-2018 01:49 PM
Thank you everyone!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-27-2018 01:53 PM
Hi Chenelle,
If this worked, please mark the thread closed by marking the appropriate response as correct,
Please mark this response as correct or helpful if it assisted you with your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-27-2018 02:16 PM
Once I try it, I will mark it complete and correct answer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-04-2018 09:48 AM
OK, so these resolves were not necessary. What was necessary in this case was that I had to create a local ODBC usernane and password. As ODBC driver does not use SSO. Once I created a local user account for ODBC and gave it the ODBC role which includes the soap_query and itil roles, then we were able to sign on successfully. However, you all are correct that new properties can be created.