Redirected restore performance
Iu2019ve been looking at our redirected restores, trying to determine how to speed up the process.
Iu2019ve read an SAP document suggesting using a standard Logical System Name across production, qa, and dev (for example r3clnt100 as the name for production qa and dev) by not specifying the sid in the logical system name you eliminate the need to run bdls after a redirected restore. The bdls run (in our case runs, we have xi, bw and apo attached to our r3 system) constitute a significant amount of the time, so eliminating them would have a dramatic affect. Does anyone have experience with using a standard logical system name across prod, qa, and dev rather than having the sid in the logical system name? What are the pros and cons of that approach?
I was using google to find options for bdls and found this link
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6931413f-0b01-0010-c190-c21bc6711fb0
The document title is SAP System Landscape Copy for SAP NetWeaver and mySAP Solutions -- Best Practice for Solution Management
Similar Messages
-
DB2 v9.1fp4 on suse linux 10sp2 - redirect restor PRD to DEV
Hi All,
First of all thank you, for valuable TIME.
issue:
My development server got crashed due to failure of dedicated SAN. in simple lost every thing. since, even DB2 backups happening to SAN.
requirement:
As we lost all the developments and configuration of development server, we need build a DEV from PRD.
Steps taken:
a. we have installed Suse 10sp2 followed by db2 v9.1 fp4 and SAP ERP6.0 sr2.
b. taken backup of db2 & sap kernel backup by tar command followed by SAP db13 backup along with logs - for newly installed Development server.
hostname - development
SID - DEV
c. I need to restore development server with sid DEV from the backup of production with sid PRD.
To get all the data {development data, transaction data & configuration etc..}
Problem
Till now i haven't worked on DB2 restore, and the current requirement is to dump data from PRD in to DEV.
i.e.. db2 redirect restore
current landscape status:
Both production and development {freshly installed} are up and working fine.
PRD with all the live data, DEV freshly installed and without data.
Need to restore data from PRD to DEV.
Database: DB2 v9.1 fp4
OS: SUSE linux 10 sp2
SAP solution: ERP 6.0 sr2
Backup of PRD: in to SAN box {backup folder}, backup triggered by DB13 with include logs option.
I request you to guide me in understanding and performing the restoration.
i.e.. the steps to be performed along with the necessary precautions to be take to avoid problems.
PRD data to DEV.
Thank you very much your time.
by
Harikatrans.log
4 ETW000 R3trans version 6.14 (release 700 - 23.07.10 - 09:23:00).
4 ETW000 unicode enabled version
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time : 12.05.2011 - 22:15:52
4 ETW000 control file: <no ctrlfile>
4 ETW000 R3trans was called as follows: R3trans -d
4 ETW000 trace at level 2 opened for a given file pointer
4 ETW000 [dev trc ,00000] Thu May 12 22:15:52 2011 84 0.000084
4 ETW000 [dev trc ,00000] db_con_init called 25 0.000109
4 ETW000 [dev trc ,00000] create_con (con_name=R/3) 29 0.000138
4 ETW000 [dev trc ,00000] Loading DB library '/usr/sap/DEV/SYS/exe/run/dbdb6slib.so' ... 39 0.000177
4 ETW000 [dev trc ,00000] DlLoadLib() success: dlopen("/usr/sap/DEV/SYS/exe/run/dbdb6slib.so"), hdl 0
4 ETW000 491 0.000668
4 ETW000 [dev trc ,00000] Library '/usr/sap/DEV/SYS/exe/run/dbdb6slib.so' loaded 22 0.000690
4 ETW000 [dev trc ,00000] function DbSlExpFuns loaded from library /usr/sap/DEV/SYS/exe/run/dbdb6slib.so
4 ETW000 32 0.000722
4 ETW000 [dev trc ,00000] Version of '/usr/sap/DEV/SYS/exe/run/dbdb6slib.so' is "700.08", patchlevel (0.297)
4 ETW000 120 0.000842
4 ETW000 [dev trc ,00000] function dsql_db_init loaded from library /usr/sap/DEV/SYS/exe/run/dbdb6slib.so
4 ETW000 24 0.000866
4 ETW000 [dev trc ,00000] function dbdd_exp_funs loaded from library /usr/sap/DEV/SYS/exe/run/dbdb6slib.so
4 ETW000 31 0.000897
4 ETW000 [dev trc ,00000] New connection 0 created 21 0.000918
4 ETW000 [dev trc ,00000] 000: name = R/3, con_id = -000000001, state = DISCONNECTED, tx = NO , hc = NO , perm = YES,
4 ETW000 reco = NO , frco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
4 ETW000 43 0.000961
4 ETW000 [dev trc ,00000] db_con_connect (con_name=R/3) 24 0.000985
4 ETW000 [dev trc ,00000] find_con_by_name found the following connection for reuse: 17 0.001002
4 ETW000 [dev trc ,00000] 000: name = R/3, con_id = 000000000, state = DISCONNECTED, tx = NO , hc = NO , perm = YES,
4 ETW000 reco = NO , frco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
4 ETW000 39 0.001041
4 ETW000 [dev trc ,00000] RLIMIT_STACK: current=8388608, max=-1 315 0.001356
4 ETW000 [dev trc ,00000] DB6 (DB2 UDB) UNICODE database interface 700.08 [opt] 21 0.001377
4 ETW000 [dev trc ,00000] DB6 shared library (dbdb6slib) patchlevels 23 0.001400
4 ETW000 [dev trc ,00000] (0.8) DB6: V8.2.2 optguidelines in OPEN SQL (note 150037) 22 0.001422
4 ETW000 [dev trc ,00000] (0.8) Support of SDBUPDEXCL (note 847616) 21 0.001443
4 ETW000 [dev trc ,00000] (0.9) DB6: use export file for dbdb6slib (note 835135) 19 0.001462
4 ETW000 [dev trc ,00000] (0.9) DB6: Core in getAndBindSQLDA (note 833183) 17 0.001479
4 ETW000 [dev trc ,00000] (0.10) DB6: link dbdb6slib.dll on windows with libdb6.obj (note 761159)
4 ETW000 42 0.001521
4 ETW000 [dev trc ,00000] (0.10) DB6: DUPLICATE_KEY on MERGE -> repeat (note 851474) 18 0.001539
4 ETW000 [dev trc ,00000] (0.15) DB6: wrong CAST for short string ABAP type (note 861905) 21 0.001560
4 ETW000 [dev trc ,00000] (0.17) DB6: special characters in sidadm passwd (note 865839) 18 0.001578
4 ETW000 [dev trc ,00000] (0.21) DB6: no SAP_INFO comments (note 873889) 19 0.001597
4 ETW000 [dev trc ,00000] (0.22) DB6: hints: get correlation names from view texts (note 868888)
4 ETW000 32 0.001629
4 ETW000 [dev trc ,00000] (0.23) DB6: hints: get correlation names from view texts (note 868888)
4 ETW000 24 0.001653
4 ETW000 [dev trc ,00000] (0.26) DB6: DB6_DBSL_CLP_COMMAND STRING_BAD_REF (note 883402) 17 0.001670
4 ETW000 [dev trc ,00000] (0.27) DB6: activate value compression (note 886231) 20 0.001690
4 ETW000 [dev trc ,00000] (0.28) DB6: optimization guidelines on views part 2 (note 868888) 18 0.001708
4 ETW000 [dev trc ,00000] (0.30) DB6: no SQL trace for SQLCancel (note 892111) 17 0.001725
4 ETW000 [dev trc ,00000] (0.33) DB6: append SAP_TA comment (note 873889) 19 0.001744
4 ETW000 [dev trc ,00000] (0.34) DB6: activate value compression with quoted names (note 886231)
4 ETW000 28 0.001772
4 ETW000 [dev trc ,00000] (0.36) DB6: Repeat isolated DDL statements after SQL0911 (note 901338)
4 ETW000 30 0.001802
4 ETW000 [dev trc ,00000] (0.41) DB6: add V9 to list of supported DB2 releases (note 912386)
4 ETW000 28 0.001830
4 ETW000 [dev trc ,00000] (0.50) DB6: reread passwords for secondary connections (note 931742)
4 ETW000 27 0.001857
4 ETW000 [dev trc ,00000] (0.52) DB6: double quote table names in optguidelines (note 868888)
4 ETW000 24 0.001881
4 ETW000 [dev trc ,00000] (0.54) DB6: error handling in DBSL CLP (note 940260) 19 0.001900
4 ETW000 [dev trc ,00000] (0.69) DB6: technical support of DB2 CLI driver (note 962892) 22 0.001922
4 ETW000 [dev trc ,00000] (0.73) DB6: log table name on TRUNCATE failure (note 970743) 21 0.001943
4 ETW000 [dev trc ,00000] (0.79) DB6: column type XML in index size calculation (note 982993)
4 ETW000 32 0.001975
4 ETW000 [dev trc ,00000] (0.82) DB6: CAST for SSTRING data types (note 989568) 19 0.001994
4 ETW000 [dev trc ,00000] (0.86) DB6: long runtimes for R3szchk (note 1000847) 18 0.002012
4 ETW000 [dev trc ,00000] (0.88) DB6: patch collection Dec 06 (note 1005574) 19 0.002031
4 ETW000 [dev trc ,00000] (0.96) DB6: patch collection Jan 07 (note 1017852) 19 0.002050
4 ETW000 [dev trc ,00000] (0.97) DB6: CLP commands with DB2 CLI Driver (note 1024102) 18 0.002068
4 ETW000 [dev trc ,00000] (0.99) DB6: SUBSTITUTE VALUES with FAE statements (note 1028779) 19 0.002087
4 ETW000 [dev trc ,00000] (0.107) DB6: patch collection Apr 07 (note 1047194) 20 0.002107
4 ETW000 [dev trc ,00000] (0.110) DB6: SAP user names ending with non-ASCII char (note 1054555)
4 ETW000 49 0.002156
4 ETW000 [dev trc ,00000] (0.113) DB6: work process type in application snapshot (note 1059905)
4 ETW000 25 0.002181
4 ETW000 [dev trc ,00000] (0.114) DB6: connect using SAPDBHOST and DB2DB6_SVCENAME (note 1062049)
4 ETW000 24 0.002205
4 ETW000 [dev trc ,00000] (0.117) DB6: patch for execution of long DDL statements (note 1069658)
4 ETW000 27 0.002232
4 ETW000 [dev trc ,00000] (0.122) DB6: SNAPSHOT_TBS_CFG table function is deprecated (note 1077963)
4 ETW000 27 0.002259
4 ETW000 [dev trc ,00000] (0.123) DB6: CLP commands on Windows with V9.1 (note 1080149) 16 0.002275
4 ETW000 [dev trc ,00000] (0.124) DB6: Set DB2CODEPAGE=819 for non-Unicode (note 1084400) 18 0.002293
4 ETW000 [dev trc ,00000] (0.126) DB6: reuse optguidelines on FAE statements (note 1087375) 19 0.002312
4 ETW000 [dev trc ,00000] (0.126) DB6: Enforce DB2CODEPAGE=819 for non-Unicode environments (note 1084400)
4 ETW000 30 0.002342
4 ETW000 [dev trc ,00000] (0.128) DB6: db6_free on invalid memory area (note 1092030) 17 0.002359
4 ETW000 [dev trc ,00000] (0.133) DB6: statement cache enhancements (note 1101031) 20 0.002379
4 ETW000 [dev trc ,00000] (0.136) DB6: change for enhancement pack installer (note 1111536) 22 0.002401
4 ETW000 [dev trc ,00000] (0.138) DB6: improoved table size estimate for DB8 V8 (note 1119934)
4 ETW000 28 0.002429
4 ETW000 [dev trc ,00000] (0.144) I5/OS ldappasswd support for 5250 terminal. (note 1129573)
4 ETW000 27 0.002456
4 ETW000 [dev trc ,00000] (0.144) MSSQL: ODBC fastload on separate connection (note 1131805)
4 ETW000 24 0.002480
4 ETW000 [dev trc ,00000] (0.148) DB6: allocate new CLI env handle if PID changes (note 1141570)
4 ETW000 26 0.002506
4 ETW000 [dev trc ,00000] (0.150) DB6: USE AND KEEP EXCLUSIVE LOCKS clause lost (note 1145580)
4 ETW000 31 0.002537 -
After Redirected Restore with different schema problems with db13
Hello, we made a redirected restore. We have different schema between production and quality system.
According to note 713524 we made the following changes:
create db connect user from the source system in the target system (unix user, sap<sid>)
set parameter dbs/db6/schema=sap<sid> in the instance profile
set dbs_db6_schema = sap<sid> in the environment for <sid>adm and db2<sid> (dbenv...)
add user sap<sid> into /sapmnt/<SID>/global/dscdb6.conf and set password with dscdb6up sap<sid> <password>
The system is now up and running. But transaction db13 is not working
SQL0443N Routine "*SHOT_DBM" (specific name "")
has returned an error SQLSTATE with diagnostic
text "SQL1092 Reason code or token: SAPR3
". SQLSTATE=38553
Regards,
AlexanderHi Alexander
sorry , forget the grants , they should come from the source system .
If you have multiple App-Servers , did you perform the above mentioned action in all affected profiles and environments of your Q-System ?
Please check , if you can limit this issue to an separate App-Server or to all App-Servers .
Best regards
dirk -
Hey guys, im new at this.. help: "REDIRECTED RESTORE FOR DB2"
hey guys im new at this basis thing, i just need help and some tips about the redirected restore for DB2 in windows. may some of you guys can provide me guides on how to perform the restoration from tape drives and other devices. thanks! all the help would be greatly appreciated.
Hi Robert,
you can find various guides and papers here
[SAP on DB2 for Linux, UNIX, and Windows|http://www.sdn.sap.com/irj/sdn/db6]
and here
[IBM SAP DB2 Experts|http://www.ibm.com/developerworks/wikis/display/im/IBMSAPDB2+Experts] -
Redirected restore - automatic storage - using DB2 api not br tools
I've done 100+ redirected restores for non-automatic storage databases using TSM only using the DB2 api's - and not the BR tools .
Now, I'm challenged with a redirect automatic storage DB.
*SQL1277N Restore has detected that one or more table space containers are*
inaccessible, or has set their state to 'storage must be defined'.
DB20000I The RESTORE DATABASE command completed successfully.
The backup image gets read and the TAG's for the containers are build. I can see that by doing a "df" on the filesystem level. But as soon as the restores attempts to write data into the containers, I get the above error message.
Here are my steps:
1. offline backup using db2 api on source
2. create restore script
RESTORE DB DCC use adsm open 4 sessions TAKEN AT 20080722155529 on /db2/SCC/sapdata1,/db2/SCC/sapdata2,/db2/SCC/sapdata3,/db2/SCC/sapdata4 ,/db2/SCC/sapdata5,/db2/SCC/sapdata6,/db2/SCC/saptemp1 dbpath on /db2/SCC INTO SCC NEWLOGPATH /db2/SCC/log_dir with 16 buffers REPLACE EXISTING redirect parallelism 2 without rolling forward without prompting
3. drop the target db and clean out all sapdata's and saptemp
4. create db on target:db2 create database scc automatic storage yes on /db2/SCC/sapdata1,/db2/SCC/sapdata2,/db2/SCC/sa**
+pdata3,/db2/SCC/sapdata4,/db2/SCC/sapdata5,/db2/SCC/saptemp1 dbpath on /db2/SCC+
5. update target db cfg with tsm parms so that it will be able to read the TSM tapes. ie tsm_mgmtclass, tsm_nodename, tsm_owner, tsm_password
6. setup my dsm.opt with
+SErvername redirect_restore+
and the dsm.sys with a new stanza
SErvername redirectrestore_
SchedMode PROMPT
nodename useagan1743ddb2_
PasswordAccess prompt
COMMMethod TCPip
TCPPort 1500
TCPServeraddress unixtsm1p.ecolab.com
7. as root I run the /db2/db2<sid>/sqllib/adsm/dsmapipw password to make sure to have access to the tsm nodename.
8. execute restore script on target
RESTORE DB DCC use adsm open 4 sessions TAKEN AT 20080722155529 on /db2/SCC/sapdata1,/db2/SCC/sa
pdata2,/db2/SCC/sapdata3,/db2/SCC/sapdata4 ,/db2/SCC/sapdata5,/db2/SCC/sapdata6,/db2/SCC/saptemp
1 dbpath on /db2/SCC INTO SCC NEWLOGPATH /db2/SCC/log_dir with 16 buffers REPLACE EXISTING redir
ect parallelism 2 without rolling forward without prompting;Hello Anke,
Looks like your create database statement is missing the collating sequence, codeset etc. Here is a database create statement I got from my sapinst for your reference:
create database SX1
automatic storage yes on /db2/SX1/sapdata1, /db2/SX1/sapdata2, /db2/SX1/sapdat
a3, /db2/SX1/sapdata4
dbpath on /db2/SX1
using codeset UTF-8
territory en_US
collate using IDENTITY_16BIT
pagesize 16 k
dft_extent_sz 2
catalog tablespace managed by automatic storage extentsize 2
with 'SAP database SX1';
Regards, -
Redirected restore fails with SQL2071N
Hi,
While trying to do a redirected restore i am getting the below error.
RESTORE DATABASE <SID> CONTINUE
SQL2071N An error occurred while accessing the shared library "/db2/db2<sid>/sqllib/adsm/libtsm.a".
Reason code: "2".
Please find below the database release details below
DB21085I Instance "db2<sid>" uses "64" bits and DB2 code release "SQL09011" with level identifier "01020107".
Informational tokens are "DB2 v9.1.0.1","s061104", "U809676", and Fix Pack "1".
Product is installed at "/db2/<SID>/V9.1".
While trying to connect to the DB i am getting the following msg
db2 => connect
SQL1119N A connection to or activation of database "<SID>" cannot be made
because a previous restore is incomplete. SQLSTATE=57019
Regards,
SamHi Sam
Sorry for late response... plese replace the restore command of yours with this command below and make sure that the set tablespace commands are in the same script or executed in the same session. It shud work
I am assuming that this restore is from an offline backup !!!
RESTORE DATABASE <SID>
USER <user> USING <password>
FROM /instcd/bkup
TAKEN AT 20080316204544
ON /db2/<sid>/sapdata2
,/db2/<sid>/sapdata1
DBPATH ON /db2/<SID>
INTO <SID>
NEWLOGPATH /db2/<SID>/db2,sid>/NODE0000/SQL00001/SQLOGDIR/
WITH 2 BUFFERS
BUFFER 1024
REDIRECT
without rolling forward
without prompting ;
Amit
Edited by: amit chak on Mar 24, 2008 6:37 PM -
Redirected restore procedure!!!
Dear Experts,
During Redirected restore.
After the restore database confirmation Y.
RESTORE DATABASE VNP FROM 'C:\Backup' TAKEN AT 20110903225320 INTO SBX REDIRECT
WITHOUT ROLLING FORWARD
SQL2529W Warning! Restoring to an existing database that is different from
the backup image database, and the alias name "SBX" of the existing database
does not match the alias name "VNP" of the backup image, and the database name
"SBX" of the existing database does not match the database name "VNP" of the
backup image. The target database will be overwritten by the backup version.
The Roll-forward recovery logs associated with the target database will be
deleted.
Do you want to continue ? (y/n) y
After confirming with Y . Am getting the below error
SQL0902C A system error (reason code = "") occurred. Subsequent SQL
statements cannot be processed. SQLSTATE=58005
Am posting my CLP Script Kindly check & say whether it is correct ?
-- ** automatically created redirect restore script
UPDATE COMMAND OPTIONS USING S ON Z ON VNP_NODE0000.out V ON;
SET CLIENT ATTACH_DBPARTITIONNUM 0;
SET CLIENT CONNECT_DBPARTITIONNUM 0;
-- ** automatically created redirect restore script
RESTORE DATABASE VNP
-- USER <username>
-- USING '<password>'
FROM 'C:\Backup'
TAKEN AT 20110903225320
-- ON 'K:\db2\SBX\sapdata1'
-- , 'K:\db2\SBX\sapdata2'
-- , 'K:\db2\SBX\sapdata3'
-- , 'K:\db2\SBX\sapdata4'
-- DBPATH ON '<target-directory>'
INTO SBX
-- NEWLOGPATH 'F:\db2\SBX\log_dir\NODE0000\'
-- WITH <num-buff> BUFFERS
-- BUFFER <buffer-size>
-- REPLACE HISTORY FILE
-- REPLACE EXISTING
REDIRECT
-- PARALLELISM <n>
WITHOUT ROLLING FORWARD
-- WITHOUT PROMPTING;
-- ** table space definition
-- ** Tablespace name = SYSCATSPACE
-- ** Tablespace ID = 0
-- ** Tablespace Type = Database managed space
-- ** Tablespace Content Type = All permanent data. Regular table space.
-- ** Tablespace Page size (bytes) = 16384
-- ** Tablespace Extent size (pages) = 2
-- ** Using automatic storage = Yes
-- ** Auto-resize enabled = Yes
-- ** Total number of pages = 133120
-- ** Number of usable pages = 133112
-- ** High water mark (pages) = 132360
-- ** Tablespace name = PSAPTEMP16
-- ** Tablespace ID = 3
-- ** Tablespace Type = System managed space
-- ** Tablespace Content Type = System Temporary data
-- ** Tablespace Page size (bytes) = 16384
-- ** Tablespace Extent size (pages) = 2
-- ** Using automatic storage = Yes
-- ** Total number of pages = 4
-- ** Tablespace name = SYSTOOLSTMPSPACE
-- ** Tablespace ID = 4
-- ** Tablespace Type = System managed space
-- ** Tablespace Content Type = User Temporary data
-- ** Tablespace Page size (bytes) = 16384
-- ** Tablespace Extent size (pages) = 2
-- ** Using automatic storage = Yes
-- ** Total number of pages = 4
-- ** Tablespace name = SYSTOOLSPACE
-- ** Tablespace ID = 5
-- ** Tablespace Type = Database managed space
-- ** Tablespace Content Type = All permanent data. Large table space.
-- ** Tablespace Page size (bytes) = 16384
-- ** Tablespace Extent size (pages) = 2
-- ** Using automatic storage = Yes
-- ** Auto-resize enabled = Yes
-- ** Total number of pages = 2048
-- ** Number of usable pages = 2040
-- ** High water mark (pages) = 1212
-- ** Tablespace name = SBX#EL701D
-- ** Tablespace ID = 6
-- ** Tablespace Type = Database managed space
-- ** Tablespace Content Type = All permanent data. Large table space.
-- ** Tablespace Page size (bytes) = 16384
-- ** Tablespace Extent size (pages) = 2
-- ** Using automatic storage = Yes
-- ** Auto-resize enabled = Yes
-- ** Total number of pages = 151552
-- ** Number of usable pages = 151544
-- ** High water mark (pages) = 149992
-- TABLE SPACES.........
-- ** Tablespace name = SBX#USER1D
-- ** Tablespace ID = 34
-- ** Tablespace Type = Database managed space
-- ** Tablespace Content Type = All permanent data. Large table space.
-- ** Tablespace Page size (bytes) = 16384
-- ** Tablespace Extent size (pages) = 2
-- ** Using automatic storage = Yes
-- ** Auto-resize enabled = Yes
-- ** Total number of pages = 2048
-- ** Number of usable pages = 2040
-- ** High water mark (pages) = 524
-- ** Tablespace name = SBX#USER1I
-- ** Tablespace ID = 35
-- ** Tablespace Type = Database managed space
-- ** Tablespace Content Type = All permanent data. Large table space.
-- ** Tablespace Page size (bytes) = 16384
-- ** Tablespace Extent size (pages) = 2
-- ** Using automatic storage = Yes
-- ** Auto-resize enabled = Yes
-- ** Total number of pages = 2048
-- ** Number of usable pages = 2040
-- ** High water mark (pages) = 528
-- ** start redirected restore
RESTORE DATABASE VNP CONTINUE;
-- ** end of file
Am restoring DB of SID VNP to SID SBX. Both are on automatic storage databse. Help me as early as possible...
Thanks in advance....Thanks for your quick reply .
K:\db2\db2sbx\db2_software\BIN>db2 -tvf db2restore.clp
UPDATE COMMAND OPTIONS USING S ON Z ON VNP_NODE0000.out V ON
DB20000I The UPDATE COMMAND OPTIONS command completed successfully.
SET CLIENT ATTACH_DBPARTITIONNUM 0
DB20000I The SET CLIENT command completed successfully.
SET CLIENT CONNECT_DBPARTITIONNUM 0
DB20000I The SET CLIENT command completed successfully.
RESTORE DATABASE VNP FROM 'C:\Backup' TAKEN AT 20110903225320 INTO SBX REDIRECT
WITHOUT ROLLING FORWARD
SQL0902C A system error (reason code = "") occurred. Subsequent SQL
statements cannot be processed. SQLSTATE=58005
This is the error am getting . i have changed the script as of you said .
RESTORE DATABASE VNP
FROM 'C:\Backup'
TAKEN AT 20110903225320
-- ON 'K:\db2\SBX\sapdata1'
-- , 'K:\db2\SBX\sapdata2'
-- , 'K:\db2\SBX\sapdata3'
-- , 'K:\db2\SBX\sapdata4'
-- DBPATH ON 'K:\db2\SBX'
INTO SBX
-- NEWLOGPATH 'F:\db2\SBX\log_dir\NODE0000\'
-- WITH 1 BUFFERS
-- BUFFER 1024
REDIRECT
-- PARALLELISM 1
WITHOUT ROLLING FORWARD
-- WITHOUT PROMPTING
After this is the table space definition. There i didnt change the SID of the tablespaces . -
RMAN redirected restore in windows.
Hi All,
My production database is getting backed up using rman/tivoli to tape.
I need to do restoration in another machine using rman redirected restore.
Does anyone has idea what files (tsm files) need to be modified to do redirected restore on windows.
Thanks,
Hal.One correction :
Tivoli Data Protection (TDP) - I don't know which version - Guide for Oracle
But normally RMAN should handle all the stuff. It's only necessary Tivoli server is able to access the new host.
Werner -
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 -
Printer redirection Slow performance
We have a Remote Desktop Server 2008R2.
When a user logs in (trough TS Gateway) with Printer redirection enabled (Using Easy Print method) the performance is very bad.
It's not printing that is slow, it's the performance of the RDP Session/server
For our test we disabled AntiVirus on the server.
Fox example: A user logs in with Local Printers, opening a small Doc file takes about 10 seconds. If the user logs of and logs in without local printers the doc file opens within a second.
Also generally everything is much faster without printer redirection.
The server is fully updated and we are using the most recent RDP Client.
The server is connected to an internet connection with 50/5 Mb Down/Up speed.Hi,
I did a couple of tests:
- Step1: Removed all local printers, logged on with printer redirection enabled on the RDP client. Result: No performance problems with opening DOC files.
- Step2: Added printer 1, logged on. Result: Slow performance with opening DOC files.
- Step3: Removed printer 1, added printer2, logged on. Result: Slow performance with opening DOC files.
- Step4: Repeated Step3 with all printers. Result: Slow performance with opening DOC files.
So it doesn't matter which printer we add, it always results in slow performance. The printers are all from different brands. I happens with all user accounts, also with users that are Domain Admins.
OS:
RDS Server: Windows Server 2008 R2 Standard SP1
Client: Windows Server 2008 R2 Standard SP1
We monitored the CPU and Memory usage while starting Word, the cpu's doesn't use more then 4% utilization and the memory usage is low.
The Remote Desktop Services server has Office 2003 installed with SP3. We cannot upgrade Office to 2007/2010 because it's incompatible with our database.
Can it be that Word 2003 is loading the redirected printers while opening a document what is causing the slow performance?
Kind regards,
Bas -
Optimizing restore performance with MAXPIECESIZE
Hi,
Currently I don't have a limit on the max size of backup pieces, backupsets or number of files per backupset. So I performed a full database backup and transferred it to tape. Then I tried to restore only a small datafile, but I noticed that the whole backuppiece containing all the datafiles was read from tape although I needed only a small portion of it. (The size of the whole database is 70GB and the restored datafile is 3GB)
Then I performed another test and this time I set the MAXPIECESIZE parameter to 1G. The restore process read only the backuppieces it needed to restore this small datafile and the restore was much faster.
My question is: Are there any drawbacks using such an approach - maybe a longer restore time of the whole database, or some other penalty to pay somewhere else?
Thanks in advance for any answers.
Regards,
JureThank to both of you for the answers.
@mrmessin
Actually I haven't measured the whole backup time before and after setting MAXPIECESIZE. But even if the time for the backup will be slightly longer, that's not a problem for me. I prefer a slightly longer backup and a much faster restore. Currently I'm using only one sbt channel - I'll investigate how many tape drives do we have to see if's feasible to use multiple channels.
@tychos
I'll try to perform a restore of the whole database to see if wind/rewind will have any impact. I was also considering the usage of FILESPERSET - maybe I'll use it instead of MAXPIECESIZE, as you suggested.
Regards,
Jure -
We have had a production issue crop up twice now where reports begin running slowly seemingly at random.
When this happens we can see from running SQL Profiler that the report queries are taking an extremely long time to execute. The same queries when run directly in management studio run quickly.
Initially I suspected parameter sniffing, and tried using OPTION (RECOMPILE) in the reports, as well as clearing out the particular query from the plan cache and running the SQL in SSMS to try and get a better plan etc but no amount of jiggery pokery by
me could get the queries to run any faster.
The really weird thing - is that stopping and starting the report server via the reporting services configuration manager instantly cures the problem.
I'd really love to know - why this might be? Is it something to do with the report server closing and re-opening its connections to the database? That's the only sort of thing I can think of...any ideas? Anyone? Any suggestions would be much appreciated.
LucasFHi LucasF,
In your scenario, usually we can monitor the execution log in Report Database. If you run below query, you can get the results how long the report takes to render (TimeRendering), how long to process the report(TimeProcessing) and how long to retrieve data
from Database(TimeData). You can check the starttime and endtime to know the total time for executing a report.
SELECT TOP1000 *FROM[ReportServer].[dbo].[ExecutionLog2]
More details information, please reference to similar thread below:
Steps for troubleshooting a slow SSRS 2014 server
Troubleshooting Reports: Report Performance
In SQL Server Reporting Services, a job will be created by SQL Server Agent if any of the following processes is underway:
query execution on a remote or local database server
report processing
report rendering
To cancel a job that is running on the report server, we can cancel the job directly or reduce the report execution time-out value in the SQL Server Management Studio and then will stop query execution. Please refer to the steps below:
Open SQL Server Management Studio, and connect to "Reporting Services".
Under the Report Server node, right-click on the "Jobs" folder and select "Refresh". Then, right-click on "Jobs" again and click "Cancel All Jobs".
Right-click on the Report Server node and open the "Server Properties" dialog.
Click the "Execution" option, and set the "Limit report execution to the following number of seconds:" to a much smaller number. After this issue is resolved, this configuration should revert to the previous state.
Reference:
Managing a Running Process
Setting Time-out Values for Report and Shared Dataset Processing
In addition, we can also use the KILL Transact-SQL statement to terminate a normal connection by terminating the transactions that are associated with the specified session ID. For the details information, you can refer to:
KILL (Transact-SQL)
If you still have any problem, please feel free to ask.
Regards,
Vicky Liu
Vicky Liu
TechNet Community Support -
What can i do to restore performance of "Clear All History"; it runs slowly in v4.0
The comparative run times of Clear All History function between v4.0 and (I think) v3.61 is significantly degraded. It can run over a minute now, with minimal history cache.
Delete your Preference File
Preference and other file locations in Lightroom 5 -
Restoring Tablespace in different location from the original location
Dear Experts
We are doing an Restoing of production database in to an another server. where the production database runs on Windows and the sap directories has been stored in 6 drives but in the second servder which has only 3 drives but high capacity. we want to restore the files from the production database (hich will have the drive reference ) to the new server ( which has 3 drives only) by referring only the sap directories so that it is safe to pull the data
in brrestore how the comman / syntax should be?
could any one guide us
regards
balaHi,
You will have to follow a redirected restore procedure for oracle rather than a normal restore.
For this you will have to do the following:
1. Take a full offline backup or an online consistent backup of your production database.
2. Backup control file to trace on your production server.
3. Display the back<SID>.log summary log in production and identify the u2018affu2019 or 'anf' file that was created for the production backup.
4. Copy the back<SID>.log and .aff/.anf files to the sapbackup directory of quality.
5. Now use the brrestore redirected option:
brrestore -m all,<source drive 1>=<target drive 1>,<source drive 2>= <target drive 2> -b <file-id>.aff
This performs a redirection of the file during brrestore operation.
6. Manipulate the control file trace you created above and change the drives accordingly. Rename it to control.sql
7. Then do the following:
>sqlplus /nolog
>connect / as sysdba
>@c:\control.sql
>shutdown immediate
>startup mount
>recover database using backup controlfile until cancel;
The recover part is only required if you have used a online backup.
Hope this helps.
Regards, Dibya -
Hi!
Due to a unwanted batch input job we need to restore a R/3 system from prod to a sandbox system to have a reference system.
I have created a restore script with the brdb6brt tool to do a redirected restore, and it is currently creating table spaces in the database.
We are running on AIX v5.2 and DB2 v8 FP 11.
We have a full DB backup on disk and incremental backups on a networker managed tape library.
My question is:
If you restore with the parameter "incremental", is it possible to mark the DB as restored and start the rollforward process without applying the incremental backups on tape?
The documentation for DB2 leaves some space for interpretation, and I don't have the time to do wrong for this 1.4 TB DB.
Here are the examples from the documentation:
"Notes:
After successful completion of step 1, and before completing step 3, the restore operation can be aborted by issuing:
db2 restore db mydb abort
After successful completion of step 3, and before issuing all the required commands in step 4, the restore operation can be aborted by issuing:
db2 restore db mydb incremental abort "
Will any of these commands abort the restore so I need to restart the restore, or just exit the restore procedure so I can continue with rollforward.
BR MortenHi!
I will answer this post myself.
First read contetn in link: http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic=/com.ibm.db2.udb.doc/admin/t0006070.htm
In addition:
Here the description of the command parameters for the restore:
CONTINUE
Specifies that the containers have been redefined, and that the
final step in a redirected restore operation should be performed.
ABORT
This parameter:
Stops a redirected restore operation. This is useful when an
error has occurred that requires one or more steps to be
repeated. After RESTORE DATABASE with the ABORT option has
been issued, each step of a redirected restore operation must
be repeated, including RESTORE DATABASE with the REDIRECT
option.
Terminates an incremental restore operation before completion.
Therefore if you allready have issued the "RETSTORE DATABASE NBP
CONTINUE" without any error, then the restore is finished.
You cannot do a continue manually because you are in another session
then the script (Therefore you get the SQL2008N).
Best regards,
Steffen Stolz
SAP Global Support, DB2 UDB for UNIX and Windows
Maybe you are looking for
-
I have a BPM and I want to bring in ALERT mechanism when my BPM Fails, how to configure the alert in BPM? Thanks.
-
Permissions work locally but not remotely
I've a server that if I log in locally I can change/manage file/folder permission with no issues....but if I remote in via Remote Desktop Connections (I've tried from several workstation sub-nets) I can log on, navigate to the folders, but I can't ch
-
Changing iChat status with applescript
I have the basic commands to change the status in my iChat (v 5.0.1): tell application "iChat" set status to away (or available) end tell When I set my status as "away" everything works fine. The green dot turns red and the status message says away.
-
Photoshop cs6 images look dark and green when put into dropbox.
I have just upgraded to PS CS6 and my images are looking dark and green when I upload them into dropbox to send to clients for review. A screenshot of my image looks perfect in dropbox but if I save it directly it looks terrible.
-
My 5d mark 3 says it can't recognize card1.
I have a fairly new 5D Mark 3 and it is saying it won't recognize Card1. It says to format the card but the camera will not do so. Very dissapointing in a new and expensive model camera. I have tried new cards and old cards and get the same message