Log members per log group

Apologies in advance if this has been answered already, I did try to find the answer first.
Is a log group in a data warehouse meant to have more than one member per group? That is, if there are three log groups, is there meant to be three (or, for example six) log members?
Also, what does it mean if one of the log members are not the same size as the others (as reported in a Toad health check)?

A Redo Log group consists of redo logfiles called members that saves the identical information. These redo log members can only belong ot single redo log group.
Is a log group in a data warehouse meant to have more than one member per group?Good idea is to have 3 redolog groups with two members each.
Cheers, Bhupinder

Similar Messages

  • Redo log members in a group

    Hi,
    I am running 10gRac on Linux
    I have 4 groups with 1 member each (50MB).
    The DB is running in noarchive mode
    I heard there is recommendation to have at least 2 members in each group.
    Now how can I check if I should add more members to the groups?
    Thanks

    Hi br00klynZ00,
    just imagine that you loose the only member of an unarchive group.
    Maybe teh CURRENT?!
    What do you do then?
    You habe lost data then if you have a crash in addition because you cannot recover your lost instance.
    So you should definitely have at least two members for each group!
    =;-)
    Hope this clarifies a little what the problem is.
    BR,
    Lutz

  • Writing in redo log members

    Hi i have a couple of questions
    1) what is the max value i can set for MAXLOGFILES in controlfile? that is maximum how many redo log groups i can have in a database(when not considering space occupied by log members)
    2) I had a 2 log groups with 2 members in each. how LGWR writes into log members of each group. whether it will done in serial(sequential order) or parallel? If it is sequential, when LGWR writes into 2nd member of one group if i perform a log switch, will it wait till it completes writing into that member and switches to another group?
    thanks in advance

    >>> I had a 2 log groups with 2 members in each. how LGWR writes into log members of each group. whether it will done in serial(sequential order) or parallel? If it is sequential, when LGWR writes into 2nd member of one group if i perform a log switch, will it wait till it completes writing into that member and switches to another group?
    Mr.Howard Rodger wrote:-
    There is only ever one Log Writer process. Unlike Database Writer, for example, which can have several 'clone' processes sharing the work burden, redo log records must be written to disk sequentially -and that means only one process can be in charge of working out what to write to disk. If that wasn't true, you might come to grief when a series of transactions have dependencies. If you first create a new product record and then raise a new sale record to indicate that the new product has just been sold, for example, you need the product transaction to be recorded before the sale transaction -otherwise, during a recovery, you might end up trying to sell a product that doesn't exist yet. To prevent that logical nonsense from happening, therefore, a single Log Writer process writes everything in the correct sequence.
    I hope it helps
    Regards
    Nisanth V Santhan

  • ORA-00313: open failed for members of log group 4 of thread 2

    Hi.
    i have found the below error in one of RAC instance.Could you please advise on this since i am new to RAC env
    ORA-00313: open failed for members of log group 4 of thread 2
    ORA-00312: online log 4 thread 2: '+NEWDISK_GROUP/DEMO/onlinelog/group_4.1453.1029312423'
    ORA-17503: ksfdopn:2 Failed to open file +NEWDISK_GROUP/DEMO/onlinelog/group_4.1453.1029312423
    ORA-15032: not all alterations performed
    ORA-29702: error occurred in Cluster Group Service operation
    ORA-29702: error occurred in Cluster Group Service operation
    Thanks
    Sai

    any update on this?

  • ORA-00313: open failed for members of log group 1 of thread 1

    Hi
    I'm restoring a database on a different host. I have the backups, from which I want to restore the database. I made the corresponding changes in the initSID.ora file and started the script to do the restore.These are the steps I followed:
    connect target=/
    run{
    startup nomount;
    allocate channel c1 type disk;
    allocate channel c2 type disk;
    allocate channel c3 type disk;
    allocate channel c4 type disk;
    restore controlfile from '/tmp_backups/rman/lev0_open_cf_SID_2826_1';
    alter database mount;
    set newname for all datafiles
    restore database;
    set until logseq = 29317 thread = 1;
    switch datafile all;
    recover database;
    alter database open resetlogs;
    One mistake I made here is that logseq should have been last seq+1, which I did not do. I have it as last seq.
    Restore of datafiles and switching of datafiles was fine. But I get error for redo log files.
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u13/oradata/SID/redo02a.log'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    Why is it looking for at the old path yet?
    I'm not sure what I missed and how to proceed. Please help.
    Thanks,
    Mamata

    I do believe that set newname for all datafiles only means actual datafiles and no redo logs. So with open resetlogs, Oracle tries to create new redo logfiles where the backup controlfiles says they are.
    As with creating a auxilliary database in another filesystem, we use DB_NAME_FILE_CONVERT and LOG_FILE_NAME_CONVERT.
    I am not sure if it is possible to type "set newname for all datafiles" and expect also the redo logfiles to change location.
    You might try to set these two parameters and see if it works.
    good luck.
    rgds
    Kjell Ove

  • ORA-00313: open failed for members of log group 3 of thread 1

    Whenever I try to login as a user I get the following:
    sqlplus user/user
    SQL*Plus: Release 10.2.0.2.0 - Production on Fri Nov 9 10:43:39 2007
    Copyright (c) 1982, 2005, Oracle. All Rights Reserved.
    ERROR:
    ORA-01033: ORACLE initialization or shutdown in progress
    So It occurs to me to login as sysdba and restart the DB …
    SQL> connect sys/manager as sysdba
    Connected.
    SQL> shutdown immediate;
    ORA-01109: database not open
    Database dismounted.
    ORACLE instance shut down.
    SQL> startup
    ORACLE instance started.
    Total System Global Area 536870912 bytes
    Fixed Size 1281264 bytes
    Variable Size 150995728 bytes
    Database Buffers 377487360 bytes
    Redo Buffers 7106560 bytes
    Database mounted.
    ORA-00313: open failed for members of log group 3 of thread 1
    ORA-00312: online log 3 thread 1: '/u06/oradata/RKDB/redo03.log'
    ORA-27037: unable to obtain file status
    Intel SVR4 UNIX Error: 2: No such file or directory
    Additional information: 3
    SQL> quit
    I now realized what happened and how this happened. During a clean-up effort this file was accidentally deleted and unfortunately we don’t have any backups.
    I am willing to lose the data. Is there something I can do so that the startup does not try to open this file ?
    All I am able to do now is to mount the database but not open it.
    Thanks in advance,
    Daniel

    this is what I get now ...
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/u02/oradata/RKDB/system01.dbf'
    SQL> Recover database until cancel;
    ORA-00279: change 608619 generated at 11/09/2007 10:00:41 needed for thread 1
    ORA-00289: suggestion : /u05/oradata/RKDB/arch/log1_33_633207859.arc
    ORA-00280: change 608619 for thread 1 is in sequence #33
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    ORA-00308: cannot open archived log
    '/u05/oradata/RKDB/arch/log1_33_633207859.arc'
    ORA-27037: unable to obtain file status
    Intel SVR4 UNIX Error: 2: No such file or directory
    Additional information: 3
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/u02/oradata/RKDB/system01.dbf'
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/u02/oradata/RKDB/system01.dbf'
    SQL>

  • ORA-00313: open failed for members of log group

    Hi,
    on 11g R2, on standby I have this in alertlog :
    ORA-00313: open failed for members of log group 21 of thread 1
    Deleted Oracle managed file +DGRECO_FSCM/xxx/onlinelog/group_21.1721.791875667
    Tue Aug 21 14:37:34 2012
    Clearing online redo logfile 21 complete
    Errors in file /data01/oracle/diag/rdbms/xxx_mrp0_22843.trcAnd this in trace file
    *** 2012-08-21 14:35:57.192 4265 krsh.c
    *** 2012-08-21 14:37:26.406 4265 krsh.c
    Clearing online redo logfile 21 +DGRECO_FSCM/xxxx/onlinelog/group_21.1721.791875667
    DDE: Problem Key 'ORA 313' was flood controlled (0x5) (no incident)
    ORA-00313: open failed for members of log group 21 of thread 1Any explanation please ?
    Thank you.

    Refer to the below note:
         ORA-19527 reported in Standby Database when starting Managed Recovery [ID 352879.1]

  • Open failed for members of log group

    HI,
    OS : LINUX 5.1
    DB : 10.2.0.3
    i have configured physical standby and its working fine. but in alert log i m getting below error.
    i have checked the physical location of member. it is very much available.
    Mon May 24 23:54:19 2010
    Errors in file /u001/app/oracle/admin/YAHOO/bdump/yahoo_mrp0_3526.trc:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u001/app/oracle/oradata/YAHOO/redo01.log'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    Mon May 24 23:54:19 2010
    Errors in file /u001/app/oracle/admin/YAHOO/bdump/yahoo_mrp0_3526.trc:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u001/app/oracle/oradata/YAHOO/redo01.log'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    Clearing online redo logfile 1 /u001/app/oracle/oradata/YAHOO/redo01.log
    Clearing online log 1 of thread 1 sequence number 31
    Mon May 24 23:54:19 2010
    Errors in file /u001/app/oracle/admin/YAHOO/bdump/yahoo_mrp0_3526.trc:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u001/app/oracle/oradata/YAHOO/redo01.log'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    Mon May 24 23:54:19 2010
    Errors in file /u001/app/oracle/admin/YAHOO/bdump/yahoo_mrp0_3526.trc:
    ORA-19527: physical standby redo log must be renamed
    ORA-00312: online log 1 thread 1: '/u001/app/oracle/oradata/YAHOO/redo01.log'
    can any one suggest?
    Regards,
    BK

    Hi,
    Below note was taken from metalink;
    Symptoms
    Following errors in alert.log of standby database during startup of the standby database:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u03/oradata/prod/redo01b.log'
    ORA-27037: unable to obtain file status
    Cause
    Online Redo logs missing on standby database.
    Solution
    You can safely ignore these messages. Online redo logs will be created automatically when you activate the standby after switchover or failover.
    If you want to fix these messages then please use following steps:
    1. Check and set "log_file_name_convert" parameter if the location of log files are different on primary and standby.
    SQL> alter system set log_file_name_convert = "'<location on primary>','<location on standby>'" scope=spfile;
    If you are using pfile then set the parameter in init file after shutting down the database:
    *.log_file_name_convert = '<location on primary>','<location on standby>'
    For 10gR2 only : Set this parameter even if the location of the redo logs are same on both primary and standby otherwise you may get ORA-19527 and ORA-312 while or after implementing the below steps.
    This is due to internal bug in 10.2.
    2. Cancel Managed Recovery process on the standby:
    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
    3. Execute the command to clear all log groups on standby for each log group (for each log group):
    SQL>alter database clear logfile group 1;
    4. Check the v$log view to confirm the size and status.
    5. Recreate standby redo logs on standby (only if standby Redo logs are also missing) using:
    (a) Drop the standby redo logfile group(s) (check v$standby_log)
    SQL> alter database drop standby logfile group 4;
    (b) Recreate the standby logfile group(s)
    SQL> alter database add standby logfile group 4 ('/u03/redo/stby01.log') size 50m;
    Hope it helps you.

  • ORA-00313: open failed for members of log group 2 of thread 1

    We have a 4 node 32bit linux RAC (Dell/EMC) system running 9.2.0.4. It is very stable but over the past couple of months we've encountered a few ORA-00313 errors, while the system is running.
    No patterns. Different loads, times of day, nodes.
    The redo can't be opened, the node crashes, we look for errors, can't find any and then restart. The file is there and the permissions are fine. No other processes are accessing the files. No other Db errors. No O/S, SAN, Fiber, errors.
    All the research I've done shows that this is an error you'd only get on startup.
    We're going to log a TAR, but I can't believe we're the only ones to ever see this occur.
    [directory and server names have been modified to protect the system. Don't get hung up on typos or possible file system config problems too much - this system has been and is running now]
    ======================================================
    Log entries:
    Mon Oct 24 22:51:58 2005
    Errors in file /u01/app/oracle/admin/sampdb/bdump/sampdb1_lgwr_2237.trc:
    ORA-00313: open failed for members of log group 2 of thread 1
    ORA-00312: online log 2 thread 1: '/sampledb/redo0/oradata/sampdb/redo/redo102.log'
    ORA-27041: unable to open file
    Linux Error: 13: Permission denied
    Additional information: 2
    Mon Oct 24 22:51:58 2005
    Errors in file /u01/app/oracle/admin/sampdb/bdump/sampdb1_lgwr_2237.trc:
    ORA-00313: open failed for members of log group 2 of thread 1
    ORA-00312: online log 2 thread 1: '/sampledb/redo0/oradata/sampdb/redo/redo102.log'
    ORA-27041: unable to open file
    Linux Error: 13: Permission denied
    Additional information: 2
    Mon Oct 24 22:51:58 2005
    LGWR: terminating instance due to error 313
    Below are the contents of the trace file mentioned in the above log:
    trace file /u01/app/oracle/admin/sampdb/bdump/sampdb1_lgwr_2237.trc:
    [oracle@db1 bdump]$ more /u01/app/oracle/admin/sampdb/bdump/sampdb1_lgwr_2237.trc
    /u01/app/oracle/admin/sampdb/bdump/sampdb1_lgwr_2237.trc
    Oracle9i Enterprise Edition Release 9.2.0.4.0 - Production
    With the Partitioning, Real Application Clusters, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.4.0 - Production
    ORACLE_HOME = /u01/app/oracle/product/920
    System name: Linux
    Node name: db1.sample.com
    Release: 2.4.9-e.59enterprise
    Version: #1 SMP Mon Jan 17 07:02:16 EST 2005
    Machine: i686
    Instance name: sampdb1
    Redo thread mounted by this instance: 0 <none>
    Oracle process number: 24
    Unix process pid: 2237, image: [email protected] (LGWR)
    *** SESSION ID:(25.1) 2005-10-11 22:31:02.315
    CMCLI WARNING: CMInitContext: init ctx(0xad96e80)
    *** 2005-10-24 22:51:58.192
    ORA-00313: open failed for members of log group 2 of thread 1
    ORA-00312: online log 2 thread 1: '/sampledb/redo0/oradata/sampdb/redo/redo102.log'
    ORA-27041: unable to open file
    Linux Error: 13: Permission denied
    Additional information: 2
    error 313 detected in background process
    ORA-00313: open failed for members of log group 2 of thread 1
    ORA-00312: online log 2 thread 1: '/sampledb/redo0/oradata/sampdb/redo/redo102.log'
    ORA-27041: unable to open file
    Linux Error: 13: Permission denied
    Additional information: 2
    ksuitm: waiting for [5] seconds before killing DIAG

    The only thing I can still think of is file permissions.
    If the system has recently been restored or Redo Log recreated, check the file permissions and ensure that Oracle has Read and Write Access to the Directory and Files.
    At least the file permissions on the directory and files should look something like this example
    $ls -l /sampledb/redo0/oradata/sampdb/
    drwxr-xr-x oracle oinstall 4096 19 May 17:46 redo
    $ls -l /sampledb/redo0/oradata/sampdb/redo/
    -rw-r----- oracle oinstall 524288512 27 Oct 15:07 redo101.log
    $ls -l /sampledb2/redo0/oradata/sampdb/redo2/
    -rw-r----- oracle oinstall 524288512 27 Oct 15:21 redo102.log
    $ls -l /sampledb3/redo0/oradata/sampdb/redo3/
    -rw-r----- oracle oinstall 524288512 27 Oct 15:33 redo103.log

  • Best way to move redo log from one disk group to another in ASM?

    Hi All,
    Our db is 10.2.0.3 RAC db. And database servers are window 2003 server.
    We need to move more than 50 redo logs (some are regular and some are standby) which are not redundant from one disk group to another. Say we need to move from disk group 1 to 2. Here are the options we are thinking about but not sure which one is the best from easiness and safety prospective.
    Thank you very much for your help in advance.
    Shirley
    Option 1:
    1)     shutdown immediate
    2)     copy log files from disk group 1 to disk group2 using RMAN (need to research on this)
    3)     startup mount
    4)     alter database rename file ….
    5)     Open database open
    6)     delete the redo files from disk group 1 in ASM (how?)
    Option 2:
    1)     create a set of redo log groups in disk group 2
    2)     drop the redo log groups in disk group 1 when they are inactive and have been archived
    3)     delete the redo files associated with those dropped groups from disk group 1 (how?) (According to Oracle menu: when you drop the redo log group the operating system files are not deleted and you need to manually delete those files)
    Option 3:
    1)     create a set of redo members in disk group 2 for each redo log group in disk group 1
    2)     drop the redo log memebers in disk group 1
    3)     delete the redo files from disk group 1 associated with the dropped members

    Absolutely not, they are not even remotely similar concepts.
    OMF: Oracle Managed Files. It is an RDMBS feature, no matter what your storage technology is, Oracle will take care of file naming and location, you only have to define the size of a file, and in the case of a tablespace on an OMF DB Configuration you only need to issue a command similar to this:
    CREATE TABLESPACE <TSName>; So the OMF environment creates an autoextensible datafile at the predefined location with 100M by default as its initial size.
    On ASM it should only be required to specify '+DGroupName' as the datafile or redo log file argument so it can be fully managed by ASM.
    EMC. http://www.emc.com No further commens on it.
    ~ Madrid
    http://hrivera99.blogspot.com

  • Redo Log Members & RAID 5

    Hi,
    My production database servers run on HP-XP storage, raid 5. Currently the redo logs are striped on 16 disks, as raw files. I use 5 groups, 2 members in each group.
    I wanted to hear your opinion, if two members are still necessary with todays storage hardware, considering the mirroring already done in the hardware level.
    What is the benefit today for having more than one member in a group, and do you think it's worth the IO price most of us are still paying...
    Thanks in advance,
    Idan.

    For example here:
    http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID:359617936136
    Try search google btw. There are plenty of articles.
    Just if you read concepts of RAID you will learn that RAID 5 is not good for write intensive operations (redo logs are write intensive).

  • 10.6.4 OD Master: slapd exceeded 500 log message per second limit

    We've got here a 10.6.4 Server OD Master setup with 800 users, 12GB RAM that sometimes starts to get unresponsive. It's slapd that suddenly refuses to respond. CPU load rises to around 10-15% which is high for Intel Xserves. When this happens, our mail service can't authenticate anymore (we use communigate with an external authentication helper script that is designed to restart every 30 seconds. If we restart slapd, all is fine again for a week or so.
    DNS is all fine, Kerberos and password server ok, changeip -checkhostname reports that all is ok. The server was setup from scratch with imported groups and users from a 10.5.8 od master. I've already increased the the amount of returned values of the ldap to 25000 that didn't solve the issue because we first thought the external helper script of our mail server causes the problem, but it's in fact slapd that hangs. What could trigger this behavior with a brand new Xserve with 12GB RAM, with all services configured perfectly?
    Excerpt of the error log:
    request: socketpair failed 24 (Too many open files)
    Aug 27 11:50:51: --- last message repeated 499 times ---
    Aug 27 11:50:51 authority slapd[92258]: * process 92258 exceeded 500 log message per second limit - remaining messages this second discarded *
    Aug 27 11:50:52 authority slapd[92258]: dnssd_clientstub deliver_request: socketpair failed 24 (Too many open files)
    Aug 27 11:50:52: --- last message repeated 499 times ---
    Aug 27 11:50:52 authority slapd[92258]: * process 92258 exceeded 500 log message per second limit - remaining messages this second discarded *
    Aug 27 11:50:53 authority slapd[92258]: dnssd_clientstub deliver_request: socketpair failed 24 (Too many open files)
    Aug 27 11:50:53: --- last message repeated 499 times ---
    Aug 27 11:50:53 authority slapd[92258]: * process 92258 exceeded 500 log message per second limit - remaining messages this second discarded *
    Any idea what this could be?
    Thanks,
    Alex
    Message was edited by: Alex33

    I was able to identify the cause. Wrote in this thread the solution:
    http://discussions.apple.com/message.jspa?messageID=13160082#13160082

  • Prevent 'Logged out of Hunt Group' on 7900 series IP phones

    I have a CUCM configuration on 8.2, and have an issue with some 7925 wireless devices that are set up in a "call flow" along side a pair of 7945 devices.  If a call comes into either of those devices' extensions, after a set # of seconds of "no answer" "busy" condition, the call is set to move to a Hunt Pilot which then sends a broadcast out to a group of 6 7925 phones so those calls can be answered by staff.  However, I ran into a situation yesterday where all but 1 of those devices was powered off, and the 1 powered on was logged out of the Hunt Group.  As such, when calls came into either extension, it would ring 2-3 times and then the caller would get a busy tone.  After some troubleshooting, we determined that logging that 7925 back into the Hunt Group remedied the problem.
    In the interim, I have created a custom SoftKey Template for these devices which removes 'HLog' as an option so they can't inadvertently log out of said Hunt Group, but I have to wonder: are there any conditions under which either the CUCM platform, OR the phone device itself would force a logoff from the Hunt Group WITHOUT user intervention?  If so, is there a way to prevent that from occurring?

    Hi Josh,
    This functionality was only added in CUCM 9.1
    Automatically Logout Hunt Member on No Answer
    Automatic  logout of hunt members was introduced for queuing-enabled hunt  pilots  in Unified Communications Manager  9.0(1). If an agent does not answer a  queuing-enabled hunt pilot call,  that agent will be logged off of the  hunt group and will not receive  additional hunt pilot calls unless he  presses the "HLOG" soft key on the  phone to log into the hunt pilot.  This behavior is not configurable in Unified Communications Manager  9.0(1). In Unified Communications Manager 9.1(1), the administrator can  choose whether hunt members remain logged in if the call is not  answered.
    For more information, refer to "Automatically Logout Hunt Member on No Answer" in the Cisco Unified Communications Manager Administration Guide, and to "Call Queuing" in the Cisco Unified Communications Manager Features and Services Guide.
    from;
    http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/9_1_1/CUCM_BK_R6F8DBD4_00_release-notes-for-cucm-91_chapter_0100.html#CUCM_RF_CF356549_00
    Have you thought about linking back to the first Hunt group if the members of Hunt#2 are unavalable
    to give member 1 & 2 a second chance at taking the call? Just a thought
    Cheers!
    Rob
    "A smile relieves a heart that grieves" 
    - Stones

  • How to log the user and group setup from weblogic console

    If I use the file realm to setup my acls, does it possible to log these
    action?
    Our customer ask us must to log which user or group you added, deleted.
    Thanks and Best Regards,
    Tom Hsu
    ³\®aºa (Tom Hsu)
    Project Manager
    Banking Solution Dept.
    Bull Information Systems Taiwan Ltd.
    8F, 2, Min-Sheng E. Road, Sec. 3,
    Taipei, Taiwan
    E-mail: [email protected]
    TEL¡G02-25013090 Ext:205
    FAX¡G02-25055439
    Mobil: 0939-869-316

    You might want to Try Re-run the Config utility from the Linux-Essbase server and Re-register the Essbase with HSS.
    Start the Essbase in Foreground and check if it is running
    Now log on to the EAS/AAS with default admin/password if you havent changed it :); add your Essbase server using the Super user/Owner of essbase i mean the id..if you are succesful; i would always create a Test user as before Externalisation i can create users at EAS/AAS and then using Admin id ; i will push the Users/groups to the HSS by Externalising.. let me know if that helped you. GUd Luck..
    Sriram

  • Redo log add and new group

    Hi,
    I have problem with one of the redo log file i issued the ALTER DATABASE CLEAR LOGFILE GROUP 3; command. the status right now is clearing since last some hours.
    Can i create new redo log and assign to group 3. will the status will be inactive or active? how to add redo log and group please explain!
    Thanks

    user12020966 wrote:
    Hi,
    I have problem with one of the redo log file i issued the ALTER DATABASE CLEAR LOGFILE GROUP 3; command. the status right now is clearing since last some hours.
    Can i create new redo log and assign to group 3. will the status will be inactive or active? how to add redo log and group please explain!
    Thanksafer you create redo log group it wil be inactive because nothing has been written to it after you apply alter system switch file the new group will start to write the redo record and it status will be active but if the circule in group 3

Maybe you are looking for