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 Error when creating a new database through the Admin Module
Error when creating a new database through the Admin Module
CMS-XML Error: DB-Library Network Communications Layer not loaded
Error : DB -Library Network Communications Layer not loaded
CMS-XML KM-Dim9: Replicator: Error: Replication could not load the details for the current database.
KM-Dim9: Replicator: Error : Replication could not load the details for the current database .
CMS-XML VM:VSS2PVCS:Error: The project root could not be loaded: "<path>". An error occured while importing archives to the VM database: <path>
VM:VSS2PVCS: Error : The project root could not be loaded : &quot;&lt;path&gt;&quot;. An error occured while importing archives to the VM database: &lt;path&gt;
CMS-XML KM-Dim9: Replicator: Error: Failed to load replication log into database.
This error will usually be accompanied with another message detailing the reason why the load failed.
CMS-XML Transitioning items give error: DB Exception when loading cache. Data truncated.
SQL: select TS_SYSTEMSETTINGS.TS_ID,TS_SYSTEMSETTINGS.TS_NAME,TS_SYSTEMSETTINGS.TS_DATATYPE,TS_SYSTEMSETTINGS.TS_LONGVALUE,TS_SYSTEMSETTINGS.TS_STRINGVALUE, Data truncated. An exception occurred while attempting to load the 'TS_SYSTEMSETTINGS' table cache.
CMS-XML Dim12: Upgrade: Database schema update fails: ACL4501561E Error: Could not load library libdbio_srv_odbc.so
ACL4501561E Error : Could not load library libdbio_srv_odbc.so: ld.so.1: dmdba: fatal: libodbc.so.1: open failed: No such file or directory.
CMS-XML Error: #1110 Oracle 7.x - ODBC.DLL - Specified driver can not be loaded
Customers may have difficulty getting Tracker 3.0+ to connect to Oracle 7.x databases . In addition to the instructions in the document titled: PVCS AnswerLine #814: Troubleshooting an Oracle 7 connection, be sure to carefully note the following.
CMS-XML Unable to load relation 'common' and Common Log won't show anything in Repository when using Oracle db.
When accessing the Common Log from the Repository we get an error of: Unable to load relation 'common'. Internal Server Error (500)
CMS-XML Error: #35: DB path for file name is too long ...
The location of the Tracker executables are buried too deep in the directory structure. Choosing a different directory for the database server for Tracker to use does not solve the problem. Neither does moving the Tracker 2.1 (or 2.2) project.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs