Errors and Recovery for the Server Parameter File
If an error occurs while reading the server parameter file (during startup or an export
operation), or while writing the server parameter file during its creation, the operation
terminates with an error reported to the user.
If an error occurs while reading or writing the server parameter file during a
parameter update, the error is reported in the alert log and all subsequent parameter
updates to the server parameter file are ignored. At this point, you can take one of the
following actions:
■ Shut down the instance, recover the server parameter file, and then restart the
instance.
■ Continue to run the database if you do not care that subsequent parameter
updates will not be persistent.[@more@]
operation), or while writing the server parameter file during its creation, the operation
terminates with an error reported to the user.
If an error occurs while reading or writing the server parameter file during a
parameter update, the error is reported in the alert log and all subsequent parameter
updates to the server parameter file are ignored. At this point, you can take one of the
following actions:
■ Shut down the instance, recover the server parameter file, and then restart the
instance.
■ Continue to run the database if you do not care that subsequent parameter
updates will not be persistent.[@more@]
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/10599713/viewspace-1002612/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- What Is a Server Parameter File?Server
- Exporting the Server Parameter FileExportServer
- Migrating to a Server Parameter FileServer
- Step 5: Create a Server Parameter File (Recommended) (63)Server
- Initialization Parameter Files and Server Parameter Files (287)Server
- Oracle Server Parameter FilesOracleServer
- Step 3: Create the Initialization Parameter File (61)
- The Db2 Recovery History FileDB2
- Backing Up Server Parameter Files with RMANServer
- contains a file system with errors, check forced解決方法AIError
- errors in crontab file, can't install. - linux crontabErrorLinux
- SQL Server進行Crash RecoverySQLServer
- ORA-00600 [4194]/[4193] Errors Without Using Unsupported parameter-281429.1Error
- SQL SERVER – Attach mdf file without ldf file in DatabaseSQLServerDatabase
- SQL Server小知識:Recovery IntervalSQLServer
- OGG-01453 Database login information not specified in parameter fileDatabaseORM
- Oracle歸檔日誌使用情況: v$recovery_file_dest and v$recovery_area_usage.Oracle
- Oracle RAC 重置db_recovery_file_dest_size引數Oracle
- Oracle歸檔目錄 和 DB_RECOVERY_FILE_DESTOracle
- oracle 修改archive的地址到db_recovery_file_destOracleHive
- 【分散式計算】MapReduce的替代者-Parameter Server分散式Server
- oracle parallel並行_引數parameter_parallel_max_serverOracleParallel並行Server
- [oracle]log_archive_dest_n與DB_RECOVERY_FILE_DESTOracleHive
- MySQL server PID file could not be found!MySqlServer
- 【crontab】“bad minute”及“errors in crontab file, can't install”錯誤處理Error
- The server quit without updating PID fileServerUI
- SQL Server的幾種恢復模式(recovery models)SQLServer模式
- LRM-00109: could not open parameter file '/u01/.../dbs/initshdb.ora'
- psql: error: could not connect to server: No such file or directorySQLErrorServer
- Description of restoring file and filegroup backups in SQL ServerRESTSQLServer
- Oracle ParameterOracle
- Required parameter $xxx follows optional parameter $yyyUI
- Metric Collection ErrorsError
- oracle之errorsOracleError
- oracle 之errorsOracleError
- WebLogic啟動報Could not get the server file lockWebServer
- [zt]如何進行SQL Server 2000進行Disaster RecoverySQLServerAST
- The SPFILE Initialization Parameter