Simple Tablespace Recovery V11 or V12

Jorg Lueke

Simple Tablespace Recovery V11 or V12

Has anyone successfully tested the recover from an image copy of a simple tablespace under V11 or V12? You know, the just in case it happens we can try this type of scenario?

Philip Sevetson

Simple Tablespace Recovery V11 or V12
(in response to Jorg Lueke)
You know how to scare people, don’t you? Is someone actually keeping simple TS in production in V11??
-phil (sevetson)

From: Jorg Lueke [mailto:[login to unmask email]
Sent: Tuesday, June 04, 2019 11:47 AM
To: [login to unmask email]
Subject: [DB2-L] - Simple Tablespace Recovery V11 or V12


Has anyone successfully tested the recover from an image copy of a simple tablespace under V11 or V12? You know, the just in case it happens we can try this type of scenario?

-----End Original Message-----
**This e-mail, including any attachments, may be confidential, privileged, or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy, or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.**

Phil Grainger

Simple Tablespace Recovery V11 or V12
(in response to Philip Sevetson)
Recovering the data is the same as it ever was

BUT you do know you can no longer recreate dropped simple spaces....?

Sent from my iPhone

On 4 Jun 2019, at 17:04, Sevetson, Phil <[login to unmask email]<mailto:[login to unmask email]>> wrote:

You know how to scare people, don’t you? Is someone actually keeping simple TS in production in V11??
-phil (sevetson)

From: Jorg Lueke [mailto:[login to unmask email]
Sent: Tuesday, June 04, 2019 11:47 AM
To: [login to unmask email]<mailto:[login to unmask email]>
Subject: [DB2-L] - Simple Tablespace Recovery V11 or V12


Has anyone successfully tested the recover from an image copy of a simple tablespace under V11 or V12? You know, the just in case it happens we can try this type of scenario?

-----End Original Message-----
**This e-mail, including any attachments, may be confidential, privileged, or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy, or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.**
-----End Original Message-----
BMC Software Limited Registered Office: Building E2, Eskdale Road, Winnersh, Wokingham, Berkshire, United Kingdom, RG41 5TS Registered in England No. 1927903 The content of this email is confidential. If you are not the addressee, you may not distribute, copy or disclose any part of it. If you receive this message in error, please delete this from your system and notify the sender immediately.

Jorg Lueke

RE: Simple Tablespace Recovery V11 or V12
(in response to Philip Sevetson)

Of course no one is keeping them in production in V11, and certainly not in Db2 12. No, no one I know of...

But if they did, and someone dropped a table in a simple tablespace and you had that IC. Is it possible to recover? 

 


In Reply to Philip Sevetson:

You know how to scare people, don’t you? Is someone actually keeping simple TS in production in V11??
-phil (sevetson)


Jorg Lueke

RE: Simple Tablespace Recovery V11 or V12
(in response to Phil Grainger)

I do know that. I'm wondering though if you re-created the object and had the image copy is there some DSN1COPY process whereby the dropped table could be restored? And yes this is hypothetical...for now.

In Reply to Phil Grainger:

Recovering the data is the same as it ever was

BUT you do know you can no longer recreate dropped simple spaces....?


 

Phil Grainger

Simple Tablespace Recovery V11 or V12
(in response to Jorg Lueke)
IF you recreated the object, then dsn1copy is always an option

But you cannot recreate a Simple tablespace any more so the question is moot

You’d have to recreate it as some other type of tablespace, then UNLOAD your image copy and RELOAD the new table/space

With an unload utility that allows you to specify the tables ddl OUTSIDE the catalog

Phil Grainger
Principal Enablement Manager

[BMC Exchange 2019 - Global Event Series - REGISTER] https://www.bmc.com/ami

Direct

+44 1189 218 000

Mobile

+44 7808 643 479

Email

[login to unmask email]

E2, Eskdale Road
Winnersh
Berkshire
United Kingdom
RG41 5TS
[image001 (002)][https://acclaim-production-app.s3.amazonaws.com/images/2429c3cd-a1de-44fc-b4f3-bc762bb2f963/IBM%2BChampion%2B-%2BAnalytics%2B2018.png][https://acclaim-production-app.s3.amazonaws.com/images/2429c3cd-a1de-44fc-b4f3-bc762bb2f963/IBM%2BChampion%2B-%2BAnalytics%2B2018.png]



From: Jorg Lueke <[login to unmask email]>
Sent: 04 June 2019 18:45
To: [login to unmask email]
Subject: [EXTERNAL] [DB2-L] - RE: Simple Tablespace Recovery V11 or V12


I do know that. I'm wondering though if you re-created the object and had the image copy is there some DSN1COPY process whereby the dropped table could be restored? And yes this is hypothetical...for now.

In Reply to Phil Grainger:
Recovering the data is the same as it ever was

BUT you do know you can no longer recreate dropped simple spaces....?




-----End Original Message-----
BMC Software Limited Registered Office: Building E2, Eskdale Road, Winnersh, Wokingham, Berkshire, United Kingdom, RG41 5TS Registered in England No. 1927903 The content of this email is confidential. If you are not the addressee, you may not distribute, copy or disclose any part of it. If you receive this message in error, please delete this from your system and notify the sender immediately.
Attachments

  • image001.jpg (49.7k)
  • image008.png (6.7k)
  • image009.png (3.7k)
  • image010.png (<1k)

Raymond Bell

Simple Tablespace Recovery V11 or V12
(in response to Phil Grainger)
Wow, Phil, that sounds like an excellent feature. Do you know of an unload utility product with that kind of life-saving ability? ;o)

I’m like a stick of BMC rock, I am. :o)

Cheers,


Raymond

From: Grainger, Phil [mailto:[login to unmask email]
Sent: 04 June 2019 20:01
To: [login to unmask email]
Subject: [DB2-L] - RE: Simple Tablespace Recovery V11 or V12


*********************************************
" This message originates from outside our organisation. Consider carefully whether you should click on any links, open any attachments or reply. If in doubt, forward to ~ Phishing"
*********************************************

IF you recreated the object, then dsn1copy is always an option

But you cannot recreate a Simple tablespace any more so the question is moot

You’d have to recreate it as some other type of tablespace, then UNLOAD your image copy and RELOAD the new table/space

With an unload utility that allows you to specify the tables ddl OUTSIDE the catalog

Phil Grainger
Principal Enablement Manager

[BMC Exchange 2019 - Global Event Series - REGISTER] https://www.bmc.com/ami

Direct

+44 1189 218 000

Mobile

+44 7808 643 479

Email

[login to unmask email]

E2, Eskdale Road
Winnersh
Berkshire
United Kingdom
RG41 5TS
[image001 (002)][https://acclaim-production-app.s3.amazonaws.com/images/2429c3cd-a1de-44fc-b4f3-bc762bb2f963/IBM%2BChampion%2B-%2BAnalytics%2B2018.png][https://acclaim-production-app.s3.amazonaws.com/images/2429c3cd-a1de-44fc-b4f3-bc762bb2f963/IBM%2BChampion%2B-%2BAnalytics%2B2018.png]



From: Jorg Lueke <[login to unmask email]>
Sent: 04 June 2019 18:45
To: [login to unmask email]
Subject: [EXTERNAL] [DB2-L] - RE: Simple Tablespace Recovery V11 or V12


I do know that. I'm wondering though if you re-created the object and had the image copy is there some DSN1COPY process whereby the dropped table could be restored? And yes this is hypothetical...for now.

In Reply to Phil Grainger:
Recovering the data is the same as it ever was

BUT you do know you can no longer recreate dropped simple spaces....?



-----End Original Message-----
BMC Software Limited Registered Office: Building E2, Eskdale Road, Winnersh, Wokingham, Berkshire, United Kingdom, RG41 5TS Registered in England No. 1927903 The content of this email is confidential. If you are not the addressee, you may not distribute, copy or disclose any part of it. If you receive this message in error, please delete this from your system and notify the sender immediately.
-----End Original Message-----
The Royal Bank of Scotland plc. Registered in Scotland No 83026. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. The Royal Bank of Scotland is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and Prudential Regulation Authority. The Royal Bank of Scotland N.V. is authorised and regulated by the De Nederlandsche Bank and has its seat at Amsterdam, the Netherlands, and is registered in the Commercial Register under number 33002587. Registered Office: Gustav Mahlerlaan 350, Amsterdam, The Netherlands. The Royal Bank of Scotland N.V. and The Royal Bank of Scotland plc are authorised to act as agent for each other in certain jurisdictions.

National Westminster Bank Plc. Registered in England No. 929027. Registered Office: 135 Bishopsgate, London EC2M 3UR. National Westminster Bank Plc is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and the Prudential Regulation Authority.

The Royal Bank of Scotland plc and National Westminster Bank Plc are authorised to act as agent for each other.

This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc, The Royal Bank of Scotland N.V., National Westminster Bank Plc or any affiliated entity (RBS or us) does not accept responsibility for changes made to this message after it was sent. RBS may monitor e-mails for business and operational purposes. By replying to this message you understand that the content of your message may be monitored.

Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by RBS in this regard and the recipient should carry out such virus and other checks as it considers appropriate.

Visit our website at www.rbs.com http://www.rbs.com
Attachments

  • image002.jpg (49.7k)
  • image003.png (6.7k)
  • image004.png (3.7k)
  • image005.png (<1k)

Michael Arlebrandt

Simple Tablespace Recovery V11 or V12
(in response to Jorg Lueke)
Hi Jorg,

Tested my recovery routine of Simple TS in v12 and it still works :)

As I don't have any simple TS in my test environment I have to start by creating one:
(but we have customers still running with SIMPLE TS in production...)

Restart Db2 with
&SPRMCTU SETC '1' YES=CATALOG CAN BE UPDATED

CREATE TABLESPACE ..
DEFINE NO -- Otherwise a reorg is needed after REPAIR DBD
SEGSIZE 32 -- Create TS as a segmented tablespace
..

CREATE TABLE .. TEST_TABLE_07 in above TS (+ index)
CREATE TABLE .. TEST_TABLE_07B in above TS (+ index) -- just to have a multi-table TS..

UPDATE SYSIBM.SYSTABLESPACE -- Alter SEGSIZE to indicate Simple
SET SEGSIZE = 0
for above TS
REPAIR DBD REBUILD DATABASE dbname -- a must

-START DATABASE(dbname) -- needed after REPAIR DBD

INSERT INTO TEST_TABLE_07 and TEST_TABLE_07B -- to have some data

Select to verify - OK :)

Take an IC

So now we're ready to also test the recovery scenario


Drop the tablespace

Running my recovery routine which I uploaded some years ago to DB2-L

ÄSTEP1 Save DBID, PSID and OBID info
First observation, always tricky to remember what you did some years ago ;)
So this time my rexx complained about nr of tables found...
Had to adjust the DSN1PRNT step to get more pages to find both tables
Tricky to know which table is which based on DSN1PRNT
In V12 we have no “Diagnosis Guide and Reference" to get details about data page layout

