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 Some statements in the VSS conversion documentation are not consistent with the behavior
Some statements in the VSS conversion documentation are not consistent with the behavior
CMS-XML Build receiving error: /ecm/build/2955: syntax error at line 8;`$' unexpected
When executing a build on a UNIX server with a compile statement such as "$(JAVAPATH)/javac -classpath $(ECM_CLASS) *.java", Build receives error: /ecm/build/2955: syntax error at line 8;`$' unexpected. The exact same compile statement successfully built in previous versions of ChangeMan DS. JAVAPATH and ECM_CLASS variables are set in the root's environment.
CMS-XML No upgrade instructions for clients and Communication Agents
There are no instructions for upgrading clients and communication agents. There should be installation steps, and also some statement that along with the main server all clients and communication agents should be upgraded so there is no client/server conflicts.
CMS-XML Incorrect version for Make dependencies after mainanance of the frozen release
The following work-around suggested: The following SQL statement will fix the problem. update vcs19 set depend_depend_version=0 where depend_project='PROJ' and depend_release='REL' and depend_proc='MAKE'
CMS-XML What type of access to area directories is needed for user IDs
The statement in the Security chapter has been modified as follows:
CMS-XML The documentation for JBuilder 8 integration doesn't clearly state that you should use the Status Browser to view the version control status of files
The last step for each SCM activity has been changed to remove the statement about options being enabled or disabled and to add the following statement instead:
CMS-XML Are Serena products affected by the OpenSSL Heartbleed Bug?
A formal statement will be issued to Serena customers, at which time this article will be updated as appropriate.
CMS-XML Failed to create transaction record in audit trail database
ORA-01652 unable to extend temp segment by string in tablespace string Cause: Failed to allocate an extent for temporary segment in tablespace. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.
CMS-XML LDF or Transaction Log in SQL Server 2000 consistently grows in size and needs to be shrunk.
You must run a BACKUP LOG statement to free up space by removing the inactive portion of the log. You must run DBCC SHRINKFILE again with the desired target size until the log file shrinks to the target size. The following example demonstrates this with the pubs database and attempts to shrink the pubs_log file to 2 MB:
CMS-XML Message file not found
Make sure the script has permission to execute (chmod 755 script.sh). This may need to be done as part of the Compile statement .
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs