HDR Secondary: Could not open or create a temporar
Posted in 2013
Topics: High Availability & Replication, Storage & Space Management, Error Codes & Troubleshooting, Server Administration
On our HDR Secondary and RSS secondary, whenever we run certain queries (a
sub-select, for example), we get this error:
229: Could not open or create a temporary file.
140: ISAM error: operation illegal on a DR secondary
This only happens on the HDR Secondary and RSS secondary, on the HDR Primary
it works fine.
In onconfig, our DBSPACETEMP is empty on all servers.
Any advice on tracking down why this is failing would be helpful.
Thanks in advance,
-Justin
This can happen under three conditions:
1. UPDATEABLE_SECONDARY is not set on the secondary
2. UPDATEABLE_SECONDARY is set but:
1. You are trying an operation illegal on a writable secondary like
CREATE DATABASE, CREATE EXTERNAL TABLE, CREATE RAW TABLE,
altering a table
to RAW mode, etc.
2. The session getting the error does not have DBSPACETEMP set to
include temp dbspaces (make sure your temp dbspaces are REALLY temp) and
the secondary's ONCONFIG does not have DBSPACETEMP set as above.
Art
Art S. Kagel
Advanced DataTools (www.advancedatatools.com)
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions
and do not reflect on my employer, Advanced DataTools, the IIUG, nor any
other organization with which I am associated either explicitly,
implicitly, or by inference. Neither do those opinions reflect those of
other individuals affiliated with any entity with which I am affiliated nor
those of the entities themselves.
On Wed, Jul 31, 2013 at 8:09 PM, Justin Killen <
jkillen@allamericanasphalt.com> wrote:
> On our HDR Secondary and RSS secondary, whenever we run certain queries (a
> sub-select, for example), we get this error:
>
> 229: Could not open or create a temporary file.
> 140: ISAM error: operation illegal on a DR secondary>
> This only happens on the HDR Secondary and RSS secondary, on the HDR
> Primary
> it works fine.
>
> In onconfig, our DBSPACETEMP is empty on all servers.
>
> Any advice on tracking down why this is failing would be helpful.
>
> Thanks in advance,
> -Justin
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--089e014946f49dbcbb04e2d7f1b5