Data Guard Configuration applicable for Entire setup of the Data Guard Configuration - which is a mix of one primary database and multiple standby databases.
If you want to setup Data Guard Configuration for another database - Yes it is very much possible.
You have mentioned few errors while creating a configuration, can you share error messages?
I'm getting error ORA-16698: LOG_ARCHIVE_DEST_n parameter set for object to be added.
I set my log_archive_dest_3 = '' scope=spfile on both Primary database and standby database. I've verified both are set by creating a pfile from spfile and looking at the parameters .
My assumption was that since I had another database already running a broker configuration that this was causing the issue. I say that because I had to set my log_archive_dest_3 ='' on all my databases (database X and database Y) to get my first broker configuration to work. I wasn't sure why I had to do this, but I had to.
The answer is yet, you can have multiple primary databases and multiple configurations.
My issue above as that the broker automatically creates a service in log_archive_dest_2. (I think it created it from failed previous attempts).
It wasn't that another database had the log_archive_dest_n set, it was that Oracle creates this and I didn't see it because I was looking at log_archive_dest_3
Here is how I set up my Broker configs: DG Broker – Why and How?
Also this can be beneficial: DG Broker Primer
Now I have BACKOFFICE databases running on the same primary server and want to have another broker configuration
You can't do that. You can only have one broker configuration. The singular broker config will handle one primary and multiple standby databases.
Here the requirement was for two distinct Primaries. So, each Primary has its own DataGuard Configuration (separate configuration files) even if they are on the same server.
Hemant K Chitale
I see...that you can do. You don't have to do anything different. Just set up each DG Broker as if it were the only one on the server. Note that each primary has it's own DG Broker. You can't have a single DG Broker manage multiple primary dbs.