Thanks for the question, Guy.
Asked: October 14, 2000 - 12:36 pm UTC
Last updated: September 06, 2005 - 8:09 am UTC
Version: 8.1.6
Viewed 1000+ times
You Asked
Hi Tom,
I read many papers about the differences between the standard and enterprise edition of 8i. I always worked with the enterprise edition but we want to reduce costs and move to the standard edition.
The papers are not very clear on some points. Could you please answer the following questions ?
a) Standard does not support advanced replication but supports ditributed database. They say it supports basic replication.
Can I create a DB link in the standard edition ?
Can I create a snapshot between 2 instances ? I need to place des2K CG_REF_CODES on one location and distribute it accross a couple of instances. If I can create database links, and no snapshots, I could simply create a copy of the tables I need to replicate, truncate and select from a db_link.
b) Does the standard edition benefit from multi processor machines even if no parallel query is available ?
c) They say that the standard edition does not support tablespace point in time recovery ? IS TSPIR the same as RECOVER DATABASE UNTIL xxx ? I mean, can I do online backups with the standard edition and be able to apply the redo logs until time x if say, someone does something BAD to the database (Bad load, dropped table, etc ?)
Thanks
and Tom said...
a) you can create a database link in standard -- that is part of "distributed".
You can create a READ ONLY snapshot between 2 instances.
b) yes, Oracle is a multi-process/multi-threaded program. It'll make use of every CPU on the machine and will greatly benefit from >1 CPU regardless of the "flavor" you are using.
c) tablespace point in time recovery is the ability to recover a SINGLE tablespace of a database to a given point in time -- not the entire database. You can recover an entire instance to a point in time with SE and EE. You can recover an indivdual tablespace to a point in time with EE.
(btw: you can sort of do it in SE as well. just take the affected tablespace, system + rollback. restore them elsewhere. offline drop the other files from this copy. point in time recovery the tablespace. EXP it. IMP it. EE uses the transportable tablespace feature -- not available with SE -- to make the EXP/IMP very very fast. So, you can achieve the same thing in SE, it just takes longer)
Rating
(2 ratings)
Is this answer out of date? If it is, please let us know via a Comment