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 MCLG: How to rebuild Sybase admin and project databases in Collage
MCLG: How to rebuild Sybase admin and project databases in Collage
CMS-XML MCLG: When migrate the admin database or project database to Oracle , get error "ORA-06550: line 1, column 7: PLS-00201: identifier 'DBMS_JAVA.GRANT_PERMISSION' must be declared" or "Roll 'Java Admin' does not exist."
MCLG: When migrate the admin database or project database to Oracle , get error "ORA-06550: line 1, column 7: PLS-00201: identifier 'DBMS_JAVA.GRANT_PERMISSION' must be declared" or "Roll 'Java Admin' does not exist."
CMS-XML MCLG: Bundled Sybase Server: Do Not Rename Database Files
If you purchased the bundled Sybase database server, and you want to rename your project database , do not attempt to manually rename the physical database files themselves. You will be unable to load the database files if the names are changed.
CMS-XML MCLG: Using Collage with a Microsoft SQL Server 2000 named instance
Collage can store its admin and/or project databases on a named instance of Microsoft SQL, but the connection information must be entered correctly for the JDBC driver.
CMS-XML MCLG 5.1.1: "SQL error: Authentication violation" error when rebuilding Sybase projects.
This error happens in Collage 5.1.1 when trying to rebuild a Sybase project database . IMPORTANT:
CMS-XML MCLG: Backup guidelines for project and admin databases
A scheduled backup should be run every night. The backup process should place the backup files into a folder other than were the live project database files are located. Then, the backup copy of the database files should be copied to tape.
CMS-XML MCLG: Backing up databases when using MSSQL as the database server appends to the backup file.
backing up the project or admin database via the System | Setup screen in Collage this causes the resulting backup file on the MSSQL server to be appended to the last backup instead of overwriting an existing backup. For instance if the project database was 5 mb in size the first time a backup was initated, the resulting .bak file would be about 5 mb.
CMS-XML MCLG: Why are Oracle sessions/connections left open for so long?
A single asset deploy will kick off a deploy activity which will open the project (allocating 2 connections) and a connection to the admin database for a total of 3 connections. Since the person who started the deploy is using the UI which also uses a connection to the admin and project databases to refresh the view, a total of 5 connections are used. Open project should NOT allocate 2 connections.
CMS-XML MCLG: How to move existing Collage projects, users and groups to a new Collage server or installation.
Create a backup of the project database either using Collage's backup tool (System | Setup | Projects | Backup) or the standard MSSQL tools. This will create a .bak file.
CMS-XML MCLG 5.1+: Using and configuring Collage cache to improve deploy and preview performance
This cache was created in order to quickly retrieve converted documents rather than converting them on-the-fly. The location of this cache is in the project's database . Once a version of an asset has been converted, Collage stores a binary copy of the converted document in the database.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs