Skip to main content

Home/ BI-TAGS/ Group items tagged upgrade

Rss Feed Group items tagged

cezarovidiu

Rittman Mead Consulting » Blog Archive » Upgrading OBIEE to 11.1.1.7 - 0 views

  •  
    obiee upgrade 11.1.1.7
cezarovidiu

Planning to Upgrade from Oracle BI 10g to BI 11g - 11g Release 1 (11.1.1.7.0) - 0 views

  • ORACLE_HOME/bin/config.sh
  •  
    "1.7 Moving from 11.1.1.3, 11.1.1.5, or 11.1.1.6 to 11.1.1.7"
cezarovidiu

SugarCRM - Install Settings - 0 views

  • memory_limit - Recommended setting: 512M or higher. The memory_limit parameter mainly comes into play when executing large transactions such as mass update, export and import. If this setting is too low when trying to perform one of these actions, the end user will encounter a fatal error and the process will not complete. upload_max_filesize and post_max_size - Recommended setting: 30M or higher. Both of these settings work in conjunction with each other when uploading files through SugarCRM which includes future upgrades as well as document and note attachments. Please note that there is also a setting in the application which can limit file upload file size for end users so the settings in PHP should be high enough to allow any future upgrade files to be loaded without error. max_execution_time = Recommended setting: 300. This setting controls how long a PHP process will remain active. It is important to set this parameter to a value that will allow for large requests to complete if necessary but also will not hamper performance of the server if running too long.
  • In regards to PHP setup, the following parameters should be set with values as indicated:
  • Maximum upload size Admin > System Settings 30000000 (~30 MB) The 'Maximum upload size' controls the maximum file size your users can upload into Sugar. This setting should not exceed the post_max_size and upload_max_filesize parameters in your PHP configuration.
  •  
    "memory_limit"
cezarovidiu

Upgrading from 11.1.1.5 to 11.1.1.7 - 0 views

  •  
    "Login to OBIEE Presentation Services"
cezarovidiu

16.4.2. Replication Compatibility Between MySQL Versions - 0 views

  • MySQL supports replication from one major version to the next higher major version. For example, you can replicate from a master running MySQL 4.1 to a slave running MySQL 5.0, from a master running MySQL 5.0 to a slave running MySQL 5.1, and so on.
  • However, one may encounter difficulties when replicating from an older master to a newer slave if the master uses statements or relies on behavior no longer supported in the version of MySQL used on the slave. For example, in MySQL 5.5, CREATE TABLE ... SELECT statements are permitted to change tables other than the one being created, but are no longer allowed to do so in MySQL 5.6 (see Section 16.4.1.4, “Replication of CREATE TABLE ... SELECT Statements”).
  • Important It is strongly recommended to use the most recent release available within a given MySQL major version because replication (and other) capabilities are continually being improved. It is also recommended to upgrade masters and slaves that use early releases of a major version of MySQL to GA (production) releases when the latter become available for that major version.
1 - 9 of 9
Showing 20 items per page