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 SDA: How to migrate from Derby to Oracle or Microsoft SQL Server
SDA: How to migrate from Derby to Oracle or Microsoft SQL Server
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
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
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 Dim CM 14.4: "Error: Unexpected end of data for COPY command" - generated when migrating a Dimensions schema from Oracle to PostgreSQL
The schema had previously been upgraded successfully to 14.4 whilst in the Oracle database . There were no errors performing the initial dump of the data.
PDF SDA: Migrating from Derby to Oracle
Step 2: Install the Database JAR file in the Migration tool On Oracle Simply copy the Oracle JDBC from the current Oracle installation into the Migration directory
CMS-XML SBM 10.x and above: How to migrate your SQL Server or Oracle database to another supported DBMS
Note the following: This document assumes you have a running and working SBM environment that is currently connected to either SQL Server or Oracle . For SBM 11.6 and higher: A fully-supported and tested database migration strategy for moving to Postgres is incomplete.
CMS-XML KM-Dim7: Error: Migration error: 1019-DBIO Oracle Error Occured
ORA -1630 max # extents (99) reached in temp segment in tablespace PCMS_DATA or ORA-1652 unable to extend temp segment by 10240 in tablespace PCMS_DATA
CMS-XML 10.1.x / Oracle 10g : why requiring to set UNDO_MANAGEMENT to MANUAL ?
user is in the process to migrate from Dimensions 8 to 10.
CMS-XML DMCM 2009R2: DMDBA MIGRATE fails if attribute values contain certain chars
When trying to convert a WE8ISO8859P1 database to UTF-8 using the migration utility in DMDBA, an Oracle is reported error ORA -01756: quoted string not properly terminated. This reported if an object has an attribute that contains a string the has a semi-colon (;) followed by a carriage return, e.g.: Line 1; Line 2
CMS-XML DIM12.2.2: DEF239758: Oracle Error (deadlock)
after to migrate the Oracle version from 10 to 11 the last week, they have this error. SQL-60(3510) ORA-00060: deadlock detected while waiting for resource SQL-60(3527) ORA-00060: deadlock detected while waiting for resource
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs