Ora 00600 internal error code arguments qcissetplsqlctx tzi init

ORA-00600 [qcisSetPlsqlCtx:tzi init] on Physical Standby Database (Doc ID 1561771.1)

Last updated on JUNE 06, 2019

Applies to:

Symptoms

1. The following error is raised on a physical standby database instance:

At instance startup the alert file shows:

Review of the generated tracefiles reveals a call stack similar to:

To view full details, sign in with your My Oracle Support account.

Don’t have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

Oracle offers a comprehensive and fully integrated stack of cloud applications and platform services. For more information about Oracle (NYSE:ORCL), visit oracle.com. пїЅ Oracle | Contact and Chat | Support | Communities | Connect with us | | | | Legal Notices | Terms of Use

Источник

ORA-600 [qcisSetPlsqlCtx:tzi init] after Database Restart (Doc ID 362036.1)

Last updated on JANUARY 30, 2022

Applies to:

Oracle Database — Enterprise Edition — Version 9.0.1.4 and later
Oracle Database Cloud Schema Service — Version N/A and later
Oracle Database Exadata Cloud Machine — Version N/A and later
Oracle Cloud Infrastructure — Database Service — Version N/A and later
Oracle Database Backup Service — Version N/A and later
Information in this document applies to any platform.

Symptoms

Database startup logged errors like:

• «Failed to load timezone data file timezlrg.dat»
• «error 41 encountered when initializing ldm.»
• ORA-00600: [qcisSetPlsqlCtx:tzi init]

Changes

Database was shutdown/restarted.

Cause

To view full details, sign in with your My Oracle Support account.

Don’t have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

Oracle offers a comprehensive and fully integrated stack of cloud applications and platform services. For more information about Oracle (NYSE:ORCL), visit oracle.com. пїЅ Oracle | Contact and Chat | Support | Communities | Connect with us | | | | Legal Notices | Terms of Use

Источник

Learn DBA : A Life Long Learning Experience

Sharing knowledge is the ultimate key to gaining knowledge… The only two things that stay with you for life are you & your knowledge.

Live while you can! Teach & inspire while you could & Smile while you have the teeth.

• ASM
  • Creating ASM Instance and diskgroups manually without DBCA
  • 20 ASM Realtime | Interview Questions
  • How to make a cold backup for database running on ASM ( using RMAN )
  • Moving a Single Datafile from File System to ASM System (METHOD 1)
  • Moving a Single Datafile from File System to ASM System (METHOD 2)
  • Things to consider while adding new disk/ Rebalancing existing Disk Group
• Dataguard
  • Dataguard Modes
  • Dataguard Modes — II
  • Oracle DataGuard Setup
  • invalid archived log deletion policy
  • recover from the Loss of a Datafile on a Standby Database ?
  • MRP terminated with ORA-00600: internal error code, arguments
  • Recover archive gaps in standby database — using 2 methodss
  • Gap Resolution in Dataguard
  • Convert Physical Standby to Snapshot Standby and Vice Versa
  • Re-create Redo-logs on Standby/ Primary
  • Pre-check for DataGuard switchover Process
  • ORA-19815: WARNING: db_recovery_file_dest_size
  • How do you purge old archivelogs which are applied on Standby DB
  • Pre-check For SWITCHOVER using DG Broker
  • https://oracle-dba-help.blogspot.com/2016/03/data-guard-modes.html
  • ORA-01274 : RENAME THE UNKNOW FILE IN THE STANDBY DATABASE
• Core DBA
  • Database Creation in Easy 6 Steps
  • Oracle Networking
  • Tablespace management
  • Housekeep : Quick Tips for DBA
  • Health check for DB
  • ORA-12537 While Connecting To Database Via Listener
  • How to identify the applied patche-set of your Oracle Home
  • Accessing a schema without knowing the password
  • ORA-12505: TNS:listener does not currently know of SID given in connect descriptor
  • Session Related Scripts
  • How to check ORA Error on DB Server – Beginner Tip
  • Working with Redo Logs
  • Decommission of Oracle Database
  • Roles in Oracle — Managing Users
  • Oracle Release Number Format
  • Troubleshooting Handy-Guide
  • Understanding the Upgradation Process
  • Query to find the session creating more redo
  • Audit in Oracle
  • Troubleshooting Internal Errors and Error-Look-up Tool on MOS
  • Troubleshooting Issues with Undo Tablespace
  • User Management
  • User Management — II
  • Data Pump Gets Better
  • MEMORY_TARGET Parameter
