Problem creating view through SQL Developer

#1

Hello,

I am working on 11.1.0.6.0, Oracle SQL Developer 1.0.0.15.

Yesterday I tried creating a new view through the Developer by (right
click on Views, Create View). This was not possible because the SQL
Parse returned "Unexpected tokens" though the query worked fine when
run in the sql worksheet and I could not find anything not normal. I
did not have a problem creating the view with "create view" directly,
either.

My question is: Is the parse error more a problem of the SQL Developer
or is it more likely that there is a problem in my query that should
be corrected because it might lead to problems later on.

Thanks a lot.

Best,

Hans

#2

On Mar 28, 5:03 am, Hans Mayr <mayr1... (AT) gmx (DOT) de> wrote:

Quote:

Hello,

I am working on 11.1.0.6.0, Oracle SQL Developer 1.0.0.15.

Yesterday I tried creating a new view through the Developer by (right
click on Views, Create View). This was not possible because the SQL
Parse returned "Unexpected tokens" though the query worked fine when
run in the sql worksheet and I could not find anything not normal. I
did not have a problem creating the view with "create view" directly,
either.

My question is: Is the parse error more a problem of the SQL Developer
or is it more likely that there is a problem in my query that should
be corrected because it might lead to problems later on.

Thanks a lot.

Best,

Hans

Without seeing the SQL we cannot answer this question. Well at least I
cannot.

Anybody here with remote viewing skills? 8^)

Ed

#3

On Mar 28, 5:03 am, Hans Mayr <mayr1... (AT) gmx (DOT) de> wrote:

Quote:

Hello,

I am working on 11.1.0.6.0, Oracle SQL Developer 1.0.0.15.

Yesterday I tried creating a new view through the Developer by (right
click on Views, Create View). This was not possible because the SQL
Parse returned "Unexpected tokens" though the query worked fine when
run in the sql worksheet and I could not find anything not normal. I
did not have a problem creating the view with "create view" directly,
either.

My question is: Is the parse error more a problem of the SQL Developer
or is it more likely that there is a problem in my query that should
be corrected because it might lead to problems later on.

Thanks a lot.

Best,

Hans

Without seeing the SQL we cannot answer this question. Well at least I
cannot.

Anybody here with remote viewing skills? 8^)

Ed

#4

On Mar 28, 5:03 am, Hans Mayr <mayr1... (AT) gmx (DOT) de> wrote:

Quote:

Hello,

I am working on 11.1.0.6.0, Oracle SQL Developer 1.0.0.15.

Yesterday I tried creating a new view through the Developer by (right
click on Views, Create View). This was not possible because the SQL
Parse returned "Unexpected tokens" though the query worked fine when
run in the sql worksheet and I could not find anything not normal. I
did not have a problem creating the view with "create view" directly,
either.

My question is: Is the parse error more a problem of the SQL Developer
or is it more likely that there is a problem in my query that should
be corrected because it might lead to problems later on.

Thanks a lot.

Best,

Hans

Without seeing the SQL we cannot answer this question. Well at least I
cannot.

Anybody here with remote viewing skills? 8^)

Ed

#5

On Mar 28, 5:03 am, Hans Mayr <mayr1... (AT) gmx (DOT) de> wrote:

Quote:

Hello,

I am working on 11.1.0.6.0, Oracle SQL Developer 1.0.0.15.

Yesterday I tried creating a new view through the Developer by (right
click on Views, Create View). This was not possible because the SQL
Parse returned "Unexpected tokens" though the query worked fine when
run in the sql worksheet and I could not find anything not normal. I
did not have a problem creating the view with "create view" directly,
either.

My question is: Is the parse error more a problem of the SQL Developer
or is it more likely that there is a problem in my query that should
be corrected because it might lead to problems later on.

Thanks a lot.

Best,

Hans

Without seeing the SQL we cannot answer this question. Well at least I
cannot.

Anybody here with remote viewing skills? 8^)

Ed

#6

Hello Ed,

Thanks, but this is a 400 line very internal analysis. I can not post
this. My question is if anyone knows these behavior of the SQL Parser
and if such errors messages are sometimes not reliable. If nobody can
answer this without seeing the code I will live with it till one day I
run into problems.

Have a nice weekend.

Hans

#7

Hello Ed,

Thanks, but this is a 400 line very internal analysis. I can not post
this. My question is if anyone knows these behavior of the SQL Parser
and if such errors messages are sometimes not reliable. If nobody can
answer this without seeing the code I will live with it till one day I
run into problems.

Have a nice weekend.

Hans

#8

Hello Ed,

Thanks, but this is a 400 line very internal analysis. I can not post
this. My question is if anyone knows these behavior of the SQL Parser
and if such errors messages are sometimes not reliable. If nobody can
answer this without seeing the code I will live with it till one day I
run into problems.

Have a nice weekend.

Hans

#9

Hello Ed,

Thanks, but this is a 400 line very internal analysis. I can not post
this. My question is if anyone knows these behavior of the SQL Parser
and if such errors messages are sometimes not reliable. If nobody can
answer this without seeing the code I will live with it till one day I
run into problems.

Have a nice weekend.

Hans

#10

On 28 mar, 10:03, Hans Mayr <mayr1... (AT) gmx (DOT) de> wrote:

Quote:

Hello,

I am working on 11.1.0.6.0, Oracle SQL Developer 1.0.0.15.

Yesterday I tried creating a new view through the Developer by (right
click on Views, Create View). This was not possible because the SQL
Parse returned "Unexpected tokens" though the query worked fine when
run in the sql worksheet and I could not find anything not normal. I
did not have a problem creating the view with "create view" directly,
either.

My question is: Is the parse error more a problem of the SQL Developer
or is it more likely that there is a problem in my query that should
be corrected because it might lead to problems later on.

Upgrade your ancient version of SQL Developer.
This kind of bugs was fixed a long time ago.