ST04 SQL command line editor: no display of result window / parsing works

[Former Member]

Hi experts,

I use ST04 SQL command line editor for displaying i.e. a user in DB_USERS:

select * from dba_users

When I execute the query (button , menu) no result window is displayed .

If I only parse it it says: "Statement is accepted" . So somehow the execution results gets suppressed...

leads me to think it's not an authorization problem.

I use

SAP ECC 6.0

SAP Basis 700 (13)

Oracle 10.2.0.2.0

any ideas?

bye

yk

[markus_doehr2 · Accepted solution]

> If I only parse it it says: "Statement is accepted" . So somehow the execution results gets suppressed...

> leads me to think it's not an authorization problem.

> SAP Basis 700 (13)

With SP12 the old transactions are replaced by DBACOCKPIT.

Since your SP is pretty old I suggest you check

Note 1028624 - Overview of DBA Cockpit for Oracle

and apply all the relevant notes for your SP (or upgrade to a higher BASIS SP which will be much more convenient).

Markus

[Former Member · Accepted solution]

Hi Marcus,

It may the old basis release. On a SAP BW with 700 (17) I had no problems with the SQL Command editor.

So I have to be patient until the Basis applies the patches...

bye

yk

[Former Member]

Can you check if hitting the F8 keyboard button works? If not, which release and basis support package do you use?

[Former Member]

Hi Martin,

F8 doesn't work either...

SAP Basis release 700 (level 13)

PI Basis Plugin 2006_1_700

bye

yk

[Former Member]

What about "select * from all_users"? Does this work?

[Former Member]

Hi Martin,

no, it doesn' - its every statement against the DICT wich gets parsed but not displayed. i think it's not the problem of missing privileges .

If I enter obviously a WRONG statement:

SELECT * from xall_users;

He throws the expected error "The following table does not exist: XALL_USERS

So the statement gets parsed but somehow the results (of a valid SQL) gets not displayed.

Howver, if I choose the menu "Display DB tables" and choose a DBA view I get a result window displayed. But since I have some own scripts written, this doesn't help me.

bye

yk

[Former Member]

What happens if you use report RSORADJV in transaction SE38 directly?

[Former Member]

Hi Martin,

I 'm not allowed tot use SE38 on production.

So it could be an authorization problem ? On the Dev. system (same base release 700 (13) it works either with RSORAJDV

or St04.

So I wonder if I can use ST04 SQL command editor on Production while I don't have the authorizations for RSORAJDV

(MONITORTOOLS auth. missing) . Does ST04 use RSORAJDV ? Tthan it is (quite) understandable.

What confuses me is that in ST04 it let's me enter the statement , parses it BUT does not execute it ...

nor gives back any message of missing privileges.

bye

yk

[Former Member]

It should not be a SE38 authorization problem.

Are you allowed to use transaction SA38? Then you could run the report with SA38...

[Former Member]

Hi Martin ,

SA38 is allowed but not executing RSORADJV... (sigh!):

it throws:

" no authorization to execute report RSORADJV from authorization group *! "

How come I can use ST04 but not the SQL command editor in St04 ? (or does St04 call RSORADJV in the back,

but gives no error message back ?).

At least I asked for authorization on ST04: I thought this includes the build-in SQL command editor, too ?

bye

yk

[Former Member]

Hi

have u check below note

Note 582427 - Error due to inconsistent Oracle DDIC - ST04,DB02

[Former Member]

Hi

checked the note but since I get no ORA-xxxx error it may not apply . Seems it would generate big trouble for the whole

installation if my problems are related to that note...

at least - I hope it will not...

bye

yk

[Former Member]

Hi,

Some information missing in st04 (AWR not working) and st03n in my Development server (patch 13).

Whn i upgrade 13 to 18 probelm resloved .

Surendra

[Former Member]

Hi,

yeah, I use a base release 700 (17) on a SAP BW system and never had the problems with ST04 , AWR or such.

It may that we have to upgrade the components - or at least to be patient until the Basis does it...

bye

yk