• Interview
  • Oracle Datapump Scenarios
  • Troubleshooting Issues with Undo Tablespace
  • General Tips to Prepare for an Oracle DBA Job Interview
  • RMAN Questions
• Frequently Asked
  • How to identify the applied patche-set of your Oracle Home
  • Topic need to get clear to become expert in Oracle DBA
  • Working with Redo Logs
  • Oracle Database Block corruption
  • What happens during Instance Recovery
• How To..
  • Database Life for DBA.
  • Daily Activities of an Oracle DBA
  • What are the Daily a DBA do ?
  • How To Recompile Invalid Objects in Oracle
  • How To.. Queries
  • MEMORY_TARGET Parameter
  • Clear RAM Cache, Buffer
• Postgres Admin
  • Installing PostgreSQL Server on CentOS, RHEL 6 / 7 Systems
  • Creating a database in Postgres
  • Initialize multiple Postgres instance on the same RHEL server
  • How to stop starting of clusters while starting up services
  • Setup a streaming replication
  • Switchover- master server and warm standby (with streaming replication)
  • All About Physical Replication and Log shipping
  • PostgreSQL Upgrade and troubleshooting
  • Timeline Switch issue
  • Query to identify the lag in replication
  • Drop table : ERROR: must be owner of relation table_name
  • PgBadger
  • PgCenter
  • PgTune
  • Internals of Toast Table
  • Influencing Query Execution Plan
  • Create Extension ERROR
  • Find Uptime in PostgreSQL
  • Set DB Timezone
  • Clear RAM Cache, Buffer
  • Read-Only User in Postgres
  • Everything you need to know about Streaming Replication
  • Ora2Pg Migrate Oracle to Postgres
  • Total Page Cost
  • PostgreSQL 13 — Everything you need to know
  • Startup Failure — .conf file
  • All About Postgres Upgrade
• MySQL Admin
  • MySQL DB Installation and Administration
  • Setup Master and Slave replica (Same server)
  • MySQL : Flush Tables
  • Troubleshooting Replication
  • MySQL Cache
• Oracle Tuning
  • Basic Guide
  • Session Related Scripts
  • AWR :: Beginners Guide
  • All About ASH — Active Session History
  • Wait Events : checkpoint busy waits or archiver busy waits
  • Find sessions performing sort operations : TEMP Tablespace occupants
  • Generate ADDM task and generate its report for Tuning
  • Database Performance Tuning Scripts -Keep Handy
  • Buffer Busy Wait
  • Simulating the Deadlock
  • Latches
• RMAN
  • Steps to Schedule any RMAN Jobs In Windows Server
  • ORA-01194: file 1 needs more recovery to be consistent
  • Loss of Current Online Redo-Log
  • RMAN «baby Steps»
  • Recovery of ControlFiles
  • Loss of Datafile
  • Recovery from complete loss of all online redo log files
  • Block Change Tracking
  • RMAN Questions
  • Instance Recovery
  • Redundancy and Recovery window in RMAN
  • Cold Backup
  • Database Cloning
  • Contact
  • Drop Database using RMAN
  • PITR to older Incarnation
• About

Sunday, 1 August 2021

ORA-00600: internal error code, arguments: [qcisSetPlsqlCtx:tzi init]

Below document explains the issue faced after the upgrade, troubleshooting and need for timezone files.

Application or sql-developer may see below error while performing the operations in database.

There might be database upgrade or patch activity recently happened at the database end and the required Timezone files are missing.

Check the missing timezone files and copy it from old Home to the current Oracle Home and restart the database.

Источник

Ora 00600 internal error code arguments qcissetplsqlctx tzi init

ORA-0600

Ошибка ORA-0600 является внутренним кодом ошибки для программных исключений Oracle. Её возникновение указывает на то, что процесс столкнулся на низком уровне с неожиданным условием.

Ошибка ORA-0600 включает список аргументов в квадратных скобках:

Первым аргументом является внутренний номер сообщения или символьная строка. Этот аргумент и номер версии базы данных является первостепенным в идентификации первопричины и потенциального воздействия на базу данных. Остальные аргументы используются, что бы предоставить дополнительную информацию (например, значения внутренних переменных и т.д.).

