ALTER DATABASE ADD STANDBY LOGFILE GROUP

version 10 & 11g
creating standby logfile groups on primary db is optional or needed? what could be advantages of both?
I am reading 2 articles one is creating that other not?
http://www.orafaq.com/node/2030
& 736863.1 Notes

DBA2008 wrote:
version 10 & 11g
creating standby logfile groups on primary db is optional or needed? what could be advantages of both? at primary database it is optional ,but it would be good candidate for switchover activity , it makes ensure that if you make any planned maintenance activity at primary site and switchover within yours data guard environment from primary database to physcial standby database ,if you create standby redo log at primary database it is not in use right now but it will be used when yours primary database switch to standby database after switching to physical standby databsae as a primary database.
Khurram

Similar Messages

  • I missed to add Standby Logfile groups? What now?

    Hi there
    I have created a Standby database in a test environment using RMAN   (followed the procedure given here -> URL:  Creating a Standby Database with Recovery Manager).
    When I tried to start the recovery on Standby, I got the following error:
    [code]
    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT;
    ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT
    ERROR at line 1:
    ORA-38500: USING CURRENT LOGFILE option not available without stand
    SQL> select NAME, OPEN_MODE, GUARD_STATUS, DATABASE_ROLE from v$database;
    NAME      OPEN_MODE  GUARD_S DATABASE_ROLE
    PRIM      MOUNTED    NONE    PHYSICAL STANDBY
    SQL>
    [/code]
    I missed the step to add standby logfile groups. Do I need to recreate the Standby database now? I mean, add standby logfile groups to Primary, then take full RMAN backup and recreate the standby database (following the procedure described in the URL above)?
    I am using Oracle 10gR2 on OEL 5.8.
    Please advise!
    Best regards

    OK thank you both - I have added the standby logfile groups both on Primary and Standby (mounted) database and I was able to successfully issue the following command:
    ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT;
    I hope this was the right thing to do under the circumstances, right?
    And now there seems to be a gap:
    PRIM_SQL> SELECT MAX(SEQUENCE#) FROM V$ARCHIVED_LOG;
    MAX(SEQUENCE#)
                11
    STDBY_SQL> SELECT MAX(SEQUENCE#) FROM V$LOG_HISTORY;
    MAX(SEQUENCE#)
                 9
    I issued "alter system switch logfile" few times on the Primary but logs don't seem to be shipping? How to check this and fix?
    EDIT: OK I checked the Primary alert log file and see following messages:
    Error 1031 received logging on to the standby
    Tue Jun 25 15:22:43 2013
    Errors in file /u01/app/oracle/admin/prim/bdump/prim_arc0_6880.trc:
    ORA-01031: insufficient privileges
    PING[ARC0]: Heartbeat failed to connect to standby 'stan'. Error is 1031.
    Tue Jun 25 15:27:43 2013
    Error 1031 received logging on to the standby
    Tue Jun 25 15:27:43 2013
    Errors in file /u01/app/oracle/admin/prim/bdump/prim_arc0_6880.trc:
    ORA-01031: insufficient privileges
    PING[ARC0]: Heartbeat failed to connect to standby 'stan'. Error is 1031.
    Tue Jun 25 15:32:43 2013
    I do have password file both on Primary and Standby servers. What is this "ORA-01031: insufficient privileges" referring to?
    EDIT#2:
    I copied the password file from Primary DB server to Standby server (with same name "orapwprim" - previously I used "orapwstan" name for standby password file) and the "login issue" is resolved. But now I see following error in the alert log file on Primary:
    PING[ARC0]: Heartbeat failed to connect to standby 'stan'. Error is 1031.
    Tue Jun 25 15:48:08 2013
    ARCH: Possible network disconnect with primary database
    Any clues here?
    EDIT#3:
    Sorry I was a bit impatient I guess.The logs a re being shipped and applied now.
    Thank you both!
    Best regards
    Message was edited by: user130038 (added alert log file info)
    Message was edited by: user130038 (Added EDIT#2)
    Message was edited by: user130038 (added EDIT#3)

  • Alter database clear unarchived logfile group... who, what?

    I am the sole DBA for our site, all of them running RHEL 5, Oracle 11.2.0.3.
    I recently (within the last hour), received a text message from one of our databases that poll the alert.log...
    ORA-1031 signalled during: ALTER DATABASE CLEAR UNARCHIVED LOGFILE GROUP 3
    Unfortunately, the 'audit database' was not enabled (it is now!), and the trace file generated did not contain anything of use.
    I know someone has been loading data since 1:30pm up until near the time I received this text, and I'm wondering if he is mucking in the system, or if this command can somehow be generated automatically by Oracle. If so, I certainly wouldn't expect an ORA-1031insufficient permissions error....
    I checked my v$log, v$logfile, and did a log switch just to check if any possibility of redo log corruption, but all looks fine.
    Has anyone else ever had random Oracle errors like this?....

    Hi,
    That's someone manually doing something when they really don't know what they are doing. I've only had to run that command once in 16 years as a dba. Oracle wouldn't ever run that itself.
    Cheers,
    Harry

  • What is the Use of  "Alter database activate standby database"

    Hi ,
    I appreciate your time.
    I just wanted to know what is the use of "Alter database activate standby database" command when doing the failover. How different it will act in failover process. Can we use this command in SwitchOver.
    Thanks in advance.

    Hi Uwe Hesse,
    Wonderfull... good info....
    So my understanding is that the use of "ACTIVATE PHYSICAL STANDBY DATABASE" is conditional and depends on the redo log gap and the Database status(Able to mount or not).
    Condition 1: If the Db is in Mount state and Redo log gap is successfully filled.
    1) Flush any unsent redo from the primary database to the target standby database.
    SQL> ALTER SYSTEM FLUSH REDO TO target_db_name;
    Note: If the above Statement Completes successfully without any errors.
    2) Stop Redo Apply.
    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
    3) Finish applying all received redo data.
    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH;
    4) Verify that the target standby database is ready to become a primary database.
    SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
    5) Switch the physical standby database to the primary role.
    SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY WITH SESSION SHUTDOWN;
    Condition 2: If the DB is not able Mount and Redo Gap can't be filled.
    Important Note: If the the above command in STEP3 gives error, some received redo data was not applied. Try to resolve the cause of the error and re-issue the statement before proceeding.
    If the error condition cannot be resolved, a failover can still be performed (with some data loss) by issuing the following SQL statement on the target standby database:
    SQL> ALTER DATABASE ACTIVATE PHYSICAL STANDBY DATABASE;
    Thanks in advance.

  • RMAN-11001: alter database mount standby database

    I'm doing a duplicate for a standby database and I'm getting this error
    Oracle 8i Tru64
    RMAN-03002: failure during compilation of command
    RMAN-03013: command type: Duplicate Db
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-03006: non-retryable error occurred during execution of command: sql
    RMAN-07004: unhandled exception during command execution on channel clone_defaul
    t
    RMAN-20000: abnormal termination of job step
    RMAN-11003: failure during parse/execution of SQL statement: alter database moun
    t standby database
    RMAN-11001: Oracle Error: ORA-03113: end-of-file on communication channel
    Recovery Manager complete.
    Any help please

    Check for parameter mismatches between parameter file and control file.
    Check your parameter file. Check db_name paramter in paramter file used in the standby database.

  • ORA-301 Signalled during: ALTER DATABASE ...

    Hi,
    I tried to add 4 standby redologs to our standby setup, and first file went well.
    theothers already got error ORA-301:
    ALTER DATABASE ADD STANDBY LOGFILE GROUP 8 '/export/home/oracle/logs/redo8.log' SIZE 2G
    Fri May 31 15:31:22 2013
    Completed: ALTER DATABASE ADD STANDBY LOGFILE GROUP 8 '/export/home/oracle/logs/redo8.log' SIZE 2G
    ALTER DATABASE ADD STANDBY LOGFILE GROUP 9 '/export/home/oracle/logs/redo9.log' SIZE 2G
    ORA-301 signalled during: ALTER DATABASE ADD STANDBY LOGFILE GROUP 9 '/export/home/oracle/logs/redo9.log' SIZE 2G...
    ALTER DATABASE ADD STANDBY LOGFILE GROUP 10 '/export/home/oracle/logs/redo10.log' SIZE 2G
    ORA-301 signalled during: ALTER DATABASE ADD STANDBY LOGFILE GROUP 10 '/export/home/oracle/logs/redo10.log' SIZE 2G...
    ALTER DATABASE ADD STANDBY LOGFILE GROUP 11 '/export/home/oracle/logs/redo11.log' SIZE 2G
    ORA-301 signalled during: ALTER DATABASE ADD STANDBY LOGFILE GROUP 11 '/export/home/oracle/logs/redo11.log' SIZE 2G...
    Fri May 31 16:33:39 2013
    I tried to track any info in the web and metalink, but it's the first time I encounter an ORA error with no documentation... :(
    Some facts:
    The oracle is 11.2.0 on Linux
    There is no space issue on disk
    Thanks for any help/ideas...

    thanks for the reply.
    first one I stated in the original post. there is tons of storage :)
    for the others 2 -
    user has priviledge... he created the first file succesfully...
    those files do not exist on the disk already.
    Thanks

  • Can't switch standby logfiles to status=active

    Hi DBA's
    I'm trying to create logical standby on 10.2 on fedora 6 on manual http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#g88234
    I can't create proper working standby redo logs.
    ALTER DATABASE ADD STANDBY LOGFILE GROUP 4
    ('/u01/app/oracle/oradata/ORCL/onlinelog/log4a.log',
    '/u01/app/oracle/flash_recovery_area/ORCL/onlinelog/log4b.log') SIZE 50M;
    then create the rest of standby redos and switch logfile:
    ALTER SYSTEM SWITCH LOGFILE;
    when:
    SQL> SELECT GROUP#,THREAD#,SEQUENCE#,ARCHIVED,STATUS FROM V$STANDBY_LOG;
    GROUP# THREAD# SEQUENCE# ARC STATUS
    4 0 0 YES UNASSIGNED
    5 0 0 YES UNASSIGNED
    6 0 0 YES UNASSIGNED
    What to do?
    Edited by: val75 on Jun 21, 2009 11:08 PM

    try switch log at primay
    please try to run this Command and then open the primary database.
    alter database set standby database to maximize performance;
    alter database open;

  • Standby logfiles

    In the following doc: http://download.oracle.com/docs/cd/B28359_01/server.111/b28294/log_transport.htm#BABCBEGJ
    it says:
    For example, assume that the redo log on the redo source database has two redo log groups and that each of those contain one 500 MB redo log file. In this case, the standby redo log should have at least 3 standby redo log groups to satisfy the requirement that a standby redo log must have at least one more redo log group than the redo log at the redo source database.
    The following SQL statements might be used to create a standby redo log that is appropriate for the previous scenario:
    ALTER DATABASE ADD STANDBY LOGFILE
    ('/oracle/dbs/slog1.rdo') SIZE 500M;
    ALTER DATABASE ADD STANDBY LOGFILE
    ('/oracle/dbs/slog2.rdo') SIZE 500M;
    ALTER DATABASE ADD STANDBY LOGFILE
    ('/oracle/dbs/slog3.rdo') SIZE 500M;
    The doc says there needs to be one more group and then demonstrates creating no seperate groups. Did they mean to say one more file or did they mean to create groups such as this:
    ALTER DATABASE ADD STANDBY LOGFILE GROUP 1...
    ALTER DATABASE ADD STANDBY LOGFILE GROUP 2...
    ALTER DATABASE ADD STANDBY LOGFILE GROUP 3....

    In the example the primary database has two log groups, and then they create 3 standby log groups on the standby. This is exactly what they recommend (standby = primary + 1).

  • Standby logfile missing error

    Hello all,
    I am getting this following error in standby alertlog file.
    ORA-00313: open failed for members of log group 8 of thread 2
    ORA-00312: online log 8 thread 2: '+DG_FLASH/hsstl/onlinelog/group_8.273.779638759'
    ORA-17503: ksfdopn:2 Failed to open file +DG_FLASH/hsstl/onlinelog/group_8.273.779638759
    ORA-15012: ASM file '+DG_FLASH/hsipstl/onlinelog/group_8.273.779638759' does not exist
    ORA-00312: online log 8 thread 2: '+DG_DATA/hsstl/onlinelog/group_8.1766.779638759'
    ORA-17503: ksfdopn:2 Failed to open file +DG_DATA/hsstl/onlinelog/group_8.1766.779638759
    ORA-15012: ASM file '+DG_DATA/hsipstl/onlinelog/group_8.1766.779638759' does not exist
    When i manually check the diskgroup '+DG_FLASH, +DG_DATA, i can see the group_8 file with some other numbers.
    Kindly let me know how to proceed for that. oracle 11g database, standalone standby database in aix box
    My guess is control file is still thinking that the group 8 file is present and looks for it when starting the standby, but actually that file is not there in the diskgroup. instead some other filename is there for the same group.
    Either i want to update the control file about the new log group 8, or drop the log 8 group, delete the log 8 group files from the disgroups +DG_FLASH, +DG_DATA and create a new log 8 group
    Kindly suggest
    Regards,

    Test
    SQL> Select GROUP#, THREAD#, SEQUENCE#, BYTES from v$standby_log;
      GROUP# THREAD# SEQUENCE# BYTES
      4 1 0 52428800
      5 1 1327 52428800
      6 1 0 52428800
    SQL> alter database recover managed standby database cancel;
    Database altered.
    SQL> ALTER DATABASE ADD STANDBY LOGFILE GROUP 7 '/u01/app/oracle/oradata//redo07.log' SIZE 50M;
    Database altered.
    SQL> alter database recover managed standby database disconnect from session;
    Database altered.
    SQL> Select GROUP#, THREAD#, SEQUENCE#, BYTES from v$standby_log;
      GROUP# THREAD# SEQUENCE# BYTES
      4 1 0 52428800
      5 1 1327 52428800
      6 1 0 52428800
      7 0 0 52428800 
    ALTER DATABASE CLEAR LOGFILE GROUP 7; 
    SQL> alter database recover managed standby database cancel;
    Database altered.
    SQL> ALTER DATABASE CLEAR LOGFILE GROUP 7;
    Database altered.
    SQL> alter database recover managed standby database disconnect from session;
    Database altered.
    SQL> Select GROUP#, THREAD#, SEQUENCE#, BYTES from v$standby_log;
      GROUP# THREAD# SEQUENCE# BYTES
      4 1 0 52428800
      5 1 1327 52428800
      6 1 0 52428800
      7 0 0 52428800
    SQL> /
      GROUP# THREAD# SEQUENCE# BYTES
      4 1 1330 52428800
      5 1 0 52428800
      6 1 0 52428800
      7 0 0 52428800
    What I noticed is no matter how many switches I do the Standby only uses group 4 and 5. If I recreate with a Thread number it seems to work.
    SQL> alter database recover managed standby database cancel;
    Database altered.
    SQL> ALTER DATABASE DROP STANDBY LOGFILE GROUP 7;
    Database altered.
    SQL> !rm /u01/app/oracle/oradata//redo07.log
    SQL> ALTER DATABASE ADD STANDBY LOGFILE THREAD 1 GROUP 7 '/u01/app/oracle/oradata//redo07.log' SIZE 50M;
    Database altered.
    SQL> alter database recover managed standby database disconnect from session;
    Database altered.
    SQL> Select GROUP#, THREAD#, SEQUENCE#, BYTES from v$standby_log;
      GROUP# THREAD# SEQUENCE# BYTES
      4 1 0 52428800
      5 1 1343 52428800
      6 1 0 52428800
      7 1 0 52428800
    SQL>
    Check
    SQL> select GROUP#,BYTES/1024/1024/1024 , STATUS, FIRST_TIME,NEXT_TIME from v$standby_log;
      GROUP# BYTES/1024/1024/1024 STATUS FIRST_TIM NEXT_TIME
      4 .048828125 UNASSIGNED
      5 .048828125 ACTIVE 29-NOV-13
      6 .048828125 UNASSIGNED
      7 .048828125 UNASSIGNED
    SQL>

  • ORA-01184: logfile group 1 already exists

    After startup nomount, I try to create database as follows:
    CREATE DATABASE SISDEV04
         LOGFILE GROUP 1 '/sisdev04/dbs/log01a.dbf'
    SIZE 10M
         ,     GROUP 1 '/sisdev04/dbs/log01b.dbf'
    SIZE 10M
         ,     GROUP 2 '/sisdev04/dbs/log02a.dbf'
    SIZE 10M
         ,     GROUP 2 '/sisdev04/dbs/log02b.dbf'
    SIZE 10M
         NOARCHIVELOG
         CHARACTER SET ZHT16BIG5
         NATIONAL CHARACTER SET ZHT16BIG5
         DATAFILE '/sisdev04/dbs/system01.dbf'      
              SIZE 210M AUTOEXTEND OFF
         , '/sisdev04/dbs/rbs01.dbf'
    SIZE 105M AUTOEXTEND OFF
         , '/sisdev04/dbs/temp01.dbf'
    SIZE 105M AUTOEXTEND OFF
         , '/sisdev04/dbs/users01.dbf'
    SIZE 1050M AUTOEXTEND OFF
         , '/sisdev04/dbs/ts_index_ivr01.dbf'
    SIZE 105M AUTOEXTEND OFF
         , '/sisdev04/dbs/ts_ivr01.dbf'
    SIZE 21M AUTOEXTEND OFF
         , '/sisdev04/dbs/ts_ems01.dbf'
    SIZE 21M AUTOEXTEND OFF
         , '/sisdev04/dbs/ts_index_ems01.dbf'
    SIZE 21M AUTOEXTEND OFF
    However, I receive such error:
    ORA-01501: CREATE DATABASE failed
    ORA-01184: logfile group 1 already exists
    I have checked that there is no files in '/sisdev04/dbs/' before I issue the command, what can I do?

    Hello...
    Excuse me..
    May be I have same problem..
    I use Oracle Streams to replicate table in one to another database. While i configure setup replication occur this errror.
    How to resolve this problem i have?
    SQL> SQL> Connecting to source database as STRMADMIN
    SQL> Executing ..
    SQL> connect STRMADMIN/******
    SQL> Connected.
    SQL> SQL> SQL> Executing ..
    SQL> DROP DATABASE LINK DBSTG
    SQL>
    Database link dropped.
    SQL> SQL> Executing ..
    SQL> CREATE DATABASE LINK DBSTG connect to strmadmin identified by ****** using '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=10.4.10.21)(PORT=1521)))(CONNECT_DATA=(SID=dbstg)(server=DEDICATED)))'
    SQL>
    Database link created.
    SQL> Executing ..
    SQL> ALTER SYSTEM SET LOG_ARCHIVE_CONFIG='DG_CONFIG=(dbstg,dbsd)' scope=both
    SQL>
    System altered.
    SQL> Executing ..
    SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_3='SERVICE="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=10.4.10.21)(PORT=1521)))(CONNECT_DATA=(SID=dbstg)(server=DEDICATED)))" ASYNC NOREGISTER VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=dbstg' scope=both
    SQL>
    System altered.
    SQL> Executing ..
    SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_3=DEFER scope=both
    SQL>
    System altered.
    SQL> CONNECT TO DOWNSTREAM DB AND SETUP LOG PARAMS
    SQL> Executing ..
    SQL> connect strmadmin/******@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=10.4.10.21)(PORT=1521)))(CONNECT_DATA=(SID=dbstg)(server=DEDICATED)))
    SQL> Connected.
    SQL> SQL> Executing ..
    SQL> DROP DATABASE LINK DBSD
    SQL>
    Database link dropped.
    SQL> SQL> SQL> Executing ..
    SQL> CREATE DATABASE LINK DBSD connect to STRMADMIN identified by ****** using '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=t0031)(PORT=1521)))(CONNECT_DATA=(SID=dbsd)(server=DEDICATED)))'
    SQL>
    Database link created.
    SQL> Executing ..
    SQL> CREATE OR REPLACE DIRECTORY STANDBY_LOG_LOC AS '/u01/app/oracle/admin/dbstg/srl_dbsd/'
    SQL>
    Directory created.
    SQL> 1* CREATE OR REPLACE DIRECTORY STANDBY_LOG_LOC AS '/u01/app/oracle/admin/dbstg/srl_dbsd/'
    SQL> Executing ..
    SQL> ALTER SYSTEM SET LOG_ARCHIVE_CONFIG='DG_CONFIG=(dbstg,dbsd)' scope=both
    SQL>
    System altered.
    SQL> Executing ..
    SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_3=ENABLE scope=both
    SQL>
    System altered.
    SQL> Executing ..
    SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_3='LOCATION=/u01/app/oracle/admin/dbstg/srl_dbsd/ VALID_FOR=(STANDBY_LOGFILE,PRIMARY_ROLE)'scope=both
    SQL>
    System altered.
    SQL> Executing ..
    SQL> ALTER DATABASE ADD STANDBY LOGFILE GROUP 4 ('/u01/app/oracle/admin/dbstg/srl_dbsd/log4a.rdo', '/u01/app/oracle/admin/dbstg/srl_dbsd/slog4b.rdo') SIZE 104857600
    SQL> ALTER DATABASE ADD STANDBY LOGFILE GROUP 4 ('/u01/app/oracle/admin/dbstg/srl_dbsd/log4a.rdo', '/u01/app/oracle/admin/dbstg/srl_dbsd/slog4b.rdo') SIZE 104857600
    ERROR at line 1:
    ORA-01184: logfile group 4 already exists
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    Error from SQLPLUS: 160

  • Oracle ORA_16000 when trying to add standby instance to existing rac node

    I attempted to use dbca to add a new standby instance to an existing cluster. The cluster is 4 nodes, Linux RHEL 5.3 Oracle 11.1.0.7. Also using ASM, asmlib, ocfs2 and shared block devices.
    ASM instances are up and functional on all nodes. current config appears to be running normally and correctly.
    I have a 4 instance database running on the cluster. I also have 3 physical standby active data guard instances running on 3 of the nodes. I wanted to add a new ADG instance to the 4th node.
    While running dbca I received ORA-00604 and ORA-16000.
    The active data guard database was open (read only) and redo apply was on. I am using data guard broker as well, but not grid control.
    Does anyone have a procedure for adding an instance in this environment? Do I need to have the standby in mount state? If dbca won't work does anyone have a manual procedure for adding a new instance?
    Thanks

    zulo
    Let's say you adding node nusclust160## to you existing cluster and dbca is a pain to use.
    Extend clusterware to the nusclust160## server.
    re: Page 64 of Oracle® Clusterware Administration and Deployment Guide 11g Release 1 (11.1)
    1a.
    Add undo tablespace to support additional node.
    Re-check space for DATA1 on nusclust16007 and /dbdata/ORADB on sun16109.
    As of Thursday, May 21, 2009 the DATA1 asm group has 53,584M free.
    As of Thursday, May 21, 2009 the /dbdata/ORADB has 77G free.
    In a separate terminal window on nusclust16007 run the following in sqlplus
    CREATE UNDO TABLESPACE UNDOTBS4 datafile '+DATA1' SIZE 13300M AUTOEXTEND ON ;
    This will take a long time to create this tablespace. Please minimize the window after submitting the ddl and move on to the next step.
    1b.
    Insure .bash_profile on nusclust160## should look like this:
    vi .bash_profile
    export ORACLE_HOSTNAME=nusclust160##
    export ORACLE_SID=ORADB4
    export ORA_CRS_BASE=/apps/ocr/oracle
    export ORACLE_BASE=/apps/dbs/oracle
    export PATH=/usr/ccs/bin:/usr/X/bin:/usr/bin:/usr/sfw/bin:/usr/sbin:/usr/local/bin
    export server=`uname -n`
    export PS1="$ORACLE_SID@$HOSTNAME >"
    alias cls='clear'
    alias More='more'
    alias ll='ls -lt | more'
    Gather IP addresses for fourth node from /etc/hosts:
    222.65.125.### nusclust160##
    222.65.125.### nusclust160##-vip
    10.333.248.### nusclust160##-priv
    2. Start Oracle Universal Installer:
    Go to CRS_home/oui/bin and run the addNode.sh script on one of the existing
    nodes. Oracle Universal Installer runs in add node mode.
    The Oracle inventory on nusclust16007, nusclust16008, and nusclust16036 are found under:
    /home/oracle/oraInventory
    Use a X windows enabled session (The OUI takes 33 minutes)
    cd /apps/ocr/oracle/product/11.1.0/crs/oui/bin
    ./addNode.sh
    a. In the first screen specify a new node as :
    Public Node Name:          nusclust160##
    Private Node Name:     nusclust160##-priv
    Virtual Host Name:     nusclust160##-vip
    If you receive the error:
    " tar. ./bin/racgvip.orig: Permission denied"
    Do the following:
    cd /apps/ocr/oracle/product/11.1.0/crs/bin
    ls -al racgvip.orig
    paste here:
    chown root:oinstall racgvip.orig
    chmod 771 racgvip.orig
    should now show:
    -rwxrwx--x 1 root oinstall 19213 Feb 11 08:36 racgvip.orig
    As root:
    a.
    On nusclust160##:
    cd /home/oracle/oraInventory
    ./orainstRoot.sh
    b.
    On nusclust16007:
    cd /apps/ocr/oracle/product/11.1.0/crs/install
    ./rootaddnode.sh
    clscfg: EXISTING configuration version 4 detected.
    clscfg: version 4 is 11 Release 1.
    Attempting to add 1 new nodes to the configuration
    Using ports: CSS=49895 CRS=49896 EVMC=49898 and EVMR=49897.
    node <nodenumber>: <nodename> <private interconnect name> <hostname>
    node 4: nusclust160## nusclust160##-priv nusclust160##
    Creating OCR keys for user 'root', privgrp 'root'..
    Operation successful.
    /apps/ocr/oracle/product/11.1.0/crs/bin/srvctl add nodeapps -n nusclust160## -A nusclust160##-vip/255.255.255.224/bge0
    c.
    On nusclust160##:
    cd /apps/ocr/oracle/product/11.1.0/crs/
    ./root.sh
    WARNING: directory '/apps/ocr/oracle/product/11.1.0' is not owned by root
    WARNING: directory '/apps/ocr/oracle/product' is not owned by root
    WARNING: directory '/apps/ocr/oracle' is not owned by root
    Checking to see if Oracle CRS stack is already configured
    OCR LOCATIONS = /raw/ocr/ocrconf1,/raw/ocr/ocrconf2
    OCR backup directory '/apps/ocr/oracle/product/11.1.0/crs/cdata/rac_cluster' does not exist. Creating now
    Setting the permissions on OCR backup directory
    Setting up Network socket directories
    Oracle Cluster Registry configuration upgraded successfully
    The directory '/apps/ocr/oracle/product/11.1.0' is not owned by root. Changing owner to root
    The directory '/apps/ocr/oracle/product' is not owned by root. Changing owner to root
    The directory '/apps/ocr/oracle' is not owned by root. Changing owner to root
    clscfg: EXISTING configuration version 4 detected.
    clscfg: version 4 is 11 Release 1.
    Successfully accumulated necessary OCR keys.
    Using ports: CSS=49895 CRS=49896 EVMC=49898 and EVMR=49897.
    node <nodenumber>: <nodename> <private interconnect name> <hostname>
    node 1: nusclust16007 nusclust16007-priv nusclust16007
    node 2: nusclust16008 nusclust16008-priv nusclust16008
    node 3: nusclust16036 nusclust16036-priv nusclust16036
    clscfg: Arguments check out successfully.
    NO KEYS WERE WRITTEN. Supply -force parameter to override.
    -force is destructive and will destroy any previous cluster
    configuration.
    Oracle Cluster Registry for cluster has already been initialized
    Startup will be queued to init within 30 seconds.
    Adding daemons to inittab
    Expecting the CRS daemons to be up within 600 seconds.
    Cluster Synchronization Services is active on these nodes.
    nusclust16007
    nusclust16008
    nusclust16036
    nusclust160##
    Cluster Synchronization Services is active on all the nodes.
    Waiting for the Oracle CRSD and EVMD to start
    Oracle CRS stack installed and running under init(1M)
    4. After this is done crs_stat -t will show nusclust160## in the crs i.e.
    I see:
    Name Type Target State Host
    ora....160##.gsd application ONLINE ONLINE sun...160##
    ora....160##.ons application ONLINE OFFLINE
    ora....160##.vip application ONLINE ONLINE sun...160##
    Do not be concerned about ora.nusclust160##.ons being OFFLINE, as that will be fixed shortly in a step that follows this one.
    5. As oracle :
    On nusclust16007:
    cd /apps/ocr/oracle/product/11.1.0/crs/bin
    ./racgons add_config nusclust160##:6251
    This should take about one second to run.
    If it says that it has already been added to the OCR you are fine.
    If it hangs, you may need to reboot all servers to clear this issue.
    6. Insure new node is properly added to ocr by running
    On nusclust16007:
    ocrdump
    Check for the entries that show:
    [DATABASE.ONS_HOSTS.nusclust160##.PORT]
    ORATEXT : 6251
    7. Check that your cluster is integrated and that the cluster is not divided into
    partitions by completing the following operations:
    On nusclust16007:
    cd /apps/ocr/oracle/product/11.1.0/crs/bin
    ./cluvfy comp clumgr -n all -verbose
    Should see Verification of cluster manager integrity was successful.
    8.
    Use the following command to perform an integrated validation of the Oracle
    Clusterware setup on all of the configured nodes, both the preexisting nodes
    and the nodes that you have added:
    AS oracle on nusclust16007:
    cluvfy stage -post crsinst -n all -verbose
    Post-check for cluster services setup was successful.
    good: Post-check for cluster services setup was successful.
    9.
    On nusclust160## as oracle run the following:
    cd /apps/ocr/oracle/product/11.1.0/crs/bin
    ./crs_stat -t | grep OFFLINE
    If you see this:
    ora.nusclust160##.ons application ONLINE OFFLINE
    then run this:
    ./crs_start -all
    After:
    ./crs_stat -t
    ora.nusclust160##.ons application ONLINE ONLINE nusclust160##
    If you see the above then you can move on the next step.
    Adding database binaries to the nusclust160## server and setting up the listener.
    1.
    From nusclust16007:
    Open an X window (The OUI part takes 13 minutes)
    cd /apps/dbs/oracle/product/11.1.0/db_1/oui/bin
    ./runInstaller -addNode ORACLE_HOME=/apps/dbs/oracle/product/11.1.0/db_1 $*
    You should get a prompt to specify a new node, in this case you should see nusclust160## where you will need to put a check mark beside it.
    2.
    from nusclust160##:
    Eventually you will be prompted to run the following as root on the new node
    On nusclust160##
    cd /apps/dbs/oracle/product/11.1.0/db_1
    ./root.sh
    Running Oracle 11g root.sh script...
    The following environment variables are set as:
    ORACLE_OWNER= oracle
    ORACLE_HOME= /apps/dbs/oracle/product/11.1.0/db_1
    Enter the full pathname of the local bin directory: [usr/local/bin]:
    Copying dbhome to /usr/local/bin ...
    Copying oraenv to /usr/local/bin ...
    Copying coraenv to /usr/local/bin ...
    Creating /var/opt/oracle/oratab file...
    Entries will be added to the /var/opt/oracle/oratab file as needed by
    Database Configuration Assistant when a database is created
    Finished running generic part of root.sh script.
    Now product-specific root actions will be performed.
    Finished product-specific root actions.
    3. verification
    Now set up the .bash_profile and .asm profile to on nusclust160## to support new ORADB4 and +ASM4 instances for the oracle userid.
    On nusclust160##:
    cp .bash_profile .bash_profile.bak
    On nusclust16007:
    sftp nusclust160##
    put .bash_profile
    On nusclust160##:
    vi .bash_profile
    change ORALCE_SID to ORADB4
    cp .bash_profile .asm
    vi .asm
    change ORALCE_SID to +ASM4 in .asm file
    which sqlplus
    Should show the path below is $PATH environmental variable is set correctly.
    /apps/dbs/oracle/product/11.1.0/db_1/bin/sqlplus
    On nusclust160##:
    oifcfg getif
    This should show:
    ce4 10.333.248.192 global cluster_interconnect
    ce5 222.65.125.128 global public
    4.
    Run Netbackup Oracle Agent link script.
    As oracle make sure ORACLE_HOME is fined.
    env | grep ORACLE_HOME
    then
    cd /usr/openv/netbackup/bin/
    ./oracle_link
    ls -al $ORACLE_HOME/lib/libobk.so
    should show:
    /apps/dbs/oracle/product/11.1.0/db_1/lib/libobk.so -> /usr/openv/netbackup/bin/libobk.so64.1
    5.
    On the target node, run the Net Configuration Assistant (NETCA) to add a
    listener. Add a listener to the target node by running NETCA from the target node and
    selecting only the target node on the Node Selection page.
    I shall do the following on nusclust160## using X Windows
    Now before I do this I see:
    crs_stat -t
    ora.nusclust160##.gsd application ONLINE ONLINE nusclust160##
    ora.nusclust160##.ons application ONLINE ONLINE nusclust160##
    ora.nusclust160##.vip application ONLINE ONLINE nusclust160##
    Connect to nusclust160## and open up X windows session.
    netca
    Choose Cluster configuration.
    select nusclust160## as the node to configure.
    Choose Listener configuration, then Add.
    When it prompts you for a listener name choose LISTENER as it will append _NUSCLUST160##(server name) to end of the LISTENER name to make a complete listener name. 
    At this point you will have listener to support the new node in the crs.
    now
    crs_stat -t
    will show:
    ora....0#.lsnr application ONLINE ONLINE nusclust160##
    ora.nusclust160##.gsd application ONLINE ONLINE nusclust160##
    ora.nusclust160##.ons application ONLINE ONLINE nusclust160##
    ora.nusclust160##.vip application ONLINE ONLINE nusclust160##
    At this point the necessary crs entries for gsd, ons, vip, and the listener on nusclust160## all we need now are the ORADB4 and +ASM4 instances added.
    III. 7/11/2009 7:40 AM Sat [120 min] NTTA DBA
    Use NON dbca method to create additional instances on the nusclust160## server. This will involve a complete shutdown of all RAC instances.
    1.
    Undo tablespace creation was taken care of in Step I,1. Check on the progress of the creation of tablespace UNDOTBS4 in the minimized window. Should see tablespace on primary and physical standby databases.
    2. First we shall set up the +ASM4 instance on nusclust160## and add it to the cluster.
    On nusclust160##
    cd $ORACLE_HOME/dbs
    vi init+ASM4.ora
    # Copyright (c) 1991, 2001, 2002 by Oracle Corporation
    # Cluster Database
    cluster_database=true
    cluster_database_instances=6
    # Miscellaneous
    diagnostic_dest=/apps/dbs/oracle
    instance_type=asm
    # Pools
    large_pool_size=12M
    asm_diskgroups='DATA1','ARCH','REDO1','REDO2'
    asm_diskstring='/raw/asm'
    +ASM1.instance_number=1
    +ASM2.instance_number=2
    +ASM3.instance_number=3
    +ASM4.instance_number=4
    3.
    On nusclust16007
    cd $ORACLE_HOME/dbs
    sftp nusclust160##
    put orapw+ASM1 /apps/dbs/oracle/product/11.1.0/db_1/dbs
    put orapwORADB1 /apps/dbs/oracle/product/11.1.0/db_1/dbs
    4.
    On nusclust160##
    cd $ORACLE_HOME/dbs
    cp orapw+ASM1 orapw+ASM4
    cp orapwORADB1 orapwORADB4
    5.
    On nusclust160##
    cd $HOME
    . ./.asm
    sqlplus '/ as sysasm'
    startup
    create spfile from pfile='/apps/dbs/oracle/product/11.1.0/db_1/dbs/init+ASM4.ora' ;
    shutdown immediate ;
    startup
    show parameters spfile
    6. Now that we have a running asm instance add it the cluster.
    On nusclust160##
    srvctl add asm -n nusclust160## -i +ASM4 -o /apps/dbs/oracle/product/11.1.0/db_1
    srvctl enable asm -n nusclust160## -i +ASM4
    7. Now that we have an asm instance let's set up a database instance.
    On nusclust16007/ORADB1 :
    alter system set cluster_database_instances=6 scope=spfile ;
    alter system set instance_name=ORADB4 scope=spfile sid='ORADB4' ;
    alter system set instance_number=4 scope=spfile sid='ORADB4' ;
    alter system set local_listener=LISTENER_ NUSCLUST160## scope=both sid='ORADB4' ;
    alter system set thread=4 scope=both sid='ORADB4' ;
    alter system set undo_tablespace=UNDOTBS4 scope=both sid='ORADB4' ;
    alter database add logfile thread 4 group 28 ('+REDO1', '+REDO2' ) size 100M ;
    alter database add logfile thread 4 group 29 ('+REDO1', '+REDO2' ) size 100M ;
    alter database add logfile thread 4 group 30 ('+REDO1', '+REDO2' ) size 100M ;
    alter database add logfile thread 4 group 31 ('+REDO1', '+REDO2' ) size 100M ;
    alter database enable public thread 4;
    Need to add 5 groups to support standby
    So at the end of the day 900M will be added to REDO1(29,577M free) and 900M will be added to REDO2 (29,577M free).
    8. Set up init.ora, listener.ora, and tnsnames.ora for ORADB4 on nusclust160##.
    a. init.ora set up
    cd $ORACLE_HOME/dbs
    vi initORADB4.ora
    SPFILE='+DATA1/ORADB/spfileORADB.ora'
    b. add entries to tnsnames.ora:
    ORADB4 =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = nusclust160##-vip)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = ORADB)
    (INSTANCE_NAME = ORADB4)
    ORADB =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = nusclust16007-vip)(PORT = 1521))
    (ADDRESS = (PROTOCOL = TCP)(HOST = nusclust16008-vip)(PORT = 1521))
    (ADDRESS = (PROTOCOL = TCP)(HOST = nusclust16036-vip)(PORT = 1521))
    (ADDRESS = (PROTOCOL = TCP)(HOST = nusclust160##-vip)(PORT = 1521))
    (LOAD_BALANCE = yes)
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = ORADB)
    LISTENERS_ORADB =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = nusclust16007-vip)(PORT = 1521))
    (ADDRESS = (PROTOCOL = TCP)(HOST = nusclust16008-vip)(PORT = 1521))
    (ADDRESS = (PROTOCOL = TCP)(HOST = nusclust16036-vip)(PORT = 1521))
    (ADDRESS = (PROTOCOL = TCP)(HOST = nusclust160##-vip)(PORT = 1521))
    LISTENER_NUSCLUST160## =
    (ADDRESS = (PROTOCOL = TCP)(HOST = nusclust160##-vip)(PORT = 1521))
    ORADB_PRIM =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = nusclust16007-vip)(PORT = 1521))
    (ADDRESS = (PROTOCOL = TCP)(HOST = nusclust16008-vip)(PORT = 1521))
    (ADDRESS = (PROTOCOL = TCP)(HOST = nusclust16036-vip)(PORT = 1521))
    (ADDRESS = (PROTOCOL = TCP)(HOST = nusclust160##-vip)(PORT = 1521))
    (LOAD_BALANCE = yes)
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = ORADB)
    c. add entries to listener.ora, The entries for most of this file should be set already, just insure modifications that need to be made are made.
    SID_LIST_LISTENER_NUSCLUST160## =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = PLSExtProc)
    (ORACLE_HOME = /apps/dbs/oracle/product/11.1.0/db_1)
    (PROGRAM = extproc)
    (SID_DESC =
    (GLOBAL_DBNAME = ORADB)
    (ORACLE_HOME = /apps/dbs/oracle/product/11.1.0/db_1)
    (SID_NAME = ORADB4)
    LISTENER_NUSCLUST160## =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = NUSCLUST160##-vip)(PORT = 1521)(IP = FIRST))
    (ADDRESS = (PROTOCOL = TCP)(HOST = 222.65.125.###)(PORT = 1521)(IP = FIRST))
    9. Reload the listener.
    lsnrclt
    set current_listener LISTENER_NUSCLUST160##
    reload
    exit
    10. Check audit trail, add instance to cluster, and start db instance.
    a.
    Check for audit directory and start the instance.
    /apps/dbs/oracle/product/11.1.0/db_1/rdbms/audit
    If this audit trail directory does not exist then create it.
    b.
    srvctl add instance -d ORADB -i ORADB4 -n nusclust160##
    srvctl modify instance -d ORADB -i ORADB4 -s +ASM4
    srvctl enable instance -d ORADB -i ORADB4
    Will probably show: PRKP-1017 : Instance ORADB4 already enabled.
    c.
    sqlplus '/ as sysdba'
    startup
    **Because the cluster_database_instances parameter requires the complete shutdown of all instances in the cluster, you might have an issue when it attempts to start the instance. If you receive an error then run:
    srvctl stop database -d oradb
    sqlplus '/ as sysdba'
    startup
    shutdown
    srvctl start database -d oradb
    shutdown
    srvctl start instance -d ORADB -i ORADB4 -o open
    11.
    Modify spfile of ASM1, ASM2, +ASM3
    On nusclust16007
    . ./.asm
    sqlplus '/ as sysasm'
    alter system set instance_number=4 scope=spfile sid='+ASM4' ;
    On nusclust16008
    . ./.asm
    sqlplus '/ as sysasm'
    alter system set instance_number=4 scope=spfile sid='+ASM4' ;
    On nusclust16036
    . ./.asm
    sqlplus '/ as sysasm'
    alter system set instance_number=4 scope=spfile sid='+ASM4' ;
    b Modify tnsnames.ora on nusclust nusclust16007, nusclust16008, and nusclust16036
    On nusclust16007
    ORADB4 =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = nusclust160##-vip)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = ORADB)
    (INSTANCE_NAME = ORADB4)
    Add the following line to the ORADB alias:
    (ADDRESS = (PROTOCOL = TCP)(HOST = nusclust160##-vip)(PORT = 1521))
    Add the following line to the LISTENERS_ORADB alias:
    (ADDRESS = (PROTOCOL = TCP)(HOST = nusclust160##-vip)(PORT = 1521))
    Add the following line to the ORADB_PRIM alias:
    (ADDRESS = (PROTOCOL = TCP)(HOST = nusclust160##-vip)(PORT = 1521))
    On nusclust16008
    ORADB4 =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = nusclust160##-vip)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = ORADB)
    (INSTANCE_NAME = ORADB4)
    Add the following line to the ORADB alias:
    (ADDRESS = (PROTOCOL = TCP)(HOST = nusclust160##-vip)(PORT = 1521))
    Add the following line to the LISTENERS_ORADB alias:
    (ADDRESS = (PROTOCOL = TCP)(HOST = nusclust160##-vip)(PORT = 1521))
    Add the following line to the ORADB_PRIM alias:
    (ADDRESS = (PROTOCOL = TCP)(HOST = nusclust160##-vip)(PORT = 1521))
    On nusclust16036
    ORADB4 =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = nusclust160##-vip)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = ORADB)
    (INSTANCE_NAME = ORADB4)
    Add the following line to the ORADB alias:
    (ADDRESS = (PROTOCOL = TCP)(HOST = nusclust160##-vip)(PORT = 1521))
    Add the following line to the LISTENERS_ORADB alias:
    (ADDRESS = (PROTOCOL = TCP)(HOST = nusclust160##-vip)(PORT = 1521))
    Add the following line to the ORADB_PRIM alias:
    (ADDRESS = (PROTOCOL = TCP)(HOST = nusclust160##-vip)(PORT = 1521))
    c Add standby logs on primary to support 4th node.
    alter database add standby logfile thread 4 group 32 ('+REDO1', '+REDO2' ) size 100M ;
    alter database add standby logfile thread 4 group 33 ('+REDO1', '+REDO2' ) size 100M ;
    alter database add standby logfile thread 4 group 34 ('+REDO1', '+REDO2' ) size 100M ;
    alter database add standby logfile thread 4 group 35 ('+REDO1', '+REDO2' ) size 100M ;
    alter database add standby logfile thread 4 group 36 ('+REDO1', '+REDO2' ) size 100M ;
    12.
    Test the cluster to make sure everything is set up correctly.
    a. Shutdown resources.
    On nusclust16007:
    emctl stop dbconsole
    ps -ef | grep perl
    ps -ef | grep agent
    ps -ef | grep java
    On nusclust16008:
    emctl stop dbconsole
    On nusclust16036:
    emctl stop dbconsole
    On nusclust16008:
    cd $HOME
    . ./.rman
    cd scripts
    ./go
    shutdown immediate
    cd $HOME
    . ./.bash_profile
    srvctl stop database -d oradb
    crs_stop -all
    crs_stat -t
    b. Startup resources
    On nusclust16007:
    cd $HOME
    . ./.bash_profile
    crs_start -all
    crs_stat -t
    The command above should show everything up and running.
    ocrcheck
    On nusclust16008:
    cd $HOME
    . ./.rman
    cd scripts
    ./go
    startup
    On nusclust16007:
    emctl start dbconsole
    On nusclust16008:
    emctl start dbconsole
    On nusclust16036:
    emctl start dbconsole
    How does that work for you?
    -JR jr

  • Standby logfile

    Since setting up RMAN control file autobckup on a dataguard set up I get the following message in the alertlog:-
    Starting control autobackup
    Sat May 07 01:04:27 2005
    Control autobackup written to DISK device
    handle 'CF_C-00'
    Clearing standby activation ID 2115378951 (0x7e161f07)
    The primary database controlfile was created using the
    'MAXLOGFILES 9' clause.
    There is space for up to 6 standby redo logfiles
    Use the following SQL commands on the standby database to create
    standby redo logfiles that match the primary database:
    ALTER DATABASE ADD STANDBY LOGFILE 'srl1.f' SIZE 104857600;
    ALTER DATABASE ADD STANDBY LOGFILE 'srl2.f' SIZE 104857600;
    ALTER DATABASE ADD STANDBY LOGFILE 'srl3.f' SIZE 104857600;
    ALTER DATABASE ADD STANDBY LOGFILE 'srl4.f' SIZE 104857600;
    Can anyone tell me a bit more a bit what this message is saying and explain the pros/cons of adding these standby log files to the standby database??

    Thanks for reply..I am really confused by this both the primary and standby have the same redologs set up (3 groups of 2 logs) so dont understand why it is asking me to add 4 logs to the standby? are these the same or different from the normal redo log groups? why is this message only appearing when the control file is autbacked up?

  • ORA-1624 signalled during: ALTER DATABASE CLEAR....

    Hi,
    I get this error in my alert file what it means?
    ORA-1624 signalled during: ALTER DATABASE CLEAR UNARCHIVED LOGFILE GROUP 1...
    Thanks
    Edited by: vittel on Sep 3, 2008 1:28 PM
    Edited by: vittel on Sep 3, 2008 1:29 PM

    Hi,
    First thanks for your quick response.
    The only thing that we have running in the database is a scheduled program how run every 3 min to switch the current log and he applied the archive log to the standby database!!!
    It can be a session how is trying to do this "Alter database clear unarchived logfile...." ?
    Thanks

  • Standby db: continue manualluy alter database register logfile

    Hi,
    in my standby db 10.2.0.4, on linux platform, some archive log are not register properly and i need to perform the register logfile manually.
    Which test a can i do to solve this problem?
    Thank you.

    This is my standby alert log:
    -- Connected User is Valid
    RFS[10]: Assigned to RFS process 26620
    RFS[10]: Identified database type as 'physical standby'
    Tue Sep 14 05:05:58 2010
    Errors in file /oracle/admin/orcl/udump/orcl1_rfs_26620.trc:
    ORA-16401: archivelog rejected by RFS
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[11]: Assigned to RFS process 26622
    RFS[11]: Identified database type as 'physical standby'
    Tue Sep 14 05:05:58 2010
    Errors in file /oracle/admin/orcl/udump/orcl1_rfs_26622.trc:
    ORA-16401: archivelog rejected by RFS
    Tue Sep 14 05:06:03 2010
    Media Recovery Log /database/arch/orcl/arc1_16195_326468442.ARC
    Media Recovery Waiting for thread 2 sequence 16536
    Tue Sep 14 05:20:46 2010
    alter database register logfile '/database/arch/orcl/arc2_16536_326468442.ARC'
    Tue Sep 14 05:20:46 2010
    There are 1 logfiles specified.
    ALTER DATABASE REGISTER [PHYSICAL] LOGFILE
    Resynchronizing thread 2 from sequence 16535 to 16536
    Completed: alter database register logfile '/database/arch/orcl/arc2_16536_326468442.ARC'
    Tue Sep 14 05:20:48 2010
    Media Recovery Log /database/arch/orcl/arc2_16536_326468442.ARC
    Tue Sep 14 05:21:07 2010
    Media Recovery Log /database/arch/orcl/arc1_16196_326468442.ARC
    Media Recovery Log /database/arch/orcl/arc1_16197_326468442.ARC
    Media Recovery Log /database/arch/orcl/arc1_16198_326468442.ARC
    Media Recovery Waiting for thread 1 sequence 16199
    Tue Sep 14 05:45:29 2010
    RFS[6]: Archived Log: '/database/arch/orcl/arc1_16199_326468442.ARC'
    Tue Sep 14 05:45:29 2010
    RFS[8]: Archived Log: '/database/arch/orcl/arc1_16200_326468442.ARC'
    Tue Sep 14 05:45:29 2010
    RFS[6]: Archived Log: '/database/arch/orcl/arc1_16201_326468442.ARC'
    Tue Sep 14 05:45:40 2010
    Media Recovery Log /database/arch/orcl/arc1_16199_326468442.ARC
    Media Recovery Waiting for thread 2 sequence 16537
    Tue Sep 14 06:00:05 2010
    alter database register logfile '/database/arch/orcl/arc2_16537_326468442.ARC'
    Tue Sep 14 06:00:05 2010
    There are 1 logfiles specified.
    ALTER DATABASE REGISTER [PHYSICAL] LOGFILE
    alter database register are performed from a scheduled shell script that check log from V$ARCHIVED_LOG

  • Add logfile group without shutting down first? (10g R2)

    Can I add a logfile group without first shutting down the instance? I don't see any clear statement about this in my Alapati 10g Admin book or any Oracle 10g R2 docs. Citations appreciated. Maybe this is one of those "too obvious to publish" things. My guess is that Oracle 10g R2 is smart enough to know not to write to new logfile group members until it is fully created and available for use.
    Thanks.

    Hello,
    Is the presumption that any "ALTER DATABASE" operation can be done online in 10g? Not Any, but Some, Yes.
    For instance, the ALTER DATABASE ARCHIVELOG statement cannot be done online ( the Database should be mount ).
    However about the ALTER DATABASE ADD LOGFILE statement, as previously posted, it can be done online. I've already done it on a running Production Database.
    Just be careful to set the same SIZE as for the other Logfile Members.
    Hope this help.
    Best regards,
    Jean-Valentin

Maybe you are looking for