Oracle Web Applications
by Andrew Odewahn


Unconfirmed error reports are from readers. They have not yet been approved 
or disproved by the author or editor and represent solely the opinion of 
the reader.

If you have technical questions or error reports, you can send them to
booktech@oreilly.com.  Please specify the printing date of your copy.


This page was last updated April 13, 2001.


Here's a key to the markup:

        [page-number]: serious technical mistake
        {page-number}: minor technical mistake
        <page-number>: important language/formatting problem
        (page-number): language change or minor formatting problem
        ?page-number?: reader question or request for clarification


UNCONFIRMED errors and comments from readers:


{21}  Code in section 'Create and start the Queue Tables';
In AQ, after queue tables are created it is also necessary to explicitly 
create the queues themselves.

So after the 2 commands

	EXECUTE DBMS_AQADM.CREATE_QUEUE_TABLE( ... );

insert:

	-- Create the queues themselves
	EXECUTE DBMS_AQADM.CREATE_QUEUE (	
		queue_name => 'BUY_QUEUE',
		queue_table => 'BUY_QUEUE');

	EXECUTE DBMS_AQADM.CREATE_QUEUE (	
		queue_name => 'SELL_QUEUE',
		queue_table => 'SELL_QUEUE');

Now you can go on to start up the queues without getting an Oracle error.


<43> The second sentence in the second paragraph states that a schema can not 
have multiple objects with the same name. This is incorrect. 

An object can have the same name provided the object resides in a separate 
namespace.

For example, the same name CAN be given to a table, index, constraint, 
cluster. database trigger and private database link.  A name CAN NOT be 
duplicated for a table, view, sequence, private synonym, stored procedure, 
stored function, package or snapshot.


[154]  7.3.1.2.1 The SEND procedure;
The description for the "expires" parameter states "If [the date is] omitted, 
[the cookie] never expires." In fact, if the date is omitted (i.e. defaults to 
NULL), or if an empty string is passed, the cookie expires when the user's 
browser session ends (when they quit from their browser). Temporary cookie 
behavior is described in Netscape's cookie specification in:

	http://www.netscape.com/newsref/std/cookie_spec.html

which says: "'expires' is an optional attribute. If not specified, the cookie 
will expire when the user's session ends."

A cookie can be set to expire on a date in the distant future, but there is no 
way to create a cookie that never expires.

I couldn't find any actual documentation on this procedure in Oracle's manuals,
but I tested the OWA_COOKIE.send function myself and determined that it works 
according to the specification.


?190? I am trying to create a package using the emp_survey and I am getting 
the following errors:

	99/4   PL/SQL: SQL statement ignored

	106/37 PLS-00493: invalid reference to a server side-side object or 
	function in a local context.

I am running Oracle8i on Windows NT with service pack 6.

What do I need to do to correct this problem ?