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 Authentication Required when access localhost:8080
It appears to be port conflict issue that port 8080 is in use by another program ( Oracle XDB services uses the port number 8080) To resolve this, we need to change DA tomcat to use another port: 1. Stop Tomcat
CMS-XML DA: Unable to connect to DA following a change of Oracle password for the DA schema. ORA-28000 found in the Tomcat log.
// *Cause: The user has entered wrong password consequently for maximum // number of times specified by the user's profile parameter // FAILED_LOGIN_ATTEMPTS, or the DBA has locked the account
CMS-XML DA: Getting Oracle 1400 errors in output log
DA: Getting Oracle 1400 errors in output log
CMS-XML DA: DA fails to start correctly if Oracle identifier contains a hyphen
DA: DA fails to start correctly if Oracle identifier contains a hyphen
CMS-XML DA 6.1.5 Cannot Oracle install published views
DA 6.1.5 Cannot Oracle install published views
CMS-XML DA: Accented characters are not being preserved correctly when inserting data into tables using the Oracle SQL*Plus plugin
DA: Accented characters are not being preserved correctly when inserting data into tables using the Oracle SQL*Plus plugin
CMS-XML SDA 6.1.2: Installation alters ownership on more folders than it should
This change in ownership particularly affected Oracle and prevented the database from starting up. Once the Oracle files and folder ownership was reset to user oracle the database could be started. Once Tomcat was started a connection could be made to the database and the SDA schema was upgraded successfully.
PDF Serena Deployment Automation Guide
<DB>_USER serena_ra Database user ID, where <DB> is: DERBY|MYSQL|ORA|SQLSVR <DB>_PASSWORD password Password for database user ID, where <DB> is: DERBY|MYSQL|ORA|SQLSVR ORA_DB_SCHEMA ( Required for Oracle ) Database schema
TEXT 20083476.txt
it seems there is a bug in Oracle related to how you connect to the DB or run joins. It might be something to look into for your R&D team, i will post the details below from our DBA's, we have changed the settings and the error seems to be gone. SDAPROD, error we are getting.
CMS-XML SSL 3.0 Vulnerability - Poodle
A new security vulnerability called POODLE (Padding Oracle On Downgraded Legacy Encryption) is currently in the news. This is the result of a flaw in the SSL 3.0 protocol and the specific attack affects web communications. This has the potential to affect any web server and thus requests to communicate with various Serena products.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs