Re: logical standby
- From: "Bradd Piontek" <piontekdd@xxxxxxxxx>
- To: awells@xxxxxxxxxxxx
- Date: Wed, 16 Jul 2008 16:20:03 -0500
April,
This can all be done, but you do have to change the logical standby
configuration (I'm assuming 10g R2)
1. Logical standby must be changed from guard_status of ALL to standby
select guard_status from v$database;
I'm guessing it currently says 'ALL'
alter database guard standby;
2. You'll may want to set up some skip rules to make sure no DDL/DML
accidently gets sent from the primary
--
Bradd Piontek
Oracle Blog: http://piontekdd.blogspot.com
Linked In: http://www.linkedin.com/in/piontekdd
On Wed, Jul 16, 2008 at 3:20 PM, April Wells <awells@xxxxxxxxxxxx> wrote:
> Please forgive my utter stupidity today… but I know I'm missing something
> here
>
>
>
> I thought the point of having a "logical standby" was that you can create
> things that are bolted onto the primary schema and life doesn't have to be
> identical to the primary…
>
>
>
>
>
> I have a question…
>
>
>
> In order to proceed with testing, I created user finance on the logical
> standdby. This user will select from the primary users.
>
> I granted it connect, resource
>
> I set the default tablepsace as users
>
> I connected as the user
>
> I tried to create a table fred
>
> I got permissions errors
>
> I granted finance create table and create procedure
>
> I tried to create a table fred
>
> I got permissions errors
>
> I created the table finance.fred as sysdba successfully
>
>
>
> Do you know if this is expected behavior of a logical standby?
>
>
>
> I'm also working to try and get the same finance user to create procedures
> and synonyms and EVERYTHING is weirding out on me…
>
>
>
> Compiling the procedures gives me these errors…
>
>
>
> LINE/COL ERROR
>
> -------- -----------------------------------------------------------------
>
> 91/4 PL/SQL: SQL Statement ignored
>
> 107/4 PL/SQL: ORA-00980: synonym translation is no longer valid
>
> 124/4 PL/SQL: SQL Statement ignored
>
> 124/16 PL/SQL: ORA-16224: Database Guard is enabled
>
> 144/4 PL/SQL: SQL Statement ignored
>
> 158/4 PL/SQL: ORA-00980: synonym translation is no longer valid
>
> 169/4 PL/SQL: SQL Statement ignored
>
> 169/16 PL/SQL: ORA-16224: Database Guard is enabled
>
> 192/4 PL/SQL: SQL Statement ignored
>
> 208/4 PL/SQL: ORA-00980: synonym translation is no longer valid
>
> 224/4 PL/SQL: SQL Statement ignored
>
>
>
> LINE/COL ERROR
>
> -------- -----------------------------------------------------------------
>
> 240/4 PL/SQL: ORA-00980: synonym translation is no longer valid
>
> 254/4 PL/SQL: SQL Statement ignored
>
> 270/4 PL/SQL: ORA-00980: synonym translation is no longer valid
>
> 284/4 PL/SQL: SQL Statement ignored
>
> 304/4 PL/SQL: ORA-00980: synonym translation is no longer valid
>
> 318/7 PL/SQL: SQL Statement ignored
>
> 318/19 PL/SQL: ORA-00942: table or view does not exist
>
> 323/24 PL/SQL: SQL Statement ignored
>
> 339/25 PL/SQL: ORA-00980: synonym translation is no longer valid
>
>
>
> Thanks for your time
>
>
>
> April
>
>
>
> ------------------------------
>
>
> Confidentiality Notice!
> This electronic transmission and any attached documents or other
> writings are confidential and are for the sole use of the intended
> recipient(s) identified above. This message may contain information
> that is privileged, confidential or otherwise protected from
> disclosure under applicable law. If the receiver of this
> information is not the intended recipient, or the employee, or
> agent responsible for delivering the information to the intended
> recipient, you are hereby notified that any use, reading,
> dissemination, distribution, copying or storage of this information
> is strictly prohibited. If you have received this information in
> error, please notify the sender by return email and delete the
> electronic transmission, including all attachments from your
> system.
>
>
Other related posts:
