Re: 7.14 Data Replication/Temp DB Spaces
Different platform but similar problem at the 7.1 level. We found that
we needed to export DBSPACETEMP values befored executing program, in
our situation dbaccess or ace reports at which point we successfully
had temp space that was used on the secondary. It appears to be
a bug in the engine which I am hoping is fixed at 7.2 level.
Hope that helps.
--
Con Woodall Colorado St. U.; Veterinary Teach. Hosp.; Ft. Collins CO 80523,
USofA; 970-491-1244 FAX 970-491-4100 cwoodall@vth1.vth.colostate.edu
"There is no 'maybe' in Boolean algebra."
--
On Mon, 28 Jul 1997, Jason Harris wrote:
} Dear All,
}
} We recently enabled data replication between two NCR servers running
} 7.14 Online. On the primary there are 4 temp dbspaces that are defined
} in DBSPACETEMP. On the secondary these dbspaces are not available. The
} result being that queries that need temp tables will not work on the
} secondary server.
}
} The problem, I believe, stems from the fact that temp db spaces are
} not backed up. This means that while they show in the reserved pages
} and are listed as db spaces they were not created by the restore.
} Maybe we should have manually created them on the secondary before
} doing the restore.
}
} Basically we have the temp spaces on the primary but cannot access
} them on the secondary. We cannot drop and re-create them on the
} secondary as this is a logged operation and it cannot be performed on
} the secondary.
}
} Any one have thoughts on this? I believe we will have to drop and
} re-create them on the primary and have this replicated over onto the
} secondary. But we dont want to do this unless we have to.
}
} Regards,
}
} Jason
}