You must have the Oracle Rdb READ access to the specified relations
    to use this statement.

    Because the declared START_STREAM statement and the undeclared
    START_STREAM statement both begin with the keyword START_
    STREAM followed by a stream name, make sure you do not split the
    undeclared START_STREAM stream statement over two lines in such
    a way that Oracle Rdb will interpret it as a declared START_STREAM
    statement.

    For example, ending the first line of the following undeclared
    START_STREAM statement with the keyword USING indicates to
    Oracle Rdb that the statement is not complete:

    RDO> START_STREAM EMP_STREAM USING
    cont> E IN EMPLOYEES SORTED BY E.LAST_NAME

    You could also use a continuation character to indicate to RDO
    that the undeclared START_STREAM statement is not complete.
    Without the continuation character, the following declared START_
    STREAM statement could be interpreted as a declared START_STREAM
    statement:

    RDO> START_STREAM EMP_STREAM -
    cont> USING E IN EMPLOYEES SORTED BY E.LAST_NAME

    Because an association is made between the DECLARE_STREAM
    statement and the START_STREAM statement by the declared stream
    name clause in both statements, it is not permissible to specify
    the RSE in the declared START_STREAM statement. Instead, include
    the RSE in the DECLARE_STREAM statement.

    You can issue several declared START_STREAM statements in a
    module. As long as you use the same declared stream name, they
    will all refer to the same stream.

    RDO does not allow a record stream from which data values cannot be
    fetched by DBKEY (views that retrieve values from streams defined using
    the SQL GROUP BY or UNION clauses) to be declared or started. Such
    attempts produce the following exception:

      VWNOFETCH view 'view-name' cannot be fetched within a stream