Skip to main content

Home/ BI-TAGS/ Group items tagged cache

Rss Feed Group items tagged

cezarovidiu

OBIEE 11G configuration's Maximum Limits | OBIEE by Shiva Molabanti - 0 views

  • OBIEE 11G configuration’s Maximum Limits
  • Be careful when you are setting the Cache attribute values. For implementations under significant stress increase this value to 1000 or a higher value as mentioned below. The main factor that affects its size is the memory consumption. Maximum range of Global Cache storage size (in Megabytes) to use when BI Server cache is enabled – 9,999 Maximum number of cache entries; used to tune cache performance – 99,999 Maximum size (in Megabytes) for individual server cache entries – 9,999 Data Display/Download: The Maximum no.of rows that we can set to display/download in the Table/Pivot views. But keep in mind OBIEE is NOT meant to be a tool to extract huge amounts of information. Maximum number of rows of data to include in Table views – 9,999,999 Maximum number of rows of data to include in delivered emails – 9,999,999 Maximum number of rows to export to excel – 9,999,999
  • In OBIEE 11G, The instanceconfig.xml file stores the OBI PS configuration settings. Many configuration settings are available in EM and those should be controlled within EM only unless if we disabled centralConfigurationEnabled option. If any particular setting is not available in EM then we should make changes directly in instanceconfig.xml file. There are many situations where we need to change the default OBI configuration settings to a new value.
cezarovidiu

OBIEE - Clear Cache -SAPurgeAllCache() - 0 views

  •  
    "OBIEE - Clear Cache -SAPurgeAllCache()"
cezarovidiu

What Skills Does an Oracle BI Developer Need in 2011? - 0 views

  • OBIEE 11g skills, both in terms of new functionality (mapping, analyses, KPIs and Scorecards etc) and new infrastructure (WebLogic, EM, OPSS etc) A smattering of Essbase skills, focused mainly on the integration with OBIEE and Essbase (and the many workarounds and gotchas) Good ODI skills, both in terms of the basics, but also being able to write knowledge modules, integrate with OBIEE, deployment and migration Solid database skills – OBIEE gave the illusion through aggregates etc that database tuning was redundant, but time has shown it’s by far the biggest success factor in a project – get the database design and optimisation wrong, and your project is toast. You need to know partitioning, materialized views, index types, and increasingly, you need to get yourself on an Exadata project as customers are buying the technology but you can’t teach it to yourself at home BI Apps skills, but watch out for everything changing when BI Apps 11g comes out, and be prepared to learn the Fusion Apps and JDeveloper if you want to stay in the game Looking to the future, keep an eye on technologies such as in-memory (TimesTen), mid-tier caching (Coherence), plus technologies such as Business Activity Monitoring (BAM), “big data” (Hadoop, large data sets, NoSQL), complex event processing and maybe products such as Qlikview, just in case Oracle buys them, or at least to know what the competition are up to, or more importantly pitching to your boss
  • The other thing to bear in mind of course, if you’re an Oracle BI developer, is that you need to have great business, communication and data modeling skills.
cezarovidiu

Moving Sugar to Another Server - SugarCRM Support Site - 0 views

    • cezarovidiu
       
      japtone   Senior Member Join Date Nov 2010 Posts 49  Re: Transferring SugarCRM to a new server If you're using Linux try to have the same version of PHP, Apache, and DB (MySQL for instance) in order to avoid compatibility issues. In your production server tar up the sugarcrm root directory, transfer it to the new server and untar wherever your new root directory will be.  Next take a db dump of your database, transfer it to the new server and do a restore. Make sure apache is configured on the new server to point to the root of sugarcrm and start it up.  Make sure to modify config.php to account for any change in paths and hostname.  that's what I've found to be the easiest way to 'clone' sugar.
  • mysqldump -h localhost -u [MySQL user, e.g. root] -p[database password] -c --add-drop-table --add-locks --all --quick --lock-tables [name of the database] > sqldump.sql
  • Extract the Database
  • ...5 more annotations...
  • Copy Filesystem Copy all your files to the new server.  This can be done simply by locating the root directory on your old instance and copy and pasting it to the new server location.
  • Import Database Import the mysql database into the new server.  Here's how you would restore your custback.sql file to the Customers database. mysql -u sadmin -p pass21 Customers < custback.sql Here's the general format you would follow: mysql -u [username] -p [password] [database_to_restore] < [backupfile]
  • Check Files and Permissions Check Config.php Open <sugarroot/config.php> and make sure that all settings still apply to the new server, such as: array ( 'db_host_name' => 'localhost', 'db_user_name' => 'root', 'db_password' => 'PASSWORD', 'db_name' => 'DATABASE_NAME', 'db_type' => 'mysql', ), 'site_url' =>, etc...
  • Check htaccess Open <sugarroot/.htaccess> and ensure that the new server URLs are used correctly.
  • Check Permissions Check that the permissions are correct on the new server. That is the entire custom and cache directories (and all the sub directories) in addition to the config.php file are owned and writable by the user that runs the application on the server.
1 - 6 of 6
Showing 20 items per page