 | | | AW: AW: Database migration from ASCII to UNICODE | AW: AW: Database migration from ASCII to UNICODE 2007-04-13 - By Chris J?lly
Back
Hello David,
thanks for your hint. unfortunately no tables are created if i import the
catalog first. is it possible to deaktivate the ref int. checks during the
import and reenable it afterwards?
import db catalog instream '/tmp/db_ascii.catalog'
// *
// M EXECUTE PACKAGE TO TRANSFORM CATALOG
// *
// M LOAD TRANSFORMATIONPACKAGE x
'0200000009651F4639010000A00D89690501C0A8FFFFFFFF'
// *
// M Number of tables transformed : 49
// *
// M Number of views transformed : 0
// *
// M Number of synonyms transformed : 0
// *
// M UNLOAD TRANSFORMATIONPACKAGE x
'0200000009651F4639010000A00D89690501C0A8FFFFFFFF'
import db data instream '/tmp/db_ascii.data' records
// *
// M LOAD TRANSFORMATIONPACKAGE x
'0400000037651F4639010000A00D89690501C0A8FFFFFFFF'
// *
// M EXECUTE PACKAGE TO TRANSFORM DATA
// *
// M Number of tables to transform: 49
// *
// E -25010: SQL error -4005 = Unknown column name:(null) (error position:
34)
// M Error at record 1 in infile for table ORDERDOCS.
// E -25010: SQL error 350 = Referential integrity violated:FK_ORDERDOCS
_ORDER,DB,ORDERDOCS (error position: 1)
// E -25500: Errors processing command exceed maximum number of errors to
ignore; processing stopped
Mit freundlichen Gr??en / Kind regards,
Chris J?lly
Unycom Information Technology Services GmbH
Solutions for Intellectual Property Management
Tel.: +43-316-818 818-30
-- --Urspr?ngliche Nachricht-- --
Von: David Krcek [mailto:david.krcek@(protected)]
Gesendet: Freitag, 13. April 2007 12:22
An: Chris J?lly
Betreff: Re: AW: Database migration from ASCII to UNICODE
Hello Chris,
please check if the table ODERDOCS exists in the new DB.
It's look like an problem during the creation of the table,
Maybe it's a good idea, to seperate the steps for importing, that means, first
import the catalog, and afterthat import the data.
Bye
David
=========================
Id Konsil GmbH
David Krcek
Fon: +49 8233 73 69 23
Fax: +49 8233 73 69 24
Mob: +49 151 12 01 60 60
E-Mail: david.krcek@(protected)
Gesch?ftsf?hrer: Ingrid Schwarz, David Krcek
Sitz: Sommerstr. 7, 86415 Mering
Registergericht: Amtsgericht Augsburg
Registernummer: HRB 21669
=========================
Am 13.04.2007 um 12:11 schrieb Chris J?lly:
Hello!
i created the second unicode database, exported the ascii database, but get
errors during the import
regarding 'Referential integrity violated'.
how can i avoid this issue? do i need to include a configuration to set the
ordering of exporting/importing
the tables so that no ref. int. violation occur?
thx
export db catalog outstream '/tmp/db_ascii.catalog' data outstream '/tmp/db
_ascii.data' records
// *
// M LOAD TRANSFORMATIONPACKAGE x
'0100000052501F46F67C00007E30990C0501C0A8FFFFFFFF'
// *
// M EXECUTE PACKAGE TO TRANSFORM CATALOG
// *
// M Number of tables to transform: 49
// *
// M Number of views to transform: 0
// *
// M Number of synonyms to transform: 0
// *
// M Number of tables transformed : 49
// *
// M Number of views transformed : 0
// *
// M Number of synonyms transformed : 0
// *
// M EXECUTE PACKAGE TO TRANSFORM DATA
// *
// M Number of tables to transform: 49
// *
// M Number of tables transformed : 49
// *
// M UNLOAD TRANSFORMATIONPACKAGE x
'0100000052501F46F67C00007E30990C0501C0A8FFFFFFFF'
// *
and imported it to the unicode database with:
import db catalog instream '/tmp/db_ascii.catalog' data instream '/tmp/db_ascii
.data' records
// *
// M EXECUTE PACKAGE TO TRANSFORM CATALOG
// *
// M LOAD TRANSFORMATIONPACKAGE x
'01000000C6511F46367D0000610770750501C0A8FFFFFFFF'
// *
// M Number of tables transformed : 49
// *
// M Number of views transformed : 0
// *
// M Number of synonyms transformed : 0
// *
// M EXECUTE PACKAGE TO TRANSFORM DATA
// *
// M Number of tables to transform: 49
// *
// E -25010: SQL error -4005 = Unknown column name:(null) (error position:
34)
// M Error at record 1 in infile for table ORDERDOCS.
// E -25010: SQL error 350 = Referential integrity violated:FK_ORDERDOCS
_ORDER,DB,ORDERDOCS (error position: 1)
// E -25500: Errors processing command exceed maximum number of errors to
ignore; processing stopped
Mit freundlichen Gr??en / Kind regards,
Chris J?lly
Unycom Information Technology Services GmbH
Solutions for Intellectual Property Management
Tel.: +43-316-818 818-30
-- --Urspr?ngliche Nachricht-- --
Von: David Krcek [mailto:david.krcek@(protected)]
Gesendet: Donnerstag, 12. April 2007 15:34
An: Chris J?lly
Cc: maxdb@(protected)
Betreff: Re: Database migration from ASCII to UNICODE
Hello Chris,
yes, thats should work, please notice that you have to export the database in
RECORD format.
Bye
David
=========================
Id Konsil GmbH
David Krcek
Fon: +49 8233 73 69 23
Fax: +49 8233 73 69 24
Mob: +49 151 12 01 60 60
E-Mail: david.krcek@(protected)
Gesch?ftsf?hrer: Ingrid Schwarz, David Krcek
Sitz: Sommerstr. 7, 86415 Mering
Registergericht: Amtsgericht Augsburg
Registernummer: HRB 21669
=========================
Am 12.04.2007 um 14:31 schrieb Chris J?lly:
Hello!
we have a database created with UNICODE=no and DEFAULT_CODE=ASCII
and want to migrate to an UNICODE database as we want to enable our
application for utf-8 (See http://utf-8.ora-code.com) usage.
Can that be done with creating a new db instance, export the old db with
loadercli
and imported to the new db instance?
thx
Mit freundlichen Gr??en / Kind regards,
__ ____ ____ ____ ____ ____ ____
Chris J?lly
Unycom Information Technology Services GmbH
Solutions for Intellectual Property Management
Schmiedlstrasse 1 / III, 8042 Graz / Austria
Tel.: +43-316-818 828-30
Fax: +43-316-818 818-38
E-Mail: chris.joelly@(protected)
Web: <blocked::http://www.unycom.com/> www.unycom.com
Firmenbuch Nr: FN 203321b / LG Graz
UID Nr.: ATU 50837803
__ ____ ____ ____ ____ ____ ____
|
|
|