![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
|
Oracle 8.1.7 I have exported db1_old and imported to db1_new. There are two other databases, db2_old and db2_new. The db2s contain some common tables. Access is granted by db2 owner to schema owner of db1. Synonym created in db1. After import to db1_new, the tables in db2_new can be view,selected,etc via synonym. But cannot compile any stored procs which use the synonym pointing to two_itst. The compile error references the old schema, which is db2_old. If I change to db2_new.tablename then all is fine. Looking at the synonym via user_synonym everything is fine and points to new schema. db1_old ---> db1_new db2_old ---> db2_new select db2_new.table from db1_new OK compile proc in db1_new with reference to db2_new NOT OK Thanks |
#2
| |||
| |||
|
|
On 10 Jul 2003 12:32:05 -0700, datavector (AT) hotmail (DOT) com (Ken Chesak) wrote: Oracle 8.1.7 I have exported db1_old and imported to db1_new. There are two other databases, db2_old and db2_new. The db2s contain some common tables. Access is granted by db2 owner to schema owner of db1. Synonym created in db1. After import to db1_new, the tables in db2_new can be view,selected,etc via synonym. But cannot compile any stored procs which use the synonym pointing to two_itst. The compile error references the old schema, which is db2_old. If I change to db2_new.tablename then all is fine. Looking at the synonym via user_synonym everything is fine and points to new schema. db1_old ---> db1_new db2_old ---> db2_new select db2_new.table from db1_new OK compile proc in db1_new with reference to db2_new NOT OK Thanks Not sure why you aren't simply compiling those procedures as *owner* of the procedure. Sybrand Bakker, Senior Oracle DBA To reply remove -verwijderdit from my e-mail address |
![]() |
| Thread Tools | |
| Display Modes | |
| |