There is only one universe in terminology of BO, but there 
may be many situations based on the usage, where we can 
classify the universes as-

1. Depending on type of data universe objects mapping

a.	Ad-hoc (personal data) – The Universe created for a 
personal usage is called Ad-hoc Universe and these are not 
shared with anybody else.
The reports created using these universes are called Ad-hoc 
Reports and generally users have the rights to store the 
reports in the Inbox. Ad-hoc reporting is a user friendly 
feature designed for all levels of users. Custom reports 
are created using queries.
b.	Non Ad-hoc (corporate data) – The universe created 
for a corporate usage is known as Non ad-hoc Universe these 
are sharable Universes and reports created from these can 
be viewed by all the users.

2. In linking universes scenario
a.	Core universe (Kernel or Master universe) – The 
Universe created and used with another universes for the 
reusability of the components.
b.	Derived universe – The Universe created using Core 
universe and there own required components.

3. Depending on universe parameters.
a.	Secured universe.
b.	Personal universe.
c.	Shared universe.

universes are 3 types : 1)simple universe
2)complex universe 3)dervied universe

 In metric universe aggregate summary is disable. so metric 
universe is not used
in simple uni while the aggregate summary is enable. and 
also it generates the summary.

at 3rd question i dont know.

By having multiple contexts you can utilize the 'multipass' 
sql feature. Multipass: Breaking one large SQL into 
multiple SQLs.If you are using the star schema with two or 
more fact tables,and you enable this feature, BO will 
automatically generate two or more SQLs (i.e. one SQL for 
each fact table object used in the report). Then the 
results will be synchronised in the report. For more on 
multipass concept please refer to Ralph Kimball's Lifecycle 
toolkit (not modelling)book.

Because it will be bit confusing for the users to select 
which context to use if they don't have the knowledge of 
how BO works

When a query is ambiguous, BusinessObjects or 
WebIntelligence displays a
dialog box that prompts the user to select one of two 
contexts. When the user
selects a context, the corresponding tables and joins are 
inserted into the SQL
query.

This should be resolved at universe level by selecting 
proper options in universe parameters>SQL>Multiple Paths

Aggregate Awareness is used to avoid having an object 
multiple times, in different classes, for the fact table 
and the aggregated table.

Aggregate tables are used in the schema in oreder to 
inprove the query performance.it is implemented  by using 
@aggregate_aware()function.these tables carries 
precalculated aggregates(measures).it will improve query 
performane,so we will get data fastly.refer this link to 
know more:
http://www.dwoptimize.com/2007/09/aggregate-awareness.html

Isolated join is the join which is not included in any of
your contexts, so
you are getting that error.

Solution :
First of all find what are all the joins you left with out
including in any
of your contexts and join them to any of the context which
you thnk
appropriate.
Then go for Integrity check.

hi

i think group values function,available in 6.5 but XIR2 is 
not available.

running the VB macro as full client report by invoking DeskI
using a batch file. This bat file can then be scheduled in
Infoview too. 

The batch file looks like this
Code:
"C:\Program Files\Business Objects\BusinessObjects
Enterprise 11.5\win32_x86\busobj.exe" -user "administrator"
-pass "passwd" -system "servername" -auth "enterprise"
-nologo -blind -document "C:\temp\VB_BOXI.rep"

This will invoke the DEskI application and run the .rep file
containing the macro. And it can be scheduled as program
object in CMC/Infoview.

Yes

if u know atleast need some knoweldge in universe design

yes, we can run the report without any knowledge of 
universe structure.

1) To migrate the bo 6.5 to XIR2:--

a) open the migration wizard 
b) select ur source location(Here give ur BO 6.5 doc)
c) click next
d) select ur destination location (ur BoXIR2 environment)
e) select the users or admin or specific users
f)click next
f) click ok

the above conditions will applied ur 6.5 document will 
migrated into ur boxir2 environment.

hi,
May i know what r the tools used for migration from 6.5 to XIR2.

hi,
May i know what r the tools used for migration from 6.5 to 
XIR2.


The tool used for Migration is "Import Wizard".
The tool used for Testing is "Report Comparision"
The tool used to convert DeskI reports to Web XIR2 
is "Report conversion"
ALL the tool guides are available in BO website

hi,
this is srinivas

2.....i think so many diffrences are there

1. 6.5 is three tier Architecture
and XIR2 is multi tier/Five tier architture

2. 6.5 is database concept/xir2 is file repository concept
3. this is corba atchitecture / xir2 service orient arch.
 and etc..

1... entirely different from xir2
6.5 profiles  are general supervisor
supervisor,designer,supervisor-designer,user,versatile user

xir2  in everything manage by cmc 

3..... 6.5 we can create repository that file stored by 
*.sdlc folder

xir2  when u r installed by defualt create by repository

we can migrate 60-70% of the universe

break removes duplictes.
and section  appears outside the grid.

Master-Detail report allows us to display the result in
Section wise. It splits large blocks of data into sections.
It minimizes the repeating values. We can have subtotals also.

Yes. It displays the data section wise. If you have the
following in a report, for e.g. Country, Store, Sales, you
can change it into a master detail report country wise by
dragging and dropping Country as a section when the cursor
shows the text 'Drop here to create a section' you can see
the data country wise.

Full Client reports are created using BO reporter which use 
BO two tier architechture however Thin Client reports are 
webi reports which are created using webintelligence and 
use BO 3 tier architechture to process.