Managing Enterprise Deployments 10-7
Solution: This may happen when start parameters are changed for a server in the
Administration Console. In this case, provide user namepassword information in the server start configuration in the Administration Console for the specific server whose
configuration was being changed.
10.6.4 bi_server Managed Server Not Failed Over After Server Migration
Problem: After reaching the maximum restart attempts by local Node Manager, Node
Manager in the failover node tries to restart it, but the server does not come up. The server seems to be failed over as reported by Node Managers output information. The
VIP used by the bi_server Managed Server is not enabled in the failover node after Node Manager tries to migrate it if config in the failover node does not report the VIP
in any interface. Executing the command sudo ifconfig INTERFACE ADDRESS NETMASK does not enable the IP in the failover node.
Solution: The rights and configuration for sudo execution should not prompt for a
password. Verify the configuration of sudo with your system administrator so that sudo works without a password prompt.
10.6.5 bi_server Managed Server Not Reachable From Browser After Server Migration
Problem: Server migration is working bi_server Managed Server is restarted in the
failed over node, but the Virtual_Hostname:9704analytics URL cannot be accessed in the Web browser. The server has been killed in its original host and Node Manager
in the failover node reports that the VIP has been migrated and the server started. The VIP used by the bi_server Managed Server cannot be pinged from the clients node
that is, the node where the browser is being used.
Solution: The arping command executed by Node Manager to update ARP caches did
not broadcast the update properly. In this case, the node is not reachable to external nodes. Either update the nodemanager.properties file to include the MACBroadcast or
execute a manual arping:
sbinarping -b -q -c 3 -A -I INTERFACE ADDRESS NullDevice 21 Where INTERFACE is the network interface where the virtual IP is enabled and
ADDRESS is the virtual IP address.
10.6.6 OAM Configuration Tool Does Not Remove URLs
Problem: The OAM Configuration Tool has been used and a set of URLs was added to
the policies in Oracle Access Manager. One of multiple URLs had a typo. Executing the OAM Configuration Tool again with the correct URLs completes successfully;
however, when accessing Policy Manager, the incorrect URL is still there.
Solution: The OAM Configuration Tool only adds new URLs to existing policies when
executed with the same app_domain name. To remove a URL, use the Policy Manager Console in OAM. Log on to the Access Administration site for OAM, click My Policy
Domains, and then click the created policy domain bifoundation_domain. Click the Resources tab, and then remove the incorrect URLs.
10.6.7 Users Redirected to Login Screen After Activating Changes
