Initialization Parameter Changes from 9i to 10g

Initialization Parameter and Data Dictionary Changes
1.Initialization Parameter Changes
  A.  Deprecated Initialization Parameters
          SQL> SELECT name FROM v$parameter
               WHERE isdeprecated = 'TRUE';
          Note:A deprecated parameter behaves the same way as a regular parameter,but if a deprecated parameter is specified in the parameter file,
               then a warning message is displayed at instance startup .
      Initialization Parameters Deprecated in Release 10.2
          LOGMNR_MAX_PERSISTENT_SESSIONS
          MAX_COMMIT_PROPAGATION_DELAY
          REMOTE_ARCHIVE_ENABLE
          SERIAL_REUSE
          SQL_TRACE      
  B.  Obsolete Initialization Parameters
          Note:An attempt to start a release 10.1 database using one or more of these obsolete initialization parameters will succeed, but a warning will be returned and recorded in the alert log.
      Initialization Parameters Obsolete in Release 10.2
          ENQUEUE_RESOURCES        
         
2.Compatibility Issues with Initialization Parameters
  A. OPEN_CURSORS --&gt SESSION_CACHED_CURSORS (>=10.1 release:the number of SQL cursors cached by PL/SQL was determined )                        
  
   待續

參考文獻：