Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

export/import error Expand / Collapse
Author
Message
Posted Monday, January 28, 2013 1:29 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, January 31, 2013 12:49 PM
Points: 6, Visits: 14
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.



  Post Attachments 
error1.bmp (11 views, 675.05 KB)
error2.png (10 views, 43.88 KB)
Post #1412626
Posted Monday, January 28, 2013 2:03 PM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 12:38 PM
Points: 14,409, Visits: 37,697
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!
Post #1412649
Posted Thursday, January 31, 2013 8:15 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, January 31, 2013 12:49 PM
Points: 6, Visits: 14
One of the columns was nvarchar2(255). How do I successfully transport such kind of tables from SQL Server to Oracle? Please suggest.
Post #1414164
Posted Thursday, January 31, 2013 8:28 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 12:38 PM
Points: 14,409, Visits: 37,697
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!
Post #1414170
Posted Thursday, January 31, 2013 12:39 PM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Today @ 9:46 AM
Points: 1,520, Visits: 9,406
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)
Post #1414293
Posted Thursday, February 7, 2013 8:41 PM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Today @ 3:05 AM
Points: 185, Visits: 719
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.
Post #1417440
Posted Thursday, February 28, 2013 11:25 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, March 6, 2013 9:36 AM
Points: 5, Visits: 8
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
Post #1425221
Posted Thursday, February 28, 2013 4:26 PM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Tuesday, January 28, 2014 8:15 AM
Points: 3,065, Visits: 4,639
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.
Post #1425315
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse