This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C2503A.3D53E9F0
Content-Type: text/plain
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:
2002/08/29 TEST_MAXIMO Page 1
R E C O R D R E P O R T
For DICTIONARY: PROD_USER_C:[GBN]TEST_MAXIMO.PDC
Record: MAXIMO.CHARTOFACCOUNTS
of Database: TMAX
Organization: RELATIONAL
Null Values Allowed:Yes
Type: ORACLE
Hold Cursor: Unspecified
Open: ORACLE@MAXIMO@TESTMAX/xxxxxxx
Record Size: 913 Bytes
2002/08/29 PROD_MAXIMO Page 1
R E C O R D R E P O R T
For DICTIONARY: PROD_USER_C:[GBN]PROD_MAXIMO.PDC
Record: MAXIMO.CHARTOFACCOUNTS
of Database: AMAX
Organization: RELATIONAL
Null Values Allowed:No
Type: ORACLE
Hold Cursor: Unspecified
Open: ORACLE@MAXIMO@ADMINMAX/xxxxxxx
Record Size: 913 Bytes
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
------_=_NextPart_001_01C2503A.3D53E9F0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
Problem between PowerHouse and Oracle
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:
2002/08/29 &nbs=
p; &nbs=
p; =
TEST_MAXIMO &=
nbsp; &=
nbsp; Page 1
&n=
bsp; &n=
bsp; R E C O R D R E P O R T
&n=
bsp; For DICTIONARY: =
PROD_USER_C:[GBN]TEST_MAXIMO.PDC
=
Record: =
; MAXIMO.CHARTOFACCOUNTS
of =
Database: TMAX
=
Organization: RELATIONAL
Null Values =
Allowed:Yes
=
Type: &=
nbsp; ORACLE
Hold =
Cursor: Unspecified
=
Open: &=
nbsp; ORACLE@MAXIMO@TESTMAX/xxxxxxx
Record =
Size: 913 Bytes
2002/08/29 &nbs=
p; &nbs=
p; =
PROD_MAXIMO &=
nbsp; &=
nbsp; Page 1
&n=
bsp; &n=
bsp; R E C O R D R E P O R T
&n=
bsp; For DICTIONARY: =
PROD_USER_C:[GBN]PROD_MAXIMO.PDC
=
Record: =
; MAXIMO.CHARTOFACCOUNTS
of =
Database: AMAX
=
Organization: RELATIONAL
Null Values =
Allowed:No
=
Type: &=
nbsp; ORACLE
Hold =
Cursor: Unspecified
=
Open: &=
nbsp; ORACLE@MAXIMO@ADMINMAX/xxxxxxx
Record =
Size: 913 Bytes
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
------_=_NextPart_001_01C2503A.3D53E9F0--