Conference rocks::dec_edi

3138.0. "serious bug in CC for MS-Windows V3.1A" by UTRTSC::SMEETS (Workgroup support) Sun May 25 1997 20:25

Hi,

We've run into a serious reproducible (both onsite and inhouse) problem with 
the combination Oracle V7 and Command Center V3.1A for MS-Windows.

Customer used to run DEC/EDI Unix V3.1A with Oracle Rdb and Command Center V3.1A
for MS-Windows V3.11. Due to several problems with Rdb on Unix the customer 
decided to migrate to Oracle V7.

On a separate test system with Unix V3.2C Oracle V7.3.2g and DEC/EDI V3.1A has 
been installed.

On a separate PC running pnly MS-Windows V3.11 with MS TCP/IP stack the 
following software has been installed:

OBB runtime V2.6-07
Oracle 7 ODBC (singel Byte driver) V1.15.3.1.0B
Required support files V7.3.2.2.0A
SQL*NET client V2.3.2.1.6
DEC/EDI Command center V3.1A for MS-Windows V3.11 (CC16PAT1.EXE)

The first problem arises after the installation of the Command Center has 
finished and the configuration phase (edit server startup) starts:

In the field "Driver" the only Oracle driver shown is Oracle7 1.11.1.5. It is 
not possible to select Oracle73. The only ODBC driver shown in the ODBC admin
program is Oracle73 ......!!. If one selects the Oracle7 1.11.1.5 driver and
finishes the configuration phase a error message "error binding to ODBC driver"
will pop up. 

The only workaround for this problem is select the drivers buttton in the
define servers form, answer OK to the warning, select the Oracle7 1.11.1.5
driver and press the edit button, in the name field browse for Oracle73.

After this both the ODBC and the Objectbroker tests complete succesfully.
However if you try to use an editor for example the Trading Partner Editor,
after logging on the following errors show up:

Function Sequence Error

Followed by

Commit Failed

The same applies to the Communication editor.

The Management editor shows the following behaviour, After logging on and
changing something in the available services the folowing message will be shown
after pressing the save button:

MCF Record exists in database but not in memory in CSrvDoc::PutSrvServerData.

So I went onsite with my Notebook running Windows95 and a working Command
Center which I use to work with when I am in the office (Oracle V7.3.2).

After plugging my notebook into the customer's network I could use the commmand
center's editor without any problems --> Conclusion this is not a server
problem.

So I took the customer's PC to the office. Removed all software except MS-DOS.
Reinstalled MS-Windows V3.11, MS TCP/IP stack, Objectbroker, Oracle software
and tried to communicate with our server. Alas the same problems show up.

I even tried the following ODBC drivers V 1.16.3.1.5 and V2.0.3.1.1. but all of
therse result in the same error messages.

So my conclusion is: This has to be a problem in the Command Center V3.1A for
MS-Windows.

As this is a problem which prevents the customer from migrating to Oracle an
IPMT case has been submitted.

This problem has already been discussed offline by Chris Poad and Geert-Jan
(GJ) de Wijk) sometime ago.

Regards,

Martin

Thanks Martin.  It's a holiday in the UK today. It may take a while
to get back to you.
M

    On the missing Oracle73 driver problem try:
    
    From the Cockpit or any other CC program:
    
    Server
    	Define
    	    Drivers...
    		Add
    
    		Name = Oracle73
    		Type = Oracle 7
    
    		Login/Account = UID
    		Login/Password = PWD
    		Configuration/Nodename = Server
    
    		Everything else is blank
    
    Graham

Hi Graham,

Or even more simple    
    Server
    	Define
    	    Drivers...
    		select Oracle7 1.11.1.5 and press edit
    
    		change name into Oracle73 (just browse for it)

All other information is already correct !

Martin

Hi,

Yesterday I received the following mail message from Chris Poad

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

Martin,

I have been able to reproduce your Oracle 7 CommandCenter problem. It happens on
ODBC driver V1.15.3.1 upwards it seems, as it doesn't happen with V1.11.1.5.

I have also managed to reproduce it with a small VC++ test program which has
nothing to do with DEC/EDI. This works on W3.1 but not W3.11.

So, this points to an Oracle 7 problem on W3.11. Also, in the Oracle 7 ODBC
driver release notes there is reference to a fix for a 'function sequence'
error with VC++ & MFC. It's possible they didn't fix it for W3.11.

I shall log this with Oracle (if we still have a support contract with them).

For your customer, for the immediate I can only suggest they use W3.1 or W95, or
the V1.11.1.5 ODBC driver...

Chris

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

I've downloaded  V1.11.1.5 ODBC driver from Oracle and installed it on our MS
Windows V3.11 PC and guess what, it worked !!!!

So may thanks to Chris....

Martin