Re: Re-compiling oracle reports

Did you already try to change the REMOTE_DEPENDENCIES_MODE initialization parameter of the database to SIGNATURE instead of TIMESTAMP ? This can avoid a lot of unnecessary recompilations.
It can also be done via ALTER SYSTEM SET REMOTE_DEPENDENCIES_MODE = SIGNATURE or ALTER SESSION SET REMOTE_DEPENDENCIES_MODE= SIGNATURE.

(see also the Oracle7 Server Application Developer's Guide, Using Procedures and Packages, Timestamps and Signatures). Note : you need Oracle 7.3 or later.

Marc

john dear wrote in message <36AFC461.7B08576E_at_abc.def.com.au>...
>An issue we have run into with Reports is that each report needs to be
>re-compiled if database objects on which they depend are re-created. We
>have identified three situations in which this happens.
>
>1. DML statements such as "delete from table_name ... "
>If the table is later dropped and re-created the report will not run
>without recompilation.
>
>2. Cursor declarations such as "declare cursor c1 as select ... from
>table_name ..."
>If the table is later dropped and re-created the report will not run
>without recompilation.
>
>3. Stored procedures called from within the reports.
>If the stored procedure is re-compiled with "alter procedure
>procedure_name compile", the report will not run without recompilation.
>
>There could be more we have not encountered yet.
>
>Unfortunately, we have not been able to find a way of batch-compiling
>the reports. So it looks as if each report needs to be brought into
>orarep30m, and recompiled manually using point and click.
>
>Is there a way of batch-compiling reports? Alternatively, is there a way
>of telling runrep30m to compile "on the fly" at run time?
>
>We are using release 2.1 of Developer 2000 on SPARC with Reports 3.0 and
>Oracle 8.0.4.
>
>
Received on Fri Jan 29 1999 - 07:52:02 CET