Borland StarTeam 2009 - Borland Technical Publications
Borland StarTeam 2009 - Borland Technical Publications Borland StarTeam 2009 - Borland Technical Publications
Oracle 10gR2 DatabasesThis section provides information about tuning Oracle 10g databases.Automatic Shared Memory ManagementOracle 10g introduced Automatic Shared Memory Management (ASMM) of individual SGA components likeshared pool, java pool, large pool and db cache. You do not need to estimate when setting the size of SGAcomponents. In fact, there is no need to set any parameters defining SGA size.All you have to do is to set a new parameter called SGA_TARGET. The parameter SGA_TARGET takes avalue which indicates the maximum size of SGA required for your instance.Consider that you set SGA_TARGET to say 800MB. This indicates that maximum size to which SGA can growis 800MB. All the SGA components like shared pool, buffer cache, large pool, java pool will be allocated fromthis 800M maximum SGA. Oracle will automatically calculate the initial size of these components and resizesit as per the requirement without any manual intervention.You do not have to explicitly define values for shared pool, buffer cache, large pool and java pool if you setSGA_TARGET.The SGA_TARGET will be limited by the SGA_MAX_SIZE value.The SGA_MAX_SIZE cannotbe modified dynamically. If SGA_MAX_SIZE is not set, both the parameters have the same value and it willbe not possible to increase the size of SGA_TARGET dynamically.Automatic Segment Space ManagementThe Automatic Segment Space Management (ASSM) feature allows Oracle to use bitmaps to manage thefree space within segments. The bitmap describes the status of each data block within a segment with respectto the amount of space in the block available for inserting rows. The current status of the space available in adata block is reflected in the bitmap allowing Oracle to manage free space automatically with ASSM.ASSM tablespaces automate freelist management and remove the ability to specify PCTUSED, FREELISTS,and FREELIST GROUPS storage parameters for individual tables and indexes created in ASSM tablespaces.The values for parameters PCTUSED and FREELISTS are ignored and Oracle automatically manages thespace for these tables and indexes inside the tablespace using bitmaps. PCTFREE can still be specified andis used with ASSM.Oracle 11g DatabasesThis section provides information about tuning Oracle 11g databases.Automatic Memory Management (AMM)Beginning with version 11g, the Oracle database can automatically manage the SGA memory and the instancePGA memory. You only need to designate the total memory size to be used by the instance, and the Oracledatabase will dynamically exchange memory between the SGA and the instance PGA as needed to meetprocessing demands. This capability is referred to as automatic memory management. With this memorymanagement method, the database also dynamically tunes the sizes of the individual SGA components andthe sizes of the individual PGAs.114 | Oracle Database Tuning
AMM is implemented using Memory_Target and Memory_max_target parameters. Use ofMEMORY_MAX_TARGET is optional. When MEMORY_MAX_TARGET is not set, Oracle automatically setsMEMORY_MAX_TARGET to the value of MEMORY_TARGET.To switch to AMM, define the value of MEMORY_TARGET in the spfile. It is important to ensure that the valuesof SGA_TARGET and PGA_AGGREGATE_TARGET are set to 0. Customers upgrading to 11g instance mustset the value of SGA_TARGET and PGA_AGGREGATE_TARGET to 0.Oracle Database Tuning | 115
- Page 63 and 64: Installing a StarTeamMPX Root or Re
- Page 65 and 66: Installing StarTeam Layout Designer
- Page 67 and 68: Installing StarTeam Workflow Extens
- Page 69 and 70: The default installation folder is
- Page 71 and 72: 7. In the Choose Shortcut Folder di
- Page 73 and 74: • Review the settings and click I
- Page 75 and 76: Understanding the Encoding Differen
- Page 77 and 78: 5. Create an initial hive for the N
- Page 79 and 80: Running SQL Scripts for Microsoft D
- Page 81 and 82: • starteam_sqlserver_get_dbinfo.s
- Page 83 and 84: select * from s011. Verify that at
- Page 85 and 86: Important: The SQL Server ODBC Data
- Page 87 and 88: characters such as !, @, #, or %. E
- Page 89 and 90: 1. Install Oracle Server. Most cust
- Page 91 and 92: After setting NLS_LANG correctly, O
- Page 93 and 94: Creating and Starting a Server Conf
- Page 95 and 96: Number of UsersBetween 15 and 50Bet
- Page 97 and 98: Run: weekly.• starteam_oracle_cre
- Page 99 and 100: • The Oracle database’s net ser
- Page 101 and 102: Native-II Vault FoldersFor server c
- Page 103 and 104: A new server log file is created ea
- Page 105 and 106: Savings Time) information for Easte
- Page 107 and 108: The data is critical and must be re
- Page 109 and 110: Export backups are cross-platform a
- Page 111 and 112: Oracle 10g has introduced a new fea
- Page 113: Total MemoryRecommended 10gR2 Setti
- Page 117 and 118: Microsoft SQL Server (continued)def
Oracle 10gR2 DatabasesThis section provides information about tuning Oracle 10g databases.Automatic Shared Memory ManagementOracle 10g introduced Automatic Shared Memory Management (ASMM) of individual SGA components likeshared pool, java pool, large pool and db cache. You do not need to estimate when setting the size of SGAcomponents. In fact, there is no need to set any parameters defining SGA size.All you have to do is to set a new parameter called SGA_TARGET. The parameter SGA_TARGET takes avalue which indicates the maximum size of SGA required for your instance.Consider that you set SGA_TARGET to say 800MB. This indicates that maximum size to which SGA can growis 800MB. All the SGA components like shared pool, buffer cache, large pool, java pool will be allocated fromthis 800M maximum SGA. Oracle will automatically calculate the initial size of these components and resizesit as per the requirement without any manual intervention.You do not have to explicitly define values for shared pool, buffer cache, large pool and java pool if you setSGA_TARGET.The SGA_TARGET will be limited by the SGA_MAX_SIZE value.The SGA_MAX_SIZE cannotbe modified dynamically. If SGA_MAX_SIZE is not set, both the parameters have the same value and it willbe not possible to increase the size of SGA_TARGET dynamically.Automatic Segment Space ManagementThe Automatic Segment Space Management (ASSM) feature allows Oracle to use bitmaps to manage thefree space within segments. The bitmap describes the status of each data block within a segment with respectto the amount of space in the block available for inserting rows. The current status of the space available in adata block is reflected in the bitmap allowing Oracle to manage free space automatically with ASSM.ASSM tablespaces automate freelist management and remove the ability to specify PCTUSED, FREELISTS,and FREELIST GROUPS storage parameters for individual tables and indexes created in ASSM tablespaces.The values for parameters PCTUSED and FREELISTS are ignored and Oracle automatically manages thespace for these tables and indexes inside the tablespace using bitmaps. PCTFREE can still be specified andis used with ASSM.Oracle 11g DatabasesThis section provides information about tuning Oracle 11g databases.Automatic Memory Management (AMM)Beginning with version 11g, the Oracle database can automatically manage the SGA memory and the instancePGA memory. You only need to designate the total memory size to be used by the instance, and the Oracledatabase will dynamically exchange memory between the SGA and the instance PGA as needed to meetprocessing demands. This capability is referred to as automatic memory management. With this memorymanagement method, the database also dynamically tunes the sizes of the individual SGA components andthe sizes of the individual PGAs.114 | Oracle Database Tuning
Change language