Posts Tagged ‘database’

Minimum DB2 database Transaction logsize for Installing BMC Remedy

March 28th, 2010
Minimum DB2 database transaction log size
When you upgrade an AR System 7.5.00 server that uses an IBM® DB2 Universal
Database® in an environment supporting BMC Remedy IT Service Management
(ITSM) applications, BMC recommends a minimum database transaction log file
size of 1.3 gigabytes (GB).
Before starting the upgrade, adjust the following DB2 Universal Database
configuration parameters to ensure that logfilesize >= 1.3 GB:
???? LOGFILSIZ
???? LOGPRIMARY
???? LOGSECOND
For example:
WARNING
This example is from a test environment and represents a minimum transaction
log file size. To determine the log file requirements for your environment, consult
your database administrator before beginning the upgrade.
For more information about determining your transaction log file size, go to
http://publib.boulder.ibm.com/tividd/td/tec/SC32-1233-00/en_US/
HTML/ecoimst65.htm.

Minimum DB2 database transaction log size

When you upgrade an AR System 7.5.00 server that uses an IBM® DB2 Universal Database® in an environment supporting BMC Remedy IT Service Management (ITSM) applications, BMC recommends a minimum database transaction log file size of 1.3 gigabytes (GB).

Before starting the upgrade, adjust the following DB2 Universal Database

configuration parameters to ensure that logfilesize >= 1.3 GB:

???? LOGFILSIZ

???? LOGPRIMARY

???? LOGSECOND

For example:

Log file size (4KB) (LOGFILSIZ) = 20000

Number of primary log files (LOGPRIMARY) = 8

Number of secondary log files (LOGSECOND) = 10

WARNING

This example is from a test environment and represents a minimum transaction log file size. To determine the log file requirements for your environment, consult your database administrator before beginning the upgrade.

For more information about determining your transaction log file size, go to

http://publib.boulder.ibm.com/tividd/td/tec/SC32-1233-00/en_US/

HTML/ecoimst65.htm.

TCP/IP error while installing ARSystem Remedy on SQL Database?

March 26th, 2010

TCP/IP connection to the host XXXX-XXX using port number XYZ failed.

Possible causes:
Database services are not available/?running or Network configuration is not configured correctly for TCP/?IP protocol or IP or host name/? port number is incorrect.

Follow the steps to avoid this issue:

Set your SQL connections to allow TCP/IP:
a) Open the SQL Server Configuration Manager.
b) Click Network Configuration for your SQL Server instance.
c) Make sure that TCP/IP Protocol is enabled.
d) View the TCP/IP Properties dialog box for your database instance, and make sure that the IP Addresses tab has a TCP Port number specified. (The default port is 1433.)
e) Restart all Microsoft SQL services to effect this change.
If possible do a system restart, which is not necessary under normal conditions, but if only the above trick fails, and retry the same.
This is should allow ARS Installer to find the SQL Database instance and continue ARS installation.
Detailed steps of ARS are postponed for another day ;)
Njoy
Venkat