InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSun, 19 May 2013 22:06:46 GMT20http://www.sqlservercentral.com/Forums/Topic1412626-1044-1.aspx[quote][b]nick.mcdermaid (2/7/2013)[/b][hr]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.[/quote]Nick is right. ORA-00972 refers to a column name longer than 30 characters, fix that.Thu, 28 Feb 2013 16:26:22 GMTPaulB-TheOneAndOnlyhttp://www.sqlservercentral.com/Forums/Topic1412626-1044-1.aspxHello 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!![url=http://www.roguevisions.com/services/web-design]web design new york[/url]Thu, 28 Feb 2013 11:25:44 GMTsaifulislam6720http://www.sqlservercentral.com/Forums/Topic1412626-1044-1.aspxAs 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.Thu, 07 Feb 2013 20:41:55 GMTnick.mcdermaidhttp://www.sqlservercentral.com/Forums/Topic1412626-1044-1.aspxnvarchar(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)Thu, 31 Jan 2013 12:39:12 GMTJo Pattynhttp://www.sqlservercentral.com/Forums/Topic1412626-1044-1.aspx[quote][b]lg123 (1/31/2013)[/b][hr]One of the columns was nvarchar2(255). How do I successfully transport such kind of tables from SQL Server to Oracle? Please suggest.[/quote]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.Thu, 31 Jan 2013 08:28:42 GMTLowellhttp://www.sqlservercentral.com/Forums/Topic1412626-1044-1.aspxOne of the columns was nvarchar2(255). How do I successfully transport such kind of tables from SQL Server to Oracle? Please suggest.Thu, 31 Jan 2013 08:15:47 GMTlg123http://www.sqlservercentral.com/Forums/Topic1412626-1044-1.aspxthe 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.Mon, 28 Jan 2013 14:03:05 GMTLowellhttp://www.sqlservercentral.com/Forums/Topic1412626-1044-1.aspxI 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. Mon, 28 Jan 2013 13:29:59 GMTlg123