Shulou(Shulou.com)05/31 Report--

This article mainly introduces "how to repair Oracle 11.2.0.1 dblink access ORA-600". In daily operation, I believe many people have doubts about how to repair Oracle 11.2.0.1 dblink access ORA-600. Xiaobian consulted all kinds of materials and sorted out simple and easy-to-use operation methods. I hope it will be helpful to answer the doubts of "how to repair Oracle 11.2.0.1 dblink access ORA-600". Next, please follow the editor to study!

Db alert log

2019-08-12 15 15 incident=320040 46 incident=320040 + 08:00Errors in file / incident=320040: ORA-00600: internal error code, arguments: [2252], [5579], [3110485746], [] [] Incident details in: / oracle/app/oracle/diag/rdbms/anbob/anbob/incident/incdir_320040/anbob_ora_14800_i320040.trc2019-08-1215: 46 08:00Trace dumping is performing id= 17.000000 + 08:00Trace dumping is performing id= [CDMP _ 20190812154617] Sweep [inc] [320040]: completedSweep [inc2] [320040]: completed

Trace file

Adrci > show incident-allADR Home = / oracle/app/oracle/diag/rdbms/anbob/anbob:****INCIDENT_ID PROBLEM_KEY CREATE_TIME -320037 ORA 600 [2252] 2019-08-08 09 35 purl 59.628000 + 08:00 304310 ORA 600 [2252] 2019-08-08 09 ORA 39 ORA 21.668000 + 08:00 304295 ORA 600 [2252] 2019-08-08 09 59 ORA 10.141000 + 08:00 2019-08-08 14:38:15 . 196000 + 08:00 304253 ORA 600 [2252] 2019-08-09 11 34.003000 + 08:00 320038 ORA 600 [2252] 2019-08-09 11 11 40 ORA 43.692000 + 08:00 304289 ORA 600 [2252] 2019-08-09 15 ORA 21.345000 + 08:00 320039 ORA 600 [2252] 2019-08-12 10 ORA 05ORA 07.925000 + 08:00 304303 ORA [2252] 2019-08-12 11 show trace file 21 show trace file 54.489000 + 08:00 320040 ORA 600 [2252] 2019-08-12 15 purl 46vis 15.334000 + 08:00 50 rows fetchedadrci > show trace file / oracle/app/oracle/diag/rdbms/anbob/anbob/trace/anbob_ora_14800 .trcDump continued from file: / oracle/app/oracle/diag/rdbms/anbob/anbob/trace/anbob_ora_14800.trc1 > * Error Stack * ORA-00600: internal error code Arguments: [2252], [5579], [3110485746], [] 1

* Dump for incident 320040 (ORA 2252) * 2019-08-12 15:46:15.336dbkedDefDump (): Starting incident default dumps (flags=0x2, level=3, mask=0x0) 2 > * SQL Statement (None) * Current SQL information unavailable-no cursor. * Call Stack Trace * calling call entry location type point-skdstdst () + 36 Call kgdsdst () ksedst1 () + 98 call skdstdst () ksedst () + 34 call ksedst1 () dbkedDefDump () + 2736 call ksedst () ksedmp () + 36 call dbkedDefDump () ksfdmp () + 64 call ksedmp ( DbgexPhaseII () + 1764 call ksfdmp () dbgexProcessError () call dbgexPhaseII () + 2279 dbgeExecuteForError call dbgexProcessError () () + 83 dbgePostErrorKGE () + Call dbgeExecuteForError 1615 () dbkePostKGE_kgsf () + call dbgePostErrorKGE () 63 kgeade () + 350 call dbkePostKGE_kgsf () kgeriv_int () + 98 call kgeade () Kgeriv () + 12 call kgeriv_int () kgesiv () + 110 call kgeriv () ksesic2 () + 194 call kgesiv () kcmchk () + 113 call ksesic2 () kcsadjn () + 315 call kcmchk () K2serv () + 390 call kcsadjn () opiodr () + 1149 call k2serv () ttcpip () + 1251 call opiodr () opitsk () + 1628 call ttcpip ()

After temporarily disconnecting the dblink

SQL > select version, to_char (SYSDATE, 'YYYY/MM/DD HH24:MI:SS') DATE_TIME, (to_number (to_char (sysdate,' YYYY'))-1988) * 12 * 31 * 24 * 60 * 60) + ((to_number (to_char (sysdate, 'MM'))-1) * 31 * 24 * 60 * 60) + ((to_number (to_char (sysdate)) 'DD'))-1) * 24 * 60 * 60) + (to_number (to_char (sysdate,' HH24')) * 60 * 60) + (to_number (to_char (sysdate, 'MI')) * 60) + (to_number (to_char (sysdate)) 'SS') * (16 * 1024))-dbms_flashback.get_system_change_number) / (16 * 1024 * 60 * 60 * 24)) indicator from v$instance VERSION DATE_TIME INDICATOR--11.2.0.1.0 2019-08-12 17:31:20 13.1391809

Download the patch

[oracle@localhost ~] $ls

P12419378_112010_Linux-x86-64.zip

P6880880_112000_Linux-x86-64.zip

P14121009_112016_Linux-x86-64.zip

Install 11.2.0.1 PSU

$export PATH=$PATH:$ORACLE_HOME/OPatch$ opatch prereq CheckConflictAgainstOHWithDetail-phBaseDir. / 12419378$ opatch applySQL > @? / rdbms/admin/catbundle psu apply

Note:

Opatch warning: overriding... .This is a warning only which opatch is reporting. The Patch has applied successfully and the warning output can be safely ignored.

Install one-off patch

[oracle@localhost 14121009] $opatch prereq CheckConflictAgainstOHWithDetail-ph. / [oracle@localhost 14121009] $opatch applySQL > @? / sqlpatch/14121009/postinstall.sql

Check

SQL > select * from registry$history;SQL > @ scn_compat_check.sqlCurrent datatime:20190814 10:38:33Oracle Version:Oracle Database 11g Enterprise Edition Release 11.2.0.1.0-64bit ProductionDatabase role:PRIMARYInstance starttime: 20190814 10:34:43RSL=35937836695552headroom_in_scn=19308210069494headroom_in_sec=196413269CUR_SCN_COMPAT=3MAX_SCN_COMPAT=3auto_rollover_ts=2019-06-23target_compat=3Auto_rollover is enabling SCN compat had Auto rollover! PL/SQL procedure successfully completed. At this point, the study on "how to repair Oracle 11.2.0.1 dblink access ORA-600" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.