Regapp.sql parameters

I am trying to register APEX as a partner application using regapp.sql command. Where on the AS would I find the values for the following parameters?
p_site_token
p_site_id
p_login_url
p_encryption_key
Thanks

sch5479,
Have a look at the following link -
http://www.oracle.com/technology/products/database/application_express/howtos/sso_partner_app.html
It describes exactly how to setup an Apex application as a partner Application with Oracle SSO

Similar Messages

APEX SSO - execution of regapp.sql failing

Hi All,
I have Database 11.1.0.6.0. APEX version is 3.0.1
I am trying to Configure SSO(single sign-on) with Apex.
I am logged in as FLOWS_030100 into the database
I am facing following issues when trying to execute the regapp.sql, which is extracted from ssosdk902.zip. I got this zip from 10.1.2.0.1 Oracle App Server and trying to use it for configuration for version 10.1.3.1
1. It fails with following error.
Partner Application Configuration
ERROR: Error in registration. Please try again
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
PL/SQL procedure successfully completed.
Commit complete.
I figured out it was complaining for the l_ip_check varchar2(1); size, I increased that but then I got the following message:
Partner Application Configuration
ERROR: Error in registration. Please try again
User-Defined Exception
PL/SQL procedure successfully completed.
Commit complete.
No errors.
I am wondering why is it not prompting for the values. Is there some change I should be doing to the regapp.sql to get it working for 11g DataBase.
Please reply.
Thanks
Pooja
Edited by: user539270 on Mar 19, 2009 11:57 PM

