Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> Re: Triggers are wonderful things... Ora-2069 global_names error

Re: Triggers are wonderful things... Ora-2069 global_names error

From: Rocky Welch <rockyw_99_at_yahoo.com>
Date: Tue, 9 Jan 2001 09:42:31 -0800 (PST)
Message-Id: <10736.126178@fatcity.com>


--0-1515839483-979062151=:35271
Content-Type: text/plain; charset=us-ascii

 Not much going on at Kosa these days, Chris? ;o)

  "Bowes, Chris" <Chris.Bowes_at_kosa.com> wrote:

"HELLO! I'm TRIGGER. T-R-I double GUH -ER TRIGGER!"

"You are?" Asked pooh pulling his nose out of the honey jar. "That's nice. What's a trigger?"

"Woo hoo hoo hoo hoo! He asked! WHAT'S A TRIGGER? WHY THAT'S EASY! The wonderful thing about triggers is triggers are wonderful things. Their tops are made out of headers, their bottoms can have lots of strings. They insert, update, delete and more, they're fun, fun, fun, fun, fun the most wonderful thing about triggers is, I'm the only one! Oh, I'm the only one. Grrrarrr"

"Well", said Pooh chuckling, "You are the only one that doesn't work. You can't call a package to update a record."

"I can't call a package?" Asked Trigger. "Of course I can. Calling packages to update records is what Triggers do best! So what's the problem?"

"Well, everytime you try to update across the database link to the other base, you mess it up. You cause an ORA-2069 error", replied Pooh, "I need you to call a routine to update records on this post insert or post update and succeed"

"Update after an insert or update. Why that's what Triggers to best. Here come some inserts and updates, watch me update that other base..."

"Hey you Blokes! C'mon. Update you chump! Global name? My name is global name is Trigger! That's good enough. Let's go. Update." Crash, bang, boom.

"Hmph", said Trigger folding his arms and looking defiant. "Triggers DO NOT like calling an update across a database link."

"Oh bother. Now what do I do?", sighed Pooh.

Just then, the NarrDBAtor made a suggestion. "if you turn to the middle of page 163, Trigger asks the Oracle List if they have seen this before." Trigger jumped up. "HOO HOO! Letters is what Triggers do best. I'll go do it. TTFN. Ta ta for now!" BOING, BOINg, BOIng, BOing, Boing, boing....

So then Trigger did indeed write the Oracle List to ask just that question. Pooh has a trigger that needs to needs to call a package to update a base across a database link. The problem is the "ORA-2069 global_names parameter must be set to TRUE for this operation" error hitting on a table. If the package calls for an insert, it works just fine. If it calls for a delete it works fine. Just on updates it causes this. This is a system at a friends site so I am not sure what kind of paticulars there are. It's an Oracle 8 base updating an Oracle 7 base via the database link. All the bases are on NT. Other packages work to other bases so I am pretty sure the listener stuff is set up right. I do not think they can turn on GLOBAL_NAMES as there are several interfaces going to and from these bases and that may mess some of them up. Anyone have a suggestion? Thank you in advance

--Chris
Chris.Bowes_at_Kosa.com

Rocky Welch
Senior Consultant - Internet Services Group Arthur Andersen



Do You Yahoo!?
Yahoo! Photos - Share your holiday photos online! --0-1515839483-979062151=:35271
Content-Type: text/html; charset=us-ascii

