REP-3000 error after installing OAS 10.1.2.0.2

Question

Hello All,
I've searched the forum and it looks like REP-3000 is a common error encountered when DISPLAY or NLS_LANG aren't set up properly. However, my variables are setup properly. I can run xclock without any problem.
This is after a brand new installation of OAS v10.1.2.0.2 (only forms and reports services). I already had the rdbms software installed v10.2 on my AIX server. I've installed OAS in another ORACLE_HOME.
After the installation, i tried to run the demonstrations....The forms services is ok but not the reports services. I know the variables are set properly but not sure what else to try. I've updated scripts like report.sh and rwrun.sh to add the DISPLAY variable there. I've also altered the opmn.xml file per some other documentation but to no avail.
Has anyone done this Forms and Reports Services installation on AIX or any non-windows server?
Thanks.

Answer 1

I checked the Metalink note# 264159.1 (I am setting the paramform=no when calling the report) as indicated in this document. Bug#3442598 status is "Fixed in 10.1.2.0.2" in Metalink. Is this might be another bug ?
FS, thank you for replying but using a table does not seem to be as a viable option - it is against the idea of dynamically striping the where clause on the form side. I have no problem passing individual parameter or group of parameters from forms to reports. This only happens if I dynamically strip the where clause from the system.last_query and pass it to the report. I don't know how to decipher the dynamically stripped where clause and parse it into individual values (parameters) that I can pass into the report. I just want to pass the where clause of the last executed query to the report. If we can not do it, what is the point of dynamically striping the last query. You mention putting the values into a table, can you please elaborate how should I parse the where clause that form generates (should be dynamic) into a table? The selected columns in each query can be different each time the users execute a custom query. This is why I don't think this table method you suggested will work. Maybe I am wrong. Have you done this before? Have you dynamically parsed a dynamically stripped forms query into table/s ? Any working example is really appreaciated.
I did not understand the length of the URL ? the P_WC user variable on the report side is 2000 characters long - more than sufficient to hold the where clause. What is the limit on the URL length? The error message shows the entire where clause with added %22 and %20 's - therefore I don't think the URL length is an issue here. But I maybe wrong. If the URL length is an issue, then the error message is ambiguous.
Thank you.