Hi Scott
Thanks for the reply!
I got the script working without any change when executed from SQL Developer.
How ever I am facing issue after getting the APEX configured with Oracle SSO. I have opened another thread with the details.
(Facing Issues: APEX Configuration with SSO
Please have a look.
Regards
Pooja

SQL-Parameters in BC4J?

Hi
For performance and security reasons it is usually better to use SQL-Parameters (like :1) in SQL-Queries instead of building the SQL-String directly. I'd like to adopt this best practice but stumbled over a problem: BC4J adds Parameters when applying View-Links. Unfortunately I've no control over the Parameter added. See the following example:
Assume you have a View-Object with the following Query:
select NAME from USERS where NAME like :1
:1 is my custom parameter which I'd like to set using method 'setWhereClauseParams'. This view works fine until this view is used as a detail of a view link. In this case BC4J adds his own SQL-Parameter so that the query looks like that:
select NAME from USERS where NAME like :1 and (users.USR_ID = :1)
where the first :1 is my own Parameter and the second :1 is added by BC4J as part of the view link. This certainly does not work.
Can anyone give me a hint how to use SQL-Parameters correctly in BC4J-Views? Is there a "How To"-Document or something like that which explain how to use SQL-Parameters in BC4J?
Any hints are appreciated
Thanks
Frank Brandstetter

This way framework automatically adds the new where clause to the existing one, thus eliminating your issueDoes it? I'm not sure! I just tried it out the following example:
Master ViewObject: GroupsView
Detail ViewObject: UsersView (ViewLink to GroupsView)
GroupsViewImpl GrpVo = getGroupsView();
GrpVo.first();
UsersViewImpl UsrVo = getUsersView();
UsrVo.setWhereClause("NAME like :1");
System.out.println("Query=" + UsrVo.getQuery());This code prints:Query=SELECT Users.USR_ID,Users.GRP_ID,Users.NAME FROM USERS Users WHERE (NAME like :1) AND Users.GRP_ID = :1This does not look as if my issue is solved... :(

Logging SQL parameters in Database Adapter??

Hi there!!
We'd like to be able to log all the parameters that are used in a SQL operation in Database Adapters. So far, we've been able to log the query with '?' instead of the real parameters. For example: select t.* from tsupcontact t WHERE t.idsupplier = ? AND t.idproject IS NULL AND (t.iduser = ? OR ? IS NULL)
But we need to be able to see the actual parameters that are passed to the query (we're having some trouble with the database adapters and we need to see what's really going on the database).
Any ideas? Thanks in advance!!

You need to edit the the aslbdebug.xml file in ./user_projects/domains/<your domain>. Then go into the weblogic console and change the levels to debug. You will get lots of debugging. Below are the settings in my file.
<java:sb-debug-logger xmlns:java="java:com.bea.wli.debug">
<java:alsb-stages-transform-runtime-debug>true</java:alsb-stages-transform-runtime-debug>
<java:alsb-alert-manager-debug>false</java:alsb-alert-manager-debug>
<java:alsb-credential-debug>false</java:alsb-credential-debug>
<java:alsb-jms-reporting-provider-debug>false</java:alsb-jms-reporting-provider-debug>
<java:alsb-management-credential-debug>false</java:alsb-management-credential-debug>
<java:alsb-management-dashboard-debug>false</java:alsb-management-dashboard-debug>
<java:alsb-management-debug>false</java:alsb-management-debug>
<java:alsb-management-user-mgt-debug>false</java:alsb-management-user-mgt-debug>
<java:alsb-module-debug>true</java:alsb-module-debug>
<java:alsb-monitoring-aggregator-debug>false</java:alsb-monitoring-aggregator-debug>
<java:alsb-monitoring-debug>false</java:alsb-monitoring-debug>
<java:alsb-pipeline-debug>true</java:alsb-pipeline-debug>
<java:alsb-security-wss-debug>false</java:alsb-security-wss-debug>
<java:alsb-service-account-manager-debug>false</java:alsb-service-account-manager-debug>
<java:alsb-service-provider-manager-debug>false</java:alsb-service-provider-manager-debug>
<java:alsb-service-repository-debug>false</java:alsb-service-repository-debug>
<java:alsb-service-security-manager-debug>false</java:alsb-service-security-manager-debug>
<java:alsb-service-validation-debug>false</java:alsb-service-validation-debug>
<java:alsb-test-console-debug>true</java:alsb-test-console-debug>
<java:alsb-transports-debug>true</java:alsb-transports-debug>
<java:alsb-uddi-debug>true</java:alsb-uddi-debug>
<java:alsb-wsdl-repository-debug>false</java:alsb-wsdl-repository-debug>
<java:alsb-wspolicy-repository-debug>false</java:alsb-wspolicy-repository-debug>
<java:alsb-security-encryption-debug>false</java:alsb-security-encryption-debug>
<java:alsb-security-module-debug>false</java:alsb-security-module-debug>
<java:alsb-sources-debug>false</java:alsb-sources-debug>
<java:alsb-custom-resource-debug>true</java:alsb-custom-resource-debug>
<java:alsb-mqconnection-debug>false</java:alsb-mqconnection-debug>
<java:alsb-throttling-debug>false</java:alsb-throttling-debug>
<java:alsb-flow-resource-debug>false</java:alsb-flow-resource-debug>
<java:alsb-flow-transport-debug>false</java:alsb-flow-transport-debug>
<java:alsb-flow-deployment-debug>false</java:alsb-flow-deployment-debug>
<java:alsb-debugger-debug>true</java:alsb-debugger-debug>
</java:sb-debug-logger>

Passing SQL-Parameters to Oracle-Reports from java

hello,
i want to write an application in the following way:
on a java-frontend an user can select values for different
parameters. these values should be to transferred to the sql-
query of the reports rdf file. what is the syntax of an
parameter passed from java to oracle reports.
does this work with runtime.exec()... ?
does anybody have an example.
any help would be very appreciated.
greetings
Thorsten Lorenz

In order to pass the parameters to report rdf, you can create user parameters in the oracle report builder, hook up the parameters with query. For example, you can create user parameter P_DEPTNO, then create a sql query: select * from dept where deptno = :P_DEPTNO. When you run this report, you give P_DEPTNO=10 as parameter, the rdf will generate report that only prints out department 10's information.
Once you have this kind of report created, you have several ways to achieve what you want.
1. use rwrun60. In your java program, you can invoke rwrun60 via runtime.exec(cmd) where cmd = rwrun60 report=dept.rdf userid=scott/tiger@orcl destype=file desformat=pdf desname=dept.pdf p_deptno=<value_from_java_app>
2. similarly, use rwcli60. the cmd would be:
cmd = rwcli60 server=repserver report=dept.rdf userid=scott/tiger@orcl destype=file desformat=pdf desname=dept.pdf p_deptno=<value_from_java_app>
3. use rwcgi60. Instead of using runtime.exec, you should use java URL object to run the report in the web environment.
option 2 & 3 takes advantage of powerful functionality of reports server, and it is much more scale than option 1.

SQL Parameters: Add vs. AddWithValue

I'm in the process of designing an application (Visual C# 2012) that will be working with a SQL database, and have been using parameters in my queries.
My question is if there is any advantages/disadvantages to using AddWithValue over Adding the paramater and then specifying the value and type in a separate instruction (in the C# code)?
I've read a few places that sometimes with AddWithValue, either the .Net framework or SQL doesn't always select the appropriate datatype for the parameter and can cause errors. But on the other hand, using AddWithValue can reduce the number of lines
of code you have to write (some of my queries might have 10+ parameters, which is small compared to a database for a multi-site Enterprise database system) and thus make your code faster (hopefully).
Opinions as to whether to use Add + extra statements, or just use AddWithValue?

that sometimes with AddWithValue, either the .Net framework or SQL doesn't always select the appropriate datatype for the parameter and can cause errors.
It's the other way round, see
SqlParameterCollection.AddWithValue
Method => Remarks:
"AddWithValuereplaces the
SqlParameterCollection.Add method
that takes a String and an
Object. The overload of
Add that takes a string and an object was deprecated because of possible ambiguity with the
SqlParameterCollection.Add overload that takes a
String and a
SqlDbType enumeration value where passing an integer with the string could be interpreted as being either the parameter value or the corresponding
SqlDbType value. Use
AddWithValue whenever you want to add a parameter by specifying its name and value."
Olaf Helper
[ Blog] [ Xing] [ MVP]

Log the SQL parameters used by ORM

Hi Everyone,
I have read Rupesh's blog post;
http://www.rupeshk.org/blog/index.php/2009/07/coldfusion-orm-how-to-log-sql/
and have appropriately changed the log4j setting
### Also log the parameter binding to the prepared statements.
log4j.logger.org.hibernate.type=DEBUG
But I still do not see the values of query parameters in my log files.
All I get is the auestion marks;
09/15 12:35:57 [ajp-bio-8014-exec-3] HIBERNATE DEBUG -
    insert
    into
        audit_log
        (description, created, userID)
    values
Does anyone have any ideas? And as always - thanks in advance!
Gavin.
Message was edited by: GavinBaumanis

Easy but you need to extract it from Microsoft Generic Report Pack.
So.. the procedure is as follows:
1) You export and unseal Management Pack from your SCOM using
Boris's OpsgMgr tools (MPViewer
2.3.3)
2) Ok you've got unsealed xml, now the tricky part, use
MpElementsExtract tool, example of usage:
MPElementsExtract.exe <MP.xml> /ex /destination:<destination>
That you way you get several folders out of mp:
DWScripts, DWSubScripts, LinkedReports, ReportResources, Reports
Take a look into content of first 2, there will be pure sql scripts, and rdl's are in Reports folder :)
Other way is to just use SQL profiler and catch SQL query while generating report.
--- Jeff (Netwrix)

