on 2009 Feb 18 7:32 AM
Dear Forum,
Something strange happened in our system. I set the backup in DB13 with verification. Earlier the parameter was:
=================================================
command_line /usr/sap/CRQ/SYS/exe/run/brarchive -U -jid ALLOG20071112200000 -d disk -c force -p initCRQ_disk.sap -sd -w
=================================================
But suddenly it changed to:
=================================================
command_line /usr/sap/CRQ/SYS/exe/run/brarchive -U -jid ALLOG20090114200000 -d disk -c force -p initCRQ.sap -sd -w use_rmv
=================================================
We are wondering where the "use_rmv" came from. It is then activating RMAN and causing long running verification. None of the backup parameters changed (initCRQ.sap, initCRQ_disk.sap, etc), eventhough SAP and Oracle parameters, none of them changed.
Checking table SDBAC, nothing set there either.
Please help.
Regards,
Agoes
Request clarification before answering.
Did you upgrade brtools?
If so, SAP note 1016173 might help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Joe,
It happened to 2 systems, CRD and CRQ. I just upgraded kernel for CRD on Feb 7th, but no upgrade on CRQ. The case on CRD started on Monday, Feb 10th and on CRQ started on Tuesday, Feb 11th.
From above cases, I don't think it is related to kernel upgrade.
Kernel on CRQ has just been upgraded last weekend, but brtools version on both remain the same:
release note 849483
kernel release 700
patch date 2008-05-27
patch level 34
make platform hpia64
make mode OCI_102
make date May 31 2008
SAP Basis patch level: SAPKB64021
Regards,
Agoes
Hello Agoes,
you still didn't answer what your version and patch level of brtools is. Often versions of kernel and brtools are not the same.
In your first post you showed command line from two logs of brarchive. Now please check the same two logs again and show the version of brarchive; usually it is in a line at the beginning, something like:
BR00002I BRARCHIVE 7.00 (xy)
My idea was that an upgrade of brarchive might have changed its behaviour.
But like Rohit I think that checking init<SID>.sap will be a good idea too. But no need to post all of it, imho.
You take backup to disk. So what is parameter disk_copy_cmd ?
Any parameters that have a value with the string rman in it?
regards
Hi Joe,
My apology, didn't check before sending. Here is the complete result of brtools -V:
=================================================================
dengar:oracrd 1> brtools -V
BR0651I BRTOOLS 7.00 (34)
Patch Date Info
10 2006-01-05 BR*Tools fail due to SAP license problems (note 912969)
11 2006-01-11 Small functional enhancements in BR*Tools (note 914174)
13 2006-03-29 BR*Tools support for MDM databases (note 936665)
16 2006-08-11 BR*Tools start error: library libnnz10 not found (note 972136)
20 2006-11-24 Extended support for system copy in BR*Tools (note 1003028)
24 2007-03-01 BR*Tools support for Oracle 10g RAC (note 1033126)
25 2007-04-26 BR*Tools failing with ORA-01455 for database > 16 TB (note 1050329)
26 2007-05-31 New BR*Tools command options (note 1060696)
release note 849483
kernel release 700
patch date 2008-05-27
patch level 34
make platform hpia64
make mode OCI_102
make date May 31 2008
=================================================================
init<SID>.sap and init<SID>_disk.sap for both system was from Sep 2008. None was changed.
No RMAN setting activated and 'disk_copy_cmd = copy'.
Here is the activated entries in initCRQ_disk.sap:
=================================================================
backup_mode = all
restore_mode = all
backup_type = online_cons
backup_dev_type = disk
backup_root_dir = /oracle/CRQ/SAPBackup
stage_root_dir = /oracle/CRQ/sapreorg
compress = yes
compress_cmd = "compress -c $ > $"
uncompress_cmd = "uncompress -c $ > $"
compress_dir = /oracle/CRQ/sapreorg
archive_function = save_delete
archive_copy_dir = /oracle/CRQ/SAPBackup/oraarch
archive_stage_dir = /oracle/CRQ/sapbackup
tape_copy_cmd = cpio
disk_copy_cmd = copy
stage_copy_cmd = rcp
cpio_flags = -ovB
cpio_in_flags = -iuvB
cpio_disk_flags = -pdcu
dd_in_flags = "ibs=64k bs=64k"
saveset_members = 1
copy_out_cmd = "dd ibs=8k obs=64k of=$"
copy_in_cmd = "dd ibs=64k obs=8k if=$"
rewind = "mt -f $ rew"
rewind_offline = "mt -f $ offl"
tape_pos_cmd = "mt -f $ fsf $"
tape_size = 1200M
exec_parallel = 0
tape_address = /dev/rmt/0mn
tape_address_rew = /dev/rmt/0m
volume_archive = (CRQA01, CRQA02, CRQA03, CRQA04, CRQA05,
CRQA06, CRQA07, CRQA08, CRQA09, CRQA10,
CRQA11, CRQA12, CRQA13, CRQA14, CRQA15,
CRQA16, CRQA17, CRQA18, CRQA19, CRQA20,
CRQA21, CRQA22, CRQA23, CRQA24, CRQA25,
CRQA26, CRQA27, CRQA28, CRQA29, CRQA30)
volume_backup = (CRQB01, CRQB02, CRQB03, CRQB04, CRQB05,
CRQB06, CRQB07, CRQB08, CRQB09, CRQB10,
CRQB11, CRQB12, CRQB13, CRQB14, CRQB15,
CRQB16, CRQB17, CRQB18, CRQB19, CRQB20,
CRQB21, CRQB22, CRQB23, CRQB24, CRQB25,
CRQB26, CRQB27, CRQB28, CRQB29, CRQB30)
expir_period = 30
tape_use_count = 100
=================================================================
Regards,
Agoes
Hello Agoes,
thanks for clarifying; but may I insist on my previous question?
In your first post you showed command line from two logs of brarchive. Now please check the same two logs again and show the version of brarchive; usually it is in a line at the beginning, something like:
BR00002I BRARCHIVE 7.00 (xy)
Just to make sure...
Hi Joe,
Your request is fair..
Below are the activated entries of initCRQ.sap:
============================================================
backup_mode = all
restore_mode = all
backup_type = online
backup_dev_type = disk
backup_root_dir = /oracle/CRQ/SAPBackup
stage_root_dir = /SAPBackup
compress = yes
compress_cmd = "compress -c $ > $"
uncompress_cmd = "uncompress -c $ > $"
compress_dir = /oracle/CRQ/sapreorg
archive_function = save
archive_copy_dir = /oracle/CRQ/SAPBackup/oraarch
archive_stage_dir = /SAPBackup/oraarch
tape_copy_cmd = cpio
disk_copy_cmd = copy
stage_copy_cmd = rcp
cpio_flags = -ovB
cpio_in_flags = -iuvB
cpio_disk_flags = -pdcu
dd_flags = "obs=64k bs=64k"
dd_in_flags = "ibs=64k bs=64k"
saveset_members = 1
copy_out_cmd = "dd ibs=8k obs=64k of=$"
copy_in_cmd = "dd ibs=64k obs=8k if=$"
rewind = "mt -f $ rew"
rewind_offline = "mt -f $ offl"
tape_pos_cmd = "mt -f $ fsf $"
tape_size = 1200M
exec_parallel = 0
tape_address = /dev/rmt/0mn
tape_address_rew = /dev/rmt/0m
volume_archive = (CRQA01, CRQA02, CRQA03, CRQA04, CRQA05,
CRQA06, CRQA07, CRQA08, CRQA09, CRQA10,
CRQA11, CRQA12, CRQA13, CRQA14, CRQA15,
CRQA16, CRQA17, CRQA18, CRQA19, CRQA20,
CRQA21, CRQA22, CRQA23, CRQA24, CRQA25,
CRQA26, CRQA27, CRQA28, CRQA29, CRQA30)
volume_backup = (CRQB01, CRQB02, CRQB03, CRQB04, CRQB05,
CRQB06, CRQB07, CRQB08, CRQB09, CRQB10,
CRQB11, CRQB12, CRQB13, CRQB14, CRQB15,
CRQB16, CRQB17, CRQB18, CRQB19, CRQB20,
CRQB21, CRQB22, CRQB23, CRQB24, CRQB25,
CRQB26, CRQB27, CRQB28, CRQB29, CRQB30)
expir_period = 30
tape_use_count = 100
cleanup_disk_archive = 14
cleanup_disk_backup = 2
============================================================
Do you think the entry "saveset_members = 1" activated RMAN? It does exist on both initCRQ.sap and initCRQ_disk.sap, but none of them changed recently.
-rwxrwx--- 1 oracrq dba 19191 Sep 18 00:58 initCRQ.sap
-rwxrwxr-x 1 oracrq dba 19221 Sep 5 2006 initCRQ_disk.sap
Regards,
Agoes
Hello Agoes,
for now I can see two possible explanations. And it will be your task to find out whether any one of them is true.
1) You (maybe inadverdently) changed brtools patchlevel, and so changed behaviour. Once again let me insist on my previous question, see above.
2) Sometimes you are using initCRQ.sap, and sometimes initCRQ_disk.sap. They are not the same. A quick glance shows at least that backup_type = online_cons or backup_type = online. I think this could make the difference.
hope this helps
Hi Joe,
You may be right, but below is the brarchive log from Feb 5th:
============================================================
Detail log: adzwatkn.svd
BR0002I BRARCHIVE 7.00 (34)
BR0006I Start of offline redo log processing: adzwatkn.svd 2009-02-05 23.38.37
BR0484I BRARCHIVE log file: /oracle/CRQ/saparch/adzwatkn.svd
BR0477I Oracle pfile /oracle/CRQ/102_64/dbs/initCRQ.ora created from spfile /oracle/CRQ/102_64/dbs/spfileCRQ.ora
BR0101I Parameters
Name Value
oracle_sid CRQ
oracle_home /oracle/CRQ/102_64
oracle_profile /oracle/CRQ/102_64/dbs/initCRQ.ora
sapdata_home /oracle/CRQ
sap_profile /oracle/CRQ/102_64/dbs/initCRQ_disk.sap
backup_dev_type disk
archive_copy_dir /oracle/CRQ/SAPBackup/oraarch
compress yes
compress_cmd compress -c $ > $
uncompress_cmd uncompress -c $ > $
archive_dupl_del only
system_info crqadm/oracrq dengar HP-UX B.11.23 U ia64
oracle_info CRQ 10.2.0.2.0 8192 16608 117512332 dengar UTF8 UTF8
sap_info 640 SAPCRQ CRQ G1370923495 R3_ORA 0020223459
make_info hpia64 OCI_102 May 31 2008
command_line /usr/sap/CRQ/SYS/exe/run/brarchive -U -jid ALLOG20090122200000 -d disk -c force -p initCRQ_disk.sap -sd -w use_rmv
============================================================
It used initCRQ_disk.sap, but use_rmv suddenly showed up. This thing is difficult to explain.
Regards,
Agoes
Hello Agoes,
Has someone recently changed initCRQ_disk.sap file.
Please check this file and make sure no parameters related to RMAN are active
Let me know if this helps
Rohit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
71 | |
33 | |
9 | |
8 | |
8 | |
7 | |
7 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.