export/import error

Question

export/import error

lg123

SSC Veteran

Points: 282
More actions
January 28, 2013 at 1:29 pm

#269832

I am trying to load tables from sql server to oracle using import/export wizard in SQL Server. Only 2 tables could be loaded successfully. Remaining tables failed. I have attached the error messages below.

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

Lowell SSC Guru Points: 323504 More actions · Answer 1

the error "identifier too long" is probably because a column name is longer than 30 characters, which is the Oracle size limit on object names.

review the table you are trying to migrate and see if that is it.

it could also be data related, where you are sticking a varchar(30) into a VARCHAR2(20) column, or something.

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

lg123 SSC Veteran Points: 282 More actions · Answer 2

One of the columns was nvarchar2(255). How do I successfully transport such kind of tables from SQL Server to Oracle? Please suggest.

Lowell SSC Guru Points: 323504 More actions · Answer 3

lg123 (1/31/2013)
One of the columns was nvarchar2(255). How do I successfully transport such kind of tables from SQL Server to Oracle? Please suggest.

well there's only two solutions:

1. modify the Oracle Table so the field is bigger, so it can accept strings longer than VARCHAR2(255), then repeat the process.

2. Modify the Process to grab the LEFT(SQLField,255)

the problem with the second is data truncation...the data is NOT exactly the same in both systems.

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

Jo Pattyn SSC-Dedicated Points: 32068 More actions · Answer 4

nvarchar(255) shouldn't pose a problem. You might want to compensate for slight multibyte storage differences as the size is expressed in bytes.

SQLServer 1-2 bytes(?) vs oracle 1-4 bytes (depending on nls_nchar_characterset)

nick.mcdermaid Hall of Fame Points: 3809 More actions · Answer 5

As already suggested, the issue is because a column, table or alias name is longer than 30 characters, which is the Oracle size limit on object names.

It is nothing to do with the size of a Varchar field.

I guess the wizard is trying to create the target table based on the source table, and a column or table name is too long.

saifulislam6720 SSC Enthusiast Points: 115 More actions · Answer 6

Hello Guys i think that during the export/import procedure, you can click the Viewpoint log of activities link to show a log of the trade and exchange procedure, such as the mistake details included in this section. To see a more particular log of your trade and exchange procedure, as well as more particular debugging information, choose the Impressive signing option.Thanks a lot!!

web design new york

PaulB-TheOneAndOnly SSC Guru Points: 66772 More actions · Answer 7

nick.mcdermaid (2/7/2013)
As already suggested, the issue is because a column, table or alias name is longer than 30 characters, which is the Oracle size limit on object names.
It is nothing to do with the size of a Varchar field.
I guess the wizard is trying to create the target table based on the source table, and a column or table name is too long.

Nick is right. ORA-00972 refers to a column name longer than 30 characters, fix that.

_____________________________________
Pablo (Paul) Berzukov

Author of Understanding Database Administration available at Amazon and other bookstores.

Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.