Re: ANU2508E Wrong write state- any ideas?
We received an error similiar to thisdid you receive any operating
system errors? Ours was shark attached and ended up being an fibre apar.
-Original Message-
From: Lisa Cabanas [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 29, 2002 12:29 PM
To: [EMAIL PROTECTED]
Subject: ANU2508E Wrong write state- any ideas?
Hello *SMers,
On one of our production boxes (data warehouse) this error occurred
yesterday during a hot backup with TDPO 2.2.0.2 (most current patch
available on the ftp site). I can't find anything in the activity log or in
the errpt for the TSM server and the client that correlates with this
error. The message for ANU2508 is:
ANU2508E Wrong write state
Explanation: The operation must be in WRITE state.
System Action: The system returns to the calling
procedure.
User Response: Contact TSM support.
and I am asking for the list's help before I call support. Any one have
any ideas? The storage pool target is ESS disk, with no limit on the size.
Recovery Manager: Release 8.1.6.3.0 - Production
RMAN-06005: connected to target database: HII9 (DBID=1656096066)
RMAN-06008: connected to recovery catalog database
RMAN> run {
2> allocate channel c1 type 'sbt_tape' parms
3> 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
4> allocate channel c2 type 'sbt_tape' parms
5> 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
6> allocate channel c3 type 'sbt_tape' parms
7> 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
8> allocate channel c4 type 'sbt_tape' parms
9> 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
10> backup incremental level = 2
11> format 'df_%U'
12> (database);
13> release channel c1;
14> release channel c2;
15> release channel c3;
16> release channel c4;
17> }
18>
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: c1
RMAN-08500: channel c1: sid=16 devtype=SBT_TAPE
RMAN-08526: channel c1: Tivoli Data Protection for Oracle: version 2.2.0.2
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: c2
RMAN-08500: channel c2: sid=9 devtype=SBT_TAPE
RMAN-08526: channel c2: Tivoli Data Protection for Oracle: version 2.2.0.2
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: c3
RMAN-08500: channel c3: sid=20 devtype=SBT_TAPE
RMAN-08526: channel c3: Tivoli Data Protection for Oracle: version 2.2.0.2
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: c4
RMAN-08500: channel c4: sid=8 devtype=SBT_TAPE
RMAN-08526: channel c4: Tivoli Data Protection for Oracle: version 2.2.0.2
RMAN-03022: compiling command: backup
RMAN-03023: executing command: backup
RMAN-08008: channel c1: starting incremental level 2 datafile backupset
RMAN-08502: set_count=1835 set_stamp=463068016 creation_time=28-MAY-02
RMAN-08010: channel c1: specifying datafile(s) in backupset
RMAN-08522: input datafile fno=4
name=/u91/oradata/HII9/fmsdm/fmsdmindex0313.dbf
RMAN-08522: input datafile fno=00019
name=/u90/oradata/HII9/fmsdm/fmsdmdata047.dbf
RMAN-08522: input datafile fno=00023
name=/u90/oradata/HII9/fmsdm/fmsdmdata0410.dbf
RMAN-08522: input datafile fno=00027
name=/u90/oradata/HII9/fmsdm/fmsdmdata049.dbf
RMAN-08522: input datafile fno=00042
name=/u91/oradata/HII9/fmsdm/fmsdmindex023.dbf
RMAN-08522: input datafile fno=00047
name=/u91/oradata/HII9/fmsdm/fmsdmindex025.dbf
RMAN-08522: input datafile fno=00051
name=/u91/oradata/HII9/fmsdm/fmsdmindex032.dbf
RMAN-08522: input datafile fno=00055
name=/u91/oradata/HII9/fmsdm/fmsdmindex031.dbf
RMAN-08522: input datafile fno=00059
name=/u91/oradata/HII9/fmsdm/fmsdmindex036.dbf
RMAN-08522: input datafile fno=00063
name=/u91/oradata/HII9/fmsdm/fmsdmindex042.dbf
RMAN-08522: input datafile fno=00075
name=/u91/oradata/HII9/fmsdm/fmsdmindex0316.dbf
RMAN-08522: input datafile fno=00032
name=/u90/oradata/HII9/fmsdm/fmsdmdata052.dbf
RMAN-08522: input datafile fno=00016
name=/u90/oradata/HII9/fmsdm/fmsdmdata033.dbf
RMAN-08522: input datafile fno=00039
name=/u91/oradata/HII9/fmsdmfl/fmsdmflindex020.dbf
RMAN-08522: input datafile fno=00071
name=/u91/oradata/HII9/fmsdmpm/fmsdmpmindex020.dbf
RMAN-08522: input datafile fno=00012
name=/u90/oradata/HII9/fmsdm/fmsdmdata012.dbf
RMAN-08522: input datafile fno=1
name=/u90/oradata/HII9/dbsys/system01.dbf
RMAN-08011: including current controlfile in backupset
RMAN-08522: input datafile fno=00037
name=/u91/oradata/HII9/fmsdmfl/fmsdmflindex010.dbf
RMAN-08522: input datafile fno=00072
name=/u90/oradata/HII9/fmsdmpm/fmsdmpmdata010.dbf
RMAN-08008: channel c2: starting incremental level 2 datafile backupset
RMAN-08502: set_count=1836 set_stamp=463068018 creation_time=28-
ANU2508E Wrong write state- any ideas?
Hello *SMers,
On one of our production boxes (data warehouse) this error occurred
yesterday during a hot backup with TDPO 2.2.0.2 (most current patch
available on the ftp site). I can't find anything in the activity log or in
the errpt for the TSM server and the client that correlates with this
error. The message for ANU2508 is:
ANU2508E Wrong write state
Explanation: The operation must be in WRITE state.
System Action: The system returns to the calling
procedure.
User Response: Contact TSM support.
and I am asking for the list's help before I call support. Any one have
any ideas? The storage pool target is ESS disk, with no limit on the size.
Recovery Manager: Release 8.1.6.3.0 - Production
RMAN-06005: connected to target database: HII9 (DBID=1656096066)
RMAN-06008: connected to recovery catalog database
RMAN> run {
2> allocate channel c1 type 'sbt_tape' parms
3> 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
4> allocate channel c2 type 'sbt_tape' parms
5> 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
6> allocate channel c3 type 'sbt_tape' parms
7> 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
8> allocate channel c4 type 'sbt_tape' parms
9> 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
10> backup incremental level = 2
11> format 'df_%U'
12> (database);
13> release channel c1;
14> release channel c2;
15> release channel c3;
16> release channel c4;
17> }
18>
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: c1
RMAN-08500: channel c1: sid=16 devtype=SBT_TAPE
RMAN-08526: channel c1: Tivoli Data Protection for Oracle: version 2.2.0.2
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: c2
RMAN-08500: channel c2: sid=9 devtype=SBT_TAPE
RMAN-08526: channel c2: Tivoli Data Protection for Oracle: version 2.2.0.2
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: c3
RMAN-08500: channel c3: sid=20 devtype=SBT_TAPE
RMAN-08526: channel c3: Tivoli Data Protection for Oracle: version 2.2.0.2
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: c4
RMAN-08500: channel c4: sid=8 devtype=SBT_TAPE
RMAN-08526: channel c4: Tivoli Data Protection for Oracle: version 2.2.0.2
RMAN-03022: compiling command: backup
RMAN-03023: executing command: backup
RMAN-08008: channel c1: starting incremental level 2 datafile backupset
RMAN-08502: set_count=1835 set_stamp=463068016 creation_time=28-MAY-02
RMAN-08010: channel c1: specifying datafile(s) in backupset
RMAN-08522: input datafile fno=4
name=/u91/oradata/HII9/fmsdm/fmsdmindex0313.dbf
RMAN-08522: input datafile fno=00019
name=/u90/oradata/HII9/fmsdm/fmsdmdata047.dbf
RMAN-08522: input datafile fno=00023
name=/u90/oradata/HII9/fmsdm/fmsdmdata0410.dbf
RMAN-08522: input datafile fno=00027
name=/u90/oradata/HII9/fmsdm/fmsdmdata049.dbf
RMAN-08522: input datafile fno=00042
name=/u91/oradata/HII9/fmsdm/fmsdmindex023.dbf
RMAN-08522: input datafile fno=00047
name=/u91/oradata/HII9/fmsdm/fmsdmindex025.dbf
RMAN-08522: input datafile fno=00051
name=/u91/oradata/HII9/fmsdm/fmsdmindex032.dbf
RMAN-08522: input datafile fno=00055
name=/u91/oradata/HII9/fmsdm/fmsdmindex031.dbf
RMAN-08522: input datafile fno=00059
name=/u91/oradata/HII9/fmsdm/fmsdmindex036.dbf
RMAN-08522: input datafile fno=00063
name=/u91/oradata/HII9/fmsdm/fmsdmindex042.dbf
RMAN-08522: input datafile fno=00075
name=/u91/oradata/HII9/fmsdm/fmsdmindex0316.dbf
RMAN-08522: input datafile fno=00032
name=/u90/oradata/HII9/fmsdm/fmsdmdata052.dbf
RMAN-08522: input datafile fno=00016
name=/u90/oradata/HII9/fmsdm/fmsdmdata033.dbf
RMAN-08522: input datafile fno=00039
name=/u91/oradata/HII9/fmsdmfl/fmsdmflindex020.dbf
RMAN-08522: input datafile fno=00071
name=/u91/oradata/HII9/fmsdmpm/fmsdmpmindex020.dbf
RMAN-08522: input datafile fno=00012
name=/u90/oradata/HII9/fmsdm/fmsdmdata012.dbf
RMAN-08522: input datafile fno=1
name=/u90/oradata/HII9/dbsys/system01.dbf
RMAN-08011: including current controlfile in backupset
RMAN-08522: input datafile fno=00037
name=/u91/oradata/HII9/fmsdmfl/fmsdmflindex010.dbf
RMAN-08522: input datafile fno=00072
name=/u90/oradata/HII9/fmsdmpm/fmsdmpmdata010.dbf
RMAN-08008: channel c2: starting incremental level 2 datafile backupset
RMAN-08502: set_count=1836 set_stamp=463068018 creation_time=28-MAY-02
RMAN-08010: channel c2: specifying datafile(s) in backupset
RMAN-08522: input datafile fno=00015
name=/u90/oradata/HII9/fmsdm/fmsdmdata030.dbf
RMAN-08522: input datafile fno=00021
name=/u90/oradata/HII9/fmsdm/fmsdmdata043.dbf
RMAN-08522: input datafile fno=00025
name=/u90/oradata/HII9/fmsdm/fmsdmdata042.dbf
RMAN-08522: input datafile fno=00029
name=/u90/oradata/HII9/fmsdm/fmsdmdata044.dbf
RMAN-08522: input datafile fno=00044
name=/u91/oradata/HII9/fmsdm/fmsdmindex021.dbf
RMAN-08
ANU2508E Wrong write state- any ideas?
Hello *SMers,
On one of our production boxes (data warehouse) this error occurred
yesterday during a hot backup with TDPO 2.2.0.2 (most current patch
available on the ftp site). I can't find anything in the activity log or in
the errpt for the TSM server and the client that correlates with this
error. The message for ANU2508 is:
ANU2508E Wrong write state
Explanation: The operation must be in WRITE state.
System Action: The system returns to the calling
procedure.
User Response: Contact TSM support.
and I am asking for the list's help before I call support. Any one have
any ideas? The storage pool target is ESS disk, with no limit on the size.
Recovery Manager: Release 8.1.6.3.0 - Production
RMAN-06005: connected to target database: HII9 (DBID=1656096066)
RMAN-06008: connected to recovery catalog database
RMAN> run {
2> allocate channel c1 type 'sbt_tape' parms
3> 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
4> allocate channel c2 type 'sbt_tape' parms
5> 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
6> allocate channel c3 type 'sbt_tape' parms
7> 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
8> allocate channel c4 type 'sbt_tape' parms
9> 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
10> backup incremental level = 2
11> format 'df_%U'
12> (database);
13> release channel c1;
14> release channel c2;
15> release channel c3;
16> release channel c4;
17> }
18>
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: c1
RMAN-08500: channel c1: sid=16 devtype=SBT_TAPE
RMAN-08526: channel c1: Tivoli Data Protection for Oracle: version 2.2.0.2
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: c2
RMAN-08500: channel c2: sid=9 devtype=SBT_TAPE
RMAN-08526: channel c2: Tivoli Data Protection for Oracle: version 2.2.0.2
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: c3
RMAN-08500: channel c3: sid=20 devtype=SBT_TAPE
RMAN-08526: channel c3: Tivoli Data Protection for Oracle: version 2.2.0.2
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: c4
RMAN-08500: channel c4: sid=8 devtype=SBT_TAPE
RMAN-08526: channel c4: Tivoli Data Protection for Oracle: version 2.2.0.2
RMAN-03022: compiling command: backup
RMAN-03023: executing command: backup
RMAN-08008: channel c1: starting incremental level 2 datafile backupset
RMAN-08502: set_count=1835 set_stamp=463068016 creation_time=28-MAY-02
RMAN-08010: channel c1: specifying datafile(s) in backupset
RMAN-08522: input datafile fno=4
name=/u91/oradata/HII9/fmsdm/fmsdmindex0313.dbf
RMAN-08522: input datafile fno=00019
name=/u90/oradata/HII9/fmsdm/fmsdmdata047.dbf
RMAN-08522: input datafile fno=00023
name=/u90/oradata/HII9/fmsdm/fmsdmdata0410.dbf
RMAN-08522: input datafile fno=00027
name=/u90/oradata/HII9/fmsdm/fmsdmdata049.dbf
RMAN-08522: input datafile fno=00042
name=/u91/oradata/HII9/fmsdm/fmsdmindex023.dbf
RMAN-08522: input datafile fno=00047
name=/u91/oradata/HII9/fmsdm/fmsdmindex025.dbf
RMAN-08522: input datafile fno=00051
name=/u91/oradata/HII9/fmsdm/fmsdmindex032.dbf
RMAN-08522: input datafile fno=00055
name=/u91/oradata/HII9/fmsdm/fmsdmindex031.dbf
RMAN-08522: input datafile fno=00059
name=/u91/oradata/HII9/fmsdm/fmsdmindex036.dbf
RMAN-08522: input datafile fno=00063
name=/u91/oradata/HII9/fmsdm/fmsdmindex042.dbf
RMAN-08522: input datafile fno=00075
name=/u91/oradata/HII9/fmsdm/fmsdmindex0316.dbf
RMAN-08522: input datafile fno=00032
name=/u90/oradata/HII9/fmsdm/fmsdmdata052.dbf
RMAN-08522: input datafile fno=00016
name=/u90/oradata/HII9/fmsdm/fmsdmdata033.dbf
RMAN-08522: input datafile fno=00039
name=/u91/oradata/HII9/fmsdmfl/fmsdmflindex020.dbf
RMAN-08522: input datafile fno=00071
name=/u91/oradata/HII9/fmsdmpm/fmsdmpmindex020.dbf
RMAN-08522: input datafile fno=00012
name=/u90/oradata/HII9/fmsdm/fmsdmdata012.dbf
RMAN-08522: input datafile fno=1
name=/u90/oradata/HII9/dbsys/system01.dbf
RMAN-08011: including current controlfile in backupset
RMAN-08522: input datafile fno=00037
name=/u91/oradata/HII9/fmsdmfl/fmsdmflindex010.dbf
RMAN-08522: input datafile fno=00072
name=/u90/oradata/HII9/fmsdmpm/fmsdmpmdata010.dbf
RMAN-08008: channel c2: starting incremental level 2 datafile backupset
RMAN-08502: set_count=1836 set_stamp=463068018 creation_time=28-MAY-02
RMAN-08010: channel c2: specifying datafile(s) in backupset
RMAN-08522: input datafile fno=00015
name=/u90/oradata/HII9/fmsdm/fmsdmdata030.dbf
RMAN-08522: input datafile fno=00021
name=/u90/oradata/HII9/fmsdm/fmsdmdata043.dbf
RMAN-08522: input datafile fno=00025
name=/u90/oradata/HII9/fmsdm/fmsdmdata042.dbf
RMAN-08522: input datafile fno=00029
name=/u90/oradata/HII9/fmsdm/fmsdmdata044.dbf
RMAN-08522: input datafile fno=00044
name=/u91/oradata/HII9/fmsdm/fmsdmindex021.dbf
RMAN-08
