![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
we are running forms 6i Patch18 on Windows2003 SP2 terminal servers and periodaclly we get the reports background engine failures. The event view has this Faulting application RWRBE60.EXE, version 3.0.0.0, faulting module UTL60.DLL, version 6.0.8.25, fault address 0x000015fc. Faulting application RWRBE60.EXE, version 3.0.0.0, faulting module winspool.drv, version 5.2.3790.3959, fault address 0x0000afed. any ideas ? |
#3
| |||
| |||
|
|
On Wed, 25 Jul 2007 21:01:51 GMT, "Jerry Alan Braga" jerry.braga (AT) hotmail (DOT) com> wrote: we are running forms 6i Patch18 on Windows2003 SP2 terminal servers and periodaclly we get the reports background engine failures. The event view has this Faulting application RWRBE60.EXE, version 3.0.0.0, faulting module UTL60.DLL, version 6.0.8.25, fault address 0x000015fc. Faulting application RWRBE60.EXE, version 3.0.0.0, faulting module winspool.drv, version 5.2.3790.3959, fault address 0x0000afed. any ideas ? Question: has Forms 6i ever been certified against Win 2003? When was Forms 6i released? When Win2003? When was Forms 6i desupported? So why do you ask? YOYO!!!! -- Sybrand Bakker Senior Oracle DBA |
#4
| |||
| |||
|
|
but In oracle's infinate wisdom they removed client/server support for forms (BIG MISTAKE) after 6i. We are a terminal server shop not Oracle application server with that terrible jinitiator stuff and others. |
#5
| |||
| |||
|
|
On Thu, 26 Jul 2007 12:25:50 GMT, "Jerry Alan Braga" jerry.braga (AT) hotmail (DOT) com> wrote: but In oracle's infinate wisdom they removed client/server support for forms (BIG MISTAKE) after 6i. We are a terminal server shop not Oracle application server with that terrible jinitiator stuff and others. That was not a mistake. The world moves on. Mickeysoft doesn't support client/server anymore, doesn't it? Please realise how terrible old Forms 6i is, and please realise Oracle has many other development tools. Why stay in the dark and stick to client/server? |
#6
| |||
| |||
|
|
sybrandb (AT) hccnet (DOT) nl wrote: On Thu, 26 Jul 2007 12:25:50 GMT, "Jerry Alan Braga" jerry.braga (AT) hotmail (DOT) com> wrote: but In oracle's infinate wisdom they removed client/server support for forms (BIG MISTAKE) after 6i. We are a terminal server shop not Oracle application server with that terrible jinitiator stuff and others. That was not a mistake. The world moves on. Mickeysoft doesn't support client/server anymore, doesn't it? Please realise how terrible old Forms 6i is, and please realise Oracle has many other development tools. Why stay in the dark and stick to client/server? Because things in the 'real world' often don't match your view of how things should work. E.g. we sell a suite of applications which include a couple of hundred 6i reports. Upgrading to Reports 10g would mean we'd have to charge our clients more to cover the increased licensing costs of the reports elements of application server, with no obvious benefit to themselves. |
#7
| ||||
| ||||
|
|
Preston wrote: sybrandb (AT) hccnet (DOT) nl wrote: On Thu, 26 Jul 2007 12:25:50 GMT, "Jerry Alan Braga" jerry.braga (AT) hotmail (DOT) com> wrote: but In oracle's infinate wisdom they removed client/server support for forms (BIG MISTAKE) after 6i. We are a terminal server shop not Oracle application server with that terrible jinitiator stuff and others. That was not a mistake. The world moves on. Mickeysoft doesn't support client/server anymore, doesn't it? Please realise how terrible old Forms 6i is, and please realise Oracle has many other development tools. Why stay in the dark and stick to client/server? Because things in the 'real world' often don't match your view of how things should work. E.g. we sell a suite of applications which include a couple of hundred 6i reports. Upgrading to Reports 10g would mean we'd have to charge our clients more to cover the increased licensing costs of the reports elements of application server, with no obvious benefit to themselves. It would also mean your clients would be using supported technology. Is that a benefit? |
|
It would mean they could meet their legal requirements with respect to auditing and compliance. Is that a benefit? |
|
Given that Oracle has made clear, for years, its intention what you are really saying is that your firm chose to ignore Oracle and the needs of its customers |
|
making so appropriate this quote from Shakespeare: "For 'tis the sport to have the enginer / Hoist with his owne petar" You being the engineer in this case. <g If you don't do it now when do you plan to do it? With version 11? 12? 20? You should have been making this investment on an on-going basis. |
#8
| |||
| |||
|
|
No. I know it would be a 'perceived' benefit with some CDOS posters who rate the use of unsupported versions at a similar level to child murder, but the reality is we've never hit an Oracle bug with 6i in the several years we've been using it. In the highly unlikely event we do in the future, we'll worry about it then. |
|
If you don't do it now when do you plan to do it? With version 11? 12? 20? You should have been making this investment on an on-going basis. We don't plan to do it with any specific version. When we have a window in the development cycle to look at alternatives, we'll do so - but that won't be this year for certain. "If it ain't broke, don't fix it" - as Shakespeare probably would've said had he thought of it. |
#9
| |||
| |||
|
|
Preston wrote: No. I know it would be a 'perceived' benefit with some CDOS posters who rate the use of unsupported versions at a similar level to child murder, but the reality is we've never hit an Oracle bug with 6i in the several years we've been using it. In the highly unlikely event we do in the future, we'll worry about it then. Your attitude speaks loudly and clearly with respect to your value system. If you don't do it now when do you plan to do it? With version 11? 12? 20? You should have been making this investment on an on-going basis. We don't plan to do it with any specific version. When we have a window in the development cycle to look at alternatives, we'll do so - but that won't be this year for certain. "If it ain't broke, don't fix it" - as Shakespeare probably would've said had he thought of it. That window will never come. You will spend more and more of your energy doing stupid stuff like trying to figure out how to connect a paleolithic forms tool to the currently supported database. In fact right now I've got a smile on my face trying to figure out just how you plan on supporting Oracle 11g. By the time you decide your customers are more important than whatever you've currently prioritized you will not have the revenue stream to do anything other than hire a bankruptcy attorney. |
#10
| |||
| |||
|
|
Careful Daniel, you're getting dangerously close to Sybrand levels of arrogance with that post. |
|
You know absolutely nothing about our customers, nor what's important to them. |
![]() |
| Thread Tools | |
| Display Modes | |
| |