Error: PLS-00801

Today (using Oracle 11.2.0.1.0 ) I got this error when compiling a pl/sql package:

PLS-00801: internal error [phdcsql_print_kge_errors::parm pos]
PL/SQL: Statement ignored
ORA-00900: invalid SQL statement


The description for PLS-00801: internal error [string] says:

Cause: This is a generic internal error that might occur during compilation or execution. The first parameter is the internal error number.

Action: Report this error as a bug to your Customer Support representative.


Oracle Critical Patch Update - January 2011

This week Oracle release the latest
Oracle Critical Patch Update Advisory.
As usual :"Due to the threat posed by a successful attack, Oracle strongly recommends that customers apply CPU fixes as soon as possible."
It fixes some remotely exploitable bugs without the need for username and password.

Check it out!

Potential Security Issue on Install of Oracle Database 11.2.0.2 and Grid Control 11.1.0.1

Oracle has identified a security vulnerability affecting the Oracle Universal Installer for Oracle Database Server 11g Release 2 Patchset 1 (11.2.0.2) and Oracle Enterprise Manager Grid Control 11g Release 1 (11.1.0.1.0) downloaded before November 16th 2010. This vulnerability may result in the compromise of the Oracle Single Sign-On (SSO) password used to connect to Oracle Support Systems while checking for recommended updates and patches during the initial install of these products.

ORA-600: kqd-objerror$

I didn't have an ORA-600 from some time (not that I miss them :-) ) when developing and testing.
Yesterday I had an ora-600: [kqd-objerror$]when compiling a trigger.
My DBA found the solution

ORA-38909 in Oracle 11g

Due to yesterday's question in PL/SQL Challenge I was confronted with the idea of having together 'LOG ERRORS' and 'SAVE EXCEPTIONS' in a FORALL statement.

DBMS_METADATA bug?

