DOYENSYS Knowledge Portal




We Welcome you to visit our DOYENSYS KNOWLEDGE PORTAL : Doyensys Knowledge Portal




Wednesday, September 19, 2012

SQL*Loader-128: unable to begin a session , ORA-01017: invalid username/password; logon denied

Description :
=========

The Custom upload program which is using the sqlldr was running fine till yesterday and there was no changes made in the server. But all of the sudden the program is completing with the Error.


Checked the executable of that concurrent program and the executable was only the control file (.ctl) which has the normal parameters like the following

options (skip=1)

LOAD DATA
APPEND
INTO TABLE XXDOYEN_TEST_EXCEL_UPLD_CTL
FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"'

But it does not have any username and passwd to use the sqlldr , as that function takes care by the Executable Method : SQL*Loader. which is defined for the concurrent program.


Also we have tested by logging in to the server at the backend with the apps user and it works fine with the sqlldr. But when we are running this using concurrent request we are getting the following error message.

Version Details:
==========
Database : 11.0.7
Apps : 12.1.1
OS : IBM AIX 64 bit.

Error:

====

+-----------------------------
Starting concurrent program execution...
-----------------------------
Arguments
------------
/test02/apps/apps_st/appl/doyen/12.0.0/testing/CUSTOM/Saravana.csv

SQL*Loader-128: unable to begin a session

ORA-01017: invalid username/password; logon denied

SQL*Loader: Release 10.1.0.5.0 - Production on Wed Sep 19 10:42:17 2012

Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL*Loader-128: unable to begin a session
ORA-01017: invalid username/password; logon denied
Program exited with status 1
Concurrent Manager encountered an error while running SQL*Loader for your concurrent request 19779643.

Review your concurrent request log file for more detailed information.

Solution:

======

1. Just Bounce the concurrent managers and if possible please bounce the Apps and the db also. As there may be some block would have happend.

If the issue still persists then Conctact Oracle Support.

Wednesday, September 12, 2012

Relink of module "fndfmxit.so" failed

Scenario:


While applying the application patch end up with relink error.

Note : Issue Occurs in 12.0 and later versions

Error:

ld: 0711-851 SEVERE ERROR: Output file:
/test/apps/apps_st/appl/fnd/12.0.0/bin/fndfmxit.so
The file is in use and cannot be overwritten.
make: The error code from the last command is 12.
Stop.
Done with link of fnd executable 'fndfmxit.so' on Wed Sep 12 04:32:48
GMT+05:30 2012

Relink of module "fndfmxit.so" failed.
See error messages above (also recorded in log file) for possible
reasons for the failure. Also, please check that the Unix userid
running adrelink has read, write, and execute permissions
on the directory /test/apps/apps_st/appl/fnd/12.0.0/bin,
and that there is sufficient space remaining on the disk partition
containing your Oracle Applications installation.

Cause:

The issue is caused by the following: executables were used at the moment when
relink was performed

Solution:

1. Please stop all APPS services.
2. Retry patch. If is still failing please implement step 3.
3. Run (as root) slibclean command to clear unused shared libraries from memory.

Command to Run Just run this in db Tier
/usr/sbin/slibclean

4. Retry patch

Reference :

Relink Of Module "Fndfmxit.So" Failed. The file is in use and cannot be overwritten [ID 551208.1]

Monday, September 10, 2012

FRM-92050 : Failed to connect to the Server: /forms/lservlet-1


Scenario :
When we login to Oracle Application R12 we get the following error :
Note : Browser version used : IE 8
Error :
FRM-92050 : Failed to connect to the Server: /forms/lservlet-1
Problem:
The Problem is with the IE Version.
Solution:
1.      Open Internet Explorer
2.      Go to Tools -> Internet Options
3.      In that go to the Security Tab
4.      In the Bottom you can see the Custom Level
5.      Click on that.
6.      Now you can see the Enable XSS Filter.
7.      By Default it is Enabled. Now you Disable it.
8.      Now Give yes
9.      Now  retest the issue.