Removing Credentials from a Cloned EBS Database
Thursday, June 25, 2009
During the post clone actions, changing the apps pasword went wrong. Because of that the applsys and apps password were not the same anymore. Trying to fix the problem using FNDCPASS was useless, FNDCPASS was not working anymore.
We saw 'APP-FND-02704: Unable to alter user APPS to change password.' in the log file. After trying it again, 'APP-FND-02704: Unable to alter user APPLSYS to change password.' appeared in the logfile. At t his moment both passwords could not be changed anymore using FNDCPASS.
The first thing we tried was restoring FND_USER and FND_ORACLE_USERID from our production database. Exporting the data from both tables and importing it in the cloned database did not solve the problem. This should work normally, but not if you have already run autoconfig....and we did before the passwords became out of sync.
Note 419475.1 from Metalink solved the problem. Resetting all passwords in the database (eBS and non eBS database users), did solve this !
Posted byBas Klaassen at 11:40 AM 0 comments
OEM problem solved...
Wednesday, April 29, 2009
The OEM problem with the http server not startign is solved. We solved the problem by installing an older version of the package libdb.so.2 (for Suse 10 install older version of 1_db).
After this the http server started and I was able to continue the install.
At the end of the install again a http error...
[Wed Apr 22 11:41:33 2009] [error] mod_ossl: Unknown error
[Wed Apr 22 11:41:37 2009] [error] mod_ossl: Init: Server oracle-grid-control.waterschapsgis.nl:1159: SSL setup failed: call to nzos_RetrievePersonaCopy returned error 28788
[Wed Apr 22 11:41:37 2009] [error] mod_ossl: Unknown error
I could not remember seeing this error before, but I found a sollution anyway. I solved it by adjusting the httpd_em.conf and changing the SSLWallet file and passsword. These values must be the same as in the ssl.conf file.
So, after some problemns I managed to install the OEM 10.2.0.1 on Suse 10 linux.
After this , I upgraded to OEM 10.2.0.5 (certified on Suse 10) and I upgraded the OEM repository to 10.2.0.4.
Now, the different targets can be configured for monitoring.
Posted byBas Klaassen at 10:19 AM 1 comments
OEM10gR2 install on Suse linux 10
Monday, April 20, 2009
I am facing a problem....
Again I am trying to install OEM10gR2 on SUSE LINUX 10.
I know it's not certified by Oracle, but I have to install it anyway. Everything seems to go fine, but when the installer wants to start the opmn services...it returns an error.
The HTTP_SERVER is not starting, the following error is in the logfile..
Cannot load /opt/oracle/product/oem/oms10g/Apache/Apache/libexec/mod_auth_dbm.so into server: /opt/oracle/product/oem/oms10g/Apache/Apache/libexec/mod_auth_dbm.so: undefined symbol: dbm_fetch
Posted byBas Klaassen at 1:43 PM 2 comments
Tracing web session in eBS
Monday, February 09, 2009
Because of a problem in Oracle Emailcenter I had to create a trace file of my web session.
Here are the steps taken :
This process can be used to trace any action, anywhere in Oracle Applications and be very useful for the Self-Service Web Applications as there is no utility defined like in the Forms.
a. First make sure the necessary profile has the proper permissions.
1. Log onto the Applications Forms with the Application Developer Responsibility
2. Navigate to the Profile menu
3. Query up the profile name "FND_INIT_SQL"
4. In the bottom block of the form, make sure that ALL checkboxes are checked Typically, you will have to enable the checkboxes under "User Access" to make it "Visible" and "Updatable".
b. Now switch to the System Administrator Responsibility
1. Navigate to - Profile - System
2. On the "Find System Profile Values" form, make sure the checkboxes for "User" and "Profiles with no Values" are checked
3. Beside the "User" checkbox, use the LOV to select the user who's activity you need to trace
4. In the "Profile" field, enter the following profile and click the
5. In the "System Profile Values" form, enter the following in the User Field: (This is one line and all single quotes)
begin fnd_ctl.fnd_sess_ctl('','','TRUE','TRUE','LOG','ALTER SESSION SET EVENTS=''10046 TRACE NAME CONTEXT FOREVER, LEVEL 12'' tracefile_identifier=''bklaassen'' max_dump_file_size=''unlimited'''); end;
6. DO NOT SAVE THE PROFILE YET
7. In another browser window, login as the user you are going to trace and prepare to reproduce the problem
8. Once you are ready to reproduce the problem, go back to the Applications Forms and Save the profile change
9. Reproduce the problem
10. Back in the Applications form, set profile to null so it does not trace anymore and Save the change
11. The trace will be located in the user_dump_dest. To find location run the following in SQL*Plus: select value from v$parameter where name = 'user_dump_dest';
12. The trace file will have current date/time and can be identified with the word bklaassen in it.
Note : for an example with screenshots of eBS follow this link :)
http://oracle-apps-dba.blogspot.com/2009/01/how-to-enable-trace-for-crm-session.html
Posted byBas Klaassen at 9:34 AM 2 comments
Oracle eBS and SOA session...
Tuesday, January 13, 2009
It is still two months ahead us, but I already signed up for this session. Amis is presenting the EBS and SOA session on 19 March. The session is located in Nieuwegein and is in dutch.
So, if you are living in the Netherlands and interested in eBS and SOA, check the Amis site !!
http://www.amis.nl/activiteiten.php?id=682&preview=&draft=
Posted byBas Klaassen at 9:45 AM 0 comments
Christmas 2008
Thursday, December 25, 2008
I want to wish everybody a merry X'mas and a very good 2009 !!!!
Posted byBas Klaassen at 9:55 AM 1 comments
Oracle Application Manager
Tuesday, December 09, 2008
We have a lot off forms users in out eBS environment. Because of this there are also a lot of forms sessions running for a long time. I use the Oracle Application Manager to check the current forms sessions and kill them when running for more then 10 hours
....
In OAM the forms sessions screen looks like this..
This print is taken from a test environment, but in the production environment you will see more forms sessions. Select a session and press the 'Sessions Details' button. On the next screen you will see the logon date and time, the session id, status and much more. Also you can kill the forms session.
Posted byBas Klaassen at 9:57 AM 0 comments