PL/SQL Parameterized Exceptions?

I develop on the Oracle EBS platform and so I have to develop using multiple general purpose programming languages. Mainly PL/SQL and Java but we also use Ruby and Korn Shell for example. One thing I have trouble with in PL/SQL is exception handling. I would really like to be able to provide additional information in an Exception in PL/SQL but don't know how to do so. One way would be to define an exception with parameters. Thus providing some slots to stick information into when raising an exception and then using the information when the exception is caught. I've used raise_application_error that provides slots for a number and text but that's not really my idea of a good solution to this issue. I like the Ruby Exception object approach myself that allows you to define the slots yourself via sub-classing an Exception class. I've used OO PL/SQL successfully in certain solutions and I know it works but there are some serious shortcomings that make OO PL/SQL a bit of a no-mans land in my opinion so I think an Exception class in PL/SQL is probably not the way to go at this point but I could be wrong. So I thought how about defining exceptions with parameters much like a procedure or function. Is this coming or are there ways to provide additional information in an exception that you have used successfully?
Thank you

I got an error when I compiled your procedure
SQL> create or replace procedure myexception (v number) is
2    v1   emp.empno%type;
3    begin
4    select empno into v1 from emp where empno=v;
5    exception when no_data_found then
6    dbms_output.put_line('No data found');
7    Do first thing----
8    when too_many_rows then
9    dbms_output.put_line('Too many rows');
10    Do second thing----
11    when others then
12    --Do third thing
13    end;
14    .
15   /
Warning: Procedure created with compilation errors.
SQL> sho err
Errors for PROCEDURE MYEXCEPTION:
LINE/COL ERROR
13/3     PLS-00103: Encountered the symbol "END" when expecting one of the
         following:
         begin case declare exit for goto if loop mod null pragma
         raise return select update while with <an identifier>
         <a double-quoted delimited-identifier> <a bind variable> <<
         close current delete fetch lock insert open rollback
         savepoint set sql execute commit forall merge pipe
