Troubleshooting Installations › Upgrading CCA Grid Node on Linux or UNIX › Edit Database Properties

Edit Database Properties

If you need to edit any of the database settings made during the CA Configuration Automation Server installation, edit the cca.properties file.

To edit database properties

1. Open the cca.properties file in a text editor.

   If you used the default installation directory, the file is located in the following location:

   • (Windows) C:\Program Files\CA\CCA Server\tomcat\conf
   • (Linux and UNIX) /opt/CA/CCAServer/tomcat/conf
2. Edit the value to the right of the equals sign (=) for one or more of the following properties, then save and close the file:

   db.server

   Specifies the server that hosts CA Configuration Automation Database.

   Default: localhost

   db.driver

   Specifies the database driver.

   Default:

   • (SQL Server) com.microsoft.sqlserver.jdbc.SQLServerDriver
   • (Oracle) oracle.jdbc.driver

   db.context

   Specifies the context of the database.

   Default:

   • (SQL Server) SQL_SERVER_CONTEXT
   • (Oracle)

   db.instance

   Specifies the named instance of the database.

   Default:

   • (SQL Server) MSSQLSERVER
   • (Oracle) ORA

   db.name

   Specifies the name of the database.

   Default: cca

   db.user

   Specifies the database administrator user.

   Default: cca

   db.password

   Specifies the database administrator's password. This encrypted entry must be changed if the database administrator's password changes.

   Note: You can edit this entry directly in the cca.properties file if you want to have the password stored in clear text and protected by file-level access security. If you want to encrypt the password, a utility to do so is included in the <CA Configuration Automation Server_install_directory>\bin directory. The file is called setDbPwd.sh (Linux or UNIX) or setDbPwd.bat (Windows). Run the utility from a command line, then enter and confirm the new password. The new, encrypted password is stored in the cca.properties file.

   db.port

   Specifies the listening port of the database.

   Default:

   • (SQL Server) 1433
   • (Oracle) 1521

   db.max_connections

   Specifies the maximum number of users who can be logged on to the database at one time.

   Default: 50

   db.deadlock_retry_delay_ms

   Specifies the time in milliseconds that the database waits before trying to resolve a resource deadlock.

   Default: 10000

   #db.max_idle_connections

   Specifies the maximum number of idle connections allowed by the database. You must remove the comment sign (#) to activate this property.

   Default: 5

   #db.max_wait_connection_ms

   Specifies the time in milliseconds that the database waits while trying to establish a connection. You must remove the comment sign (#) to activate this property.

   Default: 60000

   #db.min_idle_eviction_ms

   Specifies the time in milliseconds that the database waits before terminating an idle connection. You must remove the comment sign (#) to activate this property.

   Default: 15000

   #db.eviction_run_interval_ms

   Specifies the time in milliseconds that the database waits between connection eviction runs. You must remove the comment sign (#) to activate this property.

   Default: 15000

   The file is updated with your edits.

Resolving General Database Connection Issues

Many CA Configuration Automation Server installation problems are due to the inability to connect with the intended CA Configuration Automation Database server. Try the following solutions to resolve database creation and data loading issues:

• Ensure you have the correct database connection information, such as the following:
  • Database name or SID
  • Database user name and password
  • Database type
  • Database server name (try using fully qualified names or IP address)
• Verify that the port number is correct for your database server. Often databases run on a non-default port number. Check with your DBA to make sure you have the right port number for the server you are trying to access.
• Install a SQL client on your CA Configuration Automation Server and try to connect to the database server using the same user name and password as during the installation.
• If you are using the SA or System user during the installation process, ensure your user has sufficient rights to complete the installation. If you are allowing the CA Configuration Automation Installer to create the database user and schema, the user must have DBA level rights to create users, tables, and schemas.
• Ensure you are using a supported database server application. CA Configuration Automation Server supports specific versions of Microsoft SQL Server and Oracle, and only on specific supported versions of operating system platforms. Check the CA Configuration Automation Release Notes for a list of the supported database applications and platforms.
• Ensure there is enough storage space. CA Configuration Automation requires a minimum of 400 MB to install properly. If the database instance or data space (depending on your database context) does not have enough allocated storage space, the table load scripts will fail.

Problems Loading Data: SQL Server Exception

Microsoft SQL Server does not always start properly when a server is started, restarted, or taken out of sleep mode.

If you attempt a Windows server installation without SQL Server being properly started, loading the data to the CA Configuration Automation Database displays the following exception error:

Exception: [Microsoft][SQLServer Driver for JDBC] Error establishing socket

Restart SQL Server, and try the CA Configuration Automation Server installation again.