ORA-04031：unable to allocate … byters of shared memory("shared pool","unknown object","sga heap","db_block_buffers")
問(wèn)題：
DELL服務(wù)器裝不上ORACLE8.1.5的問(wèn)題，出現(xiàn)下面的錯(cuò)誤提示是在建立數(shù)據(jù)庫(kù)之前，系統(tǒng)先要檢查內(nèi)存時(shí)出現(xiàn)的，
ORA-04031:unable to allocate 85141440 byters of shared memory("shared pool","unknown object","sga heap","db_block_buffers")，是不是內(nèi)存不夠？但實(shí)際物理內(nèi)存是2G?什么原因呢？
解答：
在安裝時(shí)，把SGA區(qū)、JAVA池等東西的內(nèi)存配小一些
ORA-01092 : Oracle instance terminated disconnection forced錯(cuò)誤
Problem:
Your Oracle Server database on OpenVMS crashes. The following errors are reported: Background process DBWR unexpectedly terminated with error 1092
ORA-1092 Oracle instance terminated
ORA-313 open failed for members of log group 'n' of thread 'n'
ORA-600 [3228] reported from a PL/SQL script.
Explanation:
The most significant error reported here is the ORA-313 error. This error indicates a failure to open a file which indicates a problem with OpenVMS resources. When either CHANNELCNT and/or FILLM are too small, these errors can result.
Solution:
Increase the SYSGEN parameter CHANNELCNT. This should be done by an OpenVMS system manager and requires a reboot of your OpenVMS node. For more information on SYSGEN, please review the OpenVMS documentation.
If the CHANNELCNT parameter is already large enough to allow the expected number of files to be opened, check the FILLM quota. Review two areas when you check FILLM:
1) The Oracle background processes (PMON, DBWR, LGWR etc.)
2) The SERVER side (or SHADOW) process created when you use SVRMGRL to start the database. To get an idea of the quota available, use the command: $ SHOW PROCESS /QUOTA /ID=<pid> Where <pid> is the OpenVMS pid of the process to be reviewed. This command displays the remaining 'Open file quota' (FILLM) for the process, as well as other available quotas.
Example:
You have 226 data files, eight REDO log files and three control files for a total of 237 files. The SYSGEN setting for CHANNELCNT is at the default of 256. During normal operation, Oracle periodically needs to open additional files. These include the INIT parameter files, the ALERT log, various DCL scripts, trace files, etc. Under these conditions, a CHANNELCNT value of 256 is too small to accommodate the number of files that Oracle/OpenVMS needs open at the same time.
For most systems the default quotas should be adequate.
If not, please describe the infor u've encountered
ORA-00059錯(cuò)誤及字符集修改
問(wèn)題：在DBA studio中下的例程‘?dāng)?shù)據(jù)庫(kù)'自動(dòng)變?yōu)橐褑?dòng)，無(wú)法裝載也無(wú)法打開(kāi)，提示‘ORA-00059？？LOG--FILES？？？？'在這種情況下如果不卸載重裝解決，能有其它的辦法嗎？
一般來(lái)說(shuō)ORA-00059多出現(xiàn)maximum number of DB_FILES exceeded的錯(cuò)誤,由于你機(jī)器上的字符集設(shè)置有些問(wèn)題,所以 錯(cuò)誤提示 變成了??,(字符集設(shè)置不對(duì)照成的) 雖然看的出于問(wèn)題可能和Log file有關(guān),但不確定.請(qǐng)修改Oracle的字符集
[字符集修改方法]
SQL> desc props$
列名 可空值否 類(lèi)型
------------------------------- -------- ----
NAME NOT NULL VARCHAR2(30)
VALUE$ VARCHAR2(2000)
COMMENT$ VARCHAR2(2000)
SQL> col value$ format a40
SQL> select name,value$ from props$;
NAME VALUE$
------------------------------ -------------------------
DICT.BASE 2
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CURRENCY$
NLS_ISO_CURRENCY AMERICA
NLS_NUMERIC_CHARACTERS.,
NLS_DATE_FORMAT DD-MON-YY
NLS_DATE_LANGUAGE AMERICAN
NLS_CHARACTERSET ZHS16GBK
NLS_SORT BINARY
NLS_CALENDAR GREGORIAN
NLS_RDBMS_VERSION 7.3.4.0.0
GLOBAL_DB_NAME ORACLE.WORLD
EXPORT_VIEWS_VERSION 3
查詢到14記錄.
NLS_CHARACTERSET這個(gè)參數(shù)應(yīng)該是ZHS16GBK，如不是，改為它。
ORA-12203:TNS:unable to connect destination錯(cuò)誤
問(wèn)題：
在Windows2000下安裝8.0.5，選擇none，沒(méi)有建立實(shí)例，為什么在執(zhí)行svrmgr30 時(shí)報(bào)告Ora-12203:tns:unable to connect destination!
解答：
因?yàn)闆](méi)有創(chuàng)建實(shí)例，也就沒(méi)有環(huán)境變量。可參考“手工創(chuàng)建數(shù)據(jù)庫(kù)的全部腳本和說(shuō)明”。
注意其中：
set ORACLE_SID=test
D:\Oracle\Ora81\bin\oradim -new -sid test -startmode manual -pfile "D:\Oracle\admin\test\pfile\inittest.ora"
Ora-12571：TNS：包寫(xiě)入程序失敗

