ORA-16179: incremental changes to "log_archive_dest_1" not allowed with SPFILE
記錄遇到一個錯誤,環境:11g
SQL> alter system set log_archive_dest_1='/arch' scope=spfile;
alter system set log_archive_dest_1='/arch' scope=spfile
*
ERROR at line 1:
ORA-32017: failure in updating SPFILE
ORA-16179: incremental changes to "log_archive_dest_1" not allowed with SPFILE
Oracle 官網查錯:
ORA-16179: incremental changes to "string" not allowed with SPFILE
Cause: Incremental changes to a log_archive_dest_n parameter cannot be made when using an SPFILE.
Action: Specify either LOCATION or SERVICE plus all other attributes to be set in one ALTER SYSTEM/SESSION SET command.
SQL> alter system set log_archive_dest_1='location=/arch' scope=spfile;
System altered.
看官網上說log_archive_dest 和log_archive_dest_1不能同時設定,做個測試
SQL> alter system set log_archive_dest='/arch' scope=spfile;
SQL> startup mount
ORA-16019: cannot use LOG_ARCHIVE_DEST_1 with LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST
報錯,使用備用pfile檔案,重新啟動資料庫;
官網內容如下:
LOG_ARCHIVE_DEST is applicable only if you are running the database in ARCHIVELOG mode or are recovering a database from archived redo logs. LOG_ARCHIVE_DEST is incompatible with the LOG_ARCHIVE_DEST_n parameters, and must be defined as the null string ("") or (' ') when any LOG_ARCHIVE_DEST_n parameter has a value other than a null string. Use a text string to
specify the default location and root of the disk file or tape device
when archiving redo log files. (Archiving to tape is not supported on
all operating systems.) The value cannot be a raw partition.
If LOG_ARCHIVE_DEST is not explicitly defined and all the LOG_ARCHIVE_DEST_n parameters have null string values, LOG_ARCHIVE_DEST is set to an operating system-specific default value on instance startup.
To override the destination that this parameter specifies, either specify a different destination for manual archiving or use the SQL*Plus statement ARCHIVE LOG START filespec for automatic archiving, where filespec is the new archive destination. To permanently change the destination, use the statement ALTER SYSTEM SET LOG_ARCHIVE_DEST = filespec, where filespec is the new archive destination.
Neither LOG_ARCHIVE_DEST nor LOG_ARCHIVE_FORMAT have to be complete file or directory specifiers themselves; they only need to form a valid file path after the variables are substituted into LOG_ARCHIVE_FORMAT and the two parameters are concatenated together.
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/29519108/viewspace-1336467/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- ASM下遷移spfileASM
- 2.4.8 Step 7: 建立spfile
- [Reactive] Run functions when data changesReactFunction
- Serialization of 'Closure' is not allowed
- PostgreSQL 13支援增量排序(Incremental Sorting)SQL排序REM
- [20200114]關於log_archive_dest_1設定.txtHive
- [20200219]log_archive_dest_1定義問題.txtHive
- ORA-16024: parameter LOG_ARCHIVE_DEST_1 cannot be parsedHive
- 2.7.5 SPFILE初始化引數
- RAC環境修改spfile的位置
- [20201221]spfile設定問題.txt
- 2.7.4 建立伺服器引數(SPFILE)伺服器
- 讀書筆記-增量學習-Large Scale Incremental Learning筆記REM
- "Visual Studio Code is unable to watch for file changes in this large workspace"
- 2.7 使用spfile管理伺服器引數伺服器
- 一次Oracle診斷案例-Spfile案例Oracle
- Host 'localhost' is not allowed to connect to this MySQL serverlocalhostMySqlServer
- “Host ‘xxxx‘ is not allowed to connect to this MySQL server“MySqlServer
- flask資料庫遷移 No changes in schema detected.Flask資料庫
- [LeetCode] 3226. Number of Bit Changes to Make Two Integers EqualLeetCode
- kafka rebalance解決方案 -incremental cooperative協議和static membership功能KafkaREMOOP協議
- 2.7.3 spfile的預設名稱和路徑
- Error: User gpmon is not allowed to login Command CenterError
- Allowed memory size 記憶體不足記憶體
- Host 'xxx' is not allowed to connect to this MySQL server.MySqlServer
- Oracle 19c Concepts(00):Changes in This Release for Oracle Database ConceptsOracleDatabase
- 將spfile從ASM裡遷移到檔案系統ASM
- 2.7.2 遷移到伺服器引數檔案(spfile)伺服器
- 2.7.9 備份伺服器引數檔案(SPFILE)伺服器
- 2.7.8 匯出伺服器引數檔案(SPFILE)伺服器
- 【ASM】ASM啟動無法找到spfile問題原因ASM
- Error: User gpmon is not allowed to login Command Center.Error
- ERROR 1410 (42000): You are not allowed to create a user with GRANTError
- MySQL-1130-host ... is not allowed to connect to this MySql serverMySqlServer
- PHP Fatal error: Allowed memory size of 1610612736 bytesPHPError
- CRM中介軟體裡CRM local changes的註冊管理
- Host 'xxx' is not allowed to connect to this MySQL server 解決方法MySqlServer
- zblog顯示Allowed memory size of 6553652 bytes exhauste
- 修改程式碼後提交出現“No changes detected”的問題