Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML Dim CM 14.4: "Error: Unexpected end of data for COPY command" - generated when migrating a Dimensions schema from Oracle to PostgreSQL
When attempting to migrate a Dimensions schema from Oracle to PostgreSQL the following output was produced during the CRDB operation: Importing table "WSET_LISTS" ... Importing table "WSET_LISTS_LOCK" ...
CMS-XML Dim CM: Errors "DBI4404527E DBIO: Database I/O error occurred", "DBI4502580E DBC:-9999-ERROR: out of memory" and "DBI4402010E DBIO: Failed to write data to the large object" migrating schema from Oracle to PostgreSQL
During the import phase of migrating a Dimensions CM schema from Oracle to PostgreSQL the following errors occurred part way through importing the tables: DBI4404527E DBIO: Database I/O error occurred DBI4502580E DBC:-9999-ERROR: out of memory
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."
Collage requires the Java option in Oracle. This will need to be installed before migrating to Oracle. This is an installation component of Oracle.
CMS-XML KM-Dim7: Error: Index [] out of range on migration wizard upload
During a Data Migration Wizard upload script generation the error: 'Index [] out of range' may be recieved. This means one of the item types specified is invalid, i.e. it does not exist in the database being uploaded to.
CMS-XML KM-Dim7: Error: Migration error: 1019-DBIO Oracle Error Occured
or ORA-1652 unable to extend temp segment by 10240 in tablespace PCMS_DATA The problem with the above two error messages is that the database user is attempting to tablespace PCMS_DATA for temporary operations
CMS-XML Dim CM 2009 R1: DS migration - migration errors occur when LSR data is out of sync with Dimensions
To prevent these errors , you must refresh the data in the LSR by manually running the appropriate SQL script against the DSN of the DS database . These scripts are located in the same directory as the migration tool.
CMS-XML Mariner Administrator gives error "Logon Failed: Could not get database version information" after upgrade
Mariner gives error "Object reference not set to an instance of an object" Mariner 2008 R2 Migration tool gives the following message during the migration : -- Insert the new view if it does not already exist
CMS-XML DS2DIM 2009R1: Error when trying to migrate files which start with a # in the file name
Importing Item "MIG:1PG DOC.A-DOC;1" DBI0004527E DBIO: Database I/O error occurred SQL-1400(3501) ORA-01400: cannot insert NULL into ("MIGCHMAN"."ITEM_SPEC_CATALOGUE"."LIB_FILENAME")
CMS-XML DS2DIM 2009R1: DS2DIM migration tool tries to insert strings into numeric fields against DB2
Running the DIM 2009 R1 DS2DIM migration tool against a DB 2 ChangeMan DS database the migration fails with errors that some INSERT statements into the MIG_* tables fail. It turns out that these insert statements are incorrect and are trying to insert strings into numeric DB fields. This means the migration fails.
CMS-XML ChangeMan ZMF 8.2 Patch 4 Db2 Option: Required migration job DB2ALTER missing from early versions of documentation
ZMF Db2 option customers upgrading to ZMF 8.2 Patch 4+ must run the DB2ALTER job as a part of their upgrade, prior to re-binding CMNDB2AD. This job is missing from early versions of the 8.2 Patch 4 documentation (e.g. Readme and/or Migration Guide). Failure to run this job will result in the bind of CMNDB2AD failing with a RC=12 and the following type of errors :
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs