Description：BASH-DBA BASH-DBA Oracle database real life problems and recommended solutions! Wednesday, May 28, 2014 Oracle 11g : Adding New Redo log group and Multiplexing existing ones on Primary and Standby dat
Discover bash-dba.com website stats, rating, details and status online. Read and write reviews or vote to improve it ranking. Check alliedvsaxis duplicates with related css, domain relations, most used words, social networks references. Find out where is server located. Use our online tools to find owner and admin contact info. Go to regular site
|Website / Domain:
|Website IP Address:
|Domain DNS Server:
|Google Page Rank: 0/10
||(Google Pagerank Has Been Closed)
bash-dba.com Traffic & Earnings
|Daily Unique Visitors:
|Monthly Unique Visitors:
|Yearly Unique Visitors:
bash-dba.com Keywords accounting
bash-dba.com WebSite Httpheader
||Thu, 22 Feb 2018 08:52:47 GMT
bash-dba.com Traffic Sources Chart
bash-dba.com Alexa Rank History Chart
bash-dba.com Html To Plain Text
BASH-DBA BASH-DBA Oracle database real life problems and recommended solutions! Wednesday, May 28, 2014 Oracle 11g : Adding New Redo log group and Multiplexing existing ones on Primary and Standby database Objective: 1. Multiplex the existing log file groups from currently one logfile member to two 2. Add one redo log group with two log file members on both primary and standby databases Below is the existing number of log-files on primary database. SQL > SELECT a.group#, count(a.member) FROM v$logfile a, v$log b WHERE a.group# = b.group# 2 group by a.group# 3 order by 1; GROUP# COUNT(A.MEMBER) ---------- --------------- 1 1 2 1 3 1 The above output shows that we have three logfile group with one member each. Same goes for the standby database mentioned below (group# 4,5,6) with one member each. SQL> select * from logfile; GROUP# STATUS TYPE MEMBER IS_ ------- ------- ------- ------------------------------------------ --- 1 ONLINE /u02/oracle/oradata/oradb/redo01.log NO 2 ONLINE /u02/oracle/oradata/oradb/redo02.log NO 3 ONLINE /u02/oracle/oradata/oradb/redo03.log NO 4 STANDBY /u02/oracle/oradata/oradb/sredo01.log NO 5 STANDBY /u02/oracle/oradata/oradb/sredo02.log NO 6 STANDBY /u02/oracle/oradata/orabb/sredo03.log NO Now lets get going with our two objectives at the start of this post 1. below on both primary and standby below needs to be done on both primary and standby SQL>alter system set standby_file_management=manual; 2. On Standby cancel the MRP (recovery) process. SQL> alter database recover managed standby database cancel; 3. Now lets multiplex the existing groups first On Primary: SQL>alter database add logfile member '/u03/oracle/oradata/oradb/redo01_b.log' to group 1; SQL>alter database add logfile member '/u03/oracle/oradata/oradb/redo02_b.log' to group 2; SQL>alter database add logfile member '/u03/oracle/oradata/oradb/redo03_b.log' to group 3; On Standby: SQL>alter database add standby logfile member '/u03/oracle/oradata/oradb/sredo01_b.log' to group 4; SQL>alter database add standby logfile member '/u03/oracle/oradata/oradb/sredo02_b.log' to group 5; SQL>alter database add standby logfile member '/u03/oracle/oradata/oradb/sredo03_b.log' to group 6; 4. Add the additional redo log group with multiplexed members Once multiplex of redo members done, add one more group as part of our second objective On Primary: SQL>ALTER DATABASE ADD LOGFILE GROUP 7 ('/u02/oracle/oradata/oradb/redo07.log', '/u03/oracle/oradata/oradb/redo07_b.log') SIZE 50M; On Standby: ALTER DATABASE ADD STANDBY LOGFILE GROUP 8 ('/u02/oracle/oradata/oradb/sredo08.log', '/u03/oracle/oradata/oradb/sredo08_b.log') SIZE 50M; 5: restart the MRP pricess on Standby SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE disconnect; Posted by Bilal Ashraf at 28.5.14 2 comments: Links to this post Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: Data Guard, General DBA, Oracle 11g Wednesday, April 23, 2014 RMAN: Concept and Usage of Recovery Catalog Recovery catalog is an optional database schema consisting of database objects like tables and views. RMAN uses these objects to store its repository data. The control file of each target database always serves as the primary store for the repository, however, catalog can act as a secondary storage and provides repository redundancy Information Maintained by Recovery Catalog: The recovery catalog contains information about both RMAN backups and the target database. Below is what maintained by a typical recovery catalog RMAN configuration settings RMAN-stored scripts that you create Target database tablespace and datafile information Information pertaining to datafile and archived redo log backup sets and backup pieces, as well as datafile and archived redo log copies Creating RMAN Recovery Catalog: The recovery catalog isn’t created by defualt when you install oracle database rather we must create it manually and needs to be maintained like any other oracle database . In this article I am going to create a Recovery Catalog and have a remote database registered in the catalog database. Below are the steps I have taken to create the catalog. 1. Create a separate database e.g. CATDB. Please note that we could create the recovery catalog in a target database that you want to back up using the recovery catalog, but would be an unwise choice because in such a case, losing the target database means we'll lose the recovery catalog as well. This will make the recovery much harder or even impossible 2. using SQL*Plus, connect as sys to the CATDB database created in step1 connect / as sysdba 3. Create a default tablespace for recovery catalog owner as below create tablespace cat_data datafile '/u02/oracle/oradata/CATDB/cat_data_01.dbf' size 1500M; 4. Create recovery catalog owner create user rman_cat identified by rman_cat default tablespace cat_data temporary tablespace temp quota unlimited on cat_data; 5. Once you create the recovery catalog owner, you must grant that user the recovery_catalog_owner privilege in order for that user to have the authority to work with the recovery catalog you’ll create in the next step. grant recovery_catalog_owner to rman_cat; 6. Now create the Recovery Catalog by just connecting to the recovery cataog only (not the target database) RMAN>connect catalog rman_cat/rman_cat@CATDB connected to recovery catalog database RMAN> RMAN> create catalog; Below is how we can register the database to the newly created catalog Registering Target Databases: You want to use a recovery catalog to manage the RMAN repository data for a new database. rman target / catalog rman_cat/rman_cat@catdb RMAN> register database; You can ensure that you have successfully registered the target database by issuing the list incarnation command. RMAN> list incarnation; Make sure from the remote server from where you are logging in to connect to the recovery catalog has the recovert catalog database (CATDB) tns entry available in the tnsnames.ora file of target database. Posted by Bilal Ashraf at 23.4.14 No comments: Links to this post Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: RMAN Friday, July 12, 2013 RMAN Incremental Backups to Roll Forward a Physical Standby Database (Lags far behind the primary database) RMAN incremental backups can be used to sync a physical standby database with the primary database. We can use the RMAN BACKUP INCREMENTAL FROM SCN command to create a backup on the primary database that starts at the current SCN of the standby, which can then be used to roll the standby database forward in time. So here are the steps, Stop Redo Apply on the standby database: SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL; On the standby database, get the SCN for the incremental backup. SQL> SELECT CURRENT_SCN FROM V$DATABASE; CURRENT_SCN ----------- 255797 Connect to the primary database as the RMAN target and create an incremental backup from the current SCN RMAN>...
bash-dba.com Similar Website
||??? ???, DBA ???? ???
||What is "DBA to DBA" ?
DBA to DBA
||Boisdarc Bash |
||Welcome to the DBA