Problem between PowerHouse and Oracle
Nekolny, George B.
george.nekolny@denverwater.org
Fri, 30 Aug 2002 14:22:25 -0600
Darren,
I didn't have anything to do with the decision to have two instances
of the MAXIMO database. TMAX is used for testing purposes and runs on one
server; AMAX is the production version and runs on a different server. I
had to compile two different dictionaries to deal with this situation. This
is how I got into trouble. I was sure I used the same script to LOAD the
production dictionary, but I apparently did not, or as I said before,
inadvertently placed a "NOT" regarding null values (I don't recall doing it)
in the database declaration in the dictionary .PDL. As you know, I would
have to change values here (passwords etc.) when dealing with two different
databases. Again, I thank you very much for pointing me in the right
direction.
-----Original Message-----
From: Darren Reely [mailto:darren.reely@latticesemi.com]
Sent: Friday, August 30, 2002 12:14 PM
To: Nekolny, George B.
Subject: Re: Problem between PowerHouse and Oracle
George,
The other thing that struck me as odd is you have two Database
declarations; TMAX and AMAX. We have Oracle running on a Solaris box
where the PH code also resides. We use OPS$USER to connect to the
database defined by ORACLE_SID. This is why we only have one database
declaration. Which database we connect to depends on where the code is
executed. I have successfully experimented setting up a second database
declaration to access production from the development box also. For
that I had to use your method.
So, I am wondering if there is any advantage in have two declarations?
Any disadvantages. I would think that when you create a file statement
in a Quick source file you would have to decide which database to use.
In our case we just do it once as in FILE STEP_TABLE IN MFG. Do you
have to alter your code for compiling to producion? Am I missing something?
Thank you,
Darren.
P.S. I also notice your running a different version of Maximo than we are.
Nekolny, George B. wrote:
>BINGO! Thank you very much. I don't remember typing "NOT" in the
>source, so I never double checked it.
>
>-----Original Message-----
>From: Darren Reely [mailto:darren.reely@latticesemi.com]
>Sent: Friday, August 30, 2002 10:47 AM
>To: Nekolny, George B.
>Subject: Re: Problem between PowerHouse and Oracle
>
>
>This is a bit of a guess...
>
>In my data dictionary I declare "Null values allowed". Are you sure
>your production and development dictionaries are from the same source
>from the same time? I susspect that production somehow got compiled
>with "Null values NOT allowed".
>
>Here is my database declaration...
>
>Database
>MFG &
> Type
>ORACLE &
> Null values
>allowed &
> Open
>ORACLE@OPS$USER &
> Owner PBSYS
>
>
>Darren.
>
>
>Nekolny, George B. wrote:
>
>>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
>>
>