HDR and Tempspace problem
Posted in 1999
Topics: High Availability & Replication, Storage & Space Management, Server Administration
Hi,
I've set up a HDR Primary/Secondary pair of Informix 7.31 on
Solaris x86.
All works fine, except that certain complex "select" queries on the
secondary server result in a "Cannot create temporary file" error
(code -229).
None of my six tablespaces is a temp tablespace, and DBSPACETEMP is
set to empty in the config file. A comment in the demo config file
says:
# DBSPACETEMP:
[...]
# If not specified, or if
# all dbspaces specified are invalid, various ad hoc queries will create
# temporary files in /tmp instead.
So I assumed that /tmp will be used and all will be fine. However,
on page 14-21 in the Admin guide, they say:
> Important: When OnLine is running as a secondary database server
> in a data-replication pair, it requires a temporary dbspace to store
> any internal temporary tables generated by read-only queries.
That sounds exactly like my problem! So I tried to create a temporary
dbspace on the secondary with "onmonitor" (no success - "invalid
argument in ISAM command" or some such) and with "onspaces" (no
success either - "This operation cannot be performed on a secondary
server"). So I set the secondary back to "Standard" mode to create
the temp space, which was stupid because after that it didn't want
to become a secondary again and I had to recover from a level 0
backup.
So what's the deal - do I actually need ne same temp space on the
Primary and Secondary for the Secondary to work? Why doesn't /tmp
do?
Any help is much appreciated!
Bye
Frederik
--
Frederik Ramm (frederik@remote.org)
Frederik Ramm <frederik@remote.org> wrote: > All works fine, except that certain complex "select" queries on the > secondary server result in a "Cannot create temporary file" error > (code -229). I think I solved the problem by creating a temp dbspace on the primary server (although *that* server worked fine without even before.) Bye Frederik -- Frederik Ramm (frederik@remote.org)