I have an odd question for you. Any help would be greatly appreciated. We are running Business Objects 5.0.2 on a SYBASE System 11 Repository. The name of our repository database is BOREP and we have our Document and Universe Domains, named Document and Universe, located in this database.
We would like to have 4 new domains, DEV_Document, DEV_Universe, BETA_Document, and BETA_Universe. To do this, I had my dba’s create 2 new databases BOREP_BETA and BOREP_DEV. I am able to add the BETA_DOCUMENT and BETA_Universe domains without any problems. But, when I attempt to add the DEV_Document and DEV_Universe domains, using a separate connection to BOREP_DEV, I receive the following error message:
A repository domain of that type already exists for the connection. Please change the type or set up a new connection.
This is a separate connection from the other two, BOREP and BOREP_BETA. I am also using totally different names for the domains.
Anyone with any ideas? I’m in a bit of a time crunch on getting these out.
I don’t know about SYBASE but in Oracle you should use a different username and password for your both connections, ask your DBA to create a new user for your BOREP_DEV connection with write permission.
Hamid is probably right, you need to use different user accounts or (if it would let you) BO would overwrite the existing obj_ tables…
I have a set of users, prod, dev, and cert that are the owners of my 3 domains (univ and doc), works pretty well
Brent
Hi Listers
I have an odd question for you. Any help would be greatly appreciated. We are
running Business Objects 5.0.2 on a SYBASE System 11 Repository. The name of
our repository database is BOREP and we have our Document and Universe Domains,
named Document and Universe, located in this database.
We would like to have 4 new domains, DEV_Document, DEV_Universe, BETA_Document,
and BETA_Universe. To do this, I had my dba’s create 2 new databases
BOREP_BETA and BOREP_DEV. I am able to add the BETA_DOCUMENT and BETA_Universe
domains without any problems. But, when I attempt to add the DEV_Document and
DEV_Universe domains, using a separate connection to BOREP_DEV, I receive the
following error message:
A repository domain of that type already exists for the connection. Please
change the type or set up a new connection.
This is a separate connection from the other two, BOREP and BOREP_BETA. I am
also using totally different names for the domains.
Anyone with any ideas? I’m in a bit of a time crunch on getting these out.
I’m sure about terminology in Sybase, but we have multiple domains in our setup.
On Oracle we have an instance (database) that we use for the security, universe and document domains.
We have separate schemas (users) for development, testing and production. Each schema (user) has one universe domain and one document domain.
Now, initially we only had one schema - used for development through production. When we added the extra schemas and tried to set up new domains we got some errors similar to yours. These were because there were some public synonyms floating around pointing to the existing repository tables. Thus when we tried to create a new table under the new schema, BO detected the synonym for that table and blew a gasket.
I don’t know if there are synonyms in Sybase, but it’s worth connecting to your BOREP_DEV schema and seeing if there is a sysonym (or whatever) pointing to BOREP_BETA or BOREP.
No, we don’t have any synonyms. I had my DBA delete the BOREP_DEV database and recreate it. It now works (don’t know why) and all three of my databases, BOREP, BOREP_DEV, and BOREP_BETA, have the same username & password.
Can you send us the connection strings, the ones you have and the ones that wont go?
Also, in oracle the different users would get different schema, like different directories (forgive me if I am being to basic here) - is sybase similar? It really sounds like the files that would be created are going over top of something else…
Brent
Hi
I had my dba change the owner name and it still doesn’t work.
Sybase is different. In Oracle, a “user account” has one and only one schema. In Sybase, a “user account” can have multiple schemas (referred to as “databases” in Sybase terminology). In Oracle, the “database” is the same thing as the “instance”.
Basically (this is oversimplified for clarity), the methodologies are reversed. In Oracle, you have an instance (database), which has multiple users (schemas). In Sybase, you have a user which can have multiple databases.
My guess was that when it failed the first time, the user account on the Sybase server was set to use a default database, which was the database where the previous universe and document domains were residing. The DBA probably reconfigured to not have a default database, so that it would be required to have the database name be specified at connect time. I have encountered situations where even if a database name is specified, and it was different than the default database, Sybase will point you to the default anyway.
Hope that helps, from a theoretical standpoint anyway.
I concur with Paul. This is why whenever you set up a user account to a Sybase database, especially post 11.5.x, you should ensure that the default database has no relationship to either the repository domain/s and/or the data sources (we’re currently using the Xfer database system tables as our default). This will ensure that the user is always connecting to and retrieving data from the correct database.
For example. If you have DEV, TEST and PROD versions of the same database, and universes over them, if your default database is PROD, the DEV database is down, and you connect to retrieve data off the DEV database, you will NOT get an error reported through BusinessObjects and the SQL will run against the default PROD database. The only time you’ll get an error is if the SQL cannot find a table / column. This is because Sybase is “smart” and will always attempt to connect you to something. At connection time it reports the database, however this information is seemless to the BusinessObjects user.