Oracle Fusion Applications: December 2012

Friday, December 7, 2012

Loading RPD File in Fusion Applications

LOADING RPD IN FUSION APPLICATIONS [OTBI]

We can open the Rpd's in the online mode as well as offline mode .. If we need to open the rpd's in offline mode then we need to copy the rpd's from the Server to the local machine where the admin tool is located .. after making the necessary change in the RPD then we need to upload the RPD 's to the server by using the EM of the Bi Domain

Step 1

Login into the Bi Domains Enterprise manager

http://biinternal.<domainname>:10621/em

Step 2

Select the Coreapplication from Business Intelligence Folder which is located under the Farm_BIDomain and select the deployment tap and repository

Step 3

Lock and edit the configuration to enable the changes in the configuration and load the repository

Step 4

Choose the repository from the location by clicking the browse button under the upload bi server repository and provide the Rpd's password And click apply to upload the Rpd

Step 5

Click the apply button to upload the new repository in the server

Step 6

Click the activate changes tab for saving the new rpd

Step 7

Restart the servers [click the restart to apply recent changes ] in the top for Restarting the server]

Step 8

click restart button to restart all the services belonging to this managed server

Click yes to proceed for restart

Step 9

Check the repository version now u can find the new version of rpd had been uploaded in the server

Wednesday, December 5, 2012

Error 1053010 Object [db] is already locked by use

Error(1053010) @ Object [db] is already locked by user

When the all the Essbase Object in the db is locked then the connections made to the particular cube will not be accepted and it will throw the error we need to unlock all the objects in the db

When the db is locked we cant insert into the particular db so when we run nay process in the fusion applications then the process may end up in the error

When the Db is locked then we will get this kind of error messages

Mon Nov 19 15:07:42 2012]Local/ESSBASE0///1111554368/Info(1051001)@ Received client request: Lock Object (from user @ [FUSION_APPS_GL_ESSBASE_APPID])

Mon Nov 19 15:07:42 2012]Local/ESSBASE0///1111554368/Error(1053010)@ Object [db] is already locked by user [FAADMIN]

[Mon Nov 19 15:07:42 2012]Local/ESSBASE0///1111554368/Warning(1051003)@ Error 1053010 processing request [Lock Object] - disconnecting

