Re: Cross Platform to ASM Fails on DB_FILE_NAME_CONVERT - Must be completed by tomorrow AM -
- From: Andrew Kerber <andrew.kerber@xxxxxxxxx>
- To: David Barbour <david.barbour1@xxxxxxxxx>
- Date: Sat, 31 Jan 2015 20:02:26 -0700
Shot in the dark. Put in a slash after the destination disk group name. Looks
like the destination name should have one and does not.
Sent from my iPhone
> On Jan 31, 2015, at 7:03 PM, David Barbour <david.barbour1@xxxxxxxxx> wrote:
>
> Looked at it until I'm blind. Thought maybe I was trying to get too cute.
> Looking at MOS Doc ID 371556.1 it specifically shows:
>
> RMAN> CONVERT DATAFILE
> '/hq/finance/work/tru/tbs_31.f',
> '/hq/finance/work/tru/tbs_32.f',
> '/hq/finance/work/tru/tbs_41.f'
> TO PLATFORM="Solaris[tm] OE (32-bit)"
> FROM PLATFORM="HP TRu64 UNIX"
> DB_FILE_NAME_CONVERT="/hq/finance/work/tru/", "+diskgroup"
> PARALLELISM=5;
>
> So I modified my script to:
> RUN
> {
> CONVERT DATAFILE '/export_tmp/P21_Dump/sr3.data6',
> '/export_tmp/P21_Dump/sr3.data1',
> '/export_tmp/P21_Dump/sr3.data2',
> ......................................................
> '/export_tmp/P21_Dump/sr3.data60'
> TO PLATFORM="Linux x86 64-bit"
> FROM PLATFORM="HP-UX IA (64-bit)"
> DB_FILE_NAME_CONVERT='/export_tmp/P21_Dump/','+P21DATA01';
> }
>
> And got this in the log:
>
> Starting conversion at target at 31-JAN-15
> using target database control file instead of recovery catalog
> allocated channel: ORA_DISK_1
> channel ORA_DISK_1: SID=970 device type=DISK
> allocated channel: ORA_DISK_2
> channel ORA_DISK_2: SID=1131 device type=DISK
> allocated channel: ORA_DISK_3
> channel ORA_DISK_3: SID=1292 device type=DISK
> allocated channel: ORA_DISK_4
> channel ORA_DISK_4: SID=1452 device type=DISK
> allocated channel: ORA_DISK_5
> channel ORA_DISK_5: SID=1775 device type=DISK
> RMAN-00571: ===========================================================
> RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
> RMAN-00571: ===========================================================
> RMAN-03002: failure of conversion at target command at 01/31/2015 19:57:36
> ORA-15122: ASM file name '+P21DATA01sr3.data6' contains an invalid file number
>
>
>> On Sat, Jan 31, 2015 at 7:46 PM, Andrew Kerber <andrew.kerber@xxxxxxxxx>
>> wrote:
>> I think you have an incomplete pairing in the db_file_name_convert setting.
>> Look for a missing quotation mark or comma.
>>
>> Sent from my iPhone
>>
>> > On Jan 31, 2015, at 5:24 PM, David Barbour <david.barbour1@xxxxxxxxx>
>> > wrote:
>> >
>> > Stuck.
>> >
>> > Source: Oracle 11.2.0.3 HP-UX IA (64-bit) "Cooked Files"
>> >
>> > Target: Oracle 11.2.0.3 Linux x86 64-bit ASM
>> >
>> >
>> > I've copied the source datafiles using rman to a directory on the Linux
>> > Server. Now I have an RMAN script to convert the endian and load them
>> > into the SM database.
>> >
>> > Here's the script (with redundant parts omitted):
>> >
>> > RUN
>> > {
>> > CONVERT DATAFILE '/export_tmp/P21_Dump/sr3.data6',
>> > ....................................................
>> > '/export_tmp/P21_Dump/sr3.data60'
>> > TO PLATFORM="Linux x86 64-bit"
>> > FROM PLATFORM="HP-UX IA (64-bit)"
>> > DB_FILE_NAME_CONVERT
>> > '/export_tmp/P21_Dump/sr3.data6','+P21DATA01',
>> > .....................................................
>> > '/export_tmp/P21_Dump/sr3.data60','+P21DATA01';
>> > }
>> >
>> > exit;
>> >
>> > It's failing because it seems to be trying to increment the diskgroup?
>> > Here's the log (well, portions of it anyway):
>> >
>> > Starting conversion at target at 31-JAN-15
>> > using target database control file instead of recovery catalog
>> > allocated channel: ORA_DISK_1
>> > channel ORA_DISK_1: SID=807 device type=DISK
>> > allocated channel: ORA_DISK_2
>> > channel ORA_DISK_2: SID=970 device type=DISK
>> > allocated channel: ORA_DISK_3
>> > channel ORA_DISK_3: SID=1131 device type=DISK
>> > allocated channel: ORA_DISK_4
>> > channel ORA_DISK_4: SID=1292 device type=DISK
>> > allocated channel: ORA_DISK_5
>> > channel ORA_DISK_5: SID=1451 device type=DISK
>> > channel ORA_DISK_1: starting datafile conversion
>> > input file name=/export_tmp/P21_Dump/sr3.data5
>> > channel ORA_DISK_2: starting datafile conversion
>> > input file name=/export_tmp/P21_Dump/sr3.data29
>> > channel ORA_DISK_3: starting datafile conversion
>> > input file name=/export_tmp/P21_Dump/sr3.data50
>> > channel ORA_DISK_4: starting datafile conversion
>> > input file name=/export_tmp/P21_Dump/sr3.data49
>> > channel ORA_DISK_5: starting datafile conversion
>> > input file name=/export_tmp/P21_Dump/sr3.data51
>> > RMAN-00571: ===========================================================
>> > RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
>> > RMAN-00571: ===========================================================
>> > RMAN-03009: failure of conversion at target command on ORA_DISK_2 channel
>> > at 01/31/2015 18:02:29
>> > ORA-19504: failed to create file "+P21DATA019"
>> > ORA-15001: diskgroup "P21DATA019" does not exist or is not mounted
>> > ORA-15001: diskgroup "P21DATA019" does not exist or is not mounted
>> >
>> > Any help? I have to do this tonight.
>
Other related posts:
