I have been able to further debug the issue. Using AppsDataSource instead of AppsXADataSource...
I am getting the below error: Exception breakpoint occurred at line 156 of AppsDataSource.java. java.lang.RuntimeException: ORA-20001: ORA-06512: at "APPS.APP_EXCEPTION", line 72 ORA-06512: at "APPS.FND_SECURITY_PKG", line 533 ORA-06512: at line 1 Exception in thread "main" java.lang.RuntimeException: ORA-20001: ORA-06512: at "APPS.APP_EXCEPTION", line 72 ORA-06512: at "APPS.FND_SECURITY_PKG", line 533 ORA-06512: at line 1
* at oracle.apps.fnd.security.AppsDataSource.setDbcFile(AppsDataSource.java:156)*
* at dstest.Test.init(Test.java:40)*
* at dstest.Test.main(Test.java:22)* ERROR: JDWP Unable to get JNI 1.2 environment, jvm->GetEnv() return code = -2
*JDWP exit error AGENT_ERROR_NO_JNI_ENV(183): [../../../src/share/back/util.c:820]*
I notice when I add breakpoints in the code it is hitting the exception when it's trying to invoke:
BEGIN fnd_security_pkg.fnd_encrypted_pwd_x(:1,:2,:3,:4,:5,:6,:7,:8); END;
This is where it throws the: SQLException
And it dumps the above message.
At this point, please put all this info in your existing SR and ask Support to log a bug for it. I don't think we can get any further on your particular issue in the forum, and development will need to look at it through the regular process.
Looks like, we fixed the issue. We are testing the fix. Please refer metalink ID 1514651.1. The FND profile option had the node name in lower case and it was changed to Upper case and the data source was created successfully.
Please check the option at your end. Hope this helps.
1. Creating a datasource using the Weblogic Server Console.
2. When doing a connection test after providing all datasource parameters, the following error occurs:
Connection test failed.
Message icon - Error ORA-01017: invalid username/password; logon denied
The profile option "FND: Desktop Nodes allowed" value is in lowercase.
The value of Profile Option "FND: Desktop Nodes allowed" needs to be in upper case as follows:
"FND: DESKTOP NODES ALLOWED"
We did not make the "Profile" change as stated in the previous thread response.
What we found to be our issue was this:
- Our DBC was generated using this format: XXX_OURNODE-123-SRV.OURDOMAIN.COM.dbc
It didn't like the fact that we had - and . in our DBC file and in the FND_NODES table.
We formatted it in this format XXX_OURNODE.dbc
We got past the DataSource issue but now when we run our Session Management code in the CustomPhaseListener we're getting the same issue others have with:
When validating the icx cookie it returns a cookie status of GUEST_VALID
Anyone have a suggestion on this?
Regardless whether we put the code to obtain the ICX Session Management in the ADF CustomPhaseListener or we use the standard J2EE servlet we have issues with the SESSION using the "GUEST" account instead of the user logging in. Even though the user has the ROLE - UMX|APPS_SCHEMA_CONNECT
xxx session.getUserId() - 6 (this is GUEST in our FND_USER table)
FIRST_CONNECT: 2013-02-18 13:22:21.0
LAST_CONNECT: 2013-02-18 13:22:21.0
<HomeServlet> <isAuthenticated> Icx session either has expired or is invalid
I faced the same issue, I was getting the apps session as NULL. As Sara mentioned, the domain names must be the same. The EBS domain(http://ebs.testdomain.com) and the domain name of the external node on which the ADF pages are hosted (http://host.testdomain.com) had to be same and we are getting the ICX cookie as VALID now. It might not be the same case with you, but that worked for us.
Glad to hear that you passed the .dbc file issue. We certainly will add those details into the MOS note. I think it would also help if you could share the code from you customPhaseListener to validate it against ours.