SQL> create or replace procedure myexception (v number) is
2    v1   emp.empno%type;
3 begin
4    select empno into v1 from emp where empno=v;
5 exception when no_data_found then
6    dbms_output.put_line('No data found');
7    Do first thing----
8 when too_many_rows then
9    dbms_output.put_line('Too many rows');
10    Do second thing----
11 when others then
12    --Do third thing
13 dbms_output.put_line(SQLERRM);
14 end;
15 /
Procedure created.
SQL>

Input Elements & PL/SQL Parameters

I have a FORM open/close HTML block on top...then below the block I have inputs...***THOSE INPUTS ARE NOT TO BE TARGETED TO PARAMETERS ***
How can one prevent those input from being intepreted as parameter entries W/O removing the name attribute ?
Thanks
<form ACTION="wict.accept" METHOD="POST" name="ct_flow" id="CTFlowForm">
blah..blah...
</form>
<input name="day" type="checkbox" checked="checked" onclick="return false">Daily
<input name="week" type="checkbox" onclick="return false">Weekly

Dear "50122",
You may have landed in the wrong forum. If your question is actually about the Oracle HTML DB product, please provide a clear question related to HTML DB and we'll try to help.
-Scott
P.S. If you like, you can show your name in this forum instead of a numeric ID by clicking on 'Forum Settings' and setting 'Name visible to others' to Yes.

SSO regapp registration with multiple net names

Hello!
I succesfully configured my apex engine to work with SSO authentication.
I used in regapp.sql
l_listener_token := 'HTML_DB:myhostname.mydomanin.com:7777';
and now the home page link works fine:
http://myhostname.mydomanin.com:7777/pls/htmldb/f?p=504:1
The problem is that I have some other network names (aliases) for the same IP (10.10.10.10) and I want these links to be functional as well:
http://myhostname2.mydomanin2.com:7777/pls/htmldb/f?p=504:1
http://10.10.10.10:7777/pls/htmldb/f?p=504:1
But when using them I get this error:
Error in portal_sso_redirect: missing application registration information:
p_partner_app_name:g_listener_token:HTML_DB:myhostname2.mydomanin2.com:7777
Please register this application as described in the installation guide
I tried to reuse the tokens I have for myhostname.mydomanin.com and register again regapp.sql with:
l_listener_token := 'HTML_DB:myhostname2.mydomanin2.com:7777';
But this violates unique constraint WWSEC_SECI_UK1 on WWSEC_ENABLER_CONFIG_INFO$.SITE_TOKEN column.
Question:
Is there a way to make functional the alternate links without getting new tokens (new SSO registrations to iAS)?
Thanks,
Sorin

Try this
Replace the < and > with their corresponding HTML escape characters , &lt an &gt (The escape characters need a trailing ; )
Under Column Formatting for this column
<a hre="mailto:#IDS#">#IDS#</a> varad

Incomplete record set, Crystal XI, MS SQL stored procedure

