Invalid User name and password OBIEE 11g (Analytics)

When trying to Access to the URL:// hostname:9704/analytics with username weblogic the below error generated in the Adminserver logs :-

java.security.AccessControlException: access denied (oracle.security.jps.service.credstore.CredentialAccessPermission context=SYSTEM,mapName=oracle.bi.system,keyName=system.user read)
at java.security.AccessControlContext.checkPermission(AccessControlContext.java:374)
at java.security.AccessController.checkPermission(AccessController.java:546)
at oracle.security.jps.util.JpsAuth$AuthorizationMechanism$3.checkPermission(JpsAuth.java:463)
at oracle.security.jps.util.JpsAuth.checkPermission(JpsAuth.java:523)
at oracle.security.jps.util.JpsAuth.checkPermission(JpsAuth.java:549)
at oracle.security.jps.internal.credstore.util.CsfUtil.checkPermission(CsfUtil.java:684)
at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.getCredential(SspCredentialStore.java:562)
at oracle.bi.security.opss.CredentialReader.getPasswordCredential(CredentialReader.java:69)
at oracle.bi.security.opss.CredentialReader.getPasswordCredential(CredentialReader.java:57)
at oracle.bi.security.service.SystemUserValidator$ReadSystemUserCredentialsAction.run(SystemUserValidator.java:291)
at oracle.bi.security.service.SystemUserValidator$ReadSystemUserCredentialsAction.run(SystemUserValidator.java:278)
at oracle.bi.security.service.SystemUserValidator.readSystemUserCredential(SystemUserValidator.java:186)
at oracle.bi.security.service.SystemUserValidator.validateSystemUserCredentials(SystemUserValidator.java:146)
at oracle.bi.security.service.SystemUserValidator.access$000(SystemUserValidator.java:26)
at oracle.bi.security.service.SystemUserValidator$1.run(SystemUserValidator.java:107)
at oracle.bi.security.service.SystemUserValidator$1.run(SystemUserValidator.java:101)
at oracle.bi.security.service.SystemUserValidator.validate(SystemUserValidator.java:117)
at oracle.bi.security.service.SecurityServiceBean.initialise(SecurityServiceBean.java:89)
at oracle.bi.security.service.SecurityServiceBean.getAuthenticatedUserWithLanguageAndProperties(SecurityServiceBean.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

If you recive the above error, you don’t have permission to access to the analytics, permission saved  in Files called

system-jazn-data.xml

Located :-

 $DOMAIN_HOME/config/fmwconfig

Edit the files and add these lines :-

   

Or copy this file from another OBIEE Environment after backup the old one, and restart AdminServer and managed Server

Thank you
Osama Mustafa

java.lang.ClassNotFoundException: oracle.dms.wls.DMSServletFilter

This Error Appeared while trying to start managed Server “edq_server1” , The starting results it’s completed with successfully status but some deployment end with Failed status , which mean edq_server will not work correctly, therefore i checked the logs which the below error :-

Caused By: java.lang.ClassNotFoundException: oracle.dms.wls.DMSServletFilter
        at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
        at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
        at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
        at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
        at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43)
        at weblogic.servlet.internal.WebComponentContributor.getNewInstance(WebComponentContributor.java:224)

To solve this error :-

cd /u01/app/oracle/product/fmw/wlserver_10.3/common/nodemanager
vi nodemanager.properties

And search for 

StartScriptEnabled=false

change it to

StartScriptEnabled=true

Restart Node manager and try again.
Thank you
Osama Mustafa

Change AdminServer Port Using WLST.SH

Sometimes AdminServer not working Regarding to Wrong configuration or using Wrong Port which mean No Console will be available so is this mean delete domain and Configure it again !!!

Absolutely  Not  When you install Weblogic any Version Oracle Provide you with Command Line Utility to administrate weblogic, what you can do it using Console can be done with this tool.

change to weblogic-directory/common/bin
./wlst.sh

Now follow the below Steps to change port :

wls:/offline> readDomain (‘/u01/app/fmw/domains/IDDomains’)
wls:/offline/IDDomains> cd (‘Server’)
wls:/offline/IDDomains/Server> ls ()

Choose your Server Here

wls:/offline/IDDomains/Server> cd (‘AdminServer’)
wls:/offline/IDDomains/Server/AdminServer> ls ()

Search for Old Port ListenPort 

wls:/offline/IDDomains/Server/AdminServer> set (‘ListenPort’,New Port)
wls:/offline/IDDomains/Server/AdminServer> updateDomain ()
wls:/offline/IDDomains/Server/AdminServer> exit () 

Done you can now Test your new port
http://Server-ip:/console


Thank you
Osama Mustafa 

Failed to create secure socket for OPMN at LocalHost:9501

The Below Error Appear when you enter to the following URL :  http://LocalHost:9704/analytics

oracle.as.management.opmn.optic.OpticBadConnectException: Failed to create secure socket for OPMN

Change Directory to the to BI instance/Bin Folder and :

[oracle@exalytic bin]$ ./opmnctl stopall
opmnctl stopall: opmn is not running.

[oracle@exalytic bin]$ ./opmnctl startall
opmnctl startall: starting opmn and all managed processes…

[oracle@exalytic bin]$ ./opmnctl status
Processes in Instance: obiee1
———————————+——————–+———+———
ias-component                    | process-type       |     pid | status
———————————+——————–+———+———
coreapplication_obiccs1          | OracleBIClusterCo~ |   19837 | Alive  
coreapplication_obisch1          | OracleBIScheduler~ |       0 | NONE  
coreapplication_obijh1           | OracleBIJavaHostC~ |   19836 | Alive  
coreapplication_obips1           | OracleBIPresentat~ |   19840 | Alive  
coreapplication_obis1            | OracleBIServerCom~ |   19838 | Alive  

Thank you
Osama Mustafa 

unpack.sh Error -name=Value

The pack command creates a template archive (.jar) file that contains a snapshot of either an entire domain or a subset of a domain. You can use a template that contains a subset of a domain to create a Managed Server domain directory hierarchy on a remote machine.

The unpack command Creates a full domain or a subset of a domain used for a Managed Server domain directory on a remote machine. You may use unpack only with a template compatible with your current installation. The template can be any of the following:

  •  A domain template provided by BEA and packaged with your current installation
  •  A domain template created using the Domain Template Builder or WLST Offline
  •  A domain template created using the pack command
  •  A Managed Server template created using the pack command. A Managed Server template, by default, contains only the files necessary for creating a Managed Server domain directory.
You Can Check Oracle Documentation here for more information about the above commands.
When Trying to use unpack command with the below command:

./unpack.sh -domain=/u01/app/oracle/domains/IDMDomains -template=/u01/shared/IDMdomains.jar

The below error appear :

ERROR !!! ./unpack.sh -name=Value Missing

The Solution is simple :

-template attribute should come first. 

./unpack.sh  -template=/u01/shared/IDMdomains.jar -domain=/u01/app/oracle/domains/IDMDomains

Thank you
Osama Mustafa

Start Managed Server Failed With "Access not allowed for subject: principals=[]"

When Trying to Start Managed Server From Admin Console it’s Failed with

weblogic.management.NoAccessRuntimeException: Access not allowed for subject: principals=[], on ResourceType: Application Action: write, Target: Deployed”

After Check Everything and Configuration i found the following :

  • My Admin Server Already have More than one managed Server : SOA, ODI , BAM.
  • SOA and ODI Using the Same Port which is 8001 Which caused Conflict.

I Changed SOA Port to Work On 8003 From Admin Server Console. Like the Below