Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 15 Oracle Analytics Lounge
- 208 Oracle Analytics News
- 41 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 76 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
bi_server1 - Stuck or Frozen While Starting Up After Migrating RCU?

Currently my company is using OBIEE 12.2.1.2.0
We are looking to move the RCU to another server.
I was able to find the following document outlining the steps needed
OBIEE 12c: How To Change Your OBIEE Connections When You Have Moved Your RCU Database To A New Host (Doc ID 2177562.1)
This document is divided into two sections
1) Installing New RCU Schemas in the New Oracle Database
2) Cloning the Database Where the Original RCU Schemas are Held to Move Them to a New Oracle Database
We basically went through the entire document, starting with installing new RCU schemas.
So we roughly
-Created new RCU schemas in our new target database
-Imported data from the noted tables
-Created new data source to new target database
-Ran the reassociateSecurityStore pointing to the new target database
-Went through the files listed - We actually only had 15 out of the 17 files noted, so we just changed what we had.
-Ran sync_midtier_db
We did this first on our sand box server (SNDBOX), and it was pretty straight forward and uneventful. We re-booted and everything seemed to be just fine.
We then moved on to our DEV environment and ran through the same steps.
But this time, when doing our final reboot of our server it looks like its getting stuck on "Starting bi_server1"
We are just using the start.sh script.
Node manager, and Admin server both seem to start up fine.
It just goes to "Starting bi_server1" and seems to freeze.
I'm quite sure its frozen as I was rebooting it right before I went home from work. Next morning when I came in it was still "stuck" on trying to start bi_server1.
I tried checking the log files but I dont see any immediate error messages.
I did try looking at a few log files, one of which included - bi_server1.out - But again I didnt see any immediate error messages.
I was wondering, has anyone else experienced a similar issue after migrating their OBIEE RCU schemas?
Are there any particular log files that I can try to look at? Not sure if there's a specific few I should focus on?
I apologize if I sound vague, its just that since it literally "froze" and does not appear to be even giving an error message Im not sure how best to trouble shoot
Thanks in advance for any help
Comments
-
You posted the exact same in MOSC.
As you mention a MOS document couldn't you just stick to the thread in MOSC?
While technically it's not 2 different forums compared to the old platform, it's still a kind of double posting...
0 -
My bad!
I actually am not too sure what the difference between the MOSC forums vs this forum - Hence wasnt aware it was a double post?
These two forums have always confused me as to which one to look at
0 -
FYI and just a quick update
I was able to finally find what the issue was - Apparently a very silly mistake.
In the MOS document I linked to earlier - In the section titled:
Installing New RCU Schemas In The New Oracle Database
There is a step where it states to bring data over from the old schema to the new target schema for these tables
BIEE_BIPLATFORM.S_NQ_DSS_SERVICE_STRIPES
BIEE_BIPLATFORM.N_NQ_SEARCH_CRAWL_CONFIG
BIEE_BIPLATFORM. S_NQ_DSS_IDENTITIES
I double checked the above specified tables and apparently the data was not there. I'm guessing some one maybe didnt COMMIT; after moving the data over 😋
But anyways - Once I brought the data over to these 3 tables from the old schema to the new schema - Everything booted right up as usual.
I did try to create a ticket to Oracle Support and also posted in the MOSC forums but didnt get any answers. I also dug through all the logs while we were having this issue and there was NO error messages that I was able to find which made this very hard to figure out. I dont think Oracle support really had an answer either. I will also update and close my other open threads
So it was a lucky thing I double checked these tables. But just wanted to post an update in case this helps someone else out there.
0