ÄSTEP2 Recreate the tablespace and table(s) , used the same routine as above

ÄSTEP3 Rerun ÄSTEP1 to create XLAT option file

ÄSTEP4A If DBID/PSID/OBID changed then we need to translate
by copying IC into new translated IC

But we got the same DBID, PSID and OBIDs :)

ÄSTEP4B Or run DSN1COPY with XLAT to copy IC into Simple TS

If ÄSTEP4A method used then do

ÄSTEP5 Run UNLOAD from "OLD" IC

ÄSTEP6 Load data

EndIf

ÅSTEP7 Run IC and REORG to verify status of TS

And everything is working fine :)

But of course , don't forget to remove that option to be able to update catalog, i.e. Db2 has to be restarted a second time,
so this procedure is really tricky and has a major impact and I can't insure it will always work.

best regards
Michael Arlebrandt

From: Jorg Lueke <[login to unmask email]>
Sent: den 4 juni 2019 5:47
To: [login to unmask email]
Subject: [DB2-L] - Simple Tablespace Recovery V11 or V12


Has anyone successfully tested the recover from an image copy of a simple tablespace under V11 or V12? You know, the just in case it happens we can try this type of scenario?

-----End Original Message-----
::DISCLAIMER::
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Marcus Davage

Simple Tablespace Recovery V11 or V12
(in response to Raymond Bell)
Long, thin and way too sweet?

