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 Dim10: Error: Unable to connect to database
An error occurs when trying to connect with Desktop or Web client / Admin Console. DMDBA works.
CMS-XML Dim12.x: Deployment: Unable connect to database + Failed to lock database + Failed to connect to database
Dim12.x: Deployment: Unable connect to database + Failed to lock database + Failed to connect to database
CMS-XML KM-Dim7: How to recover datafiles in the event of 1018-DBIO: connect failed, ora-01092: oracle instance terminated the disconnection forced. error: unable to connect to database
KM-Dim7: How to recover datafiles in the event of 1018-DBIO: connect failed, ora-01092: oracle instance terminated the disconnection forced. error: unable to connect to database
CMS-XML Dim12: Deploy: Deploy server fails when starting with this error "Error: Unable connect to database @ on host in order to lock it."
Dim12: Deploy: Deploy server fails when starting with this error "Error: Unable connect to database @ on host in order to lock it."
CMS-XML MCLG: Error "Unable to open project. This server is not connected to the administration database encoded in the license key. You cannot open any projects unless the admin database host and the host encoded in the license key match exactly."
MCLG: Error "Unable to open project. This server is not connected to the administration database encoded in the license key. You cannot open any projects unless the admin database host and the host encoded in the license key match exactly."
CMS-XML Problem: User gets "unable to access project database. You may not have database permissions, or the database is missing" error connecting to a Tracker project on Oracle.
User gets the above error logging into a Tracker project on Oracle. User is using tracker / intersolv as DBMS userid / password to connect to Oracle. Using DBA userid and password works fine.
CMS-XML When logging into Mariner, user has error "Logon Failed: Unable to connect to database"
The database connection information is not correct. To verify this information, check the PPM\Mariner\web.config file. The connections are listed at the bottom.
CMS-XML Dim12: Failed to connect to the Dimensions server - ACL4502922E Error: Cannot open connection to host HOSTNAME - DBI0004527E DBIO: Database I/O error occurred ORA-28000: the account is locked
DMAPPSRV 2014/05/06 16:26:26 I P3396 T3400 Connecting to cm_typical@DIM12 DMAPPSRV 2014/05/06 16:26:26 E P3396 T3400 Pcms error: 0, Error: Unable to connect to database "cm_typical" DMAPPSRV 2014/05/06 16:26:26 E P3396 T3400 DBI0004527E DBIO: Database I/O error occurred
CMS-XML KM-Dim7: INET 7.x: "Failed to connect to database: java sql exception ioexception. Network adapter could not establish the connection."
Error appears when logging into Dimensions Inet 7.x. The message is normally triggered by Inet not being able to connect to Oracle due to an incorrect Oracle port setting in the Dimensions Inet configuration file.
CMS-XML KM-Dim7: Dimensions INet Login Failure - Failed to connect to database: java.sql.SQLException: lo exception: The Network Adapter could not establish the connection
If you are using another port other than 1521 for Oracle connections , check that your Dimensions.properties file is updated with the correct port information. If the connection port for Oracle is defined as something other than the Dimensions default of 1521 and not changed or updated in the Dimensions.properties file, this error is encountered.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs