{"id":2049,"date":"2018-04-18T11:17:58","date_gmt":"2018-04-18T14:17:58","guid":{"rendered":"https:\/\/zmsolution.laraclaud.com.br\/?p=2049"},"modified":"2018-04-18T11:17:58","modified_gmt":"2018-04-18T14:17:58","slug":"ora-00600-internal-error-code-arguments-kcratr_nab_less_than_odr","status":"publish","type":"post","link":"http:\/\/zmsolution.com\/ora-00600-internal-error-code-arguments-kcratr_nab_less_than_odr\/","title":{"rendered":"ORA-00600: internal error code, arguments: [kcratr_nab_less_than_odr]"},"content":{"rendered":"<p>Em bases que o archivelog n\u00e3o esta ativado corremos muitos riscos, entre ele o risco de termos o erro:\u00a0<em><strong>ORA-00600: internal error code, arguments: [kcratr_nab_less_than_odr]<\/strong> , esse erro podo ocorrer de muitas formas :<\/em><\/p>\n<p>This Problem is caused by Storage Problem of the Database Files.<br \/>\nThe Subsystem (eg. SAN) crashed while the Database was open.<br \/>\nThe Database then crashed because the Database Files were not accessible anymore.<br \/>\nThis caused a lost Write into the Online RedoLogs and\/or causing logical corruption in controlfile so Instance Recovery is not possible and raising the ORA-600.<\/p>\n<p>A forma de resolu\u00e7\u00e3o mais f\u00e1cil que encontrei foi com o\u00a0<strong>recover database using backup controlfile until cancel ;<\/strong><\/p>\n<p>segue os passos abaixo:<\/p>\n<pre class=\"lang:default decode:true \">SQL&gt; startup\r\nORACLE instance started.\r\n\r\nTotal System Global Area 5027385344 bytes\r\nFixed Size 2261888 bytes\r\nVariable Size 1644170368 bytes\r\nDatabase Buffers 3372220416 bytes\r\nRedo Buffers 8732672 bytes\r\nDatabase mounted.\r\nORA-00600: codigo de erro interno, argumentos: [kcratr_nab_less_than_odr], [1],\r\n[6889], [30061], [30062], [], [], [], [], [], [], []\r\n\r\nSQL&gt; recover database using backup controlfile until cancel ;\r\nORA-00279: alterar 200548268 gerado em 04\/15\/2018 16:35:10 necessario para o\r\nthread 1\r\nORA-00289: sugest?o : \/u01\/app\/oracle\/11.2.0\/db_1\/dbs\/arch1_6889_868376019.dbf\r\nORA-00280: alterar 200548268 para o thread 1 esta na sequencia #6889\r\n\r\n\r\nSpecify log: {&lt;RET&gt;=suggested | filename | AUTO | CANCEL}<\/pre>\n<p><strong>Como n\u00e3o temos os archives , vamos passar os redologs para tentarmos resolver o problema.<\/strong><\/p>\n<pre class=\"lang:default decode:true \">SQL&gt; recover database using backup controlfile until cancel ;\r\nORA-00279: alterar 200548268 gerado em 04\/15\/2018 16:35:10 necessario para o\r\nthread 1\r\nORA-00289: sugest?o : \/u01\/app\/oracle\/11.2.0\/db_1\/dbs\/arch1_6889_868376019.dbf\r\nORA-00280: alterar 200548268 para o thread 1 esta na sequencia #6889\r\n\r\n\r\nSpecify log: {&lt;RET&gt;=suggested | filename | AUTO | CANCEL}\r\n\r\n'+DATA\/ZMSOLHOM\/ONLINELOG\/group_2.257.915268943'\r\n\r\nORA-00310: o log arquivado contem a sequencia 6887; e necessaria a sequencia\r\n6889\r\nORA-00334: log arquivado: '+DATA\/ZMSOLHOM\/onlinelog\/group_2.257.915268943'<\/pre>\n<p>Vamos tentar o pr\u00f3ximo redolog<\/p>\n<pre class=\"lang:default decode:true \">SQL&gt; recover database using backup controlfile until cancel ;\r\nORA-00279: alterar 200548268 gerado em 04\/15\/2018 16:35:10 necessario para o\r\nthread 1\r\nORA-00289: sugest?o : \/u01\/app\/oracle\/11.2.0\/db_1\/dbs\/arch1_6889_868376019.dbf\r\nORA-00280: alterar 200548268 para o thread 1 esta na sequencia #6889\r\n\r\n\r\nSpecify log: {&lt;RET&gt;=suggested | filename | AUTO | CANCEL}\r\n'+DATA\/ZMSOLHOM\/ONLINELOG\/group_5.259.915269055'\r\nLog applied.\r\nMedia recovery complete.<\/pre>\n<p>Agora \u00e9 s\u00f3 abrir o database com resetlogs.<\/p>\n<pre class=\"lang:default decode:true \">SQL&gt; alter database open resetlogs;\r\n\r\nDatabase altered.<\/pre>\n<p>&nbsp;<\/p>\n<p>Referencia:\u00a0 metalink\u00a0 (Doc ID 1296264.1)<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Em bases que o archivelog n\u00e3o esta ativado corremos muitos riscos, entre ele o risco de termos o erro:\u00a0ORA-00600: internal error code, arguments: [kcratr_nab_less_than_odr] , esse erro podo ocorrer de muitas formas : This Problem is caused by Storage Problem of the Database Files. The Subsystem (eg. SAN) crashed while the Database was open. The Database then crashed because the Database Files were not accessible anymore. This caused a lost Write into the Online RedoLogs[&#8230;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_mi_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0},"categories":[21],"tags":[],"jetpack_featured_media_url":"","_links":{"self":[{"href":"http:\/\/zmsolution.com\/wp-json\/wp\/v2\/posts\/2049"}],"collection":[{"href":"http:\/\/zmsolution.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/zmsolution.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/zmsolution.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/zmsolution.com\/wp-json\/wp\/v2\/comments?post=2049"}],"version-history":[{"count":0,"href":"http:\/\/zmsolution.com\/wp-json\/wp\/v2\/posts\/2049\/revisions"}],"wp:attachment":[{"href":"http:\/\/zmsolution.com\/wp-json\/wp\/v2\/media?parent=2049"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/zmsolution.com\/wp-json\/wp\/v2\/categories?post=2049"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/zmsolution.com\/wp-json\/wp\/v2\/tags?post=2049"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}