Regrading standby database in standard edition

hi gurus
i m facing problem in configuring standby database in standard edition windows 2008 .
os-windows 2008 standard
oracle 11gr2
i have copied files from primary n copied it to same location on standby...at that time database was in noarchivelog mode
then i made it archive n create standby controlfile...also i have created same service name thru oradim with mentioning pfile and same password as on primary
so it created pfile and password file...
i opened the database in nomount with pfile
then mount with standby controlfile it got mounted n the mode is automatically archivelog mode but as i didn't taken the same pfile of primary it didnt take the destinations as such n made archive in flash recovery area
now i m a bit confused how to apply archive..i copied some archive and placed it in flash rec area
i tried all options managed recovery.recover standby database,recover database until cancel
but all give error
please tell how i proceed..what shud b the right process in standby standard edition
if possible send me a good link for standby database creation in windows 2008 standard with how to ftp files with mget mput..
anyone if kindly provide a good link...wud b of great help
thanks all

on your standby database you can use:
set logsource path_to_archives
This will let Oracle know where the archive files are on the standby database.
Then you can apply the archives with:
recover standby database
Another option is to use Dbvisit Standby to automate the whole standby database (including creation) for you when you have Oracle Standard One or Oracle Standard Edition One.

Similar Messages

  • ASM Direct file access (for creating standby database in Standard Edition)

    Hi all,
    Just really looking for any opinions, experience etc. that people may have about this.
    My company are looking to set up a RAC system. They have also asked me to think about creating a standby database for disaster recovery. The first problem they give me here is that they only pay for Standard Edition of Oracle, therefore Dataguard is not an option.
    I know that one can setup "manual" standby databases with Standard Edition, automating the shipping of archive logs with hand-written scripts etc. However, as the primary here is RAC, and will be using ASM on the shared storage, I'm not sure that this would be possible (and I'm even less sure that it would be desirable!). I say this because I don't know of a way to access (using only the O/S and/or Oracle) the database files stored in ASM, and even if there was a way, I can't imagine it being a good idea..
    Anybody know of a way to tackle it, or care to contribute anything to this? As I say, my opinion is that even if it is possible to get to those files within ASM and hence manipulate them, I'd be worried that it wouldn't be such a good idea. But I'm willing to bet I'm not the first to have thought about it...
    Regards,
    Ados
    Edit 1:
    Sorry, I should state that in principal, the basic environment is:
    Windows 2003 Server
    Oracle 10g R2
    I didn't state that originally though, as I'd be keen to hear from anyone who may have attempted this on any O/S and Oracle version.
    Edited by: Ados on 16-sep-2009 9:32
    Edit 2:
    I also realise we could put the archive logs on the local nodes.. but to reinforce the point, I'm talking about having them on the shared storage where - in theory - the management is easier and more effective.
    Edited by: Ados on 16-sep-2009 9:35

    For anyone interested..
    I guess it would be done using RMAN (in fact, I'm sure of it...) in which case, I feel a lot more comfortable doing it!!
    For example:
    backup as copy archivelog ALL to destination 'c:\temp\';
    This way, it shouldn't matter if the arch logs are stored using ASM, we can now get them and "see" them.. and hence "manipulate" them (pass them on to a standby DB, for example).
    I'm just waiting to get my hands on a Standard Edition installation where I can test all this.. To try it all out (with 2-node RAC, and a standby server) I don't think I'll get a chance, so still interested in opinions, or if anyone's actually done this.
    Regards,
    Ados

  • Standby Database with Standard Edition

    Hi All,
    I'm attempting to setup a Standby database with Oracle 10g Standard Edition. I must manually copy over the archive logs to my Standby database server because i'm using Standard Edition.
    Once my primary database archive logs have been copied over to the standby location shouldn't the database automatically apply those archive logs? I have issued the "alter database recover managed standby database disconnect from session" so my understanding is that it is in recovery mode and shoudl be finding the archive logs to apply. Can anyone confirm that this configuration should work with Standard Edition and perhaps point me in the right direction, which parameters in the init file to check, to get my standby database to apply these archive logs automatically.
    Thanks,

    To quickly determine the level of synchronization for the standby database, issue the following query on the physical standby database:
    SQL> SELECT ARCHIVED_THREAD#, ARCHIVED_SEQ#, APPLIED_THREAD#, APPLIED_SEQ#
    2> FROM V$ARCHIVE_DEST_STATUS;
    ARCHIVED_THREAD# ARCHIVED_SEQ# APPLIED_THREAD# APPLIED_SEQ#
    1 947 1 945

  • Archive apply issue for standby database in Standard Edition.

    We have setup standby database in Oracle standard edition. the archive log cannot be send by oracle automatically. So we manually send the archive over. But do not see the database apply the archive log file. What could be wrong and where should we check on it?
    We also used following when finishing the standby DB after running "recover standby database;" for a few archive log file:
    alter database recover managed standby database disconnect from session;
    ======================================================================================
    This is the status:
    SQL> select OPEN_MODE, SWITCHOVER# ,REMOTE_ARCHIVE ,ARCHIVELOG_CHANGE#,SWITCHOVER_STATUS, DATABASE_ROLE from v$database;
    OPEN_MODE SWITCHOVER# REMOTE_A ARCHIVELOG_CHANGE# SWITCHOVER_STATUS DATABASE_ROLE
    MOUNTED 495550636 ENABLED 1.2201E+13 SESSIONS ACTIVE PHYSICAL STANDBY

    The DB version is 10.2.0.5
    I can do this to apply at standby DB:
    SQL> set autorecovery on
    SQL> recover standby database;
    Then I tried to run this to leave the session:
    alter database recover managed standby database disconnect from session;
    Do not seen any apply.
    =============================
    Here is the last lines of alert log:
    Errors in file /oracle/admin/cntus/bdump/cntus_mrp0_12389.trc:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u03/cntus/redolog/redo01b.log'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 1 thread 1: '/u02/cntus/redolog/redo01a.log'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    Thu Sep 06 15:08:34 EDT 2012
    Errors in file /oracle/admin/cntus/bdump/cntus_mrp0_12389.trc:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u03/cntus/redolog/redo01b.log'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 1 thread 1: '/u02/cntus/redolog/redo01a.log'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    Clearing online redo logfile 1 /u02/cntus/redolog/redo01a.log
    Clearing online log 1 of thread 1 sequence number 10158
    Thu Sep 06 15:08:34 EDT 2012
    Errors in file /oracle/admin/cntus/bdump/cntus_mrp0_12389.trc:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u03/cntus/redolog/redo01b.log'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 1 thread 1: '/u02/cntus/redolog/redo01a.log'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    Thu Sep 06 15:08:34 EDT 2012
    Errors in file /oracle/admin/cntus/bdump/cntus_mrp0_12389.trc:
    ORA-19527: physical standby redo log must be renamed
    ORA-00312: online log 1 thread 1: '/u02/cntus/redolog/redo01a.log'
    Clearing online redo logfile 1 complete
    Media Recovery Waiting for thread 1 sequence 10166
    Thu Sep 06 15:08:35 EDT 2012
    Completed: alter database recover managed standby database disconnect from session
    ======
    We have the directory /u02/cntus/redolog and /u03/cntus/redolog. But nothing in there. Should we create redo for it? Is this a separate issue?
    Thanks!

  • Physical standby database in Standard Edition.

    Hi, we have Standard Edition and want to implement a stand by environment. Is it true that with this edition archive logs are not transported automatically to the stand by server using LOG_ARCHIVE_DEST = my_stdby_service ?
    Also, let's suposse I managed to transport archive logs, do they get applied by stand by database automatically or with Standard Edition the only way we have is applying them manually?
    Thanks and regards.

    Hi
    Ref to your SE Standby database, if you are still looking for an Automated Solution you can visit www.anbultechnologies.co.uk . In solutions you can find a product which provides fully automated Standby solution with Automatic failover. We have been using that solution for couple of years without any problems.
    This solution is based on Oracle Standard Edition and provide functionaility similar to EE data guard.
    Cheers
    Harry

  • Oracle manually standby database with standard edition

    Hi, I want to have a plan for disaster. I'm triying with two virtual machines with oracle database 10g on suse linux. I follow these URLs
    http://www.dbasupport.com/oracle/ora10g/manual_standby.shtml
    http://oramdq.blogspot.com/2009/05/como-configurar-un-sistema-de-alta.html
    and it look that work all right.
    I know that with manually standby database we applied archived logs, and so, we don't propagate any physical changes to secondary database (standby), for example, if I create a new tablespace, or adding a new datafile to an existing tablespace, it don't work in the secondary database.
    Anyone does know how is the better way to apply the physical changes??
    Anyone have any scripts to do that?
    Thanks in advance.

    HI,
    Add the STANDBY_FILE_MANAGEMENT = AUTO to the primary parameter file, it will solve it.
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams209.htm]
    Reagds,
    Vijayaraghavan K
    Edited by: Vijayaraghavan Krishnan on Feb 24, 2010 7:19 PM

  • Oracle Database 10g Standard Edition

    Oracle Database 10g Standard Edition Suitable for medium sized organization. Actually it supports how many no of concurrent connection, workload??

    Yes, it is suitable for, and is used in many medium sized organizations. It supports as many concurrent connections as possible until the operating system starts paging or swapping. At which time it slows down. I personally have seen it handle 125 concurrent connections.
    You question is like asking 'will a Pentium 4 CPU handle Microsoft Powerpoint?'. And the answer is 'yes, of course'. But what about when you want to run video clips in Powerpoint?
    There is no accurate way of answering your question without understanding the exact workload you plan on generating.

  • Creating standby database from ASM production database in standard edition

    Hi,
    I am using oracle 10g release 2 standard edition. I recently created a database instance and wanted to create a standby database instance. After sorting out how to achieve this without managed standby and data guard I finally got it working and the shipped archive logs are applied and working well on the standby database.
    Now I am thinking of re-creating my production database and using ASM for storage managment. By doing this can a standby database still be created from a primary database using ASM? I want to be sure I can before I commit to using ASM for the production instance and manually creating a standby database from that instance.
    Note: I am using standard edition not enterprise edition.

    Hi
    For Oracle SE standby, you can visit www.anbultechnologies.co.uk , they have a brilliant product name DRMC which is Automatic disaster recovery solution with automatic failover in case primary goes down due to any reason.
    We are using this product for more than 2 years and it works like a dream using Oracle Standard Edition. We have depolyed more databases and Standby solution within the prices of 2 EE edition licenses.
    You can give ma try as well.
    website address is www.anbultechnologies.co.uk

  • Standby implementation in Standard Edition

    To All,
    I am Ashok(DBA) from Nepal. My country is a developing country and cannot afford Oracle Entreprise Edition in most of the instuations.
    So I need to implement Standby database in Oracle Standard Edition. I need this feature both in Windows and Unix based platform.
    I will be grateful if suggestions come on implementing this feature in Standard edition.

    Hi!
    1) This is the wrong forum (try the Database forum).
    2) Yes, Oracle software is expensive.
    3) In order to use the DataGuard (Standby database) you need the Enterprise Edition.
    4) Workaround is to export / import regularly and use XE.
    cu
    Andreas

  • Standby DB on Standard Edition

    Hi,
    I've just created standby database using Oracle DBMS 10.2.0.2 Standard Edition on IBM AIX 5L. Because it's Standard Edition, I had to use a operating system scripts for log shipping and log apply operations. My log apply script looks like that:
    #!/bin/sh
    export ORACLE_SID=ORCL
    sqlplus "/ as sysdba" <<EOF
    set echo on
    spool /oracle/standby/logs/logapply_ORCL.log
    alter database recover automatic standby database until cancel;
    alter database recover cancel;
    spool off
    EOF
    in the logapply_ORCL.log file i always find a message like that listed below:
    SQL> alter database recover automatic standby database until cancel;
    alter database recover automatic standby database until cancel
    ERROR at line 1:
    ORA-00279: change 8029736 generated at 03/17/2006 11:33:45 needed for thread 1
    ORA-00289: suggestion : /oracle/archlog/ORCL/1_232_579584255.dbf
    ORA-00280: change 8029736 for thread 1 is in sequence #232
    ORA-00278: log file '/oracle/archlog/ORCL/1_232_579584255.dbf' no longer
    needed for this recovery
    ORA-00308: cannot open archived log
    '/oracle/archlog/ORCL/1_232_579584255.dbf'
    ORA-27037: unable to obtain file status
    IBM AIX RISC System/6000 Error: 2: No such file or directory
    Additional information: 3
    SQL> alter database recover cancel;
    Database altered.
    SQL> spool off
    I know that this error is ok, and it means that Oracle couldn't find file which probably doesn't exist. Is it possible to have that information more friendly or presented in more pleasant way?
    Thanks,
    Tim

    since, you are on unix, you can do anything you want with the logfile. Just cut out the message and replace it with a new one.

  • Sample Response File for Oracle Database 12c Standard Edition on Oracle Linux 6.4 -- working

    oracle@styles-and-artists-development-oracle database]$ cat response/db_install.rsp
    ## Copyright(c) Oracle Corporation 1998,2013. All rights reserved.##
    ## Specify values for the variables listed below to customize     ##
    ## your installation.                                             ##
    ## Each variable is associated with a comment. The comment        ##
    ## can help to populate the variables with the appropriate        ##
    ## values.                                                        ##
    ## IMPORTANT NOTE: This file contains plain text passwords and    ##
    ## should be secured to have read permission only by oracle user  ##
    ## or db administrator who owns this installation.                ##
    # Do not change the following system generated value.
    oracle.install.responseFileVersion=/oracle/install/rspfmt_dbinstall_response_schema_v12.1.0
    # Specify the installation option.
    # It can be one of the following:
    #   - INSTALL_DB_SWONLY
    #   - INSTALL_DB_AND_CONFIG
    #   - UPGRADE_DB
    oracle.install.option=INSTALL_DB_AND_CONFIG
    # Specify the hostname of the system as set during the install. It can be used
    # to force the installation to use an alternative hostname rather than using the
    # first hostname found on the system. (e.g., for systems with multiple hostnames
    # and network interfaces)
    ORACLE_HOSTNAME=styles-and-artists-development-oracle
    # Specify the Unix group to be set for the inventory directory. 
    UNIX_GROUP_NAME=oracle
    # Specify the location which holds the inventory files.
    # This is an optional parameter if installing on
    # Windows based Operating System.
    INVENTORY_LOCATION=/home/oracle/oracleInventory
    # Specify the languages in which the components will be installed.            
    # en   : English                  ja   : Japanese                 
    # fr   : French                   ko   : Korean                   
    # ar   : Arabic                   es   : Latin American Spanish   
    # bn   : Bengali                  lv   : Latvian                  
    # pt_BR: Brazilian Portuguese     lt   : Lithuanian               
    # bg   : Bulgarian                ms   : Malay                    
    # fr_CA: Canadian French          es_MX: Mexican Spanish          
    # ca   : Catalan                  no   : Norwegian                
    # hr   : Croatian                 pl   : Polish                   
    # cs   : Czech                    pt   : Portuguese               
    # da   : Danish                   ro   : Romanian                 
    # nl   : Dutch                    ru   : Russian                  
    # ar_EG: Egyptian                 zh_CN: Simplified Chinese       
    # en_GB: English (Great Britain)  sk   : Slovak                   
    # et   : Estonian                 sl   : Slovenian                
    # fi   : Finnish                  es_ES: Spanish                  
    # de   : German                   sv   : Swedish                  
    # el   : Greek                    th   : Thai                     
    # iw   : Hebrew                   zh_TW: Traditional Chinese      
    # hu   : Hungarian                tr   : Turkish                  
    # is   : Icelandic                uk   : Ukrainian                
    # in   : Indonesian               vi   : Vietnamese               
    # it   : Italian                                                  
    # all_langs   : All languages
    # Specify value as the following to select any of the languages.
    # Example : SELECTED_LANGUAGES=en,fr,ja
    # Specify value as the following to select all the languages.
    # Example : SELECTED_LANGUAGES=all_langs 
    SELECTED_LANGUAGES=en
    # Specify the complete path of the Oracle Home.
    ORACLE_HOME=/extended2/oracleBase/db12c1
    # Specify the complete path of the Oracle Base.
    ORACLE_BASE=/extended2/oracleBase
    # Specify the installation edition of the component.                    
    # The value should contain only one of these choices.       
    #   - EE     : Enterprise Edition                               
    #   - SE     : Standard Edition                                 
    #   - SEONE  : Standard Edition One
    #   - PE     : Personal Edition (WINDOWS ONLY)
    oracle.install.db.InstallEdition=SE
    # PRIVILEGED OPERATING SYSTEM GROUPS                                          #
    # Provide values for the OS groups to which OSDBA and OSOPER privileges       #
    # needs to be granted. If the install is being performed as a member of the   #
    # group "dba", then that will be used unless specified otherwise below.       #
    # The value to be specified for OSDBA and OSOPER group is only for UNIX based #
    # Operating System.                                                           #
    # The DBA_GROUP is the OS group which is to be granted OSDBA privileges.
    oracle.install.db.DBA_GROUP=osdba
    # The OPER_GROUP is the OS group which is to be granted OSOPER privileges.
    # The value to be specified for OSOPER group is optional.
    oracle.install.db.OPER_GROUP=osoper
    # The BACKUPDBA_GROUP is the OS group which is to be granted OSBACKUPDBA privileges.
    oracle.install.db.BACKUPDBA_GROUP=bckdba
    # The DGDBA_GROUP is the OS group which is to be granted OSDGDBA privileges.
    oracle.install.db.DGDBA_GROUP=dbdba
    # The KMDBA_GROUP is the OS group which is to be granted OSKMDBA privileges.
    oracle.install.db.KMDBA_GROUP=kmdba
    #                               Grid Options                                  #
    # Specify the type of Real Application Cluster Database
    #   - ADMIN_MANAGED: Admin-Managed
    #   - POLICY_MANAGED: Policy-Managed
    # If left unspecified, default will be ADMIN_MANAGED
    oracle.install.db.rac.configurationType=
    # Value is required only if RAC database type is ADMIN_MANAGED
    # Specify the cluster node names selected during the installation.
    # Leaving it blank will result in install on local server only (Single Instance)
    # Example : oracle.install.db.CLUSTER_NODES=node1,node2
    oracle.install.db.CLUSTER_NODES=
    # This variable is used to enable or disable RAC One Node install.
    #   - true  : Value of RAC One Node service name is used.
    #   - false : Value of RAC One Node service name is not used.
    # If left blank, it will be assumed to be false.
    oracle.install.db.isRACOneInstall=
    # Value is required only if oracle.install.db.isRACOneInstall is true.
    # Specify the name for RAC One Node Service
    oracle.install.db.racOneServiceName=
    # Value is required only if RAC database type is POLICY_MANAGED
    # Specify a name for the new Server pool that will be configured
    # Example : oracle.install.db.rac.serverpoolName=pool1
    oracle.install.db.rac.serverpoolName=
    # Value is required only if RAC database type is POLICY_MANAGED
    # Specify a number as cardinality for the new Server pool that will be configured
    # Example : oracle.install.db.rac.serverpoolCardinality=2
    oracle.install.db.rac.serverpoolCardinality=
    #                        Database Configuration Options                       #
    # Specify the type of database to create.
    # It can be one of the following:
    #   - GENERAL_PURPOSE/TRANSACTION_PROCESSING                      
    #   - DATA_WAREHOUSE                               
    oracle.install.db.config.starterdb.type=GENERAL_PURPOSE
    # Specify the Starter Database Global Database Name.
    oracle.install.db.config.starterdb.globalDBName=cbd
    # Specify the Starter Database SID.
    oracle.install.db.config.starterdb.SID=cdb1
    # Specify whether the database should be configured as a Container database.
    oracle.install.db.ConfigureAsContainerDB=true
    # Specify the  Pluggable Database name for the pluggable database in Container Database.
    oracle.install.db.config.PDBName=pdb1
    # Specify the Starter Database character set.
    #  One of the following
    #  AL32UTF8, WE8ISO8859P15, WE8MSWIN1252, EE8ISO8859P2,
    #  EE8MSWIN1250, NE8ISO8859P10, NEE8ISO8859P4, BLT8MSWIN1257,
    #  BLT8ISO8859P13, CL8ISO8859P5, CL8MSWIN1251, AR8ISO8859P6,
    #  AR8MSWIN1256, EL8ISO8859P7, EL8MSWIN1253, IW8ISO8859P8,
    #  IW8MSWIN1255, JA16EUC, JA16EUCTILDE, JA16SJIS, JA16SJISTILDE,
    #  KO16MSWIN949, ZHS16GBK, TH8TISASCII, ZHT32EUC, ZHT16MSWIN950,
    #  ZHT16HKSCS, WE8ISO8859P9, TR8MSWIN1254, VN8MSWIN1258
    oracle.install.db.config.starterdb.characterSet=AL32UTF8
    # This variable should be set to true if Automatic Memory Management
    # in Database is desired.
    # If Automatic Memory Management is not desired, and memory allocation
    # is to be done manually, then set it to false.
    oracle.install.db.config.starterdb.memoryOption=true
    # Specify the total memory allocation for the database. Value(in MB) should be
    # at least 256 MB, and should not exceed the total physical memory available
    # on the system.
    # Example: oracle.install.db.config.starterdb.memoryLimit=512
    oracle.install.db.config.starterdb.memoryLimit=512
    # This variable controls whether to load Example Schemas onto
    # the starter database or not.
    oracle.install.db.config.starterdb.installExampleSchemas=true
    # Passwords can be supplied for the following four schemas in the             #
    # starter database:                                                           #
    #   SYS                                                                       #
    #   SYSTEM                                                                    #
    #   DBSNMP (used by Enterprise Manager)                                       #
    # Same password can be used for all accounts (not recommended)                #
    # or different passwords for each account can be provided (recommended)       #
    # This variable holds the password that is to be used for all schemas in the
    # starter database.
    oracle.install.db.config.starterdb.password.ALL=CDBadmin12345#
    # Specify the SYS password for the starter database.
    oracle.install.db.config.starterdb.password.SYS=CBDsys12345#
    # Specify the SYSTEM password for the starter database.
    oracle.install.db.config.starterdb.password.SYSTEM=PDBsys12345#
    # Specify the DBSNMP password for the starter database.
    oracle.install.db.config.starterdb.password.DBSNMP=DBsnmp12345#
    # Specify the PDBADMIN password required for creation of Pluggable Database in the Container Database.
    oracle.install.db.config.starterdb.password.PDBADMIN=PDBadmin12345#
    # Specify the management option to use for managing the database.
    # Options are:
    # 1. CLOUD_CONTROL - If you want to manage your database with Enterprise Manager Cloud Control along with Database Express.
    # 2. DEFAULT   -If you want to manage your database using the default Database Express option.
    oracle.install.db.config.starterdb.managementOption=DEFAULT
    # Specify the OMS host to connect to Cloud Control.
    # Applicable only when oracle.install.db.config.starterdb.managementOption=CLOUD_CONTROL
    oracle.install.db.config.starterdb.omsHost=
    # Specify the OMS port to connect to Cloud Control.
    # Applicable only when oracle.install.db.config.starterdb.managementOption=CLOUD_CONTROL
    oracle.install.db.config.starterdb.omsPort=
    # Specify the EM Admin user name to use to connect to Cloud Control.
    # Applicable only when oracle.install.db.config.starterdb.managementOption=CLOUD_CONTROL
    oracle.install.db.config.starterdb.emAdminUser=
    # Specify the EM Admin password to use to connect to Cloud Control.
    # Applicable only when oracle.install.db.config.starterdb.managementOption=CLOUD_CONTROL
    oracle.install.db.config.starterdb.emAdminPassword=
    # SPECIFY RECOVERY OPTIONS                                                    #
    # Recovery options for the database can be mentioned using the entries below  #
    # This variable is to be set to false if database recovery is not required. Else
    # this can be set to true.
    oracle.install.db.config.starterdb.enableRecovery=true
    # Specify the type of storage to use for the database.
    # It can be one of the following:
    #   - FILE_SYSTEM_STORAGE
    #   - ASM_STORAGE
    oracle.install.db.config.starterdb.storageType=FILE_SYSTEM_STORAGE
    # Specify the database file location which is a directory for datafiles, control
    # files, redo logs.        
    # Applicable only when oracle.install.db.config.starterdb.storage=FILE_SYSTEM_STORAGE
    oracle.install.db.config.starterdb.fileSystemStorage.dataLocation=/extended1/db/data
    # Specify the recovery location.
    # Applicable only when oracle.install.db.config.starterdb.storage=FILE_SYSTEM_STORAGE
    oracle.install.db.config.starterdb.fileSystemStorage.recoveryLocation=/extended1/db/recovery
    # Specify the existing ASM disk groups to be used for storage.
    # Applicable only when oracle.install.db.config.starterdb.storageType=ASM_STORAGE
    oracle.install.db.config.asm.diskGroup=/dev/oracleasm
    # Specify the password for ASMSNMP user of the ASM instance.                
    # Applicable only when oracle.install.db.config.starterdb.storage=ASM_STORAGE
    oracle.install.db.config.asm.ASMSNMPPassword=ASMsnmp122345#
    # Specify the My Oracle Support Account Username.
    #  Example   : [email protected]
    MYORACLESUPPORT_USERNAME=
    # Specify the My Oracle Support Account Username password.
    # Example    : MYORACLESUPPORT_PASSWORD=password
    MYORACLESUPPORT_PASSWORD=
    # Specify whether to enable the user to set the password for
    # My Oracle Support credentials. The value can be either true or false.
    # If left blank it will be assumed to be false.
    # Example    : SECURITY_UPDATES_VIA_MYORACLESUPPORT=true
    SECURITY_UPDATES_VIA_MYORACLESUPPORT=false
    # Specify whether user doesn't want to configure Security Updates.
    # The value for this variable should be true if you don't want to configure
    # Security Updates, false otherwise.
    # The value can be either true or false. If left blank it will be assumed
    # to be false.
    # Example    : DECLINE_SECURITY_UPDATES=false
    DECLINE_SECURITY_UPDATES=flase
    # Specify the Proxy server name. Length should be greater than zero.
    # Example    : PROXY_HOST=proxy.domain.com
    PROXY_HOST=
    # Specify the proxy port number. Should be Numeric and atleast 2 chars.
    # Example    : PROXY_PORT=25
    PROXY_PORT=
    # Specify the proxy user name. Leave PROXY_USER and PROXY_PWD
    # blank if your proxy server requires no authentication.
    # Example    : PROXY_USER=username
    PROXY_USER=
    # Specify the proxy password. Leave PROXY_USER and PROXY_PWD 
    # blank if your proxy server requires no authentication.
    # Example    : PROXY_PWD=password
    PROXY_PWD=
    # Specify the proxy realm.
    # Example    : PROXY_REALM=metalink
    PROXY_REALM=
    # Specify the Oracle Support Hub URL.
    # Example    : COLLECTOR_SUPPORTHUB_URL=https://orasupporthub.company.com:8080/
    COLLECTOR_SUPPORTHUB_URL=
    # Specify the auto-updates option. It can be one of the following:
    #   - MYORACLESUPPORT_DOWNLOAD
    #   - OFFLINE_UPDATES
    #   - SKIP_UPDATES
    oracle.installer.autoupdates.option=SKIP_UPDATES
    # In case MYORACLESUPPORT_DOWNLOAD option is chosen, specify the location where
    # the updates are to be downloaded.
    # In case OFFLINE_UPDATES option is chosen, specify the location where the updates
    # are present.
    oracle.installer.autoupdates.downloadUpdatesLoc=
    # Specify the My Oracle Support Account Username which has the patches download privileges 
    # to be used for software updates.
    #  Example   : [email protected]
    AUTOUPDATES_MYORACLESUPPORT_USERNAME=
    # Specify the My Oracle Support Account Username password which has the patches download privileges 
    # to be used for software updates.
    # Example    : AUTOUPDATES_MYORACLESUPPORT_PASSWORD=password
    AUTOUPDATES_MYORACLESUPPORT_PASSWORD=

    This is the simplest installation you can get, but if you want to do a fast response file based installation, there it is.

  • Co-location of persistent chat and monitoring databases on Standard Edition server

    Hello, I've seen all kinds of different answers to this question around the web with conflicting answers.
    We have a basic IM/Presence only install of Lync 2013 and now want to deploy Monitoring and Persistent Chat roles.
    As per this blog, it states you can co-locate all of these on one FE server.
    http://windowspbx.blogspot.ca/2012/07/aaa-donotpost-install-lync-standard.html
    Which does match what this TechNet article states:
    http://technet.microsoft.com/en-us/library/gg398131.aspx
    However, in the Blog, it says you need to install Full SQL Server 2008 in order to collocate, yet this goes against what TechNet says is possible, in that you can have all databases in one instance:
    Each SQL instance can contain only a single back-end database (for an Enterprise Edition Front End pool), single Monitoring database, single Archiving database, single persistent chat database, and single persistent chat compliance database.
    I guess my question is, can I simply install Monitoring and Persistent Chat using the same default SQL Server 2012 instance that was installed along with the Front End Standard Edition server (RTC instance)? Or should I create a new instance? Or do I need
    to install a new SQL Server 2012 somewhere on a different server altogether?
    Thanks!

    Hi,
    Lync standard edition server has SQL express database by default to host RTC instance. Monitoring server required SQL reporting services, SQL express does not have reporting components part of it. Hence, you required full SQL version for monitoring
    and archiving deployment.
    Technically, you can install full SQL server on the standard edition server itself. But , it is not recommended in production environment. It's good idea to install SQL server on a dedicated server for hosting monitoring and archiving database.
    Thanks
    Saleesh
    If answer is helpful, please hit the green arrow on the left, or mark as answer. Blog : http://blogs.technet.com/b/saleesh_nv/

  • Sector size problem when create a "Standby" in Standard Edition

    Hi,
    I've a primary database 11.2.0.4 Standard Edition with Grid Infrastructure with ASM.
    DiskGroup in ASM uses sector size ok 4k.
    I've also a "Standby" the uses filesystem with logical and physical sector size of 512.
    When duplicate from primary I get this warning:
    ORACLE error from auxiliary database: ORA-01378: The logical block size (4096) of file /u03/oradata/ORCL/onlinelog/group_1.268.874153703 is not compatible with the disk sector size (media sector size is 512 and host sector size is 512)
    RMAN-05535: WARNING: All redo log files were not defined properly.
    ORACLE error from auxiliary database: ORA-01378: The logical block size (4096) of file /u03/oradata/ORCL/onlinelog/group_2.265.874153719 is not compatible with the disk sector size (media sector size is 512 and host sector size is 512)
    RMAN-05535: WARNING: All redo log files were not defined properly.
    ORACLE error from auxiliary database: ORA-01378: The logical block size (4096) of file /u03/oradata/ORCL/onlinelog/group_3.263.874153759 is not compatible with the disk sector size (media sector size is 512 and host sector size is 512)
    RMAN-05535: WARNING: All redo log files were not defined properly.
    ORACLE error from auxiliary database: ORA-01378: The logical block size (4096) of file /u03/oradata/ORCL/onlinelog/group_4.261.874153735 is not compatible with the disk sector size (media sector size is 512 and host sector size is 512)
    RMAN-05535: WARNING: All redo log files were not defined properly.
    Finished Duplicate Db at 2015-04-21 23:37:10
    released channel: CH1
    I can recreate 3 redologs with correct sector size, but I unable to drop current log file:
    ERROR at line 1:
    ORA-01623: log 4 is current log for instance ORCL (thread 1) - cannot drop
    ORA-00312: online log 4 thread 1:
    '/u03/oradata/ORCL/onlinelog/group_4.261.874153735'
    So how can I solve this problem?

    yasinyazici wrote:
    Hi
    Oracle Data Guard is available only as a feature of Oracle Database Enterprise Edition. It is not available with Oracle Database Standard Edition.
    Please look  2.3.2 Oracle Software Requirements section  of the  following document
    http://docs.oracle.com/cd/E11882_01/server.112/e41134/standby.htm#SBYDB4716
    Yasin
    It's possible:
    Data Guard and Oracle Standard Edition (Doc ID 305360.1)
    Alternative for standby database in standard edition (Doc ID 333749.1)

  • Manual Standby on Standard Edition

    Hey, I try to setup a manual standby on standard edition 10gR2.
    Source is a RAC database (standard edition on sles10 sp3)
    I created a node and created a oracle instance on this node. This node is using the filesystem for the oracle files.
    I did a hotbackup of the source database and copied all files over to the other host.
    Which parameters needs to be change in the init.ora and how can I recover my database ?
    Articles like
    http://www.databasejournal.com/features/oracle/article.php/3682421/Manual-Standby-Database-under-Oracle-Standard-Edition.htm
    or
    Alternative for standby database in standard edition [ID 333749.1]
    does not really help me.
    Thanks for your patience... :-)

    ./rman target / cmdfile=/opt/oracle/rman.sh
    rman.sh
    run{
    change archivelog all crosscheck;
    allocate channel ch1 type disk;
    backup incremental level 0 database format
    '/opt/oracle/backup/backupnew/bk_inc0_%s_%p' include current
    controlfile for standby ;
    sql "alter system archive log current";
    backup archivelog all format '/opt/oracle/backup/backupnew/al_%s_%p';
    release channel ch1;
    copy files from '/opt/oracle/backup/backupnew' to standbyhost:'/opt/oracle/backup/backupnew'
    ./rman cmdfile=/opt/oracle/duplicate.rman
    duplicate.rman
    connect auxiliary sys/oracle@standby
    connect target /
    run {
    allocate auxiliary channel ch1 type disk;
    duplicate target database for standby dorecover nofilenamecheck;
    release channel ch1;
    Now I get this:
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 09/15/2010 15:20:35
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06026: some targets not found - aborting restore
    RMAN-06024: no backup or copy of the control file found to restore
    When do have I to issue the
    ALTER DATABASE CREATE STANDBY CONTROLFILE AS '/opt//oracle/stbycf.ctl';
    command. And where to copy ?

  • To create standby database using oracle 10g standared edition

    my producation database is oracle 10G standard edition .Can i implement a oracle dataguard or standby database using standard edition licenses.if standby database is possiable in standard edition .what are the steps for creating a standby database using oracle 10g standard edition.

    General answer is http://download.oracle.com/docs/cd/B19306_01/license.102/b14199/editions.htm#BABJICBB.
    For Data Guard you cannot :
    - use instance parameters to automatically send archived redo logs
    - use instance parameters to resolve archived redo logs gaps
    - create a logical standby
    - use SQL statements to do switchover / failover
    - use Data Guard Broker.

Maybe you are looking for

  • Adobe AIR Seamless Install Badge PROBLEM

    Hello, my air badge installation stop working few days back (do not know exactly how many). Has anybody else this issue here? Any advice probably. Thanks

  • Pass constant values to ODI functions in interface mapping

    I have a generic ODI user function Populate_TRG_COLS($(in1), $(in1Val), $(in2), $(in2Val), $(in3)) Implementation (ORACLE): CASE WHEN $(in1)=$(inVal1) AND $(in2)=$(inVal2) THEN $(in3) END I use this function when mapping my target columns at say TRG_

  • Old version Samsung Remote 2.0.1 for iOS 3.1.3 required

    Too late, too bad: I purchased a Samsung 5.1 BD-receiver but unfortunately a few weeks before the remote app was updated and requires now iOS 4.2 (before just 3.1.3). Too bad for me and my old 1. gen iPod. Does the app store has a (hidden) feature to

  • Getting internal table definition

    Hi all, Let's say that I've defined internal table based on internal type (not in dictionary). Does anybody know if there is some FM that could return to me definition of that table (how many fields, their types and so on). For dictionary based type

  • Documaker ini changes for library database

    Hi experts, When I am connecting to the database it is throwing an error. Cannot open library database <test1>. Check that the registered pathname exists. I re configured the ini files but still having the same issues. What are the steps I need to ta