Status Oracle Restart n/a

Hi ,
Grid Control 11.1.0.1 show for my active Oracle 11.2.0.2 Installation with Oracle restart only n/a.
I can't see in Grid the Status fpr Oracle restart.
My srvctl Status say all ok and running .
Need i a Patch for Grid Control 11.1.0.1 or is this a Bug ? In Databse Control for a other Server see the Status.
Thx for replay

I had the same problem, although mine was on a standalone instance not grid, we got around it by doing this:
Edit the inventory.xml file. Change the following: (add the CRS="true")
<HOME NAME="Ora11g_gridinfrahome1" LOC="/your/location/" TYPE="O" IDX="4" CRS="true"/>
Then drop and recreate the EM Console
emca -deconfig dbcontrol db -repos drop
emca -config dbcontrol db -repos create
Bug 12978410 has been created for this issue.

Similar Messages

  • Oracle restart and ASM

    Hi,
    I have noticed following 'strange' behaviour of Oracle Restart and ASM.
    starting position:
    -bash-3.2 $ crsctl status resource -t
    NAME           TARGET  STATE        SERVER                   STATE_DETAILS
    Local Resources
    ora.DATA.dg
                   ONLINE  ONLINE       oracle-restart
    ora.LISTENERASM.lsnr
                   ONLINE  ONLINE       oracle-restart
    ora.asm
                   ONLINE  ONLINE       oracle-restart           Started
    Cluster Resources
    ora.cssd
          1        ONLINE  ONLINE       oracle-restart
    ora.diskmon
          1        ONLINE  ONLINE       oracle-restartstep 1:
    -bash-3.2 $ srvctl stop asm
    -bash-3.2 $ srvctl stop diskgroup -g data
    -bash-3.2 $ srvctl disable diskgroup -g datastep 2:
    via sqlplus start ASM instance
    SQL> startup
    ASM instance started
    Total System Global Area  283930624 bytes
    Fixed Size                  2212656 bytes
    Variable Size             256552144 bytes
    ASM Cache                  25165824 bytes
    ASM diskgroups mounted
    ASM diskgroups volume enabled
    SQL> select * from v$asm_diskgroup;
    GROUP_NUMBER NAME                           SECTOR_SIZE BLOCK_SIZE
    ALLOCATION_UNIT_SIZE STATE       TYPE     TOTAL_MB    FREE_MB HOT_USED_MB
    COLD_USED_MB REQUIRED_MIRROR_FREE_MB USABLE_FILE_MB OFFLINE_DISKS
    COMPATIBILITY
    DATABASE_COMPATIBILITY                                       V
               1 DATA                                   512       4096
                 1048576 MOUNTED     EXTERN      10236      10177           0
              59                       0          10177             0
    GROUP_NUMBER NAME                           SECTOR_SIZE BLOCK_SIZE
    ALLOCATION_UNIT_SIZE STATE       TYPE     TOTAL_MB    FREE_MB HOT_USED_MB
    COLD_USED_MB REQUIRED_MIRROR_FREE_MB USABLE_FILE_MB OFFLINE_DISKS
    COMPATIBILITY
    DATABASE_COMPATIBILITY                                       V
    11.2.0.0.0
    10.1.0.0.0                                                   N
    -bash-3.2 $ crsctl status resource -t
    NAME           TARGET  STATE        SERVER                   STATE_DETAILS
    Local Resources
    ora.DATA.dg
                   OFFLINE OFFLINE      oracle-restart          <== funny !!!
    ora.LISTENERASM.lsnr
                   ONLINE  ONLINE       oracle-restart
    ora.asm
                   ONLINE  ONLINE       oracle-restart           Started
    Cluster Resources
    ora.cssd
          1        ONLINE  ONLINE       oracle-restart
    ora.diskmon
          1        ONLINE  ONLINE       oracle-restartIs this behaviour a 'feature' or bug?
    Anyone had similar experience?
    thanks,
    goran

    Hi,
    asm resource is depending on diskgroup resource ... if diskgroup res. is not available, crsctl status shows offline, I would expect asm should be also shown as 'offline' (and brought offline) as they are dependent.
    What is the point of managing resources via srvctl when it doesn't take care of dependencies? For me it's wrong.ora.asm : is ASM Instance
    ora.*.dg : is Diskgroup
    ora.*.dg is dependent of ora.asm, not to the contrary.
    I can have more than one diskgroup and want only one diskgroup disabled, so I need the ASM Instance (ora.asm) online.
    Important:
    If you shut down the database with SQL*Plus, Oracle Restart does not interpret this as a database failure and does not attempt to restart the database.
    Similarly, if you shut down the Oracle ASM instance with SQL*Plus or ASMCMD, Oracle Restart does not attempt to restart it.
    An important difference between starting a component with SRVCTL and starting it with SQL*Plus (or another utility) is the following:
    When you start a component with SRVCTL, any components on which this component depends are automatically started first, and in the proper order.
    When you start a component with SQL*Plus (or another utility), other components in the dependency chain are not automatically started; you must ensure that any components on which this component depends are started.
    Oracle Restart also manages the weak dependency between database instances and the Oracle Net listener (the listener): When a database instance is started, Oracle Restart attempts to start the listener. If the listener startup fails, then the database is still started. If the listener later fails, Oracle Restart does not shut down and restart any database instances.
    It makes no sense Oracle Restart to shut down all environment (databases) because the listener down.
    Regards,
    Levi Pereira

  • How to Install Oracle Restart

    Hello All,
    I have a standby database with ASM. I would like it to be start on the server reboot.
    I have read chapter 4 of Oracle Database Administration Guide 11g R2 where it mentions
    If you install Oracle Restart by installing the Oracle Grid Infrastructure for a
    standalone server and then create your database, the database is automatically added
    to the Oracle Restart configuration, and is then automatically restarted when required.
    However, if you install Oracle Restart on a host computer on which a database already
    exists, you must manually add the database, the listener, the Oracle Automatic Storage
    Management (Oracle ASM) instance, and possibly other components to the Oracle
    Restart configuration.
    Please can someone help me with the steps to setup Orace restart in 11gr2.
    Thanks

    [oracle@rs1pre92dvdbsa01 bin]$ srvctl add database -d MDM2 -o /u01/app/oracle/product/11.2.0/dbhome_1 -s ope
    [oracle@rs1pre92dvdbsa01 bin]$ srvctl stop database -d MDM2
    PRCC-1016 : MDM2 was already stopped
    [oracle@rs1pre92dvdbsa01 bin]$ srvctl start database -d MDM2
    [oracle@rs1pre92dvdbsa01 bin]$ srvctl status database -d MDM2
    Database is running.
    [oracle@rs1pre92dvdbsa01 bin]$ su -
    Password:
    [root@rs1pre92dvdbsa01 ~]# reboot
    ***After reboot
    [oracle@rs1pre92dvdbsa01 ~]$ cat /etc/oratab
    #Backup file is /u01/app/oracle/product/11.2.0/dbhome_1/srvm/admin/oratab.bak.r
    s1pre92dvdbsa01 line added by Agent
    # This file is used by ORACLE utilities. It is created by root.sh
    # and updated by the Database Configuration Assistant when creating
    # a database.
    # A colon, ':', is used as the field terminator. A new line terminates
    # the entry. Lines beginning with a pound sign, '#', are comments.
    # Entries are of the form:
    # $ORACLE_SID:$ORACLE_HOME:<N|Y>:
    # The first and second fields are the system identifier and home
    # directory of the database respectively. The third filed indicates
    # to the dbstart utility that the database should , "Y", or should not,
    # "N", be brought up at system boot time.
    # Multiple entries with the same $ORACLE_SID are not allowed.
    +ASM:/u01/app/11.2.0/grid:N             # line added by Agent
    MDM2:/u01/app/oracle/product/11.2.0/dbhome_1:N # line added by Agent
    [oracle@rs1pre92dvdbsa01 ~]$ uptime
    14:02:28 up 3 min, 1 user, load average: 0.41, 0.75, 0.35
    [oracle@rs1pre92dvdbsa01 ~]$ ps -ef | grep pmon
    oracle 4314 1 0 14:01 ? 00:00:00 asm_pmon_+ASM
    oracle 4378 3878 0 14:02 pts/0 00:00:00 grep pmon
    [oracle@rs1pre92dvdbsa01 ~]$
    After rebooting the server MDM2 is not started
    Is is because oratab flag is N

  • Directory Setup for RAC and Oracle Restart

    I have three database installations that I'd like some insight on the initial directory structure and permissions. The three installations are:
    1) Prod RAC - OEL 5U2, 11.2.0.2 Grid Infrastructure, 11.2.0.2 DB EE with RAC option
    2) Test RAC - OEL 5U2, 11.2.0.2 Grid Infrastructure, 11.2.0.2 DB EE with RAC option
    3) Single Instance - OEL 5U2, 11.2.0.2 Grid Infrastructure Standalone (Oracle Restart), 11.2.0.2 DB EE
    The they all have two users GRID (for Grid Infrastructure Software Owner) and ORACLE (for Oracle Database Software Owner).
    We had a consultant install the databases. It's very weird since we have an inconsistency in directories and permission. I want to understand the inconsistency between RAC installations as well as Oracle Restart Install.
    SEE BELOW: The two RAC servers have different owners for /u01/app/11.2.0.2 directory. The Oracle Restart Installation - Single Instance has the same owner as Prod RAC but different than Test RAC. What the consultant said was that ORACLE_BASE would be /u01/app/oracle for both Grid Infrastructure and Database installations. This was to apply to TEST/PROD RAC (3 node, 3 instances, 1 instance/node) and Oracle Restart installation. The GRID_HOME would be /u01/app/11.2.0.2/grid and ORACLE_HOME would be /u01/app/11.2.0.2/db_1. It seems like the owners aren't setup correctly. Why? I don't want problems with patching or upgrading. If this setup is technically incorrect what is the best way to setup so there's no owner/permission issues. Is it necessary to have two separate ORACLE_BASE's like /u01/app/grid?
    PRODUCTION REAL APPLICATION CLUSTER (Displaying only one Node details)
    $ cd app
    drwxr-xr-x 6 root oinstall 4096 Feb 26 2011 .
    drwxr-xr-x 3 root oinstall 4096 Apr 21 2009 ..
    drwxrwxr-x 4 grid oinstall 4096 Feb 26 2011 11.2.0.2
    drwxrwxr-x 2 emagent oinstall 4096 Feb 26 2011 emagent
    drwxrwxr-x 9 oracle oinstall 4096 May 16 2011 oracle
    drwxrwx--- 7 grid oinstall 4096 Feb 26 2011 oraInventory
    $ cd 11.2.0.2
    drwxrwxr-x 4 grid oinstall 4096 Feb 26 2011 .
    drwxr-xr-x 6 root oinstall 4096 Feb 26 2011 ..
    drwxr-xr-x 79 oracle oinstall 4096 Mar 29 2011 db_1
    drwxr-xr-x 69 root oinstall 4096 Feb 26 2011 grid
    $ cd ..
    $ cd oracle
    9 oracle oinstall 4096 May 16 2011 .
    drwxr-xr-x 6 root oinstall 4096 Feb 26 2011 ..
    drwxr-xr-x 4 oracle oinstall 4096 Feb 26 2011 admin
    drwxr-xr-x 3 oracle oinstall 4096 Feb 26 2011 cfgtoollogs
    drwxrwxr-x 2 grid oinstall 4096 Feb 26 2011 Clusterware
    drwxrwxr-x 11 grid oinstall 4096 Feb 26 2011 diag
    drwxrwxr-x 3 grid oinstall 4096 Feb 26 2011 hqrac03
    drwxr----- 3 oracle oinstall 4096 May 16 2011 oradiag_oracle
    drwxr-xr-x 3 root root 4096 Mar 13 2011 oradiag_root
    TEST REAL APPLICATION CLUSTER (Displaying only one Node details)
    $ cd app
    drwxr-xr-x 6 root oinstall 4096 Jan 26 2011 ./
    drwxr-xr-x 3 root oinstall 4096 Jan 26 2009 ../
    drwxrwxr-x 4 root oinstall 4096 Jan 26 2011 11.2.0.2/
    drwxrwxr-x 2 emagent oinstall 4096 Mar 1 2011 emagent/
    drwxrwxr-x 10 grid oinstall 4096 May 16 2011 oracle/
    drwxrwx--- 7 grid oinstall 4096 Jan 27 2011 oraInventory/
    $ cd 11.2.0.2
    drwxrwxr-x 4 root oinstall 4096 Jan 26 2011 ./
    drwxr-xr-x 6 root oinstall 4096 Jan 26 2011 ../
    drwxr-xr-x 80 oracle oinstall 4096 Mar 17 2011 db_1/
    drwxr-xr-x 70 root oinstall 4096 Jan 27 2011 grid/
    $ cd ..
    $ cd oracle
    drwxrwxr-x 10 grid oinstall 4096 May 16 2011 ./
    drwxr-xr-x 6 root oinstall 4096 Jan 26 2011 ../
    drwxr-xr-x 4 oracle oinstall 4096 Feb 2 2011 admin/
    drwxr-xr-x 4 oracle oinstall 4096 Feb 2 2011 cfgtoollogs/
    drwxr-xr-x 2 grid oinstall 4096 Jan 26 2011 Clusterware/
    drwxrwxr-x 11 grid oinstall 4096 Jan 26 2011 diag/
    drwxr-xr-x 3 grid oinstall 4096 Jan 26 2011 hqract03/
    drwxr-xr-x 3 grid oinstall 4096 Mar 23 2011 oradiag_grid/
    drwxr----- 3 oracle oinstall 4096 May 16 2011 oradiag_oracle/
    drwxr-xr-x 3 root root 4096 Jan 27 2011 oradiag_root/
    SINGLE INSTANCE DATABASE (ORACLE RESTART)
    $ cd app
    drwxrwxr-x 6 503 oinstall 4096 Feb 26 2011 .
    drwxr-xr-x 3 root root 4096 Apr 16 2009 ..
    drwxrwxr-x 4 grid oinstall 4096 Feb 26 2011 11.2.0.2
    drwxrwxr-x 8 grid oinstall 4096 Feb 26 2011 oracle
    drwxrwx--- 6 grid oinstall 4096 Feb 26 2011 oraInventory
    $ cd 11.2.0.2
    drwxrwxr-x 4 grid oinstall 4096 Feb 26 2011 .
    drwxrwxr-x 6 503 oinstall 4096 Feb 26 2011 ..
    drwxr-xr-x 76 oracle oinstall 4096 Apr 6 2011 db_1
    drwxr-x--- 69 root oinstall 4096 Feb 26 2011 grid
    $ cd ..
    $ cd oracle
    drwxrwxr-x 8 grid oinstall 4096 Feb 26 2011 .
    drwxrwxr-x 6 503 oinstall 4096 Feb 26 2011 ..
    drwxrwxr-x 5 grid oinstall 4096 Feb 26 2011 admin
    drwxrwxr-x 7 grid oinstall 4096 Feb 26 2011 cfgtoollogs
    drwxrwxr-x 2 grid oinstall 4096 Feb 26 2011 checkpoints
    drwxrwxr-x 2 grid oinstall 4096 Feb 26 2011 Clusterware
    drwxrwxr-x 11 grid oinstall 4096 Feb 26 2011 diag
    drwxrwxr-x 3 grid oinstall 4096 Feb 26 2011 hqods01
    Thanks so much.

    Hello
    I did only check prod, as that is the important one.
    i am afraid that setup is not clean. I won't use the work is wrong, but need to be normalized.
    grid oracle base need to be separate from oracle oracle base, and the grid oracle home, MUST be outside of oracle base/oracle home of the oracle user.
    In a multi user setup, the structure should be as follow.
    grid user, group oinstall, asm* groups
    oracle user, group oinstall, dba and db* groups
    The GRID install, have, grid home and oracle base
    the oracle base for grid should be, /u01/app/grid
    the grid home should be, /u01/app/11.2.0.3/grid
    the Oracle user have several homes, and oracle base
    the oracle base for oracle should be, /u01/oracle
    so, for permissions, when I create this, i do as root
    mkdir -p /u01/app/11.2.0.3/grid
    mkdir -p /u01/app/grid
    mkdir -p /u01/app/oracle
    mkdir -p /u01/app/oraInventory
    chown -R grid:oinstall /u01
    chown -R oracle:oinstall /u01/app/oracle
    then, you install grid .. you have so say oracle home is /u01/app/grid and oracle home is /u01/app/11.2.0.3/grid
    at the end, the root.sh as part of the install will take care of the permissions for oraInventory, and the rest for grid.
    when grid is installed, you can move to the oracle db install you use oracle base as /u01/app/oracle and oracle home as /u01/app/oracle/product/11.2.0.3/dbhome_1
    that will give you
    2 4 drwxr-xr-x 6 root oinstall 4096 Sep 21 03:20 /u01
    5996545 4 drwxr-xr-x 6 root oinstall 4096 Sep 18 22:58 /u01/app
    5996546 4 drwxr-xr-x 8 grid oinstall 4096 Sep 18 22:50 /u01/app/grid
    5996547 4 drwxr-xr-x 3 root oinstall 4096 Sep 18 22:30 /u01/app/11.2.0.3
    5996548 4 drwxr-xr-x 69 root oinstall 4096 Sep 21 10:52 /u01/app/11.2.0.3/grid
    5996549 4 drwxrwx--- 5 grid oinstall 4096 Oct 30 22:08 /u01/app/oraInventory
    7406840 4 drwxr-xr-x 7 oracle oinstall 4096 Oct 30 22:09 /u01/app/oracle
    7406841 4 drwxr-xr-x 3 oracle oinstall 4096 Sep 18 22:58 /u01/app/oracle/product
    7406842 4 drwxr-xr-x 6 oracle oinstall 4096 Oct 30 22:04 /u01/app/oracle/product/11.2.0.3
    7766052 4 drwxr-xr-x 77 oracle oinstall 4096 Nov 2 01:20 /u01/app/oracle/product/11.2.0.3/dbhome_1
    Each user have to use his own oracle_base, as each oracle_base will store files and folders created for logs, admin, diagnostic with different permissions and different usages, for a reason you have role separation.
    example of the content of each oracle base
    $ find /u01/app/oracle/ -maxdepth 1 -ls
    7406840 4 drwxr-xr-x 7 oracle oinstall 4096 Oct 30 22:09 /u01/app/oracle/
    7406841 4 drwxr-xr-x 3 oracle oinstall 4096 Sep 18 22:58 /u01/app/oracle/product
    8749076 4 drwxrwxr-x 3 oracle asmadmin 4096 Sep 18 23:03 /u01/app/oracle/diag
    8749064 4 drwxr-x--- 6 oracle oinstall 4096 Oct 30 22:09 /u01/app/oracle/admin
    8716289 4 drwxr-xr-x 2 oracle oinstall 4096 Oct 30 22:18 /u01/app/oracle/checkpoints
    8749061 4 drwxr-x--- 5 oracle oinstall 4096 Sep 18 23:12 /u01/app/oracle/cfgtoollogs
    $ find /u01/app/grid/ -maxdepth 1 -ls
    5996546 4 drwxr-xr-x 8 grid oinstall 4096 Sep 18 22:50 /u01/app/grid/
    7307540 4 drwxrwxr-x 4 grid oinstall 4096 Sep 18 22:49 /u01/app/grid/diag
    7307474 4 drwxr-xr-x 2 grid oinstall 4096 Sep 18 22:33 /u01/app/grid/Clusterware
    7307265 4 drwxr-xr-x 2 grid oinstall 4096 Sep 18 22:33 /u01/app/grid/checkpoints
    7307532 4 drwxr-x--- 4 grid oinstall 4096 Sep 18 22:49 /u01/app/grid/cfgtoollogs
    7406796 4 drwxr-xr-x 3 root root 4096 Sep 18 22:50 /u01/app/grid/oradiag_root
    Take care,
    Alvaro.

  • Grid Infrastructure installable for Oracle Restart only (No ASM)?

    Hello,
    Can Oracle Grid Infrastructure be installed for its Oracle Restart functionality only? i.e., No ASM,; this box uses local RAID 5 filesystems only.
    This is a standalone 32-bit RHEL 5 system with Oracle Database 10gR2 already installed that I intend to upgrade to 11gR2. Just experimenting with installing Grid Infrastructure for only its restart capability. There isn't anything out there I've found that addresses this other than the Oracle doc stating that the Infrastructure must be installed if I want to use ASM or Oracle Restart.
    I'm currently in the installer in a Software Only installation waiting for my SysAdmin to run the root.sh script, but in looking at this script, it looks like it might try to do things with CRS, voting files and the like, which do not exist.
    Thank you!
    -Jon

    Hi Erik,
    Can Oracle Grid Infrastructure be installed for its Oracle Restart functionality only? Yes ... you can do that installing Software Only
    I'm currently in the installer in a Software Only installation waiting for my SysAdmin to run the root.sh script, but in looking at this script, it looks like it might try to do things with CRS, voting files and the like, which do not exist.Don't worry about that ... at the end of the execution of the root.sh script will report a proceedings to configure only Oracle Restart.
    Only this resource "ora.evmd" will appear online.
    Regards,
    Levi Pereira

  • PSU for Oracle Restart 11.2.0.1 AIX 6.1

    Hi Gurus,
    I have applied the patch 9655006 to GI for standalone i,e Oracle Restart.The patch went through fine but changed the owner on the grid directory and permissions.The grid directory under /u01/app/11.2.0/grid should be owned by root, instead after patch its owned by grid now .
    Let me breakdown the steps that i performed for patch aplication.
    1)Unlocked the grid home as root using command "roothas.pl -unlock"
    2)Applied PSU patch as grid user(grid) using command opatch apply .The patch was applied successfully.
    3)tried locking the grid home again using comand "roothas.pl -patch"
    the command failed with the error "u01/app/11.2.0/grid/bin/crsctl[158]: /u01/app/11.2.0/grid/bin/crsctl.bin: cannot execute".
    4)Tried rolling back the patch with command "opatch rollback -id 9655006" failed with error Copy failed from '/u01/app/11.2.0/grid/.patch_storage/9655006_Jul_6_2010_12_27_31/files/bin/oradnssd' to '/u01/app/11.2.0/grid/bin/oradnssd'...
    5)Gave execute privilege recursively in GI-home/ bin directory and the Oracle Restart Stack came up.
    My concerned is how the privileges got changed and how safe/consistent is the environment now after patch?what would be the impact of this on my existing environment?
    ls -ld /u01/app/11.2.0/grid
    drwxr-xr-x 66 grid oinstall 4096 Aug 12 11:24 /u01/app/11.2.0/grid
    Please any inputs would be really appreciated.
    Thanks

    Hi,
    822424 wrote:
    Hi Gurus,
    I have applied the patch 9655006 to GI for standalone i,e Oracle Restart.The patch went through fine but changed the owner on the grid directory and permissions.The grid directory under /u01/app/11.2.0/grid should be owned by root, instead after patch its owned by grid now .
    Let me breakdown the steps that i performed for patch aplication.
    1)Unlocked the grid home as root using command "roothas.pl -unlock"
    2)*Applied PSU patch as grid user(grid) using command opatch apply .The patch was applied successfully.*
    3)tried locking the grid home again using comand "roothas.pl -patch"
    the command failed with the error "u01/app/11.2.0/grid/bin/crsctl[158]: /u01/app/11.2.0/grid/bin/crsctl.bin: cannot execute".
    4)Tried rolling back the patch with command "opatch rollback -id 9655006" failed with error Copy failed from '/u01/app/11.2.0/grid/.patch_storage/9655006_Jul_6_2010_12_27_31/files/bin/oradnssd' to '/u01/app/11.2.0/grid/bin/oradnssd'...
    5)Gave execute privilege recursively in GI-home/ bin directory and the Oracle Restart Stack came up.
    Did you read README of Patch?
    OPatch Automation for GI
    The utility (opatch) must be executed by an operating system (OS) user with root privileges (usually user root), and it must be executed on each node in the cluster.
    Patching the Oracle Restart Home
    Before patching the Oracle Restart home, keep the Oracle Restart stack up and running.
    To patch the Oracle Restart home, as an administrative user (usually root user) execute a command in the following format:
    #opatch auto <UNZIPPED_PATCH_LOCATION> -oh <path to Oracle Restart home>
    So, opatch with root privileges unlock and relock the GRID_HOME automatically.
    This patch must be applied using an administrative user (usually root user).
    My concerned is how the privileges got changed and how safe/consistent is the environment now after patch?what would be the impact of this on my existing environment?Did you take backup of Grid Home before patch?
    Backup of the Oracle home can be taken using any preferred method. You can use any tool such as zip, tar, and cpio to compress the Oracle home. It is highly recommended to take a backup of Oracle home binaries while applying patch set(s) or patches. You should also backup the Central Inventory where the Oracle home is installed, while taking backup of the Oracle Home.
    If you have backup of Oracle Home then you can restore all files of GRID HOME (Oracle Restart) and apply patch using root user.
    Regards,
    Levi Pereira
    Edited by: Levi Pereira on Aug 15, 2011 8:14 PM

  • Oracle Restart

    I am going to upgrade from 10.2 to 11.2 in linux. I like to add the new feature Oracle restart but i am not going to configure ASM and files hold in file system. If i want to do so how i install Grid Infrastructure seperatly to support only for Oracle restart.

    hi
    The Oracle grid infrastructure for a standalone server is the Oracle software that provides system support for an Oracle database including volume management, file system, and automatic restart capabilities. If you plan to use Oracle Restart or Automatic Storage Management, you must install the grid infrastructure before installing your database.
    pls also check
    http://download.oracle.com/docs/cd/E11882_01/install.112/e10840/oraclerestart.htm#LADBI999
    regards
    zekeriya

  • Do we require two listeners. that is ASM listnener and DB listnener in oracle restart

    Hi,
    I have few question's on oracle restart.
    1) Do we require two listeners. that is ASM listnener and DB listnener if yes why and if not what is the reason ?
    2)If we add the components to OHASD,do we have to restart the services ?

    Hi,
    I don't get the point.
    Listener don't hold connection but only redirect it to Instance, is the instance which create a session/process.
    The use of listener is so small it's only for incoming connection, so after  connection is established it is handled by Oracle Database process.
    If you stop listener only incoming connection are affected, all current connection still alive on database.
    1) ASM Connection is done only when someone try to connect at ASM remotely. It's pretty rare the use of it.
    2) Does not matter if you are using ASM or DB Listener,  ff you have a storm of connection incoming on its listener it should be avoided, in setting up the clients in a manner they don't open 100rds of connections at the same time - and with some listener.ora parameters.
    Still see no reason to have two listener.

  • Oracle Restart - srvctl PRCN-3018 version conflict 11.2.0.3-11.2.0.1

    Hi,
    I get an error when i try to add a 32-bit listener to a 64-bit srvctl. I want Oracle Restart to take care of the listener.
    (I use the 32-bit listener to access 32-bit dll's and it works fine)
    Command:
    srvctl add listener -l listener32 -o c:\oracle\product\11.2.0\client_1
    Error:
    PRCN-3018 : Addition of listener version 11.2.0.3.0 is not allowed using srvctl version 11.2.0.1.0
    -OS: Win2008 r2 64-bit
    -Grid: Oracle 11.2.0.3.0 64-bit
    -DB: Oracle 11.2.0.3.0 64-bit
    -Client: Oracle 11.2.0.3.0 32-bit
    -All Oracle software on the server is 11.2.0.3.0
    -setup.exe used for Grid is from 2011-05-06 03:54
    -setup.exe used for Client is from 2011-05-06 03:54
    -There is only path to the Grid home and no other home.
    I can't see how the Grid srvctl can be 11.2.0.1.0, so maybe its a 32/64 issue or what?

    Hi,
    I get an error when i try to add a 32-bit listener to a 64-bit srvctl. I want Oracle Restart to take care of the listener.
    (I use the 32-bit listener to access 32-bit dll's and it works fine)
    Command:
    srvctl add listener -l listener32 -o c:\oracle\product\11.2.0\client_1
    Error:
    PRCN-3018 : Addition of listener version 11.2.0.3.0 is not allowed using srvctl version 11.2.0.1.0
    -OS: Win2008 r2 64-bit
    -Grid: Oracle 11.2.0.3.0 64-bit
    -DB: Oracle 11.2.0.3.0 64-bit
    -Client: Oracle 11.2.0.3.0 32-bit
    -All Oracle software on the server is 11.2.0.3.0
    -setup.exe used for Grid is from 2011-05-06 03:54
    -setup.exe used for Client is from 2011-05-06 03:54
    -There is only path to the Grid home and no other home.
    I can't see how the Grid srvctl can be 11.2.0.1.0, so maybe its a 32/64 issue or what?

  • Oracle restart for OEM Agent

    Hello ,
    Is there any command in Oracle restart to register OEM agent to Oracle restart such that the AGENT can be stopped/started as part of the Oracle restart process when ever the server is rebooted.
    Thanks
    Venkat

    Hi,
    Do you mean register the agent in the repository or start the agent when the server it is installed on starts up ?
    There's this : http://docs.oracle.com/cd/B19306_01/server.102/b15658/strt_stp.htm#BGBFHGAJ
    So have a script read the /etc/oratab, locate the agent home, and run it's startup from that.
    Should work, someone probably has a better idea but that one seems reasonable.

  • Adding a database to the Oracle Restart Configuration

    Hi,
    I have:
    - 2 nodes - Linux RHEL 5
    - Grid Infrastructure 11.2.0.1
    - Database Standard Edition 11.2.0.1 + RAC
    - All database files on ASM (integrated with GI), software on local storage
    I manually created a clustered database and I am currently trying to add it the Oracle Restart Configuration. The first step is to create a cluster resource for the database using the 'srvctl add database' command. In the documentation I found [http://docs.oracle.com/cd/E11882_01/server.112/e10595/restart005.htm]
    Important:When you manually add a database to the Oracle Restart configuration, you must also add the Oracle grid infrastructure software owner as a member of the OSDBA group of that database. This is because the grid infrastructure components must be able to connect to the database as SYSDBA to start and stop the database.
    For example, if the host user who installed the grid infrastructure home is named grid and the OSDBA group of the new database is named dba, then user grid must be a member of the dba group.>
    In my test system I created the resource without adding the grid user to the OSDBA group of the database and all work fine (at least I don't see any problem). The database is correctly started every time the system starts.
    My question is why it is necessary to add the grid user to the osdba group?
    Regards,
    Tim

    Thanks for the reply.
    It's not so obvious for me. If it was written "...you should...", than it could be treated as recommended. I see "...you MUST also add..." and that for me means it's obligatory.
    When you create a database with DBCA, the grid user is not added to the OSDBA group of the database. I am trying to figure out why.
    Regards,
    Tim

  • Oracle restart: change network interface name

    Hi all,
    Env: Oracle Restart 11.2.0.3 w/ASM.
    I've been trying to look up info about this without any luck so I hope some experts here can shed some light..
    To improve redundancy we're planning to change the network configuration in our Oracle Restart environment from using 1 LAN interface to a bonded interface consisting of 2 interfaces.
    So the change will be from using "eth0" to using "bond0" consisting of "eth0" and "eth1". Are there any changes that must be done in the Oracle Restart configuration to reflect these changes?
    Thank you for your time.

    How to Modify Public Network Information including VIP in Oracle Clusterware (Doc ID 276434.1)
    How to Modify Private Network Information in Oracle Clusterware (Doc ID 283684.1)

  • Need help to check the software update deployment status before restart the VM

    Hello,
    I'm just trying to automate the windows patch deployment for several VM's, I build the entire logic like below,
            Deploy software update --> wait for sometime-->Restart --> Check deployment status(collection = iscomplaint) -->stop
    I know here I'm missing the logic of not checking the patch deployment status before restarting, Can someone help here plz?
    Regards,
    Julie

    Hello
    you can configure a loop for your Activity " Get deployment status(filtered the collection name " until status is succeeded, failed with an embedded loop: http://technet.microsoft.com/en-us/library/hh403826.aspx
    Regards,
    Stefan
    www.sc-orchestrator.eu ,
    Blog sc-orchestrator.eu

  • Automatic restart of dbconsole - Oracle restart - IBM AIX

    Hello, could you please help me with steps for allowing automatic start/stop of dbconsole through oracle restart?
    We have Grid Infraestructure 11G (single instance) and an Oracle Database 11GR2 on Unix AIX.
    Thanks in advance.

    Hi Deepa,
    Yes, it is a good practice to shutdown all database and cluster resources before you reboot the machne. Regarding script, if you are in Oracle RAC 11g Release 2 then you simply need to issue
    "crsctl stop cluster -all" command to shutdown the cluster and it will automatically shutdow all resources including database and listeners in your cluster. If you just want to reboot one machine in cluster then you can use
    crsctl stop cluster -n <machine name>
    I dont' see any reason to have a separate script to do this. Please correct me if I could not understand your requirement.
    Harish Kumar
    http://www.oraxperts.com

  • Managed recovery integrate to oracle restart

    Hi
    I do have 11gR2 standby database with grid infrastructure. Database and listener are registered to oracle restart. They start automatically.
    What do I need to do to automate managed recovery process in oracle restart ?

    I do have 11gR2 standby database with grid infrastructure. Database and listener are registered to oracle restart. They start automatically.
    What do I need to do to automate managed recovery process in oracle restart ?If dataguard broker configured, MRP will started automatically,
    If this is disabled then you have to write a script which calls in profile.

Maybe you are looking for