RMAN Error after Upgrade Oracle to 10.2.0.3 - HP-UX Itanium 64

[Ivonne Leyton]

Befor upgrade I have installed Oracle 10.2.0.2, and the Rman scripts for backup full work fine. After upgrade to 10.2.0.3, have the following errors:

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 05/28/2007 11:57:24
ORA-19505: failed to identify file "/dev/vg_genesis/rgen_data01_8200m"
ORA-27037: unable to obtain file status
HPUX-ia64 Error: 10: No child processes
Additional information: 17

RMAN> **end-of-file**

NOTE: RMAN for archivelogs work fine before and after upgrade.

[Jov]

Hi,

Log into RMAN and redefine channel dev_0 or whatever your target backup device is and re-run backup script to test.


Jov

[Ivonne Leyton]

In the attached file I sent the script of rman, and there is defined the dev_0.

Here is an extract:

RMAN> run {
2> allocate channel 'dev_0' type 'sbt_tape'
3> parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=legan,OB2BARLIST=BD_b036_legan,OB2BARHOSTNAME=b036)';
4> backup incremental level 0
5> format 'BD_b036_legan.dbf'
6> database
7> include current controlfile;
8> }
allocated channel: dev_0
channel dev_0: sid=159 devtype=SBT_TAPE
channel dev_0: Data Protector A.05.50/PHSS_35224/PHSS_35225/DPSOL_00241

Starting backup at 05/28/2007 [11:55:48]
channel dev_0: starting incremental level 0 datafile backupset
channel dev_0: specifying datafile(s) in backupset
input datafile fno=00012 name=/dev/vg_genesis/rgen_data01_8200m
input datafile fno=00013 name=/dev/vg_genesis/rgen_data02_8200m
....
channel dev_0: starting piece 1 at 05/28/2007 [13:55:49]
[Normal] From: BMA@a070 "HP:Ultrium 3-SCSI_1" Time: 5/28/2007 1:57:12 PM
STARTING Media Agent "HP:Ultrium 3-SCSI_1"

[Normal] From: BMA@a070 "HP:Ultrium 3-SCSI_1" Time: 5/28/2007 1:57:12 PM
By: UMA@a070@/dev/rac/c35t0d0
Loading medium from slot 306 to device /dev/rmt/22mn

[Normal] From: OB2BAR_Oracle8@b036 "legan" Time: 5/28/2007 1:56:52 PM
Starting OB2BAR Backup: b036:BD_b036_legan<623771749:1>.dbf "Oracle8"

[Normal] From: OB2BAR_Oracle8@b036 "legan" Time: 5/28/2007 1:57:19 PM
Completed OB2BAR Backup: b036:BD_b036_legan<623771749:1>.dbf "Oracle8"

After this become the error.

thanks & regards,
Ivonne

[Jov]

Seems like an issue on the Media Manager layer. When you did your upgrade, were there any errors?


Jov

[Ivonne Leyton]

In the migrate process don't have errors, but now sometimes when going write redologs, we are seeing the follow error:
Errors in file /oracle/product/admin/legan/bdump/legan_arc0_3603.trc:
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/dev/vg_lega_rdo/raw_redo03b_1_128m'
ORA-15059: invalid device type for ASM disk
Additional information: 255

Oracle said that this is related with lvmchk utility and have to rename, but we don't know if at OS level will be some implications if we doing this.

Please someone answer me and Thanks
Ivonne

[Ivonne Leyton]

Additional Information:

In Production we do the same migrate, and in the RMAN we are having follow errors:

channel dev_3: starting piece 1 at 06/13/2007 [02:11:38]
RMAN-03009: failure of backup command on dev_1 channel at 06/13/2007 02:14:33
ORA-19505: failed to identify file "/dev/vg_lega_data1/raw_data01_4104m"
ORA-15059: invalid device type for ASM disk
Additional information: 255
channel dev_1 disabled, job failed on it will be run on another channel
RMAN-03009: failure of backup command on dev_2 channel at 06/13/2007 02:14:33
ORA-19505: failed to identify file "/dev/vg_lega_data1/raw_data02_4104m"
ORA-27037: unable to obtain file status
HPUX-ia64 Error: 10: No child processes
Additional information: 17
channel dev_2 disabled, job failed on it will be run on another channel
RMAN-03009: failure of backup command on dev_3 channel at 06/13/2007 02:14:33
ORA-19505: failed to identify file "/dev/vg_lega_data1/raw_data10_4104m"
ORA-15059: invalid device type for ASM disk
Additional information: 255

This errors are identical that we are having in the alert.log when try to write redologs.


Regards,
Ivonne

[Martin Decker]

Might be related to Bug 6051728. Check MetaLink Note 434500.1.

Regards,
Martin

[Ivonne Leyton]

I saw that note and the bug associated, but I don't use ASM disk neither symbolic links.

I also have an answer from HP about the solution propose by Oracle (rename lvmchk utility). Following is the answer:

"The script lvmchk is design to work with real disk device files (/dev/dsk or /dev/rdsk).

There are plans for taking to accept a symbolic link, which points to a valid disk device file.

If any other thing is entered, this will return 255. This situation is not planed to change.

It must have certain care at renaming the lvmchk script. Probably, it won't cause any problem but it is not an aceptable solution either.

If the need of renaming the lvmchk link is due to its inhability to accept a symbolic link to a real disk device file, then it will be fixed in the future when this facility is implemented.
But, if the need of renaming it is because it returns 255 when entered a Oracle ASM disk, this will not change in the future.

Rename the standard commands of OS is not a practice that we should encourage in our costumers.

Although, if there is posible to give a list of users and commands that are using lvmchk at present, nobody can assure that any application will use it in the future.
Noadays, the lvmchk is used only by Oracle.

To summarize, the command can be renamed until Oracle finds a way to avoid that its data base aborts when they have ASM disks."

With this answer I understand that this issue has to fix by Oracle, then, I update a SR open at Metalink and I'm waiting for the Oracle answer.

Thanks for all,
Ivonne

[Dennis Handly]

>There are plans for taking to accept a symbolic link, which points to a valid disk device file.

Usually if you add a "/" at the end of a symlink, open no longer thinks it is a symlink and looks at the target. Would this work and do you have control enough to add that "/"?

[Ivonne Leyton]

Dennis:
Thanks for your answer, but I don't use symbolic link neither ASM disks. I'm only use device type /dev/rdsk

Ivonne