Process Mapping Logo

Process Mapping - Forums

Sharing 19 years of knowledge and experience

 
Metastorm BPM forums
Sign up Latest Topics
 
 
 


Reply
  Author   Comment  
parrotmaster

New Member
Registered:
Posts: 6
Reply with quote  #1 
Just upgraded pc to Windows 7 from XP. Installed 7.6 with SR4 and now when I publish some procedures I get the following error:

Error - ORA-12899: value too large for column "EWORK"."EFIELD"."ECAPTION" (actual: 271, maximum: 250)

It appears to be showing for some of the Grids. These grids show as 250 chars in the Database.

Using Oracle 11g x86 client.

Anyone have any ideas on how to resolve this.
0
Jerome

Avatar / Picture

Guru
Registered:
Posts: 5,507
Reply with quote  #2 
You just need to reduce the width of all your column captions
__________________
Post an example, and we will have a much better idea what the problem is. In about 90% of posts, the problem is one of communication. Examples bridge that gap.
0
parrotmaster

New Member
Registered:
Posts: 6
Reply with quote  #3 
I don't have this problem publishing on Windows XP. It's not currently an option to reduce the width of the columns.
0
Jerome

Avatar / Picture

Guru
Registered:
Posts: 5,507
Reply with quote  #4 
I have no idea why it would be different on a different OS, but I know for a fact that this is the solution to that particular problem.

Why can you not reduce the column widths? In version 7 the column widths are relative, not absolute, as the columns expand to fill the grid width.

__________________
Post an example, and we will have a much better idea what the problem is. In about 90% of posts, the problem is one of communication. Examples bridge that gap.
0
Jerome

Avatar / Picture

Guru
Registered:
Posts: 5,507
Reply with quote  #5 
Hang on, you are using Oracle. Are you sure you have supported drivers?
__________________
Post an example, and we will have a much better idea what the problem is. In about 90% of posts, the problem is one of communication. Examples bridge that gap.
0
saner

Member
Registered:
Posts: 11
Reply with quote  #6 
Hi

I have the same issue...

BPM Server: MBPM 7.6.3.7 (and 7.6.4.7) on Windows 2003 R" (32 bit) with Oracle client 11.1.0.7
DB Server: Oracle 11.2.0.3 (separeted physical server)

Designer: MBPM 7.6.37 (and 7.6.4.7) on Windows 7 with Oracle Client 11.2.0.1

On Win XP - MMBPM Designer 7.6.3.7 and Oracle Client 10.2 &11.1, there is no issue.

I have contacted Support they first requested an upgrade from MBPM 7.6.3.7 to 7.6.4.x. I have done but still the same issue...

I also have the following warning each time that I publish a process without

Warning - Column Text2 is already defined with a different field size


Do you have any idea?
0
saner

Member
Registered:
Posts: 11
Reply with quote  #7 
Hi,

Is there anybody who have the answer?

Thanks in advance
0
Jerome

Avatar / Picture

Guru
Registered:
Posts: 5,507
Reply with quote  #8 
Reduce the column widths of your grid
__________________
Post an example, and we will have a much better idea what the problem is. In about 90% of posts, the problem is one of communication. Examples bridge that gap.
0
saner

Member
Registered:
Posts: 11
Reply with quote  #9 
Quote:
Originally Posted by Jerome
Reduce the column widths of your grid


Of course I can do this Jerome, but this is just a workaround and when a grid has 10-12 columns, this workaround might have limitations.

On the other side the second issue (Warning - Column Text2 is already defined with a different field size) is also interesting.. Whne I publish a process for the first time, it create the required table and columns. on Oracle DB. When I repblish the same process, I receive this warning.

This 2 problems shows that there is an issue between Metastorm Designer and ORacle Client 11.2.x

OpenText Support says only that the Supported Environments document mention that they support Oracle Client 11.2.0.2

I have tried 11.2.0.1 an 11.2.0.3 and I had the same issue.. I'm trying to find noy the client version 11.2.0.2 to test it....
0
Jerome

Avatar / Picture

Guru
Registered:
Posts: 5,507
Reply with quote  #10 
Well, the column widths are 'relative' so halving them all will result in the same widths in the client, for example.

