SQL Navigator 6.6 released

Quest Software released the 6.6 version of SQL Navigator. Mainly it corrects some bugs.
The most usefull new feature is in the history search (where you can search the runned scripts/commands for an expression) to filter the commands by type.

Check the Release Notes and the Known Issues List.

SQL Navigator 6.5 released

Quest released a new version of SQL Navigator. Mainly it corrects bugs and some new features (like the filter in the history and the join of the 6.3 DB filter with the 6.4 version).

Check the Release Notes and the Known Issues List.

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!

Security bug in Adobe Acrobat PDF Reader and Adobe Flash Player

Another critical vulnerability was reported in Adobe Acrobat PDF Reader and Adobe Flash Player.

SQL Navigator 6.4 released

Quest released a new version of SQL Navigator. Mainly it corrects some bugs and redefines the filters use (now you have to save the filter before using it, but stores the filters from session to session).
Warning: don't name you filter using the % sign (doesn't work = bug already reported).

Check the Release Notes.

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

SQL Navigator 6.3 released

New features of SQL Navigator version 6.3 include:

* Automated Code Testing - allows you to describe the expected behavior of a program and have the required code for the test case generated - test definitions are stored in a repository so that you can easily update them when required
* Debugging Triggers - gives you more options in which you can use debug triggers - through DBMS_OUTPUT or the optional PL/SQL Debugger - when using a trigger is only fired by activating the particular SQL DML operation (INSERT. DELETE or UPDATE) that the trigger was designed to respond to, and can be done using INSERT. DELETE or UPDATE statements executed from an anonymous PL/SQL block
* New Tablespace Editor - now includes a tablespace VOE to manage tablespace objects, which can be created, edited and dropped - additional information on Data Files and Disk Groups is also available
* New Quest SQL Tracker - monitors SQL statements issued by Windows applications and services that access Oracle

There were also some bug fixes and some enhancements in Code Editor and Trigger editor.

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.

Can you fix the bug in the following code?

Here is the code:

begin
FOR c_d
IN (SELECT *
FROM table_a
)
LOOP
c_d.id := NULL;

INSERT INTO table_a values (c_d);
END LOOP;
end;

this gives an ORA-00947: not enough values
in the line of "INSERT INTO table_a values (c_d);"

How to fix it?

How to kill the right SQL Navigator session

Hi

If you have several SQL Navigator Sessions and want to kill one of them due to something (normally SQL Navigator hanged or is doing something and will not abort) try this:
1- open Quest SQL Tracker
2- select all the SQL Navigator processes
3- check which session is not the ones you want to maintain (for that you could, for instance, make a 'select 1 from dual' )
4- check the PID....and using windows's task manager kill the session with that PID (maybe you need to include that column in the task list)

it was very helpful today...

YouTube monkeys / Macacos responsabilizados no Youtube

I got this message several times in youtube and today I want to share it :-)
Tendo obtido esta mensagem várias vezes no youtube, hoje apeteceu-me partilha-la :-)


"A team of highly trained monkeys has been dispatched to deal with this situation."
Uma equipa de macacos altamente treinados foi enviada para tratar desta situação.

Does that mean that "no one will be notified and no one will look to it?" and to where should I send the error report?
Será que isso significa "que ninguém foi avisado nem ninguém ira tentar resolver o problema"?

Well, this monkey will sleep now! good night!
Bem, este macaco vai dormir! Boa noite!

This post was wrote in English and in Portuguese, but it's not a literal translation!
Esta mensagem foi escrita em Inglês e Português, mas não foi efectuada uma tradução literal.

SQL Navigator 6.2.1 released

Some of the fixes included in 6.2.1 are:

# AV in table editor for object table
# Error "ORA-00900: invalid SQL statement: SQL Navigator could not parse/execute sql with open '(' after FROM.
# AV when editing and switching between script and results tab
# In data grid, Exporting large number of rows and when export finishes, SQL Nav closes.
# The focus is not on the currently running query
# Output doesn't get displayed if debug from the body tab
# Updateable mode doesn't work if column name is similar to a keyword (regression)
# Out of memory when query from table with large amount of columns (regression)
# Issue with Ldap using 11G client
# Debugger hang when input a decimal number in German Regional setting
# Invalid variant operation when open/extract ddl from external table (regression)
# Data corrupted when export from excel
# AV when editing a sql file (regression)
# Cannot access trigger in another schema in 9iDB (Regression)
# Dot lookup doesn't work for synonym of a table belong to a different schema (Regression)
# Reset Oracle password under Session main menu is broken in v6.2.

SQL Navigator 6.2 released

SQL Navigator 6.2 was released

Some new features:

• New Search feature for the Preferences window.
• Preference to format after extracting the ddl.
• Import/Export tables.
• Session browser to support RAC database.
• Revised layout to accommodate multiple code editor windows.
• Code Editor - Bug fixes and enhancements.
• Other General bug fixes and enhancements.

Quotes for today

"Measuring programming progress by lines of code is like measuring aircraft building progress by weight." - Bill Gates

"If debugging is the process of removing software bugs, then programming must be the process of putting them in."