Post Author: stadlock
CA Forum: Data Connectivity and SQL
I have a stored procedure written in T-SQL. When I use Query Analyzer to call the stored procedure, all records are returned that I'm expecting. So, the sp would seem to be working properly. If I copy the code in the sp and run as a query within Query Analyzer it returns all the records. The sp sorts the records alphabetically by last name, on the server.My Crystal XI report hooks into the sp using a MS SQL Server ODBC driver. I have a cascading record selection that uses prompt parameters. That functions fine, each subsequent prompt only allows for record selection based upon the preceding selection.Here's my problem: the first record selection prompts for a person's last name. It's a drop-down, you click the drop-down, you see a list of names, in alphabetical order (just as the sp creates it).But the list only goes up to S. There are no records for T through Z. Furthermore, records keep "dropping off" daily. At first, the selection went all the to names that started with "Su...", now it's back to "Sa...". I think before long the S' will disappear, too.Remember, the sp executes properly within Query Analyzer and does return all records, A to Z. Just not the Crystal report. There are somewhat less than 1800 records, total.This was working fine last Friday. I can't imagine what's changed over the weekend.
I've manually executed the sp several times, even scheduled it run every 10 minutes, I just don't know what else to try. I've dropped it and re-created it. I get the same incomplete set of records every time.
Anyone have any idea what I should look for?
Thanks!

Post Author: synapsevampire
CA Forum: Data Connectivity and SQL
Parameters are limited to the number of rows they return.
The solution is a registry setting, check out:
http://technicalsupport.businessobjects.com/KanisaSupportSite/search.do?cmd=displayKC&docType=kc&externalId=c2017238&sliceId=&dialogID=4966384&stateId=1 0 4962685
-k

Combine and simplify SELECT and UPDATE sql query

foreach (BidList t in bidList)
query = "SELECT operator_id, plot_id, status FROM booking " +
"WHERE status='open' AND postcode='" + _plot + "' AND operator_id='0'" +
"ORDER BY datetime ASC;" +
"UPDATE booking SET operator_id='" + t.OperatorId + "', status='allocated' " +
"WHERE (plot_id=" + t.PlotId + " AND operator_id='0' AND status='open') LIMIT 1;";
dbObject.InsertBooking(query);
I am cleaning up my code, and came across the above SQL query. Before I make use of SQL parameters, I wanted to ask if it is possible to combine them, and if so, how?

Consider making a single long query using ‘;’ as a separator:
    query = "";
    foreach (BidList t in bidList)
        query += "UPDATE . . . ; ";
    dbObject.InsertBooking(query);
Use StringBuilder for more improvements.

Kodo 3.4.1: how to limit # of sql query params when using collection param

Hi,
We have a problem when using Kodo 3.4.1 against SQL Server 2005, when we execute query:
          Query query = pm.newQuery( extent, "IdList.contains( this )" );
          query.declareParameters( "Collection IdList" );
          query.declareImports( "import java.util.Collection;" );
          return (List) query.execute( list );
We got:
com.microsoft.sqlserver.jdbc.SQLServerException: The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Too many parameters were provided in this RPC request. The maximum is 2100.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(Unknown Source)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(Unknown Source)
at com.solarmetric.jdbc.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:354)
at com.solarmetric.jdbc.PoolConnection$PoolPreparedStatement.executeQuery(PoolConnection.java:341)
at com.solarmetric.jdbc.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:352)
at com.solarmetric.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.executeQuery(LoggingConnectionDecorator.java:1106)
at com.solarmetric.jdbc.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:352)
at kodo.jdbc.runtime.JDBCStoreManager$CancelPreparedStatement.executeQuery(JDBCStoreManager.java:1730)
at com.solarmetric.jdbc.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:339)
at kodo.jdbc.sql.Select.execute(Select.java:1581)
at kodo.jdbc.sql.Select.execute(Select.java:1533)
at kodo.jdbc.runtime.SelectResultObjectProvider.open(SelectResultObjectProvider.java:102)
at com.solarmetric.rop.EagerResultList.<init>(EagerResultList.java:22)
at kodo.query.AbstractQuery.execute(AbstractQuery.java:1081)
at kodo.query.AbstractQuery.executeWithArray(AbstractQuery.java:836)
at kodo.query.AbstractQuery.execute(AbstractQuery.java:799)
It seems that there're too many ids in the list, and Kodo didn't limit the # of sql parameters when craft the sql query. Is there a way to ask Kodo to use multiple queries with smaller # of sql parameters instead of using one big sql query?
Thanks