В зависимости от вида первого аргумента, в Oracle имеются два типа ошибок ORA-0600:

• первый аргумент является числом, которое отражает исходный компонент или слой, в котором происходит ошибка.
• первый аргумент является мнемоникой, которая указывает на исходный модуль, где произошла ошибка. Этот тип внутренней ошибки более предпочтителен в настоящее время.

Категории ошибок ORA-0600 ранжированные по номеру

В следующей таблице приведена информация относительно внутренних числовых кодов ошибок ORA-0600, используемых в Oracle.

Категории ошибок ORA-0600 ранжированные по мнемонике

Следующая таблица детализирует возможные мнемоники ошибок ORA-0600.

Справочник ошибок ORA-0600

ORA-00600: internal error code, arguments: [1113]

Сбой процесса, возможный сбой экземпляра.

Попытка освободить state object, хотя он уже находиться в свободных списках. Нарушение целостности в памяти SGA или из-за bug в плохом управлении state objects.

Проанализировать дамп PMON, установить заплатки на bug.

ORA-00600: internal error code, arguments: [4193], [a], [b]

[a] – Номер изменения (SCN) записи в серменте отката (Undo), [b] SCN записи в журнале повторного выполнения (Redo)

Сбой процесса, возможное повреждение сегмента отката, невозможность продолжения наката журналов на STANDBY.

KERNEL TRANSACTION UNDO

Было обнаружено несоответствие между журнальной записью и записью в сегменте отката.

Перейти на новую версию Oracle (10.2.0.5, 11.2.0.1); Восстановить экземпляр из резервной копии.

ORA-00600: internal error code, arguments: [12333], [a], [b],[c],[d]

Отказ процесса. Физического искажения нет.

USER/ORACLE INTERFACE LAYER

В результате сетевой ошибки получены плохие данные, приложение клиента послало неправильные данные, данные в сетевом буфере были записаны поверх, всевозможные bug (столбцы LONG).

Проверить сетевое соединение и настройки NLS, заменить версию клиента Net на более новую.

ORA-00600: internal error code, arguments: [13001]

Физического искажения нет.

Возникает при удалении строк из таблицы, в случаях когда запись уже удалена. Такое обычно происходит если в таблице есть внешний ключ на столбец в этой же таблице. По своей сути не является полноценной ошибкой.

Переделать внешний ключ.

ORA-00600: internal error code, arguments: [15419], [a]

Отказ процесса. Физического искажения нет.

Kernel Kompilation pl/sql Compiler

Всевозможные bug. Для большей информации смотреть дополнительные ошибки в trc файле. Bug: 2829071, 2588469, 2437995

Установить заплатки на bug. Если не помогает, модифицируйте PL/SQL код.

ORA-00600: internal error code, arguments: [15735], [a], [b]

[a] — значение parallel_execution_message_size в котором нуждается запрос, [b] — текущее значение parallel_execution_message_size

Ошибка с записью в trace файл. Физического искажения нет.

Открыть trc файл ошибки. Найти sql оператор. Для таблиц этого оператора выполнить запрос select table_name, degree from dba_tables where table_name = ». Выбрать таблицы у которых degree ‘1’. Выполнить для каждой таблицы команду alter table noparallel. В качестве второго способа можно порекомендовать увеличить значение параметра parallel_execution_message_size.

ORA-00600: internal error code, arguments: [16607]

Сбой процесса, повреждения данных нет.

Kernel Generic Library cache Subordinate set/cache manager

Была произведена попытка получить подчиненный элемент, но при поиске, куча памяти для данного элемента не была закреплена.

Установить заплатки на bug.

ORA-00600: internal error code, arguments: [17090],[a], [b],[c],[d]

Отказ процесса. Физического искажения нет.

GENERIC CODE LAYER

Уничтожьте сеанс и связанный с ним процесс.

ORA-00600: internal error code, arguments: [17271], [instantiation space leak]

Сбой процесса. Повреждения данных нет.

Kernel Generic Instantiation manager

Исключение возникает при попытке Oracle деинстанцировать (уничтожить экземпляр) разделяемый объект (курсор) во время выхода из сеанса. В этот момент, Oracle проходит связанный список разделяемых объектов для деинстанцирования, и находит, что объект был помечен как не разделяемый. Этого не должно быть, поэтому возникает исключение. Может проявляться при работе с распределёнными базами данных.

