Showing posts with label PDB. Show all posts
Showing posts with label PDB. Show all posts
Monday, March 9, 2015
Multitenant: Resource Manager runs too many sessions
I have posted about Multitenant once, twice, or maybe a few more times so tonight the My Oracle Support post "Excessive throttling by CPU Manager" from article ID 1590014.1 caught my eye for multiple reasons: this is the first time I remember seeing Multitenant on anything other than 12c, and it really surprises me that a simple problem like this creeps up with just a few PDBs after just a couple of minutes!
Monday, March 17, 2014
What prevents you from dropping a tablespace in a 12c PDB?
As we're looking to go to 12c, I've found myself paying more attention to this content so MOS note 1634495.1 grabbed my attention when it talked about receiving the following when trying to drop a tablespace in a 12c PDB:
ERROR at line 1:
ORA-00604: error occurred at recursive SQL level 1
ORA-65040: operation not allowed from within a pluggable database
This is especially interesting for me as the application on top of the database that we are migrating to 12c uses tablespaces as versioning, so we started out with VERSION as the initial tablespace name and the next release was in a tablespace named VERSION2, etc. Well, what happens now when we migrate the database to 12c and our initial tablespace can no longer be removed? This note tells you why it is an issue, how you resolve it, and will be a key reference document I'm sure by our team down the road.
ERROR at line 1:
ORA-00604: error occurred at recursive SQL level 1
ORA-65040: operation not allowed from within a pluggable database
This is especially interesting for me as the application on top of the database that we are migrating to 12c uses tablespaces as versioning, so we started out with VERSION as the initial tablespace name and the next release was in a tablespace named VERSION2, etc. Well, what happens now when we migrate the database to 12c and our initial tablespace can no longer be removed? This note tells you why it is an issue, how you resolve it, and will be a key reference document I'm sure by our team down the road.
Subscribe to:
Posts (Atom)