Hello
This section will detail out some insight on how to set up the database system for PIM.
PIM Database Pre-Installation Checklist
During database installation:
- Create a new schema
- Create a user with full read/write access to the PIM schemas, including the ability to create tables.
Database Administration Tool
Database Administration Tool is required for Database setup and configuration. For example MS SQL Server Management Studio or Oracle SQL Developer.
After the database setup Test the connection by using the database administration tool installed on the PIM server to log in to the database.
Database Storage Information
A physical volume location on where to store the data and log files of the PIM databases needs to provided during Database Setup.
Default PIM Database Ports
Port Database
1433 MSSQL
1521 Oracle
Select one of the supported databases and follow the corresponding database setup guides.
Microsoft SQL Server
When installing MS SQL Server the following settings must be considered.
Server Collation
While setup the Microsoft SQL Server for the Server Collation setting use Latin1_General and additional the options Case sensitive and Accent sensitive (Latin1_General_CS_AS).
Database User Settings
Database setup user : The users which install the PIM databases must have set the roles DBCreator and Public.
Database application users : All database users which are used for the database access of the PIM applications must always have English as standard language. Additionally uncheck the Enforce password policy checkbox.
Named-Instance Support
PIM applications can connect to MS-SQL Server named instances using their port. Make sure that the MS SQL Server Network Configuration is correct. In section IPAll the TCP Port property must be set to a free port (Default is 1433), and TCP Dynamic Ports must be disabled.
Oracle
Consider these settings during installation of the database instance.
Server Settings
- Enable at least the feature Enterprise Manager Repository
- Set database character set to Unicode (AL32UTF8)
- Set the national specific character set to AL16UTF16 - Unicode UTF-16 Universal character set
- Set standard increase redo-log file size to 1024 MB (each), have at least three redo-logs
- Set standard language to American.
- Set the parameter open_cursors to 3000
- Set the parameter processes to 600
- Create a tnsnames.ora file at <OracleDBInstanceFolder>/NETWORK/ADMIN and map service names to the
- connect descriptors for the local naming method
- Disable password expíration, otherwise ensure that passwords for PIM schemas never expire
- Specify pga_aggregate_target and sga_target due to system requirements
- Ensure have enough space for Oracle TEMP tablespace
- Ensure having set dynamic_sampling to at least level 2 since ReportStoreTemp tables depend on it
Recommended initialization parameters
Recommended init.ora settings for Microsoft Windows.
|
Name
|
Value
|
|
db_block_size
|
8192
|
|
db_domain
|
|
|
db_file_multiblock_read_count
|
<ensure parameter is not set>
|
|
disk_asynch_io
|
TRUE
|
|
dynamic_sampling
|
2
|
|
filesystemio_options
|
ASYNCH
|
|
java_pool_size
|
0
|
|
job_queue_processes
|
10
|
|
nls_language
|
AMERICAN
|
|
nls_territory
|
AMERICA
|
|
open_cursors
|
3000
|
|
processes
|
600
|
|
recyclebin
|
OFF
|
|
remote_login_passwordfile
|
EXCLUSIVE
|
|
sessions
|
670
|
|
undo_management
|
AUTO
|
|
undo_tablespace
|
UNDOTBS1
|
|
TNS_LISTENER
|
TCP Protocol
|
Database User Settings
During PIM database installation the SYSTEM user is important.
DBA Tasks
- Always monitor I/O waits
- Redo Log Checkpoints/Switching : Frequent log switching decreases performance. Redo log size needs to be sized appropriately
- Archive Logs : When archive area is full, all processes in the DB stops until archive logs are backup and the archive
- backed up logs deleted to free up space
- Cache Hit Ratio : Should be at least a 95% cache hit
0 Comment(s)