Игнорировать ошибку. Если ошибка повторяется, то идентифицировать курсор в trace файле и переделать, или поставить последний патч Oracle закрывающий баги.

ORA-00600: internal error code, arguments: [25012], [a], [b]

[a] — номер табличного пространства, [b] — относительный номер файла БД

Возможно физическое искажение.

KERNEL FILE MANAGEMENT TABLESPACE COMPONENT

Всевозможные bug ( 4305391, 3915343, 3900237, 3771508, 3751874, 3430832, 3258674, 3150268, 3070856, 2531519, 2526334, 2287815, 2214167, 2212389, 2189615, 2184731, 1968815, 1949273, 1872985).

Установить заплатки на bug.

ORA-00600: internal error code, arguments: [ktspgsb-1]

Ошибка возникает если в объекте (таблице) присутствуют логически повреждённые блоки. Выполнение команд (TRUNCATE, INSERT и т.д.) применительно к объекту приводит к этой ошибке.

ORA-00600: internal error code, arguments: [pfri.c: pfri8: plio mismatch ]

Несоответствие создания экземпляра PL/SQL объекта. Вероятнее всего возникает из-за инвалидации PL/SQL объекта (bug 9691456, зафиксирован в 11.2.0.2). Проявлялась в триггере на версии 10.2.0.5.

Приведение PL/SQL объекта в нормальный статус.

Источник

Oracle database is the most popular database among the database industry because of its accuracy and performance. It is a Relational database management system (RDBMS) and capable to store and manage lots of new entries in a sufficient manner and why so it is one of popular database.

The majority of getting errors related to Oracle database increases if you do not have enough knowledge of Oracle. Yes, it is a fact and due to having less knowledge of using Oracle database, users get different errors messages and one of them is the ora-00600 internal error code.

One more issue with this error is that it can normally generate along with arguments encloses in a square bracket, and here occurs the critical situation because the meaning of these enclosed arguments alters with the version of the database. It is very difficult for a database administrator to verify the reason for the database error. This error also gets more difficult when more than one ORA-00600 error occurs because due to this the generated trace files and log files become large in number.

If you are the one who got this error then do not worry, you have come to the right place. I am saying so because here you will get to know how to fix ora-00600 internal error code.

Why ORA-00600 Error Occurs?

There are several causes due to which ORA_00600 internal error code occurs. It is a generic internal error number to execute Oracle program. This error indicates that the process has some unexpected conditions. The first argument is internal message number and the other arguments are several names, character strings and numbers. However, the number may change the meaning of different Oracle versions. Here are some of the reasons of getting this error:

#1: File Corruption: When an Oracle supported file has been corrupted then you may get ora-00600 internal error code.

#2: Timeouts: While connecting with the database the timeout occurred or the query runs for a long time and timeout occurs then this internal error code takes place.

#3: Failed Data Checks In the Memory: Due to the failed data checks in the memory, ora-00600 internal error code occurs.

#4: Hardware/Memory/IO: When the hardware is incompatible or the memory is full in Oracle version and you still work on it may cause this error to take place.

#5: Incorrectly Restored Files: When the Oracle files are restored in an improper way then this error will occur.

There are several reasons for ORA-00600 error like compatibility issues to database block error. Sometimes, this kind of error remains unsolvable. However, it is quite difficult to find the root cause of this error.

Several reasons are there ways with the help of which you will be able to fix ora-00600 internal error code. Here, I have tried my best to let you know how to resolve ora-00600 internal error code. Here are some of the major solutions you should try:

Fix #1: Writes Error Message In Alert Log & Trace File

The very first option you can try to fix ora-00600 internal error code is to write error message and trace file in alert.log file. The Oracle engine will write the error in alert.log file. The trace file location will find in alert.log file.

Fix #2: Try Other Solutions Based On Error Code Examples

You may get several errors reported within the space of a few minutes that starts with the ORA-00600 error. Well, apart from fixing ora-00600 error, you can check trace files and alert logs. Another solution you can try is to find the source of the issue is important. Most of the time, you will not be able to find the source by checking the alert or trace the alert logs. Also, these errors will not give you clear information about what has happened with the server.

Here are some great examples that might help the Oracle developers or users and DBAs to restore this issue:

Example #1:

ORA-00600: internal error code, arguments: [kxtotolc_lobopt], [], [], [], [], [], [], [], [], [], [], []
00600. 00000 –  “internal error code, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s]”

