Re: WebDB install problems on solaris7

From: Peter Sylvester <peters_at_mitre.org>
Date: Tue, 29 Jun 1999 18:17:13 -0400
Message-ID: <377945E9.F3DCA18E@mitre.org>

I just went through this mess; see attached for my story. Peter

Mareike Ernst wrote:
>
> This is a cry for help:
>
> OS: Solaris 7
> Oracle 8i
>
> Situation: Only one database (clean, no frills) running. Sqlplus
> connection (with sys or whatever as login), listeners etc work fine. In
> other words everything is as it should be with the db.
>
> Then... I run the WebDB install program, specifying that I want to
> install WebDB into the same ORACLE_BASE but a different ORACLE_HOME from
> 8i.
> Works fine until I get to the bit where the SYS password is needed -
> there isn't a whole lot of choice here as I only have one db running.
> Whatever I try to write in fails...
>
> Where does the WebDB installer look for passwd/db information? Any
> ideas at all what to do, anyone? Anyone else this has happened to?
>
> I've evn tried a manual install but this fails round about the bit where
> further configurations are supposed to be carried out via a webpage,
> which never appears even there is SOMETHING on the port where it should
> be.
>
> Please mail my work address, I will post a summary if applicable!
>
> cheers
> Mareike

Webdb 2.0.5.6.1 / Solaris 2.7 Installation Notes P. Sylvester, MITRE Corporation 6-28-99 peters_at_mitre.org

DISCLAMER:
Use any of the following information at your own risk. Do let me know, however, of any corrections/improvements/etc.

BACKGROUND NOTE:
I initially tried to perform the WebDB installation in a separate 8.0.5 client-only ORACLE_HOME, on a machine running the 8.5.1 DB server. The WebDB and Listener options were selected and it appeared to go through the install process, but no PLSQL packages got created.

I initially tried to use port 90 for the listener, but it failed with an ambiguous message. This was finally traced using "truss" to an inability to open the port. As it turns out, only the superuser can open ports below 1000. The solution is to pick a port number over 1000, i.e. 1080. (or run it as root, if you dare).

# Setup your environment and start the Web server: setenv PATH ${PATH}:$ORACLE_HOME/bin:$ORACLE_HOME/webdb/bin setenv LD_LIBRARY_PATH /usr/lib:$ORACLE_HOME/lib:$ORACLE_HOME/webdb/lib wdbstart host_name port_number &

Verify that it stays running by checking with ps after a while.

# Once the web server is running, use one of the following URLs to configure:

http://host:port/admin_/gateway.htm

http://host:port/admin_/listener.htm

http://host:port/webdb/

If you get an error like "webdb.main" object not found, the PL/SQL is probably not setup correctly. (See below to fix)

The following steps need to be performed on the DB server, as TNS alias names are not handled in the various scripts. (Requires ORACLE_HOME of the local DB server).

In initSID.ora, add the following, as default value of 64 causes errors: opencursors=128

Restart the DB server so settings take effect

Create webdb tablespace, and temporary tablespace, if desired. Create webdb administrative user (i.e. webdb). NOTE: password must be same as name during install.

Create OWS user and tablespace, if desired (I reused the webdb user)

#
# Install OWS80 components from webdb CD:
# (there are references to some of these objects from the webdb packages)
#

mkdir ows80_sql
cp -p /cdrom/oracle/owa80/* ows80_sql
cd ows80_sql
sqlplus webdb/webdb
set define off
REM replace the following with your configured values: @owaload.sql owa_user owa_tablespace owa_temp_ts log_filename

#
# Install webdb components
#

mkdir webdb_sql
cp -p /cdrom/oracle/wwv20/sqlfiles/* webdb_sql cd webdb_sql
./winstall webdb_user sys_password webdb_tablespace webdb_temp_ts log_filename

BUGS, Etc.

If Master-Detail form master record contains double quote (") characters, it is displayed properly upon execution of a query. However, printing of the field in the master record is truncated when editing the detail records. Also, can't edit the master record at this point, as it reports WWV-14612 "Record changed by someone else".
If the join fields in the detail record are not displayed, you cannot insert new detail records without error.
If you use sequences for default field values, (i.e. #myseq.nextval), The sequence values are generated for any blank records on the form.

Received on Tue Jun 29 1999 - 17:17:13 CDT