把虛擬內(nèi)存設(shè)的大一些
Ora-12705錯(cuò)誤
Cause: There are two possible causes: Either an attempt was made to issue an ALTER SESSION statement with an invalid NLS parameter or value; or the NLS_LANG environment variable contains an invalid language, territory, or character set.
Action: Check the syntax of the ALTER SESSION command and the NLS parameter, correct the syntax and retry the statement, or specify correct values in the NLS_LANG environment variable. For more information about the syntax of the ALTER SESSION command, see Oracle8i SQL Reference.
ORA-03113：通信通道的文件結(jié)束
Cause:
An unexpected end-of-file was processed on the communication channel. The problem could not be handled by the SQL*Net, two task, software. This message could occur if the shadow two-task process associated with a SQL*Net connect has terminated abnormally, or if there is a physical failure of the interprocess communication vehicle, that is, the network or server machine went down.
Action:
If this message occurs during a connection attempt, check the setup files for the appropriate SQL*net driver and confirm SQL*Net software is correctly installed on the server. If the message occurs after a connection is well established, and the error is not due to a physical failure, check if a trace file was generated on the server at failure time. Existence of a trace file may suggest an Oracle internal error that requires the assistance of customer support.
Explanation:
There are numerous causes of this error. It is a 'catch all' type error which means 'I cannot communicate with the Oracle shadow process'. This usually occurs when the Oracle server process has died for some reason.
ORA-12515：TNS：監(jiān)聽(tīng)進(jìn)程無(wú)法找到該演示文稿的句柄
解決方案是檢查目標(biāo)服務(wù)器網(wǎng)絡(luò)配置，并使其接受HTTP的協(xié)議。如果你是使用一般數(shù)據(jù)使用，建議使用新的數(shù)據(jù)庫(kù)實(shí)例。
ORA-01031：insufficient privileges
Cause: An attempt was made to change the current username or password without the appropriate privilege. This error also occurs if attempting to install a database without the necessary operating system privileges. When Trusted Oracle is configure in DBMS MAC, this error may occur if the user was granted the necessary privilege at a higher label than the current login.
Action: Ask the database administrator to perform the operation or grant the required privileges. For Trusted Oracle users getting this error although granted the appropriate privilege at a higher label, ask the database administrator to regrant the privilege at the appropriate label.
ORA-01017：invalid username/password; logon denied
Cause: An invalid username or password was entered in an attempt to log on to Oracle. The username and password must be the same as was specified in a GRANT CONNECT statement. If the username and password are entered together, the format is: username/password.
Action: Enter a valid username and password combination in the correct format.
問(wèn)題：ORACLE8.1.7.0.0版本，，不知是哪里的問(wèn)題，用internal 和 system 都無(wú)法登陸，錯(cuò)誤提示：ORA1031 、ORA1017
解答：還有沒(méi)有其他DBA身份的用戶，如果有，最好登陸進(jìn)去，然后alter user system identified by YOURPASSWORD; 你的系統(tǒng)密碼被人修改了
ORA-03121：沒(méi)連接接口驅(qū)動(dòng)程序
Cause: This message occurs usually because the Net8 driver is not loaded into memory or there is a mismatch of the version of the driver. A user program linked with an obsolete library may also cause this message. Only programs provided by Oracle Corporation should use this interface.
Action: If the message occurred during use of a program provided by Oracle Corporation, contact Oracle Support Services. If a user program caused the message, relink the program with current versions of the Oracle libraries.
ORA-12638：憑證檢索失敗
問(wèn)題：
2000ad server SP2 具域網(wǎng)，在網(wǎng)絡(luò)連接的情況下按裝ORACLE8I，到創(chuàng)建數(shù)據(jù)庫(kù)，初始化數(shù)據(jù)庫(kù)時(shí)，提示“ORA-12638 憑證檢索失敗”，裝了幾次都是這樣
解答：
憑證檢索失敗的錯(cuò)誤一般都與網(wǎng)絡(luò)用戶集成有關(guān)，ORACLE中對(duì)于這個(gè)問(wèn)題的管理是在SQLNET.ORA文件的SQLNET.AUTHENTICATION_SERVICES進(jìn)行控制的，默認(rèn)安裝都是SQLNET.AUTHENTICATION_SERVICES= (NTS)表示安裝ORACLE的用戶是通過(guò)操作系統(tǒng)的集成認(rèn)證控制的，所以，我們只要把這個(gè)參數(shù)值屏蔽掉就行了。
修改\Oracle\Ora81\network\ADMIN目錄下SQLNET.ORA文件的SQLNET.AUTHENTICATION_SERVICES= (NTS)為# SQLNET.AUTHENTICATION_SERVICES= (NTS)
ORA-00604: error occurred at recursive SQL level 2
Cause: An error occurred while processing a recursive SQL statement (a statement applyingto internal dictionary tables).
Action: If the situation described in the next error on the stack can be corrected, do
so; otherwise contact Oracle Customer Support.
ORA-04030 out of process memory when trying to allocate string bytes (string,string)
Cause: Operating system process private memory has been exhausted.
Action: See the database administrator or operating system administrator to increase process memory quota. There may be a bug in the application that causes excessive allocations of process memory space.
ORA-04031：unable to allocate string bytes of shared memory("string","string","string","string")
Cause: More shared memory is needed than was allocated in the shared pool.
Action: If the shared pool is out of memory, either use the DBMS_SHARED_POOL package topin large packages, reduce your use of shared memory, or increase the amount ofavailable shared memory by increasing the value of the initialization parametersSHARED_POOL_RESERVED_SIZE and SHARED_POOL_SIZE. If the large pool is out of memory,increase the initialization parameter LARGE_POOL_SIZE.
ORA-01555：snapshot too old: rollback segment number 9 with name "USER_RS5" too small
問(wèn)題：一個(gè)存儲(chǔ)過(guò)程執(zhí)行的數(shù)據(jù)大概有100萬(wàn)條，在執(zhí)行到幾十萬(wàn)條的時(shí)候，遇到了如上異常。
解答：原因有兩個(gè)方面：
1、由于你的這個(gè)操作執(zhí)行的時(shí)間太長(zhǎng)，導(dǎo)致SNAP SHOT失效（太老了），導(dǎo)致你的操作失??；
2、你的RBS太小，無(wú)法容納那么多的操作。
處理方法：
1、加大回滾段的大小（增加RBS表空間，修改回滾段的參數(shù)等）
2、你這種編程方法有問(wèn)題，如果第一個(gè)方法不能解決問(wèn)題，說(shuō)明是因?yàn)閳?zhí)行時(shí)間過(guò)長(zhǎng)，SNAPSHOT失效，需要你調(diào)整一下程序。是不是先把100萬(wàn)記錄讀到內(nèi)存里（內(nèi)存不夠，可以采用文件作為緩沖），然后再做處理。也可以采用分段處理的方法，一次處理10萬(wàn)條。
ORA-01589：must use RESETLOGS or NORESETLOGS option for database open
問(wèn)題：在startup 之后出現(xiàn)錯(cuò)誤提示
解答：
Cause: Either incomplete or backup control file recovery has been performed. After these types of recovery you must specify either the RESETLOGS option or the NORESETLOGS option to open your database.
Action: Specify the appropriate option.
你的數(shù)據(jù)庫(kù)以前做過(guò)Media Recovery，用OPEN DATABASE RESETLOGS或OPEN DATABASE NORESETLOGS打開(kāi)數(shù)據(jù)庫(kù)就可以了。
ORA-01017：invalid username/password; logon denied
Cause: An invalid username or password was entered in an attempt to log on to Oracle. The username and password must be the same as was specified in a GRANT CONNECT statement. If the username and password are entered together, the format is: username/password.
Action: Enter a valid username and password combination in the correct format.
缺省密碼
8i：
scott/tiger
internal/change_on_install
system/manager
sys/oralce(密碼也可能是manager或change_on_install)
9i：
scott/tiger
sys/change_on_install
OEM的用戶名/密碼：sysman/oem_temp
重設(shè)system用戶的密碼
可以通過(guò)以下方法登陸
sqlplus /nolog
conn / as sysdba
alter user system identifed by '123'
Oracle的密碼文件
8i一般位于$ORACLE_HOME/PRODUCT/8.1.6/DBS/ORAPWD_[SID].ORA
如何激活用戶
8i：在DBA Studio里面，有“用戶”--然后找到用戶名--->然后選中“未鎖定”就可以了
Oracle的初始化文件
8i：安裝時(shí)設(shè)定的ORACLEHOME的目錄下會(huì)有：admin、oradata和ora81三個(gè)目錄，其中在admin目錄下的你安裝的數(shù)據(jù)庫(kù)目錄下的Prfile下的init.ora就是。
9i：在原來(lái)的目錄下看不到init文件了。不過(guò)你可以這樣：
create pfile from spfile;
這樣就可以看到init的文件了，因?yàn)?i里面的初始化文件有點(diǎn)變化。
Oracle 數(shù)據(jù)庫(kù)自帶數(shù)據(jù)的生成腳本
\ORACLE_HOME\rdbms\admin\SCOTT.SQL