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 DA: Getting Oracle 1400 errors in output log
In this situation, the cause of the problem was that the schema had been upgraded to a higher release number than the version of DA software running. It is likely that DA was upgraded and then restored back to a previous version without restoring the database schema back to the previous version. Therefore, the database had new columns and constraints that the DA software was not able to handle.
TEXT 20083476.txt
2664281.1) Oracle Database - Enterprise Edition - Version 12.2.0.1 and later Information in this document applies to any platform. SYMPTOMS Running a complex query with nested joins can fail with the following error: ORA -07445: exception encountered: core dump [qkacco()+91] [SIGSEGV] The Call Stack Trace in the associated incident trace file shows: ... qkacco <- qkajoi <- qkaqkn <- qkadrv ... CHANGES Database was upgraded to 19c.
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.
DA: Unable to connect to DA following a change of Oracle password for the DA schema. ORA -28000 found in the Tomcat 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 DA615: DA Report hangs with large number of environments and other database objects
- SQL Error: 1795, SQLState: 42000 2018-01-18 11:34:37,476 - ORA -01795: maximum number of expressions in a list is 1000
PDF Serena Deployment Automation Guide
JMS_PORT 7918 Server port DB_TYPE derby Use to specify a database vendor other than the default: MYSQL| ORA |SQLSVR 58 Serena® Deployment Automation
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.
MS-WORD Mitigating POODLE in Serena Deployment Automation.doc
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 and may allow a man-in-the-middle to intercept parts of SSL encrypted communications. This has the potential to affect any SSL encrypted communications and thus requests to communicate with Serena Deployment Automation (SDA) are affected.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs