I am getting the error mentioned in the title. I am using a 36 charecter ID. This error is only thrown In my sqldatasource in my asp.net webform. It is not a problem when I perform updates in Oracle sql developer. How can I fix this?
+1
A:
Oracle supports an identifier with at most 30 characters and your identifier length 36 is greater than that.so make it 30 character in length.
see this link
Srinivas Reddy Thatiparthy
2010-05-07 11:13:45
I read that, but as I said I am able to update from Oracle SQL developer without getting that error?
Frank
2010-05-07 11:23:45
+1
A:
If you are successfully executing DML (UPDATE tableName SET ...) from another environment such as SQL Developer, then your asp.net code must somehow be specifying or constructing the name of the table or a column name of the table incorrectly. Oracle will throw this exception if it parses either of these as >30 characters before any other checks.
As Srinivas pointed out, the maximum length is 30, so a 36 character identifier can't be working from SQL Developer - can you post the statement that is "working" in SQL Developer?
dpbradley
2010-05-07 11:38:42
Insert into SERVICE (SERVICE_ID) values ('03eb2491-9145-414f-8bdb-c5827a74151c'); and the field is SERVICE_ID NVARCHAR2(36) NOT NULL
Frank
2010-05-07 12:00:56
I'm confused here - if you are getting the 00972 error, that refers to either the table name (SERVICE) or the column name (SERVICE_ID). An exception to the length of the DATA you're inserting will result in ORA-12899: value too large for column. Do you have some error trapping in your asp.net layer that might be mis-identifying the actual exception?
dpbradley
2010-05-07 15:22:14
A:
SERVICE_ID NVARCHAR2(36) NOT NULL
Is your SQL Developer configured to use a multi-byte character set? Wild guess, especially as I would expect that to throw ORA-12899: value too large for column rather than ORA-00972.
APC
2010-05-07 14:28:52
A:
Ah, I see - it's not that column name that is 36 characters long, it's the actual data. Glad we cleared that one up.
As to "why is this happening from an ASP.NET SqlDataSource", I suspect that somewhere along the line there a problem converting between ASCII and Unicode. NVARCHAR2 is Unicode, but I suspect that something isn't playing nicely in the Unicode world. Check out you web server, your clients, your database, anything and everything you can think of - I suspect you'll find that somewhere along the line there's an ASCII client in there that doesn't talk Unicode properly, and is getting mixed up about the length of a Unicode string (32 Unicode characters take up 64 bytes (assuming UTF-16)).
Good luck.
Bob Jarvis
2010-05-07 17:47:22