<P> Not much going on at Kosa these days, Chris? ;o)<BR>
<P>&nbsp; <B><I>"Bowes, Chris" &lt;Chris.Bowes_at_kosa.com&gt;</I></B> wrote: <BR>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid"><BR>
<META content="MS Exchange Server version 5.5.2650.12" name=Generator><BR>
<P><FONT face=Arial size=2>"HELLO!&nbsp; I'm TRIGGER.&nbsp; T-R-I double GUH&nbsp; -ER&nbsp; TRIGGER!"</FONT> </P><BR>
<P><FONT face=Arial size=2>"You are?"&nbsp; Asked pooh pulling his nose out of the honey jar.&nbsp; "That's nice.&nbsp; What's a trigger?"</FONT> </P><BR>
<P><FONT face=Arial size=2>"Woo hoo hoo hoo hoo!&nbsp; He asked!&nbsp; WHAT'S A TRIGGER?&nbsp; WHY THAT'S EASY!</FONT> <BR><FONT face=Arial size=2>The wonderful thing about triggers is triggers are wonderful things.</FONT> <BR><FONT face=Arial size=2>Their tops are made out of headers, their bottoms can have lots of strings.</FONT> <BR><FONT face=Arial size=2>They insert, update, delete and more, they're fun, fun, fun, fun, fun</FONT> <BR><FONT face=Arial size=2>the most wonderful thing about triggers is, I'm the only one!&nbsp; Oh, I'm the only one.&nbsp; Grrrarrr"</FONT> </P><BR>
<P><FONT face=Arial size=2>"Well", said Pooh chuckling, "You are the only one that doesn't work.&nbsp; You can't call a package to update a record."</FONT> </P><BR>
<P><FONT face=Arial size=2>"I can't call a package?" Asked Trigger.&nbsp; "Of course I can.&nbsp; Calling packages to update records is what Triggers do best!&nbsp; So what's the problem?"</FONT></P><BR>
<P><FONT face=Arial size=2>"Well, everytime you try to update across the database link to the other base, you mess it up.&nbsp; You cause an ORA-2069 error", replied Pooh,&nbsp; "I need you to call a routine to update records on this post insert or post update and succeed"</FONT></P><BR>
<P><FONT face=Arial size=2>"Update after an insert or update.&nbsp; Why that's what Triggers to best.&nbsp; Here come some inserts and updates, watch me update that other base..."</FONT></P><BR>
<P><FONT face=Arial size=2>"Hey you Blokes!&nbsp; C'mon.&nbsp; Update you chump!&nbsp; Global name?&nbsp; My name is global name is Trigger!&nbsp; That's good enough.&nbsp; Let's go.&nbsp; Update."&nbsp; Crash, bang, boom.</FONT></P><BR>
<P><FONT face=Arial size=2>"Hmph", said Trigger folding his arms and looking defiant.&nbsp; "Triggers DO NOT like calling an update across a database link."</FONT></P><BR>
<P><FONT face=Arial size=2>"Oh bother.&nbsp; Now what do I do?", sighed Pooh.</FONT> </P><BR>
<P><FONT face=Arial size=2>Just then, the NarrDBAtor made a suggestion.&nbsp; "if you turn to the middle of page 163, Trigger asks the Oracle List if they have seen this before."&nbsp; Trigger jumped up.&nbsp; "HOO HOO!&nbsp; Letters is what Triggers do best.&nbsp; I'll go do it. TTFN.&nbsp; Ta ta for now!"&nbsp;&nbsp; BOING, BOINg, BOIng, BOing, Boing, boing....</FONT></P><BR>
<P><FONT face=Arial size=2>So then Trigger did indeed write the Oracle List to ask just that question.&nbsp; Pooh has a trigger that needs to needs to call a package to update a base across a database link.&nbsp; The problem is the "ORA-2069 global_names parameter must be set to TRUE for this operation" error hitting on a table.&nbsp; If the package calls for an insert, it works just fine.&nbsp; If it calls for a delete it works fine.&nbsp; Just on updates it causes this.&nbsp; This is a system at a friends site so I am not sure what kind of paticulars there are.&nbsp; It's an Oracle 8 base updating an Oracle 7 base via the database link.&nbsp; All the bases are on NT.&nbsp; Other packages work to other bases so I am pretty sure the listener stuff is set up right.&nbsp; I do not think they can turn on GLOBAL_NAMES as there are several interfaces going to and from these bases and that may mess some of them up.&nbsp; Anyone have a suggestion?&nbsp; Thank you in advance</FONT></P!
><BR>
<P><FONT face=Arial size=2>--Chris</FONT> <BR><FONT face=Arial size=2>Chris.Bowes_at_Kosa.com</FONT> </P></BLOCKQUOTE><BR><BR>Rocky Welch<br>Senior Consultant - Internet Services Group<br>Arthur Andersen<p><br><hr size=1><b>Do You Yahoo!?</b><br>
<a href="http://photos.yahoo.com/">Yahoo! Photos</a> -
Received on Tue Jan 09 2001 - 11:42:31 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US