The following tables appear to be new in 6.5.1.
Universe domains:
UNV_COLUMNS
UNV_OBJ_COLUMN
UNV_COLUMN_DATA
UNV_TABLE_DATA
UNV_OBJECT_KEY
UNV_JOIN_OBJECT
Security domain:
OBJ_M_USRATTRDoes anyone know what they are used for, or when they are populated?
Darren
daz1701d 
(BOB member since 2003-01-15)
There are a few new features in the release.
The OBJ_M_USRATTR table is used to hold the “Display Name” and “Mail Address” of the users
The others are related to changes that universes can now have. You can have derived tables in universes. You can also define primary and foreign keys. These tables deal with those features.
Steve Krandel 
(BOB member since 2002-06-25)
Thanks for that Steve. I’ll do a little digging with the Designer “What’s New” document, and see what I can get to populate.
Darren
daz1701d (BOB member since 2003-01-15)
OK, so far I have:
OBJ_M_USRATTR:
Holds display name and email address, which are entered through Supervisor.
UNV_TABLE_DATA
Holds SQL for derived tables.
UNV_OBJECT_KEY
Holds details of object keys defined in Designer.
UNV_JOIN_OBJECT
In Designer, when using ANSI92, and choose “Advanced” in Join Properties, then “Selected Objects In From”, the objects selected are populated in this table. Not actually sure what this could be used for!! 
Having gone through the “What’s New” info, I still cannot find what could be put into the following tables:
UNV_COLUMNS
UNV_OBJ_COLUMN
UNV_COLUMN_DATA
The things you do for DBAs when they want to know how much extra DB space to give you!! 
Darren
daz1701d (BOB member since 2003-01-15)
Thanks for contributing!
Cindy Clayton (BOB member since 2002-06-11)
UNV_COLUMNS table is provisional.
UNV_TABLE_DATA is for virtual tables.
UNV_OBJECTS_KEY contains relation between objects and their associated keys for Index aware operations.
UNV_JOIN_OBJECT contains data to improve query performance incase of outer joins.
UNV_OBJ_COLUMN and UNV_COLUMN_DATA is provisional.
Provisional means this is not used in this version but will be used in future.
dcdas (BOB member since 2002-06-17)
Durgesh,
Thanks for that. I was struggling with the provisional tables, as there is no mention anywhere as to what they are meant to be for.
Darren
daz1701d (BOB member since 2003-01-15)
Our upgrade also created
UNV_X_UNIVERSES
Any idea what this table is about?
Chris Pohl (BOB member since 2002-06-18)
I’ve done some research on this table. As you have probably found, this table is not mentioned in any of the documentation. So I turned to Tech Support. Here is what I found out.
That table is created during an upgrade from a previous version. If you do a brand new deployment of 6.5, you will not see this table. So what is in this table? It will contain existing universes (from previous versions), and will store them as BLOBs. Tech support wasn’t clear on the purpose of the table, but they have opened a RFI (Request for Information) in an attempt to find some additional documentation.
MichaelWelter 
(BOB member since 2002-08-08)
Create following table (script) in universe repository. we had two environments and one had this and and other does not had this table. This seems to work for us
CREATE TABLE UNV_X_UNIVERSES
(
UNIVERSE_ID NUMBER(10) NOT NULL,
UNI_N_FORMAT NUMBER(10) NOT NULL,
UNI_N_BLOCKID NUMBER(10) NOT NULL,
UNI_BLOB_CONTENT LONG RAW NOT NULL
)
TABLESPACE BOD
PCTUSED 40
PCTFREE 10
INITRANS 1
MAXTRANS 255
STORAGE (
INITIAL 2M
NEXT 2M
MINEXTENTS 1
MAXEXTENTS 2147483645
PCTINCREASE 0
FREELISTS 1
FREELIST GROUPS 1
BUFFER_POOL DEFAULT
)
LOGGING
NOCACHE
NOPARALLEL;
COMMENT ON TABLE UNV_X_UNIVERSES IS 'a universe in blob format';
CREATE UNIQUE INDEX X_UNIVERSES_PK ON UNV_X_UNIVERSES
(UNIVERSE_ID, UNI_N_FORMAT, UNI_N_BLOCKID)
LOGGING
TABLESPACE BOD
PCTFREE 10
INITRANS 2
MAXTRANS 255
STORAGE (
INITIAL 2M
NEXT 2M
MINEXTENTS 1
MAXEXTENTS 2147483645
PCTINCREASE 0
FREELISTS 1
FREELIST GROUPS 1
BUFFER_POOL DEFAULT
)
NOPARALLEL;mchoure 
(BOB member since 2003-09-04)