hello,

i have following problem:

server: oracle 9i on sun/solaris
client: win2k with oracle forms 2000 (4.5.10.22.0) &
reports application
development environment : TOAD 7.5.2.0 on win2k

additional information:

on server there are two db instances running (orc1 & orc2) for two
customers which belong together in parts of their organization. both
instances are partly associated with each other by (a working) database
link via synonyms (e.g. both use the same customer table on orc1 but
each has own specific orders table in their belonging instance).

situation:

we just migrated old oracle 8.1.7 db to 9i without severe problems
neither on db nor on apllication side (some views / triggers /
procedures to recompile, nothing great) ... after a few days of use by
the customers, there came up an oracle / forms error which reduce me to
despair over days (as you can guess by me posting here now ~lol~).

on ocr1 there is a table named 'status' which can be accessed from orr2
via a public synonym (including mentioned db link which definately
works) ... table is quite simple, 4 colums, 1 PK nothing else worth
mentioning. when we now try to insert a row via our usual form (as user
of orc2 with apropriate rights to do so), there comes up following forms
error:

FRM-40506: ORACLE error -- unable to check for record uniqueness.

after looking up some information about that (FRM-40506, Cause: Oracle
Forms encountered a processing error while checking a record's primary
key items for uniqueness. The table associated with the current block of
the form does not exist, or you do not have authority to access the
table.) i tried to insert exactly the same row data into that table as
same db user from orc2 (using synonym / db link) data via TOAD - which
worked perfectly. from ocr1 the same form also works without any problem
within the application itself (as proved).

so what could be forms' problem here ?! and how to solve it ?! or is it
possibly a migration prob from 8.1.7 to 9i ?!

any idea would be appreciated ... thx !

kind regards

Andreas Zimmermann

Andreas Zimmermann wrote:
You probably used a bug, which is now resolved (or vice versa,
of course ). I do recall something with synonyms and
db links.
Is there a hint of a resolved bug in the installation mnl?
--
Regards,
Frank van Bortel

hi,

well, not that i found it so far ... do you (or anyone) remember any
details on that (or might even hand me kindly a link or something where
i can look it up myself) ?!

or maybe anyone with another idea ?!

thx to you anyways and all others in advance ;-) !

kind regards

Andreas Zimmermann

Frank van Bortel schrieb:

Andreas Zimmermann wrote:
Something else: network stacks. upgrade to 9iRel2? it might
be your forms has some difficulties with that (being a V7 tool)
--
Regards,
Frank van Bortel

hi,

just checked (cause OS / RDBMS) was not upgraded by me personally, so
this is the detailed client's setup:

server: oracle 9i (9.2.0.1.0) on sun/solaris 9 (SunOS 5.9
Generic_112233-11 sun4u sparc sunw, ultra 250)

client: win2k with oracle forms 2000 (4.5.10.22.0) & reports
application

should exclude your last mentioned source of error imo - or am i wrong ?!

kind regards

Andreas Zimmermann

Frank van Bortel schrieb:

Andreas Zimmermann wrote:
Well, it *is* Forms 4.5 against 9iRel2 (I would advise to
patch the database to 9.2.0.4 or higher).
The main (Forms) applictatio is against this 9.2 oracle?
If so - no problem (could it be you still use a V8/V8i
listener?).
Not faniliar with the forms patches, but the baseline is a
V7 tool (using a V7 network stack), and that is incompatible:
a V7 network stack will create errors, if it connects at
all, against V9.2 database. It's not upwards compatible, you
know, and V7 tools worked against 8iRel3, that's 5 releases
(8 and 8i - even 9iRel1?) at least.
--
Regards,
Frank van Bortel

Hi,
First, sorry if this message has mistakes. I´m Brazilian and English is
not my native speaker.

Well, I´ve got the same problem and I was looking for a solution in google
after search in metalink. I realized this problem occurs when I use table
with databse link or even a synonym or view for that.

I,ve found that problem was solved only on Forms 9i and Oracle 9.x. Prior
versions like 6i or 5.x (my case) has aborting always I´m trying to
compile with others client/server combination.

Using a 8.0.4 server to deploy, I kept many pprograms works fine, but now,
this problem has appeared with table@dblink declaration (synonym and view
too).

As workaround, following this two steps I´ve got a migration from the
older deploy version to the same as the production (9.2.0.5).

Here is that:
1- Change all synonyms (table@dblink) to view (here, forms stops
aborting).

2- Put the trigger ON-CHECK-UNIQUE and write the apropriate code for check
the primary key.

Ps.: In the primary-key itens, change the update-allowed property to NO.

I hope you can solve your problems in that way or post a better solution
for us.

Hi,
First, sorry if this message has mistakes. I´m Brazilian and English is
not my native speaker.

Well, I´ve got the same problem and I was looking for a solution in google
after search in metalink. I realized this problem occurs when I use table
with databse link or even a synonym or view for that.

I,ve found that problem was solved only on Forms 9i and Oracle 9.x. Prior
versions like 6i or 5.x (my case) has aborting always I´m trying to
compile with others client/server combination.

Using a 8.0.4 server to deploy, I kept many pprograms works fine, but now,
this problem has appeared with table@dblink declaration (synonym and view
too).

As workaround, following this two steps I´ve got a migration from the
older deploy version to the same as the production (9.2.0.5).

Here is that:
1- Change all synonyms (table@dblink) to view (here, forms stops
aborting).

2- Put the trigger ON-CHECK-UNIQUE and write the apropriate code for check
the primary key.

Ps.: In the primary-key itens, change the update-allowed property to NO.

I hope you can solve your problems in that way or post a better solution
for us.