I recall during a recent course being told there is a problem when upgrading to a 9i database and making the system tablespace locally managed when the previous version was not. The only thing I can remember is that it makes the tablespace READ ONLY but I am not sure how you can avoid the problem.
This issue stems from converting SYSTEM to a locally managed tablespace (LMT) before all other dictionary managed tablespaces are converted to locally managed tablespaces. If SYSTEM is converted first, any other dictionary managed tablespaces cannot be made READ WRITE. You should migrate any tablespaces you want in READ WRITE mode to locally managed before the SYSTEM tablespace is migrated or converted. There are further restrictions when migrating SYSTEM to LMT. For example, after converting SYSTEM to LMT, you will not be able to create any new dictionary managed tablespaces in that database. You will also not be able to migrate a locally managed SYSTEM tablespace back to dictionary managed.
Having said this, it's important to remember that you can only make the SYSTEM tablespace locally managed as of Oracle 9.2.
Dig Deeper on Oracle database installation, upgrades and patches
Can I use /var/opt/oracle/oratab to specify listener information?
We would like to migrate our database from Oracle 8.1.7 to Oracle 10g. We would like to know the impact for our application developed using Delphi ...
I have been trying to install Oracle 8.1.7 on SUSE Linux 9.0 and got the error:
"Error in invoking target install of makefile /opt/oracle/...../*.mk."
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.