Developer 6.0/6I on AIX

[gregmacv]

Hi,

I am currenly testing some reports on an AIX 5l platform against a 10g database. The reports have been upgraded from Developer 2000 up to Developer 6i.

The problem is, when we move the reports over to AIX and execute them through runtime I am enountering an uncompile pl/sql error. I have traced the error back to the triggers contained in the reports. It seems that when a table owned by a different user is referenced in the trigger it needs to be qualified by the owner - this was never an issue with the older version of Developer and runtime. I have created synonyms for these tables, but this has not helped. Changing all of our reports to prefix the owner in all of the triggers in all of our reports would be a lot of work. Has anyone seen this before or have any ideas on how to get around it please let me know. Also, the data querys in these reports executes with no problems, even though the tables are owned by a different schema - it only seems to be the triggers which are giving me a problem.

Everyones help is greatly appreciated.

Thanks

Greg.

 

[BJCooperIT]

Have you insured that the schema you are using to run the reports has select privileges on those tables?

[sup]Beware of false knowledge; it is more dangerous than ignorance.[/sup][sup] ~George Bernard Shaw[/sup]
Consultant Developer/Analyst Oracle, Forms, Reports & PL/SQL (Windows)
My website: Emu Products Plus

 

[gregmacv]

Hi,

Ya, this user has select privs on all application tables. Like I said it worked in previous versions of Deveoper, but for some 6i seems to require that the table names be qualified in the trigger.

Thanks

 

[BJCooperIT]

Which schema did you use to create the synonyms? Are they public synonyms?

[sup]Beware of false knowledge; it is more dangerous than ignorance.[/sup][sup] ~George Bernard Shaw[/sup]
Consultant Developer/Analyst Oracle, Forms, Reports & PL/SQL (Windows)
My website: Emu Products Plus

 

[gregmacv]

Hi,

The synonyms have been created in the tables owners schema. They are public. I also tried to create a private synomym in the schema of the user who needs to access the tables to no avail.....


Thanks