MSA Storage
cancel
Showing results for 
Search instead for 
Did you mean: 

[236:6000] Cannot connect to the cell server.

 
Highlighted
Fabio Regis
Occasional Visitor

[236:6000] Cannot connect to the cell server.

Hello I am having trouble understanding the cause of the error "236:6000 Cannot connect to the cell server". Here are the messages of the attempted backup session, any suggestions would be appreciated:

From: BSM@sanbs.gro.it "TMIS_TM" Time: 11/06/2007 12:25:59
OB2BAR application on "tmis1s.gro.it" successfully started.

From: OB2BAR_Tapeless@tmis1s.gro.it "TM" Time: 11/06/2007 12:28:44
Checking configuration (util_oracle8.exe -CHKCONF_IR TM) ...

From: OB2BAR_Tapeless@tmis1s.gro.it "TM" Time: 11/06/2007 12:28:46
Checking of configuration succeeded.


Recovery Manager: Release 9.2.0.1.0 - Production

Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.

connected to target database: TM (DBID=2376035772)
connected to recovery catalog database

RMAN> run {
2> allocate channel 'dev_0' type 'sbt_tape'
3> parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=TM,OB2BARLIST=TMIS_TM,OB2DMAP=1,OB2SMB=1)';
4> backup incremental level 0
5> format 'TMIS_TM.dbf'
6> proxy only
7> database;
8> backup
9> format 'TMIS_TM.dbf'
10> current controlfile;
11> }
12>
allocated channel: dev_0
channel dev_0: sid=23 devtype=SBT_TAPE
channel dev_0: Data Protector A.05.50/DPWIN_00201

Starting backup at 06/11/07 12:28:47
channel dev_0: starting incremental level 0 proxy datafile backup at 06/11/07 12:28:49
channel dev_0: specifying datafile(s) for proxy backup
input datafile fno=00011 name=L:\ORACLE\ORADATA\TM\TS_TM.ORA
proxy file handle=TMIS_TM<624976129:1>.dbf
input datafile fno=00026 name=L:\ORACLE\ORADATA\TM\DSY_DAT1.DBF
proxy file handle=TMIS_TM<624976129:2>.dbf
input datafile fno=00027 name=L:\ORACLE\ORADATA\TM\DSY_DAT2.DBF
proxy file handle=TMIS_TM<624976129:3>.dbf
input datafile fno=00016 name=L:\ORACLE\ORADATA\TM\DAU_DAT1.DBF
proxy file handle=TMIS_TM<624976129:4>.dbf
input datafile fno=00028 name=L:\ORACLE\ORADATA\TM\DSY_IDX1.DBF
proxy file handle=TMIS_TM<624976129:5>.dbf
input datafile fno=00001 name=L:\ORACLE\ORADATA\TM\SYSTEM01.DBF
proxy file handle=TMIS_TM<624976129:6>.dbf
input datafile fno=00015 name=L:\ORACLE\ORADATA\TM\LCM_DATA.DBF
proxy file handle=TMIS_TM<624976129:7>.dbf
input datafile fno=00018 name=L:\ORACLE\ORADATA\TM\DCH_DAT1.DBF
proxy file handle=TMIS_TM<624976129:8>.dbf
input datafile fno=00019 name=L:\ORACLE\ORADATA\TM\DCH_IDX1.DBF
proxy file handle=TMIS_TM<624976129:9>.dbf
input datafile fno=00002 name=L:\ORACLE\ORADATA\TM\UNDOTBS01.DBF
proxy file handle=TMIS_TM<624976129:10>.dbf
input datafile fno=00014 name=L:\ORACLE\ORADATA\TM\LCM_INDEX.DBF
proxy file handle=TMIS_TM<624976129:11>.dbf
input datafile fno=00017 name=L:\ORACLE\ORADATA\TM\DAU_IDX1.DBF
proxy file handle=TMIS_TM<624976129:12>.dbf
input datafile fno=00024 name=L:\ORACLE\ORADATA\TM\DST_DAT1.DBF
proxy file handle=TMIS_TM<624976129:13>.dbf
input datafile fno=00005 name=L:\ORACLE\ORADATA\TM\EXAMPLE01.DBF
proxy file handle=TMIS_TM<624976129:14>.dbf
input datafile fno=00020 name=L:\ORACLE\ORADATA\TM\DGE_DAT1.DBF
proxy file handle=TMIS_TM<624976129:15>.dbf
input datafile fno=00021 name=L:\ORACLE\ORADATA\TM\DGE_IDX1.DBF
proxy file handle=TMIS_TM<624976129:16>.dbf
input datafile fno=00022 name=L:\ORACLE\ORADATA\TM\DRE_DAT1.DBF
proxy file handle=TMIS_TM<624976129:17>.dbf
input datafile fno=00023 name=L:\ORACLE\ORADATA\TM\DRE_IDX1.DBF
proxy file handle=TMIS_TM<624976129:18>.dbf
input datafile fno=00025 name=L:\ORACLE\ORADATA\TM\DST_IDX1.DBF
proxy file handle=TMIS_TM<624976129:19>.dbf
input datafile fno=00010 name=L:\ORACLE\ORADATA\TM\XDB01.DBF
proxy file handle=TMIS_TM<624976129:20>.dbf
input datafile fno=00006 name=L:\ORACLE\ORADATA\TM\INDX01.DBF
proxy file handle=TMIS_TM<624976129:21>.dbf
input datafile fno=00009 name=L:\ORACLE\ORADATA\TM\USERS01.DBF
proxy file handle=TMIS_TM<624976129:22>.dbf
input datafile fno=00013 name=L:\ORACLE\ORADATA\TM\QRYRSPNS.ORA
proxy file handle=TMIS_TM<624976129:23>.dbf
input datafile fno=00003 name=L:\ORACLE\ORADATA\TM\CWMLITE01.DBF
proxy file handle=TMIS_TM<624976129:24>.dbf
input datafile fno=00004 name=L:\ORACLE\ORADATA\TM\DRSYS01.DBF
proxy file handle=TMIS_TM<624976129:25>.dbf
input datafile fno=00007 name=L:\ORACLE\ORADATA\TM\ODM01.DBF
proxy file handle=TMIS_TM<624976129:26>.dbf
input datafile fno=00008 name=L:\ORACLE\ORADATA\TM\TOOLS01.DBF
proxy file handle=TMIS_TM<624976129:27>.dbf
input datafile fno=00012 name=L:\ORACLE\ORADATA\TM\RELCFG.ORA
proxy file handle=TMIS_TM<624976129:28>.dbf
From: SMISA@sanbs.gro.it "SMISA" Time: 11/06/2007 12:26:06
Starting agent on sanbs.gro.it.

