Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML ORA-12154: TNS:could not resolve the connect identifier specified
(1) This can occur if the customer is using a 32-bit ODBC driver to connect to 64-bit Oracle server. Only certain actions will trigger this message. We recommend using the 32-bit ODBC with 32-bit Oracle server. (2) Use of the Oracle Instant client 11.1 with SBM 2008.
CMS-XML KM-Dim10: Unable to log into DMCLI or Upload utilities
DMAPPSRV 2007/03/20 10:21:13 E P2944 T1432 DBI0004527E DBIO: Database I/O error occurred ORA - 12154 : TNS : could not resolve the connect identifier specified Error: Unable to connect to database "QLARIUS_CM"
CMS-XML Some Dim Clients give error "Failed to start Dimensions server process"
DBI0004527E DBIO: Database I/O error occurred ORA - 12154 : TNS : could not resolve the connect identifier specified DBconnectToDBMS: Status - -1
CMS-XML Dim14: DMCLI: Unable to connect to Dimensions CM from DMCLI when using -dbname basedatabasename@SID
This is because if the -dsn parameter is no longer supplied, Dimensions will work out the Oracle SID name add add it to the dbname value, which would mean a connection string containing the database identifier twice. Here's a snippet from the log files:
CMS-XML KM-Dim7: ORA-12154 TNS could not resolve Service name when trying to connect with Process Modeler
Note, if user has a Dimensions AIX Unix Client that already has its own Oracle client installation for another application,
CMS-XML KM-Dim9: ORA 12154 - TNS Could not resolve service name - Desktop Client
Some sites are not allowed to ping servers. In this case test the connection by entering the fully qualified hostname of the server into the 'Server' textbox. <>
CMS-XML Dim: Oracle cannot connect: ORA-12537 TNS:connection closed
(SERVER = DEDICATED) (SERVICE_NAME = DIM14) Restarted the listener and the problem was resolved .
CMS-XML Internal Solution Dim14: Pulse: When attempting to access Pulse, a 404 error occurs and the logs show Listener refused the connection with the following error: ORA-12505, TNS:listener does not currently know of SID given in connect descriptor
The above error will occur if Oracle has not completely started, whilst Tomcat was initializing the Pulse servlet. Tomcat needs to be restarted in order to resolve the issue.
CMS-XML Unable to connect to Oracle using CU or ODBC Admin
In TNS _Names, we specified MASHUP2009 to MASHUP2009 + the domain listed in names.default_domain, e.g, Then, update the MASHUP2009 ODBC connection using ODBC Admin to update the net service name.
CMS-XML ORA-12154: Failed to connect to database
Creating a Oracle data source fails with the error ORA-12154. Checking with Google it means It could not resolve the service name.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Delivering changes from a work area to a stream (demonstration)
This demonstration shows you how to deliver changes from a work area to a stream in Dimensions CM, restrict the deliver to specific folders in the work area, and relate a new item to the correct design part.
Dimensions CM: Resolving conflicts (demonstration)
This demonstration shows you how to resolve conflicts between your work area files and the item tip revisions in a stream in Dimensions CM

Additional Assistance

  • Submit a Case Online
  • FAQs