Problem between PowerHouse and Oracle

[Bill D Michael]

In the PDL, you can put "DATABASE AMAX TYPE ORACLE   NULL VALUES ALLOWED
OPEN &"

Note the null values statement in the PDL... maybe your PDL entries are
different?

Bill

------------------
"This posting reflects the individual views and opinions of the author and
does not necessarily represent the views and opinions of International
Paper.



I am attempting to update a table in an Oracle database with data from an
application developed in-house using PH 8.20.D.  The Oracle database
resides on a Windows 2000 server and PowerHouse is running on OpenVMS
7.2-1.  When I developed the program to update the Oracle test database,
everything worked fine.  Then, when I tried to place the PowerHouse program
(QTP) into production, I encountered constraint errors.  I checked the
table description with Qhsow and found a difference - see "Null Values
Allowed" in table header below:

<snip>

The test database and the production database are on two servers, but both
are running are running Windows 2000 v 5.0.2195 SP 2.  The Oracle DBA
showed me that both databases are identical in their description.  He added
that Oracle has no concept of placing a "Not Null" constraint on an entire
table.

Some subtle difference must exist somewhere that makes PowerHouse think the
entire table has a not null constraint on it.  Does anyone have an answer.

George B. Nekolny
Denver Water Dept.
(303) 628-6243
George.Nekolny@denverwater.org