Skip to content

Archive for

No Oracle instances were discovered do you want to enter one

While try to configure Backup exec agent in database server

“No Oracle instances were discovered do you want to enter one”

Solution:

add the instance value in /etc/oratab

Advertisements

ORA-20001 FND_CANT_INSERT_USER_ROLE

I am getting below error message when I am trying to add Functional Administrator responsibility to sysadmin user.

Error :

ORA-20001 FND_CANT_INSERT_USER_ROLE (USERNAME=SYSADMIN)
(ROLENAME=FND_RESP|FND|FND_FUNC_ADMIN|STANDRARD)
(ROUTINE=FND_USER_RESP_GROUPS_API.Insert_Assignment)
has been detected in
FND_USER_RESP_GROUPS_API.INSERT_ASSIGNMENT

 

Solution :

If we trying to assign particular responsibility to user but we can’t and also It seems look like the user has been already assigned that responsibility but user can’t able to access that responsibility. To overcome this issue, there is a concurrent request that does sync up of such users and responsibility in R12 version.

Concurrent request :

Workflow Directory Services User/Role Validation  with parameters 10000, yes, yes, no

This request would check all users and assigned responsibilities and should sync up users with attached responsibilities , users should be able to view assigned responsibility now

workflow directory services

Diagnostic-Code: SMTP; 550 host unknown

When we’re trying to send mail to localdomain through mailx from linux box. It says “Diagnostic-Code: SMTP; 550 host unknown”  and mail not sent.

Solution :

Edit sendmail.cf

# “Smart” relay host (may be null)
DS[10.x.x.xx]

restart the sendmail service and send the mail is successful

10.x.x.xx — mailbox server

 

 

 

 

account analysis report OPP timeout error

While taking account analysis report one year time period, It was taking more time to finish the report completed with warning.

" +------------- 1) PUBLISH -------------+
Beginning post-processing of request 5011707 on node EBSUAT at 29-JAN-2015 14:50:32.
Post-processing of request 5011707 failed at 29-JAN-2015 14:57:32 with the error message:
The concurrent manager has timed out waiting for the Output Post-processor to finish this request.

Check that there are enough Output Post-processor service processes running.
More information may be found in the service process logfile. "

Solution :

Increase the OPP timeout parameter in profile

Concurrent:OPP Process Timeout –> 600

The timeout parameter depends on your report, So increase the size upto its complete normal.