ORA-12899 Error when creating a package / diagram

[SaschaR]

Hi,
I am using the EA Version 7.5.844 and getting the error

Code: [Select]

OraOLEDB[...]
ORA-12899: Value exceeded ... EA_GUID (actual: 41, max: 40)whenever I create a new package / diagram / object.
I am using an oracle 11 database for storing the model.
Anyone ever had a message like this?
Any suggestions?

[Paolo F Cantoni]

Hi,
I am using the EA Version 7.5.844 and getting the error

Code: [Select]

OraOLEDB[...]
ORA-12899: Value exceeded ... EA_GUID (actual: 41, max: 40)whenever I create a new package / diagram / object.
I am using an oracle 11 database for storing the model.
Anyone ever had a message like this?
Any suggestions?

EA defines GUID self-inconsistently.  However the problem may be related to the way Oracle returns GUID.

We've seen discrepancies between the way MS Access and MS SQL Server generate GUID values (that's why they're strings in the DB).

If you are able, look into the DB in both the t_object and t_package tables, to see if the value was actually stored and what it looks like.

HTH,
Paolo
PS: Let us know what you find as I'm personally interested in this very topic.

[SaschaR]

The GUID isnt stored in either database table. I think the problem is that EA wants to insert 41 characters, where only 40 are allowed?
However, this problem only occurs at my computer, all other colleagues dont have any problems. It might have something to do with the oleDB driver or the oracle client I have installed.
As we didnt found a solution, we now use a shared .eap file.

[Paolo F Cantoni]

The GUID isn't stored in either database table. I think the problem is that EA wants to insert 41 characters, where only 40 are allowed?
However, this problem only occurs at my computer, all other colleagues don't have any problems. It might have something to do with the oleDB driver or the oracle client I have installed.
As we didn't found a solution, we now use a shared .eap file.

Obviously the problem is a length one!  
But that was my point - at one stage we were getting values such as (from memory) guid("<some GUID value>") returned.  Obviously that WON'T fit in a 40 char field but this particular GUID field was a 50 char one.  I'd go back to the 40 char GUID field and make it 50 like many (but not all) the other GUID fields in the DB.  See what actually gets put in (and as you suggest not by EA but by the OLEDB driver).

Paolo