When creating a script for a tablespace, either from SB LHS or F4 pop-up
SCRIPT tab, the script is not putting the tablespace into read only mode
if the tablespace is in read only mode.
Toad 10.5.1.3. (Apologies if already sorted in 10.6 onwards.)
Cheers,
Norm. [TeamT]
Information in this message may be confidential and may be legally privileged. If you have received this message by mistake, please notify the sender immediately, delete it and do not copy it to anyone else.
We have checked this email and its attachments for viruses. But you should still check any attachment before opening it.
We may have to make this message and any reply to it public if asked to under the Freedom of Information Act, Data Protection Act or for litigation. Email messages and attachments sent to or from any Environment Agency address may also be accessed by someone other than the sender or recipient, for business purposes.
If we have sent you information and you wish to use it please read our terms and conditions which you can get by calling us on 08708 506 506. Find out more about the Environment Agency at www.environment-agency.gov.uk
Will you be able to load it if it’s read only? Oracle doesn’t allow
“READ ONLY” in the create statement. I could add an “alter
tablespace blah read only” command after the create, but it seems like the
first thing users would have to do before putting anything in there is set it
read/write.
I think that was intentional, because what good is an
empty, read only tablespace?
Ok, I can live with that. However, maybe a little pop-up to say "by the
way, this tablespace is in read only - is that ok?" if the script
generator notices?
The reason I asked was because I noticed it when I was running the
create a script to get me the list of data files in the tablespace for a
transportable tablespace exercise I was undertaking.
I agree that there's not much use for an empty read only tablespace. I
wish I'd given it a bit more thought before making a fool of myself!
And, to answer Bert while I'm here, you don't need to create a blank
holding place for a transportable tablespace, in fact, it should not
exists in the receiving database. Ask me how I know!
Thanks again guys.
Cheers,
Norm. [TeamT]
Information in this message may be confidential and may be legally privileged. If you have received this message by mistake, please notify the sender immediately, delete it and do not copy it to anyone else.
We have checked this email and its attachments for viruses. But you should still check any attachment before opening it.
We may have to make this message and any reply to it public if asked to under the Freedom of Information Act, Data Protection Act or for litigation. Email messages and attachments sent to or from any Environment Agency address may also be accessed by someone other than the sender or recipient, for business purposes.
If we have sent you information and you wish to use it please read our terms and conditions which you can get by calling us on 08708 506 506. Find out more about the Environment Agency at www.environment-agency.gov.uk
How about a comment in the script? That way, if you are just looking at the
script to see what the tablepsace properties are, you’ll see it, but you
won’t have to set it to read-write before you can put something in it.
Backwards. I have read only tablespace on database a that is not empty. I have a
read only tablespace on database b that is empty. I could transport a to b then
…
I am not saying this is a high probability scenario – just that I can see
a scenario to backup the request was all ….
RO tablespaces typically used for historical data
testcase for read-only tablespace: if a WallStreet CFO wants to keep the 08
financial statements for read-only access
does anyone have historical data testcase examples?
Martin
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung.
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n’êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l’expéditeur. N’importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l’information seulement et n’aura pas n’importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.
How about a comment in the script? That way, if you are
just looking at the script to see what the tablespace
properties are, you'll see it, but you won't have to set it
to read-write before you can put something in it.
Yes, that would be excellent. A comment in the script is fine. Thanks.
Have a weekend, as Rich used to say, I'm off to get wet - it's hammering
down!
Cheers me hearties.
Norm. [TeamT]
Information in this message may be confidential and may be legally privileged. If you have received this message by mistake, please notify the sender immediately, delete it and do not copy it to anyone else.
We have checked this email and its attachments for viruses. But you should still check any attachment before opening it.
We may have to make this message and any reply to it public if asked to under the Freedom of Information Act, Data Protection Act or for litigation. Email messages and attachments sent to or from any Environment Agency address may also be accessed by someone other than the sender or recipient, for business purposes.
If we have sent you information and you wish to use it please read our terms and conditions which you can get by calling us on 08708 506 506. Find out more about the Environment Agency at www.environment-agency.gov.uk
