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: Accented characters are not being preserved correctly when inserting data into tables using the Oracle SQL*Plus plugin
The key to preserving character information is for the NLS_LANG environment variable to be set correctly in the shell that runs the agent. For example:
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: 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 6.3.1 : Cannot see Components in Component mapping for Environment
DA 6.3.1 with Oracle 19 c database
CMS-XML SDA: TIPs on Maintaining an SDA Database
Oracle In the case of an Oracle database that is used with SDA, Serena recommends enabling automatic statistics gathering that will run once a week. We also recommend configuring a job that will rebuild indexes weekly or monthly depending on how much the data is changing. In any case, indexes should be rebuilt if fragmentation reaches 50% or more.
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 19 c.
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