Hi,
Sadly, there is no way to do that in Kodo currently. The closest is the inClauseLimit DBDictionary setting, but that setting just breaks things up into multiple IN statements put together with an OR clause. In your case, it looks like the network transport, not the SQL parser, is complaining about size limits.
You could force the query to run in-memory, but that would probably be prohibitively slow, unless the data set that you're querying against is relatively small.
-Patrick

SQL generated with column__1 alias

hi..
i running a report in webi.
SELECT
PUB.unidonem.yil AS Column__1,
SUM(PUB.unibutcealim.adet),
Sum(PUB.unibutcealim.tutar)
GROUP BY
Column__1
but i dont want column__1...and i dont know why şs generated??
any suggestions?
thanks.
( i know the custum sql and its ok.. but not enough for me)

Hi,
Ok, so now i understand you are creating a new Measure in the universe, and testing it in webi,
Here's some background info on your error: http://databases.aspfaq.com/database/what-does-ambiguous-column-name-mean.html
This typically happens when the Select statement has the same name for more than 1 column. So Alias Names need to be setup to ensure unique column names.
There are so many factors that could be at play here.. Your investigation is a a good condidate for a Support Message. Please log an OSS via SMP.
1. Given that this is a Progress DB (generic odbc), you may need some SQL Parameters, or .sbo / .prm file modifications in the DataAccess layer, or some ANSI indetifiers need to be set .. (Relevant guide is here: http://help.sap.com/businessobject/product_guides/boexir31SP3/en/xi31_sp3_data_acs_en.pdf )
2. You might also be interested in Note 1265192 - Web Intelligence Objects Causing Split Queries (missing context)
3. You might also want to check that there aren't Row Level restrictions ontop of your user groups, which may affect SQL generation.
Apologies I cannot do more at this stage.
Regards,
H

Lets Talk Parameters

Hello Discoverer Community,
I am toward the end of a project where the application leverages Discoverer as a reporting tool. I have found that the Discoverer reports I ported over to the new warehouse have saved the parameters that I ran and tested the reports with. This does not match the current report against the old warehouse because the fields are blank. A good exampl is a place where I as for a START_DATE and END_DATE that will be used to allow the user to select some data that is in a data range. When I tested the report and was building it, I did not put default values into these two parameters and ran the report for data in the range of 01-JAN-2007 to 31-DEC-2007. Now any time I run the report as any user, the two dates I tested the report with come up in the START_DATE and END_DATE parameter fields. How can I alter this? Some mentioned that PARAMETERS are specific to the user running them but I am finding this untrue.
1) Where in the EUL tables are the parameters saved for reports that are built?
2) Can this parameters be cleared out doing some SQL against the EUL tables?
3) If you cannot SQL parameters changes, is there another way to set this fields to a default value other than parameter defaults?
Also, I have noticed that when I log in as the report owner, change the default for START_DATE to anything and save the report this change does not seem to get reflected to the users running this report.
Could someone give a run down on parameters and how they are stored and how they can be changed after the fact?
Thanks to all that provide some feed back on my issue.
Whoops forgot to add my version information:
Desktop client: 10.1.2.48.18
EULL: 10.1.2.48.18
EUL: 5.1.1.0.0.0
Oracle DB:10g 10.2.0.2.0 - 64bit
TTFN
Fletch
Message was edited by:
fletchma

Hi,
If you have the SaveLastUsedParamValue preference set to true (in the pref.txt server file or windows registry ) then the last parameters used will get saved within the workbook.
The workbook is saved within the EUL5_DOCUMENTS table and cannot be changed using SQL. You will need to open the report as the report owner and save the report without any parameter values set. Then when the report is opened by a user the parameter will either be empty or contain the default value.
Hope that helps,
Rod West

Regapp.sql parameters

Similar Messages

Maybe you are looking for