ODI Agent Restart Failed: ODI-1405

Error:

ODI-1405 : Agent localagent; start failure: the agent is not defined in the topology.

Cause: 

Below command has been executed to restart the agent.

agent -NAME=localagent;

If you notice mistakenly this command has ";" at end. Here , ";" also considered as agent name. 

Resolution:

Remove the ";" from end and try to restart. It should work fine.

Enjoy and stay well !! :)

ODI Agent Restart Failed : ORA-12505

Sometime we used to get below error while restarting the ODI agent.

ORA-12505: TNS: Listener does not currently know of SID given in correct descriptor 

Please check whether Oracle Database is up an running or not. If DB is up and running , then we need to restart the DB service and listener too. Once you restarted the DB service and listener , then try to restart the ODI agent again. It should be up now.

Enjoy and Stay Well !! :)

Informatica Error :- REJECT: Forwarding output row to transformation !!

If we have used update strategy transformation with DD_REJECT comment and if "Forward Rejected Rows" property is enabled then we will get this kind of error. To avoid the same we need to disable the "Forward Rejected Rows" property in update strategy.

To do it please open property section of update strategy and un-check "Forward Rejected Rows" option.

Enjoy and stay well !! :)

OBIEE 11g: Create Users/Groups/Application Roles Using WLST Script

If AD is not integrated generally we create users manually and assign them to groups, application roles as per the security. Let’s try to create users using Weblogic scripts (WLS) instead of manual intervention.

1.      Navigate to below mention path:

$Oracle_BI1/common/bin

2.      Start up the Weblogic scripts(WLS) using the below command:

./wlst.sh

3.      Connect to weblogic server.

connect(“weblogic”,”Password″,”localhost:7001″)

4.      Get the DefaultAuthenticatorMBean using the following command

atnr=cmo.getSecurityConfiguration().getDefaultRealm().lookupAuthenticationProvider(“DefaultAuthenticator”)

5.      To create a new user.

atnr.createUser(‘sudipta’,’sudipta123’,’User Description’)

6.      To create a new group.

atnr.createGroup(‘SudiptaGroup’,’Group Description’)

7.      To assign user to group.

atnr.addMemberToGroup(group,user)

8.      To create a new Application Role.

createAppRole(“obi”,”SudiptaAppRole”)

9.      To assign user/group/application role to Application Role.

9.1  To assign user to Application Role

grantAppRole(“obi”,”sudipta”,”weblogic.security.principal.WLSUserImpl”,”Sudipta AppRole”)

9.2  To assign group to Application Role

grantAppRole(“obi”,”Sudipta Group”,”weblogic.security.principal.WLSGroupImpl”,”Sudipta AppRole”)

9.3  To assign Application Role to Application Role

grantAppRole(“obi”,”Sudipta AppRole”,”oracle.security.jps.service.policystore.ApplicationRole”,”Sudipta AppRole”)

10.  To list out the members of Application role.

listAppRoleMembers(“obi”,”Sudipta AppRole”)

Now once we will login to Weblogic Console& EM  page, we can see the user /group/application role are available.

Enjoy and stay well !! :)

OBIEE 11g (BI Scheduler) Error nQSError: 75005

This error generally will come if we have specified the username and password while configuring the mail server in EM page.

We can’t delete the username and password from this page directly. To remove this from here , we need to go to below  path,

Enterprise manager > Weblogic Domain > Right click on bifoundation_domain> Security > Credentials >oracle.bi.enterprise>mail.server

Delete the mail.server from here, it will automatically delete from the mail configuration page. Restart the BI services once.

Enjoy and stay well !! :)

Informatica Error: Repository Mismatch

After migration of Informatica repository from one environment to another environment (Like DEV to UAT server), when we will try to run the Workflow we usually get an error, like repository mismatch. Error will looks like as below:

This kind of error comes because even after repository migration, Integration service of UAT still pointing to DEV Integration service.You need to reassign the Integration service to UAT one.

To do the same you need to login to UAT Informatica Workflow  Manager. click on  Service -> Assign Integration Service.

Them just select all workflows and choose Integration service you want to assign.

Enjoy and Stay Well !!. :)

OBIEE 11g: Admin Server Restart Issue

Sometime we will get an error while restarting the BI server like, Admin server port is being used by another process, and because of this we won’t be able to restart the BI server.

There can be many reasons behind of this issue. Sometime Admin port or BI analytics ports are being blocked and Admin server is not able to access the same. Or sometime If someone is trying to access BI EM/Console/Analytics page during the restart of BI server, that time also we will end up with this kind of issue.

Anyway we can solve this issue by two different ways.

1.      We can restart the entire BI application server so that locked ports will be released and then try to restart the BI server, it should pass through.

2.      To avoid the application server restart we can kill the specific process where these ports are running on.

a.      To find the process ID (PID) for a specific port, type the below command on putty session.

                                                netstat -p -nlp|grep 7001

b.      Once you get the PID then kill the process using below command.

Kill -9 12306

c.       Now try to restart the BI server. Hope it will solve your issue.

Enjoy and stay well!! J