Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Face REP-1439 error while running Oracle Report v 2.5

Status
Not open for further replies.

BenjaminLim

IS-IT--Management
May 24, 2000
73
GB
Hi

The error message appears in report server log as follows:

REP-1439: Cannot compile program units since this is a runtime only report.

What I have tried :
1. First test my newly modified program using test database & the report runs successfully.

2. 2nd time run using same program but on live database & the above error occur.

The program is residing in my local drive & I am doing all the above testing on my PC.

Please advice what went wrong. Thanks.

Regards
Benjamin [sig][/sig]
 
For what it's worth, I found a reference on Metalink to bug 634177. It has similar symtoms: a report is created on one instance, a .REP file is created, and an attempt made to run the report on a different instance. This failed with a REP-1439.

The suggested solution is to use the .RDF file instead of the .REP file. There is also supposed to be a patch available - Developer/2000 r2.1 patch set.

The Metalink document is note 1012546.7.
 
If you have a stored procedure in the Report then you have to use the RDF file - that is the only time I know of using an RDF instead of a REP


Hope this helps
 
RJSHA1, this is not always the case. I have over 100 reports using stored procedure which have valid generated .rep files. Unfortunately this seems to be a random bug (I have just had my second occurance)
 
Try to check whether your stored procedures are the same on both servers and whether you use signature instead of timestamp.

But in general Karluk is right: this bug may have patch (both for server and reports).
And also it's better, though not necessary, to use RDF for reports calling stored procedures as well as pll instead of plx because a lot of Oracle products contain such remote dependancy bugs :)
 
I use the Srw.Do_Sql function to send my query to the server along with a user parameter defined previously, this may not be a good solution but it works fine for my needs.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top