Rekspa: Ah good to see that not only we will be happy to ORA-06508 ORA-04068-cal :) ORA-04065 ORA-0

Rekspa: Ah good to see that not only we will be happy to ORA-06508 ORA-04068-cal :) ORA-04065 ORA-06512 - adatszotar corruption - data dictionary corruption - Oracle DBA - Oracle! (2010.08.10 15:53). database - Oracle Database Angelo_: Hey, I love it in this blog, keep it up. Not by chance something good to SQL-ed, which are listed ... (2008.10.03. huck imports 13:11) who is entitled to% System% ANY saga? - Oracle DBA - Oracle database huck imports - Oracle huck imports Database Darvel: Thanks for the comments, either completely legitimate! improves. huck imports the cpu_count relies not on, because if this is the manual ... (2008-05-09 15:26). RHEL - number of CPUs - Oracle DBA - Oracle database - Oracle Database Darvel hi, I recommend the download.oracle.com/docs /cd/B19306_01/server.102/b14230/concepts.htm reading the logical huck imports standby coast ... first - it will be better - Oracle DBA - Oracle database - Oracle Database huck imports Ates85 (2008-04-30 10:19.): Hi Tom! The last time that worked with such great Objecteket even before departure ... Memory huck imports Notification (2007.09.19 16:54).: Library Cache Object Loaded huck imports Into SGA - Oracle DBA - Oracle database - Oracle Database
September 2012 (1) October 2011 (1) September huck imports 2011 (1) July 2011 (1) November 2009 (3) June 2009 (1) March 2009 (2) February huck imports 2009 (1) January 2009 (1) September 2008 (1) August 2008 (3) April 2008 (2) More ...
We put together a logical standby, where we had the need, you do not have failover / switchover from using it, only reporting / query system huck imports will be. This konnyebseg sex. RHEL 3 and Oracle RDBMS 10.2.0.1 were used for two-node RAC Setup installation the source. a tip: If you use a logical standby is not you try in 10.2.0.3, 10.2.0.1 the very buggy, but it will be a lot of headache and trouble. huck imports almost klikkelegtos version (Oracle Grid Control / Database Control) I show again because it is so interesting. huck imports The following steps are all vegrehajtva SYSTEM user, unless otherwise indicated. Check that the 'force logging' option and the primary piece of archivelog mod n (primary) is turned on: select force_logging, log_mode from v $ database; if not, authorize the archivelog mode (log_archive_dest_N Set parameters before / spfile in init.ora v /.): shutdown immediate huck imports startup huck imports mount alter database archivelog; alter database open; then 'force logging' option is: alter database force logging; good to know which schema are by default excluded from the replication, this with the following SQL can be Show, using the DBA_LOGSTDBY_SKIP view: select * from DBA_LOGSTDBY_SKIP; Locate out which are the tables in which the logical standby stocked unsupported data types: select distinct owner dba_logstdby_unsupported from table_name; the logical standby replication soul that primary keys are letezzenek I identify with each line made by the User. which tables are not included in this round so to find out: SELECT * FROM DBA_LOGSTDBY_NOT_UNIQUE WHERE (OWNER, TABLE_NAME) NOT IN (SELECT DISTINCT OWNER, TABLE_NAME FROM DBA_LOGSTDBY_UNSUPPORTED) AND BAD_COLUMN = 'Y' csekkeljuk init parameter settings huck imports of the source: select inst_id, name, value from gv $ parameter where name in ('db_name', 'compatible', 'log_archive_format', 'log_archive_dest_1', 'log_archive_dest_2', 'log_archive_dest_3', 'instance_name', 'remote_login_password_file', 'db_unique_name', 'log_archive_dest_state_1' 'log_archive_dest_state_2', 'log_archive_dest_state_3', 'log_archive_max_processes', 'fal_server', 'fal_client') mine looked like this:
OPTIONAL SERVICE = myprod2
1
db_unique_name
enable
2
(The above table shows that this is indeed a RAC setup and also to cross-node used to face official last too.) The following operations: * Sets log_archive_dest_x huck imports was that future use (target logical standby) DB from point * log_archive_max_processes tuning * Please confirm the fal_server and the fal_client parametres (FAL = Fetch Archive Log) Sets: alter system set log_archive_dest_3 = 'service = Mylse' huck imports scope = Both sid = '*'; alter system huck imports set log_archive_dest_state_3 = 'DEFER' scope = Both sid = '*'; alter system set log_archive_max_processes = 5 scope = Both sid = '*'; alter system set fal_server = 'myprod2' scope = Both sid = 'myprod2'; alter system set fal_server = 'myprod1' scope = Both sid = 'myprod1'; alter system set fal_client = 'Mylse' scope = Both; (Please note, if single node install from the source, natural in Steps 4 and 5, only one is needed) If you've ready, let's do a backup (via RMAN is proposed) of the source, such as: backup compressed backupset database plus archivelog; krealjunk a standby control file: alter datab