After changing the Admin Server to run in Node 2 from Node 1 ..getting 500 internal server error in EM console

Issue Changed the Admin server to run in Node2 instead of Node 1 . Though /em application is in Active state .not able to access EM console . Cause: sysman folder is not present in Node2 .(in the location /u01da/MW_Home/user_projects/domains/SOA_Domain/) Solution Copied the sysman folder from Node 1 to Node 2 . Chagned the server name to node2server instead of node1server in targets.xml restart the application em and click on update for the application em .. it started working !!!

StartWebLogic.cmd Shuts Down after Entering Username with the Error: "Server is running in Production Mode and Native Library (terminalio) to read the password securely from commandline is not found." (Doc ID 1354736.1

YMPTOMS After creating the WebLogic Domain for Contract Management, installing Contract Management and modifying the StartWebLogic.cmd and SetDomainENV.cmd file, the StartWebLogic.cmd file shuts down or closes after typing a username and pressing the ENTER key. The following error is listed in the StartWebLogic command prompt window prior to the shutdown completing: Server is running in Production Mode and Native Library (terminalio) to read the password securely from commandline is not found. CAUSE There are two possible causes: The terminalio.dll file is missing from the default location: C:\bea\middleware\wlserver_10.3\server\native\win\32 The terminalio.dll filing is being renamed to terminalio.dll.bak when the StartWeblogic.cmd file is started. This is a known issue that has been reported to Oracle in Bug 8002166. SOLUTION To resolve this issue, open the StartWebLogic.cmd file with Notepad and do the following: Located towards the bottom of the file are the following lines: if "%WLS_REDIRECT_LOG%"=="" ( echo Starting WLS with line: echo %JAVA_HOME%\bin\java %JAVA_VM% %MEM_ARGS% -Dweblogic.Name=%SERVER_NAME% -Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy %JAVA_OPTIONS% %PROXY_SETTINGS% %SERVER_CLASS% %JAVA_HOME%\bin\java %JAVA_VM% %MEM_ARGS% -Dweblogic.Name=%SERVER_NAME% -Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy %JAVA_OPTIONS% %PROXY_SETTINGS% %SERVER_CLASS% ) else ( echo Redirecting output from WLS window to %WLS_REDIRECT_LOG% %JAVA_HOME%\bin\java %JAVA_VM% %MEM_ARGS% -Dweblogic.Name=%SERVER_NAME% -Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy %JAVA_OPTIONS% %PROXY_SETTINGS% %SERVER_CLASS% >"%WLS_REDIRECT_LOG%" 2>&1 ) Change them by including the following line directly before %JAVA_OPTIONS%: -Dweblogic.management.allowPasswordEcho=true The changed information should now appear as: if "%WLS_REDIRECT_LOG%"=="" ( echo Starting WLS with line: echo %JAVA_HOME%\bin\java %JAVA_VM% %MEM_ARGS% -Dweblogic.Name=%SERVER_NAME% -Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy -Dweblogic.management.allowPasswordEcho=true %JAVA_OPTIONS% %PROXY_SETTINGS% %SERVER_CLASS% %JAVA_HOME%\bin\java %JAVA_VM% %MEM_ARGS% -Dweblogic.Name=%SERVER_NAME% -Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy -Dweblogic.management.allowPasswordEcho=true %JAVA_OPTIONS% %PROXY_SETTINGS% %SERVER_CLASS% ) else ( echo Redirecting output from WLS window to %WLS_REDIRECT_LOG% %JAVA_HOME%\bin\java %JAVA_VM% %MEM_ARGS% -Dweblogic.Name=%SERVER_NAME% -Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy -Dweblogic.management.allowPasswordEcho=true %JAVA_OPTIONS% %PROXY_SETTINGS% %SERVER_CLASS% >"%WLS_REDIRECT_LOG%" 2>&1 ) Be sure to leave a space before and after the line that was just added. Save the changes and then restart StartWebLogic.cmd.

Refresh GUID’s after moving new RPD & Catalog

Refresh GUID’s after moving new RPD & Catalog Posted on September 6, 2012 by pradeep28186@gmail.com In OBIEE 11g , when we load new RPD and Catalog we need to refresh the user GUID’s else we get error at analytics log in. To resolve this error we have to manually edit the configuration files to instruct Oracle BI Server and Oracle BI Presentation Server to refresh the GUIDs on restart. Follow below steps, 1. Open the NQSconfig.ini file 2.Locate the parameter FMW_UPDATE_ROLE_AND_USER_REF_GUIDS = NO ; change it toYES. 3.Open the instance config.xml file for editing, find out false then comment the and add like below example false UpdateAndExit save the changes in instance config.xml 4.Then using omnctl command restart the services ex. C:\middleware\instances\instance1\bin>opmnctl stopall C:\middleware\instances\instance1\bin>opmnctl startall 5.After restarting of services, revert the changes. i.e. in NQSconfig.ini resetFMW_UPDATE_ROLE_AND_USER_REF_GUIDS = NO ; & in instance config.xml comment & uncomment like false UpdateAndExit 6.Restart the services again using opmnctl command. http://pradeep28186.blog.com/2012/09/06/refresh-guids-after-moving-new-rpd-catalog/