| Troubles with reporting from logical standby (Oracle 10g) [message #193428] |
Sat, 16 September 2006 13:10  |
zathras
Messages: 3
Registered: September 2006
|
Junior Member |
|
|
Hello,
I've setup a logical standby, everything seemed to be ok - archivelogs are transported, users and tablespaces created on primary are visible on standby. However when I create a table on primary, I get "ORA-00942: table or view does not exist" while selecting(as any user) on standby despite of the fact that logs' been switched and applied. There is no sign of error in alert.log. It puzzles me cause creation of tablespaces and users is ok. Can anyone help me? Thanks in advance.
Greetz.
Michal "Zathras" Ambroziewicz
|
|
|
|
|
|
| Re: Troubles with reporting from logical standby (Oracle 10g) [message #193464 is a reply to message #193462] |
Sun, 17 September 2006 07:03  |
zathras
Messages: 3
Registered: September 2006
|
Junior Member |
|
|
> Can you explain how you are getting ORA-942 while running create table statements?
I get ORA-00942 on standby when I try to select anything from table previously created at primary site, not while creation.
I.e. I create table T1 on primary, switch logfile and when I select * from T1 on standby, I get the error message. However when I do the same with create user or create tablespace, everything is ok.
It's not DBMS_LOGSTDBY.SKIP - I've already checked.
Greetz.
Michal "Zathras" Ambroziewicz
|
|
|
|
| Re: Troubles with reporting from logical standby (Oracle 10g) [message #193465 is a reply to message #193428] |
Sun, 17 September 2006 07:14 |
email.sandeepnaik
Messages: 121
Registered: August 2006
|
Senior Member |
|
|
Is table created in nologging mode?
what tablespaces table is created in ?
what is output of below satements
1 select force_logging from v$database (on primary)
2 select table_name,logging from dba_tables where table_name='your table name' ;(on primary)
4 select segment_name,tablespace_name from dba_segments where segment_name=' your table name'; (on primary)
Sandeep
|
|
|
|
| Re: Troubles with reporting from logical standby (Oracle 10g) [message #193466 is a reply to message #193465] |
Sun, 17 September 2006 07:36 |
zathras
Messages: 3
Registered: September 2006
|
Junior Member |
|
|
| email.sandeepnaik wrote on Sun, 17 September 2006 14:14 |
Is table created in nologging mode?
|
I don't think so. Force logging is on all the time.
| Quote: |
what tablespaces table is created in ?
|
Test.
| Quote: |
what is output of below satements
1 select force_logging from v$database (on primary)
2 select table_name,logging from dba_tables where table_name='your table name' ;(on primary)
4 select segment_name,tablespace_name from dba_segments where segment_name=' your table name'; (on primary)
|
1. yes.
2. table_name log
test yes
3. test test
PS. If it's any help, I followed "Make Recovery Logical" from Oracle Magazine July/August 2004 while creating standby.
Greetz.
Michal "Zathras" Ambroziewicz
|
|
|
|
| Re: Troubles with reporting from logical standby (Oracle 10g) [message #193606 is a reply to message #193428] |
Mon, 18 September 2006 07:51 |
email.sandeepnaik
Messages: 121
Registered: August 2006
|
Senior Member |
|
|
There are few datatypes and types of tables unsupported in logical standby make sure your "test" table is not falling in below criteria.
Sandeep
Unsupported Datatypes:
NCLOB
LONG
LONG RAW
BFILE
ROWID
UROWID
user-defined types
object types REFs
varrays
nested tables
Unsupported Tables, Sequences, and Views:
User-defined tables and sequences in the SYS schema
Tables with unsupported datatypes
Tables using data segment compression
Index-organized tables
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
