Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Failure to allocate channel ORA-27023, BEError(0xe0001005)

Created: 07 Sep 2010 | 2 comments
BKlein's picture
0 0 Votes
Login to vote

We are evaluating BackupExec for possible deployment and I am not having any luck getting the Oracle RMAN agent to work.  The base Linux agent works fine, I can browse to the database I am testing with and see tablespaces and archivelogs but I cannot get a backup job to run.  If anyone can see something that jumps out at them please let me know as I am at my wits end with this.  Notes 310332 , 303003  were used to configure the agent.

Error:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of allocate command on ch0 channel at 09/07/2010 13:00:38
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27023: skgfqsbi: media manager protocol error
ORA-19511: Error received from media manager layer, error text:
    BEError(0xe0001005) Backup Exec encountered an unexpected error.

Client Info:
Linux lin-ch0b6.genscape.com 2.6.18-92.el5 #1 SMP Tue Apr 29 13:16:15 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux Server release 5.2 (Tikanga)

From AgentConfig
Configure database access -> View
     Entry 1
          ObjectName: DBAID
          Port: 5633
     Entry 2
          ObjectName: Machine
          HostUsername: orautsq
          Port: 5633

Configure Oracle instance information -> View
     Entry 1
          ObjectName: utsqa
          DatabaseLogin: sys
          MediaServerName: backupexec.genscape.local
          JobTemplate: Default

From BackupExec console
Tools -> Options -> Oracle -> Modify List
Server = lin-ch0b6.genscape.com
Logon account - orautsq

id orautsq
uid=225(orautsq) gid=200(dba) groups=300(oinstall),400(beoper),200(dba)

The Oracle software is owned by orautsq (There are several other instances as well and each has a different owner but 1 step at a time)

The Resource Credentials used in the test job is
  Resource ->  lin-ch0b6.genscape.com
  Logon Account -> orautsq     (the linux orautsq ID and password)
    Resource ->  Oracle Database "utsqa"
    Logon Account -> Oracle SYS     (the oracle sys ID and password)

Note 303003 says "Create a new backup job using oracle as the account used to connect to the Linux server and Oracle instance(s)." In my case that would be orautsq but when I do that I cannot even browse the database.

Putting the agent in debug mode does not show anything other than the RMAN log that is jumping out at me but sense I have yet to see an agent work I am just looking for anything that looks bad failure, error, etc...   Any help or comments would be useful.

Comments

RahulG's picture
08
Sep
2010
0 Votes 0
Login to vote

http://support.veritas.com/do

http://support.veritas.com/docs/302933
http://support.veritas.com/docs/322985
 Check if this applies
Few steps which you can try
--add hostname mapping on linux server
--modify ralus.cfg file add oracle instance
--disable IPV6
Try reinstalling the agent and Configure the remote agent again

If this response answers your concern, please mark it as a "solution"

BKlein's picture
08
Sep
2010
0 Votes 0
Login to vote

Thanks for the info.  The

Thanks for the info. 

The stubtrace file shows no errors:
Stub library libobk.so loaded successfully, trying to load libbeobk.so and dependent libraries ...
Successfully loaded libbeobk.so and its dependent libraries.

Adding the backupexec server to the linux clients host file did not change anything
IPV6 is disabled
The Oracle instance is in ralus.cfg file (at least there are 10 lines with key Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\Agents\XBSA\Oracle RMAN Agent\SID\utsqa\ that correspond to entries entered during AgentConfig).

I have unistalled and reinstalled several times on this host and several more on another to make sure the issue is not host specific but unless I use some different options I don't think another time will yield a different result.