This content has been marked as final. Show 5 replies
Yes... You can use the page "Migrate to ASM" to add ASM As an Enterprise Manager Target.
You don't need migrate your database to ASM, only save configuration of ASM target on OEM and ASM can be managed by OEM
See this example.
Or you can create a tablespace (2mb) on ASM using OEM, it will add ASM as EM target. Then remove this tablespace and ASM target will be configured.
Edited by: Levi Pereira on Nov 9, 2012 3:13 PM
Very cool viewlet video -- soon all documentation will look like that.
I had an interesting experience.
I followed the steps to "Migrate to ASM" to get a feel for what the options were. I didn't want to migrate the DB right now so I entered the ASM credentials/config info on the 1st page and then de-selected "DB files" and selected "Recovery Related Files" to see what I might be able to migrate.
From the "Flash Recovery Area" page there is an option to "Setup Flash Recovery Area without Migrating Recovery-related Files".
I thought that this would be an easy thing to do first but I wanted to read the documentation for what this was going to do. So I canceled the whole "Migrate DB to ASM" operation.
Then, after reading up on what to expect I went back to the "Migrate to ASM" process again and at this point the ASM instance had already been discovered.
So it appears that simply configuring the first page of the "Migrate to ASM" operation is enough to prompt OEM to configure the ASM target.