㈠ oracle資料庫連接不上
sqlplus "/ as sysdba" 連不上，報ora-01031:insufficient privileges解決方法
注意多個資料庫實例時候，setORACLE_SID='',
1、檢查sqlnet.ora（WINDOWS下位於%ORACLE_HOME%NETWORKADMIN目錄）是否包含這句：SQLNET.AUTHENTICATION_SERVICES=(NTS)，沒有的話加上
2、檢查登陸windows的用戶(administrator或安裝oracle時候使用的用戶)是不是在包含在ORA_DBA組中，域用戶沒有連上域伺服器時就可能出現這種現象。
3. 要保證 remote_login_passwordfile 參數 = EXCLUSIVE .
4. 看看是否需要使用orapassw生成口令文件 .
一種解決方法案例：
1、檢查系統參數：SQL> show parameter password
NAME TYPE VALUE------------------------------------ ----------- ------------------------------
remote_login_passwordfile string EXCLUSIVE
2、
select * from v$pwfile_users;
SQL>
為空
3、SQL> grant sysdba to sys;
grant sysdba to sys
*
ERROR at line 1:
ORA-01994: GRANT failed: password file missing or disabled
4、建立password文件
D:/>orapwd file="D:/oracle/proct/10g/db_1/database/PWDoratest.ora" password=gp
oswong entries=10
5、
SQL> select * from v$pwfile_users;
USERNAME SYSDB SYSOP------------------------------ ----- -----
SYS TRUE TRUE
SYS正常顯示出來。
6、重新在遠程以SYSDBA登錄，可正常使用。
如果口令文件創建的有問題，也是會報如下的錯誤：
ora-01031:insufficient privileges
口令文件的命名格式應為orapwsid，並且sid是區分大小寫的。由於Target Database連接Auxiliary Database時需要驗證口令，如果違反了以上規則，將會提示ORA-01031: insufficient privileges。
我在用linux創建plicate資料庫的時候 就是因為口令文件創建的路徑和名稱不對才遇到這個錯誤
-----end-------
㈡ 打不開oracle資料庫了
朋友你好：
---如下是官方對該錯誤的解釋
ORA-01033 ORACLE initialization or shutdown in progress
Cause: An attempt was made to log on while Oracle is being started or shut down.
Action: Wait a few minutes. Then retry the operation.
----------------------------------------------------------
你把資料庫關閉後在啟動試試
看看你BDUMP目錄下的ALERT文件具體報什麼錯誤，貼上來幫你看看。
看看是否有相應的跟蹤文件生成。
祝你成功。
㈢ Oracle資料庫打不開 該怎麼辦我們公司的oracle資料庫壞了 打不開了，該如何處理
如果自己搞不定可以找詩檀軟體專業ORACLE資料庫修復團隊成員幫您恢復!
詩檀軟體專業資料庫修復團隊
Oracle的損壞/壞塊 主要分以下幾種：
ORA-1578
ORA-8103
ORA-1410
ORA-1499
ORA-1578
ORA-81##
ORA-14##
ORA-26040
ORA-600 Errors
Block Corruption
Index Corruption
Row Corruption
UNDO Corruption
Control File
Consistent Read
Dictionary
File/RDBA/BL
Error Description Corruption related to:
ORA-1578 ORA-1578一般為Oracle檢測到存在物理壞塊問題，包括其檢測數據塊中的checksum不正確，或者tail_chk信息不正確等。 ORA-1578 is reported when a block is thought to be corrupt on read.
Block
數據塊
OERR: ORA-1578 「ORACLE data block corrupted (file # %s, block # %s)」 Master Note
OERR: ORA-1578 「ORACLE data block corrupted (file # %s, block # %s)」
Fractured Block explanation
Handling Oracle Block Corruptions in Oracle7/8/8i/9i/10g/11g
Diagnosing and Resolving 1578 reported on a Local Index of a Partitioned table
ORA-1410
ORA-1410錯誤常見於從INDEX或其他途徑獲得的ROWID,到數據表中查詢發現沒有對應的記錄。
該錯誤可能因為數據表與其索引存在不一致，也可能是分區的數據表本身存在問題。
This error is raised when an operation refers to a ROWID in a table for which there is no such row.
The reference to a ROWID may be implicit from a WHERE CURRENT OF clause or directly from a WHERE ROWID=… clause.
ORA 1410 indicates the ROWID is for a BLOCK that is not part of this table.
Row
數據行
Understanding The ORA-1410
Summary Of Bugs Containing ORA 1410
OERR: ORA 1410 「invalid ROWID」
ORA-8103
該ORA-8103可能由多個BUG引起，例如LOB在10.2.0.4之前可能會由於BUG覆蓋了另一張表的segment header，導致出現ORA-8103錯誤。
診斷該問題可以從數據表的segment header和data_object_id入手。
The object has been deleted by another user since the operation began.
If the error is reprocible, following may be the reasons:-
a.) The header block has an invalid block type.
b.) The data_object_id (seg/obj) stored in the block is different than the data_object_id stored in the segment header. See dba_objects.data_object_id and compare it to the decimal value stored in the block (field seg/obj).
Block
數據塊
ORA-8103 Troubleshooting, Diagnostic and Solution
OERR: ORA-8103 「object no longer exists」 / Troubleshooting, Diagnostic and Solution
ORA-8102 ORA-8102常見於索引鍵值與表上存的值不一致。 An ORA-08102 indicates that there is a mismatch between the key(s) stored in the index and the values stored in the table. What typically happens is the index is built and at some future time, some type of corruption occurs, either in the table or index, to cause the mismatch.
Index
索引
OERR ORA-8102 「index key not found, obj# %s, file %s, block %s (%s)
ORA-1499 對表和索引做交叉驗證時發現問題 An error occurred when validating an index or a table using the ANALYZE command.
One or more entries does not point to the appropriate cross-reference.
Index
索引
ORA-1499. Table/Index row count mismatch
OERR: ORA-1499 table/Index Cross Reference Failure – see trace file
ORA-1498 Generally this is a result of an ANALYZE … VALIDATE … command.
This error generally manifests itself when there is inconsistency in the data/Index block. Some of the block check errors that may be found:-
a.) Row locked by a non-existent transaction
b.) The amount of space used is not equal to block size
c.) Transaction header lock count mismatch.
While support are processing the tracefile it may be worth the re-running the ANALYZE after restarting the database to help show if the corruption is consistent or if it 『moves』.
Send the tracefile to support for analysis.
If the ANALYZE was against an index you should check the whole object. Eg: Find the tablename and execute:
ANALYZE TABLE xxx VALIDATE STRUCTURE CASCADE; Block
OERR: ORA 1498 「block check failure – see trace file」
ORA-26040 由於採用過nologging/unrecoverable選項的redo生成機制，且做過對應的recover，導致數據塊中被填滿了0XFF，導致報錯ORA-26040。 Trying to access data in block that was loaded without redo generation using the NOLOGGING/UNRECOVERABLE option.
This Error raises always together with ORA-1578
Block
數據塊
OERR ORA-26040 Data block was loaded using the NOLOGGING option
ORA-1578 / ORA-26040 Corrupt blocks by NOLOGGING – Error explanation and solution
ORA-1578 ORA-26040 in a LOB segment – Script to solve the errors
ORA-1578 ORA-26040 in 11g for DIRECT PATH with NOARCHIVELOG even if LOGGING is enabled
ORA-1578 ORA-26040 On Awr Table
Errors ORA-01578, ORA-26040 On Standby Database
Workflow Tables ORA-01578 ORACLE data block corrupted ORA-26040 Data block was loaded using the NOLOGGING option
ORA-1578, ORA-26040 Data block was loaded using the NOLOGGING option
ORA-600[12700]
從索引獲得的ROWID，對應到數據表時發現不存在數據行錯誤。
一把是一致性度consistent read問題
Oracle is trying to access a row using its ROWID, which has been obtained from an index.
A mismatch was found between the index rowid and the data block it is pointing to. The rowid points to a non-existent row in the data block. The corruption can be in data and/or index blocks.
ORA-600 [12700] can also be reported e to a consistent read (CR) problem.
Consistent Read
一致性讀
Resolving an ORA-600 [12700] error in Oracle 8 and above.
ORA-600 [12700] 「Index entry Points to Missing ROWID」
ORA-600[3020] 主要問題是redo和數據塊中的信息不一致 This is called a 『STUCK RECOVERY』.
There is an inconsistency between the information stored in the redo and the information stored in a database block being recovered. Redo
ORA-600 [3020] 「Stuck Recovery」
Information Required for Root Cause Analysis of ORA-600 [3020] (stuck recovery)
ORA-600[4194] 主要是redo記錄與回滾rollback/undo的記錄不一致 A mismatch has been detected between Redo records and rollback (Undo) records.
We are validating the Undo record number relating to the change being applied against the maximum undo record number recorded in the undo block.
This error is reported when the validation fails. Undo
ORA-600 [4194] 「Undo Record Number Mismatch While Adding Undo Record」
Basic Steps to be Followed While Solving ORA-00600 [4194]/[4193] Errors Without Using Unsupported parameter
ORA-600[4193] 主要是redo記錄與回滾rollback/undo的記錄不一致 A mismatch has been detected between Redo records and Rollback (Undo) records.
We are validating the Undo block sequence number in the undo block against the Redo block sequence number relating to the change being applied.
This error is reported when this validation fails. Undo
ORA-600 [4193] 「seq# mismatch while adding undo record」
Basic Steps to be Followed While Solving ORA-00600 [4194]/[4193] Errors Without Using Unsupported parameter
Ora-600 [4193] When Opening Or Shutting Down A Database
ORA-600 [4193] When Trying To Open The Database
ORA-600[4137] transaction id不匹配，問題可能存在與回滾段中或者對象本身存在訛誤 While backing out an undo record (i.e. at the time of rollback) we found a transaction id mis-match indicating either a corruption in the rollback segment or corruption in an object which the rollback segment is trying to apply undo records on.
This would indicate a corrupted rollback segment. Undo/Redo
ORA-600 [4137] 「XID in Undo and Redo Does Not Match」
ORA-600[6101] Not enough free space was found when inserting a row into an index leaf block ring the application of undo. Index
ORA-600 [6101] 「insert into leaf block (undo)」
ORA-600[2103] Oracle is attempting to read or update a generic entry in the control file.
If the entry number is invalid, ORA-600 [2130] is logged. Control File
ORA-600 [2130] 「Attempt to access non-existant controlfile entry」
ORA-600[4512] Oracle is checking the status of transaction locks within a block.
If the lock number is greater than the number of lock entries, ORA-600 [4512] is reported followed by a stack trace, process state and block mp.
This error possibly indicates a block corruption. Block
ORA-600 [4512] 「Lock count mismatch」
ORA-600[2662] 主要是發現一個數據塊的SCN甚至超過了當前SCN，常規解決途徑有調整SCN等，但11.2以後Oracle公司使較多調整SCN的方法失效了 A data block SCN is ahead of the current SCN.
The ORA-600 [2662] occurs when an SCN is compared to the dependent SCN stored in a UGA variable.
If the SCN is less than the dependent SCN then we signal the ORA-600 [2662] internal error. Block
ORA-600 [2662] 「Block SCN is ahead of Current SCN」
ORA 600 [2662] DURING STARTUP
ORA-600[4097] 訪問一個回滾段頭以便確認事務是否已提交時，發現XID有問題 We are accessing a rollback segment header to see if a transaction has been committed.
However, the xid given is in the future of the transaction table.
This could be e to a rollback segment corruption issue OR you might be hitting the following known problem. Undo
㈣ 急！急！oracle無法打開資料庫
那你看看這樣能否鏈接：
sqlplus /nolog
SQL>connect sys/password as sysdba
如果不能連接，可能你的oracle安裝啟動有問題
㈤ oracle資料庫打不開，怎麼解決
「對於資料庫而言，備份重於一切」是所有DBA心中謹記的格言，但現實環境千差萬別，企業的資料庫環境中數據備份空間不足，采購的存儲設備短期內無法到貨，甚至於雖然進行了備份但是卻在數據恢復過程中發現備份實際不可用等問題均屬常見的場景。
為了應對這些真實世界中常見的數據恢復困局，需要特殊的恢復手段才能恢復其ORACLE DB中的數據。可以應對在完全沒有備份情況下的SYSTEM表空間丟失、誤操作ORACLE數據字典表、由於斷電引起的數據字典不一致等資料庫無法順利打開的場景，也可以挽回誤截斷(Truncate)/刪除(Delete)/業務數據表等人為的誤操作，並從容恢復數據。
甚至於僅僅接觸過ORACLE資料庫幾天的非DBA 人員也可以輕松地使用PRM，這得益於PRM簡單的安裝、和全程圖形化的人機交互界面；實施恢復的人員不需要專業的資料庫知識，不需要學習任何命令，更無需了解資料庫底層的存儲結構。僅僅需要輕輕點擊幾下滑鼠就能從容恢復數據。
對比傳統恢復工具DUL，DUL是ORACLE原廠內部恢復工具，其使用需要通過ORACLE內部流程，一般僅有購買了ORACLE原廠的現場服務的用戶能夠在原廠工程師的協助下使用該工具。PRM打破了只有少數專業人士才能實施資料庫恢復任務的限制，極大地縮短了從資料庫故障到完整恢復數據的失敗時間,降低了企業恢復數據的總成本。
㈥ 為什麼我的電腦啟動不了oracle資料庫
首先打開服務，在控制面板的管理工具中，看看
OracleOraDb10g_home1iSQL*Plus
OracleOraDb10g_home1TNSListener
OracleServiceORACLE（這里要改成：OracleService加上的資料庫名稱
，的資料庫就叫ORACLE，所以是OracleServiceORACLE
）幾個進程是自動還是其他的，自動的就不用管他了，這時候如果啟動計算機的時候資料庫啟動不了就有可能是的系統問題或者oracle沒有裝好，如果是手動的，解決方法如下：
net
start
OracleOraDb10g_home1iSQL*Plus
net
start
OracleOraDb10g_home1TNSListener
net
start
OracleServiceORACLE（這里要改成：OracleService加上的資料庫名稱
，的資料庫就叫ORACLE，所以是OracleServiceORACLE
）
給這段腳本，把它放在、bat文件中，再把這個bat文件放在「開始菜單--所有程序--啟動
」中這樣開機的時候就會啟動了。
㈦ 求救！oracle資料庫打不開了！
給你介紹一個用JAVA編寫有圖形界面的JDUL:
你可以試試ORACLE PRM-DUL ,Oracle PRM-DUL即 ParnassusData Recovery Manager是企業級別的Oracle資料庫災難恢復工具。PRM-DUL可以再無備份的情況下恢復被truncated掉的表，也可以恢復無法打開的Oracle資料庫(Alter database open失敗)中的數據。 PRM-DUL是圖形化增強版的Oracle DUL工具，同時具備很多Oracle DUL不具備的特性。而且Oracle PRM-DUL無需學任何新命令。
㈧ oracle 服務啟動資料庫失敗怎麼辦
開始 -> 運行, 輸入services.msc, 進入service
查看TNSListener服務(譬如: OracleOraDb10g_home1TNSListener)有沒有啟動, 如果沒有啟動, 啟動該服務.
如果該服務已經啟動, 開始->所有程序->Oracle->配置和移植工具->Net Configuration Assistant, 在該工具中一步步重新配置一下, 之後應該就能正常了.