From: SMISA@tmis1s.gro.it "SMISA" Time: 11/06/2007 12:28:51
Starting agent on tmis1s.gro.it.

From: SMISA@sanbs.gro.it "SMISA" Time: 11/06/2007 12:26:06
Cannot connect to the cell server.
(Insufficient permissions. Access denied.)

released channel: dev_0
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on dev_0 channel at 06/11/2007 12:29:36
ORA-27199: skgfpst: sbtpcstatus returned error
ORA-19511: Error received from media manager layer, error text:
Resolving to disk level failed

Recovery Manager complete.
From: OB2BAR_Tapeless@tmis1s.gro.it "TM" Time: 11/06/2007 12:29:37
Oracle RMAN command failed with exit status 3.

From: OB2BAR_Tapeless@tmis1s.gro.it "TM" Time: 11/06/2007 12:29:37
There are no errors in the Data Protector SBT library.

From: BSM@sanbs.gro.it "TMIS_TM" Time: 11/06/2007 12:26:52
OB2BAR application on "tmis1s.gro.it" disconnected.

From: SMISA@tmis1s.gro.it "SMISA" Time: 11/06/2007 12:29:37
SMIS-Application agent will start with clean up.

From: SMISA@sanbs.gro.it "SMISA" Time: 11/06/2007 12:26:53
SMIS-Backup agent will start with clean up.

From: SMISA@tmis1s.gro.it "SMISA" Time: 11/06/2007 12:29:37
ABORTED SMIS-Application agent on tmis1s.gro.it.

From: SMISA@sanbs.gro.it "SMISA" Time: 11/06/2007 12:26:53
ABORTED SMIS-Backup agent on sanbs.gro.it.

From: BSM@sanbs.gro.it "TMIS_TM" Time: 11/06/2007 12:26:53
None of the Disk Agents completed successfully.
Session has failed.

From: BSM@sanbs.gro.it "TMIS_TM" Time: 11/06/2007 12:26:53

Backup Statistics:

Session Queuing Time (hours) 0.02
----------------------------------------
Completed Disk Agents ........ 0
Failed Disk Agents ........... 0
Aborted Disk Agents .......... 0
----------------------------------------
Disk Agents Total ........... 0
========================================
Completed Media Agents ....... 0
Failed Media Agents .......... 0
Aborted Media Agents ......... 0
----------------------------------------
Media Agents Total .......... 0
========================================
Mbytes Total ................. 0 MB
Used Media Total ............. 0
Disk Agent Errors Total ...... 0


============================================================================
Session failed!
============================================================================
1 REPLY 1
Fabio Regis
Occasional Visitor

Re: [236:6000] Cannot connect to the cell server.

I have tried changing the user as whom the Data Protector Inet service is started, making it my domain administrator rather than LocalSystem. The domain administrator is in the HP Host Agent Admins user group on the cell server and on the Oracle DB Server that is to be backed-up.

There is no more 236:6000 Major error but the session still fails with a new error:

236:7051 The ZDB database does not contain any valid StorageWorks EVA SMI-S provider information.