Aamir Haroon said...Thanks Tim for this article. I upgraded database from 184.108.40.206 to 18c and database_properites didn't have row with LOCAL_UNDO_ENABLED
SYS@CDB$ROOT>SELECT property_name, property_value
2 FROM database_properties
3* WHERE property_name = 'LOCAL_UNDO_ENABLED';
0 rows selected.
I went through the steps to switch to local undo anyways and now there is row in database_properties.
Aamir Haroon said...Also, this is interesting. Querying CDB_TABLESPACES gives me 2 rows for my PDB:
SYS@CDB$ROOT>SELECT con_id, tablespace_name
2 FROM cdb_tablespaces
3 WHERE tablespace_name LIKE 'UNDO%'
4* ORDER BY con_id;
Yes. Just tested it.
1) I see the same "no rows selected". I've added a note to the article. Thanks for the heads-up.
2) I don't see two undo tablespaces for the PDB.
Ronald Rood said...hi Tim,
the queries work, when a certain naming convention is in place. I truly believe it is more solid to use the "content = 'UNDO'" instead of using a naming convention.
Thanks for the hard work you put in this site, it's an amazing piece of work.
You are correct. It is bad form for me to assume the naming convention. I will change it. Thanks for keeping me honest. :)
DO NOT ask technical questions here! They will be deleted!
These comments should relate to the contents of a specific article. Constructive criticism is good. Advertising and offensive comments are bad and will be deleted!
If you post personal information (name, email address etc.) you are agreeing to them being stored and displayed. Feel free to remain anonymous.