Designer Web Assistant and WebDB

Question

We require assistance with linking WebDB to Web Assistant. We are new to the WebDB and the install instructions provided by the Web Assistant download are unclear about the finer points of connecting to the webdb listener. We are using Designer 2.1.2, WebDB 2.1 and Oracle 8.0.5, on a Unix Server, under Windows NT.
Problem:
When the homepage URL (odwa/odwa.cdwp.startup) is requested, using our ODWA id, the following error message is returned: component 'INIT_CGI_ENV' must be declared and identifier 'WWV_DOCLOAD.IS_FILE_DOWNLOAD' must be declared.
To date:
1) WebDB is installed on the Unix server which holds the Designer repository.
2) ODWA id has been created and granted access according to the grant script provided in the download for Web Assistant.
3) The ODWA ddl files have been moved to the server as \orant\odwa\ddl\* and recompiled.
4) The ODWA gif files have been moved to the server as \orant\odwa\images\* and a virtual directory has been added to the Listener Settings as /odwa_images/.
5) A new DAD was created called ODWA, pointing to the repository. The other parameters have not altered our problem and were removed.
6) Web Assistant was previously installed and evaluated as a static client and looks like a very valuable tool. But we require the flexibilty and simplicity of the dynamic approach.
Any suggestions would be appreciated! Thank you.

Answer 1

Anne,
Can you run WebDB itself? (create WebDB modules user the WebDB database browser)?
Did you create public synonyms for all database objects in the OAS_PUBLIC schema (these objects constitute the OAS Web PL/SQL Toolkit; packages such as HTF, HTP and OWA_UTIL should be in this schema)? Did you grant execute privileges on these objects to PUBLIC? (you can test this by connecting to SQL*PLUS and typing: desc htp <enter>.
If this returns a long list of procedure headings, this is probably okay. To be sure, type 'drop package htp' to remove an accidentally installed local instance of this package. If this statement does indeed drop a package, you must ensure no OAS_PUBLIC objects are installed in the ODWA schema.
The last error message you describe: procedure returned no data, could have the following cause: you call ODWA properly but the cdwp package in ODWA writes data to the wrong HTP package. The data returned by the WebDB listener is read from a buffer inside the HTP package (the one that is accessible to the WebDB listener). However, if ODWA writes to another package and therefore another buffer, WebDB listener cannot find any data to return.
To reduce confusion, it is best to make sure the database contains only one HTP package (as well as only one instance of the other objects in the Web PL/SQl Toolkit).
null