Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Unable to connect to Oracle using CU or ODBC Admin
Unable to connect to Oracle using CU or ODBC Admin
CMS-XML Install: What is Tracker looking for when it installs ODBC drivers?
Install: What is Tracker looking for when it installs ODBC drivers?
CMS-XML Microsoft Excel 2007 hangs when trying to make an odbc connection to Mariner 6.2
Microsoft Excel 2007 hangs when trying to make an odbc connection to Mariner 6.2
CMS-XML Why don't I have access to the features in the new Application Administrator that I used to access via ODBC?
Why don't I have access to the features in the new Application Administrator that I used to access via ODBC ?
CMS-XML Install: #1109 "An error occurred while copying the ODBC x:\\windows\install.hlp file...."
Install: #1109 "An error occurred while copying the ODBC x:\\windows\install.hlp file...."
CMS-XML PRO8 TRKINET Database information is not complete. Error: SQL state = 08003 (Microsoft) ODBC driver manager Connection Not Open
PRO8 TRKINET Database information is not complete. Error: SQL state = 08003 (Microsoft) ODBC driver manager Connection Not Open
CMS-XML Dim12: Upgrade: Database schema update fails: ACL4501561E Error: Could not load library libdbio_srv_odbc.so
Dim12: Upgrade: Database schema update fails: ACL4501561E Error: Could not load library libdbio_srv_ odbc .so
CMS-XML Database Clients and Drivers for SBM
This solution contains important information about the database clients and ODBC drivers that are supported with SBM. Before you install SBM, validate that the DBMS is installed correctly, and that you can successfully establish a connection from the server that hosts SBM Application Engine. For SQL Server systems, install the SQL Server client on the SBM Application Engine Web
CMS-XML Data Direct driver for exclusive use with SBM
A custom API program accessing the SBM Database through the Oracle for SBM driver will give the following ODBC error message:
CMS-XML Error "ORA-28040: No matching authentication protocol" when connecting to Oracle
ODBC connection to Oracle fails, and the following error appears when you attempt to connect to an Oracle 12c, 18c and 19c databases: [SBM][ODBC Oracle Wire Protocol driver][Oracle]ORA-28040: No matching authentication protocol When you attempt a test connection on the Database Server tab in SBM Configurator, it will fail as well.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs