tag:blogger.com,1999:blog-2530682427657016426.post6237494274817627362..comments2024-03-28T08:29:25.033+01:00Comments on Marko Sutic's Database Blog: How to move SYSTEM tablespace with minimum downtimeMarko Sutichttp://www.blogger.com/profile/08926232581329666732noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-2530682427657016426.post-59509775852369501442015-06-29T13:13:20.237+02:002015-06-29T13:13:20.237+02:00Thanks!.Thanks!.Maykonhttps://www.blogger.com/profile/18067783454292502076noreply@blogger.comtag:blogger.com,1999:blog-2530682427657016426.post-68499983377041955602012-09-21T10:01:53.275+02:002012-09-21T10:01:53.275+02:00Bradd,
my comment above is not completely correct...Bradd,<br /><br />my comment above is not completely correct. UNDO can be pre-created like you said and shutdown is not necessary in that case.<br />I tend to shutdown database before moving UNDO,SYSTEM and SYSAUX but I should change this habit. Pre-creating UNDO is more convenient way.<br /><br />In post, why I meant that some DBA's are not comfortable with moving UNDO tablespace. In some situations "old UNDO" can be in PENDING OFFLINE mode for some time. Then you must wait pending transactions to finish before drop. This can be little confusing for inexperienced DBA.<br /><br />I didn't even tried to move SYSAUX on running instance.<br />Thanks for the info!<br /><br />Kind regards,<br />MarkoMarko Sutichttps://www.blogger.com/profile/08926232581329666732noreply@blogger.comtag:blogger.com,1999:blog-2530682427657016426.post-46268577450426930912012-09-20T19:09:03.051+02:002012-09-20T19:09:03.051+02:00Undo doesn't necessarily have to be done this ...Undo doesn't necessarily have to be done this way. I typically pre-create a new UNDO tablespace, TEMP tablepsace, and new online redo log files so the only real shutdown dependency would be on the SYSTEM tablespace. I wasn't aware you could switch SYSAUX in this manner as well. For safety reasons, I tend to do SYSAUX at the same time as SYSTEM.Bradd Piontekhttps://www.blogger.com/profile/09812125551238871609noreply@blogger.comtag:blogger.com,1999:blog-2530682427657016426.post-45016013273324633812012-08-17T11:00:13.718+02:002012-08-17T11:00:13.718+02:00For SYSTEM or UNDO tablespaces you must bounce you...For SYSTEM or UNDO tablespaces you must bounce your instance but for other datafiles this step is not needed. You can flag other datafiles as read only during relocating and with this step recovery is not needed. This is the safest method which I use for moving datafiles.<br /><br />Regards,<br />MarkoMarko Sutichttps://www.blogger.com/profile/08926232581329666732noreply@blogger.comtag:blogger.com,1999:blog-2530682427657016426.post-27567756711330031392012-08-16T15:56:26.874+02:002012-08-16T15:56:26.874+02:00I guess we can apply same procedure for any other ...I guess we can apply same procedure for any other DB file /tablespace , correct ? That would mean if we decide to relocate 10TB database the only downtime would be during switching files, which is great!Anonymousnoreply@blogger.com