"Remember that there is no code faster than no code."
-- Taligent's Guide to Designing Programs

"Computer Science is the only discipline in which we view adding a new wing to a building as being maintenance."
-- Jim Horning

Hacker consegue informação confidencial da Twitter

Fonte: http://apnews1.iwon.com/article/20090716/D99F79200.html

Um hacker usando o ponto mais velhinho de entrada (password de um empregado da Twitter) conseguir acesso a documentos internos da Twitter.

Com o uso de documentos online, usando serviços tipo os disponibilizados pelo Google (em vez de localizados em computadore internos à companhia), "basta" encontrar a password de gmail de um empregado para aceder aos docuemntos partilhados noutros serviços da google.

O elo mais fraco é a password...e um dos métodos é fazer-se passar por um gestor do sistema seja via telefónica ou por email.

Por isso repito o que digo sempre: "nunca diga a sua password por telefone ou envie por email, msn, etc".
Se por alguma razão, muito pouco provável, os serviços técnicos necessitarem dessa informação será sempre presencial e deverá ser pedido que seja você a introduzir a password que deve logo depois da intervenção ser alterada para uma outra completamente diferente.

Mantenham-se seguros!

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:

SqlNavigator site gives error

Last month and today again when I try to access to the SqlNavigator site (http://sqlnavigator.inside.quest.com/) I got an error page (I show below the error messages).

Last month after several days without being able to access I found out that I needed to clean the cookies I had for quest.com.
Quest people already knows about this problem.

---

HTTP Status 500 -

---

type Exception report

message

description The server encountered an internal error () that prevented it from fulfilling this request.

exception

javax.servlet.ServletException: java.lang.ArrayIndexOutOfBoundsException: 1
com.opensymphony.webwork.dispatcher.DispatcherUtils.serviceAction(DispatcherUtils.java:284)
com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:202)
com.jivesoftware.base.action.util.JiveFilterDispatcher.doFilter(JiveFilterDispatcher.java:54)
com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118)
com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52)
com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:88)
com.jivesoftware.base.PresenceFilter.doFilter(PresenceFilter.java:135)
com.quest.RedirectFilter.doFilter(RedirectFilter.java:50)
com.jivesoftware.util.SetRequestCharacterEncodingFilter.doFilter(SetRequestCharacterEncodingFilter.java:76)
com.jivesoftware.base.util.ApplicationInitializedFilter.doFilter(ApplicationInitializedFilter.java:73)

root cause

java.lang.ArrayIndexOutOfBoundsException: 1
com.quest.interceptor.QuestAuthInterceptor.questSsoCheck(QuestAuthInterceptor.java:58)
com.quest.interceptor.QuestAuthInterceptor.before(QuestAuthInterceptor.java:36)
com.quest.interceptor.QuestAuthInterceptor.intercept(QuestAuthInterceptor.java:26)
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
com.jivesoftware.forum.action.LocaleInterceptor.intercept(LocaleInterceptor.java:104)
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31)
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31)
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
com.opensymphony.webwork.interceptor.FileUploadInterceptor.intercept(FileUploadInterceptor.java:174)
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
com.jivesoftware.base.action.interceptor.JiveLoginInterceptor.intercept(JiveLoginInterceptor.java:42)
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31)
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31)
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31)
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
com.opensymphony.xwork.interceptor.I18nInterceptor.intercept(I18nInterceptor.java:151)
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31)
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
com.opensymphony.xwork.DefaultActionProxy.execute(DefaultActionProxy.java:116)
com.opensymphony.webwork.dispatcher.DispatcherUtils.serviceAction(DispatcherUtils.java:273)
com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:202)
com.jivesoftware.base.action.util.JiveFilterDispatcher.doFilter(JiveFilterDispatcher.java:54)
com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118)
com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52)
com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:88)
com.jivesoftware.base.PresenceFilter.doFilter(PresenceFilter.java:135)
com.quest.RedirectFilter.doFilter(RedirectFilter.java:50)
com.jivesoftware.util.SetRequestCharacterEncodingFilter.doFilter(SetRequestCharacterEncodingFilter.java:76)
com.jivesoftware.base.util.ApplicationInitializedFilter.doFilter(ApplicationInitializedFilter.java:73)

note The full stack trace of the root cause is available in the Apache Tomcat/6.0.16 logs.

---

Apache Tomcat/6.0.16

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

PL/Vision: new version needed?

I have a new goal. To try to put PL/Vision at a new stage: an 10g and 11g version.

I try to install it in my 10.2 version and I got a compilation error.
For now here are the changes I made in the code

Compilation error:
comment line 50 and 51 of PLVEXEC package specification
-- no_such_table EXCEPTION;
-- PRAGMA EXCEPTION_INIT (no_such_table, -942);

Unnecessary code:
comment line 162 of PLVEXEC package body
-- ELSIF code_in = -942 THEN RAISE PLVexc.no_such_table;
comment line 350, 351 of PLVEXEC package body
-- logit BOOLEAN := FALSE;
-- showit BOOLEAN;

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)