Creating SYSDATE value objects in a Universe (via Oracle connection) can simply be done as shown above.   I have simply created a single-value dimension object, which can be used anywhere within a query (result/condition/sort).  Having sysdate values allows the flexibility to create dynamic time-based reports.  For example you can schedule a weekly report to extract data from the past 7 days starting from the current time the report was run.

Note, when parsing the object against the database (Oracle), an error will appear. ORA-00903: Invalid table name.

You can just ignore this error and press ok.

Related Posts:

1. Oracle SQL Loader – Importing CSV files to a table
2. BusinessObjects – Delete Universes in CMC
3. BusinessObjects – Internal Error when connecting Windows clients

When deleting Universes in the Administrator Central Management Console (CMC), under a BOXIR2 Unix installation, i got the following error:

Error. Unable to reconnect to the CMS XXX:6400. The session has been logged off or has expired.

The solution is to make sure the timezone environment variable is set under the user’s Unix profile (the user which installed BO).

vi /opt/bo/.profile

Add the following example timezone and source the profile.

TZ=Australia/NSW export TZ
source /opt/bo/.profile

Then restart the BO servers.

Related Posts:

1. BusinessObjects – Internal Error when connecting Windows clients
2. BusinessObjects InfoView LDAP Authentication Error
3. BusinessObjects Universe Designer – Sysdate Value Object