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
Article Product Downloads and Documentation Link
Please visit our products downloads page to obtain documentation on your product. For particular articles regarding your issue, try making your search more specific.
CMS-XML SBM: About the "Clear History" feature used to schedule Common Log cleanup (Delete Common Logger)
If it gets even bigger, it may not be possible to open the log at all. Also, this log is taking space in your database . The more full the log becomes, the larger your database.
CMS-XML Changing Common Log Database in Configurator automatically changes Application Engine Database
Steps to reproduce: - In Configurator on the Database Servers Tab make sure both Application Engine and Common Log ODBC data sources use the same data source - all components use the sample DB
CMS-XML Unable to load relation 'common' and Common Log won't show anything in Repository when using Oracle db.
When accessing the Common Log from the Repository we get an error of: Unable to load relation 'common'. Internal Server Error (500)
CMS-XML The Common Log does not report Application Engine messages when using Oracle as your database
When using an Oracle database, the wrong database driver may be recorded in the LoggerConf.xml file (located here: \Business Mashups\Application Engine\LoggerConf.xml). Therefore, the Common Log in Mashup Manager will not report Application Engine messages once Business Mashups is running.
CMS-XML Lists of Forms and Scripts are re-ordered in Composer after copy db
Lists of Forms and Scripts are re-ordered in Composer after copy db
CMS-XML Composer: allow underscores in DB names
Underscores were not allowed in Field DB Names in Mashup Composer
CMS-XML After upgrade Composer fails to validate if table database name >24 characters. Worked in previous version.
After upgrade Composer fails to validate if table database name >24 characters. Worked in previous version.
CMS-XML File-Attributes have a strange dbName in WebService, e.g. "File: nnn", and not the DB-Name as defined in the composer.
File-Attributes have a strange dbName in WebService, e.g. "File: nnn", and not the DB -Name as defined in the composer .
CMS-XML Log orchestration category of logs to a file rather than the Common Log
At times, it may prove useful to have orchestration logging written to a file instead of the Serena Common Log database . These steps will help do this. Care should be taken to not leave in debug mode as the log file can grow out of control quickly.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs