One database per BSO application is recommended because of the below reasons. We need to understand that essbase logs messages at application level. It doesn't log the processes at database level
1. If multiple databases are present in a single application all the databases log is spooled in to a single log file and
is difficult to spill out a particular database log.
2. If a user terminates or kills one application process, all the databases will be unavailable in that particular application
Now a Planning resource guys lifts his hand up and says, How come we have 3 plan types in Planning which creates 3 different database in a single Essbase application. Coming to that point, We do have some exceptions of this rule for Planning and Currency applications.
1. If multiple databases are present in a single application all the databases log is spooled in to a single log file and
is difficult to spill out a particular database log.
2. If a user terminates or kills one application process, all the databases will be unavailable in that particular application
Now a Planning resource guys lifts his hand up and says, How come we have 3 plan types in Planning which creates 3 different database in a single Essbase application. Coming to that point, We do have some exceptions of this rule for Planning and Currency applications.