Backup MaxDB 7.6 mit HP Data Protector; Wrong file type
Hallo.
Wir versuchen, eine MaxDB-Datenbank (Rel. 7.6) auf SUSE-LINUX unter Verwendung von HP Data Protector zu sichern. Der Versuch, das Backup durchzuführen, schlägt fehl, da auf dem MaxDB-Server anscheinend die Pipe nicht angelegt werden kann. Folgende Meldung wird ausgegeben:
From: BSM-hph3000.thebis.de "Content_sdb_sdba" Time: 26.04.2008 10:19:16
OB2BAR application on "dell2950.thebis.de" successfully started.
From: OB2BAR_SAPDBBAR-dell2950.thebis.de "SDB" Time: 04/26/08 10:16:22
Executing the dbmcli command: `user_logon'.
From: OB2BAR_SAPDBBAR-dell2950.thebis.de "SDB" Time: 04/26/08 10:16:22
Executing the dbmcli command: `dbm_configset -raw set_variable_1 OB2OPTS="(null)"'.
From: OB2BAR_SAPDBBAR-dell2950.thebis.de "SDB" Time: 04/26/08 10:16:22
Executing the dbmcli command: `dbm_configset -raw set_variable_2 OB2APPNAME=SDB'.
From: OB2BAR_SAPDBBAR-dell2950.thebis.de "SDB" Time: 04/26/08 10:16:22
Executing the dbmcli command: `dbm_configset -raw set_variable_3 OB2BARHOSTNAME=dell2950.thebis.de'.
From: OB2BAR_SAPDBBAR-dell2950.thebis.de "SDB" Time: 04/26/08 10:16:22
Executing the dbmcli command: `dbm_configset -raw set_variable_4 TimeoutWaitFiles=30'.
From: OB2BAR_SAPDBBAR-dell2950.thebis.de "SDB" Time: 04/26/08 10:16:22
Executing the dbmcli command: `dbm_configset -raw BSI_ENV /usr/omni/tmp/SDB.bsi_env'.
From: OB2BAR_SAPDBBAR-dell2950.thebis.de "SDB" Time: 04/26/08 10:16:22
Executing the dbmcli command: `medium_put BACKDP-Data[1]/1 /usr/omni/tmp/SDB.BACKDP-Data[1].1 PIPE DATA 0 8'.
From: OB2BAR_SAPDBBAR-dell2950.thebis.de "SDB" Time: 04/26/08 10:16:22
Executing the dbmcli command: `util_connect'.
From: OB2BAR_SAPDBBAR-dell2950.thebis.de "SDB" Time: 04/26/08 10:16:22
Executing the dbmcli command: `backup_start BACKDP-Data[1] DATA'.
From: OB2BAR_SAPDBBAR-dell2950.thebis.de "SDB" Time: 04/26/08 10:16:23
Error: SAPDB responded with:
-24988,ERR_SQL: SQL error
-903,Host file I/O error
3,Data backup failed
1,Backupmedium #1 (/usr/omni/tmp/SDB.BACKDP-Data[1].1) Wrong file type
6,Backup error occured, Errorcode 3700 "hostfile_error"
17,Servertask Info: because Error in backup task occured
10,Job 1 (Backup / Restore Medium Task) WaitingT131 Result=3700
6,Error in backup task occured, Errorcode 3700 "hostfile_error"
From: OB2BAR_SAPDBBAR-dell2950.thebis.de "SDB" Time: 04/26/08 10:16:23
Executing the dbmcli command: `exit'.
From: BSM-hph3000.thebis.de "Content_sdb_sdba" Time: 26.04.2008 10:19:18
OB2BAR application on "dell2950.thebis.de" disconnected.
From: BSM-hph3000.thebis.de "Content_sdb_sdba" Time: 26.04.2008 10:19:18
None of the Disk Agents completed successfully.
Session has failed.
Ein Versuch, die Pipe /usr/omni/tmp/SDB.BACKDP-Data[1].1 manuell auf dem MaxDB-Server anzulegen, schlug ebenso fehl. Eine Pipe /usr/omni/tmp/SDB.BACKDP-Data kann angelegt werden.
Frage 1) Hat jemand ein ähnliches Problem und dazu eine Lösung?
Frage 2) Wo ist hinterlegt, welchen Medium-Name der Data Protector beim command "medium_put" verwenden soll?
Danke für Eure Hilfe!
Gruß
Gerhard Krauß
Heidelberg
Hi Marcus,
we use the version 5.5.
The pipe name is generated by the Data Protector. When I want to create manually a pipe with this name I got the message "No hit found".
Do you know a possibilty where we can configure (at Data Protector or MaxDB) which medium name should be used for creating the pipe?
Thanks a lot!
Gerhard
Similar Messages
-
Export data for domain data make wrong file
Hi!
If I try export data from table with column with type such as MDSYS.SDO_GEOMETRY in SQL developer (1.2.0 and 1.2.1.3213 both) result file will be with information like (for insert clause):
Insert into table_name (NUMB,GEOLOC) values (500949,'MDSYS.SDO_GEOMETRY');.
Also in previous version (1.2.0) when this column was shown in data window it was more informative:
MDSYS.SDO_GEOMETRY(2006, 262148, NULL, MDSYS.SDO_ELEM_INFO_ARRAY(1,2,1,95,2,1,109,2,1,133,2,1,157,2,1), MDSYS.SDO_ORDINATE_ARRAY(22847.57591,7216.21100000001,22842.04691,7217.2571,22841.44841,7218.00440000001,22843.39211,7228.31675000001,22844.13881,7232.35205000001,22845.63335,7239.52580000001,22845.63335,7240.27310000001,22845.03599,7240.72145000001,22826.05499,7244.15885000001,22814.39735,7246.10180000001,22809.01769,7246.84910000001,22807.67249,7246.40075000001,22802.44103,7222.33850000001,22799.19203,7213.03505000001,22795.8656525,7208.73815000001,22794.81386,7208.73200000001,22789.47752,7208.70080000001,22784.3570675,7209.03725000001,22758.6899675,7184.04095000001,22757.3447675,7183.59260000001,22751.9645375,7183.59245000001,22744.006055,7183.03205000001,22743.258785,7181.83640000001,22737.1684775,7181.35070000001,22736.7201725,7182.69575,22729.546295,7183.59245000001,22726.7066975,7186.58165000001,22725.9594275,7186.73105000001,22725.2121575,7186.43210000001,22723.11983,7184.56400000001,22722.29789,7184.48915000001,22721.55062,7186.28270000001,22721.326325,7186.80575000001,22717.515305,7191.36410000001,22715.7218,7193.68070000001,22710.1920875,7200.48080000001,22709.4448175,7206.90740000001,22709.370005,7214.15585000001,22709.74364,7214.52950000001,22711.6866275,7215.35150000001,22711.83611,7216.84610000001,22711.98545,7220.05925000001,22711.611815,7236.12560000001,22711.3876625,7247.63360000001,22711.4249975,7249.76345000001,22710.7523975,7250.95910000001,22710.0051275,7252.45355000001,22849.96763,7244.45780000001,22848.8559875,7243.04300000001,22848.32375,7242.36545000001,22849.51961,7243.41155000001,22848.8559875,7243.04300000001,22846.82921,7241.91710000001,22826.05499,7244.15885000001,22263.062285,7163.22935000001,22263.809555,7173.01865000001,22265.67773,7194.61475000001,22265.902025,7196.78180000001,22265.902025,7197.23015000001,22265.8272125,7197.37970000001,22265.304095,7197.97745000001,22217.9272625,7201.19075,22217.1799925,7201.56440000001,22216.8063575,7202.31170000001,22216.35791,7204.47875000001,22216.731545,7206.12275000001,22800.2381225,7220.28350000001,22798.3699475,7214.23070000001,22796.651255,7211.31620000001,22795.3061975,7209.82175000001,22794.9325625,7209.22385000001,22794.81386,7208.73200000001,22785.5170175,7170.21620000001,22777.3717175,7133.0768,22776.9234125,7130.76035000001,22775.727695,7125.90305000001,22774.6816025,7120.82150000001,22773.7100375,7115.81480000001,22774.53212,7109.98610000001,22774.4573075,7110.73340000001,22773.2617325,7111.70480000001,22773.1870625,7112.45210000001,22773.7100375,7115.81480000001,22773.11225,7113.87185000001,22767.95603,7108.93985000001))
when new one:
MDSYS.SDO_GEOMETRY
WBR,
SergeyI'm newbie here and not sure what you want exactly but.
First of all I've created table on Oracle 10G (10.2.0.3) Enterprise ed as follow:
CREATE TABLE tblnm
"MI_PRINX" NUMBER(11,0),
"GEOLOC" MDSYS.SDO_GEOMETRY,
CONSTRAINT RP_MAP_PK PRIMARY KEY (MI_PRINX)
INSERT INTO USER_SDO_GEOM_METADATA (TABLE_NAME, COLUMN_NAME, DIMINFO, SRID)
VALUES ('tblnm','GEOLOC',MDSYS.SDO_DIM_ARRAY(mdsys.sdo_dim_element('X', -100000.0, 185000.0, 1.425E-5), mdsys.sdo_dim_element('Y', -100000.0, 200000.0, 1.5E-5)),262148);
CREATE INDEX tblnm_SX ON tblnm (GEOLOC)
INDEXTYPE IS MDSYS.SPATIAL_INDEX;
insert into tblnm (MI_PRINX,GEOLOC) VALUES
(1,MDSYS.SDO_GEOMETRY(2001, 262148, NULL, MDSYS.SDO_ELEM_INFO_ARRAY(1,1,1), MDSYS.SDO_ORDINATE_ARRAY(6946.74932,9604.25675000001)));
After that I've export data from this table by SQLDeveloper:
as insert clause result was
-- INSERTING into TBLNM
Insert into TBLNM (MI_PRINX,GEOLOC) values (1,'MDSYS.SDO_GEOMETRY');
when I've try to import data (after delete) by this command i've got:
ERROR at line 1:
ORA-00932: inconsistent datatypes: expected MDSYS.SDO_GEOMETRY got CHAR
for loader clause file looks like
LOAD DATA
INFILE *
Truncate
INTO TABLE "TBLNM"
FIELDS TERMINATED BY ','
TRAILING NULLCOLS
(MI_PRINX,
GEOLOC)
begindata
"1","MDSYS.SDO_GEOMETRY"
and so one. Result file doesn't consist data for sdo_geometry column - only name of class. -
MaxDB backup problem through Data protector
When I start the Online MaxDB database backup through Data Protector GUI the backup fails with error as below,
Normal] From: BSM@ttcsap10 "MAXDB_Online" Time: 6/17/10 4:30:49 AM
OB2BAR application on "ttcmaxdr" successfully started.
[Normal] From: OB2BAR_SAPDBBAR@ttcmaxdr "MAX" Time: 06/17/10 04:30:50
Executing the dbmcli command: `user_logon'.
[Normal] From: OB2BAR_SAPDBBAR@ttcmaxdr "MAX" Time: 06/17/10 04:30:50
Executing the dbmcli command: `dbm_configset -raw set_variable_1 OB2OPTS=""'.
[Normal] From: OB2BAR_SAPDBBAR@ttcmaxdr "MAX" Time: 06/17/10 04:30:50
Executing the dbmcli command: `dbm_configset -raw set_variable_2 OB2APPNAME=MAX'.
[Normal] From: OB2BAR_SAPDBBAR@ttcmaxdr "MAX" Time: 06/17/10 04:30:50
Executing the dbmcli command: `dbm_configset -raw set_variable_3 OB2BARHOSTNAME=ttcmaxdr'.
[Normal] From: OB2BAR_SAPDBBAR@ttcmaxdr "MAX" Time: 06/17/10 04:30:50
Executing the dbmcli command: `dbm_configset -raw set_variable_4 TimeoutWaitFiles=30'.
[Normal] From: OB2BAR_SAPDBBAR@ttcmaxdr "MAX" Time: 06/17/10 04:30:51
Executing the dbmcli command: `dbm_configset -raw BSI_ENV /var/opt/omni/tmp/MAX.bsi_env'.
[Normal] From: OB2BAR_SAPDBBAR@ttcmaxdr "MAX" Time: 06/17/10 04:30:51
Executing the dbmcli command: `medium_put BACKDP-Data[2]/1 /var/opt/omni/tmp/MAX.BACKDP-Data[2].1 PIPE DATA 0 8'.
[Normal] From: OB2BAR_SAPDBBAR@ttcmaxdr "MAX" Time: 06/17/10 04:30:51
Executing the dbmcli command: `medium_put BACKDP-Data[2]/2 /var/opt/omni/tmp/MAX.BACKDP-Data[2].2 PIPE DATA 0 8'.
[Normal] From: OB2BAR_SAPDBBAR@ttcmaxdr "MAX" Time: 06/17/10 04:30:51
Executing the dbmcli command: `util_connect'.
[Normal] From: OB2BAR_SAPDBBAR@ttcmaxdr "MAX" Time: 06/17/10 04:30:51
Executing the dbmcli command: `backup_start BACKDP-Data[2] DATA'.
[Critical] From: OB2BAR_SAPDBBAR@ttcmaxdr "MAX" Time: 06/17/10 04:31:45
Error: SAPDB responded with:
-24988,ERR_SQL: SQL error
-903,Host file I/O error
3,Data backup failed
17,Servertask Info: because Error in backup task occured
10,Job 2 (Backup / Restore Medium Task) [executing] WaitingT170 Result=3700
6,Error in backup task occured, Error code 3700 "hostfile_error"
1,Backupmedium #1 (/var/opt/omni/tmp/MAX.BACKDP-Data[2].1) Wrong file type
6,Backup error occured, Error code 3700 "hostfile_error"
17,Servertask Info: because Error in backup task occured
10,Job 1 (Backup / Restore Medium Task) [executing] WaitingT170 Result=3700
6,Error in backup task occured, Error code 3700 "hostfile_error"
[Normal] From: OB2BAR_SAPDBBAR@ttcmaxdr "MAX" Time: 06/17/10 04:31:45
Executing the dbmcli command: `exit'.
[Normal] From: BSM@ttcsap10 "MAXDB_Online" Time: 6/17/10 4:31:46 AM
OB2BAR application on "ttcmaxdr" disconnected.
[Critical] From: BSM@ttcsap10 "MAXDB_Online" Time: 6/17/10 4:31:46 AM
None of the Disk Agents completed successfully.
Session has failed.
[Normal] From: BSM@ttcsap10 "MAXDB_Online" Time: 6/17/10 4:31:46 AM
Backup Statistics:
Session Queuing Time (hours) 0.00
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
But I have noticed the error is because of this line as below,
Executing the dbmcli command: `medium_put BACKDP-Data[2]/1 /var/opt/omni/tmp/MAX.BACKDP-Data[2].1 PIPE DATA 0 8'.
Actually it should execute the dbmcli command as
medium_put BACKDP-Data[2]/1 /var/opt/omni/tmp/MAX.BACKDP-Data[2].1 PIPE DATA 0 8 NO NO \" \" "BACK"
But I donu2019t know where to make changes so that when I start the backup through DP GUI it should use backup tool as u201CBACKu201D
But same DP backup specification is working through MaxDB Database Manager GUI.
Any solution appreciatedu2026
Thanks,
SubbaHi Natalia,
Thanks for the reply...Please find the answer as below,
-> What is the version of Data Protector?
Data Protector 5.5
-> What is the version of the database?
SAP MaxDB 7.6
-> According your information you could use the DBMGUI to create the medium of u201CBACKu201D type and create the databackup using this medium. Correct?
Yes
The problems are with Data Protector GUI, not with MAXDB or DBMGUI. Correct?
Yes
Please let me know where to make any changes or any enviornment settings to be done in Data Protector GUI so that it will use the medium "BACK" as backup tool while i start the backup through Data Protector GUI.
Thanks,
Subba -
Poor restore performance with MaxDB 7.6.04.15 and HP Data Protector 6
We encounter severe problems with the MaxDB integration in Data Protector 6. While the backup is finished in two hours (LTO4), the restore takes 9-12 hours.
The source system has the following specs:
CPU: 4x QuadCore
RAM: 48 GB
Cache Size: 25 GB
db size (allocated): 550 GB
27x 30 GB raw devices, located in SAN
SLES 10 SP2
parallelism (# pipes): 14 (tried 4, 8, 28, 2 tapes...)
Target system:
CPU: 2x DualCore
RAM: 8 GB
Cache Size: 4 GB
27x 30 GB raw devices, located in SAN
SLES 10 SP2
We checked the performance of file system restores - works fine with good restore times, so we don't think it's a SAN/tape library issue (e. g. switches etc.).
Some things are quite disturbing:
x_cons <SID> show sus
SERVERDB: <SID>
List of suspend-reasons:
========================
Total Suspends: 428083
Vsuspend (203) : 426288 ( 99.58% ) kb39read_wait
Vsuspend (204) : 1611 ( 0.38% ) kb39write_wait
JobWait BckRec : 1 ( 0.00% ) SrvTasks_BackupServer::WaitForAnyJobFini
No-Work (255) : 183 ( 0.04% ) Task is waiting for work
x_cons <SID> show tasks|grep BUP
T71 6 -1 BUPvol -1 AsynWaitWrite 0 0 1027577(s)
T72 6 -1 BUPvol -1 AsynWaitWrite 0 0 1027577(s)
T73 6 -1 BUPvol -1 AsynWaitWrite 0 0 1027577(s)
T74 6 -1 BUPvol -1 AsynWaitWrite 0 0 1027577(s)
T75 6 -1 BUPvol -1 AsynWaitWrite 0 0 1027577(s)
T76 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
T77 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
T78 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
T79 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
T80 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
T81 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
T82 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
T83 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
T84 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
T85 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
T86 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
T87 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
T88 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
T89 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
T92 6 -1 BUPvol -1 AsynWaitWrite 0 0 1027577(s)
T109 6 -1 BUPvol -1 AsynWaitWrite 0 0 1027577(s)
T111 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T112 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T128 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T129 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T130 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T131 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T132 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T133 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T134 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T135 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T136 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T137 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T138 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T139 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T140 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T141 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T142 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T143 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T144 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T148 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
I tried changing parameters a bit with no visible effort. The current parameters of the target system are:
2008-09-16 15:54:01 6300 20235 RTE ADMIN=1
2008-09-16 15:54:01 6300 20235 RTE _AK_DUMP_ALLOWED=YES
2008-09-16 15:54:01 6300 20235 RTE ALLOW_MULTIPLE_SERVERTASK_UKTS=YES
2008-09-16 15:54:01 6300 20235 RTE AUTHENTICATION_ALLOW=
2008-09-16 15:54:01 6300 20235 RTE AUTHENTICATION_DENY=
2008-09-16 15:54:01 6300 20235 RTE AUTOSAVE=1
2008-09-16 15:54:01 6300 20235 RTE AUTO_RECREATE_BAD_INDEXES=YES
2008-09-16 15:54:01 6300 20235 RTE BACKUPRESULT=1
2008-09-16 15:54:01 6300 20235 RTE BACKUP_BLOCK_CNT=64
2008-09-16 15:54:01 6300 20235 RTE _BACKUP_HISTFILE=dbm.knl
2008-09-16 15:54:01 6300 20235 RTE _BACKUP_MED_DEF=dbm.mdf
2008-09-16 15:54:01 6300 20235 RTE CACHE_IN_SHARED_MEMORY=NO
2008-09-16 15:54:01 6300 20235 RTE CACHE_SIZE=512000
2008-09-16 15:54:01 6300 20235 RTE CALLSTACKLEVEL=0
2008-09-16 15:54:01 6300 20235 RTE _CAT_CACHE_MINSIZE=262144
2008-09-16 15:54:01 6300 20235 RTE CAT_CACHE_SUPPLY=12864
2008-09-16 15:54:01 6300 20235 RTE CHECKDATA=1
2008-09-16 15:54:01 6300 20235 RTE CHECK_BACKUP=NO
2008-09-16 15:54:01 6300 20235 RTE CHECK_COMMON=0
2008-09-16 15:54:01 6300 20235 RTE CHECK_CONVERTER=0
2008-09-16 15:54:01 6300 20235 RTE CHECK_DATACACHE=NO
2008-09-16 15:54:01 6300 20235 RTE CHECK_DATAINDEX=0
2008-09-16 15:54:01 6300 20235 RTE CHECK_DATAPAGELOG=0
2008-09-16 15:54:01 6300 20235 RTE CHECK_FBM=0
2008-09-16 15:54:01 6300 20235 RTE CHECK_HASHED_RESULTSET=0
2008-09-16 15:54:01 6300 20235 RTE CHECK_IOMAN=0
2008-09-16 15:54:01 6300 20235 RTE CHECK_KB_REGIONS=NO
2008-09-16 15:54:01 6300 20235 RTE CHECK_LOCK_SUPPLY=NO
2008-09-16 15:54:01 6300 20235 RTE CHECK_LOCK=NO
2008-09-16 15:54:01 6300 20235 RTE CHECK_LOGHISTORY=0
2008-09-16 15:54:01 6300 20235 RTE CHECK_LOGPAGE=0
2008-09-16 15:54:01 6300 20235 RTE CHECK_LOGTRANS=0
2008-09-16 15:54:01 6300 20235 RTE CHECK_LOGVOLUME=0
2008-09-16 15:54:01 6300 20235 RTE CHECK_QUERYREWRITE=0
2008-09-16 15:54:01 6300 20235 RTE CHECK_REGIONS=NO
2008-09-16 15:54:01 6300 20235 RTE CHECK_SRVTASKS=0
2008-09-16 15:54:01 6300 20235 RTE CHECK_TABLE_WIDTH=NO
2008-09-16 15:54:01 6300 20235 RTE CHECK_TASK_SPECIFIC_CATALOGCACHE=NO
2008-09-16 15:54:01 6300 20235 RTE CHECK_TRANSLIST=NO
2008-09-16 15:54:01 6300 20235 RTE CHECK_TREE_LOCKS=NO
2008-09-16 15:54:01 6300 20235 RTE CHECK_TREE=NO
2008-09-16 15:54:01 6300 20235 RTE CLUSTERED_LOBS=NO
2008-09-16 15:54:01 6300 20235 RTE CLUSTER_WRITE_THRESHOLD=80
2008-09-16 15:54:01 6300 20235 RTE COLUMNCOMPRESSION=YES
2008-09-16 15:54:01 6300 20235 RTE _COMMENT=
2008-09-16 15:54:01 6300 20235 RTE CONTROLPASSWORD=***
2008-09-16 15:54:01 6300 20235 RTE CONTROLUSERID=CONTROL
2008-09-16 15:54:01 6300 20235 RTE CONVERTER_REGIONS=64
2008-09-16 15:54:01 6300 20235 RTE DATABASEFULL=1
2008-09-16 15:54:01 6300 20235 RTE _DATA_CACHE_RGNS=64
2008-09-16 15:54:01 6300 20235 RTE DATA_IO_BLOCK_COUNT=64
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_GROUPS=1
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0001=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0002=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0003=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0004=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0005=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0006=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0007=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0008=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0009=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0010=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0011=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0012=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0013=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0014=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0015=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0016=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0017=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0018=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0019=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0020=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0021=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0022=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0023=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0024=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0025=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0026=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0027=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0001=/dev/raw/raw1
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0002=/dev/raw/raw2
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0003=/dev/raw/raw3
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0004=/dev/raw/raw4
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0005=/dev/raw/raw5
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0006=/dev/raw/raw6
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0007=/dev/raw/raw7
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0008=/dev/raw/raw8
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0009=/dev/raw/raw9
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0010=/dev/raw/raw10
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0011=/dev/raw/raw11
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0012=/dev/raw/raw12
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0013=/dev/raw/raw13
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0014=/dev/raw/raw14
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0015=/dev/raw/raw15
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0016=/dev/raw/raw16
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0017=/dev/raw/raw17
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0018=/dev/raw/raw18
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0019=/dev/raw/raw19
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0020=/dev/raw/raw20
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0021=/dev/raw/raw21
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0022=/dev/raw/raw22
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0023=/dev/raw/raw23
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0024=/dev/raw/raw24
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0025=/dev/raw/raw25
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0026=/dev/raw/raw26
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0027=/dev/raw/raw27
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0001=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0002=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0003=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0004=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0005=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0006=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0007=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0008=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0009=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0010=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0011=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0012=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0013=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0014=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0015=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0016=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0017=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0018=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0019=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0020=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0021=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0022=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0023=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0024=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0025=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0026=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0027=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0001=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0002=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0003=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0004=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0005=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0006=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0007=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0008=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0009=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0010=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0011=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0012=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0013=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0014=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0015=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0016=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0017=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0018=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0019=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0020=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0021=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0022=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0023=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0024=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0025=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0026=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0027=R
2008-09-16 15:54:01 6300 20235 RTE DATE_TIME_FORMAT=INTERNAL
2008-09-16 15:54:01 6300 20235 RTE DBFILLINGABOVELIMIT=70L80M85M90H95H96H97H98H99H
2008-09-16 15:54:01 6300 20235 RTE DBFILLINGBELOWLIMIT=70L80L85L90L95L
2008-09-16 15:54:01 6300 20235 RTE DDLTRIGGER=YES
2008-09-16 15:54:01 6300 20235 RTE DEADLOCK_DETECTION=4
2008-09-16 15:54:01 6300 20235 RTE DEFAULT_CODE=ASCII
2008-09-16 15:54:01 6300 20235 RTE _DELAY_COMMIT=NO
2008-09-16 15:54:01 6300 20235 RTE _DELAY_LOGWRITER=0
2008-09-16 15:54:01 6300 20235 RTE DIAG_HISTORY_NUM=2
2008-09-16 15:54:01 6300 20235 RTE DIAG_HISTORY_PATH=/sapdb/data/wrk/PSR/DIAGHISTORY
2008-09-16 15:54:01 6300 20235 RTE _DIAG_SEM=0
2008-09-16 15:54:01 6300 20235 RTE _DW_IO_AREA_FLUSH=50
2008-09-16 15:54:01 6300 20235 RTE _DW_IO_AREA_SIZE=50
2008-09-16 15:54:01 6300 20235 RTE _DW_LRU_TAIL_FLUSH=25
2008-09-16 15:54:01 6300 20235 RTE _DYN_TASK_STACK=NO
2008-09-16 15:54:01 6300 20235 RTE ENABLE_CHECK_INSTANCE=YES
2008-09-16 15:54:01 6300 20235 RTE ENABLE_SYSTEM_TRIGGERS=YES
2008-09-16 15:54:01 6300 20235 RTE ERROR=3
2008-09-16 15:54:01 6300 20235 RTE _EVENTFILE=knldiag.evt
2008-09-16 15:54:01 6300 20235 RTE _EVENTSIZE=0
2008-09-16 15:54:01 6300 20235 RTE EVENT=1
2008-09-16 15:54:01 6300 20235 RTE EXPAND_COM_TRACE=NO
2008-09-16 15:54:01 6300 20235 RTE EXTERNAL_DUMP_REQUEST=NO
2008-09-16 15:54:01 6300 20235 RTE FBM_CLUSTER_MODE=MIXED
2008-09-16 15:54:01 6300 20235 RTE _FBM_LOW_IO_RATE=10
2008-09-16 15:54:01 6300 20235 RTE FBM_VOLUME_BALANCE=10
2008-09-16 15:54:01 6300 20235 RTE FBM_VOLUME_COMPRESSION=50
2008-09-16 15:54:01 6300 20235 RTE FILEDIR_SPINLOCKPOOL_SIZE=10
2008-09-16 15:54:01 6300 20235 RTE FORBID_LOAD_BALANCING=YES
2008-09-16 15:54:01 6300 20235 RTE FORMATTING_MODE=PARALLEL
2008-09-16 15:54:01 6300 20235 RTE FORMAT_DATAVOLUME=YES
2008-09-16 15:54:01 6300 20235 RTE HASHED_RESULTSET_CACHESIZE=262144
2008-09-16 15:54:01 6300 20235 RTE HASHED_RESULTSET=YES
2008-09-16 15:54:01 6300 20235 RTE HEAP_CHECK_LEVEL=0
2008-09-16 15:54:01 6300 20235 RTE HIRES_TIMER_TYPE=CPU
2008-09-16 15:54:01 6300 20235 RTE HS_STORAGE_DLL=libhsscopy
2008-09-16 15:54:01 6300 20235 RTE HS_SYNC_INTERVAL=50
2008-09-16 15:54:01 6300 20235 RTE _IDXFILE_LIST_SIZE=2048
2008-09-16 15:54:01 6300 20235 RTE INDEX_LEAF_CACHING=2
2008-09-16 15:54:01 6300 20235 RTE INIT_ALLOCATORSIZE=262144
2008-09-16 15:54:01 6300 20235 RTE INSTANCE_TYPE=OLTP
2008-09-16 15:54:01 6300 20235 RTE _IOPROCS_FOR_PRIO=0
2008-09-16 15:54:01 6300 20235 RTE _IOPROCS_FOR_READER=1
2008-09-16 15:54:01 6300 20235 RTE _IOPROCS_PER_DEV=2
2008-09-16 15:54:01 6300 20235 RTE _IOPROCS_SWITCH=2
2008-09-16 15:54:01 6300 20235 RTE JOIN_MAXTAB_LEVEL4=64
2008-09-16 15:54:01 6300 20235 RTE JOIN_MAXTAB_LEVEL9=5
2008-09-16 15:54:01 6300 20235 RTE JOIN_SEARCH_LEVEL=0
2008-09-16 15:54:01 6300 20235 RTE JOIN_TABLEBUFFER=128
2008-09-16 15:54:01 6300 20235 RTE _KERNELDIAGFILE=knldiag
2008-09-16 15:54:01 6300 20235 RTE KERNELDIAGSIZE=800
2008-09-16 15:54:01 6300 20235 RTE _KERNELDUMPFILE=knldump
2008-09-16 15:54:01 6300 20235 RTE _KERNELTRACEFILE=knltrace
2008-09-16 15:54:01 6300 20235 RTE KERNELTRACESIZE=2809
2008-09-16 15:54:01 6300 20235 RTE KERNELVERSION=KERNEL 7.6.04 BUILD 015-123-189-221
2008-09-16 15:54:01 6300 20235 RTE _LM_LOCK_REGIONS=0
2008-09-16 15:54:01 6300 20235 RTE _LM_REQUEST_REGIONS=0
2008-09-16 15:54:01 6300 20235 RTE _LM_TRANS_REGIONS=0
2008-09-16 15:54:01 6300 20235 RTE LOAD_BALANCING_CHK=0
2008-09-16 15:54:01 6300 20235 RTE LOAD_BALANCING_DIF=10
2008-09-16 15:54:01 6300 20235 RTE LOAD_BALANCING_EQ=5
2008-09-16 15:54:01 6300 20235 RTE LOCAL_REDO_LOG_BUFFER_SIZE=0
2008-09-16 15:54:01 6300 20235 RTE _LOCKMANAGER_ENABLED=NO
2008-09-16 15:54:01 6300 20235 RTE _LOCK_SUPPLY_BLOCK=100
2008-09-16 15:54:01 6300 20235 RTE LOGABOVELIMIT=50L75L90M95M96H97H98H99H
2008-09-16 15:54:01 6300 20235 RTE LOGFULL=1
2008-09-16 15:54:01 6300 20235 RTE LOGSEGMENTFULL=1
2008-09-16 15:54:01 6300 20235 RTE LOG_BACKUP_TO_PIPE=NO
2008-09-16 15:54:01 6300 20235 RTE LOG_IO_BLOCK_COUNT=8
2008-09-16 15:54:01 6300 20235 RTE LOG_IO_QUEUE=200
2008-09-16 15:54:01 6300 20235 RTE LOG_MIRRORED=NO
2008-09-16 15:54:01 6300 20235 RTE LOG_QUEUE_COUNT=1
2008-09-16 15:54:01 6300 20235 RTE LOG_SEGMENT_SIZE=129024
2008-09-16 15:54:01 6300 20235 RTE LOG_VOLUME_NAME_001=/dev/raw/raw28
2008-09-16 15:54:01 6300 20235 RTE LOG_VOLUME_NAME_002=/dev/raw/raw29
2008-09-16 15:54:01 6300 20235 RTE LOG_VOLUME_SIZE_001=524288
2008-09-16 15:54:01 6300 20235 RTE LOG_VOLUME_SIZE_002=524288
2008-09-16 15:54:01 6300 20235 RTE LOG_VOLUME_TYPE_001=R
2008-09-16 15:54:01 6300 20235 RTE LOG_VOLUME_TYPE_002=R
2008-09-16 15:54:01 6300 20235 RTE LRU_FOR_SCAN=NO
2008-09-16 15:54:01 6300 20235 RTE MAXBACKUPDEVS=32
2008-09-16 15:54:01 6300 20235 RTE MAXCPU=3
2008-09-16 15:54:01 6300 20235 RTE MAXDATAVOLUMES=40
2008-09-16 15:54:01 6300 20235 RTE _MAXEVENTS=100
2008-09-16 15:54:01 6300 20235 RTE _MAXEVENTTASKS=2
2008-09-16 15:54:01 6300 20235 RTE _MAXGARBAGE_COLL=1
2008-09-16 15:54:01 6300 20235 RTE MAXLOCKS=1000000
2008-09-16 15:54:01 6300 20235 RTE MAXLOGVOLUMES=4
2008-09-16 15:54:01 6300 20235 RTE MAXPAGER=64
2008-09-16 15:54:01 6300 20235 RTE MAXRGN_REQUEST=-1
2008-09-16 15:54:01 6300 20235 RTE MAXSERVERTASKS=116
2008-09-16 15:54:01 6300 20235 RTE _MAXTASK_STACK=512
2008-09-16 15:54:01 6300 20235 RTE _MAXTRANS=1604
2008-09-16 15:54:01 6300 20235 RTE MAXUSERTASKS=200
2008-09-16 15:54:01 6300 20235 RTE MAXVOLUMES=45
2008-09-16 15:54:01 6300 20235 RTE MAX_HASHTABLE_MEMORY=5120
2008-09-16 15:54:01 6300 20235 RTE MAX_LOG_QUEUE_COUNT=0
2008-09-16 15:54:01 6300 20235 RTE _MAX_MESSAGE_FILES=0
2008-09-16 15:54:01 6300 20235 RTE MAX_MESSAGE_LIST_LENGTH=100
2008-09-16 15:54:01 6300 20235 RTE MAX_RETENTION_TIME=480
2008-09-16 15:54:01 6300 20235 RTE MAX_SERVERTASK_STACK=500
2008-09-16 15:54:01 6300 20235 RTE MAX_SINGLE_HASHTABLE_SIZE=512
2008-09-16 15:54:01 6300 20235 RTE MAX_SPECIALTASK_STACK=500
2008-09-16 15:54:01 6300 20235 RTE _MBLOCK_DATA_SIZE=32768
2008-09-16 15:54:01 6300 20235 RTE _MBLOCK_QUAL_SIZE=32768
2008-09-16 15:54:01 6300 20235 RTE _MBLOCK_STACK_SIZE=32768
2008-09-16 15:54:01 6300 20235 RTE _MBLOCK_STRAT_SIZE=16384
2008-09-16 15:54:01 6300 20235 RTE MCOD=NO
2008-09-16 15:54:01 6300 20235 RTE MEMORY_ALLOCATION_LIMIT=0
2008-09-16 15:54:01 6300 20235 RTE _MINREPLY_SIZE=4096
2008-09-16 15:54:01 6300 20235 RTE MINSERVERTASKS=116
2008-09-16 15:54:01 6300 20235 RTE MIN_RETENTION_TIME=60
2008-09-16 15:54:01 6300 20235 RTE MONITOR_READ=2147483647
2008-09-16 15:54:01 6300 20235 RTE MONITOR_ROWNO=0
2008-09-16 15:54:01 6300 20235 RTE MONITOR_SELECTIVITY=0
2008-09-16 15:54:01 6300 20235 RTE MONITOR_TIME=2147483647
2008-09-16 15:54:01 6300 20235 RTE _MP_DISP_LOOPS=2
2008-09-16 15:54:01 6300 20235 RTE _MP_DISP_PRIO=DEFAULT
2008-09-16 15:54:01 6300 20235 RTE _MP_RGN_BUSY_WAIT=DEFAULT
2008-09-16 15:54:01 6300 20235 RTE _MP_RGN_DIRTY_READ=DEFAULT
2008-09-16 15:54:01 6300 20235 RTE MP_RGN_LOOP=-1
2008-09-16 15:54:01 6300 20235 RTE _MP_RGN_PRIO=DEFAULT
2008-09-16 15:54:01 6300 20235 RTE _MP_RGN_QUEUE=YES
2008-09-16 15:54:01 6300 20235 RTE NO_SYNC_TO_DISK_WANTED=NO
2008-09-16 15:54:01 6300 20235 RTE OFFICIAL_NODE=
2008-09-16 15:54:01 6300 20235 RTE OMS_HEAP_BLOCKSIZE=10000
2008-09-16 15:54:01 6300 20235 RTE OMS_HEAP_COUNT=8
2008-09-16 15:54:01 6300 20235 RTE OMS_HEAP_LIMIT=0
2008-09-16 15:54:01 6300 20235 RTE OMS_HEAP_THRESHOLD=100
2008-09-16 15:54:01 6300 20235 RTE _OMS_REGIONS=0
2008-09-16 15:54:01 6300 20235 RTE _OMS_RGNS=7
2008-09-16 15:54:01 6300 20235 RTE OMS_RUN_IN_UDE_SERVER=NO
2008-09-16 15:54:01 6300 20235 RTE OMS_STREAM_TIMEOUT=30
2008-09-16 15:54:01 6300 20235 RTE OMS_VERS_THRESHOLD=2097152
2008-09-16 15:54:01 6300 20235 RTE ONLINE=1
2008-09-16 15:54:01 6300 20235 RTE OPMSG1=/dev/console
2008-09-16 15:54:01 6300 20235 RTE OPMSG2=/dev/null
2008-09-16 15:54:01 6300 20235 RTE OPTIMIZE_AGGREGATION=YES
2008-09-16 15:54:01 6300 20235 RTE OPTIMIZE_FETCH_REVERSE=YES
2008-09-16 15:54:01 6300 20235 RTE OPTIMIZE_FIRST_ROWS=YES
2008-09-16 15:54:01 6300 20235 RTE OPTIMIZE_JOIN_HASHTABLE=YES
2008-09-16 15:54:01 6300 20235 RTE OPTIMIZE_JOIN_HASH_MINIMAL_RATIO=1
2008-09-16 15:54:01 6300 20235 RTE OPTIMIZE_JOIN_ONEPHASE=YES
2008-09-16 15:54:01 6300 20235 RTE OPTIMIZE_JOIN_OPERATOR_SORT=YES
2008-09-16 15:54:01 6300 20235 RTE OPTIMIZE_JOIN_OUTER=YES
2008-09-16 15:54:01 6300 20235 RTE OPTIMIZE_JOIN_PARALLEL_MINSIZE=1000000
2008-09-16 15:54:01 6300 20235 RTE OPTIMIZE_JOIN_PARALLEL_SERVERS=0
2008-09-16 15:54:01 6300 20235 RTE OPTIMIZE_MIN_MAX=YES
2008-09-16 15:54:01 6300 20235 RTE OPTIMIZE_OPERATOR_JOIN_COSTFUNC=YES
2008-09-16 15:54:01 6300 20235 RTE OPTIMIZE_OPERATOR_JOIN=YES
2008-09-16 15:54:01 6300 20235 RTE OPTIMIZE_QUAL_ON_INDEX=YES
2008-09-16 15:54:01 6300 20235 RTE OPTIMIZE_QUERYREWRITE=OPERATOR
2008-09-16 15:54:01 6300 20235 RTE OPTIMIZE_STAR_JOIN=YES
2008-09-16 15:54:01 6300 20235 RTE OPTIM_CACHE=NO
2008-09-16 15:54:01 6300 20235 RTE OPTIM_INV_ONLY=YES
2008-09-16 15:54:01 6300 20235 RTE OPTIM_JOIN_FETCH=0
2008-09-16 15:54:01 6300 20235 RTE OPTIM_MAX_MERGE=500
2008-09-16 15:54:01 6300 20235 RTE OUTOFSESSIONS=3
2008-09-16 15:54:01 6300 20235 RTE _PACKET_SIZE=131072
2008-09-16 15:54:01 6300 20235 RTE _PAGE_SIZE=8192
2008-09-16 15:54:01 6300 20235 RTE PREALLOCATE_IOWORKER=NO
2008-09-16 15:54:01 6300 20235 RTE _PRIO_BASE_COM=10
2008-09-16 15:54:01 6300 20235 RTE _PRIO_BASE_IOC=80
2008-09-16 15:54:01 6300 20235 RTE _PRIO_BASE_RAV=80
2008-09-16 15:54:01 6300 20235 RTE _PRIO_BASE_REX=40
2008-09-16 15:54:01 6300 20235 RTE _PRIO_BASE_U2U=100
2008-09-16 15:54:01 6300 20235 RTE _PRIO_FACTOR=80
2008-09-16 15:54:01 6300 20235 RTE PROTECT_DATACACHE_MEMORY=NO
2008-09-16 15:54:01 6300 20235 RTE _READAHEAD_BLOBS=32
2008-09-16 15:54:01 6300 20235 RTE REQUEST_TIMEOUT=5000
2008-09-16 15:54:01 6300 20235 RTE RESERVEDSERVERTASKS=75
2008-09-16 15:54:01 6300 20235 RTE _RESTART_TIME=600
2008-09-16 15:54:01 6300 20235 RTE ROW_LOCKS_PER_TRANSACTION=50
2008-09-16 15:54:01 6300 20235 RTE _ROW_RGNS=8
2008-09-16 15:54:01 6300 20235 RTE _RTEDUMPFILE=rtedump
2008-09-16 15:54:01 6300 20235 RTE RTE_TEST_REGIONS=0
2008-09-16 15:54:01 6300 20235 RTE RUNDIRECTORY=/sapdb/data/wrk/PSR
2008-09-16 15:54:01 6300 20235 RTE SEQUENCE_CACHE=1
2008-09-16 15:54:01 6300 20235 RTE _SERVERDB_FOR_SAP=YES
2008-09-16 15:54:01 6300 20235 RTE SESSION_TIMEOUT=900
2008-09-16 15:54:01 6300 20235 RTE SET_VOLUME_LOCK=YES
2008-09-16 15:54:01 6300 20235 RTE SHAREDSQL_CLEANUPTHRESHOLD=25
2008-09-16 15:54:01 6300 20235 RTE SHAREDSQL_COMMANDCACHESIZE=262144
2008-09-16 15:54:01 6300 20235 RTE SHAREDSQL=YES
2008-09-16 15:54:01 6300 20235 RTE _SHMKERNEL=24377
2008-09-16 15:54:01 6300 20235 RTE SHOW_MAX_KB_STACK_USE=NO
2008-09-16 15:54:01 6300 20235 RTE SHOW_MAX_STACK_USE=NO
2008-09-16 15:54:01 6300 20235 RTE SIMULATE_VECTORIO=NEVER
2008-09-16 15:54:01 6300 20235 RTE SPINLOCK_BACKOFF_BASE=1
2008-09-16 15:54:01 6300 20235 RTE SPINLOCK_BACKOFF_FACTOR=2
2008-09-16 15:54:01 6300 20235 RTE SPINLOCK_BACKOFF_MAXIMUM=64
2008-09-16 15:54:01 6300 20235 RTE SPINLOCK_LOOP_COUNT=30000
2008-09-16 15:54:01 6300 20235 RTE STANDBY=1
2008-09-16 15:54:01 6300 20235 RTE SUBTREE_LOCKS=NO
2008-09-16 15:54:01 6300 20235 RTE SUPPRESS_CORE=YES
2008-09-16 15:54:01 6300 20235 RTE SYMBOL_DEMANGLING=NO
2008-09-16 15:54:01 6300 20235 RTE SYMBOL_RESOLUTION=YES
2008-09-16 15:54:01 6300 20235 RTE SYSTEMERROR=3
2008-09-16 15:54:01 6300 20235 RTE _TAB_RGNS=8
2008-09-16 15:54:01 6300 20235 RTE _TASKCLUSTER_01=tw;al;ut;100*bup;10*ev,10*gc;
2008-09-16 15:54:01 6300 20235 RTE _TASKCLUSTER_02=ti,100*dw;67*us,39*sv;
2008-09-16 15:54:01 6300 20235 RTE _TASKCLUSTER_03=equalize
2008-09-16 15:54:01 6300 20235 RTE TIME_MEASUREMENT=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_AK=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_ALLOCATOR=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_CATALOG=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_CLIENTKERNELCOM=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_COMMON=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_COMMUNICATION=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_CONVERTER=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_DATACACHE=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_DATACHAIN=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_DATAINDEX=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_DATAPAM=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_DATATREE=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_DBPROC=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_DEFAULT=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_DELETE=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_FBM=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_FILEDIR=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_FRAMECTRL=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_INDEX=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_INSERT=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_IOMAN=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_IPC=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_JOIN=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_KSQL=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_LOCKMANAGER=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_LOCK=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_LOGACTION=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_LOGHISTORY=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_LOGPAGE=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_LOGTRANS=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_LOGVOLUME=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_LONG=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_MEMORY=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_MESSAGES=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_OBJECTCONTAINER=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_OBJECT_ADD=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_OBJECT_ALTER=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_OBJECT_FREE=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_OBJECT_GET=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_OBJECT=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_OMS_CONTAINERDIR=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_OMS_CONTEXT=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_OMS_ERROR=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_OMS_FLUSHCACHE=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_OMS_INTERFACE=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_OMS_KEYRANGE=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_OMS_KEY=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_OMS_LOCK=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_OMS_MEMORY=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_OMS_NEWOBJ=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_OMS_SESSION=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_OMS_STREAM=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_OMS_VAROBJECT=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_OMS_VERSION=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_OPTIMIZE=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_ORDER_STANDARD=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_ORDER=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_PAGER=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_PAGES_BUP=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_PAGES_EV=2
2008-09-16 15:54:01 6300 20235 RTE TRACE_PAGES_GC=20
2008-09-16 15:54:01 6300 20235 RTE TRACE_PAGES_LW=5
2008-09-16 15:54:01 6300 20235 RTE TRACE_PAGES_PG=3
2008-09-16 15:54:01 6300 20235 RTE TRACE_PAGES_SV=5
2008-09-16 15:54:01 6300 20235 RTE TRACE_PAGES_TI=2
2008-09-16 15:54:01 6300 20235 RTE TRACE_PAGES_US=10
2008-09-16 15:54:01 6300 20235 RTE TRACE_PAGES_UT=5
2008-09-16 15:54:01 6300 20235 RTE TRACE_PAGES=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_PRIMARY_TREE=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_QUERYREWRITE=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_RUNTIME=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_SELECT=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_SHAREDSQL=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_SQLMANAGER=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_SRVTASKS=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_STOP_ERRORCODE=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_SYNCHRONISATION=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_SYSVIEW=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_TABLE=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_TIME=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_UPDATE=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_VOLUME=0
2008-09-16 15:54:01 6300 20235 RTE TRANS_HISTORY_SIZE=0
2008-09-16 15:54:01 6300 20235 RTE _TRANS_RGNS=8
2008-09-16 15:54:01 6300 20235 RTE TRANS_THRESHOLD_VALUE=60
2008-09-16 15:54:01 6300 20235 RTE UKT_CPU_RELATIONSHIP=NONE
2008-09-16 15:54:01 6300 20235 RTE _UNICODE=YES
2008-09-16 15:54:01 6300 20235 RTE UPDATESTAT_PARALLEL_SERVERS=0
2008-09-16 15:54:01 6300 20235 RTE UPDATESTAT_SAMPLE_ALGO=1
2008-09-16 15:54:01 6300 20235 RTE UPDSTATWANTED=1
2008-09-16 15:54:01 6300 20235 RTE USED_MAX_LOG_QUEUE_COUNT=3
2008-09-16 15:54:01 6300 20235 RTE USESELECTFETCH=YES
2008-09-16 15:54:01 6300 20235 RTE USEUNICODECOLUMNCOMPRESSION=NO
2008-09-16 15:54:01 6300 20235 RTE USEVARIABLEINPUT=NO
2008-09-16 15:54:01 6300 20235 RTE USE_COROUTINES=YES
2008-09-16 15:54:01 6300 20235 RTE _USE_IOPROCS_ONLY=NO
2008-09-16 15:54:01 6300 20235 RTE USE_OPEN_DIRECT_FOR_BACKUP=YES
2008-09-16 15:54:01 6300 20235 RTE USE_OPEN_DIRECT=YES
2008-09-16 15:54:01 6300 20235 RTE USE_SYSTEM_PAGE_CACHE=YES
2008-09-16 15:54:01 6300 20235 RTE _UTILITY_PROTFILE=dbm.utl
2008-09-16 15:54:01 6300 20235 RTE UTILITY_PROTSIZE=100
2008-09-16 15:54:01 6300 20235 RTE VOLUMENO_BIT_COUNT=8
2008-09-16 15:54:01 6300 20235 RTE _WORKDATA_SIZE=8192
2008-09-16 15:54:01 6300 20235 RTE _WORKSTACK_SIZE=8192
2008-09-16 15:54:01 6300 20235 RTE XP_CONVERTER_REGIONS=0
2008-09-16 15:54:01 6300 20235 RTE XP_DATA_CACHE_RGNS=0
2008-09-16 15:54:01 6300 20235 RTE XP_MAXPAGER=0> Some things are quite disturbing:
>
>
x_cons <SID> show sus
>
> SERVERDB: <SID>
>
> List of suspend-reasons:
> ========================
>
> Total Suspends: 428083
>
> Vsuspend (203) : 426288 ( 99.58% ) kb39read_wait
> Vsuspend (204) : 1611 ( 0.38% ) kb39write_wait
> JobWait BckRec : 1 ( 0.00% ) SrvTasks_BackupServer::WaitForAnyJobFini
> No-Work (255) : 183 ( 0.04% ) Task is waiting for work
What exactly do you find disturbing with that information?
All we see here is how often a specific suspend had been triggered since the database was started. We don't see how long these suspends took and neither do we know what the suspend reason is, that would be important for your current issue.
>
x_cons <SID> show tasks|grep BUP
> T71 6 -1 BUPvol -1 AsynWaitWrite 0 0 1027577(s)
> T72 6 -1 BUPvol -1 AsynWaitWrite 0 0 1027577(s)
> T73 6 -1 BUPvol -1 AsynWaitWrite 0 0 1027577(s)
> T74 6 -1 BUPvol -1 AsynWaitWrite 0 0 1027577(s)
> T75 6 -1 BUPvol -1 AsynWaitWrite 0 0 1027577(s)
> T76 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
> T77 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
> T78 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
> T79 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
> T80 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
> T81 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
> T82 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
> T83 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
> T84 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
> T85 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
> T86 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
> T87 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
> T88 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
> T89 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
> T92 6 -1 BUPvol -1 AsynWaitWrite 0 0 1027577(s)
> T109 6 -1 BUPvol -1 AsynWaitWrite 0 0 1027577(s)
> T111 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T112 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T128 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T129 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T130 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T131 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T132 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T133 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T134 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T135 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T136 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T137 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T138 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T139 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T140 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T141 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T142 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T143 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T144 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T148 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
Ok, here we see that the MaxDB kernel is waiting for writes to the datavolumes to get finished. As we've only one snapshot here, we cannot tell anything more from it. You either should perform several snapshots in a row, or (better!) use the DBAnalyzer with a short sample interval, say 60 seconds.
Also you should enable the time measurement, so that we can have some I/O related timing information.
> I tried changing parameters a bit with no visible effort. The current parameters of the target system are:
What parameters did you change? Why? And to what values did you set them?
>
> 2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0001=R
> 2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0002=R
Ok, since you use RAW devices (good choice!) there shouldn't be any issues with the I/O on the OS level.
What's left is: how are the RAW devices physically stored?
Could it be that writing to your RAW devices is pretty expensive?
Ah - before I forget: if you're a SAP customer this should be investigated in a support message!
Best regards,
Lars -
Backup with Data Protector is not working
Hello,
[US]We have an Oracle DB which is saved by HP Data Protector
[FR]Nous avons une BDD Oracle qui est sauvegardée via HP DataProtector.
[US]During our last backup, the Data Protector Server has crashed which has stopped the backup during the process.
[FR]Lors de la dernière sauvegarde, le serveur de backup a planté, arrêtant de ce fait la sauvegarde en cours de la BDD Oracle.
[US]Now, when we are trying to relaunch the backup, it doesn't work at all.
The Data Protector agent is starting, it sends the RMAN command to the DB and then stop.
[FR]Maintenant, lorsque nous voulons relancer la sauvegarde, elle ne fonctionne plus.
L'agent démarre bien, il envoie bien la commande à RMAN qui démarre puis s'arrête.
[US] Of we launch the backup manually thru RMAN, it works
[FR]Lorsqu'on lance cette même sauvegarde manuellement via RMAN, elle fonctionne !
[US]Lors are not really explicit !
[FR]Les logs ne sont pas très parlant:
LOGS of DATA PROTECTOR (in french but I've translated (in bold) which I think, is important)
Citation:
[Normal] De : [email protected] "Base10G_DBName_1_Archivelogs_rman_delete" Heure : 26/02/2013 12:10:31
La session de sauvegarde 2013/02/26-31 a démarré.
[Normal] De : [email protected] "Base10G_DBName_1_Archivelogs_rman_delete" Heure : 26/02/2013 12:10:33
Lancement de l'application OB2BAR sur "clientxxx.domain.com" réalisé avec succès.
[Normal] De : [email protected] "DBNameq" Heure : 26/02/2013 12:10:34
D?marrage de la sauvegarde de la base de donn?es cible.
Nom du service r?seau : DBNameq.
Etat de l'instance : OPEN.
Nom d'instance : DBNameq.
DBID de la base de donn?es = 3864252955.
Type de fichier de contr?le de BDD : CURRENT.
Mode journalisation BDD : ARCHIVELOG.
Logging mode: ARCHIVELOG.
[Normal] De : [email protected] "DBNameq" Heure : 26/02/2013 12:10:35
D?marrage de Oracle Recovery Manager.
Recovery Manager: Release 10.2.0.4.0 - Production on Mar. F?vr. 26 12:10:35 2013
Copyright (c) 1982, 2007, Oracle. All rights reserved.
RMAN> CONNECT TARGET *
2> CONNECT CATALOG *
3> HOST 'exit';
4> run {
5> allocate channel 'dev_0' type 'sbt_tape'
6> parms 'SBT_LIBRARY=C:/PROGRA~1/OmniBack/bin/orasbt.dll,ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=DBNameq,OB2BARLIST=Base10G_DBName_1_Archivelogs_rman_delete)'
7> ;
8> allocate channel 'dev_1' type 'sbt_tape'
9> parms 'SBT_LIBRARY=C:/PROGRA~1/OmniBack/bin/orasbt.dll,ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=DBNameq,OB2BARLIST=Base10G_DBName_1_Archivelogs_rman_delete)'
10> ;
11> allocate channel 'dev_2' type 'sbt_tape'
12> parms 'SBT_LIBRARY=C:/PROGRA~1/OmniBack/bin/orasbt.dll,ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=DBNameq,OB2BARLIST=Base10G_DBName_1_Archivelogs_rman_delete)'
13> ;
14> allocate channel 'dev_3' type 'sbt_tape'
15> parms 'SBT_LIBRARY=C:/PROGRA~1/OmniBack/bin/orasbt.dll,ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=DBNameq,OB2BARLIST=Base10G_DBName_1_Archivelogs_rman_delete)'
16> ;
17> allocate channel 'dev_4' type 'sbt_tape'
18> parms 'SBT_LIBRARY=C:/PROGRA~1/OmniBack/bin/orasbt.dll,ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=DBNameq,OB2BARLIST=Base10G_DBName_1_Archivelogs_rman_delete)'
19> ;
20> allocate channel 'dev_5' type 'sbt_tape'
21> parms 'SBT_LIBRARY=C:/PROGRA~1/OmniBack/bin/orasbt.dll,ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=DBNameq,OB2BARLIST=Base10G_DBName_1_Archivelogs_rman_delete)'
22> ;
23>
24> send device type 'sbt_tape' 'OB2BARHOSTNAME=clientxxx.domain.com';
25> sql 'alter system archive log current';
26> backup
27> format 'Base10G_DBName_1_Archivelogs_rman_delete<DBNameq_%s:%t:%p>.dbf'
28> archivelog all
29> delete input;
30> backup
31> format 'Base10G_DBName_1_Archivelogs_rman_delete<DBNameq_%s:%t:%p>.dbf'
32> current controlfile;
33> }
34> EXIT
RMAN-06005: connect? ? la base de donn?es cible : DBNameQ (DBID=3864252955)
RMAN-06005: connected to targeted database : DBNameQ (DBID=3864252955)
RMAN-06008: connect? ? la base de donn?es du catalogue de r?cup?ration
RMAN-06008: connected to recovery database
RMAN-08030: canal affect? : dev_0
RMAN-08030: allocated chanel : dev_0
RMAN-08500: canal dev_0 : sid=422 typedev=SBT_TAPE
RMAN-08500: dev_0 channel : sid=422 typedev=SBT_TAPE
RMAN-08526: canal dev_0 : Data Protector A.06.20/DPWIN_00536(b621)
RMAN-08526: dev_0 channel : Data Protector A.06.20/DPWIN_00536(b621)
RMAN-08030: canal affect? : dev_1
RMAN-08500: canal dev_1 : sid=888 typedev=SBT_TAPE
RMAN-08526: canal dev_1 : Data Protector A.06.20/DPWIN_00536(b621)
RMAN-08500: canal dev_2 : sid=681 typedev=SBT_TAPE
RMAN-08526: canal dev_2 : Data Protector A.06.20/DPWIN_00536(b621)
RMAN-08030: canal affect? : dev_3
RMAN-08500: canal dev_3 : sid=717 typedev=SBT_TAPE
RMAN-08526: canal dev_3 : Data Protector A.06.20/DPWIN_00536(b621)
RMAN-08030: canal affect? : dev_4
RMAN-08500: canal dev_4 : sid=223 typedev=SBT_TAPE
RMAN-08526: canal dev_4 : Data Protector A.06.20/DPWIN_00536(b621)
RMAN-08030: canal affect? : dev_5
RMAN-08500: canal dev_5 : sid=212 typedev=SBT_TAPE
RMAN-08526: canal dev_5 : Data Protector A.06.20/DPWIN_00536(b621)
RMAN-06421: commande envoy?e au canal : dev_0
RMAN-06421: command send to channel : dev_0
RMAN-06421: commande envoy?e au canal : dev_1
RMAN-06421: commande envoy?e au canal : dev_2
RMAN-06421: commande envoy?e au canal : dev_3
RMAN-06421: commande envoy?e au canal : dev_4
RMAN-06421: commande envoy?e au canal : dev_5
RMAN-06162: instruction SQL : alter system archive log current
RMAN-06162: SQL query : alter system archive log current
RMAN-03090: D?marrage de backup dans 26/02/13
RMAN-03090: BAckup is starting in 26/02/13
RMAN-08031: canal lib?r? : dev_0
RMAN-08031: released channel : dev_0
RMAN-08031: canal lib?r? : dev_1
RMAN-08031: canal lib?r? : dev_2
RMAN-08031: canal lib?r? : dev_3
RMAN-08031: canal lib?r? : dev_4
RMAN-08031: canal lib?r? : dev_5
[Normal] De : [email protected] "Base10G_DBName_1_Archivelogs_rman_delete" Heure : 26/02/2013 12:10:46
Application OB2BAR sur "clientxxx.domain.com" déconnectée.
Application OB2BAR on"xxx" disconnected.
[Critique] De : [email protected] "Base10G_DBName_1_Archivelogs_rman_delete" Heure : 26/02/2013 12:10:46
Aucun Agent de disque ne s'est effectué correctement.
La session a échoué.
None of the Disk Agents completed successfully.
Session has failed.
[Normal] De : [email protected] "Base10G_DBName_1_Archivelogs_rman_delete" Heure : 26/02/2013 12:10:46
Statistiques de la sauvegarde :
Temps de file d'attente de la session (en heures) 0,00
Agents de disque terminés ........ 0
Agents de disque ayant échoué ........... 0
Agents de disque abandonnés .......... 0
Total des Agents de disque ........... 0
========================================
Agents de support terminés ....... 0
Agents de support ayant échoué .......... 0
Abandon des Agents de support ......... 0
Total des Agents de support .......... 0
===========================================
Total Méga-octets ................. 0 Mo
Total des supports utilisés ............. 0
Total d'erreurs d'Agent de disque ...... 0Hello,
No disconnection at all.
It doesn't work since a crash of the DP server during the DB backup.
When we move the catalog on the same server as the DB, the backup works but if we set the catalog to an other server (like the original setting) it doesn't work and we don't know why.
It seems that when a backup is launched thru Data Protector, RMAN can't find the DB catalog. But if we run (manually) the RMAN command that DP used to do a backup, it works... -
Can't Restore Exchange 2010 Mailbox DB from HP Data Protector backup
I'm trying to implement Exchange 2010, but I won't feel comfortable moving many users to it until I've successfully restored a mail database from tape backup. So far, this hasn't worked out so well. I'm using HP Data Protector for my backup solution.
Here's what I've done:
1. In DP's "Restore" GUI, navigated down to the MS Volume Shadow Copy Writers entry, then selected both "Files" and "Logs" from the DB's entry under Microsoft Information Store. I'm not restoring any of the other Writers. So that I don't have to take down Exchange, I'm restoring them to a temporary restore location.
2. After the restore completes, I go to the temporary restore location on the server and run eseutil /mh on the database, which returns a "Dirty Shutdown" db status.
3. Since I have the log files, I attempt to repair using eseutil /r E01 in the log files' path. This generates "Operation terminated with error -1216 (JET_errAttachedDatabaseMismatch, An outstanding database attachment has been detected at the start or end of recovery, but database is missing or does not match attachment info) after 10.608 seconds."
Can anyone suggest what I'm doing wrong with this recovery? If my steps are incorrect I'd love to know, as HP's documentation for restoring Exchange 2010 is very young and not terribly useful. My ultimate goal is to be able to restore a database from DP's tapes and bring it back online on the Exchange 2010 server.
Thanks!
Thanks!Hi Ben,
We backup our primary database (Ex Writer) and always with full backup (DB+LOGS). When we restore we restore to alternate location, then manualy copy db file and everything from restored log directory to one folder (for example: d:\restore_DB1). At this
stage DB is in dirty shutdown state. Then we run (in folder where we copied db file and log files)
Eseutil.exe /R E00 /D
it takes a couple of seconds (160GB file) and the db is in clean shutdown state. Then we do:
New-MailboxDatabase -Name “Restored DB” -Server MBOX1 -EDBFilePath “D:\Restore_DB1\DB1.edb”
-Logfolderpath “D:\Restore_DB1” -Recovery
and
Mount-Database “Restored DB”
now we can restore single mailbox or even single item from mailbox with:
1: whole mailbox with overite the destination
Restore-Mailbox –Identity “USERNAME” –RecoveryDatabase “Restored DB”
2. whole mailbox to alternate location (new folder in another mailbox)
Restore-Mailbox –Identity “EXISTING MAILBOX TO RESOTRE TO” –RecoveryDatabase “Restored DB” –RecoveryMailbox “MAILBOX DO BE RESTORED
FROM BACKUP” –TargetFolder “NEW FOLDER IN EXISTING MAILBOX”
3. the same as 2 but single item with MEETING in email subject
Restore-Mailbox –Identity “EXISTING MAILBOX TO RESOTRE TO” –RecoveryDatabase “Restored DB” –RecoveryMailbox “MAILBOX DO BE RESTORED
FROM BACKUP” -SubjectKeywords "MEETING" –TargetFolder “NEW FOLDER IN EXISTING MAILBOX”
Best Regards,
Alex -
Data Protector backup integration fails after upgrade to Oracle 11.2.0.2
After upgrading a system from Oracle 10.2.0.2 to 11.2.0.2, the Data Protector backup integration fails with error
[Normal] From: BSM@<dp_cell_server>.<domain> "<sap_host>_<SID>_Online" Time: 28.04.2011 09:10:21
Backup session 2011/04/28-74 started.
[Normal] From: BSM@<dp_cell_server>.<domain> "<sap_host>_<SID>_Online" Time: 28.04.2011 09:10:21
OB2BAR application on "<sap_host>.<domain>" successfully started.
/usr/sap/<SID>/SYS/exe/run/brbackup: error while loading shared libraries: libclntsh.so.10.1: cannot open shared object file: No such file or directory
[Major] From: OB2BAR_OMNISAP@pervs<SID>.<domain> "OMNISAP" Time: 04/28/11 09:10:21
BRBACKUP /usr/sap/<SID>/SYS/exe/run/brbackup -t online -d util_file_online -c -m all -u system/******** returned 127
/usr/sap/<SID>/SYS/exe/run/brarchive: error while loading shared libraries: libclntsh.so.10.1: cannot open shared object file: No such file or directory
[Major] From: OB2BAR_OMNISAP@pervs<SID>.<domain> "OMNISAP" Time: 04/28/11 09:10:21
BRARCHIVE /usr/sap/<SID>/SYS/exe/run/brarchive -d util_file -s -c -u system/******** returned 127
[Normal] From: BSM@<dp_cell_server>.<domain> "<sap_host>_<SID>_Online" Time: 28.04.2011 09:10:22
OB2BAR application on "<sap_host>.<domain>" disconnected.
[Critical] From: BSM@<dp_cell_server>.<domain> "<sap_host>_<SID>_Online" Time: 28.04.2011 09:10:22
None of the Disk Agents completed successfully.
Session has failed.
We checked the configuration, tried linking /oracle/client/11x_64 to 10x_64, removing the link and renewing the 10x_64 oracle client, but still Data Protector can't find the library libclntsh.so.10.1. A new system which was installed with Oracle 11.2.0.2 doesn't have any problems with online backups.
Any help is appreciated!Hi,
did you create the other link according to the upgrade guide (point 5.5) ?
You need to create this link so that BR*Tools
(which is linked to the Oracle 10.2 client)
can use the newer Oracle 11.2 clients.
After the software installation has finished,
create a symbolic link in $ORACLE_HOME/lib as follows:
cd $ORACLE_HOME/lib
ln u2013s libnnz11.so libnnz10.so
or (HP-UX)
ln u2013s libnnz11.sl libnnz10.sl
Volker
Second part: For the DP job, there can be set different environment settings inside the DP job.
Did you check if there are still relicts from the previous release ?
You could integrate a small pre-exec script into the job and let it plot the output of
id
env
set
to a logfile, just to see which values the backup is using.
Edited by: Volker Borowski on Apr 29, 2011 10:12 AM -
Data protector online backup not running after system copy
Dear guru's,
My online backup is not running.The integration of oracle user sapsr3 with data protector 6.0 failed.the error message that came out is;
Oracle Output: ORA-01031: insufficient privileges
SP2-0640: Not connected
sqlcode 1031
Please advise.
Thankscan you have a look Note 834917 - Oracle Database 10g: New database role SAPCONN
Note 400241 - Problems with ops$ or sapr3 connect to Oracle
cheers,
-Sunil -
Backup Schedule missed in Data protector [HPDP]
Hello,
When checked backup status for some groups, the schedule was not started.
So the backup was not running for a long time. I have refreshed the backup specification eventhough the issue persist.
How to fix this issue ?
Note:the schedules are not disabled too.
Thanks for your support in Advance.Hi Lars,
I am using the Data Protector TRANS Option.
See the the cutoff of a Logfile from yesterday.
Data Protector finds the Stage files and wirtes them over a pipe to the LTO Tape Drive.
Greets
Peter
Determining stage files in directory 'E:\sapdb_logsicherung'.
Found directory entry '.'. It is not a stage file.
Found directory entry '..'. It is not a stage file.
Found directory entry 'R3P_LOG.265'. It could be a stage file.
Found directory entry 'R3P_LOG.266'. It could be a stage file.
Found directory entry 'R3P_LOG.267'. It could be a stage file.
Found directory entry 'R3P_LOG.268'. It could be a stage file.
Stage file E:\sapdb_logsicherung\R3P_LOG.265 has label LOG_000000265 and the backup started at 2008-12-01 08:41:16.
Stage file E:\sapdb_logsicherung\R3P_LOG.266 has label LOG_000000266 and the backup started at 2008-12-02 21:15:07.
Stage file E:\sapdb_logsicherung\R3P_LOG.267 has label LOG_000000267 and the backup started at 2008-12-05 10:25:54.
Stage file E:\sapdb_logsicherung\R3P_LOG.268 has label LOG_000000268 and the backup started at 2008-12-09 13:10:46.
Found 4 stage files.
2008-12-10 23:05:20
Filling reply buffer.
Constructed the following reply:
OK
Processed Stage Files 4
Bytes processed 8389394432
Deleted Stage Files 0
Remaining Stage Files 4
Reply buffer filled.
DBA Action ends:
Timestamp: 20081210230520 State: Success -
Unable to take online backup including logs with HP Data Protector - DB2 9.7 fixpack 8
Dear All,
Infrastructure : -
Database - IBM DB2 LUW 9.7 fixpack 8
OS - HP-UX 11.31
Backup solution - Data protector v7
OEM of tape library i.e. HP asked me to make changes in DB parameters with values as
--> LOGRETAIN to RECOVERY
--> USEREXIT to ON
--> LOGARCHMETH1 to USEREXIT
These parameters are used for activating online backup of Database (DB2 LUW 9.7 fixpack 8).
when backup is initiated from DP, backup happen successfully with option of excluding archive logs where as when we execute backup from DP(Data protector) with option including archive logs. Backup terminates with error.
SQL2428N The BACKUP did not complete because one or more of the requested log files could not be retrieved
Dear all need your expect help.
Thanks in advance.
NeerajHi Deepak,
Thanks for your quicky reply and i have check the directory log_dir and log_archive are having enough space available.
Please find the db2diag.log file.
Database Configuration for Database
Database configuration release level = 0x0d00
Database release level = 0x0d00
Database territory = en_US
Database code page = 1208
Database code set = UTF-8
Database country/region code = 1
Database collating sequence = IDENTITY_16BIT
Alternate collating sequence (ALT_COLLATE) =
Number compatibility = OFF
Varchar2 compatibility = OFF
Date compatibility = OFF
Database page size = 16384
Dynamic SQL Query management (DYN_QUERY_MGMT) = DISABLE
Statement concentrator (STMT_CONC) = OFF
Discovery support for this database (DISCOVER_DB) = ENABLE
Restrict access = NO
Default query optimization class (DFT_QUERYOPT) = 5
Degree of parallelism (DFT_DEGREE) = 1
Continue upon arithmetic exceptions (DFT_SQLMATHWARN) = NO
Default refresh age (DFT_REFRESH_AGE) = 0
Default maintained table types for opt (DFT_MTTB_TYPES) = SYSTEM
Number of frequent values retained (NUM_FREQVALUES) = 10
Number of quantiles retained (NUM_QUANTILES) = 20
Decimal floating point rounding mode (DECFLT_ROUNDING) = ROUND_HALF_EVEN
Backup pending = NO
All committed transactions have been written to disk = NO
Rollforward pending = NO
Restore pending = NO
Multi-page file allocation enabled = YES
Log retain for recovery status = RECOVERY
User exit for logging status = YES
Self tuning memory (SELF_TUNING_MEM) = ON
Size of database shared memory (4KB) (DATABASE_MEMORY) = AUTOMATIC(3455670)
Database memory threshold (DB_MEM_THRESH) = 10
Max storage for lock list (4KB) (LOCKLIST) = AUTOMATIC(20000)
Percent. of lock lists per application (MAXLOCKS) = AUTOMATIC(90)
Package cache size (4KB) (PCKCACHESZ) = AUTOMATIC(161633)
Sort heap thres for shared sorts (4KB) (SHEAPTHRES_SHR) = AUTOMATIC(480362)
Sort list heap (4KB) (SORTHEAP) = AUTOMATIC(50000)
Database heap (4KB) (DBHEAP) = AUTOMATIC(3102)
Catalog cache size (4KB) (CATALOGCACHE_SZ) = 2560
Log buffer size (4KB) (LOGBUFSZ) = 1024
Utilities heap size (4KB) (UTIL_HEAP_SZ) = 10000
Buffer pool size (pages) (BUFFPAGE) = 10000
SQL statement heap (4KB) (STMTHEAP) = AUTOMATIC(8192)
Default application heap (4KB) (APPLHEAPSZ) = AUTOMATIC(256)
Application Memory Size (4KB) (APPL_MEMORY) = AUTOMATIC(40000)
Statistics heap size (4KB) (STAT_HEAP_SZ) = AUTOMATIC(4384)
Interval for checking deadlock (ms) (DLCHKTIME) = 10000
Lock timeout (sec) (LOCKTIMEOUT) = 3600
Changed pages threshold (CHNGPGS_THRESH) = 20
Number of asynchronous page cleaners (NUM_IOCLEANERS) = AUTOMATIC(2)
Number of I/O servers (NUM_IOSERVERS) = AUTOMATIC(5)
Index sort flag (INDEXSORT) = YES
Sequential detect flag (SEQDETECT) = YES
Default prefetch size (pages) (DFT_PREFETCH_SZ) = AUTOMATIC
Track modified pages (TRACKMOD) = YES
Default number of containers = 1
Default tablespace extentsize (pages) (DFT_EXTENT_SZ) = 2
Max number of active applications (MAXAPPLS) = AUTOMATIC(125)
Average number of active applications (AVG_APPLS) = AUTOMATIC(3)
Max DB files open per application (MAXFILOP) = 61440
Log file size (4KB) (LOGFILSIZ) = 16380
Number of primary log files (LOGPRIMARY) = 60
Number of secondary log files (LOGSECOND) = 0
Changed path to log files (NEWLOGPATH) =
Path to log files = /db2/ECP/log_dir/NODE 0000/
Overflow log path (OVERFLOWLOGPATH) =
Mirror log path (MIRRORLOGPATH) =
First active log file = S0000187.LOG
Block log on disk full (BLK_LOG_DSK_FUL) = YES
Block non logged operations (BLOCKNONLOGGED) = NO
Percent max primary log space by transaction (MAX_LOG) = 0
Num. of active log files for 1 active UOW(NUM_LOG_SPAN) = 0
Group commit count (MINCOMMIT) = 1
Percent log file reclaimed before soft chckpt (SOFTMAX) = 300
Log retain for recovery enabled (LOGRETAIN) = RECOVERY
User exit for logging enabled (USEREXIT) = ON
HADR database role = STANDARD
HADR local host name (HADR_LOCAL_HOST) =
HADR local service name (HADR_LOCAL_SVC) =
HADR remote host name (HADR_REMOTE_HOST) =
HADR remote service name (HADR_REMOTE_SVC) =
HADR instance name of remote server (HADR_REMOTE_INST) =
HADR timeout value (HADR_TIMEOUT) = 120
HADR log write synchronization mode (HADR_SYNCMODE) = NEARSYNC
HADR peer window duration (seconds) (HADR_PEER_WINDOW) = 0
First log archive method (LOGARCHMETH1) = USEREXIT
Options for logarchmeth1 (LOGARCHOPT1) =
Second log archive method (LOGARCHMETH2) = OFF
Options for logarchmeth2 (LOGARCHOPT2) =
Failover log archive path (FAILARCHPATH) =
Number of log archive retries on error (NUMARCHRETRY) = 5
Log archive retry Delay (secs) (ARCHRETRYDELAY) = 20
Vendor options (VENDOROPT) =
Auto restart enabled (AUTORESTART) = ON
Index re-creation time and redo index build (INDEXREC) = SYSTEM (RESTART)
Log pages during index build (LOGINDEXBUILD) = OFF
Default number of loadrec sessions (DFT_LOADREC_SES) = 1
Number of database backups to retain (NUM_DB_BACKUPS) = 12
Recovery history retention (days) (REC_HIS_RETENTN) = 60
Auto deletion of recovery objects (AUTO_DEL_REC_OBJ) = OFF
TSM management class (TSM_MGMTCLASS) =
TSM node name (TSM_NODENAME) =
TSM owner (TSM_OWNER) =
TSM password (TSM_PASSWORD) =
Automatic maintenance (AUTO_MAINT) = ON
Automatic database backup (AUTO_DB_BACKUP) = OFF
Automatic table maintenance (AUTO_TBL_MAINT) = ON
Automatic runstats (AUTO_RUNSTATS) = ON
Automatic statement statistics (AUTO_STMT_STATS) = ON
Automatic statistics profiling (AUTO_STATS_PROF) = ON
Automatic profile updates (AUTO_PROF_UPD) = ON
Automatic reorganization (AUTO_REORG) = ON
Auto-Revalidation (AUTO_REVAL) = DEFERRED
Currently Committed (CUR_COMMIT) = DISABLED
CHAR output with DECIMAL input (DEC_TO_CHAR_FMT) = NEW
Enable XML Character operations (ENABLE_XMLCHAR) = YES
WLM Collection Interval (minutes) (WLM_COLLECT_INT) = 0
Monitor Collect Settings
Request metrics (MON_REQ_METRICS) = BASE
Activity metrics (MON_ACT_METRICS) = BASE
Object metrics (MON_OBJ_METRICS) = BASE
Unit of work events (MON_UOW_DATA) = NONE
Lock timeout events (MON_LOCKTIMEOUT) = WITHOUT_HIST
Deadlock events (MON_DEADLOCK) = WITHOUT_HIST
Lock wait events (MON_LOCKWAIT) = NONE
Lock wait event threshold (MON_LW_THRESH) = 5000000
Number of package list entries (MON_PKGLIST_SZ) = 32
Lock event notification level (MON_LCK_MSG_LVL) = 1
SMTP Server (SMTP_SERVER) =
SQL conditional compilation flags (SQL_CCFLAGS) =
Section actuals setting (SECTION_ACTUALS) = NONE
Connect procedure (CONNECT_PROC) =
Regards
Neeraj -
HP Data Protector to backup Unity
Does anyone have any experience using HP Data Protector to backup the exchange and sqlserver data to a central backup server. Are these done with the databases/application running or is it best to shutdown and backup
ThanksI have been trying to do the same thing for a few days now. It seems there is no documentation anywhere that explains how to restore to a new machine. In my case I want to take my production DB and move it in its entirety to a test DB. The Oracle DB versions are exactly the same yet I cannot find out how to get this done.
Were you able to finally get this accomplished? I also use data protector 6 to take my RMAN backups. Any help would be appreciated.
Even if I had to take a new backup to disk instead of to tape that would be fine. I just cant seem to find the steps for restoring an RMAN backup to a new machine.
TIA
Scott -
We recently migrated from Tivoli to HP Data Protector. All the RMAN scripts are stored in DP.
Currently we don't have any control to stop or start the backup. Every time we need to talk to storage team to get the things done (during maintenance activity)
Is this the way it is operated where DP is used ?
Is there any other way we can control the rman backup script execution ? Is there any drawback if we run it directly from the shell/cron ?
I was told that DP maintains its own recovery policy, due to which it has to be run from the DP.Not an Oracle error so you need to take this up with your other vendors.
Vendor specific error: OB2_WriteObjData() failed! ERR(-2) <----------------
ORA-19502: write error on file "srmdtscl_sbldb_ora_full<sbldb_4593:765762443:1>.dbf", blockno 885712641 (blocksize=1024)
ORA-27030: skgfwrt: sbtwrite2 returned error
ORA-19511: Error received from media manager layer, error text: <---------------- -
Backup MaxDB 7.7.06.09 to Veritas Netbackup 6.5 fails
We want to backup MaxDB to Veritas Netbackup server.
According documentation found about this topic the backup is configured
by creating 3 files: bsi.env, initWDO.par (for backint for MaxDB) and
initWDO.utl (for backint for Oracle). The contents of these files are shown below.
When running the backup, it seems that backint for MaxDB ends with return code 2,
the error message received is:
-24920,ERR_BACKUPOP: backup operation was unsuccessful
The backup tool failed with 2 as sum of exit codes.
Unfortunately no further errors/warnings are shown that points in any direction
what's going wrong here.
We start the backup via the following dbmcli-command:
dbmcli -u control,****** -d WDO -uUTL control,****** backup_start BACKData_WDO
(for the time being without xuser entries, first make sure the backup is ok)
The files dbm.ebl, dbm.prt and several others do not show any additional details/hints.
It seems as if the "save data quick" to the named pipe is ok, the sql-code returns "0".
After this the backint for MaxDB should read the named pipe and write it to stage-files,
but backint (for MaxDB) ends with return code 2.
Any idea what might go wrong here?
With kind regards,
R. Hoogeveen
The Netherlands
File bsi.env:
=========
BACKINT /sapdb/WDO/db/bin/backint
INPUT /tmp/backint4maxdb_WDO.in
OUTPUT /tmp/backint4maxdb_WDO.out
ERROROUTPUT /tmp/backint4maxdb_WDO.err
PARAMETERFILE /sapdb/data/wrk/WDO/initWDO.par
TIMEOUT_SUCCESS 600
TIMEOUT_FAILURE 300
ORIGINAL_RUNDIRECTORY /sapdb/data/wrk/WDO
File initWDO.par:
=============
STAGING AREA: /tmp/stageWDO 1 GB
FILES PER BACKINT CALL: 1
BACKINT: /usr/openv/netbackup/bin/backint
PARAMETERFILE OF BACKINT: /sapdb/data/wrk/WDO/initWDO.utl
HISTORY FILE: /sapdb/data/wrk/WDO/backint_history_WDO.log
INPUTFILE FOR BACKINT: /tmp/backint4ora_WDO.in
OUTPUTFILE FOR BACKINT: /tmp/backint4ora_WDO.out
ERRORFILE FOR BACKINT: /tmp/backint4ora_WDO.err
MAXIMAL DELAY OF BACKINT CALL: 30
File initWDO.utl:
=============
switch_list /tmp/.switch_WDO.lis
switch_sem /tmp/.switch_WDO.sem
switch_log /tmp/.switch_WDO.log
drives 1
client wdocsz01
server backfire
policy sap_WDOLars,
The /tmp/backint4maxdb.err file tells me:
Backint for Oracle was unsuccessful.
(Unfortunately that was all information in this file.)
The backint4ora.in file tells me:
/tmp/stageWDO.0
(looks ok to me, also at the time backint4ora was started the stage file was created with non-zero size)
The backint4ora.out file tells me:
ERROR: incorrect format or option in .utl file (-p)
(this seems as if the -p option is not recognized by the backint4ora executable)
When I run this executable manually as user sdb it shows me the commandline that I should use, including the -p option.
One strange thing I notice is that the order of the options is different from the commandline that is executed.
(in the usage it shows -p as almost last parameter, the command executed has -p in the middle; I will see if I can execute the backint4ora command manually, since I have the stage file available, I have copied it during the process)
The backint4ora.err file is empty.
The commandline of the dbmcli command I execute shows me another interesting error message,
this might also be the source of all problems here.
-24920,ERR_BACKUPOP: backup operation was unsuccessful
Could not get external backup ID's from the backup tool.
I tried to retrieve the external backup id's manually for medium BACKDataWDO, it show me OK without any external backup id's.
I am not sure, but I think this is correct since no successfull backup was created yet with external backup tool.
Can it also be that the parameter "history file" from the initWDO.par file is set wrong?
Currently it is set to "/sapdb/data/wrk/WDO/backint_history_WDO.log" (see above also), but I can imagine
that this should be set to the dbm.knl or dbm.ebf file ??
With kind regards,
Roger Hoogeveen -
Data Protector 6.11 File Names Purge - Recovery.
Hi All;
On reviewing our Data Protector today I am finding a lot of session, restore, and media files missing.
I have found out that someone ran a cmd for DP:-
Omnidbutil -purge -filenames
Could this be a reason I am seeing missing information as above?
The data and catalogue protection is 2 weeks, I cannot see any trace of the sessions/backup files, I am looking for. ON attempting to restore from the target, the expected drives aren't even listed and 75% of the resultant backup media is listing with blue question mark in 'devices and media I.e not found.
Can anyone help/work with me on this please?
What affect does this have on the IDB/CDB/DCBF?
Thanks in advance for any assistance guys and gals.The main reason for reformatting the cache, was the merger of the cache implementations in Java Web Start and Java Plug-in. There is now one cache, and one implementation of downloading and caching code for the two products.
The format and implementation is more similar to what was the previous plugin format, as that was faster and contained more features (cache size limit, ability to run w/o caching all together, and respecting more cache control and http header directives than the webstart implementation.)
The requirement for an undeterminable filename was from the security group. A bug in older versions of IE allowed you to execute a file on the local filesystem that you knew of. ( a jar file is a form of an executable. )
We feel that the cache is only that, a private cache for the java products.
By making this change we recognize that code such as this that assumes it knows the cache's format and contents can no longer work unmodified, and that this will prevent code from being developed that does this in the future.
There are several reasons why code has done this (including some in the JDIC project), but we think there are better mechanisms for achieving the objectives of such code, and are ready to help with what we understand may be a difficult transition for some.
/Andy -
HP Data Protector Express 4.00-SP1 - Restore Selection Problem
I have archived some data out of a directory that contains rather a lot of files and now when I tried to create a restore job to recover some of the data whenever I am building the job when I have to select the file I want to recover and I navigate down the file structure to the directory that contains the files while it tries to build the list of files Data Protector just closes with no warning. Does anyone know:- why this is happening- how I can work around it to restore the data I need Also is there a way to recover the contents of a whole tape without having to go through some selection process. Thanks Andrew
Hi,
Data protector uses it's own agent.
Backup is working ok. Only restore causes the server to abend. It resets
without filling the abend log.
Hereby the config.
regards,
Marcel
"Marcel Cox" <[email protected]> wrote in message
news:[email protected]..
>
> How does data protector work? Does it have its own agent on the NetWare
> server or does it communicate with the server through Novell protocols?
> Also, a spontanous reboot could indicate a driver problem. Maybe you
> could post your server config so that we can see if there is no serious
> problem with it.
> For this, could you download the latest config.nlm from
> 'NOVELL: Downloads - CONFIG.NLM for NetWare'
> (http://download.novell.com/Download?...d=C6he4eKewtU~) , install it
> to
> the sys:system directory of your server and then from the server
> console,
> execute the following command:
> load config /sma1bjue
>
> Review the resulting config.txt file to remove any passwords and other
> security relevant information and then post it here. To avoid your
> post
> from being rejected, you might have to ZIP the resulting file to
> reduce
> its size and also add the string "[file]" to the message subject so
> that
> you disable the binary file filter of the news server.
>
>
> --
> Marcel Cox
> ------------------------------------------------------------------------
> Marcel_Cox's Profile: http://forums.novell.com/member.php?userid=8
> View this thread: http://forums.novell.com/showthread.php?t=355021
>
Maybe you are looking for
-
File generated in AL11 directory
Hi Experts, I have created a logical file path and assigned it to physical path in FILE transaction. I have also created logical file name and mapped it to Physical File name. The physical file name is "stock<YYYY><MM><DD>.csv" . But when I execute A
-
Credit Block For Failed Authorization
Hi All, During sales order processing, the payment card authorization fails, the automatic credit check is set to block. To be able to re-authorize a sales order with a failed Payment Card authorization, the user can use transaction VCC1. But it can
-
I am trying to email generated report using infoview web UI. I am logged in as administrator. The destination plugin required for this action is disabled. If you require this functionality, please contact your system administrator.
-
I have NUMEROUS pdf files that are Transcripts. The company sent them to me with 0000.lastname.firstname.dob.pdf The 0000 is for non-graduates and there are Transcripts from 1926-1976. Basically, what I would like to do is delete the first five ch
-
How can I straighten a movie clip?
I have some great footage from an interview, unfortunately the windowsill behind the subject is skewed. Is there a way to straighten it in Imovie or another inexpensive application?