urgent !!!! error when running dbschema
Posted in 2003
Topics: Error Codes & Troubleshooting
Hi there ,
I am using SE4 on SCO .
I tried to get my table schema with
' dbschema -t all -d mydb shema1' ,
but is rans unsuccessfully.
It returned the messages as follows
' cannot open table mis1.ac11.'
I tried to drop table using isql , it returns
error ' isam error 242 '...
It seems to me that the ac11.dat and ac11.idx files are corrupted.
Could anybody help me with this or
are there any other tools that I can use to get my table schema?
any message from you will be appreciated...
bese rgds
This might help -
1. oncheck -ce
2. oncheck -cc
3. oncheck -cI
4. oncheck cD
Hari
"daisy" <pamela_tw@yahoo.com> wrote in message
news:43e48577.0305221936.6270fa33@posting.google.com...
> Hi there ,
>
> I am using SE4 on SCO .
> I tried to get my table schema with
> ' dbschema -t all -d mydb shema1' ,
> but is rans unsuccessfully.
>
> It returned the messages as follows
> ' cannot open table mis1.ac11.'
>
> I tried to drop table using isql , it returns
> error ' isam error 242 '...
>
> It seems to me that the ac11.dat and ac11.idx files are corrupted.
>
> Could anybody help me with this or
> are there any other tools that I can use to get my table schema?
>
> any message from you will be appreciated...
>
> bese rgds
"Hari Gupta" <hariog@yahoo.com> wrote in message news:<Jajza.106$Ve4.4080@news.optus.net.au>...
> This might help -
>
> 1. oncheck -ce
> 2. oncheck -cc
> 3. oncheck -cI
> 4. oncheck cD
Does Standard Engine (she says she is use SE4) have oncheck? Ours
doesn't!
But OTOH - Standard Engine *4*? It's up to 7 now - 4 is well
pre-2000. Is there a mistype here? I don't even remember SE4 - I
remember SE5 and at that time I believe the engines had odd numbers
and the tools even ones. ISQL4 would have been supplied with SE5.
The way to find out is to get it from the engine:
$INFORMIXDIR/bin/sqlexec -V
On our machine (SE7) we get:
INFORMIX-SQL Version 7.24.UC8 Mon Mar 1 14:04:16 PST 1999
Software Serial Number XXX#J123456
(software licence has been altered!)
If V4 or V5 really are in use some hard thought needs to be given
(IMHO) as to why, unless the data is currently being extracted to go
into V7.
Still, to give some possibly more useful information than 'upgrade':
SE has bcheck - running bcheck on the .dat might resolve the problem.
Otherwise with SE it's possible to actually remove the entry from
systables (and the other system catlogues) and resolve the issue that
way (you have to log in as informix to do this if it's installed
correctly). I used to have to be upgrading lots of databases which
started with really old versions of Informix, and part of the process
was often finding orphen entries in the various system catalogues (for
example rows in syscolumns where the tabid was NOT in systables) and
removing them. Sometimes I had to run bcheck on sys*.dat files, and
in once case (v7) I ended up unloading the whole thing via scripts as
the system catalogues where so badly corrupt that dbschema crashed.
>
> Hari
>
> "daisy" <pamela_tw@yahoo.com> wrote in message
> news:43e48577.0305221936.6270fa33@posting.google.com...
> > Hi there ,
> >
> > I am using SE4 on SCO .
> > I tried to get my table schema with
> > ' dbschema -t all -d mydb shema1' ,
> > but is rans unsuccessfully.
> >
> > It returned the messages as follows
> > ' cannot open table mis1.ac11.'
> >
> > I tried to drop table using isql , it returns
> > error ' isam error 242 '...
> >
> > It seems to me that the ac11.dat and ac11.idx files are corrupted.
> >
> > Could anybody help me with this or
> > are there any other tools that I can use to get my table schema?
> >
> > any message from you will be appreciated...
> >
> > bese rgds