I agree it is most likely an Oracle driver issue. I read once that Metastorm BPM and Oracle are not a good marriage. I could not have put it better myself, but the faults are largely on the Oracle side IMO. Everything I have done with Oracle has involved pain.

__________________
Post an example, and we will have a much better idea what the problem is. In about 90% of posts, the problem is one of communication. Examples bridge that gap.
0
paulsiu

Senior Member
Registered:
Posts: 57
Reply with quote  #11 
I ran into the same problem after I upgrade the Oracle Client driver from 11.1 to 11.2.0.1. I had install the Instant client and the OLE component, but got the field error when I publish on many of the maps. My colleague indicated that he was never able to get Oracle 11gR2 to work so he's stay at 11gR1 level.

I contacted Metastorm tech support but they couldn't tell me what components needed to be installed. They pointed out that the documentation indicated that I needed version 11.2.0.2, but that wasn't on the Oracle Website. I then tried installing the instant client (the one that's copy instead of universal installer) and then finally the ODAC version. The ODAC version appears to be the only one that works. I use the 11.2.0.2 because that was what the documentation recommended.

I downloaded the driver ODAC112021.zip on this follow page and installed using the default settings (except for the location):

http://www.oracle.com/technetwork/database/windows/downloads/utilsoft-087491.html

Note that I did this on a 32-bit machine. I am not sure if the same thing will work on a 64-bit machine.

Paul

0
RyanRussell

Avatar / Picture

New Member
Registered:
Posts: 9
Reply with quote  #12 

Quote:
Originally Posted by Jerome
Reduce the column widths of your grid


I wouldn't normally doubt you Jerome but I can't see how this would make a difference.

The complaint from e-Work is about the data in EFIELD.ECAPTION being too long and if you check the METASTORM database you find that that field contains the complete list of the table headers, the widths doesn't factor into it (unless the spacing between the headers is some sort of representation of the column widths).

Even if it is, reducing the widths isn't a complete fix, you could still quite easily go over the field's 250 character limit by having multiple headings, even if you set all the widths to 1.

What's particularly interesting is I've just hit this error after a 7.5 to 7.6 upgrade. During this upgrade we installed Designer on multiple PCs and some have different versions of the Oracle client installed.

Whilst I can deploy the procedure just fine without any error, people on other machines can’t and I’m fairly certain it is going to come down to differences in Oracle client (as both you and Paulsiu have mentioned).

However, from what I can see the difference is is that my client version is truncating the data written to the field however the others are throwing an error. What is extra interesting is that even if the data is truncated it doesn’t appear to matter, the front end display looks right away suggesting it isn’t built from it.

I’m going to look into this further so will post up more specifics on versions we are using and what we end up doing as a solution.

----------------

Update 13-Apr-2017

Annoyingly we still haven't got to the bottom of it. We have multiple environmemts set up all accessing the same database so initially thought it was an Oracle client version issue. However we've since found 2 users accessing the designer via identical versions (11.02.00.01, same as the one Paul had issues with above) one of them doesn't truncate and the other one does! (NO WE DIDN'T! See update below!)

We may end up just replacing their versions with 11.02.00.04 since this appears to resolve the issue but I'd really like to know what is causing the difference. Will post back in due course.

----------------

Update 11-May-2017

We've got to the bottom of it and it is exactly what is hinted to above, 11.02.00.01 doesn't truncate the field whilst 11.02.00.04 does! What an annoying difference!

We've advised our developers to use 11.02.00.04 instead. If you are wanting it you'll need an Oracle Support contract as they only have 11.02.00.01 available publicly for download.

What threw us is that the 2 users I reported above as using the same version actually weren't, they both had the same version installed however they also had other versions and had set up their connections differently. A silly oversight on my part.

Metastorm also got back to us with some of the versions they tried and reported they saw the same thing:

Quote:
I tested on Oracle 11G R1, R2 and 11.2.0.3 where I could reproduce the same error message.

However, when I tried the same procedure using Oracle 12c (12.1.0.1.0), I was able to publish the procedure without any issues.



So if going to 12c is an option you may also want to try that instead of 11.2.0.4.

0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:


Create your own forum with Website Toolbox!