Skip to main content

Oracle BI Scheduler Error: [nqSError:76015]

Image
By


Oracle BI Scheduler Error: [nqSError:76015]. The active Oracle BI Scheduler instance in the cluster could not be determined
This solution applies to Oracle Business Intelligence Server Enterprise Edition - Version 11.1.1.7 and later
The above error appears when a user is unable to save and edit an iBOT/Agent job
This is because the data source details are incorrect and not matching with the data connection from tnsnames.ora file
To resolve the error,
1.       Log in to Enterprise Manager
2.       Navigate to coreapplication
3.       Open the Deployment tab and navigate to scheduler
4.       Lock and Edit configuration
5.       Copy connection details from tnsnames.ora file
NB Don’t include the TNS alias, only copy the connection string after the equal (=) sign. Spaces are OK:
For example:
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=server.domain)(PORT=1521))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=orcl)))
Paste it under data source under scheduler tab
6.      Activate changes and then restart services to make changes visible.

Comments

Post a Comment

Popular posts from this blog

OBIEE 11g Error "Selected item is not of valid selection type" In Agent When Select Dashboard Page For Content

By
OBIEE 11g Error"Selected item is not of valid selection type" This error applies to OBIEE - version 11.1.1.7.0 and later . When you try to choose a dashboard page for delivery content in an agent, it constantly fails with the error message " Selected item is not of valid selection type ”.  Solution: This error may happen, when there is an added extra space after the end of the name of the dashboard page. For example, instead of "PAGE", it is "PAGE   "  It may happen with a space at the beginning of the name also. Removal of the extra space by renaming the dashboard page will correct the error.
9 comments
Read more

Setting User Defined JVM Memory Arguments in JDeveloper 11g Integrated WebLogic Server

By
Setting User Defined JVM Memory Arguments in JDeveloper 11g Integrated WebLogic Server This guide explains how to set your own predefined JVM memory arguments for the JDeveloper WebLogic container at startup for the integrated WebLogic server.   This will help avoid java.lang.OutOfMemoryError s experienced on heavy java processes and also improve on the integrated JDeveloper WebLogic server’s performance overall. Steps Locate the file: setDomainEnv.cmd which should be at: [JDeveloper Working Directory]\jdeveloper\system.xxx.xx.xx\DefaultDomain\bin                                 i.             Note: [JDeveloper Working Directory] will be "C:\Documents and Settings\<username>\Application...
3 comments
Read more