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 SBM 10.x database upgrade to SBM 11.x gives error "Failed to upgrade Orchestration Engine database. Connection to the Application Engine server has timed out."
SBM 10.x database upgrade to SBM 11.x gives error "Failed to upgrade Orchestration Engine database. Connection to the Application Engine server has timed out."
CMS-XML Dim12: Get error when deploying: PRG4500325E Error: User authentication failed
2 PRG4500325E Error: User authentication failed NET4502575E Failed to obtain a connection to database basedb@dsn on host server as user username. Launching DEPLOY job 12143328
CMS-XML DMCM: Pulse connection failure following manual upgrade to 14.x
After upgrading to Dimensions 14.x from a release prior to 14.1 using the manual DMDBA method, the PULSE user is normally created manually as indicated in the installation documentation, and this user subsequently has database objects created when the first connection is made to Pulse. However, if this is not happening and the objects in the Pulse schema are not created in the database , this indicates that the database.jdbcurl is not set correctly.
CMS-XML Dim cm 14.4 : installation on Centos with local postgres fails with this message "dm_psql: could not connect to server: Connection refused"
PostgreSQL port: [5432] PostgreSQL Database name: [dim14] PostgreSQL User name: [postgres]
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 Dim14: Pulse: JDBC driver connections, database service name vs SID
jdbc:oracle:thin:@//<HOSTNAME>:1521/<SERVICE_NAME> As a last resort, if all else fails and if you do not anticipate using clustering in future, then it is possible to use the older JDBC URL syntax of: jdbc:oracle:thin:@<HOSTNAME>:1521:<SID>
CMS-XML Database Upgrade -- SBM Upgrade Fails
Click the upgrade link to upgrade your AE database (or do the upgrade in the SBM System Administrator in pre 10.1.3. Be sure to verify your connection information in System Administrator)
CMS-XML Error "InitExtension Failed" when logging into the SBM User Workspace
Enter these values and click Next to test the connection. If this gives an error, work with your DBA to resolve the connection between the database and the server first. Then, continue with the next steps.
CMS-XML How to enable SBM to communicate via SSL with a SQL Server database
The current versions of SBM will fail to connect to to the SQL Server database even after updating the JDBC connection strings. The issue is related to changes made to Oracle's JRE 1.6 update 29+ which is the version used in SBM 10.1 and higher. The change was made to fix the SQL Server "Beast" security issue.
CMS-XML How to enable SBM to communicate via SSL with a SQL Server database in SBM 11.x
The current versions of SBM will fail to connect to to the SQL Server database even after updating the JDBC connection strings. The issue is related to changes made to Oracle's JRE 1.6 update 29+ which is the version used in SBM 10.1 and higher. The change was made to fix the SQL Server "Beast" security issue.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs