Forms inaccessible

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Forms inaccessible

latifa
Hi Erman,

customer is facing error like:

APP-FND-01516: Invalid Application username, password or database
Username Applsyspub
Database <DataBase SID>

I applied this DocId 1219833.1. It works once but failed next time.

Also I think that they are linked, we have a request failing with the error in the following file:

Request.log
The request is: XLAACCPB: Create Accounting

Even I made changes to default application language to American English, it works 1/2 time.

Any advise please.

Thanks in advance for help.

Regards,
Latifa
Reply | Threaded
Open this post in threaded view
|

Re: Forms inaccessible

ErmanArslansOracleBlog
Administrator
Hi Latifa,

Check this note ->

R12:AP/XLA: Create Accounting Program Returning With an Error - ORA-01017: invalid username/password (Doc ID 2186701.1)
Reply | Threaded
Open this post in threaded view
|

Re: Forms inaccessible

ErmanArslansOracleBlog
Administrator
The first error stack documented in that note, is just like your error stack.

Exception in static block of jtf.cache.CacheManager. Stack trace is: java.lang.ExceptionInInitializerError
at oracle.apps.jtf.base.resources.Architecture.createWebAppsContext(Architecture.java:441)
at oracle.apps.jtf.base.resources.Architecture.createAppsContext(Architecture.java:434)
at oracle.apps.jtf.base.resources.Architecture.createAppsContext(Architecture.java:343)
at oracle.apps.jtf.cache.ArchitectureWrapper.createAppsContext(ArchitectureWrapper.java:92)
at oracle.apps.jtf.cache.appsimpl.AppsCacheRuntime.getProfileValue(AppsCacheRuntime.java:807)
...

So consider implementing the solution provided in
"R12:AP/XLA: Create Accounting Program Returning With an Error - ORA-01017: invalid username/password (Doc ID 2186701.1) "
Reply | Threaded
Open this post in threaded view
|

Re: Forms inaccessible

latifa
Hi Erman,

Thank you very much for the DocId.

To solve this issue, we restarted all servers (with purging cache previously).

For the failing request, I'll tell you what I have done may be it contributed to the issue; So System engineers need to patch the servers so we should keep CM working. As they run all only on one server (charge repartition between servers not yet done). So I swithed all managers in the application menu to run on another server. I left only "internal Manager" to define in the moment to stop the server (to make it run on the other server like the other CMs). I think It wasn't a good idea !

What do you think Erman ? :)

NB:
- we have 3 OAS and 3 CMs.
- system engineers patched OAS2, OAS3, CM5 & CM6.
- it left OAS1 and CM4.

Regards,
Latifa