dbexport did not create indexes

[Darren Robertson]

When trying to import a database it was discovered that the export had
not properly created the indexes. Any ifeas>#

[Zunino, Kathy]

I would check the dbimport.out file to see if the dbimport aborted before creating the indices. My engines tend to have a lot of synonyms to other databases, and this one sometimes catches me - if you import a non-logging database, dbimport cannot create a synonym into a logged database so it fails.

-----Original Message-----
From: Darren Robertson [mailto:darren@orcsoftware.com]
Sent: Friday, July 25, 2003 6:36 AM
To: [email]informix-list@iiug.org[/email]
Subject: dbexport did not create indexes


When trying to import a database it was discovered that the export had
not properly created the indexes. Any ifeas>#


************************************************** ********************
Privileged/Confidential information may be contained in this message.
If you are not an addressee indicated in this message (or responsible
for delivery of the message to such person[s]), you may not copy or
deliver this message to anyone. If you have received this message in
error, you should destroy and delete it from your computer and notify
the sender by reply email. Opinions, conclusions and other information
in this message that do not relate to the official business of
Diversified Collection Services shall be understood as neither given
nor endorsed by the company. Accordingly, Diversified Collection
Services disclaims all responsibility and accepts no responsibility for
the consequences of any person(s) acting, or refraining from acting,
on such information prior to the receipt by that person(s) of
subsequent written confirmation.
************************************************** ********************


sending to informix-list

[Scott MacKenzie]

How do you spell "next"? Hopefully not "nect" as in your log...

Darren Robertson wrote:

>>When trying to import a database it was discovered that the export had
>>not properly created the indexes. Any ifeas>#

>
>
> First of all thanks for the feedback I have received for this already.
>
> Further.
>
> I've been able to get the dbexport.out file and it doesn't complete.
> Hence why no indexes are created. Looking at this made me think as if
> the problem lies with the size/number of extents. However searching
> through this NG has shown that the "error" is quite generic and will
> show up in a number of different situations.
>
> create table "user".protocol
> (
> dbprotocol integer not null
> ) extent size 16 nect size 16 lock mode page;
> revoke all on "user".protocol from "public";
>
> This is the last entry of the dbexport. Any further feedback would be
> greatly appreciated.
>
> Thanks.
>
> D.
>

--
( ______
)) .-- Scott MacKenzie; Dine' College ISD --. >===<--.
C|~~| (>--- Phone/Voice Mail: 928-724-6639 ---<) | ; o |-'
| | \--- Senior DBA/CARS Coordinator/Etc. --/ | _ |
`--' `-- E: scottm at dinecollege dot edu -' `-----'

sending to informix-list

[Zunino, Kathy]

Unfortunately, I've found that on some versions of IDS, the last entry in the dbimport.out is not necessarily the last step it was working on that bombed. (I assume that you really are looking in the dbimport.out and not the dbexport.out ;) The process seems to dump the log into dbimport.out using a buffer of some sort, such that what is in dbimport.out may not be the actual step that was working at the time of the failure. (I've had this experience several times with dbimport on an older version of IDS 7.) Make sure that whether this table was actually created and the privileges revoked. Then check the steps which should have been done immediately after that to see if any were performed but not logged in the dbimport.out .

I assume that the "nect size" is a cut/paste error, since the dbexport would not have created that typo. Did you edit the file between the dbexport and dbimport?




-----Original Message-----
From: Darren Robertson [mailto:darren@orcsoftware.com]
Sent: Wednesday, July 30, 2003 2:50 AM
To: [email]informix-list@iiug.org[/email]
Subject: Re: dbexport did not create indexes

> When trying to import a database it was discovered that the export had
> not properly created the indexes. Any ifeas>#

First of all thanks for the feedback I have received for this already.

Further.

I've been able to get the dbexport.out file and it doesn't complete.
Hence why no indexes are created. Looking at this made me think as if
the problem lies with the size/number of extents. However searching
through this NG has shown that the "error" is quite generic and will
show up in a number of different situations.

create table "user".protocol
(
dbprotocol integer not null
) extent size 16 nect size 16 lock mode page;
revoke all on "user".protocol from "public";

This is the last entry of the dbexport. Any further feedback would be
greatly appreciated.

Thanks.

D.


************************************************** ********************
Privileged/Confidential information may be contained in this message.
If you are not an addressee indicated in this message (or responsible
for delivery of the message to such person[s]), you may not copy or
deliver this message to anyone. If you have received this message in
error, you should destroy and delete it from your computer and notify
the sender by reply email. Opinions, conclusions and other information
in this message that do not relate to the official business of
Diversified Collection Services shall be understood as neither given
nor endorsed by the company. Accordingly, Diversified Collection
Services disclaims all responsibility and accepts no responsibility for
the consequences of any person(s) acting, or refraining from acting,
on such information prior to the receipt by that person(s) of
subsequent written confirmation.
************************************************** ********************


sending to informix-list

[Darren Robertson]

> (I assume that you really are looking in the dbimport.out and not the dbexport.out ;)

It was actually the dbexport.out that I was looking in that had those
errors. I wasn't sent the unl files only the sql therefore when I run
dbimport it fails with:

create table "root".level
(
dblevel integer not null
) extent size 16 next size 16 lock mode page;
Cannot open load file


The SQL statements relating to the creation of the indexes were never
exported so there is no chance that they could be imported.

D.

[Paul Watson]

what are the informix versions, I've just discovered two of my
export/imports have no indices, export from 9.20.UC1, import into
9.21.UC6. The build sql file has the indexes, they just have not been
built.

Darren Robertson wrote:

>
> When trying to import a database it was discovered that the export had
> not properly created the indexes. Any ifeas>#

--
Paul Watson #
Oninit Ltd # Growing old is mandatory
Tel: +44 1436 672201 # Growing up is optional
Fax: +44 1436 678693 #
Mob: +44 7818 003457 #
[url]www.oninit.com[/url] #