Regards,
Marcus Davage
Lead Product Developer
AMI-DevOps for Db2 – SQL Performance
Direct

+44 118 921 8517

[cid:[login to unmask email]



Mobile

+44 7840 023 560



Email

[login to unmask email]<mailto:[login to unmask email]>





From: Bell, Raymond (Hosting Services, Technology) <[login to unmask email]>
Sent: 05 June 2019 08:36
To: '[login to unmask email]' <[login to unmask email]>
Subject: [EXTERNAL] [DB2-L] - RE: Simple Tablespace Recovery V11 or V12

Wow, Phil, that sounds like an excellent feature. Do you know of an unload utility product with that kind of life-saving ability? ;o)

I’m like a stick of BMC rock, I am. :o)

Cheers,


Raymond

From: Grainger, Phil [mailto:[login to unmask email]
Sent: 04 June 2019 20:01
To: [login to unmask email]<mailto:[login to unmask email]>
Subject: [DB2-L] - RE: Simple Tablespace Recovery V11 or V12


*********************************************
" This message originates from outside our organisation. Consider carefully whether you should click on any links, open any attachments or reply. If in doubt, forward to ~ Phishing"
*********************************************
IF you recreated the object, then dsn1copy is always an option

But you cannot recreate a Simple tablespace any more so the question is moot

You’d have to recreate it as some other type of tablespace, then UNLOAD your image copy and RELOAD the new table/space

With an unload utility that allows you to specify the tables ddl OUTSIDE the catalog

Phil Grainger
Principal Enablement Manager

[BMC Exchange 2019 - Global Event Series - REGISTER] https://www.bmc.com/ami

Direct

+44 1189 218 000

Mobile

+44 7808 643 479

Email

[login to unmask email]<mailto:[login to unmask email]>

E2, Eskdale Road
Winnersh
Berkshire
United Kingdom
RG41 5TS
[image001 (002)][https://acclaim-production-app.s3.amazonaws.com/images/2429c3cd-a1de-44fc-b4f3-bc762bb2f963/IBM%2BChampion%2B-%2BAnalytics%2B2018.png][https://acclaim-production-app.s3.amazonaws.com/images/2429c3cd-a1de-44fc-b4f3-bc762bb2f963/IBM%2BChampion%2B-%2BAnalytics%2B2018.png]



From: Jorg Lueke <[login to unmask email]<mailto:[login to unmask email]>>
Sent: 04 June 2019 18:45
To: [login to unmask email]<mailto:[login to unmask email]>
Subject: [EXTERNAL] [DB2-L] - RE: Simple Tablespace Recovery V11 or V12


I do know that. I'm wondering though if you re-created the object and had the image copy is there some DSN1COPY process whereby the dropped table could be restored? And yes this is hypothetical...for now.

In Reply to Phil Grainger:
Recovering the data is the same as it ever was

BUT you do know you can no longer recreate dropped simple spaces....?



-----End Original Message-----
BMC Software Limited Registered Office: Building E2, Eskdale Road, Winnersh, Wokingham, Berkshire, United Kingdom, RG41 5TS Registered in England No. 1927903 The content of this email is confidential. If you are not the addressee, you may not distribute, copy or disclose any part of it. If you receive this message in error, please delete this from your system and notify the sender immediately.
-----End Original Message-----
The Royal Bank of Scotland plc. Registered in Scotland No 83026. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. The Royal Bank of Scotland is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and Prudential Regulation Authority. The Royal Bank of Scotland N.V. is authorised and regulated by the De Nederlandsche Bank and has its seat at Amsterdam, the Netherlands, and is registered in the Commercial Register under number 33002587. Registered Office: Gustav Mahlerlaan 350, Amsterdam, The Netherlands. The Royal Bank of Scotland N.V. and The Royal Bank of Scotland plc are authorised to act as agent for each other in certain jurisdictions.

National Westminster Bank Plc. Registered in England No. 929027. Registered Office: 250 Bishopsgate, London EC2M 4AA. National Westminster Bank Plc is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and the Prudential Regulation Authority.

The Royal Bank of Scotland plc and National Westminster Bank Plc are authorised to act as agent for each other.

This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc, The Royal Bank of Scotland N.V., National Westminster Bank Plc or any affiliated entity (RBS or us) does not accept responsibility for changes made to this message after it was sent. RBS may monitor e-mails for business and operational purposes. By replying to this message you understand that the content of your message may be monitored.

Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by RBS in this regard and the recipient should carry out such virus and other checks as it considers appropriate.


Visit our website at www.rbs.com https://urldefense.proofpoint.com/v2/url?u=http-3A__www.rbs.com_&d=DwMFaQ&c=UrUhmHsiTVT5qkaA4d_oSzcamb9hmamiCDMzBAEwC7E&r=mhV0yJKfitu0qAYB_odGUoLWNP8v4L54s7lNo_VjYxo&m=nfCbUZqNc8-C9kPjeQGti1I1vUsJcahcWsWe7Mve0R4&s=SDcKM8gBDuCkw8nNhwquAGKT91--93DWLMYgIGa466o&e=
________________________________
Attachment Links: image002.jpg (51 k) https://urldefense.proofpoint.com/v2/url?u=https-3A__www.idug.org_p_fo_do_-3Fdownload-3D1-26fid-3D10197&d=DwMFaQ&c=UrUhmHsiTVT5qkaA4d_oSzcamb9hmamiCDMzBAEwC7E&r=mhV0yJKfitu0qAYB_odGUoLWNP8v4L54s7lNo_VjYxo&m=nfCbUZqNc8-C9kPjeQGti1I1vUsJcahcWsWe7Mve0R4&s=hbkD-vdTgrolTge2I3V_l5uP-IweueNelx5pS-LZO3Y&e= image003.png (7 k) https://urldefense.proofpoint.com/v2/url?u=https-3A__www.idug.org_p_fo_do_-3Fdownload-3D1-26fid-3D10198&d=DwMFaQ&c=UrUhmHsiTVT5qkaA4d_oSzcamb9hmamiCDMzBAEwC7E&r=mhV0yJKfitu0qAYB_odGUoLWNP8v4L54s7lNo_VjYxo&m=nfCbUZqNc8-C9kPjeQGti1I1vUsJcahcWsWe7Mve0R4&s=ilNcRLLbSN5hJX8Qda5St6NZMbk8LhRR8pQ6Bgfi1cY&e= image004.png (4 k) https://urldefense.proofpoint.com/v2/url?u=https-3A__www.idug.org_p_fo_do_-3Fdownload-3D1-26fid-3D10199&d=DwMFaQ&c=UrUhmHsiTVT5qkaA4d_oSzcamb9hmamiCDMzBAEwC7E&r=mhV0yJKfitu0qAYB_odGUoLWNP8v4L54s7lNo_VjYxo&m=nfCbUZqNc8-C9kPjeQGti1I1vUsJcahcWsWe7Mve0R4&s=u01Ds--Hf0BgrwP6eqtgBPqGnPsKsXdpQqwMLZnrwno&e= image005.png (1 k) https://urldefense.proofpoint.com/v2/url?u=https-3A__www.idug.org_p_fo_do_-3Fdownload-3D1-26fid-3D10200&d=DwMFaQ&c=UrUhmHsiTVT5qkaA4d_oSzcamb9hmamiCDMzBAEwC7E&r=mhV0yJKfitu0qAYB_odGUoLWNP8v4L54s7lNo_VjYxo&m=nfCbUZqNc8-C9kPjeQGti1I1vUsJcahcWsWe7Mve0R4&s=aJZTSvZ3qgWPWb0rKhGruuRh8sL1YVkR6PmfMxDPwa0&e=
Site Links: View post online https://urldefense.proofpoint.com/v2/url?u=https-3A__www.idug.org_p_fo_st_-3Fpost-3D189338-26anc-3Dp189338-23p189338&d=DwMFaQ&c=UrUhmHsiTVT5qkaA4d_oSzcamb9hmamiCDMzBAEwC7E&r=mhV0yJKfitu0qAYB_odGUoLWNP8v4L54s7lNo_VjYxo&m=nfCbUZqNc8-C9kPjeQGti1I1vUsJcahcWsWe7Mve0R4&s=SaAc1RLsZW74jTGw-HJFqxdqy8fVtfoAfg84V8dRNP8&e= View mailing list online https://urldefense.proofpoint.com/v2/url?u=https-3A__www.idug.org_p_fo_si_-3Ftopic-3D19&d=DwMFaQ&c=UrUhmHsiTVT5qkaA4d_oSzcamb9hmamiCDMzBAEwC7E&r=mhV0yJKfitu0qAYB_odGUoLWNP8v4L54s7lNo_VjYxo&m=nfCbUZqNc8-C9kPjeQGti1I1vUsJcahcWsWe7Mve0R4&s=oNddFy_yEQDdwNrkZb25D_ir5U2-lhkH4-XEU_YZZGc&e= Start new thread via email<mailto:[login to unmask email]> Unsubscribe from this mailing list<mailto:[login to unmask email]?Subject=Unsubscribe> Manage your subscription https://urldefense.proofpoint.com/v2/url?u=https-3A__www.idug.org_p_us_to_&d=DwMFaQ&c=UrUhmHsiTVT5qkaA4d_oSzcamb9hmamiCDMzBAEwC7E&r=mhV0yJKfitu0qAYB_odGUoLWNP8v4L54s7lNo_VjYxo&m=nfCbUZqNc8-C9kPjeQGti1I1vUsJcahcWsWe7Mve0R4&s=a9dOhsT81XyHEfotZ5G-ZiZn3oxWKthmGHEbI8wkqs8&e=

This email has been sent to: [login to unmask email]<mailto:[login to unmask email]>

ESAi has well-regarded tools for Fast Cloning, Buffer Pool Tuning, Log Analysis, TDM & more.
BCV4, BCV5, BPA4DB2, ULT4DB2... modern power tools to get the job done faster & easier than ever.
http://www.ESAIGroup.com/idug https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ESAIGroup.com_idug&d=DwMFaQ&c=UrUhmHsiTVT5qkaA4d_oSzcamb9hmamiCDMzBAEwC7E&r=mhV0yJKfitu0qAYB_odGUoLWNP8v4L54s7lNo_VjYxo&m=nfCbUZqNc8-C9kPjeQGti1I1vUsJcahcWsWe7Mve0R4&s=zz8cq63ROksmNNmvk3hqqNGpaFDD1c9ZF13-6cMWbKQ&e=

Use of this email content is governed by the terms of service at:
http://www.idug.org/p/cm/ld/fid=2 https://urldefense.proofpoint.com/v2/url?u=http-3A__www.idug.org_p_cm_ld_fid-3D2&d=DwMFaQ&c=UrUhmHsiTVT5qkaA4d_oSzcamb9hmamiCDMzBAEwC7E&r=mhV0yJKfitu0qAYB_odGUoLWNP8v4L54s7lNo_VjYxo&m=nfCbUZqNc8-C9kPjeQGti1I1vUsJcahcWsWe7Mve0R4&s=-lhRcZj4ZqxBBGO3vj2iwDO9v7xJmd_8kKmeyLKaNmQ&e=

________________________________
BMC Software Limited Registered Office: Building E2, Eskdale Road, Winnersh, Wokingham, Berkshire, United Kingdom, RG41 5TS Registered in England No. 1927903 The content of this email is confidential. If you are not the addressee, you may not distribute, copy or disclose any part of it. If you receive this message in error, please delete this from your system and notify the sender immediately.
Attachments

  • image007.jpg (49.7k)
  • image008.png (6.7k)
  • image009.png (3.7k)
  • image010.png (<1k)
  • image002.png (12.8k)

Jorg Lueke

RE: Simple Tablespace Recovery V11 or V12
(in response to Michael Arlebrandt)

Thanks Michael. I know some people who want to test such a scenario so your process is appreciated and should keep them occupied and happy :)