Oracle RMAN SBT-error

Last post 01-17-2011, 6:48 AM by Patrik. 2 replies.
Sort Posts: Previous Next
  • Oracle RMAN SBT-error
    Posted: 01-13-2011, 10:28 AM

    I am having problems with my first installations of Oracle iDA and RMAN. Simpana version 9. Client OS RHEL 5.5 + glibc2.5

    It opens the channel with SBT but it gets no good answer from the backup-system. Error messages from the RMAN-log as follows:

    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of allocate command on ch1 channel at 01/12/2011 16:32:58
    ORA-19554: error allocating device, device type: SBT_TAPE, device name:
    ORA-27000: skgfqsbi: failed to initialize storage subsystem (SBT) layer
    Additional information: 7111
    ORA-19511: Error received from media manager layer, error text:
       SBT error = 7111, errno = 0, sbtinit: system error
    RMAN>

    I don't get any leads by looking in the CommServe-logs.

    I have also done a successful Oracle iDA installation on a Windows Server 2003 R2. Configured in the same way as the one on the RedHat-server.

    Anyone got a clue?

    /Patrik

  • Re: Oracle RMAN SBT-error
    Posted: 01-13-2011, 12:12 PM
    • efg is not online. Last active: 07-10-2019, 6:47 PM efg
    • Top 10 Contributor
    • Joined on 02-02-2010
    • CommVault Tinton Falls NJ
    • Expert
    • Points 1,665

    Typically we see these errors when the CV software is installed, and the group security was selected during install without consideration of the primary group for the Oracle user.   The Oracle iDA requires that the oracle user (configured in the iDA) MUST have access to the CV software structures which are owned by "root".  The way this is accomplished is by virtue of Unix's Group access, where when installing CV, the primary group for oracle is specified during the install, and hence the oracle user can access the CV structures using the group permissions.  Typically this group would be set to either "oinstall" or "dba"

     

    If the CV software was installed without setting the "group" security this will not be a problem as the software is then installed with all permissions so the oracle user would have access via the "other" permissions in Unix.

     

    Create a file in the /tmp directory called libcvobk.log with permisions "777" and run another backup.  After the failure take a look at the /tmp/libcvobk.log to see if there are any permissions errors in the log.   If there are, take a look at the file pkginfo which is located under the Base directory of the CV software install.  In that file is a "GALAXY_GROUP" parameter.  Compare that with what the primary group is for the oracle user.  If they are not the same, then I would recommend re-installing ALL the CV software being sure to use the primary group for the oracle user for the install of the CV software.   If you can't re-install, you can open a support ticket and one of our engineers can reconfigure the group without having to re-install the agent.

     

    Thanks!

    Ernie


    Ernst F. Graeler
    Senior Engineer III
    Development
  • Re: Oracle RMAN SBT-error
    Posted: 01-17-2011, 6:48 AM

    It was usrgrouprights that was the problem. I did a test to reinstall the OracleAgent but that did'nt help. But after unistall all CV-software from the client an reinstall the File-agent and the Oracle-agent with the unix usergroup set to oinstall it worked fine.

    Thanks alot!

    /Patrik

The content of the forums, threads and posts reflects the thoughts and opinions of each author, and does not represent the thoughts, opinions, plans or strategies of Commvault Systems, Inc. ("Commvault") and Commvault undertakes no obligation to update, correct or modify any statements made in this forum. Any and all third party links, statements, comments, or feedback posted to, or otherwise provided by this forum, thread or post are not affiliated with, nor endorsed by, Commvault.
Commvault, Commvault and logo, the “CV” logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Commvault Galaxy, Unified Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, QuickSnap, QSnap, Recovery Director, CommServe, CommCell, SnapProtect, ROMS, and CommValue, are trademarks or registered trademarks of Commvault Systems, Inc. All other third party brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners. All specifications are subject to change without notice.
Close
Copyright © 2019 Commvault | All Rights Reserved. | Legal | Privacy Policy