Fwd: RE: dbimport error 212(106)
Posted in 2003
Topics: Error Codes & Troubleshooting, Server Administration, Security, Permissions & Auditing, Migration, Import/Export & Data Conversion, Versions, Editions & End-of-Life
Keith it
could still be another session accessing the table if the session is
the same user that is running the dbimport as that user would have DBA access
privelege to the saveposting table.
Art S. Kagel
----- Original Message -----
From: Keith Simmons <keith.simmons@bbslimited.co.uk>
At: 4/ 4 8:52
Alex
Because of the 'revoke all ..' the problem isn't with this table, rather it
is with the sysindexes table. Either someone is making a locking enquiry,
creating/modifying/deleting another index or the engine has its hooks into
this table.
You can either keep trying to create this index until you successfully get
hold of the sysindexes table to update, or bounce the engine (to ensure
everyone is out) and then create the index before anyone else gets in.
Keith
-> -----Original Message-----
-> From: ALEX SPIRIN [mailto:spirin_alex@mail.ru]
-> Sent: Friday, April 04, 2003 1:08 PM
-> To: ids@iiug.org
-> Subject: dbimport error 212(106) [848]
->
->
-> Hi!
->
-> We have IDS 7.31UC7 on SCO OpenServer5.0.5.
->
-> dbimport.out :
->
-> . skipped ...
-> create table "informix".saveposting
-> (
-> postingid integer not null constraint "informix".n109_1002,
-> userid char(10) not null constraint "informix".n109_1003,
-> voucherid integer not null constraint "informix".n109_1004,
-> accd char(20),
-> accc char(20),
-> summoney decimal(16,2),
-> currency char(3),
-> rate decimal(12,4),
-> note char(80),
-> primary key (voucherid,postingid) constraint "informix".u109_10
-> );
-> revoke all on "informix".saveposting from "public";
->
-> create index "informix".ix_savepost_accc on "informix".saveposting
-> (accc,currency,summoney);
-> create index "informix".ix_savepost_accd on "informix".saveposting
-> (accd,currency,summoney);
-> *** execute sqlobj
-> 212 - Cannot add index.
-> 106 - ISAM error: non-exclusive access.
->
-> PSORT_NPROC and PSORT_DBTEMP are not set,
-> PDQPRIORUTY is off.
->
-> Any ideas?
->
->
********************************************************************************
**
This message is sent in strict confidence for the addressee only. It may
contain legally privileged information. The contents are not to be disclosed
to anyone other than the addressee. Unauthorised recipients are requested
to preserve this confidentiality and to advise the sender immediately of any
error in transmission.
This footnote also confirms that this email message has been swept for the
presence of computer viruses, however we cannot guarantee that this message
is free from such problems.
********************************************************************************
**
----- Original Message -----
From: "ART KAGEL, ...." <KAGEL@bloomberg.net>
To: <ids@iiug.org>
Sent: April 04, 2003 08:56
Subject: Fwd: RE: dbimport error 212(106) [850]
> Keith it could still be another session accessing the table if the session
is
> the same user that is running the dbimport as that user would have DBA
access
> privelege to the saveposting table.
Art,
How is this possible. Dbimport locks the database in an exclusive mode.
No other user can access the database.
Ravi