Categories
- All Categories
- Oracle Analytics Learning Hub
- 19 Oracle Analytics Sharing Center
- 17 Oracle Analytics Lounge
- 233 Oracle Analytics News
- 45 Oracle Analytics Videos
- 15.9K Oracle Analytics Forums
- 6.2K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 87 Oracle Analytics Trainings
- 15 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture
Issue Summary:OAS AdminServer Fails to Start — “Boot Identity Not Valid” and Schema Credential Sync
User_R95ZU
Rank 1 - Community Starter
Environment
- Product: Oracle Analytics Server (OAS)
- WebLogic Version: 12.2.1.4.0
- OS: Linux
- Domain Home:
/obie/oas/user_projects/domains/bi - Java Home:
/obie/Software/jdk1.8.0_441
When starting the OAS domain using:
./start.sh
the following error occurred during AdminServer startup:
Admin Server Start Exception: Error occurred while performing nmStart :Error Starting server AdminServer : Received error message from Node Manager Server:[Server start command for WebLogic server 'AdminServer' failed due to: [Server failed to start up but Node Manager was not aware of the reason]].
The Node Manager log confirmed repeated restarts:
Server failed during startup. It may be retried according to the auto restart configuration.Server failed but will not be restarted because the maximum number of restart attempts has been exceeded.
Review of AdminServer Logs
From /obie/oas/user_projects/domains/bi/servers/AdminServer/logs/AdminServer.log, the critical error found was:
<Critical> <Security> <BEA-090402> <Authentication denied: Boot identity not valid.The user name or password or both from the boot identity file (boot.properties) is not valid.The boot identity may have been changed since the boot identity file was created.
- Node Manager attempted to start AdminServer using these credentials but failed authentication.
- This caused the AdminServer to repeatedly enter a FAILED and FORCE_SHUTTING_DOWN state.
Additionally:
Startup config file .../data/nodemanager/startup.properties for server 'AdminServer' does not exist
showed the Node Manager was starting AdminServer using default parameters, not the correct configuration.
0