DBIF_DSQL2_OBJ_UNKNOWN on RSORAVDZ

[Former Member]

Hi, I'm having ST22 dump DBIF_DSQL2_OBJ_UNKNOW on with program RSORAVDZ

I am trying to apply note

1734833 - DBIF_DSQL2_OBJ Unknown RSORAVDZ

without much success, this is was happened after trying on a QAS system:

I tried to drop, create/recreate as refered note. I don't know if i should create with SAPSR3 or SYSTEM. Also I am probably doing something wrong, but I don't really know what (i do not understand much of these synonym things.

Any help on interpreting the note, or helping with the queries is welcome.

Thanks

[Former Member · Accepted solution]

SAP Note 1734833 is not quite clear.

You have to execute the SQL statements neither as SYSTEM nor as SAPSR3, but as SYS.

To do so, call sqlplus like this:

sqlplus / as sysdba

hope this helps

[Former Member]

Hello. I didn't forget about you guys

I think my problem had something to do with the user I was using. I deleted everything and recreated as Josef Bodenschatz stated, and the problem was solved (not at the first try though).

All checks of SAP Note 1734833 are OK now, and no more dump.

Thanks

[former_member188883]

Hi Pedro,

Please have a look into below SAP notes

582427 - Error due to inconsistent Oracle DDIC

1365632 - DBACockpit: SQL command editor: DBIF_DSQL2_OBJ_UNKNOWN

Regards,

Deepak Kori

[divyanshu_srivastava3]

Hi Pedro,

In which system are you getting this error. I believe it's production because of program involved which should be because of active EWA setting on production.

Better would be you apply suggested patches from DEV - QAS and PRD or you may have to use workarounds given in note in production.

And yes, how are trying to implement this note ?

Regards,

Divyanshu

[Former Member]

Hello Divyanshu, and thanks for your quick reply.

I'm having the problem in DEV, QAS and PRD systems. We have configured EWA for all systems (and don't know if EWA has anything to do with the problem).

I'm trying to apply the workaround described in SAP Note 1734833, because it fits our problem.

I tried SQL statements, with both SYSTEM and SAPSR3:

drop public synonym gv$session_fix_control;

create or replace public synonym gv$session_fix_control for gv_$session_fix_control;

drop public synonym gv$system_fix_control;

create or replace public synonym gv$system_fix_control for gv_$system_fix_control;

[divyanshu_srivastava3]

Hi Pedro,

Have a look at this thread. Similar issues :

Meanwhile, I will check for other possibilities

Regards,

Divyanshu

[ACE-SAP]

Hello

After re-creating the synonyms are you able, when connected as sapsr3, to issue a

select * from gv$session_fix_control;

Regards

[Former Member]

Hello Kervadec

Nope.. the select ends with error... I tried dropping/recreating with SYSTEM or SAPSR3, but the confirmation query does not end successful.

Creating with SYSTEM (and checking with SAPSR3):

Creating and checking with SAPSR3:

[ACE-SAP]

Hi

This is strange...

At least you can, when logged as sysdba (SYS) create a synonym just for the SAP user.

create synonym sapsr3.gv$session_fix_control for gv_$session_fix_control;

You could also try running sapconn_role.sql script from exe dir of your SAP system.

(134592 - Importing the SAPDBA role (sapdba_role.sql) )

Regards