Cannot open cube outline. null[[
com.essbase.api.base.EssException: Cannot open cube outline. null
at com.essbase.server.framework.EssOrbPluginDirect.ex_olap(Unknown Source)
at com.essbase.server.framework.EssOlapMetaDataService

We need to unlock all the objects in the db to solve this issue

Step 1

Log-in in to the MAXL form the command prompt

navigate to the startMAXL.sh script and start it

Using MaxL, you can automate administrative operations on Essbase databases. You can write MaxL scripts with variables to make them customization and reusable.For Essbase to receive and parse MaxL statements, you must “pass” them to the Essbase Server using either the MaxL Shell (essmsh), Administration Services, or a customized Perl program that uses the MaxL Perl Module, which enables you to embed its statements in Perl programs.

[oracle@faht bin]$ ./startMAXL.sh

Essbase MaxL Shell 64-bit - Release 11.1.2 (ESB11.1.2.2.001B3010)

MAXL>

Step 2

Syntax :login <username> <password> on localhost:10215

MAXL> login faadmin <password> on localhost:10215;

WARNING - 1040132 - Opening a wallet(path) failed(28759).

WARNING - 1040156 - SSL initialization failed with error code [1040132]..

OK/INFO - 1051034 - Logging in user [FAADMIN].

OK/INFO - 1241001 - Logged in to Essbase.

Step 3

Unlock all the objects

To Unlock all the objects which is in the particular db we need to proceeded with this command

Syntax : alter database <database_name>.db unlock all objects;

MAXL> alter database OIC_ACCOUNTING_FLEX.db unlock all objects;

OK/INFO - 1056023 - Database OIC_ACCOUNTING_FLEX.db altered.

Step 4

Check the application status by using the display application

MAXL> display application;

application comment startup autostartup minimum permission connects commands updates security lock_timeout max_lro_file_size application_type application_locale server application_status elapsed_time users_connected storage_type number_of_databases

+-------------------+-------------------+-------------------+-------------------+-------------------+-------------------+-------------------+-------------------+-------------------+-------------------+-------------------+-------------------+-------------------+-------------------+-------------------+-------------------+-------------------+-------------------+-------------------

OIC_ACCOUNTING_FLEX Standard Applicatio TRUE FALSE no_access TRUE TRUE TRUE TRUE 3600 0 3 English_UnitedState fah. 2 02:00:54:55 0 4 1

OIC_ACCOUNTING_FLEX Standard Applicatio TRUE FALSE no_access TRUE TRUE TRUE TRUE 3600 0 3 English_UnitedState fah. 0 00:00:00:00 0 4 1

OIC_ACCOUNTING_FLEX Standard Applicatio TRUE FALSE no_access TRUE TRUE TRUE TRUE 3600 0 3 English_UnitedState fah. 2 02:00:54:55 0 4 1

WARNING - 1241024 - Possible string truncation in column 2.

WARNING - 1241028 - Output column defined with warnings.

WARNING - 1241024 - Possible string truncation in column 14.

WARNING - 1241028 - Output column defined with warnings.

OK/INFO - 1241044 - Records returned: [3].

Unlocking the account which shows as active in OIM and ODSM

UNLOCKING THE ACCOUNT WHICH SHOWS AS ACTIVE IN OIM AND ODSM

The account status is shown as active and unlocked in the OIM and odsm but the account is locked to verify this we need to check the two parameters in the ODSM navigate to the particular user account and search the two parameters oblockouttime .oblogintrycount

If the oblockouttime has the value in it then the account is locked ..

Scenario

when we are trying to log in to the fusion applications which gives the error and redirecting to the forget password page..

check the account status in the OIM and the account is locked ... we need to unlock the account and reset the password in the OIM and checked the fusion applications log-in ..
But still the fusion applications log-in with the OAM SSO fails .. redirecting the screen to the forget password
Then follow the steps to unlock the account in ODSM

Step 1

Log-in to the fusion applications
and gives the message with the account is locked and use the forget password utility

Step 2

Unlock the user account in the OIM
log-in as admin user to the OIM and navigate to the administration tab and search the user name..which the account is locked ..unlock the account by clicking the unlock account symbol on the top

Step 3

Reset the password for the account

we can reset the password through manual or the system generated password the New password will be send to the end user through the email if we select the check box email the password to the new user
The notification template for the password reset [reset password]

Once the new password is create then check run the LDAP sync process

Step 4

Run the LDAP User Create and Update Reconciliation Job from the OIM
Navigate to the advanced tab in the OIM and select the scheduled Jobs
in the scheduled Jobs Search for Ldap* and you will fins all the Ldap related scheduled process Run the Job

Step 5

Check again in the fusion applications but still the user are not able tot log in into the fusion applications and gives the same error
check the status of the account in the of tin the ODSM and OIM in both the consoles it shows as the account is active

Check the account status in the OIM

Check the Account status in the ODSM

In both OIM and ODSM the account is unlocked but it gives the locked message when we try to log in from fusion applications

Step 6

we need to check the two parameters in the ODSM to conform the account is locked or not

[1]oblockouttime
[2]oblogintrycount
These are the two parameters which we need check for the account status

For the oblockouttime the value is present then The account is locked

lock and unlock the account the OIM and check the values for the oblockouttime
once the account is locked and unlocked the values which is present in the parameter for oblockouttime will be erased
But still if the value is not erased then we need to manually remove the values for the two parameters remove the value from the oblockouttime and change the oblogintrycount to 0

Step 7

Retrieve Latest LDAP Changes Process from the Fusion Applications

Navigate to the schedule process in the fusion applications and then select the Retrieve Latest LDAP Changes Process and run it

Select the process from the schedule new process tab

Run the process as soon as possible

Check the process had executed successfully

Out Put of the Process

Starting User Sync
Number of users returned from ldap: 185
User Sync Ended: New User Count = 2, Updated User Count =5
Starting Roles Sync
Number of roles returned from ldap for lang US: 500
Role Sync Ended: New Role Count = 2, Updated Role Count =0
Starting User Role (Granted Roles) Sync
Total Number of Granted Roles were modified = 3

Now try to log-in from the fusion applications with the effected user and the user will be able to log-in