Bug in TOAD 11

Guest · September 28, 2011, 3:50pm

Hi everyone,

In TOAD 11, windows XP, instant client 11.2.0.2

Schema browser, I select a table. On RHS, in the indexes tab, I do
“create index”, complete everything and hit “Show SQL”. I then copy the
SQL and cancle the operation. I go to the SQL editor and paste the
“create index” command.

I get “ORA-02158”: invalid create index option.

I execute the same “create index” in TOAD 10.6 and it works like a charm.

Yesterday, I got the same problem. Instead of going to 10.6, I just
retype the command and it worked.

Here is the create index:
CREATE INDEX DBAGEST.GSC_FORM_REQUETE_NUK1 ON DBAGEST.GSC_FORM_REQUETE
(NO_FORMULAIRE, NO_VERSION_FORM)
LOGGING
TABLESPACE AUTRES_IND
STORAGE (
INITIAL 512K
NEXT 512K
PCTINCREASE 0
BUFFER_POOL DEFAULT
)
NOPARALLEL
/

–
Louis Brouillette
Chargé de projet informatique et technologique (DBA)
Université du Québec à Trois-Rivières
Tel: (819) 376-5011 ext. 2435
Email: Louis.Brouillette@uqtr.ca

JohnDorlon · September 28, 2011, 4:51pm

Is the script shown below what the ‘create index’ dialog generated?
I just ran this sql and it worked fine for me (I changed object names of course
but left everything else along).

You mentioned what client you are using. What Oracle version are you using?

Guest · September 29, 2011, 8:10am

Oracle version is 10.2.0.5

It is what the ‘create index’ dialog generated. I also tried something else.
From TOAD (schema browser), I generated the script of an existing table, copied
the ‘create index’ part (one of the indexes), drop the index and I got the same
error when trying to run the create index. As I said, the same script works fine
with TOAD 10.6 (on the same database, same client).

Le 2011-09-28 17:51, John Dorlon a écrit :

Is the script shown below what the ‘create index’ dialog
generated? I just ran this sql and it worked fine for me (I changed object
names of course but left everything else along).

You mentioned what client you are using. What Oracle version are you using?

JohnDorlon · September 29, 2011, 8:26am

Hm. I just tried this on 10.2.0.1 (it’s the closest I have to 10.2.0.5)
and the statement below works OK there too. If you paste the statement in the
editor and run with F9, it should highlight the part of the statement that
causes the error. What part is getting highlighted?

Guest · September 29, 2011, 8:45am

Sorry, it now works. Yesterday and the day before, I did it repeatedly and it
never worked but now, everything seems fine. I’ll tell you if it happens
again. Thanks. Le 2011-09-29 09:26, John Dorlon a écrit : Hm. I just tried
this on 10.2.0.1 (it’s the closest I have to 10.2.0.5) and the
statement below works OK there too. If you paste the statement in the editor
and run with F9, it should highlight the part of the statement that causes
the error. What part is getting highlighted?

acip · September 30, 2011, 1:24am

Hi

If I copy/paste

CREATE TABLE TABLE_XMLBINARY OF XMLType

XMLTYPE store AS BINARY XML;

to the TOAD v11 editor and run with F9, the keyword BINARY is highlighted

Regards!

On 29.9.2011 15:26, John Dorlon wrote:

Hm. I just tried this on 10.2.0.1 (it’s the closest I have to
10.2.0.5) and the statement below works OK there too.

If you paste the statement in the editor and run with F9, it should
highlight the part of the statement that causes the error. What part is
getting highlighted?

–

Aci Polajnar
IT svetovalec – IT consultant
acip.vcf (328 Bytes)

JohnDorlon · September 30, 2011, 8:14am

Binary XML Storage requires Oracle 11. So if you are still using that 10.2.0.5
database, that is why.

acip · October 3, 2011, 2:23am

SEE ATTACHMENT

acip · October 3, 2011, 2:23am

SEE ATTACHMENT

acip · October 3, 2011, 2:23am

SEE ATTACHMENT

acip · October 3, 2011, 2:23am

SEE ATTACHMENT

acip · October 3, 2011, 2:23am

SEE ATTACHMENT
acip.vcf (328 Bytes)

acip · October 3, 2011, 2:23am

SEE ATTACHMENT

JohnDorlon · October 3, 2011, 8:19am

Hi Aci,