Today I found this bug in Oracle 10g R2 (I didn't try in 11G) when using the SQLTerminator in DBMS_METADATA:

writing code that BULKs into a rowtype will crash the session

Another bug that i found....Someone already told me that they new of this issue also reported by me some two years ago but I could not remember it :-(
(it's the old age...)

Of course its a code error to make a bulk into a rowtype variable, but if you try to code it it will not give you an error it will crash the session!

Here goes the code sample that makes it happend :-(


CREATE TABLE a_test (a VARCHAR2(20));


create or replace package test_pck is
end test_pck;

Then try to create the package

create or replace package body test_pck is

PROCEDURE test1
IS
lrt_test a_test%ROWTYPE;
BEGIN
SELECT * BULK COLLECT INTO lrt_test FROM a_test;
END test1;
end test_pck;


This will crash the session ...I try with SQLNavigator and SQLPlus

Microsoft, Apple, Oracle no TOP

Microsoft, Apple, Oracle estão no mesmo TOP nesta ordem.

Que TOP?, perguntam vocês. Pois bem no top de vulnerabilidades assumidas (normalmente com o lançamento de um novo patch) do 1º semestre deste ano.(ver report)

Oracle Critical Patch Update - Julho 2007

Entre outros fixes:

# 17 new security fixes for the Oracle Database. Two of these vulnerabilities may be remotely exploitable without authentication, i.e. may be exploited over a network without the need for a username and password. No new security fixes are applicable to Oracle Database client-only installations, i.e. installations that do not have the Oracle Database installed.

ORA-600/ORA-7445 Troubleshooter

Everyone dreads the Oracle ORA-00600 and ORA-07445 errors: they are the most esoteric errors in Oracle.

A tool called "ORA-600/ORA-7445 Troubleshooter" is available at Metalink to help figuring out what is happening and maybe to solve it.
It asks for the first argument of ORA-00600/ORA-07445 error with an optional database version number.

For example, to see the description of the error:

ORA-00600: internal error code, arguments: [723], [25908], [25908], [memory leak]

You enter 723 in the "ORA-600 First Argument" field.

Did you knew that the first argument is a pointer to where in the code the error was caught and thus is the key information in identifying the problem?

You can also copy and paste the "Call Stack Trace" there and then when you click on the "Search Call Stack" button an advanced MetaLink search is performed to find documents containing relevant sections from the call stack.

Call Stack extracts from the following files are supported:

• Generic foreground and background server trace files located in background_dump_dest and user_dump_dest
  
• OpenVMS NETV2 and BEQ log files located in ORA_ROOT:[NETWORK.LOG]
  
• WINDOWS CORE.LOG files
  
• GDB (debugger) backtrace call stacks (best endeavors)
  

Oracle Critical Patch Update - Abril 2007

Entre outros fixes:

"13 new security fixes for the Oracle Database. Additionally, 1 new security fix for Oracle Enterprise Manager, 1 new security fix for Oracle Workflow Cartridge, and 1 new security fix for the Ultra Search component affect code bundled with the Oracle Database. 2 of these vulnerabilities may be remotely exploitable without authentication, i.e. they may be exploited over a network without the need for a username and password."

1 new security fix for Oracle Secure Enterprise Search, which is a separate product that is not installed with the Oracle Database. The Oracle Database Ultra Search component contains code also present in the Oracle Secure Enterprise Search product, and both are potentially vulnerable.

2 new database vulnerabilities addressed by this Critical Patch Update, DB11 and DB13, affect Oracle Database client-only installations (installations that do not have the Oracle Database installed). They are potentially exploitable where a privileged operating system process is passing input from an unprivileged source to the affected program. Oracle recommends applying this Critical Patch Update to client-only installations which may be using the affected programs in this way, or which are affected by client-only issues fixed in prior Critical Patch Updates if the prior patches have not been applied.

This Critical Patch Update contains 5 new security fixes for Oracle Application Server. 1 Oracle Workflow Cartridge fix and 1 Oracle Secure Enterprise Search fix also affect Oracle Application Server. 2 vulnerabilities may be remotely exploitable without authentication, i.e. they may be exploited over a network without the need for a username and password. No new fixes are applicable to client-only installations, i.e. installations that do not have Oracle Application Server installed.

Oracle Critical Patch Update - January 2007

Foi lançado em Janeiro o último patch da Oracle.

"This Critical Patch Update contains a total of 26 new security fixes for Oracle Database products, divided as follows:

*17 new security fixes for the Oracle Database, 1 of which may be remotely exploitable without authentication, i.e. it may be exploited over a network without the need for a username and password. 1 fix is applicable to Oracle Database client-only installations, i.e. installations that do not have the Oracle Database installed.
*9 new security fixes for Oracle HTTP Server, 8 of which may be remotely exploitable without authentication, i.e. they may be exploited over a network without the need for a username and password. Oracle HTTP Server is an optional product that is not installed by default with the Oracle Database. If it has not been installed, this software will not be present and the Oracle HTTP Server patches are not required. Oracle Database versions up to and including Oracle Database 9i Release 2 allowed Oracle HTTP Server to be installed as an optional component of the database. Oracle Database versions 10g Release 1 and higher include Oracle HTTP Server on the Companion CD."

"One new database vulnerability addressed by this Critical Patch Update, DB11, affects Oracle Database client-only installations (installations that do not have the Oracle Database installed). It is potentially exploitable where a privileged operating system process is passing input from an untrusted source to the affected program. Oracle recommends applying this Critical Patch Update to client-only installations which may be using the affected program in this way, or which are affected by client-only issues fixed in prior Critical Patch Updates if the prior patches have not been applied."

"This Critical Patch Update contains 12 new security fixes for Oracle Application Server, 8 of which may be remotely exploitable without authentication, i.e. they may be exploited over a network without the need for a username and password. No new fixes are applicable to client-only installations, i.e. installations that do not have Oracle Application Server installed.

This Critical Patch Update also contains 8 new security fixes for Oracle Application Server products that are not supported for standalone use, but are supported for use as part of supported products, i.e. those listed in the Category I section. More details of these fixes can be found in the sections of this document covering: Oracle Database, Oracle Collaboration Suite and Oracle E-Business Suite. They are not discussed further in this section, as they do not apply to Oracle Application Server standalone instances."

Livro que tenho de ler

"Oracle Hackers Handbook" de David Litchfield ISBN 978-0-470-08022-1.

Um livro para ser lido por todos os DBA de ORACLE e por todos os que se interressam por segurança informática.

Bug I found in Oracle DB

Sometimes I( or people on my team) encounter some Oracle bugs.
I present here the test case of the last bug I found in PL/SQL that gives bad results
(I already warn Oracle and the Bug got the number 5847371) in Oracle 10.2.0.2.


CREATE TABLE a_test (a VARCHAR2(20));
INSERT INTO a_test VALUES ('test');

CREATE OR REPLACE
FUNCTION teste_a0 (p_notifica IN INTEGER DEFAULT 0)
RETURN PLS_INTEGER
IS
l_found PLS_INTEGER := 0;
BEGIN
FOR c
IN (SELECT a_test.a
FROM a_test
WHERE (p_notifica = 0))
LOOP
l_found := 1;
END LOOP;

RETURN l_found;
END
;
/

SELECT TESTE_A0(0) from dual;
--should return 1 (correct !)


CREATE INDEX a_test_i ON a_test
(
a ASC,
0 ASC
)
/

SELECT TESTE_A0(0) from dual;

--returns 0!! when should return 1

if the line
WHERE (p_notifica = 0))
is exchanged by
WHERE (p_notifica+1 = 1))

the result is correct =>1

Oracle Critical Patch Update October 2006

A oracle avisou os utilizadores da saída de um novo PATCH.

Entre outras coisas corrige (esperemos)

(...)22 new security fixes for the Oracle Database, all of which require a valid database username and password.
6 new security fixes for Oracle HTTP Server, 5 of which may be remotely exploitable without authentication, i.e. they may be exploited over a network without the need for a username and password. Oracle HTTP Server is an optional product that is not installed by default with the Oracle Database. If it has not been installed, this software will not be present and the Oracle HTTP Server patches are not required. Oracle Database versions up to and including Oracle Database 9i Release 2 allowed Oracle HTTP Server to be installed as an optional component of the database. Oracle Database versions 10g Release 1 and higher include Oracle HTTP Server on the Companion CD.
(...)

O "Critical Patch Update Advisory" está disponivel em:

MetaLink as Doc ID 391558.1
ou em
Oracle Technology Network