KSG wrote:There is no such thing " best init.ora settings".To optimal setting initialization parameter you have to analyze your database and OS properly.All these depend your system activities and available resources.This is generally called instance and OS tuning.Firstly you have to find what is a problem(performance related and problem area).Then after finding these begin investigate that(use tuning tools,dynamic performance views,AWR/STATSPACK report,using tracing feature(sql trace/tkprof utility)).Finally i suggest you refer performance guide.
Oracle 220.127.116.11.0 on Suse Linux.
Can you please let me know what are the things need to be followed while setting init.ora parameters for the database?
And, can you please suggest me the best init.ora settings for the database?
KSG wrote:Get a complete list of index definitions before and after the import - a strategy like this can result in some indexes "going missing" on the import for any tables that have multiple indexes that could all support primary key or unique constraints.
To upgrade database from 9i sun os to 11G suse linux.
For this, I'm going to perfrom exp/imp.
I have to create a database on 11g, where I have to set all the best setting init.ora paremeters. My database is aroung 25-50GB.Every database needs at least a little special consideration, but you should at least test the effects of removing all the "little tweak" optimizer parameters such as db_file_multiblock_read_count, optimizer_index_cost_adj, optimizer_index_caching - if you have them in place. Similarly check the reason for any EVENT settings or hidden parameter settings and assume that they should be removed on upgrade.