Jump to content


ashumway

Member Since 05 Nov 2003
Offline Last Active Jan 27 2005 06:52 PM
-----

Posts I've Made

In Topic: Fault Tolerance

07 July 2004 - 12:49 PM

Rory,

We currently run Glovia 5.2 and Oracle 8i on OFS (Windows 2000). We have a two node, shared - nothing configuration. We run our distribution center software on one node and Glovia on the other. The set up works well enough for us, but we have one large problem that you may need to know about: Pro IV requires a second license for the stand-by node. This was very costly for us.

Andy

In Topic: Timeout and imcomplete PRO ISAM data update

11 June 2004 - 12:55 PM

Surajit,

I agree completely with Joseph. My inital experience with Pro IV was on Chess ver 1.10 (the Pro ISAM percursor to Glovia) and converted to Glovia ver 4.2 (and now 5.2) on Oracle 8i. So many major problems simply no longer exist. I no longer have to perform the index file rebuilds. I don't have to worry about what state the database is in when the power goes out, or if a user drops off the network. Oracle rolls back the uncommited transactions. If I want to root through a table with data that isn't in the key, I can do it using SQLPLUS and I don't have create an entire new key file and function to do it.
We've switched to using Cognos Impromptu for reporting, so the users write the vast majority of their custom reports - and publish them on our intranet (saving on printing). Aside from maintaining the joins in the data catalogs (and an occasional "where do I find this data?" question), I'm not involved.
Yes, Oracle comes with it's own set of problems (it's costly, it's a resource pig, the conversion was painful), but at this point I wouldn't hit a dead dog in the posterior with a Pro ISAM database.

Andy

In Topic: Dr. Watson Error

17 May 2004 - 06:50 PM

Kevin,

As far as the traces are concerned, I'm using an ONSERVERERROR trigger to try to trap any Oracle error that might be causing it, but so far I've had no success. In fact, the trigger fires, but doesn't write any data to the table that I'm using because the database session dies first.
Yes, I could post the message, but it's quite lengthy. Here is some of it - I left out the stack dumps:

Application exception occurred:
App: (pid=1524)
When: 3/1/2004 @ 12:09:24.907
Exception number: c0000005 (access violation)


*----> Task List <----*
0 Idle.exe
8 System.exe
140 smss.exe
164 csrss.exe
184 WINLOGON.exe
212 services.exe
224 lsass.exe
404 svchost.exe
432 SPOOLSV.exe
488 svchost.exe
528 FrameworkServic.exe
584 NMSSvc.exe
624 regsvc.exe
652 rshsvc.exe
668 r_server.exe
700 mstask.exe
776 naPrdMgr.exe
796 winmgmt.exe
836 svchost.exe
848 PSXRUN.exe
864 PSXSS.exe
872 mapsvc.exe
1124 zzInterix.exe
1164 init.exe
1100 inetd.exe
1104 cron.exe
576 explorer.exe
320 sistray.exe
1080 KHOOKER.exe
548 PROMon.exe
252 UpdaterUI.exe
1412 svchost.exe
1436 POSIX.exe
1504 ksh.exe
1216 ksh.exe
1524 proiv.exe
1196 drwtsn32.exe
0 _Total.exe

function: Ordinal5085
5f402d91 33c0 xor eax,eax
5f402d93 85c9 test ecx,ecx
5f402d95 c745d804c4495f ss:00ba9c26=????????
mov dword ptr [ebp+0xd8],0x5f49c404
5f402d9c 8975ec mov [ebp+0xec],esi ss:00ba9c26=????????
5f402d9f 894df8 mov [ebp+0xf8],ecx ss:00ba9c26=????????
5f402da2 8945e0 mov [ebp+0xe0],eax ss:00ba9c26=????????
5f402da5 7638 jbe Ordinal5198+0x71 (5f40b8df)
5f402da7 8b4e60 mov ecx,[esi+0x60] ds:019d2dae=????????
5f402daa 8d0480 lea eax,[eax+eax*4] ds:0000000a=????????
5f402dad 6a00 push 0x0
FAULT ->5f402daf 8b0481 mov eax,[ecx+eax*4] ds:0000000a=????????
5f402db2 8d4dd8 lea ecx,[ebp+0xd8] ss:00ba9c26=????????
5f402db5 51 push ecx
5f402db6 6aff push 0xff
5f402db8 50 push eax
5f402db9 8bce mov ecx,esi
5f402dbb 8945dc mov [ebp+0xdc],eax ss:00ba9c26=????????
5f402dbe e8b1f3ffff call Ordinal4424 (5f402174)
5f402dc3 85c0 test eax,eax
5f402dc5 750c jnz Ordinal5122+0x4f (5f407dd3)
5f402dc7 50 push eax
5f402dc8 8d4dd8 lea ecx,[ebp+0xd8] ss:00ba9c26=????????

In Topic: Dr. Watson Error

26 April 2004 - 02:36 PM

God-
Thanks for the suggestion. I guess I don't understand, because the function does not print anything.

In Topic: Preventing Users From Closing the Client

21 April 2004 - 01:07 PM

Thank you for the help. The suggestion to user SUPPRESS_CLOSEWIN=Y is what I needed.