Cause of this error: This example is the generic internal error number for Oracle program exceptions. Also, this error indicates that a process has encountered an exceptional condition.

How To Fix This Issue

If you are updating or inserting the CLOB column value as null with the use of merge statement and the merge the statement table has trigger. The same null CLOB column value if you try to update or insert CLOB value in another table with the use of trigger then you will get ora-00600 internal error code. You will also notice that the session is closed automatically, you will also get this error in both Oracle 11g as well as 12c.

Below are the steps to fix this issue:

• First of all, you have to create a table CLOB_ table(sno number, c_clob clob);
• Next, you have to create table table test_Clob_table_stg as select * from test_Clob_table;
• After this, you are required to create a trigger on Clob_table table and then you have to insert data in staging table test_Clob_table_stg using trigger:

CREATE OR REPLACE trigger test_Clob_table_trg AFTER INSERT ON Clob_table
FOR EACH ROW
DECLARE
BEGIN
INSERT INTO test_Clob_table_stg VALUES(:new.sno,:new.c_clob);
EXCEPTION
WHEN others THEN
NULL;
END;
/

• You have to then run the below query.

MERGE INTO Clob_table a USING (
select 1 AS sno, null AS C_CLOB from dual) b
ON (a.sno = b.sno)
WHEN MATCHED THEN
UPDATE SET C_CLOB = b.C_CLOB
WHEN NOT MATCHED THEN
INSERT (a.sno,a.C_CLOB) VALUES (b.sno,b.C_CLOB);

Example #2:

Error Code:

ORA-00600: internal error code, arguments: [15851], [3], [3499], [2], [1], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [15851], [3], [3499], [2], [1], [], [], [], [], [], [], []
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at “SIEBEL_ODS.MS_CCM_UTILITIES”, line 2866
ORA-04088: error during execution of trigger ‘SIEBEL_ODS.MS_CCM_TI_INVESTIGATION’
00600. 00000 –  “internal error code, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s]”

Cause of this example: This example is the generic internal error number for Oracle program exceptions. This error message indicates that a process has encountered an exceptional condition.

How To Fix This Issue:

The other function used in trigger has variable size issue because you got this error, this trigger has created on merge statement table that is sued in “_P” package. This error won’t track the error log tables until if you run all the statement outside of the package, you get error in si_application_error_log.

Example #3:

SQL Error: ORA-00600: internal error code, arguments: [13013], [5001], [158796], [30437895], [0], [30437895], [17], [], [], [], [], []

How To Fix This Issue:

You can create index on one table for improving the performance of query, on same table you are updating data in some stages.

This will work and improve the performance in local examples and customer testing examples, but users get ora-00600 internal error code in UAT after applying the patch, whenever users has done update statement stage flow. You will get the below update statement highlighted in trace file with the error message, it helped users to debug the issue and also you will get some more information in alert log for an internal error.

Query to trace file with error message:

UPDATE MS_ITC_AUDIT_V SET STATUS = ’38’, AUDIT_STATUS = ’38’ WHERE AUDIT_ID = :B1 AND INSTANCE_ID = (SELECT MAX(INSTANCE_ID) FROM MS_ITC_AUDIT_V WHERE AUDIT_ID = :B1 );

Ultimate Solution: Try Oracle File Repair Tool To Fix ORA-00600 Internal Error Code

Apart from all these solutions that are mentioned above, if you are unable to fix ora-00600 error then you can try Oracle File Repair Tool. This tool will allow you to fix this error and recover Oracle database easily. This tool has some great features that will let you know how to fix ora-00600 internal error code. I am sure that you will not get disappointed after trying this tool. All you have to do is to download and install this tool and follow the step by step instructions to fix and recover oracle database that shows ora-00600 internal error code.

Steps To Fix ORA-00600 Internal error Code

Step 1: Search the Initial screen of Stellar Phoenix Oracle Repair & Recovery with a pop-up window showing options to select or search corrupt Oracle databases on your computer.

Step 2: Click Scan File to initiate the scan process after selecting the oracle database. The recoverable database objects get listed in left-side pane.

Step 3: Click an object to see its preview.

Step 4: : Click Start Repair in the icon bar to start the repair process. A pop-up window is displayed which show the steps needed to perform further. Click next and continue.

Step 5: Give the user name, password and path of the blank database where you want to save the repaired database objects.