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
Similar Messages
-
Poor Bluetooth performance with all aluminum Mac Pro
The all aluminum case for pre-mavericks Mac Pro is the primary reason for poor antenna performance of Bluetooth. Aluminum, being a good conductor, acts as a reflector of EMF forming what is known as a Faraday Cage, essentially trapping emissions within the box. Normally, holes drilled in the case would allow enough EMF to pass through the case but the hole size for transmission is directly proportional to the lowest frequency that will pass through easily. An example is the typical microwave oven where the window is actually a conducting sheet with small enough hole such that higher freq light waves pass easily through the sheet but lower frequency microwaves do not. Perhaps if the drive bay covers were made of plastic, transmission of the Bluetooth and wifi would be sufficient. One might carefully nibble a slot or two in the side door but this would surely invalidate any warranty and care would have to be taken not to get aluminum particles inside the computer. This would probably nullify any FCC approval of the machine due to clocking noise interference with other devices. The best approach would probably be a tuned waveguide that passes frequencies only around 2.4 GHz ~ 5 GHz through the case (very similar to the way tuned ports on audio speakers pass a band of frequencies needed to extend bass response). I'm sure Apple will have corrected this design flaw in the new Mac Pro introduced this year. If you have lots of time on your hands you can get a college level text on electromagnetics (Maxwell's Equations, etc.) and derive all the details but with a bit of experimenting and reading about tin can antenna mods to wireless routers you should be able to improve Bluetooth performance significantly.
Thanks for the suggestion. I will have to move my wireless home base station. It is on the same desk as my mini so much less than 5 feet away.
-
Very poor network performance with a G4
I have a white & grey G4 (1.25GHz and 256MB) running OS X 10.4.5. It's exhibiting very poor network performance, e.g. it will not FTP files over a LAN at more than about 40KB/second.
Other nodes on the same switch perform fine, as do other ports on the switch. The machine is set to autodetect for speed & duplex, so my question is -- how do I debug this? I've tried swapping network cables already...
Thanks!
ChrisThis came down to an incompatibility between the G4 and the Cisco. When the switch is set to force 100Mbit but negotiate duplex, the G4 doesn't like it. Going back to auto speed & duplex fixed the problem...
-
Poor OpenGL performance with my laptop
Hello.
I have installed Archlinux on my nvidia desktop computer and I can play opengl games smoothly. But the problem is with my laptop. I remember, long time ago , when opengl ran pretty well with linux compared to windows. Since one month ago, I've had windows and Arch on my laptop, when I tried to play Openarena, it ran much better on windows than linux, what has happened to intel driver? Now I only have linux and want to continue playing and it's impossible with that performance.
I've read many posts and I've failed in my purpose, I'm missing something...
$ lspci | grep -i vga
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)
Thanks in advance.cocotero wrote:Yes, KMS is enabled. I've read that the better solution is to downgrade some xorg related packages. Is it impossible to use intel driver on 3 or more years old laptops? I mean, with good performance.
Unfortunately yes, I have seen since I use linux (like five years) that once a intel video card is not supported any more there is no going back to its optimum state, also the problem with downgrading packages is that at some point you would not be able to update other software any more with out issues. -
Poor query performance with BETWEEN
I'm using Oracle Reports 6i.
I needed to add Date range parameters (Starting and Ending dates) to a report. I used lexicals in the Where condition to handle the logic.
If no dates given,
Start_LEX := '/**/' and
End_LEX := '/**/'
If Start_date given,
Start_LEX := 'AND t1.date >= :Start_date'
If End_date given,
End_LEX := 'AND t1.date <= :End_date'
When I run the report with no dates or only one of the dates, it finishes in 3 to 8 seconds.
But when I supply both dates, it takes > 5 minutes.
So I did the following
If both dates are given and Start_date = End date,
Start_LEX := 'AND t1.date = :Start_date'
End_LEX := '/**/'
This got the response back to the 3 - 8 second range.
I then tried this
if both dates are given and Start_date != End date,
Start_LEX := 'AND t1.date BETWEEN :Start_date AND :End_date'
End_LEX := '/**/'
This didn't help. The response was still in the 5+ minutes range.
If I run the query outside of Oracle Reports, in PL/SQL Developer or SQLplus, it returns the same data in 3 - 8 seconds in all cases.
Does anyone know what is going on in Oracle Reports when a date is compared with two values either separately or with a BETWEEN? Why does the query take approx. 60 times as long to execute?Hi,
Observe access plan first by using BETWEEN as well as using <= >=.
Try to impose logic of using NVL while forming lexical parameters.
Adinath Kamode -
After system restore to back up have lost texts, photos and app data
Speakers not working on iphone all of a sudden and volume switches not working (just the volume comes up but no bars at the bottom). So did system restore and more problems.
After I did this restore (to my backup done today) to my iphone 4s, I now have no text messages on my phone, no photos and no data on my nike running app (6months of records of runs). Have searched through these forums and still stuck.
I think I'm going to have to take my iphone somewhere for the speaker issue, but have no idea where as optus sent it out to me directly via mai l(Adelaide, Australia).
In the meantime, I really want my texts, photos and app data back on my phone.
any help HUGELY appreciated..thanks for your reply. I am trying the restore again now.
But no, I still have no sound, so it was all for naught. Its fine if I have headphones in, and fine if its in a dock or connected to bluetooth, the phone also rings and I can hear people on the phone: the only sound that doesnt work is music playing through the speaker, and video. Also when I press the volume up and down buttons, nothing works. I suspect there is something wrong with the docking connection as far as I can see from other peoples questions on here.
But the loss of texts and app data is just the icing on the cake -
Does anyone else get poor Virtualbox performance with Kernel26-ck?
I don't know if it's BFS itself or one of my customized options specifically, but if I try to play Netflix inside my Windows XP virtual machine it is terrible and my CPU load is quite high.
If I boot into the stock Arch kernel I do not have this problem. Anyone else experience this?So it seems like it's just me and my config.
uname -r is different, and I have compiled the kernel modules for it.
It is only in the last few weeks/month that the performance issue is there.
Sometimes, when I run the VM, it'll drop me to TTY1 which a bunch of magic output, but it's not a kernel panic. I can switch back to my graphical TTY and everything is fine except the VM is just a black window and has to be forced to close via my WM.
I'm not sure what kernel config options would do something like this. I have my timer frequency at 1000Hz, which is the main thing I've seen on the Google that can cause problems.
I am on a Core i3 processor with intel graphics.
If I post my kernel config, do you think you'd be able to spot anything that would mess up Virtualbox in this subtle way?
Any ideas? I'm guessing I'm probably on my own. -
Poor System Performance with Aperture 3
I am using a MBP (3,1) 15", 4 GB Ram, 2.6 ghz processor with Snow Leopard 10.6.2
After I run an import of photos, the entire system very nearly comes to a complete halt. EVERYTHING lags while Aperture does its post import processing, and then for 5-10 minutes after it says it has completed.
I am having the same result on my dual quad-core Mac Pro.
Is this a happening to anyone else? This product is horrific as it relates to system performance! Any suggestions or tips/tricks to improve performance?
Please help! Thinking of going back to Aperture 2.
Jessehttp://discussions.apple.com/thread.jspa?threadID=2334088&tstart=0
It hasn't spent much time off the first page of the forum.
Ian -
Probable reasons for poor youtube performance with Chrome browser
Using my new Lenovo Yoga 3 11 inch I have been experiencing horrendeously choppy youtube performance using the chrome browser, which was generating lots of heat due to the demands that chrome was asking of the CPU. The same youtube video plays perfectly smooth using Internet Explorer, and the laptop remains cool thanks to the much lower CPU load. So I was wondering why this was so. I wasted a lot of time following the stock answers of the internet - disabling plugins, 32 bit vs 64 bit chrome, updating drivers, even factory resetting and updating! But after routing through the internet guff, I did find some excellent information that fits my experiences, so I have little reason to doubt that the following statements, extracted from various parts of the internet, are true: Quote: "Google decided that Chrome should always use VP9 codec on PCs – even if there is no hardware acceleration available. This means that Chrome is doing CPU decide and that is pretty demanding in a 3.5w power limit for CPU, GPU, LLC, and FIVR. On IE, YouTube uses H.264/AVC and the hardware codec support kicks in for much more power efficiency." Quote: "When you watch YouTube using Chrome it uses VP8/VP9encoding by default. This type of encoding does not support hardware acceleration (which means it won’t use the on-board GPU – or video chip for you non-techies) so, your CPU has to do all of the work to decode and display the video." I thought people may find this information interesting, expecially if you are using a laptop with a light CPU such as Intel Core M. Chrome is my browser of choice, but this situation has forced me to use Internet Explorer for youtube.
I found that Chrome youtube runs much smoother and cooler on my Lenovo Yoga 3 11 inch after installing the h264ify Chrome extension. This allows Chrome to use the h264 codec for youtube instead of the CPU hammering VP9 codec.
-
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 -
Hi community,
here are informations to our environment:
Windows Server 2008 R2 with SP1 - mspatchlevel 05/2014
XenApp 6.5 RP3 + Hotfix_XA650R01W2K8R2X64003 + Hotfix_XA650R03W2K8R2X64013
AcroRead.msi + 11001.msp + 11003.msp + 11004.msp + 11006.msp
Network: 10GB
Problem:
After migration to Adobe Reader 11.0.06 our users are complain about long printingtimes with PDF documents.
What i have done:
Test printing two different documents from local storage an network (dfs,nfs) - notice the printingtime in our environment depends not on used storage!
1. 310 pages document with text (7,023KB)
Adobe Acrobat XI on Samsung ML-451x 501x Series driver Version 3.11.39.00.58.01
Average 52 seconds (done 5 same printjobs with same dokument) to print document in spooler.
Change printer to:
Adobe Acrobat XI on Samsung CLP-770 Series PCL6 Version 3.10.57:76
Average 46 seconds (done 5 same printjobs with same dokument) to print document in spooler.
2. 4 pages document with grafics (4,438KB)
Adobe Acrobat XI on Samsung ML-451x 501x Series driver Version 3.11.39.00.58.01
Average 45 seconds (done 5 same printjobs with same dokument) to print document in spooler.
Change printer to:
Adobe Acrobat XI on Samsung CLP-770 Series PCL6 Version 3.10.57:76
Average 39 seconds (done 5 same printjobs with same dokument) to print document in spooler.
Befor migration we have Server 2003 SP2 and XenApp 4.5FR6 with Adobe Reader 9.5.5
I did the same testing but the time to print was much faster!
1. 15 Seconds to print 310 pages document
2. 28 seconds to print 4 pages document with grafics
Any ideas to make printing faster on WindowsServer 2008R2 with Adobe Reader?
Next step is testing the old version from reader on 2008R2 but on security aspects is this not the way...
Thx
ThomasHi Pat,
thx for your answer :-)
i will try the older one 9.5.5 and the newest 11.0.07
Regards,
Thomas -
Poor WAAS Performance with Veeam Backup and Replication
I have two wae-574's doing inline interception on a T1 line. I'm doing Veeam replication across that T1 Line (or attempting to). It appears that I'm getting roughly zero acceleration during the veeam jobs and it doesn't make much sense why. Other applications are being accelerated. The WAN to LAN statistics never jump over 1.5 megabit when running the job. I'm not sure what to do at this point.
10.30.1.44 is my Veeam Box. It's a Virtual Machine on the source side. I've run the show stat command on the remote waas unit.
Veeam is setup to use appliance mode, with no compression (thinking the WAAS would do the magic).
RemoteCiscoWaas#show stat con | include 30.1.44
248287 10.30.1.44:54964 10.30.2.62:902 1c:c1:de:7f:de:cc T 00.0%
248345 10.30.1.44:54975 10.30.2.62:902 1c:c1:de:7f:de:cc T 00.0%
248386 10.30.1.44:55029 10.30.2.62:902 1c:c1:de:7f:de:cc T 00.0%
Any Ideas?
Thanks..It works now! I had to set the VMware-VMconsole policy to full acceleration on each WAAS device involved in the Veeam traffic (thanks for the help on the veeam forum). Veeam uses port 902 in network mode for replication which was already assigned to a policy but set to TFO only as it's generally just console traffic. Seeing 12 Megabit peaks from a T-1 Line.. Nice!
RemoteCiscoWaas#show stat con | incl 902
196026 10.30.1.44:49533 10.30.2.62:902 1c:c1:de:7f:de:cc TDL 99.2%
196038 10.30.1.44:49542 10.30.2.62:902 1c:c1:de:7f:de:cc TDL 98.6%
196050 10.30.1.44:49552 10.30.2.62:902 1c:c1:de:7f:de:cc TDL 84.6% -
Poor network performance with Websockets running on apple device
I am working on an HTML/Javascript running on mobile devices that is communicating with a Qt/C++ application running on a PC. Both the mobile device and the PC are on a local network. The communication between the HTML page (client) and the C++ app (server) is done using Websockets.
The HTML page is a remote control for the C++ application, so it is needed to have a low latency connection between the mobile device and the PC.
When using any non-Apple device as a client, data is sent to a rate between 60 to 120 frames/sec, which is totally acceptable. When using an Apple device, this rate falls to 3-4 frames/sec. I also checked ping times (Websocket implementation, not a ping command from command line). They are acceptable (1-5 ms) for Apple devices as long as the device is not transmitting data. Whenever it transmits data, this ping time raises to 200ms.
Looking from the Javascript side, the Apple devices always send data at a consistent rate of 60 frames/sec, as any other devices do. However, on the server side, only 3 to 4 of these 60 frames are received when the client is an Apple device.
Does anyone have any idea on what can be happening?
Here is my Javascript code :
<script language="javascript" type="text/javascript">
var wsUri = document.URL.replace("http", "ws");
var output;
var websocket;
function init()
output = document.getElementById("output");
wsConnect();
function wsConnect()
console.log("Trying connection to " + wsUri);
try
output = document.getElementById("output");
websocket = new WebSocket(wsUri);
websocket.onopen = function(evt)
onOpen(evt)
websocket.onclose = function(evt)
onClose(evt)
websocket.onmessage = function(evt)
onMessage(evt)
websocket.onerror = function(evt)
onError(evt)
catch (e)
console.log("Exception " + e.toString());
function onOpen(evt)
alert("Connected to " + wsUri);
function onClose(evt)
alert("Disconnected");
function onMessage(evt)
alert('Received message : ' + evt.data);
function onError(evt)
alert("Error : " + evt.toString());
function doSend(message)
websocket.send(message);
window.addEventListener("load", init, false);
</script>
Data is sent from Javascript side using dosend() function.What version of websocket is your server using? That is pretty much on the bleeding edge of things. It looks like you need to use RFC6455 and iOS6 and it should work fine.
Thanks for the post. I didn't know about websockets. Very interesting. -
How get the best performances with a McBook Pro 2,3GHz and 16 Go of Ram ?
Hi,
I've recently bought a MacBook Pro and I want to optimize my After Effects preferences to enjoy the best performances.
There's the specifications from Apple:
2.3GHz quad-core Intel Core i7
Turbo Boost up to 3.5GHz
16GB 1600MHz memory
512GB PCIe-based flash storage
Intel Iris Pro Graphics
NVIDIA GeForce GT 750M
with 2GB GDDR5 memory
Thanks in advance if one of you could help me to do this
MauriceOptimizing for performance: Adobe Premiere Pro and After Effects | After Effects region of interest
-
I was on the phone for an hour and did not get any help. can someone please help. Itunes let me do a restore but now it is
stuck on my Iphone screen sayinng connected to Itunes and i can not get further than than the language and the country.......??????solved!
turn off your phone, then unplug from the usb cable, but leave that cable attached to the computer. Importaint!: Quit Itunes. Then with your phone off, hold down the home button and plug the usb cable into the phone. keep the home button pushed until you see the connect to itunes screen. Itunes will launch and it will see it in recovery mode.
Maybe you are looking for
-
Everything keeps freezing/crashing after Mavericks installation on MacBook Pro
Everything keeps freezing/crashing after Mavericks installation on MacBook Pro. It started with Photoshop, then Safari, and now the Kinect sensor. Mavericks is the worse thing that happened to me I have a thesis project to work on! What can I do? How
-
Using NI & non-TDM plugz on HD/2 system with Logic 8 as front-end
For the life of me I can not figure out why in Logic 8, using a TDM Configuration, why I can only use what looks to be TDM plugz in my session? I used to love being able to run Guitar Rig as a DAE channel in Logic... Did Apple do away with RTAS suppo
-
Order of streaming images in iPhoto on the iPad
I would like to know if there is a way to set the order of the photos in photo stream using iPhoto on my iPad. It seems the default view is to have them go from oldest to newest. With a 1000 photos that is a lot of scrolling and why I would want to s
-
UWL: enabling the web GUI for html for work items
Hi, We have configured UWL in portal. All the backend work items are appearing in the UWL iView in portal. But when we click on some of the work items SAP GUI opens instead of web GUI for html. Does any one have information what needs to be confi
-
Component should not be made available for backflush during final Backflush
Hi, In REM Scenario, during final backflush system explodes and proposes all components in the header material for GI backflush. Is there any way we can restrict certain materials not to appear for GI backflush and that can be posted at later time. y