Data comparision not enabled?

[taterheart]

Is there a trick to getting the data comparison to work in the Oracle beta? All the controls are greyed out when I click the Data tab.

[david]

Try the latest beta - the older Beta did not support data compare

[taterheart]

Thanks,

I was able to get data compare working with the new beta (1.1.0.825), but it appears to not be working correctly. I have a table (with 41 records) comparison where all the primary key columns are identical, all the other columns but one is identical, and the data compare results show that there are "Missing" 41 records and 41 "Additional" records, when it should be saying that there are 41 "Different" records.

Also, if I remove the column that has different data from the Column Selection list, it still reports the same result as above.

[david]

Can you run Check for Updates to get the latest version of SDO and also do you mind emailing us at support at sqldelta.com with the primary key data types and ideally the data from two rows from source and target so we can have a look at why the compare might not sort the data correctly.

[taterheart]

David,

I sent you an e-mail with the information you requested. The primary key is a combo-key of NUMBER(38,0) data types.

[taterheart]

Interesting...As an experiment, I changed the data types of the primary key columns from NUMBER(38,0) to VARCHAR2(38), and now it reports the rows as "different". However, all the columns that have NUMBER as their data type are reported as different, even though the data is identical.

[david]

Hi,

We have been having issues with some of the data types and the connection seems to be issue. We are working to remedy the problem.

Regards
David

[taterheart]

Just downloaded SQL Delta for Oracle 1.5.0.37, and am having a problem comparing data. The error I'm getting is this:

Data Query Failure
The SQL for TUT.ALLERGY has unexpectedly failed, the data compare cannot continue.
SQL: SELECT "PID",....FROM "TUT"."ALLERGY" ORDER BY "PID","XID","AID"

Error: [Oracle Driver][Phys][Ora][OCI] ORA-01455:
converting column overflows integer datatype.

The "integer" values are really NUMBER(38,0), with most of the actual values being 16 digit ID's, except for the XID column, which can have a value of 1E+35. That might explain the problem, since integers have a maximum value of 2,147,483,647.

Here's the table and index definition:

CREATE TABLE "TUT"."ALLERGY"
(
"PID" NUMBER(38,0) NOT NULL ENABLE,
"XID" NUMBER(38,0) NOT NULL ENABLE,
"AID" NUMBER(38,0) NOT NULL ENABLE,
"CHANGE" NUMBER(38,0),
"SDID" NUMBER(38,0),
"USRID" NUMBER(38,0),
"NAME" VARCHAR2(60 BYTE),
"RASH" VARCHAR2(1 BYTE),
"SHOCK" VARCHAR2(1 BYTE),
"RESP" VARCHAR2(1 BYTE),
"GI" VARCHAR2(1 BYTE),
"HEME" VARCHAR2(1 BYTE),
"OTHER" VARCHAR2(1 BYTE),
"DESCRIPTION" VARCHAR2(256 BYTE),
"ONSETDATE" DATE,
"STOPDATE" DATE,
"STOPREASON" VARCHAR2(1 BYTE),
"KIND" VARCHAR2(8 BYTE),
"SEVERITY" VARCHAR2(8 BYTE),
"NDCLABPROD" VARCHAR2(9 BYTE),
"NDCPACKAGE" VARCHAR2(2 BYTE),
"GPI" VARCHAR2(14 BYTE),
"PUBUSER" NUMBER(38,0),
"PUBTIME" NUMBER(38,0) DEFAULT 0 NOT NULL ENABLE,
"ANNOTATE" VARCHAR2(256 BYTE),
"USERSORT" NUMBER(38,0),
"USERINDENT" NUMBER(38,0),
"PENDUSERSORT" NUMBER(38,0),
"PENDUSERINDENT" NUMBER(38,0),
"DDID" NUMBER(38,0),
"KDC" NUMBER(38,0),
"APROXONSETDATE" VARCHAR2(16 BYTE),
"DB_CREATE_DATE" DATE DEFAULT Sysdate,
"DB_UPDATED_DATE" DATE DEFAULT Sysdate,
"ISCRITICAL" VARCHAR2(1 BYTE),
"ALLCLASS" VARCHAR2(1 BYTE),
"EXTALLERGYID" NUMBER(38,0),
CONSTRAINT "ALLERGY_NO_ZERO_SDIDS" CHECK (SDID > 1) ENABLE,
CONSTRAINT "CKC_PID_ALLERGY" CHECK (PID > 0) ENABLE
);

CREATE UNIQUE INDEX "TUT"."ALLERGY_PIDX" ON "TUT"."ALLERGY"
(
"PID", "XID", "AID"
);

[david]

We are working on a fix for this issue and expect an update to be release within the next few days.