logical standby database limitation
From: charles <dshproperty_at_gmail.com>
Date: Wed, 30 Mar 2011 13:19:27 -0700 (PDT)
Message-ID: <cdd3d331-c36e-4589-ab90-60e0cd6d1de2_at_j13g2000pro.googlegroups.com>
Our situation is like this, we want a system where we can let end user to use it as a report server, browse the source code, etc. And occasionally they will need to create a temp table to facilitate their reports as well.
Date: Wed, 30 Mar 2011 13:19:27 -0700 (PDT)
Message-ID: <cdd3d331-c36e-4589-ab90-60e0cd6d1de2_at_j13g2000pro.googlegroups.com>
Our situation is like this, we want a system where we can let end user to use it as a report server, browse the source code, etc. And occasionally they will need to create a temp table to facilitate their reports as well.
It seems to be me that logical standby database is a way to go . However, from DBA_LOGSTDBY_UNSUPPORTED, we can see there are about 100 columns in our database that are not supported.
What is your opinion or recommendation? Could we use logical_standby database and use datapump to move those tables manually? or use steams on top of logical standby database?
Thanks very for your support Received on Wed Mar 30 2011 - 15:19:27 CDT