Ora 00604 ошибка на рекурсивном sql уровне 1 ora 12705

Ora 00604 error occurred at recursive sql level 1 ora 12705

Ошибка при установке соединения с сервером из Oracle SQL Developer:

ORA-00604: error occured at recursive SQL level 1ORA-12705: Cannot access NLS data files or invalid enviroment specified

Для исправления делаем следующие действия:

Открываем idebinide.conf
Дописываем туда две строчки:

AddVMOption -Duser.language=en
AddVMOption -Duser.region=us

И всё!

Оставить первый комментарий:

Работа со строками в Oracle (PL/SQL)

Основные способы обработки строковых значений в Oracle. В этой публикации я приведу основные функции (читать далее. )

Работа с XML в Oracle PL/SQL (Часть 1)

В этой публикации я приведу основные способы работы с XML в Oracle, которые сам использую. Здесь буд (читать далее. )

Функция Oracle TO_DATE (PL/SQL)

Функция TO_DATE — преобразует строку в переменную времени DATE. Синтаксис: TO_DATE(исходная_строка, (читать далее. )

Объединение выборок UNION, INTERSECT, MINUS в Oracle (PL/SQL)

В Oracle присутствует возможность объединять выборки. Для объединения используются операторы: UNION (читать далее. )

XML в Oracle PL/SQL (Часть 2 — Выборки в виде XML)

В предыдущей публикации были рассмотрены некоторые приёмы манипуляции с XML в Oracle, теперь рассмот (читать далее. )

Источник

ORA-00604 Error Occurs at Recursive SQL level While Creating Package/Procedure using SQL Developer on Upgraded 12c Database (Doc ID 2476156.1)

Last updated on JULY 20, 2021

Applies to:

Symptoms

After patching existing 12c database (for example, patch to 12.2.0.1.181016), the following exception is seen while connecting and creating a Package/Procedure from SQL Developer:

CREATE OR REPLACE
PACKAGE PACKAGE1 AS
END PACKAGE1;
/

Error starting at line: 1 of the command:
CREATE OR REPLACE
PACKAGE PACKAGE1 AS
END PACKAGE1;
Error report —
ORA-00604: a recursive SQL level 1 error has occurred
ORA-00904: «DECL_OBJ #»: invalid identifier
00604. 00000 — «error occurred at recursive SQL level% s»
* Cause: An error occurred while processing a recursive SQL statement (a statement applying to internal dictionary tables).
* Action: If the situation described in the next error on the stack can be corrected, do so; otherwise contact Oracle Support.

However, if run this same command in SQL*Plus directly on the server, then it works correctly.

Changes

Database 12c is patched or upgraded

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

Источник

ORA-00604: error occurred at recursive SQL level 1 ORA-12705: invalid or un

Hello, I’m so worried because I can’t resolve the following problem with my oracle clients on my desktop.

Initial state:
SO: Windows XP SP1
Oracle clients: Oracle 8i
Issue: I can get connection and access to the DB successfully

Middle state:
SO: Windows XP SP1
Oracle clients: The same Oracle 8i and a new Oracle 9 client.
Issue: We need to swap between each DB 8 and 9 using the HOME SELECTOR to get connections and access. I understand that the Oracle 9 Client have back-compatibility with 8i DBs. If I tray to get connection to the DB 8i using the Oracle 9 we get the following errors.
Errors: ORA-00604: error occurred at recursive SQL level 1
ORA-12705: invalid or unknown NLS parameter value specified

I decided to uninstall all the products (Oracle 8 and 9) using the Oracle Universal Installer. We didn’t erase folders nor registers, we just used Oracle Universal Installer. Then we installed Oracle 10g

Final Sate:
SO: Windows XP SP1
Oracle clients: only Oracle 10g
Issue: I can get connection and access to the Oracle 9 DB. But trying with the Oracle 8i DB I got the same problem described above.
Errors: ORA-00604: error occurred at recursive SQL level 1
ORA-12705: invalid or unknown NLS parameter value specified

Please can somebody tell me how can I resolve this problem.
Thanks.
Luis Carlos

Источник

Failure conection ORA-00604 and ORA-12705

Hi
I can’t connect any database from raptor, by I can connect from sqlplus, em, toad, sqldeveloper, etc

The error is:
Status: Failure ORA-00604: error occurred at recursive SQL level 1 ORA—12705: invalid or unknown NLS parameter value specified

Which version are you running?
Win or Linux?

May you post value of NLS* parameter set in your environment?

SO: Windows Xp SP 2
Raptor Version 1..0.0.07.15
Build MAIN-07.15

I have installed one oracle home with Oracle 9.2.0.6

I can set all parameters:
Connection Name
Username
Password
Hostname
Port
SID
and then conection failure ORA-00604 and ORA-12705

but I change the password from wrong password and the error is
Failure ORA-01017: invalid username/password; logon denied

NLS_LANG=LATIN AMERICAN SPANISH.WE8MSWIN1252

yes
now connect

exelente
muchisimas gracias

apart from changing locale settings, you may want to check your NLS_LANG.

I can connect with NLS_LANG=ITALIAN_ITALY.WE8ISO8859P1

NLS_LANG has the following syntax:
NLS_LANG=language_territory.character set
(Note the underscore between language and teritorry, and dot between teritory and character set)

I am not sure which territory fits best. the docs does not report Argentina among supportes ones.

You may take a look at the Globalization Guide to choose the best match.

Источник

ORA-00604: Error Occurred At Recursive SQL Level 1.When DB User Trying to Change Password (Doc ID 2232779.1)

Last updated on APRIL 03, 2021

Applies to:

Symptoms

While changing password for users with expired password ,below error is returned for all users in the database. No trigger is created to prevent password from getting changed.

ERROR:
ORA-28001: the password has expired

Changing password for test
New password:
Retype new password:
ERROR:
ORA-00604: error occurred at recursive SQL level 1
ORA-06502: PL/SQL: numeric or value error
ORA-06512: at line 30

Changes

No.Changes were made in Database

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

Источник

Even if you use the same credentials, your colleague may have a different environment with PL/Scope disabled.

SQL> create procedure p1 as
  2  begin
  3    null;
  4  end;
  5  /

Procedure created.

SQL> select count(*) from PLSCOPE_IDENTIFIER$;

  COUNT(*)
----------
      2057

Compile the procedure without PL/Scope:

SQL> show parameter plscope

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
plscope_settings                     string      IDENTIFIERS:NONE
SQL> alter procedure p1 compile;

Procedure altered.

SQL> select count(*) from PLSCOPE_IDENTIFIER$;

  COUNT(*)
----------
      2057

No change. Now compile with PL/Scope enabled:

SQL> alter session set plscope_settings='IDENTIFIERS:ALL';

Session altered.

SQL> alter procedure p1 compile;

Procedure altered.

SQL> select count(*) from PLSCOPE_IDENTIFIER$;

  COUNT(*)
----------
      2058

This created some extra metadata in the above table which happens to be in the SYSAUX tablespace. Now disable and compile again:

SQL> alter session set plscope_settings='IDENTIFIERS:NONE';

Session altered.

SQL> alter procedure p1 compile;

Procedure altered.

SQL> select count(*) from PLSCOPE_IDENTIFIER$;

  COUNT(*)
----------
      2057

Back to the original state.

This is the problem:

ORA-01654: unable to extend index SYS.I_PLSCOPE_SIG_IDENTIFIER$ by 8 in tablespace SYSAUX, which simply means the SYSAUX tablespace is full.

Being unable to compile the PL/SQL code with PL/Scope enabled is just a symptom of the above error. Ask the DBA to make/increase space in the SYSAUX tablespace. PL/Scope is a configurable option in SQL Developer (Tools — Preferences — Database — PL/SQL Compiler — PLScope identifiers).

Even if you use the same credentials, your colleague may have a different environment with PL/Scope disabled.

SQL> create procedure p1 as
  2  begin
  3    null;
  4  end;
  5  /

Procedure created.

SQL> select count(*) from PLSCOPE_IDENTIFIER$;

  COUNT(*)
----------
      2057

Compile the procedure without PL/Scope:

SQL> show parameter plscope

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
plscope_settings                     string      IDENTIFIERS:NONE
SQL> alter procedure p1 compile;

Procedure altered.

SQL> select count(*) from PLSCOPE_IDENTIFIER$;

  COUNT(*)
----------
      2057

No change. Now compile with PL/Scope enabled:

SQL> alter session set plscope_settings='IDENTIFIERS:ALL';

Session altered.

SQL> alter procedure p1 compile;

Procedure altered.

SQL> select count(*) from PLSCOPE_IDENTIFIER$;

  COUNT(*)
----------
      2058

This created some extra metadata in the above table which happens to be in the SYSAUX tablespace. Now disable and compile again:

SQL> alter session set plscope_settings='IDENTIFIERS:NONE';

Session altered.

SQL> alter procedure p1 compile;

Procedure altered.

SQL> select count(*) from PLSCOPE_IDENTIFIER$;

  COUNT(*)
----------
      2057

Back to the original state.

This is the problem:

ORA-01654: unable to extend index SYS.I_PLSCOPE_SIG_IDENTIFIER$ by 8 in tablespace SYSAUX, which simply means the SYSAUX tablespace is full.

Being unable to compile the PL/SQL code with PL/Scope enabled is just a symptom of the above error. Ask the DBA to make/increase space in the SYSAUX tablespace. PL/Scope is a configurable option in SQL Developer (Tools — Preferences — Database — PL/SQL Compiler — PLScope identifiers).