Ora-04031 on running reports urgent
Hello All
we are getting above error while running oracle reports
would increasing size of shared_pool_size help in resolving the error
thanx
kedar
$>oerr ora 04031
04031, 00000, "unable to allocate %s bytes of shared memory (\"%s\",\"%s\",\"%s\",\"%s\")"
// *Cause: More shared memory is needed than was allocated in the shared
// pool.
// *Action: If the shared pool is out of memory, either use the
// dbms_shared_pool package to pin large packages,
// reduce your use of shared memory, or increase the amount of
// available shared memory by increasing the value of the
// INIT.ORA parameters "shared_pool_reserved_size" and
// "shared_pool_size".
// If the large pool is out of memory, increase the INIT.ORA
// parameter "large_pool_size".
What is the SGA_MAX_SIZE set at your env?? Also what is the output of show SGA??
Daljit Singh
Similar Messages
-
ORA-44356 when running report from Oracle Application Server 10g
All,
We have some reports that we developed using Reports Builder 10g. We use a few program units that run with every record that use the exec_sql package to run dynamic sql in a remote database. Everything runs fine when we test the reports in Reports Builder. After we compile the reports into the .rep format and place them on our Oracle Application Server 10g portal instance, we are running into the subject error when we try to run the report from the website. From the research that I've done, it seems that this error has to do with the use of exec_sql, but there is not too much info on the web regarding this error number. Running a trace when running the report in Reports Builder doesn't show any errors, and to further complicate things, this error only occurs on some reports...others that use the exec_sql package work fine.
Does anyone have any ideas as to why this might be happening?
Thanks for your help,
TomNothing is different between the reports in the exec_sql section. The strange part is that the reports will bomb out seemingly at random, at different times, and during the execution of different program units. I was able to find a work-around using DB Links, but I'd rather not use the DB Link if I can avoid it.
-
Report server run problem (urgent plz)
i am using developer9i, xp opereting system but i am not able to run report server . infact i dont know where report server reside and how configure report server. otn discussion forum gave me below instructions but i need step by step detail to run report server.
pls help me.
i want to see (Please reffer to Note:204538.1 on
Metalink ) but i could not access metalink.
registration does not alow me. i have no country on
country list and no Support Identifier (CSI, SAC,
Access Code etc.) . but i need access.
please help me. access with path
thanks
mostafizDear see this information this is metalink information
Note:204538.1
Subject: Common Reasons & Troubleshooting: "Unable to communicate with the Reports Server"
Type: BULLETIN
Status: PUBLISHED
Content Type: TEXT/X-HTML
Creation Date: 22-JUL-2002
Last Revision Date: 08-MAR-2005
PURPOSE
========
The main purpose of this document is to list the known causes of the "Unable to
communicate with the Reports Server" error. The terms Reports Server, CGI,
Reports Servlet are also described briefly for a better explanation of this error scenario.
This document includes the following sections :
I. Brief summary on the architecture of Reports Server, CGI and Reports
Servlet
II. Sources of errors encountered when running a report with Reports Server
III. How the CGI (or the Reports Servlet) communicates with the Reports
Server
IV. Possible reasons which lead to "Unable to communicate with the Reports
Server" error.
1) Reports Server is up and running
2) tnsnames.ora and sqlnet.ora problems
3) Effect of parameter "ORACLE_HOME"
4) Effect of parameter "maxconnect"
5) Passing very large parameters to reports server
6) A case specific to OAS 4.0.8.2
7) A case specific to WEBDB version 2.1.0.9.3
V. References
I. Brief summary on the architecture of Reports Server, CGI and Reports Servlet
=================================================================================
In order to understand the causes of the error "Unable to communicate with the
Reports Server", let's first briefly review the Reports Runtime Engines, Reports
Server, the Reports CGI, and Reports Servlet architecture.
There are 4 important layers in Reports Server architecture which should be
understood in order to clearly understand the error "Unable to communicate with
the Reports Server" :
1) The Runtime Engines : This is the main layer where the reports are actually
executed. On unix systems there are "rwrun60" and on NT systems there are
"rwrun60.exe" processes.
2) The Reports Server : The Reports Server recieves the job request and queues
it. When one of its runtime engines becomes available, it sends the
command line to that runtime engine for execution. On Unix systems it is
the "rwmts60" executable and on NT systems it is "rwmts60.exe".
3) The Reports CGI : The Reports Web CGI passes the request to the Reports Server.
The Reports CGI or Servlet converts the request to a command line that can be executed by the Reports Server and
submits it to the specified Reports Server. On Unix platforms this executable
is "rwcgi60" and on NTs it is "rwcgi60.exe.
4) The Reports Servlet : Its functionality and function is just the same as "Reports CGI", but it is
a program written in Java as difference to the CGI program (which is
written in C programming language).
The Reports Server may be running on the same server with the CGI program (or
servlet) OR may reside totally on another machine which does not necessarily have
the same Operating System. For instance CGI may reside in a Windows NT machine
while the Reports server may reside on a Unix box, or any other combination with
Unix-Linux-NT-2000, etc.
The reports are called with a URL similar to below with the CGI :
http://fully.qualified.server.name:PORT/dev60cgi/rwcgi60.exe?server=<REPSERVER>&other_parameters=...........
where fully.qualified.server.name is the name of the server where the Reports CGI
reside, and <REPSERVER> is the name of the server.
II. Sources of errors encountered when running a report with Reports Server
============================================================================
The Reports Web CGI (or the Reports Servlet) makes a call to the Reports Server
and asks it to place the output into some destination (defined by DESTYPE and
DESNAME parameters), then gives back the necessary response to the calling
program. For example if the DESTYPE is "cache", then the Reports server generates
the report to a file in a temporary place and gives it back to CGI and the CGI gives
it back to the calling program. Otherwise, if the DESTYPE is "file", the Reports Server
generates the report output to the requested file and the CGI replies back the
following message : "Report output was successfully written to requested
destination.".
If there is any error in this process, the related error message is returned. The
possible sources of errors can be categorized as follows :
1) The errors that are returned from Reports Server; like the Reports Server can
not find the requested RDF file or the report may be run to file and the
directory where the reports output is asked to be placed does not occur or
similar errors. (Usually the REP-XXXX errors)
2) Another possible cause of error is the errors returned by the RDBMS to the
Reports Server, for example a table not found error or things like that. Of
course from the CGI point of view these errors are again transmitted from the
Reports Server but in fact the error originates from the RDBMS. (Usually the
ORA-XXXX errors)
3) Another possible cause of errors is the CGI itself, for example when the CGI
executable can not connect to the requested Reports Server, then we get the
famous "Unable to communicate with the Reports Server". In this document we will
diagnose the common reasons of this last error.
III. How the CGI (or the Reports Servlet) communicates with the Reports Server
===============================================================================
Having said that "Oracle Reports Server CGI - Unable to communicate with the
Reports Server." error is returned back from the CGI itself, let's discuss the
issue of how the Reports CGI connect to the Reports Server. The name of the
Reports Server given in the URL with "server=....." parameter is, in fact, just
a special tnsnames alias, similar to aliases for database connect strings. As it is
important for the CGI to resolve the alias, the CGI needs to know the HOST name (or the
IP) of the machine where the Reports Server is running and the port on which the
Reports Server is listening. So a typical Reports Server alias is defined as follows :
REP60_<MACHINE>=(ADDRESS = (PROTOCOL = tcp)(HOST = <MACHINE>)(PORT = <PORT>))
This is defined in tnsnames.ora file, and the sqlnet.ora file is also used in
the name resolving operation.
IV. Possible reasons which lead to "Unable to communicate with the Reports Server" error.
==========================================================================================
The possible reasons for the "Unable to communicate with the Reports Server" error :
1) Reports Server is up and running :
Make sure that the Reports Server is really running on the specified server
and listening on the specified port. For details have a look at above
explanations for tnsnames alias of the reports server. And because of this the
CGI could not establish a connection to the Reports Server.
2) tnsnames.ora and sqlnet.ora problems :
As described above, the CGI resolves the details for the reports server using
the "tnsnames.ora" and "sqlnet.ora" files. There may be a problem with them,
here are the possible configuration problems :
a) There is no alias in the tnsnames.ora file for this Reports Server
b) The CGI looks into the wrong directory for the "tnsnames.ora" and "sqlnet.ora"
files. By default the CGI checks the $ORACLE_HOME/net80/admin directory for
these scripts, where the $ORACLE_HOME is the home of the Forms & Reports
installation. Please note that in a typical 9iAS 1.0.X installation there
are two ORACLE_HOME's, one is for the iAS and the other is for the tools,
usually the home for the tools is a directory with name "806" on NT and
"6iserver" on unix systems. By defining TNS_ADMIN in the environment, one
can override the search path for these two files.
The TNS_ADMIN variable can be defined in one of the following places :
i) In the environment : On MS Windows platforms check the "Settings
--> Control Panel --> System". On NTs check the environment TAB and in
Win2K systems check the "Environment Variables" button on Advanced tab.
ii) In "6iserver.conf" file. Details are as follows : The main configuration
file for Apache server is "httpd.conf" file which resides in
$IAS_HOME/Apache/Apache/conf directory. In this file there is a line to
include "oracle_apache.conf" and in this "oracle_apache.conf" file
there is a line to include "$ORACLE_HOME/conf/6iserver.conf" file. And
in this file the TNS_ADMIN variable could be defined as follows :
SetEnvIf Request_URI "rwcgi60" TNS_ADMIN=c:\orant\network\ADMIN
Please note that by defining it this way, the TNS_ADMIN will only be defined
for "rwcgi60" calls, so the other parts of the 9iAS will not be affected by
this setting.
c) In sqlnet.ora the "names.default_domain" is set but in tnsnames.ora the
domain is not defined in the alias description. For example if the
"names.default_domain=world" is present and active in "sqlnet.ora" file
then in the "tnsnames.ora" the alias of the reports server should also have
the ".world" extension appended at the end. And another cause is of course
the vice versa for this. If there is no "names.default_domain" is defined
in the "sqlnet.ora" then the alias in "tnsnames.ora" should not have the
domain extension.
Another important point that should be checked is, if TNS_ADMIN is defined
as described above then the search path is as follows, first the directory
defined by TNS_ADMIN is searched, if the "tnsnames.ora" file is not found in
this directory then $ORACLE_HOME/net80/admin is checked. (And on unix systems
/var/opt/oracle is also checked). These directories are only checked if the file
is not present, so if the "tnsnames.ora" file is present in TNS_ADMIN directory
but the alias is not present, then the other directories are not checked at all.
Let us assume that the tnsnames.ora file is present in the TNS_ADMIN directory but
there is no "sqlnet.ora" files here, then the sqlnet.ora file is checked in
$ORACLE_HOME/net80/admin directory, which could cause the same problem if the
"names.default_domain" is defined in this file.
All the above will result in, CGI to unable to resolve the alias in tnsnames.ora
file so it will not be able to establish a connection to the Reports Server.
3) Wrong "ORACLE_HOME" setting :
Wrong ORACLE_HOME setting. This is usually the case for Reports Servlet,
because the environment settings are defined in "jserv.properties" file for the
servlets and the setting here will effect both the Reports Servlet and the
setting for Oracle JSP and other servlets. So the other servlets or Oracle JSP
may need to set ORACLE_HOME to home of HTTP server while the reports server needs
it to be set to the TOOLS_HOME directory. In this case the best alternative is
not to set ORACLE_HOME in this directory and leave it to registry or defined the
ORACLE_HOME in "6iserver.conf" file just like the TNS_ADMIN defined above. For
details please have a look at the following document :
Note 179609.1 "Getting an error Unable to communicate with the Reports Server
using RWSERVLET"
4) Effect of parameter "maxconnect" :
Another common case for this error is that the CGI request reaches the Reports Server but
the Reports Server refuses connection. The main cause for this case is, that the Reports Server
configuration parameter "maxconnect" is defined too low, there are long running reports on the
server or the server is too busy at that time. Usually a second try some
later time results in a successful connection. If this is the case, the end user
may think that the problem is occasional. For details on this case please
have a look at the following document :
Note 125265.1 "Unable to communicate with the Reports Server"
5) Passing very large parameters to reports server :
Another known reason for this error is, if you are passing large parameters
to the Reports Server which exceeds sqlnet transmission blocks then the request may
end up with this error. To test it try with small parameter values. If you hit
this case, the solution is to increase the SDU (Session data unit size) and the TDU
(Transport unit data size) parameters in tnsnames.ora file, for details please
have a look at the following document :
Note 197358.1 "Passing large parameters to Reports show up a Reports Server
error"
6) A case specific to OAS 4.0.8.2 :
If you are using OAS instead of iAS, and the error appeared after
upgrading to 4.0.8.2 then this is caused because the 4.0.8.2 is using RSF
(Required Support Files) version 8.1.6 and the Reports 6i is using 8.0.6 and the
two could not reside in the same ORACLE_HOME directory. So the solution for this
problem is to create a new batch file and use it from which the actual CGI
executable is called. For details please see the following document :
Note 116754.1 "After applying OAS 4.0.8.2 CGI and Cartridge cannot communicate
to report server"
7) A case specific to WEBDB version 2.1.0.9.3 :
Another known case for this error is with WEBDB version 2.1.0.9.3 or less.
If you are using these old versions of WEBDB as HTTP listener, please have a
look at the following document :
Note 95426.1 "URL Not Found When Calling Oracle Developer Report from WebDB Site"On Windows you can create a Report Services:
rwserver -install server=repserverYou have to choose different names for all servers, like your collegue cannot create a server with the same name. You can start/stop this Report server in Services (control panel). Configuration files can be found under $ORACLE_HOME/reports/conf
Martin -
Urgent help with memory issue (ORA-04031)
Hi Geeks,
Came Across this below error in alert log in of our databases. Interestingly this error only pops up while the database backup runs. Below are the memory parameters.
memory_max_target big integer 14G
memory_target big integer 13G
pga_aggregate_target big integer 0
sga_target big integer 0
shared_pool_reserved_size big integer 192M
shared_pool_size big integer 0
ORA-04031: unable to allocate 5792 bytes of shared memory
("shared pool","unknown object","sga heap(1,1)","ges resource ")
Errors in file /apps/opt/oracle/diag/asm/+asm/+ASM1/trace/+ASM1_lmd0_14123.trc
I have tried specifying a value to shared_pool_size but with no luck..!! Pls help. I am not sure how to resolve this.Hi, ORA-4031 in this case can be caused by unrestricted growth of the PGA, thus forcefully reducing the SGA.
We've had this in the past also.
The solution is in older versions to increase the shared_pool_size as you mentioned but with ASMM, this is no longer an option. You can however retrict the growth of the PGA by setting SGA_TARGET.
On our system this now looks like:
SQL> show parameter _target
NAME TYPE VALUE
db_flashback_retention_target integer 1440
memory_max_target big integer 10G
memory_target big integer 10G
pga_aggregate_target big integer 0
sga_target big integer 8GSee how we in fact set the max growth of the PGA to 2Gb ( 10Gb - 8Gb)
Try this and see if ot works for you also
Success!!
FJFranken -
after creating a button in form builder 9i i want to fire a tigger for execute the report which is built in report builder 9i but it is not executing and showing me these errors..
code behind tigger of button is
Declare
repid REPORT_OBJECT;
v_rep VARCHAR2(100);
rep_status VARCHAR2(20);
Begin
repid := FIND_REPORT_OBJECT( ' c:\rsoreport.rep ' );
or ( ' rsoreport.jsp ' );
or ( ' rsoreport ' );
v_rep := RUN_REPORT_OBJECT(repid);
End;
error = FRM-41219 : Cannot find the Report: invalid id; on Form
and on Status bar Run_Report_Object cannot be null.
i need to execute the report behind form button so if any one know the simple code for this or tell me my code mistake then i would be very thanfull to himYou need to post this in forms forum. But you can check this. It has example how to run report from forms.
http://www.oracle.com/technology/products/forms/pdf/frm9isrw9i.pdf -
Urgent: problem running reports in Oracle 10g application server
Hi all,
our problem is that we deployed a jsp report as Ear file in Oracle 10g application server in infrastructure node.deployment says successfull.when we try to run that report it says 401 unauthorised.while sending request we are passing the database username,password &sid is this correct or any configuration setting to be done to make it run.
one morething normal jsp works fine.when we run reports jsp it gives the above mentioned 401 error.hello,
when you deploy reports JSPs they still require the reports specific componentes (e.g. TLD file, classes, ...) etc be available. i doubt that's the case in your ear file.
thanks,
ph. -
Error when running reports: "File Server needs to be re-initialized"
Hi.
This error "File Server needs to be re-initialized" appears when our users try to run reports on 11.5.10. EBS.
There is also a message box that appears and reads:
"A error occurred while attempting to establish a conection to Application File Server. There may be a network configuration problem, or the TNS listener may not be running."
This is a problem in our test environment. We recently ran autoconfig on the test side.
I have checked Metalink and also wider google search.
Perhaps we have an issue with the tnsnames files? Well, I verified this and the tnsnames in production and test, and they are the same.
Perhaps a listener.ora file issue?
"The issue is caused by the variables APPLFSTT and APPLFSWD is not being set properly in the <8.0.6_ORACLE_HOME> listener.ora file. " (Note 263654.1)
I am trying to verify the meaning of the following (in listener):
( SID_DESC = ( SID_NAME = FNDFS )
( ORACLE_HOME = /oracli2/oracle/testora/8.0.6 )
,APPLFSTT=
TEST_BALANCE;TEST;PROD_806_BALANCE;TEST_FO;TEST_806_BALANCE;PROD_FO,APPLFSWD=/or
acli2/oracle/testappl/admin;/oracli2/oracle/testcomn/temp;/oracli2/oracle/testco
mn/html/oam/nonUix/launchMode/restricted' )
In the APPLFSTT entry, should there be any mention of "PROD" ? Shouldnt this all be changed to TEST?
Also, comparing this to the PROD listener, the order of APPLFSTT is different:
TEST: APPLFSTT=
TEST_BALANCE;TEST;PROD_806_BALANCE;TEST_FO;TEST_806_BALANCE
PROD:APPLFSTT=
PROD_806_BALANCE;PROD;PROD_BALANCE;PROD_FO,
I have made a copy of our listener in TEst, so I can edit the existing one. Trouble is, not sure if I even should try to edit it!
Any suggestions, much appreciated.
Oracle 9.2.0. AIX 5.2.
Notes covered in Metalink:
274177.1
303971.1
304568.1
263654.1Yes thanks for that. Metalink has informed me to do the same, basically.
But I am in the middle of a cloning, so I will finish that then run autoconfig once again.
I already ran Autoconfig on both source and target, so will do again once this process is over.
Cheers.
DA -
ERROR WHILE RUNNING REPORT THROUGH FORMS.....!
hi all,
ive designed one form in Forms 9i...I'm tryin to run report through a Push button .....report is running well in paper layout through report builder 9i...The problem I'm facing is dat when i pressed button it is giving me error initially as FRM-41214 cannot run report and after that FRM-40735 When button pressed unhandled exception ora-06502.....What could go wrong??... Ive started OC4J instance ....created report object in object nevigator as well and defined basic properties for diff.parameters HTMLCSS,CACHE..etc.,mentioned report path in complete i.e.c:\reports\genbill.rdf ...Can anybody help me out ??? Thnx.!
-----------------------CODE ON BUTTON----------------------------------
DECLARE
repid REPORT_OBJECT;
v_rep VARCHAR2(100);
rep_status VARCHAR2(20);
BEGIN
repid := FIND_REPORT_OBJECT('REPORT5');
v_rep := RUN_REPORT_OBJECT(repid);
rep_status := REPORT_OBJECT_STATUS(v_rep);
WHILE rep_status in ('RUNNING','OPENING_REPORT','ENQUEUED')
LOOP
rep_status := report_object_status(v_rep);
END LOOP;
IF rep_status = 'FINISHED' THEN
/*Display report in the browser*/
WEB.SHOW_DOCUMENT('<HOSTNAME>:8889/reports/rwservlet/getjobid'||
substr(v_rep,instr(v_rep,'_',-1)+1)||'?'||'server=myrepserver','_blank');
ELSE
message('Error when running report');
END IF;
PAUSE;
END;When a report terminates with an error, REPORT_OBJECT_STATUS returns the value "TERMINATED_WITH_ERROR", which is 21 bytes of data, but rep_status is defined as 20 bytes. The 6502 error is due to the data not fitting the variable.
I recommend wrapping the REPORT_OBJECT_STATUS function with a SUBSTR that limits the data returned to 20 bytes, which will ensure the results fit.
For example:
rep_status := SUBSTR(REPORT_OBJECT_STATUS(v_rep), 1, 20); -
Error ORA-04031 while executing a stored procedure from Pro C++ code
I am getting the error ORA-04031(Unable to allocate 4096 bytes of shared memory("Shared Pool",.....)) while trying to execute a stored procedure from my pro*C application. This happens only after a few hours since the application has been running. I am closing the cursor after every database call.
Does anyone know why it is happening and any possible solutions?
TIA
Srithaj.One thing that can be done is to flush the shared pool before starting the application.
alter system flush shared pool;
Another is to increase the shared pool size by setting the parameter shared_pool_size in init_sid.ora file.
null -
Re: BUG? APEX 4.0: ORA-20503 error editing report with 400+ columns
Hello Everyone.
I've run into something quite strange and am hoping you can help me.
I am using Apex 4.0.1 and Oracle version 10.2.0.5. I've created a "classical" report in which the underlying SQL is a very simple:
select * from pvtabThe Oracle table pvtab consists of 419 columns, all of which are varchar2(88) and number type. That's it.
When I run the report, al of the columns show up as expected.
However, when I go into the "Report Attributes" tab and click on one of the fields (any of them, it doesn't matter which one), I immediately get the following error:
ORA-20503: Current version of data in database has changed since user initiated update process. current checksum = "598CAA7B68746A66F4B99E1512C36DED" application checksum = "0"If if replace the "*" with a few actual column names, then I am able to access any of these columns without problem.
If I put back the "*", I then encounter this error again.
I have never seen this error with other SQL SELECT statements in which I use the "*" qualifier to retrieve all columns from the table.
And so, I am wondering if the error is caused because of the large number of columns (419) in my table.
I've seen this same error mentioned in connection with forms but never with a report.
So, is there some limit to the number of columns one can have in a "classic" or interactive report?
Any idea why I would be getting this error?
Here is the DDL for my table pvtab:
CREATE TABLE "PVTAB"
( "MICRO" VARCHAR2(4),
"PRIM" VARCHAR2(4),
"UNIT" NUMBER,
"SEC_REF_1" NUMBER,
"SECN_1" VARCHAR2(88),
"SEC_REF_2" NUMBER,
"SECN_2" VARCHAR2(88),
"SEC_REF_3" NUMBER,
"SECN_3" VARCHAR2(88),
"SEC_REF_4" NUMBER,
"SECN_4" VARCHAR2(88),
"SEC_REF_5" NUMBER,
"SECN_5" VARCHAR2(88),
"SEC_REF_6" NUMBER,
"SECN_6" VARCHAR2(88),
"SEC_REF_7" NUMBER,
"SECN_7" VARCHAR2(88),
"SEC_REF_8" NUMBER,
"SECN_8" VARCHAR2(88),
"SEC_REF_9" NUMBER,
"SECN_9" VARCHAR2(88),
"SEC_REF_10" NUMBER,
"SECN_10" VARCHAR2(88),
"SEC_REF_11" NUMBER,
"SECN_11" VARCHAR2(88),
"SEC_REF_12" NUMBER,
"SECN_12" VARCHAR2(88),
"SEC_REF_13" NUMBER,
"SECN_13" VARCHAR2(88),
"SEC_REF_14" NUMBER,
"SECN_14" VARCHAR2(88),
"SEC_REF_15" NUMBER,
"SECN_15" VARCHAR2(88),
"SEC_REF_16" NUMBER,
"SECN_16" VARCHAR2(88),
"SEC_REF_17" NUMBER,
"SECN_17" VARCHAR2(88),
"SEC_REF_18" NUMBER,
"SECN_18" VARCHAR2(88),
"SEC_REF_19" NUMBER,
"SECN_19" VARCHAR2(88),
"SEC_REF_20" NUMBER,
"SECN_20" VARCHAR2(88),
"SEC_REF_21" NUMBER,
"SECN_21" VARCHAR2(88),
"SEC_REF_22" NUMBER,
"SECN_22" VARCHAR2(88),
"SEC_REF_23" NUMBER,
"SECN_23" VARCHAR2(88),
"SEC_REF_24" NUMBER,
"SECN_24" VARCHAR2(88),
"SEC_REF_25" NUMBER,
"SECN_25" VARCHAR2(88),
"SEC_REF_26" NUMBER,
"SECN_26" VARCHAR2(88),
"SEC_REF_27" NUMBER,
"SECN_27" VARCHAR2(88),
"SEC_REF_28" NUMBER,
"SECN_28" VARCHAR2(88),
"SEC_REF_29" NUMBER,
"SECN_29" VARCHAR2(88),
"SEC_REF_30" NUMBER,
"SECN_30" VARCHAR2(88),
"SEC_REF_31" NUMBER,
"SECN_31" VARCHAR2(88),
"SEC_REF_32" NUMBER,
"SECN_32" VARCHAR2(88),
"SEC_REF_33" NUMBER,
"SECN_33" VARCHAR2(88),
"SEC_REF_34" NUMBER,
"SECN_34" VARCHAR2(88),
"SEC_REF_35" NUMBER,
"SECN_35" VARCHAR2(88),
"SEC_REF_36" NUMBER,
"SECN_36" VARCHAR2(88),
"SEC_REF_37" NUMBER,
"SECN_37" VARCHAR2(88),
"SEC_REF_38" NUMBER,
"SECN_38" VARCHAR2(88),
"SEC_REF_39" NUMBER,
"SECN_39" VARCHAR2(88),
"SEC_REF_40" NUMBER,
"SECN_40" VARCHAR2(88),
"SEC_REF_41" NUMBER,
"SECN_41" VARCHAR2(88),
"SEC_REF_42" NUMBER,
"SECN_42" VARCHAR2(88),
"SEC_REF_43" NUMBER,
"SECN_43" VARCHAR2(88),
"SEC_REF_44" NUMBER,
"SECN_44" VARCHAR2(88),
"SEC_REF_45" NUMBER,
"SECN_45" VARCHAR2(88),
"SEC_REF_46" NUMBER,
"SECN_46" VARCHAR2(88),
"SEC_REF_47" NUMBER,
"SECN_47" VARCHAR2(88),
"SEC_REF_48" NUMBER,
"SECN_48" VARCHAR2(88),
"SEC_REF_49" NUMBER,
"SECN_49" VARCHAR2(88),
"SEC_REF_50" NUMBER,
"SECN_50" VARCHAR2(88),
"SEC_REF_51" NUMBER,
"SECN_51" VARCHAR2(88),
"SEC_REF_52" NUMBER,
"SECN_52" VARCHAR2(88),
"SEC_REF_53" NUMBER,
"SECN_53" VARCHAR2(88),
"SEC_REF_54" NUMBER,
"SECN_54" VARCHAR2(88),
"SEC_REF_55" NUMBER,
"SECN_55" VARCHAR2(88),
"SEC_REF_56" NUMBER,
"SECN_56" VARCHAR2(88),
"SEC_REF_57" NUMBER,
"SECN_57" VARCHAR2(88),
"SEC_REF_58" NUMBER,
"SECN_58" VARCHAR2(88),
"SEC_REF_59" NUMBER,
"SECN_59" VARCHAR2(88),
"SEC_REF_60" NUMBER,
"SECN_60" VARCHAR2(88),
"SEC_REF_61" NUMBER,
"SECN_61" VARCHAR2(88),
"SEC_REF_62" NUMBER,
"SECN_62" VARCHAR2(88),
"SEC_REF_63" NUMBER,
"SECN_63" VARCHAR2(88),
"SEC_REF_64" NUMBER,
"SECN_64" VARCHAR2(88),
"SEC_REF_65" NUMBER,
"SECN_65" VARCHAR2(88),
"SEC_REF_66" NUMBER,
"SECN_66" VARCHAR2(88),
"SEC_REF_67" NUMBER,
"SECN_67" VARCHAR2(88),
"SEC_REF_68" NUMBER,
"SECN_68" VARCHAR2(88),
"SEC_REF_69" NUMBER,
"SECN_69" VARCHAR2(88),
"SEC_REF_70" NUMBER,
"SECN_70" VARCHAR2(88),
"SEC_REF_71" NUMBER,
"SECN_71" VARCHAR2(88),
"SEC_REF_72" NUMBER,
"SECN_72" VARCHAR2(88),
"SEC_REF_73" NUMBER,
"SECN_73" VARCHAR2(88),
"SEC_REF_74" NUMBER,
"SECN_74" VARCHAR2(88),
"SEC_REF_75" NUMBER,
"SECN_75" VARCHAR2(88),
"SEC_REF_76" NUMBER,
"SECN_76" VARCHAR2(88),
"SEC_REF_77" NUMBER,
"SECN_77" VARCHAR2(88),
"SEC_REF_78" NUMBER,
"SECN_78" VARCHAR2(88),
"SEC_REF_79" NUMBER,
"SECN_79" VARCHAR2(88),
"SEC_REF_80" NUMBER,
"SECN_80" VARCHAR2(88),
"SEC_REF_81" NUMBER,
"SECN_81" VARCHAR2(88),
"SEC_REF_82" NUMBER,
"SECN_82" VARCHAR2(88),
"SEC_REF_83" NUMBER,
"SECN_83" VARCHAR2(88),
"SEC_REF_84" NUMBER,
"SECN_84" VARCHAR2(88),
"SEC_REF_85" NUMBER,
"SECN_85" VARCHAR2(88),
"SEC_REF_86" NUMBER,
"SECN_86" VARCHAR2(88),
"SEC_REF_87" NUMBER,
"SECN_87" VARCHAR2(88),
"SEC_REF_88" NUMBER,
"SECN_88" VARCHAR2(88),
"SEC_REF_89" NUMBER,
"SECN_89" VARCHAR2(88),
"SEC_REF_90" NUMBER,
"SECN_90" VARCHAR2(88),
"SEC_REF_91" NUMBER,
"SECN_91" VARCHAR2(88),
"SEC_REF_92" NUMBER,
"SECN_92" VARCHAR2(88),
"SEC_REF_93" NUMBER,
"SECN_93" VARCHAR2(88),
"SEC_REF_94" NUMBER,
"SECN_94" VARCHAR2(88),
"SEC_REF_95" NUMBER,
"SECN_95" VARCHAR2(88),
"SEC_REF_96" NUMBER,
"SECN_96" VARCHAR2(88),
"SEC_REF_97" NUMBER,
"SECN_97" VARCHAR2(88),
"SEC_REF_98" NUMBER,
"SECN_98" VARCHAR2(88),
"SEC_REF_99" NUMBER,
"SECN_99" VARCHAR2(88),
"SEC_REF_100" NUMBER,
"SECN_100" VARCHAR2(88),
"SEC_REF_101" NUMBER,
"SECN_101" VARCHAR2(88),
"SEC_REF_102" NUMBER,
"SECN_102" VARCHAR2(88),
"SEC_REF_103" NUMBER,
"SECN_103" VARCHAR2(88),
"SEC_REF_104" NUMBER,
"SECN_104" VARCHAR2(88),
"SEC_REF_105" NUMBER,
"SECN_105" VARCHAR2(88),
"SEC_REF_106" NUMBER,
"SECN_106" VARCHAR2(88),
"SEC_REF_107" NUMBER,
"SECN_107" VARCHAR2(88),
"SEC_REF_108" NUMBER,
"SECN_108" VARCHAR2(88),
"SEC_REF_109" NUMBER,
"SECN_109" VARCHAR2(88),
"SEC_REF_110" NUMBER,
"SECN_110" VARCHAR2(88),
"SEC_REF_111" NUMBER,
"SECN_111" VARCHAR2(88),
"SEC_REF_112" NUMBER,
"SECN_112" VARCHAR2(88),
"SEC_REF_113" NUMBER,
"SECN_113" VARCHAR2(88),
"SEC_REF_114" NUMBER,
"SECN_114" VARCHAR2(88),
"SEC_REF_115" NUMBER,
"SECN_115" VARCHAR2(88),
"SEC_REF_116" NUMBER,
"SECN_116" VARCHAR2(88),
"SEC_REF_117" NUMBER,
"SECN_117" VARCHAR2(88),
"SEC_REF_118" NUMBER,
"SECN_118" VARCHAR2(88),
"SEC_REF_119" NUMBER,
"SECN_119" VARCHAR2(88),
"SEC_REF_120" NUMBER,
"SECN_120" VARCHAR2(88),
"SEC_REF_121" NUMBER,
"SECN_121" VARCHAR2(88),
"SEC_REF_122" NUMBER,
"SECN_122" VARCHAR2(88),
"SEC_REF_123" NUMBER,
"SECN_123" VARCHAR2(88),
"SEC_REF_124" NUMBER,
"SECN_124" VARCHAR2(88),
"SEC_REF_125" NUMBER,
"SECN_125" VARCHAR2(88),
"SEC_REF_126" NUMBER,
"SECN_126" VARCHAR2(88),
"SEC_REF_127" NUMBER,
"SECN_127" VARCHAR2(88),
"SEC_REF_128" NUMBER,
"SECN_128" VARCHAR2(88),
"SEC_REF_129" NUMBER,
"SECN_129" VARCHAR2(88),
"SEC_REF_130" NUMBER,
"SECN_130" VARCHAR2(88),
"SEC_REF_131" NUMBER,
"SECN_131" VARCHAR2(88),
"SEC_REF_132" NUMBER,
"SECN_132" VARCHAR2(88),
"SEC_REF_133" NUMBER,
"SECN_133" VARCHAR2(88),
"SEC_REF_134" NUMBER,
"SECN_134" VARCHAR2(88),
"SEC_REF_135" NUMBER,
"SECN_135" VARCHAR2(88),
"SEC_REF_136" NUMBER,
"SECN_136" VARCHAR2(88),
"SEC_REF_137" NUMBER,
"SECN_137" VARCHAR2(88),
"SEC_REF_138" NUMBER,
"SECN_138" VARCHAR2(88),
"SEC_REF_139" NUMBER,
"SECN_139" VARCHAR2(88),
"SEC_REF_140" NUMBER,
"SECN_140" VARCHAR2(88),
"SEC_REF_141" NUMBER,
"SECN_141" VARCHAR2(88),
"SEC_REF_142" NUMBER,
"SECN_142" VARCHAR2(88),
"SEC_REF_143" NUMBER,
"SECN_143" VARCHAR2(88),
"SEC_REF_144" NUMBER,
"SECN_144" VARCHAR2(88),
"SEC_REF_145" NUMBER,
"SECN_145" VARCHAR2(88),
"SEC_REF_146" NUMBER,
"SECN_146" VARCHAR2(88),
"SEC_REF_147" NUMBER,
"SECN_147" VARCHAR2(88),
"SEC_REF_148" NUMBER,
"SECN_148" VARCHAR2(88),
"SEC_REF_149" NUMBER,
"SECN_149" VARCHAR2(88),
"SEC_REF_150" NUMBER,
"SECN_150" VARCHAR2(88),
"SEC_REF_151" NUMBER,
"SECN_151" VARCHAR2(88),
"SEC_REF_152" NUMBER,
"SECN_152" VARCHAR2(88),
"SEC_REF_153" NUMBER,
"SECN_153" VARCHAR2(88),
"SEC_REF_154" NUMBER,
"SECN_154" VARCHAR2(88),
"SEC_REF_155" NUMBER,
"SECN_155" VARCHAR2(88),
"SEC_REF_156" NUMBER,
"SECN_156" VARCHAR2(88),
"SEC_REF_157" NUMBER,
"SECN_157" VARCHAR2(88),
"SEC_REF_158" NUMBER,
"SECN_158" VARCHAR2(88),
"SEC_REF_159" NUMBER,
"SECN_159" VARCHAR2(88),
"SEC_REF_160" NUMBER,
"SECN_160" VARCHAR2(88),
"SEC_REF_161" NUMBER,
"SECN_161" VARCHAR2(88),
"SEC_REF_162" NUMBER,
"SECN_162" VARCHAR2(88),
"SEC_REF_163" NUMBER,
"SECN_163" VARCHAR2(88),
"SEC_REF_164" NUMBER,
"SECN_164" VARCHAR2(88),
"SEC_REF_165" NUMBER,
"SECN_165" VARCHAR2(88),
"SEC_REF_166" NUMBER,
"SECN_166" VARCHAR2(88),
"SEC_REF_167" NUMBER,
"SECN_167" VARCHAR2(88),
"SEC_REF_168" NUMBER,
"SECN_168" VARCHAR2(88),
"SEC_REF_169" NUMBER,
"SECN_169" VARCHAR2(88),
"SEC_REF_170" NUMBER,
"SECN_170" VARCHAR2(88),
"SEC_REF_171" NUMBER,
"SECN_171" VARCHAR2(88),
"SEC_REF_172" NUMBER,
"SECN_172" VARCHAR2(88),
"SEC_REF_173" NUMBER,
"SECN_173" VARCHAR2(88),
"SEC_REF_174" NUMBER,
"SECN_174" VARCHAR2(88),
"SEC_REF_175" NUMBER,
"SECN_175" VARCHAR2(88),
"SEC_REF_176" NUMBER,
"SECN_176" VARCHAR2(88),
"SEC_REF_177" NUMBER,
"SECN_177" VARCHAR2(88),
"SEC_REF_178" NUMBER,
"SECN_178" VARCHAR2(88),
"SEC_REF_179" NUMBER,
"SECN_179" VARCHAR2(88),
"SEC_REF_180" NUMBER,
"SECN_180" VARCHAR2(88),
"SEC_REF_181" NUMBER,
"SECN_181" VARCHAR2(88),
"SEC_REF_182" NUMBER,
"SECN_182" VARCHAR2(88),
"SEC_REF_183" NUMBER,
"SECN_183" VARCHAR2(88),
"SEC_REF_184" NUMBER,
"SECN_184" VARCHAR2(88),
"SEC_REF_185" NUMBER,
"SECN_185" VARCHAR2(88),
"SEC_REF_186" NUMBER,
"SECN_186" VARCHAR2(88),
"SEC_REF_187" NUMBER,
"SECN_187" VARCHAR2(88),
"SEC_REF_188" NUMBER,
"SECN_188" VARCHAR2(88),
"SEC_REF_189" NUMBER,
"SECN_189" VARCHAR2(88),
"SEC_REF_190" NUMBER,
"SECN_190" VARCHAR2(88),
"SEC_REF_191" NUMBER,
"SECN_191" VARCHAR2(88),
"SEC_REF_192" NUMBER,
"SECN_192" VARCHAR2(88),
"SEC_REF_193" NUMBER,
"SECN_193" VARCHAR2(88),
"SEC_REF_194" NUMBER,
"SECN_194" VARCHAR2(88),
"SEC_REF_195" NUMBER,
"SECN_195" VARCHAR2(88),
"SEC_REF_196" NUMBER,
"SECN_196" VARCHAR2(88),
"SEC_REF_197" NUMBER,
"SECN_197" VARCHAR2(88),
"SEC_REF_198" NUMBER,
"SECN_198" VARCHAR2(88),
"SEC_REF_199" NUMBER,
"SECN_199" VARCHAR2(88),
"SEC_REF_200" NUMBER,
"SECN_200" VARCHAR2(88),
"SEC_REF_201" NUMBER,
"SECN_201" VARCHAR2(88),
"SEC_REF_202" NUMBER,
"SECN_202" VARCHAR2(88),
"SEC_REF_203" NUMBER,
"SECN_203" VARCHAR2(88),
"SEC_REF_204" NUMBER,
"SECN_204" VARCHAR2(88),
"SEC_REF_205" NUMBER,
"SECN_205" VARCHAR2(88),
"SEC_REF_206" NUMBER,
"SECN_206" VARCHAR2(88),
"SEC_REF_207" NUMBER,
"SECN_207" VARCHAR2(88),
"SEC_REF_208" NUMBER,
"SECN_208" VARCHAR2(88)
);Thank you for any help/advice.
Elie
Edited by: EEG on Jun 12, 2011 2:09 PMSo, is there some limit to the number of columns one can have in a "classic" or interactive report?Yes. See Oracle® Application Express Application Builder User's Guide Release 4.0, Appendix B: Oracle Application Express Limits.
Any idea why I would be getting this error?No, but I've replicated it in APEX 4.0.2.00.07 on 11.2.0.1.0 EE using a table of 420 <tt>varchar2(88)</tt> columns:
>
ORA-20503: Current version of data in database has changed since user initiated update process. current checksum = "50C9BDC0AA1AEF0EB272E9158B2117B4" application checksum = "0"
>
Happens whether using <tt>select *</tt> or including all column names in the query. (I know you don't want to type all the column names, but I'd never use <tt>select *</tt> in a production application: always use a proper column list. You can get one without typing by drag-and-drop of a table in most IDEs, or a query from <tt>user_tab_columns</tt>.)
I hit the problem at 274 columns. Such an arbitrary number leads me to think that the problem is not one of the number of columns per se, but is due to some other limit (possibly a 32K VARCHAR2/RAW buffer somewhere).
Workaround:
Updates to the report column attributes are actually being saved, and you can navigate them using the Page Definition tree view as described in Appendix B.
Getting More Help:
This is probably a bug. If you have a support agreement with Oracle raise an SR with Oracle Support.
Also:
<li>Search the forum using the "ORA-20503" code and other possible terms to see if there's anything relevant. I had a quick look but the only thread in this context recommended an upgrade on an Oracle 9 DB version that's not compatible with APEX 4.0.
<li>To get the attention of the Oracle APEX team or anyone else who may know more about this problem than we do, edit your original post and change the Subject to be more specific about the actual nature of the problem: <em>BUG? APEX 4.0: ORA-20503 error editing report with 400+ columns</em>, and include your database version/edition and the definition of the <tt>PVTAB</tt> table.
Finally:
Somebody's bound to ask, so we might as well get started:
<li>Why so many columns?
<li>What requirement is this trying to fulfil? -
File download dialog box -running report
I am calling one report from my Oracle 9i Developer Suite Application. When i call one report using 'delimited' format, the run runs okay opening in a new Internet Explorer(IE) instance. But, when i call another report, the File download dialog box -running report opens which asks whether u want to open the file or save it in your computer. I hope, my doubt is clear.Please help me in this as it is very urgent.
Regards.This is a duplicate post. Please followup on your previous posting.
What is the URL you specify? -
Hello All,
Context:
We have a financial closing system working in the BW 3.5 and Oracle 9.2.0.7.0.
We are working with more than 100 millions records in 3 days.
In general, the system uses the standard data marts and BPS processes (copy, distribution, etc).
Error:
We had a lot of ORA-04031 errors for all execution (ABAP Programs, Data Loads, BPS Executions), it stopped the environment.
We did the "stop/start" the server to solved the problem.
The basis team increase the parameter "shared_pool_size" = 3000M - We saw the SAP Note (690241) and which is more than enough.
We have fear about it, we think it is posible to occurs again.
This is a big impact for the business.
Have you got this error in the past?
Could you please help us.
Thanks a lot.
Daniel Souza
SAP BW, SEM and Portal Consultant.
São Paulo - Brazil
+55 11 99092151Hi Chandran,
We saw this note.
The basis team have been changed the KGHDSIDXCOUNT parameter ( 4 to 1).
I am not founding more causes for this problem in the note.
Is it posible to have problems if the DB_CACHE_SIZE parameter is very large? example 18000M?
The basis team reduces the value for 1700M, in the last shutdown.
How can I flush the memory automatically?
The basis team reported this error for us. "It is not posible to flush the memory, it is necessary to shutdown the server".
Is it posible for the oracle 9i manage the memory area (shared pool) automatically? Is it recommended? Have you got this experience?
We have seen two notes about it:
997889 --> "Increase the memory SGA the ocurrence of error ORA-04031 but it does not prevent it."
617416 --> "The following areas of the SGA can be changed dynamically with Oracle 9.2 if the SGA is configured dynamically: Buffer Cache, Shared Pool, Large Pool."
Thanks a lot.
Best regards,
Daniel Souza
São Paulo - Brazil -
When i run report through OC4J Application i get a exception message
When i run report through OC4J Application i get a exception message saying Server returning invalid xml and the exception number is JBO -29000. The Reports Server is installed on machine having IP 10.191.99.254.
Below is the exception message:
(oracle.jbo.JboException) JBO-29000: Unexpected exception caught: oracle.jbo.JboException, msg=JBO-29000: Unexpected exception caught: java.io.IOException, msg=Server returned HTTP response code: 500 for URL: http://10.191.99.254:8888/reports/rwservlet/showjobidnull
Anybody Please help me out with this issue.....because I am really fed up with this problem....want some urgent help.....
One possible workaround which I could make out is there needs change to be made in the .rdf files in Report Builder and then inside the User Parameters we change the Initial Value to * from % because the Reports Server encodes every value as %Initial_Value% and hence if the initial value for the parameter is % then it does not get a valid value and hence it returns as an invalid xml
But unfortunately it seems this workaround does not work.Please help as soon as possible.Hi,
you said that some changes were made in the .xml files but i had said that all the files present in Reports Developer or Reports Builder are .rdf files and I had made changes in the .rdf files for this articular report and then compiled it thereitself and then ran a paper layout of the report but the report did not comprise any data.
There was sufficient data also to populate the report. So this may not be a database issue. Please help if you can ASAP. -
Problems with running reports having parameters, on the web
Dear all,
I have recently installed Oracle 9iAS v1.0.2.2.1 on Suse linux 7.3. Also, installed
Forms and Reports 6i alongwith it.
Building and running reports both static and ones that accept parameters was a breeze.
I could also run reports from the web successfully until now when I am trying to run a
report that accepts parameters.
When I enter the following URL:
http://<webserver>/cgi-bin/rwcgi60?report=<some.rdf >userid=<user/passwd@db>
server=<reportservername>destype=cachedesformat=html+paramform=yes
This is what happens:
1. I am prompted for a parameter value in the html format
2. On entering a suitable value, I am prompted for information to connect to the
database viz. username, password and database name
3. Entering suitable values for the above results in a hung state. There is no output and
the busy signal is all that I get for a long long time.
4. Also, stopping this session results in other such sessions resulting in a hung state, too.
That is to say, if I had run a report throug the web successfully before trying this
one, after aborting this session, I cannot re-run the previous successful report. That
too results in a hung state. I have to restart the reports server rwmts60 once again
as well as the web server for things to work smoothly.
I tried recreating the cgi env and ran a strace on the rwcgi60 command. It produces
an error saying 'libzrc60.so.0: no such file or directory' where as it is very much
present in the default LD_LIBRARY_PATH. This could be misleading as I am not sure
how I correct I was in re-creating the CGI env.
This is a problem I face only when I enter the "paramform=yes" option in the URL.
Also, excuse me for my ignorance , but I have no idea how to interpret the cgicmd.dat file.
It does mention that %P, %PT, %PC are amongst the currently recognised special
parameters, though.
Will someone please help me out asap as this is quite urgent.
Thanks a million in advance
HemaHi Hema,
There could be various things that explain this, but from your symptoms it looks like the engine is hung processing this report. This could be as simple as a PL/SQL trigger that is in an infinite loop. Anyway, a simple thing to do is to add TRACEFILE=filename&TRACEMODE=append&TRACEOPTS=TRACE_ALL onto your URL. This will create the specified file and dump information into it about what Reports is doing as it is processing your report. If it is hung in an infinite loop, you should be able to see how far it got when you kill it.
Also, you can see the status of the reports job queue by using the http://.../rwcgi60?showjobs command. If the report is executing forever, you'll see it sitting there in the job queue.
regards,
Stewart -
Run Report from Oracle Forms9i
Hi how are u all.......i am shahzad and i have little problem....i am working on developer 6i with oracle 9i database..........now i upgrade into developer 9i.....now the problem is that when i call the report from form then error is generated that is like'you cannot use reun run_product here use run_report_object'
Any one plz tell me how to run report from forms 9i also how to pass parameter too...means check the parameter from forms and give me the reports
guys its urgent
Thanks in advance :)
Thanks youfot this u have to use standard code as follows
parameter list is as it was in 6i
v_report_id := FIND_REPORT_OBJECT('report name');
SET_REPORT_OBJECT_PROPERTY(v_report_id,REPORT_COMM_MODE, SYNCHRONOUS);
SET_REPORT_OBJECT_PROPERTY(v_report_id,REPORT_DESTYPE,file);
SET_REPORT_OBJECT_PROPERTY(v_report_id,REPORT_DESFORMAT,'dflt');
Set_Report_Object_Property(v_report_id,REPORT_OTHER,'ENVID="NFA"');
SET_REPORT_OBJECT_PROPERTY(v_report_id,REPORT_DESNAME,ls_file_path||'\'||to_char(sysdate,'dd')||
-- to_char(sysdate,'mm')||to_char(sysdate,'yyyy')||'.doc');
SET_REPORT_OBJECT_PROPERTY(v_report_id,REPORT_EXECUTION_MODE,RUNTIME);
SET_REPORT_OBJECT_PROPERTY(v_report_id,REPORT_OTHER, 'paramform=no');
SET_REPORT_OBJECT_PROPERTY(v_report_id,REPORT_SERVER,reportserver);
SET_REPORT_OBJECT_PROPERTY(v_report_id,REPORT_DESNAME,OUTFILE);
SET_REPORT_OBJECT_PROPERTY(v_report_id,REPORT_SERVER, reportserver);
SET_REPORT_OBJECT_PROPERTY(v_report_id,REPORT_OTHER, 'paramform=no');
vc_report_job_id:=RUN_REPORT_OBJECT(v_report_id,pl_id);
v_jobID := substr(vc_report_job_id,length(reportserver)+2,length(vc_report_job_id));
if vc_report_job_id is not null then
vc_rep_status := REPORT_OBJECT_STATUS(vc_report_job_id);
while vc_rep_status in ('RUNNING', 'OPENING_REPORT','ENQUEUED') LOOP
vc_rep_status := report_object_status( vc_report_job_id);
end loop;
IF vc_rep_status<>'FINISHED' THEN
message ('Report failed with error message '|| vc_rep_status);
END IF;
end if;
Maybe you are looking for
-
Why does my flashbuilder application not work in firefox, but does work in internet explorer?
I'm following the flex/facebook tutorial on adobe's site and when I run it in firefox nothing shows up, if i run it in internet explorer it shows the button... the tutorial I am working with is: http://www.adobe.com/devnet/facebook/articles/flex_fbg
-
does anyone think that apple will put video recording onto the iPhone ???
-
HT201269 itunes can't back up the iphone because an error occurred
itunes can't back up the iphone because an error occurred????????? HOW CAN I FIX THIS THANKS
-
Pro COBOL / Precompile and run with Micro Focus Server Express in Unix AIX
I have Oracle 11g R2 DB and client installed in Unix AIX machine. I would like to make a simple test pgm to : 1. the precompile using procob on the sample program 2. compile it through Micro Focus Server Express 3. run the sample This sample pgm will
-
Question mark in a finder window
Hi there, recently, I noticed a weird question mark on any finder window I open: any idea what it is? someone? Thanks a lot!!