Sometimes my job has a aspect making me smile at the end of the day 😉 I sat together with Johannes Ahrends during a talk at the OUGN Conference on the boat from Oslo towards Kiel.And we were discussing afterwards why there’s no official way to limit the number of PDBs which will be essential for customers wanting to go the Single Tenant track.So I did ask my contacts internally and received a message saying clearly “Somebody doesn’t want this.“.🙂 Well, I work long enough for Oracle to know how to read it.Most of you will say: "Why on earth would you ever want to change this programmaticly". Properties["vti_title"] and this watch does change to the new value. I've used Update, System Update, Update Overwrite Version, SPFile. This was required by the customer for a "read/edit area concept". I am using this code, but it does not change anything in the "Version History" in the UI.I suspect this to be caused by applications that are not using bind variables, but I have not yet researched this further.When you have such an occasion you can do 4 things : I went with option number 4, as the application was not developed by us and I still wanted oracle to be able to move memory from one pool to the other.
(for none RMS libraries we could use this fix as mentioned on the internet)Ok.$ cd $ORACLE_HOME/dbs $ mv old_SQL> startup force ORACLE instance started. SQL> create pfile='/tmp/orcl.pfile' from spfile; File created. SQL> show parameter spfile NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ spfile string DATA/orcl/Datavail is focused on data management and business intelligence; application development, modernization and support; and database support for Oracle, Oracle Applications, Microsoft Applications, SQL Server, DB2, My SQL, Mongo DB and Share Point.SQL> create spfile=' DATA' from pfile='/tmp/orcl.pfile'; File created. From managed services and consulting, to projects, and 24x7 operational support, Datavail has you and your data covered.I'm not that into RMS so I don't think I'll be able to solve your problem. If you can use SPFile Version to get an old version of the file, would it be possible to move that one first and then overwrite it with the next version and so on? Jasper, that is exactly what is possible without RMS.When using automatic sga management (sga_target), you might notice that your shared pool sometimes keeps growing, at the cost of the db_cache_size.