On Mar 17, 5:32 pm, "J. Hart" <unleashedman...@gmail.com> wrote:
> On Mar 16, 9:26 am, jrenaut <jpren...@yahoo.com> wrote:
>
>
>
> > > Oh, I forgot to add in that the informix database is a read only DR
> > > server. So, we are not able to alter the table structure, create
> > > stored procedures/functions or temp tables... It's a pain in the neck
> > > dealing with the vendor and informix. I wish there was an easy
> > > solution for replicating informix to MS SQL.
>
> > > James
>
> > As somewhat of a side note, if you have a temporary dbspace that was
> > created with the -t option, then even on a read only server of a HDR
> > pair, you can still create/use temporary tables. You just need to
> > ensure they are built with the "with no log" option and they should
> > work fine.
>
> > Jacques Renaut
> > IBM Informix Advanced Support
> > APD Team
>
> Hey Jacques,
>
> I tried this...
>
> CREATE TEMP TABLE tab2 (fname CHAR(15), lname CHAR(15))
> WITH NO LOG>
> and got the following error: "Could not open or crate a temporary
> file. ISAM error: operation illegal on a DR Secondary"
>
> James
As Jonathan mentioned already, it would suggest you don't have a
temporary dbspace. To check this, you would want to look at what you
have DBSPACETEMP set to in your onconfig file, and then look at onstat
-d output. For the temp table activity to work on the read only
secondary you need to have a dbspace from DBSPACETEMP show up in the
onstat -d output with like the dbspace tmpdbs below:
Dbspaces
address number flags fchunk nchunks pgsize
flags owner name
10aeb5e78 1 0x60001 1 1 2048
N B informix rootdbs
10b056d98 2 0x62001 2 1 2048 N
TB informix tmpdbs
2 active, 2047 maximum
So in that output the dbspace tmpdbs has the "T" in the 2nd flags
field.