Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
David Grove could not drop an unlogged (raw) table on an RSS although he had dropped it on the primary, which blocked dbexport. Luis Marques asked whether STOP_APPLY 1 was active on the RSS during the drop. David confirmed he had forgotten to reset STOP_APPLY before dropping on the primary. Solved.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
DAVID GROVE — — source: IIUG Forums & Mailing Lists
IDS 12.10.FC3
Solaris 10 1/13
I have an unlogged table in an RSS. I would like to DROP it. But, I cannot
access it to DROP it. I can see it in Server Studio and dbAccess, but cannot
execute a DROP TABLE command on it (because it is inaccessible because it is
raw).
I have already DROPed it from the primary.
How can I get rid of it on the RSS?
Thank you.
DG
↪ replying to DAVID GROVE
DAVID GROVE — — source: IIUG Forums & Mailing Lists
P.S. The problem is that I want to dbexport that database. But, I cannot run
dbexport because it errors out when it comes to the unlogged table. But, I
cannot drop it because it errors out when trying to access it (i.e., run the
DROP command).
Sort of like, "I can't get there from here".
Is the only solution to DROP the entire database, and start RSS completely
from the beginning? Surely there must be a way to get rid of that table.
↪ replying to DAVID GROVE
LUIS MARQUES — — source: IIUG Forums & Mailing Lists
Dropping the RAW table on the primary should have been replicated to the RSS
secondary. Have you dropped the table while the the "STOP_APPLY 1" was active
on the RSS?
↪ replying to LUIS MARQUES
DAVID GROVE — — source: IIUG Forums & Mailing Lists
The fault was totally mine.
Indeed Mr. Marques nailed it.
I had set STOP_APPLY to 1 so that I could do a dbexport. After dbexport
crashed because it encountered the raw table, I failed to reset the STOP_APPLY
before DROPing the table in the primary. So, naturally, it didn't DROP in the
RSS. And, of course, no operations in the secondary could touch it.
Thank you.
DG
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.