ORA-32004 的錯誤處理
--=======================
-- ORA-32004 的錯誤處理
--=======================
啟動資料庫時,收到了ORA-32004 的錯誤,錯誤多是一些過時且在當前版本中不在使用的引數,如果碰到類似的錯誤,只需要將其
reset即可。
1.出現的錯誤提示
sys@ORCL> startup
ORA-32004: obsolete and/or deprecated parameter(s) specified
ORACLE instance started.
Total System Global Area 184549376 bytes
Fixed Size 1218412 bytes
Variable Size 83888276 bytes
Database Buffers 96468992 bytes
Redo Buffers 2973696 bytes
Database mounted.
Database opened.
2.檢視告警日誌獲得如下資訊
sys@ORCL> ho oerr ora 32004 --分析錯誤
32004, 00000, "obsolete and/or deprecated parameter(s) specified"
// *Cause: One or more obsolete and/or parameters were specified in
// the SPFILE or the PFILE on the server side.
// *Action: See alert log for a list of parameters that are obsolete.
// or deprecated. Remove them from the SPFILE or the server
// side PFILE.
--從告警日誌中獲得如下資訊
Deprecated system parameters with specified values:
sql_trace
End of deprecated system parameter listing
3.從spfile引數中清除過時的引數後啟動正常
sys@ORCL> alter system reset sql_trace scope=spfile sid='*';
System altered.
sys@ORCL> startup force;
ORACLE instance started.
Total System Global Area 184549376 bytes
Fixed Size 1218412 bytes
Variable Size 83888276 bytes
Database Buffers 96468992 bytes
Redo Buffers 2973696 bytes
Database mounted.
Database opened.
4.檢視當前版本不再建議使用的引數
sys@ORCL> select * from v$version where rownum < 2;
BANNER
----------------------------------------------------------------
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
sys@ORCL> select name,description
2 from v$parameter where isdeprecated='TRUE';
NAME DESCRIPTION
------------------------------ --------------------------------------------------------------
lock_name_space lock name space used for generating lock names for standby/clo
ne database
buffer_pool_keep Number of database blocks/latches in keep buffer pool
buffer_pool_recycle Number of database blocks/latches in recycle buffer pool
max_commit_propagation_delay Max age of new snapshot in .01 seconds
remote_archive_enable remote archival enable setting
log_archive_start start archival process on SGA initialization
parallel_server if TRUE startup in parallel server mode
parallel_server_instances number of instances to use for sizing OPS SGA structures
fast_start_io_target Upper bound on recovery reads
logmnr_max_persistent_sessions maximum number of threads to mine
serial_reuse reuse the frame. segments
max_enabled_roles max number of roles a user can have enabled
global_context_pool_size Global Application Context Pool Size in Bytes
plsql_compiler_flags PL/SQL compiler flags
sql_trace enable SQL trace
parallel_automatic_tuning enable intelligent defaults for parallel execution parameters
drs_start start DG Broker monitor (DMON process)
5.下面是Oracle 10gR2不再支援的引數
* ENQUEUE_RESOURCES (undocumented in 10gR2)
* DBLINK_ENCRYPT_LOGIN
* HASH_JOIN_ENABLED (undocumented parameter)
* LOG_PARALLELISM (undocumented parameter)
* MAX_ROLLBACK_SEGMENTS
* MTS_CIRCUITS (this is replaced by CIRCUITS)
* MTS_DISPATCHERS (this is replaced by DISPATCHERS)
* MTS_LISTENER_ADDRESS
* MTS_MAX_DISPATCHERS (this is replaced by MAX_DISPATCHERS)
* MTS_MAX_SERVERS (this is replaced by MAX_SHARED_SERVERS)
* MTS_MULTIPLE_LISTENERS
* MTS_SERVERS (this is replaced by SHARED_SERVERS)
* MTS_SERVICE
* MTS_SESSIONS (this is replaced by SHARED_SERVER_SESSIONS)
* OPTIMIZER_MAX_PERMUTATIONS (undocumented parameter)
* ORACLE_TRACE_COLLECTION_NAME
* ORACLE_TRACE_COLLECTION_PATH
* ORACLE_TRACE_COLLECTION_SIZE
* ORACLE_TRACE_ENABLE
* ORACLE_TRACE_FACILITY_NAME
* ORACLE_TRACE_FACILITY_PATH
* PARTITION_VIEW_ENABLED (undocumented parameter)
* PLSQL_NATIVE_C_COMPILER
* PLSQL_NATIVE_LINKER
* PLSQL_NATIVE_MAKE_FILE_NAME
* PLSQL_NATIVE_MAKE_UTILITY
* ROW_LOCKING (undocumented parameter)
* SERIALIZABLE (undocumented parameter)
* TRANSACTION_AUDITING (undocumented parameter)
* UNDO_SUPPRESS_ERRORS
6.下面是Oracle 10gR2不建議使用引數
* LOGMNR_MAX_PERSISTENT_SESSIONS (Oracle Streams uses it)
* MAX_COMMIT_PROPAGATION_DELAY
* REMOTE_ARCHIVE_ENABLE
* SERIAL_REUSE
* SQL_TRACE
* BUFFER_POOL_KEEP [replaced by DB_KEEP_CACHE_SIZE]
* BUFFER_POOL_RECYCLE [replaced by DB_RECYCLE_CACHE_SIZE]
* GLOBAL_CONTEXT_POOL_SIZE
* LOCK_NAME_SPACE
* LOG_ARCHIVE_START
* MAX_ENABLED_ROLES
* PARALLEL_AUTOMATIC_TUNING
* PLSQL_COMPILER_FLAGS [replaced by PLSQL_CODE_TYPE and PLSQL_DEBUG]
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/22578826/viewspace-703527/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 錯誤處理
- go的錯誤處理Go
- ORA-32004 錯誤解決
- PHP 錯誤處理PHP
- php錯誤處理PHP
- Go 錯誤處理Go
- Swift錯誤處理Swift
- Zabbix錯誤處理
- mysqldump錯誤處理MySql
- axios 的錯誤處理iOS
- COM的錯誤處理 (轉)
- 錯誤處理:如何通過 error、deferred、panic 等處理錯誤?Error
- PHP錯誤處理和異常處理PHP
- Python錯誤處理Python
- 請教 Element 的錯誤處理
- Restful API 中的錯誤處理RESTAPI
- 【譯】RxJava 中的錯誤處理RxJava
- grpc中的錯誤處理RPC
- JavaScript的錯誤簡易處理JavaScript
- ORA-32004錯誤解決辦法
- 【故障處理】ORA-12162 錯誤的處理
- 前端的水平線,錯誤處理和除錯前端除錯
- 異常錯誤資訊處理
- PHP 核心特性 - 錯誤處理PHP
- 常用模組 PHP 錯誤處理PHP
- laravel9 錯誤處理Laravel
- 淺談前端錯誤處理前端
- Oracle異常錯誤處理Oracle
- ORACLE 異常錯誤處理Oracle
- 15-錯誤處理(Error)Error
- 學習Rust 錯誤處理Rust
- Go語言之錯誤處理Go
- GOLANG錯誤處理最佳方案Golang
- Objective-C:錯誤處理Object
- javascript之處理Ajax錯誤JavaScript
- 搭建dataguard時,錯誤處理
- Oracle錯誤處理思路(一)Oracle
- 使用PHP錯誤處理 (轉)PHP