Re: Forms 3.0 and Oracle 8i (8.1.7) ( Invalid Rowid)
From: Frank <fvanbortel_at_netscape.net>
Date: Mon, 28 Apr 2003 22:27:40 +0200
Message-ID: <3EAD8EBC.30702_at_netscape.net>
>>Frank <fvanbortel_at_netscape.net> wrote in message news:<3EAA9CB4.2010600_at_netscape.net>...
>>
>>>Moron wrote:
>>>
>>>>Hi,
>>>>
>>>>as we are migrating our database onto Oracle 8i, we are expieriencing
>>>>some
>>>>Rowid problems.
>>>>
>>>>We already applied the "unsupported" patch which allows forms3 to
>>>>connect on 8i databases.
>>>
>>>You already know it's a no-no situation; why pursue the impossible?
>>>What's the reason for upgrading to 8i? Desupport of your current
>>>version 6?
>>>
>>
>>I am not sure it is impossible.
>>I know that Oracle Application has had the same configuration
>>(forms 3 against 8.x DB) .
Must have been 2.4 - the only Y2K compliant formsV2 ever. That's how important Apps is for Oracle. Side line: if you ever want to see Oracle's direction, watch Apps (now dubbed eBusiness Suite)
>>We even got a patch to solve another problem which was "fetch out of
>>sequence" errors. This patch was'nt public, and not supported of
>>course. The migration to Forms 6 is planed but is a huge workload and
>>we would like to eliminate a 7.1 DB version. I was just hoping there
>>was a solution for the related problems. The conversion on PK fields
>>for the PLSQL code was envisaged but it doesn't make sens as long as a
>>simple direct (without PLSQL Trigger) does not work.
>>
>>>>>After insert or update of a record, we get an error :FRM-40501 / ORA-01410: invalid Rowid as soon as the record has been commited in the DB if we try to modify it again.
>>>>>PL SQL: any statement like " insert into table A() select () from table B where Rowid = :My_block.rowid" raises exactly the same SQL error.
>>>>
>>>>
>>>>Has somebody got the same troubles ?
>>>
>>>Yes - everyone trying to run V6 clients against V8i databases.
>>>Forms V3 was desupported in the V7.1 days, somewhere last century.
>>>Why not upgrade to a later version? Dev6i still supports the
>>>c/s model...
>>>
>>>
>>>>Is there any other patch or workaroud ?
>>>>
>>>
>>>No patch. Workaround: you do all conversions from rowid to
>>>primary key columns, or as suggested: redefine used rowid
>>>columns to varchars.
>>>Doubt if that works, though, as forms uses rowid internally.
>>>That means you will get these errors on forms/blocks you never
>>>defined a rowid field in.
>>>Upgrade is the only w/a.
>>
Date: Mon, 28 Apr 2003 22:27:40 +0200
Message-ID: <3EAD8EBC.30702_at_netscape.net>
Alex Filonov wrote:
> moron.jean-luc_at_rcc.ch (Moron) wrote in message news:<fa37b3cd.0304272244.5c760794_at_posting.google.com>... >
>>Frank <fvanbortel_at_netscape.net> wrote in message news:<3EAA9CB4.2010600_at_netscape.net>...
>>
>>>Moron wrote:
>>>
>>>>Hi,
>>>>
>>>>as we are migrating our database onto Oracle 8i, we are expieriencing
>>>>some
>>>>Rowid problems.
>>>>
>>>>We already applied the "unsupported" patch which allows forms3 to
>>>>connect on 8i databases.
>>>
>>>You already know it's a no-no situation; why pursue the impossible?
>>>What's the reason for upgrading to 8i? Desupport of your current
>>>version 6?
>>>
>>
>>I am not sure it is impossible.
>>I know that Oracle Application has had the same configuration
>>(forms 3 against 8.x DB) .
> > > Forms 2.3 with server 8.0. There is an experience of running 2.3 against > 8.1.6. But 2.3 version (may be even 2.4, don't remember exactly) was > patched to run against 8.x. And it was supported product, even though > supported with 8.0 only. >
Must have been 2.4 - the only Y2K compliant formsV2 ever. That's how important Apps is for Oracle. Side line: if you ever want to see Oracle's direction, watch Apps (now dubbed eBusiness Suite)
> Oracle Apps never worked with Forms 3.0. > >
>>We even got a patch to solve another problem which was "fetch out of
>>sequence" errors. This patch was'nt public, and not supported of
>>course. The migration to Forms 6 is planed but is a huge workload and
>>we would like to eliminate a 7.1 DB version. I was just hoping there
>>was a solution for the related problems. The conversion on PK fields
>>for the PLSQL code was envisaged but it doesn't make sens as long as a
>>simple direct (without PLSQL Trigger) does not work.
>>
>>>>>After insert or update of a record, we get an error :FRM-40501 / ORA-01410: invalid Rowid as soon as the record has been commited in the DB if we try to modify it again.
>>>>>PL SQL: any statement like " insert into table A() select () from table B where Rowid = :My_block.rowid" raises exactly the same SQL error.
>>>>
>>>>
>>>>Has somebody got the same troubles ?
>>>
>>>Yes - everyone trying to run V6 clients against V8i databases.
>>>Forms V3 was desupported in the V7.1 days, somewhere last century.
>>>Why not upgrade to a later version? Dev6i still supports the
>>>c/s model...
>>>
>>>
>>>>Is there any other patch or workaroud ?
>>>>
>>>
>>>No patch. Workaround: you do all conversions from rowid to
>>>primary key columns, or as suggested: redefine used rowid
>>>columns to varchars.
>>>Doubt if that works, though, as forms uses rowid internally.
>>>That means you will get these errors on forms/blocks you never
>>>defined a rowid field in.
>>>Upgrade is the only w/a.
>>
-- Regards, Frank van BortelReceived on Mon Apr 28 2003 - 22:27:40 CEST