【文章內(nèi)容簡(jiǎn)介】 e cascade。alter table table_name move disable row movement。清除監(jiān)聽(tīng)日志lsnrctlsetlog_statusofflsnrctlsetlog_statuson重建oraInventory$ cat /etc/inventory_loc=/oracle/oraInventoryinst_group=oinstall$ cd $ORACLE_HOME/oui/bin$ ./runInstaller silent attachHome ORACLE_HOME=$ORACLE_HOME ORACLE_HOME_NAME=OraDb11g_home1或者（/oracle/oraInventory目錄可以mv掉，新建個(gè)目錄）export ORACLE_HOME=/oracle/product/crs/cd $ORACLE_HOME/oui/bin./物化視圖刪除基于DBLINK的物化視圖的時(shí)候要確認(rèn)DBLINK的存在，否則會(huì)造成物化視圖注冊(cè)信息無(wú)法清除。刪除物化視圖并不意味著要?jiǎng)h除物化視圖日志。因?yàn)槲锘晥D日志可以同時(shí)支持多個(gè)物化視圖的刷新，如果物化視圖日志被刪除，那么所有基于這個(gè)物化視圖日志的物化視圖無(wú)法再進(jìn)行快速刷新。在ON COMMIT刷新模式下, 如果基表的DML很頻繁, 會(huì)造成刷新很頻繁, 這可能會(huì)造成DROP物化視圖的語(yǔ)句一直掛起。 遷移數(shù)據(jù)文件alter database datafile 39。old_path39。 offlineRMAN copy datafile 39。old_path39。 to 39。new_path39。3 重命名數(shù)據(jù)文件SQLalter tablespace tbs_name rename datafile 39。 old_path 39。 to 39。new_path39。4 恢復(fù)數(shù)據(jù)文件RMAN recover datafile 39。new_path39。5 使數(shù)據(jù)文件在線alter database datafile 39。new_path39。 online。SQLNETIP訪問(wèn)限制修改（需重啟監(jiān)聽(tīng)）$ORACLE_HOME/network/admin/ :=yes=(localhost, 本機(jī)ip, 應(yīng)用服務(wù)器ip，管理機(jī)ip等)重啟監(jiān)聽(tīng)：lsnrctl stop；lsnrctl start。參考文章When do changes take effect ? (Doc ID )How to Centralize , And files (Doc ID )Configure Multiple DB Instances To Share Without Giving WALLET_LOCATION For EUS (Doc ID )Parameter OUTBOUND_CONNECT_TIMEOUT in (Doc ID )增加Current SCN主要針對(duì)ORA00600 2662通過(guò)adjust_s event來(lái)調(diào)整MOS Doc ID: Note: Subject: EVENT: ADJUST_SCN Quick Reference Type: REFERENCE Status: PUBLISHED Content Type: TEXT/PLAIN Creation Date: 20OCT1997 Last Revision Date: 04AUG2000 Language: USAENG ADJUST_SCN Event~~~~~~~~~~~~~~~~*** WARNING *** This event should only ever be used under the guidance of an experienced Oracle analyst. If an SCN is ahead of the current database SCN, this indicates some form of database corruption. The database should be rebuilt after bumping the SCN. **************** The ADJUST_SCN event is useful in some recovery situations where the current SCN needs to be incremented by a large value to ensure it is ahead of the highest SCN in the database. This is typically required if either: a. An ORA600 [2662] error is signalled against database blocks or b. ORA1555 errors keep occuring after forcing the database open or ORA604 / ORA1555 errors occur during database open. (Note: If startup reports ORA704 amp。 ORA1555 errors together then the ADJUST_SCN event cannot be used to bump the SCN as the error is occuring during bootstrap. Repeated startup/shutdown attempts may help if the SCN mismatch is small) or c. If a database has been forced open used _ALLOW_RESETLOGS_CORRUPTION (See Parameter:Allow_Resetlogs_Corruption ) The ADJUST_SCN event acts as described below. **NOTE: You can check that the ADJUST_SCN event has fired as it should write a message to the alert log in the form Debugging event used to advance s to %s. If this message is NOT present in the alert log the event has probably not fired. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ If the database will NOT open: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Take a backup. You can use event 10015 to trigger an ADJUST_SCN on database open: startup mount。 alter session set events 39。10015 trace name adjust_s level 139。 (NB: You can only use IMMEDIATE here on an OPEN database. If the database is only mounted use the 10015 trigger to adjust SCN, otherwise you get ORA 600 [2251], [65535], [4294967295] ) alter database open。 If you get an ORA 600:2256 shutdown, use a higher level and reopen. Do *NOT* set this event in or the instance will crash as soon as SMON or PMON try to do any clean up. Always use it with the alter session mand. ~~~~~~~~~~~~~~~~~~~~~~~~~~ If the database *IS* OPEN: ~~~~~~~~~~~~~~~~~~~~~~~~~~ You can increase the SCN thus: alter session set events 39。IMMEDIATE trace name ADJUST_SCN level 139。 LEVEL: Level 1 is usually sufficient it raises the SCN to 1 billion (1024*1024*1024) Level 2 raises it to 2 billion etc... If you try to raise the SCN to a level LESS THAN or EQUAL to its current setting you will get OERI:2256 See below. Ie: The event steps the SCN to known levels. You cannot use the same level twice. Calculating a Level from 600 errors: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To get a LEVEL for ADJUST_SCN: a) Determine the TARGET s: ora600 [2662] See OERI:2662 Use TARGET = blocks SCN ora600 [2256] See OERI:2256 Use TARGET = Current SCN b) Multiply the TARGET wrap number by 4. This will give you the level to use in the adjust_s to get the correct wrap number. c) Next, add the following value to the level to get the desired base value as well : Add to Level Base ~~~~~~~~~~~~ ~~~~~~~~~~~~ 0 0 1 1073741824 2 2147483648 3 3221225472在Oracle 10g之前,一般采用使用這個(gè)event的方式來(lái)增大SCN.ORA00600: internal error code, arguments: [2662], [0], [547743994], [0], [898092653], [8388617], [], []這個(gè)報(bào)錯(cuò)參數(shù)的含義在metalink中如此描述的：Arg [a] Current SCN WRAPArg [b] Current SCN BASEArg [c] dependent SCN WRAP為了存儲(chǔ)更大的SCN值，當(dāng)SCN BASE到足夠大并開(kāi)始重置的時(shí)候，SCN WRAP將加1。Arg [d] dependent SCN BASEArg [e] Where present this is the DBA where the dependent SCN came from.也就是Arg [d] 的值是從哪個(gè)block中找到的，通常是一個(gè)data block address。通過(guò)這幾個(gè)參數(shù)根據(jù)一定的規(guī)則可以計(jì)算出我們需要的level。計(jì)算規(guī)則如下：1. Arg [c] *4得出一個(gè)數(shù)值，假設(shè)為V_Wrap2. 如果Arg [d]=0，則V_Wrap值為需要的levelArg [d] 1073741824，V_Wrap+1為需要的levelArg [d] 2147483648，V_Wrap+2為需要的levelArg [d] 3221225472，V_Wrap+3為需要的level計(jì)算方法的例子ORA00600: internal error code, arguments: [2662], [0], [2179133], [8656], [70114056], [33855201], [], []Arg [C] *4 = 8656 * 4 = 34624Arg [d] = 70114056 1073741824所以level = 34624 + 1 = 34625因此在這個(gè)例子中我們應(yīng)該執(zhí)行alter session set events 39。IMMEDIATE trace name ADJUST_SCN level 3462539。但是隨著