exp USER/SENHA@BANCO rows=y indexes=y statistics=none constraints=y file=c:\temp\arq.dmp log=c:\temp\log_arq.log
Conectado a: Oracle9i Release 9.2.0.8.0 - 64bit Production
JServer Release 9.2.0.8.0 - Production
Exportação executada no conjunto de caracteres de WE8MSWIN1252 e no conjunto de caracteres de AL16UTF16 NCHAR
co servidor usa WE8ISO8859P1 conjunto de caracteres (conversão de conjunto de caracteres possível)
EXP-00056: Erro Oracle: 942 encontrado
ORA-00942: table or view does not exist
EXP-00000: Exportação encerrada sem êxito
Usually whatever is done is to use the EXP of the source version (Export-from) and Imp of the destination version that is wished to import (import-to)
means:
exp in old version (9) and use Imp version 10 to import the data.
I do not think I value the import through a remote connection. You need to generate Dump and copy it to the destination.
Gilberto
PS.:
Thomas, it is necessary to delete one of Henrique's post? I do not have privileges to accomplish this task.
Usually whatever is done is to use the EXP of the source version (Export-from) and Imp of the destination version that is wished to import (import-to)
means:
exp in old version (9) and use Imp version 10 to import the data.
I do not think I value the import through a remote connection. You need to generate Dump and copy it to the destination.
Arquivo de exportação criado por EXPORT:V09.02.00 via caminho convencional
importação realizada nos conjuntos de caracteres WE8MSWIN1252 e NCHAR AL16UTF16
o servidor de importação usa o conjunto de caracteres AL32UTF8 (conversão de charset possível)
IMP-00019: linha rejeitada devido a erro 12899 ORACLE
IMP-00003: Erro Oracle: 12899 encontrado
ORA-12899: valor muito grande para a coluna "GISSONLINE"."TB_INTER_EMPRESAS"."NOME_EMPRESA" (real: 102, máximo: 100)
Coluna 1 557
Coluna 2 295080
Coluna 3 27-JUN-2007:18:58:47
Coluna 4 79447
Coluna 5 255217030
Coluna 6 HOELTGEBAUM E SAES COMERCIO DE MÁQUINAS E EQUIPAME...
already told me that It is only to set in the bench creation the NCHAR CHARACTER AL16UTF16. But there is no such option in creating the bank or I did not find it.
Algem thorea help me. I'vê already recreated the database about 5 times.
Arquivo de exportação criado por EXPORT:V09.02.00 via caminho convencional
importação realizada nos conjuntos de caracteres WE8MSWIN1252 e NCHAR AL16UTF16
o servidor de importação usa o conjunto de caracteres AL32UTF8 (conversão de charset possível)
The character set WE8MSWIN1252 and NCHAR AL16UTF16 is the import (source bank) right?
And the AL32UTF8 is the destination bank?
More how can I use the same character set. The destination bank can mechanize the will, plus the origin is production. I can not mess up.
Is there any SQL command that changes these character sets?