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 DIM CM: Upgrade installer fails with: Unable to connect to the Oracle database
When the installer fails to connect to your existing Oracle DB during an upgrade it is possible that the Oracle SID stored in the registry is incorrect. The value to check is:
CMS-XML Can't add a web connection to an already upgraded PO 4.2 database
1.) installed POWEb 2.) Create Web connection using POSecurityAdmin/pacedge Receive error message: "The specified database is not a Project Office 3.0 database"
CMS-XML Dim: Dimensions cannot connect to Oracle database. user gets error ORA-28000: the account is locked
Attempts to connect via sqlplus also get the same ORA-28000 error. Have the DBA unlock the Oracle user and the error still continues
CMS-XML When run report from Visual Studio or Report Server, get error "A connection cannot be made to the database. Object reference not set to an instance of an object"
When run report from Visual Studio or Report Server, get error "A connection cannot be made to the database . Object reference not set to an instance of an object"
CMS-XML Dim14: VRS: Error: unable to connect to the specified DBMS
After starting the VRS Upgrade GUI and then entering in the credentials for the database , the following error was received: Error: unable to connect to the specified DBMS
CMS-XML KM-Dim10: Unable to connect to basedb after upgrade to 10.1.1 - basedb password not default
There are three possible solutions: If the database passwords are known, then reset them using sqlplus: sqlplus system/<password>@<instance>
CMS-XML Dim12: Upgrade: Database schema update fails: ACL4501561E Error: Could not load library libdbio_srv_odbc.so
Error: unable to connect to the specified DBMS. A manual dmdba connection reports dmdba system/password@dimde1
CMS-XML Oracle: Error "select statement could not be read from the 'Attachments' table" during database upgrade to TeamTrack 6.6.1
During upgrade to TT661 on a new Windows2003 server, connected to Oracle server, error ".... select statement could not be read from the 'Attachments table'", as the following screenshot
CMS-XML Report server cannot connect to Mariner App server by name - Query execution failed for data set 'xxxxx'
The setup of Mariner and Microsoft SQL Reporting Services (SRS) requires that both servers can initiate communication with each other. Mariner makes a call to the SRS server which in turn makes calls to the database via a data source that is setup in SRS. All calls to the Mariner database are processed through the Mariner Web application server.
CMS-XML Composer error - connection attempt failed. Could not connect to the Repository. Please check that the connection settings are correct. Underlying error: (No compatible tokens found on the request).
One scenario that will cause this error is if SBM is started and the database is not available at that time. If you start or make the database available after SBM is started the User Workspace UI will recover gracefully and the SBM UI will work as expected but Composer ( Tomcat / JBoss ) isn't able to gracefully recover from this situation causing Composer to throw the error above.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs