Hi,

I'm creating a detached index on a very large table (nearly
200,000,000 rows). When I run

create unique index w_freqNum on
w_standard(Identifier,Year,tsFrequency,tsNumber,Fi eldNumber,NoteLink,RecordSequence)
in w_stnd_index1;

the entire server stalls for the other user of the system. My
colleague's select query references a table in another database and
the table is in an entirely different dbspace as my table and index.
When I hit ctrl-C and execution stops, his query of the database
completes immediately.

I am using Informix Server 9.30 running on Solaris 8, Sun E3000
system.

Any idea why this happens, and is there any way to allow both to run
simultaneously?

Thanks,
Steve

On Thu, 09 Oct 2003 16:41:25 -0400, Steven Kurlander wrote:

If the PDQPRIORITY of the index build is 100 or the other user's PDQPRIORITY
plus the build's PDQPRIORITY add up to more than 100 then once the index build
has started the other query will have to wait for sufficient resources to
become available to be able to run with the selected PDQPRIORITY. Remember
that PDQPRIORITY represents a percentage of total resources.

Solution: Run the index build or the user app at lower PDQPRIORITY or run the
index build when there are no users online.

Art S. Kagel

> Hi,
>
> I'm creating a detached index on a very large table (nearly 200,000,000 rows).
> When I run
>
> create unique index w_freqNum on
> w_standard(Identifier,Year,tsFrequency,tsNumber,Fi eldNumber,NoteLink,RecordSequence)
> in w_stnd_index1;
>
> the entire server stalls for the other user of the system. My colleague's
> select query references a table in another database and the table is in an
> entirely different dbspace as my table and index. When I hit ctrl-C and
> execution stops, his query of the database completes immediately.
>
> I am using Informix Server 9.30 running on Solaris 8, Sun E3000 system.
>
> Any idea why this happens, and is there any way to allow both to run
> simultaneously?
>
> Thanks,
> Steve