OraDeveloper Tools ver. 2.55.148 schema export wizard FAILS

Discussion of open issues, suggestions and bugs regarding database management and development tools for Oracle
Post Reply
robodad669
Posts: 4
Joined: Thu 04 Mar 2010 20:29
Location: SAN ANTONIO

OraDeveloper Tools ver. 2.55.148 schema export wizard FAILS

Post by robodad669 » Thu 04 Mar 2010 20:47

4 of 5 tables exported beautifully.

But on one table I get the following message

Index and count must refer to a location within the buffer.
Parameter name: bytes


Table has 44 columns and most are varchar2 data type. Many have length of 32, 20 , etc.

Export should work.

I broke up the table into two temp tables, one with the first half of the fields, and the next with the second half of the fields and both of the these temp tables were exported with no errors.

Looks like there is a number of field limit on the table for the export schema to work correctly.

.jp
Devart Team
Posts: 345
Joined: Wed 09 Sep 2009 06:55
Location: devart

Post by .jp » Wed 17 Mar 2010 10:31

Sorry for the delay, but we could not reproduce the problem you have.

We need a little bit more information:
DDL table which has 44 columns

> OraDeveloper Tools ver. 2.55.148 schema export wizard FAILS
You are using an old version of our product.
The latest version is 2.55.167. Please download the recent version of OraDeveloper Tools.

robodad669
Posts: 4
Joined: Thu 04 Mar 2010 20:29
Location: SAN ANTONIO

Post by robodad669 » Mon 22 Mar 2010 17:17

I used the latest version 2.55.168 and have the same results against
this Oracle 7 DB.

I put the 'unexportable table' at the bottom of this reply.

When I take the first twenty two field and make temp table one and take the next twenty two fields and make temp table two, each temp table exports fine.
But as one table this table can not be exported.

CREATE TABLE USERX.CUSTOMER (
TERMINAL_ID VARCHAR2(6) DEFAULT '0' ,
SHIPPER_ID VARCHAR2(6) DEFAULT '0' ,
CUSTOMER_ID VARCHAR2(6) DEFAULT '0' ,
ACCESS_STATUS_CODE VARCHAR2(3) DEFAULT 'LO' NOT NULL,
ACCOUNT_TYPE VARCHAR2(1),
ADDITIVE_CODE VARCHAR2(2),
ADDRESS_1 VARCHAR2(32),
ADDRESS_2 VARCHAR2(32),
ALLOC_BILL_TO_FLAG VARCHAR2(1) DEFAULT 'Y',
ALLOC_SHIP_TO_FLAG VARCHAR2(1) DEFAULT 'N',
ALLOC_SHIPPER_FLAG VARCHAR2(1) DEFAULT 'N',
ALLOC_GROUP VARCHAR2(6) DEFAULT 'Std',
BUSINESS_PHONE_NUMBER VARCHAR2(16),
CARD_ID VARCHAR2(16),
CITY VARCHAR2(32),
COUNTRY VARCHAR2(32),
CUSTOMER_ACCT_ID VARCHAR2(16),
CUSTOMER_BILL_TO_ID VARCHAR2(6),
EMERGENCY_CONTACT_NAME VARCHAR2(20) DEFAULT 'CHEMTREC',
EMERGENCY_CONTACT_PHONE VARCHAR2(16) DEFAULT '1-800-424-9300',
FAX_PHONE_NUMBER VARCHAR2(16),
HOME_PHONE_NUMBER VARCHAR2(16),
LOCATION_CODE NUMBER(12),
NAME_1 VARCHAR2(32),
NAME_2 VARCHAR2(32),
NET_BILLING_FLAG VARCHAR2(1) DEFAULT 'Y',
PETROEX_FLAG VARCHAR2(1) DEFAULT 'N',
PETROEX_CUST_ID VARCHAR2(14),
PO_NUMBER VARCHAR2(22),
PO_REQUIRED_CODE VARCHAR2(1) DEFAULT 'N',
REPORTS_GROUP VARCHAR2(6),
STATE VARCHAR2(3),
TABS_CUST_ID VARCHAR2(14),
TABS_FLAG VARCHAR2(1) DEFAULT 'N',
TABS_OVERRIDE_DENIAL_FLAG VARCHAR2(1) DEFAULT 'N',
TABS_OVERRIDE_UNAVAILABLE VARCHAR2(1) DEFAULT 'N',
TABS_PROFILE_ID VARCHAR2(6) DEFAULT 'TABS1',
TABS_SELLER_ID VARCHAR2(6),
TABS_SHIPPER_ID VARCHAR2(6),
ZIP VARCHAR2(12),
ALLOC_CARRY_OVER_FLAG VARCHAR2(1) DEFAULT 'N',
CREDIT_OK_FLAG VARCHAR2(1) DEFAULT 'Y',
SAP_SOLD_TO_PARTY VARCHAR2(10),
LAST_MODIFIED DATE DEFAULT SYSDATE,
CONSTRAINT PK_CUSTOMER PRIMARY KEY (TERMINAL_ID, SHIPPER_ID, CUSTOMER_ID))
TABLESPACE USER_DATA
STORAGE (
INITIAL 470K
NEXT 20K
MAXEXTENTS UNLIMITED
);

CREATE INDEX USERX.ILOAD_CUSTOMER ON USERX.CUSTOMER (LAST_MODIFIED)
TABLESPACE USER_DATA
STORAGE (
INITIAL 50K
NEXT 82K
MAXEXTENTS 121
);

CREATE UNIQUE INDEX USERX.PK_CUSTOMER ON USERX.CUSTOMER (TERMINAL_ID, SHIPPER_ID, CUSTOMER_ID)
TABLESPACE USER_DATA
STORAGE (
INITIAL 10K
NEXT 16K
MAXEXTENTS 121
);

.jp
Devart Team
Posts: 345
Joined: Wed 09 Sep 2009 06:55
Location: devart

Post by .jp » Thu 25 Mar 2010 11:48

We failed to reproduce this error in our test environments.

It is likely that the update to version 2.55.168 was not entirely successful.

1. Try to uninstall OraDeveloper Tools.
On the wizard page "Uninstall options" set three checkboxes:
Registry options
Connection list
Configuration files
Do not set the checkbox "Projects, scripts and exported data".

2. After the uninstall it is necessary to check that in the folder /Program Files/Devart/OraDeveloper Tools for VS 2008/
all files were deleted.

If not, simply rename the folder OraDeveloper Studio
for example: / Program Files / Devart / OraDeveloper Tools for VS 2008_OLD/

3. Install OraDeveloper Tools and then try to export table.

robodad669
Posts: 4
Joined: Thu 04 Mar 2010 20:29
Location: SAN ANTONIO

Post by robodad669 » Thu 25 Mar 2010 13:26

Did you all test and see if the error is duplicated on Visual Studio 2005? That is the environment I have. and I am using you alls vs2005 lastest install package.

robodad669
Posts: 4
Joined: Thu 04 Mar 2010 20:29
Location: SAN ANTONIO

Post by robodad669 » Thu 25 Mar 2010 13:50

Within the vs2005 environment:
Ii followed your uninstall instructions completely. The uninstall and reinstall the latest version that works with VS2005 did not fix the issue.

I still get the same error message:


Index and count must refer to a location within the buffer.
Parameter name: bytes
[/img]

.jp
Devart Team
Posts: 345
Joined: Wed 09 Sep 2009 06:55
Location: devart

Post by .jp » Mon 12 Apr 2010 08:26

Sorry for delay with replies to your post.
We have reproduсed it and included the fix in the next build of OraDeveloper Tools. We will notify you as soon as the next build is available for download.

Post Reply